Thread: Kobo Bug thread
View Single Post
Old 11-14-2019, 06:39 AM   #1176
John F
Grand Sorcerer
John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.
 
Posts: 7,969
Karma: 71261339
Join Date: Feb 2009
Device: Kobo Clara 2E
Quote:
Originally Posted by jackie_w View Post
Short answer - there will always be some kind of modification needed. The mere presence of a sideloaded font is not enough. You also have to tell the epub/kepub exactly where/how to find it.

Patching firmware isn't compulsory but if you don't, simple edits to each epub will be necessary instead - either manually or via calibre.
I'm not an epub coder and ignorant of the epub specs, but the above (bolded) really surprises me. I'm surprised that it isn't part of the epub standard that if an epub specifies a monospace font family, and the font is in one the RMDSK specified font search locations, that it doesn't get used.

Isn't that the purpose of the epub spec: not needing to know the each implementation of the an epub renderer as to where fonts are stored, how they are named, ...

And in case it isn't clear, I'm not talking about some random mal-formed corner case epub; I'm asking about well formed commercial epubs where the coder knows what they are doing, so they can get expected results on as many platforms as possible.
John F is offline   Reply With Quote