View Single Post
Old 09-07-2015, 03:39 AM   #272
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
Quote:
Originally Posted by sherman View Post
I was getting fustrated, because the newer version just wasn't being displayed by Nickel or ACCESS properly, compared to the previous version. RMSDK didn't care.

Today, I found out what the problem seems to be. It seems that Nickel and ACCESS do not like having the PANOSE information set in the font file. I set all values to 0 (any), and now there is no wackiness in either the interface (Nickel) or when reading KEPUB's.


So, it seems fonts destined for Kobo Readers should not have any PANOSE information set.
Thank you! This was the piece of the puzzle I needed to get all my sideloaded fonts to work properly with KePubs.

In each case the fonts I had that didn't work properly with KePubs had the PANOSE weight set incorrectly, I didn't need to remove the PANOSE info altogether, I just corrected the weight so it matched the actual font weights (book/bold.)

The only font that still has problems is the built-in OpenDyslexic font, so perhaps someone could tell Kobo that they need to look at the PANOSE weight for that font?
GeoffR is offline   Reply With Quote