View Single Post
Old 05-19-2013, 03:28 PM   #7
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: 46,768
Karma: 169712580
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by ShellShock View Post
And even if Adobe did fix this bug, how confident are we that a new release of Adobe reader mobile would not contain new bugs? Kobo probably cannot devote a lot of resources to a full regression test, so they probably prefer to direct effort to kepub support instead, i.e., where they control the software development.
Actually, Kobo does not control much of the software development for kepub support since they use the ACCESS NetFront BookReader software. I'd suspect that Kobo would have more influence with ACCESS but that's just a personal opinion with no visible means of support. ACCESS also uses quite a bit of open source which is downloadable if you want to go through the 93MB tarball for the BookReader software.

http://gl.access-company.com/news_ev...2012/120712-2/

Regards,
David
DNSB is offline   Reply With Quote