View Single Post
Old 06-11-2013, 10:11 AM   #322
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,260
Karma: 171291590
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by guma View Post
Assuming you are speaking for KOBO here: From a customer perspective this point of view is just plain not acceptable. epub2 is the current standard and should work properly. Even if epub3 comes along at some point in the future many people will still have epub2 files they want to read.
As is shown by the ACCESS renderer on the Kobo ereaders being able to display an epub2 file simply by renaming it to .kepub.epub, an epub3 compliant renderer is able to display epub2 ebooks. Given that money and developer time are finite resources, Kobo is likely to feel that they are better served by concentrating on the future. The only good reason I see for Kobo keeping the Adobe RMSDK code in place is to handle Adept DRMed books either purchased or through a library loan.

Regards,
David
DNSB is offline   Reply With Quote