View Single Post
Old 05-19-2013, 05:57 PM   #9
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,076
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Anak View Post
Hopefully this will improve with a full epub3 renderer. I don't know is Kobo planning to use the new Readium engine or adds epub3 support to the engines they currently use.
I don't know if Kobo (or other vendors) update their current line of devices with the most recent available versions of the engines.
But open source projects (like OpenInkpot) seems to be all dead.
I'll wait for an installable version of KOreader to check it out (and find some bugs too).
ACCESS and Kobo are both members of Readium and the ACCESS renderer is partly EPUB3 compliant and, from their website, is moving in the direction of full EPUB3 compliance.

The problem being is that Kobo still uses the Adobe engine for epub2 files. I suspect this is mostly for compatibility with Adobe's ADEPT DRM scheme which is used for most DRMed epub files. Adobe did have a roadmap for EPUB3 but that road map has disappeared.

As for the ARM engine update, that's hard to tell. The file dates seem to change but that could just be an artifact of the build process.

Regards,
David
DNSB is offline   Reply With Quote