Quote:
Originally Posted by DiapDealer
You shouldn't be shocked at all. Bookari uses Readium for its EPUB3 rendering engine and RMSDK for EPUB2.
|
Although this may be, it makes no sense.
After the determination of whether a file is EPUB2 or EPUB3, the metadata read gets done, and the structure of the book sorted out by the program. At that point, it should then pass the first HTML page to the HTML/CSS renderer, and having different ones is merely code bloat. There is nothing in the HTML of an EPUB2 that will render incorrectly using an HTML/CSS renderer that is EPUB3-compliant.
Quote:
|
Do you think Kobo's kepubs are rendered with the same engine they use for presenting their regular epubs?
|
I've never seen the HTML inside a kepub, but based on the MR Wiki description, again, using another HTML renderer is just useless code bloat. The kepub reader and epub reader could use the same HTML/CSS rendering engine. The extra kepub features are merely for navigation and annotations, and the next level above the renderer should pay attention to them. Also, there is zero need for the extra HTML to allow the reader app to offer those same features...most of them are available on EPUB on Kobo readers, too.
Basically, this is another case of a company that builds decent hardware but can't write good code.