Thread: Firmware 3.8.0 released
View Single Post
Old 09-07-2014, 01:18 AM   #177
Rev. Bob
Wizard
Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.
 
Rev. Bob's Avatar
 
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
Quote:
Originally Posted by JSWolf View Post
The point is that there is no reason for these eBooks to be ePub 3 because they do not make use of any actual ePub 3 features. [...] It's not hard to go back to ePub 2. It just requires editing the OPF header. Not difficult if you copy/paste from an ePub 2 OPF. Then you can get rid of the excess meta data and the excess ToC.
So, to translate - all you have to do to turn a v3 EPUB into a v2 EPUB is get rid of all the v3 stuff and replace it with v2 stuff. Or - wacky idea, but hear me out - you could just leave it alone, since it's got everything a v2 reader needs, so a v2 reader will handle it just fine. I sideload v3 EPUBs onto my Glo, and they work just fine, as long as they're set up to degrade properly - which the reputable publishers who're distributing v3 do, precisely so their books WILL work on existing readers.

Quote:
Originally Posted by JSWolf
What I think should have been done was to extend ePub 2 into ePub 3 and not actually change things that worked fine as is.
That's, um, exactly what they did. That's why v3 permits the NCX file, as a fallback for v2 readers (which will ignore the nav TOC, so you don't need to get rid of it). It's a very common practice - even a necessary one - during periods of transition from one version to the next.
Rev. Bob is offline   Reply With Quote