View Single Post
Old 02-07-2015, 06:36 PM   #117
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by fjtorres View Post
How are the Kobo readers with sideloaded epub3? New ones, old ones...?
I'd imagine it depends on the EPUB.

All my books are EPUB 3, but they provide a full complement of EPUB 2 metadata, with the exception of the HTML TOC being in a different format that is more appropriate for EPUB 3, but should still work fine on anything that can render HTML. So barring the reader simply being stupid and having an assert(epub.version = 2) or some other such nonsense, it ought to work.

However, it is also possible to build EPUB 3 books without any of the EPUB 2 compatibility features (e.g toc.ncx). Those books could range from somewhat broken to completely unusable on an EPUB 2 reader, depending on the reader.

Either way, though, this is going to affect three books that I'm about to ship, so I'm now having a serious debate about whether to offer my books through Kobo, and if so, whether to ship them a slightly different EPUB file built with my toolchain set to EPUB 2 mode just so they won't do this. I'm going to get in touch with Kobo and I'll let you know if I hear anything back from them.
dgatwood is offline   Reply With Quote