Thread: Why ePub 3?
View Single Post
Old 09-18-2017, 04:00 PM   #33
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,728
Karma: 205159604
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by nabsltd View Post
I would be shocked if the underlying HTML/CSS renderer for a reader that understands EPUB3 changes when the reader encounters an EPUB2.
You shouldn't be shocked at all. Bookari uses Readium for its EPUB3 rendering engine and RMSDK for EPUB2. Many dedicated devices also use entirely different engines for rendering the different formats they make available via their walled gardens. Do you think Kobo's kepubs are rendered with the same engine they use for presenting their regular epubs?

In all honesty, I would be more shocked if a reading system that supports EPUB3 didn't use an entirely different rendering engine than it does for its EPUB2 content.
DiapDealer is offline   Reply With Quote