Quote:
Originally Posted by JSWolf
CSS is not a buzzword. It's the set of instructions that says how to format th eBook. If the program doesn't respect the CSS, then you don't get the formatting you should and that's a bug that should be reported so it can be fixed.
|
It is a buzzword, Jon. Each engine has their own set of rules to render html. Here's
chromium's html.css. The fact that your desired epub file doesn't override most of them doesn't mean they're not applied.
Before reporting "rendering differences" between engines you should check that the "root" rules are equal. For instance KOReader uses
epub.css for lean & mean epub files and
html5.css for generic web-like stuff.
Claiming that CREngine doesn't support a given tag just because it is applying "epub.css" rules don't help. Of course your book might override some rules but knowing
how CSS inheritance works is helpful.
I'm not aware how to change Coolreader rules (or if it's possible at all). On KOReader you can set them on document styles (see attachment). Users are suggested to apply
what about if html5.css before reporting issues.