View Single Post
Old 04-26-2018, 12:15 PM   #43
roger64
Wizard
roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.
 
Posts: 2,608
Karma: 3000161
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
Thank you sherman for your information and examples.

So ligature display can vary according to the font (Alegreya > Georgia), the renderer (RMSDK > creengine (for koreader)), the subsetter (to be determined) and probably some other - yet- unidentified factors.

The subset of a defective -on this regard- font, will not display ligatures. The subsetter has nothing to do about it. That's why it would be unfair to speak about a "bug" of the subsetter without providing an example. Examples will help us ascertain the origin of the defect. It's not a test.

Last edited by roger64; 04-26-2018 at 12:23 PM.
roger64 is offline   Reply With Quote