Quote:
Originally Posted by nabsltd
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.
|
The code that handles ePub 2 also handles the DRM. If Kobo went with the newest version of RMDSK, then maybe they could do away with Access (the renderer for kepub/ePub 3). But then they'd lose kepub.