Quote:
Originally Posted by dmapr
I've sideloaded Amasis, Caecilia, Gill Sans & Malabar fonts from the Nook onto the Aura (the Nook versions have Cyrillic glyphs in them while Kobo does not). All of the fonts continue to show in the list with advanced options available for each, however only the Gill Sans is the sideloaded one, the other three are still the original ones. As far as I can tell all the fonts are named properly (internal name matches the filename with attribute specifiers). Any idea on why Kobo picks up the sideloaded Gill Sans but not the others?
|
I don't know of anyone else who has reported trying to replace an existing Kobo built-in font with a sideloaded font of the same name. I deliberately only sideloaded fonts without a built-in equivalent already present.
Regarding
Gill Sans, I wonder if it's a coincidence that the only one of your test fonts which DID work is the one whose built-in equivalent DOESN'T currently work properly (
bold instead of italics problem)? The other built-in fonts which are currently known to be problematic are
Kobo Nickel and
Avenir Next.
As an aside, I've also occasionally wondered whether it's a coincidence that the 3 problematic built-in fonts are the ones containing a space in their name?