Quote:
Originally Posted by MicroDrie
The version of the render engine used in the EPUB reader determines what can and cannot be done within the specific EPUB rules.
|
Actually the version of the render engine has very little to do with what EPUB rules they will support. An EPUB3 rendering engine should (and can) support all of the EPUB3 specs. Same for an EPUB2 rendering engine. Devs don't choose to defy EPUB specifications in their rendering engines because doing so would be hard to do. They defy EPUB specifications because they (or their employers) simply don't care about complying with all of it.
Just remember that Sigil is not an EPUB rendering engine. It's a browser that we use to approximate what an epub
might look like on an ereading system. We try to support everything that the epub specifications say should be supported. But it's not to be trusted implicitly. It will also probably support many things that very few mainstream rendering engines will. The devices people will be reading your work on should always be what's used for final testing. It's better to fail gracefully than spectacularly where ebooks are concerned. Unsupported CSS that creates unflattering-looking text is still much, much better than unsupported CSS that creates something unreadable.