Installing fonts

[Pajamaman]

I'm having trouble getting Koreader to see custom fonts. I've installed the .otf and the .ttf version of Caecilia and the .ttf of Rockwell in the koreader/fonts folder, both in subfolders dedicated to the fonts, and the actual root of the /fonts folder. Koreader doesn't see them. Does anyone know what I'm doing wrong?

[Frenzie]

Could be that they're blacklisted for not working?

https://github.com/koreader/koreader....lua#L137-L188

[NiLuJe]

If they're either blacklisted or using an already registered family name, they'll be dropped. You can check the crash.log for more details about what's happening in your case.

[mkozlows]

Originally Posted by NiLuJe

If they're either blacklisted or using an already registered family name, they'll be dropped. You can check the crash.log for more details about what's happening in your case.

Okay, so I'm hoping somebody can help me out with this, because I'm sort of at my wit's end about what I'm supposed to do. Trying to load a family of fonts onto the Kobo for use with KOReader.

In Fontforge, if I set the font family to "Whatever-Regular", "Whatever-Bold", "Whatever-Italic", and "Whatever-BoldItalic", to match the "Fontname" field (and the .otf filename), then they all load... but they show up as four separate and unrelated fonts.

If I set the font family to "Whatever", with the "Fontname" including the "-Bold" etc modifiers, then only the first one (bold) loads, and the rest get a "ERROR failed to register crengine font" log entry, and using that font just displays everything in bold.

It feels like I should be setting them all to the same family -- and doing that makes the font work in the Kobo's default reader software -- but I'm clearly missing something here. I've googled around, but can't find a thread with more relevant info than this.

Any ideas on what I'm missing or doing wrong?

[NiLuJe]

If you have access to a Python setup, just use gftools' nametable-from-filename tool.

(c.f., http://trac.ak-team.com/trac/browser...s/REMINDER#L96)

[mkozlows]

Thank you! That did it. I'm not quite sure what it did (it's definitely using the same font family like I was trying), so it must be doing something non-obvious in one of those Panose tabs or something, but the important thing is that it works now.

[NiLuJe]

IIRC, CRe doesn't give a lick about the Panose stuff, the (moderately crappy) heuristic only cares about the OS/2 name tables.

And, yeah, a common Family, and the Style properly set in the right place (but not in the family name itself) should be enough.

It's generally not an issue, but, gftools does the right thing, and as my notes explain, it also does part of the right thing to make both ACCESS & RMSDK happy too, so, win-win-win .