Thread: Glo 2.4.0 bugs
View Single Post
Old 02-24-2013, 02:47 PM   #83
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,997
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by ShellShock View Post
That is correct. Some fonts, INCLUDING KOBO'S OWN NICKEL FONT, are broken when using any locale, INCLUDING THE DEFAULT en_US. You have to change the font name AND make sure you have a matching locale, for them to work. In my book this makes it a bug.
I have Charis SIL on my Glo as my main font since I read quite a few books that are enhanced by it's support for diacriticals. I tried changing from en_CA which is my normal locale to nl_NL, en_GB, en_NZ, fr_CA, fr_FR and ja_JP and I could see no difference in the behaviour of the Charis SIL font using my font tester epub. Strictly speaking, "Charis SIL Modified" as modified by JS Wolf with the font file names changed to the naming convention required by a Kobo reader from his original font file names.

Regards,
David
Last edited by DNSB; 02-24-2013 at 03:04 PM.
DNSB is offline   Reply With Quote