View Single Post
Old 12-20-2012, 02:04 PM   #4
ShellShock
Wizard
ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.
 
ShellShock's Avatar
 
Posts: 1,178
Karma: 2431850
Join Date: Sep 2008
Device: IPad Mini 2 Retina
On my Glo (firmware 2.1.5) I have noticed the same problem with ligatures, particular "ff" in the word officers, which is displayed as "o icers". This only happens with certain fonts; for example Kobo Nickel (built in) is OK, as is Charis SIL (side-loaded) but other side loaded fonts (e.g., Fontin) display the problem. Charis SIL has over 4000 glyphs in it, many of them ligatures, whereas Fontin only has about 240 glyphs, and I don't think it has any ligatures. So presumably if I could add the correct ligature glyph to the Fontin font, it would be OK too, but I have not been able to work out what the correct glyph is.

Also, strangely if I copy the epub with the ligature off the Glo, unzip it and then open the html with the ligature in it in a text editor (such as Notepad++), I do not see any ligature character, just two normal "f" characters. It is as though the Glo is converting to ligatures on the fly when it renders the epub.
ShellShock is offline   Reply With Quote