Thread: Glo 2.4.0 bugs
View Single Post
Old 02-25-2013, 01:34 PM   #109
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: 2,235
Karma: 6127887
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Aura HD, Glo, Nexus 7 HD, iPad Air
Quote:
Originally Posted by ShellShock View Post
No problem. I was wondering about including all the special glyphs (fractions, ligatures etc) in the main text line, so that they get displayed in the different font-styles (bold, italics). This would trap the cases where a glyph is present in e.g., normal style but not bold/italic.

I was also thinking about having a whole sample paragraph (of several lines) in normal, to give an idea of the general reading experience with that font.
Go ahead and have fun modifying the file. I have no problems with anyone adding features that they would find useful.

I originally created it when I got tired of seeing square boxes (some empty, some with question marks) in books I was reading so I wanted a quick and dirty test file to allow me to see how well diacriticals were handled. After fun with the various Kobo fonts that, as you noticed, displayed italics as bold and the need to follow the naming convention for add-on fonts, I added the italic, bold, etc. test lines.

Regards,
David
DNSB is offline   Reply With Quote