Thread: Kobo Bug thread
View Single Post
Old 04-06-2014, 01:38 AM   #467
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,105
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by bobb40 View Post
I've attached it, and added a comment saying so after all other text. I don't understand the ADE/Access discussion which assigns this bug to ADE; if comments of my original post confuse the issue, tell me what to alter or remove. Thanks.
The Kobo ereaders use two different renderers to display ebooks. If the ebook filetype is .kepub.epub, it will be opened with the ACCESS renderer, if the filetype is .epub, it will be opened with the Reader Mobile renderer.

Reader Mobile is an epub 2.01 compliant renderer from a code base supplied by Adobe who also are responsible for ADE. Many of the issues seen with the Kobo's RMSDK renderer also appear when the ebook is opened in ADE. The major reason I think that Kobo is still using the RMSDK is for compatibility with Adobe's ADEPT DRM management allowing borrowing books from a library and purchasing books from multiple vendors.

NetFront BookReader is an epub 3.0 compliant renderer supplied by ACCESS. Kobo uses it with their own proprietary DRM. It works quite well with epub 3 content from other vendors though Kobo does not officially support such usage. A Kobo produced .kepub.epub has several non-standard items but simply renaming an .epub to .kepub.epub will allow using the ACCESS renderer which is handy when testing.

Both renderers have bugs but different bugs. In the case of your test book, the RMSDK renderer has severe issues with displaying the pages while the ACCESS renderer displayed the pages more or less properly.

Regards,
David
Last edited by DNSB; 04-06-2014 at 01:41 AM.
DNSB is offline   Reply With Quote