View Single Post
Old 01-22-2014, 02:50 PM   #59
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,466
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Rev. Bob View Post
Again, that's completely beside the point. I'm complaining about a problem with Kobo's website, not debating the merits of EPUB3 or advocating its adoption. EPUB3 is only relevant in this thread in that it seems to be the root of the Kobo website bug.

I'm not disagreeing with your points. I'm simply noting that this thread is not the place for that discussion.
We seem to disagree as to whether this is a bug. A decision not to support downloads that could easily not work with most reader software is, to me, not a bug. If you download the epub3 ebook as a .kepub.epub and use the ACCESS renderer to open the file, the publication should render properly. If you download it as an .epub and try opening it with ADE, an RMDSK-based renderer or other epub2 renderer, the experience may not considered acceptable by many.
DNSB is offline   Reply With Quote