View Single Post
Old 03-03-2013, 11:10 PM   #31
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: 35,498
Karma: 145557716
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by ShellShock View Post
Your are a star sir! That works for me, and also fixes all the other broken side-loaded fonts, regardless of locale. Have some freshly baked karma.

I think the Kobo 2.4.0 firmware looks for a font file in the following format:

Font Family Name-Font Subfamily Name.ttf

Font Family Name must have the same spacing as in the font itself.

Font Subfamily Name is normally one of:

Bold
Italic
BoldItalic
Regular

You do not need a space in "BoldItalic", even if there is one in the font file ("Bold Italic").

.otf file extension is also supported.

Firmware 2.1.5 would find a matching font file even if there were no spaces in the file name but there were in the Font Family Name within the font. For some reason after 2.1.5 this was changed so that the spacing had to be the same for the font to be found.

Some of the built-in fonts are still broken e.g., Avenir and Kobo Nickel, presumably because the internal font file is actually called "KoboNickel-Regular.ttf" etc.
You can also use i b and z as in the builtin Georgia font where the filenames are georgia.ttf, georgiab.ttf, georgiai.ttf and georgiaz.ttf. The -Regular is not needed but I use it just to keep the file naming convention consistent. At this time, I can't open the built-in font files to see what their font family names are since they report as not being a valid font file.

Regards,
David
DNSB is offline   Reply With Quote