View Single Post
Old 09-10-2024, 05:43 AM   #3
babadockia
Zealot
babadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshesbabadockia can read faster than his screen refreshes
 
Posts: 112
Karma: 14166
Join Date: Jun 2013
Location: Stockholm, Sweden
Device: kobo aura hd, trekstor pyrus maxi with texet 138 firmware
Quote:
Originally Posted by jonnyl View Post
So in the same book, all other settings being equal, other fonts would display correctly?

I'm not sure what the problem could be. One thing you could do is check the koreader/crash.log file, which logs the start-up process of KOReader (among other things). If those fonts don't load correctly, it would register in that log file. In that case, the fonts don't meet technical specifications required by the rendering engine, and there's probably not much you could do.

It's still unusual though that it would fall back to an italics font. KOReader doesn't depend on filenames to determine font style by the way. Have you used the fonts on a computer or different ereader (or Nickel) and they work fine there?
yes, only with those fonts and, oddly enough, they render correctly on nickel
babadockia is offline   Reply With Quote