View Single Post
Old 02-09-2019, 12:44 PM   #42
forster01
Groupie
forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.
 
Posts: 197
Karma: 82624
Join Date: May 2013
Device: Kobo Forma, Kobo Aura One, Kobo Aura HD, Kindle, Amazon Fire HD
Question

Quote:
Originally Posted by jackie_w View Post
Probably not. It's more likely that it's a combination of the way that particular book has coded its HTML/CSS and the aggressive overrides the kepub renderer uses in order to try and enforce your chosen settings in your device's font menu. The epub renderer uses less aggressive override rules.

It's almost certainly fixable but it depends whether you want to do the work.

Solving CSS overriding problems like this (font-family, line spacing, text alignment) usually involve a combination of manually editing the HTML/CSS for that particular book and/or making the kepub override rules less aggressive on your Kobo. The latter can be done via various Kobo patches but as this will affect all your books afterwards it may have unwelcome consequences for some books if/when your font menu choices are not enforced when you want them to be.
Apparently it is a bug. When a font is defined in for example h1 class it won't be shown. It will be visible only as span class font-family. In kepub that is.

Last edited by forster01; 02-09-2019 at 12:46 PM.
forster01 is offline   Reply With Quote