Quote:
Originally Posted by DNSB
The ACCESS renderer would be the equivalent of a HTML 5 browser in a world where most of the content is still being programmed for HTML 4. Adobe's RMDSK is fine for epub2 compliant files but, at a pace best described as glacial, the publishing world is moving in the direction of epub3.
You can view a non-DRMed epub3 ebook with an epub2 renderer but quite a few strange glitches where the standards differ and use of some epub3 features such as the improved SVG image handling will cause the ebook to be pretty much unreadable on an epub2 renderer.
The Kobo app on my iPad and Nexus 7 are capable of working with DRM free .epub files which is why I use them since that way the choice is pretty much transparent to me (iTunes to copy the epubs for the iPad, file copy for the Nexus 7, syncing over the network for .kepub ebooks on either). The Kobo app will not work with Adobe ADEPT DRMed epubs which limits borrowing library books or purchasing on the web. I've also purchased a couple of DRM free ebooks and downloaded and opened them on iOS and Android but not my normal mode of operation. Mostly concerns about connecting to a network outside home or work and sending sensitive information. It's not paranoia if you know they are out to get you! 
I would agree about converting epub to kepub.epub at home - it seems to be a crap shoot. But then such conversions are not a supported mode so I can't blame Kobo for any problems.
Regards,
David |
My understanding is that Kobo makes the majority of money from selling books. Correct me if I am wrong. This is what I fail to understand about the big push for the access renderer. If they decide to go exclusively access than they cut off customers with non Kobo devices. Sure we can convert but even then some might resent the necessity and many people can't or won't. And it is not in a bookseller's interest to encourage conversion.
No skin off my nose, just do not understand the big picture I guess
Helen