Quote:
Originally Posted by doubleshuffle
@Danger:
Yeah, that's what Anak explained in his post he linked to. Unfortunately, that correction works only if the font IDs also end in -Bold, -Italic, etc. As soon as they are different, you are screwed unless you get a font creation program; which I will probably do now. Nice thing to be forced to do after buying "the only premium eReader on the market".
|
As far as I can tell, if you have the font names correct for sideloaded fonts, a Kobo ereader has no problems with using the fonts and variants correctly. I installed a couple of fonts that had Oblique variants instead of italic but renaming, as an example, the Oblique font file to Deja San-Italic.ttf uses the oblique font for italics.
As George Talusan once commented: "
This is true. The Adobe SDK allows us to specify a URL to a font file but Qt doesn't allow us to introspect a TTF/OTF for its font family/weight without difficulty.
The resolution is that fonts should end with -Bold, -BoldItalic, -Italic, or alternatively, b, i, z."
The font name used in naming the font file must be the font name (Windows font viewer) or font family (FontForge) embedded in the font file -- if a font is named GillSans-Bold.ttf but the internal name is Gill Sans, the file must be renamed to Gill Sans-Bold.ttf to work on a Kobo ereader. Alternately you can edit the font family name but much easier, in my opinion, to change the font file name.
There are other issues pointed out by Anak if you start using other font variants such as a semi-bold instead of a normal in order to get a darker glyph on the eInk screen. You will need to change some of the internal naming but that is not an issue for the majority who are not into editing their own fonts.
Regards,
David