Thread: Why ePub 3?
View Single Post
Old 09-18-2017, 03:38 PM   #32
nabsltd
Fanatic
nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.
 
Posts: 528
Karma: 9529956
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by DiapDealer View Post
The answer is "all of them". Epub3 engines render Epub3s using epub3 specifications.
I would be shocked if the underlying HTML/CSS renderer for a reader that understands EPUB3 changes when the reader encounters an EPUB2.

Basically, the reason that readers that understand EPUB3 render better is not because of the EPUB3 part...it's because the HTML/CSS renderer has been upgraded along with the EPUB unpacker. There are many EPUB2-only readers that handle a lot more HTML/CSS than is actually legal in the EPUB2 specification. In the same way, a reader that understands EPUB3 will likely handle more HTML/CSS than is required by the EPUB3 spec, simply because the HTML/CSS renderer is newer.
nabsltd is offline   Reply With Quote