Quote:
Originally Posted by rashkae
Just the way CSS works. (in conjunction with ADE, which is used by Kobo to display epubs, and which Kobo can only modify in limited ways, per licensing agreements with Adobe.)
It makes perfect sense that Kobo silently appends body {attributes} into an e-book CSS (per user preferences) and ADE uses those as it should to display the books. However, if the body has a class, the values of body.class would then take precedence.
Features are not bugs, even if you don't want them and would rather be without, it's still working as designed. Whether or not this particular idea is bad... I'll leave to the jury. I already said my piece on that.
|
OK, now that I understand the issue a little better, I need to ask: How should one go on about displaying the fonts as defined in the epub (apart fro making sure the specific font is available in the reader)?
Should there be an option in the reader to over-ride user choice and use embedded fonts if available?