Quote:
Originally Posted by Vetchy
But I have one hypothesis. Can we got some font, like Georgia and rename it to Avenir, after it create patch wich replace Avenir by new font in firmware?
|
If I've understood you correctly, the problem with this theory is
- the Kobo looks inside the font files for the font's name not just at the filenames
- Kobo's built-in fonts are either encrypted, obfuscated or some other locking method
so, unless someone knows otherwise, simply trying to "fool" it isn't going to work.
When I tried to replicate your images from post #319 I got a different result. I still saw a problem with the Avenir fallback font used for the Cyrillic characters, but I didn't get Georgia as the fallback. My result was even uglier than yours because the fallback font (probably one of the CJK fonts) did show the Cyrillic characters but they were double-spaced.
This leads me to ask whether you have any other font hacks installed? I have a vague memory that a long time ago some Cyrillic users had a hack to physically remove these problematic built-in fallback font(s) so that Georgia would be used instead.
This is just an idea, but if you
are using that hack without problems, then maybe extending it to also physically remove the Avenir fonts would automatically default to using Georgia as fallback whenever one was required. I must stress that I haven't (and won't be) testing this myself. I've no idea whether it could cause chaos.
In the meantime, if you want to try a more benign, but only partial, solution you could try the attached simple patch. In your image 2, it should force to Georgia, the chapter name/book title parts of the new header/footer respectively. It's not what you wanted but it's the best I can come up with right now. It won't be added to the kobopatch standard pack in it's current form but it's generic enough that it may survive across firmware updates.
Put it in nickel.yaml or wherever you store any other custom patches for nickel.
New header/footer font-family - beta