Quote:
Originally Posted by JSWolf
Any eBooks that's ePub3 that can be converted to ePub2 and lose no functionality is ePub2 in an ePub3 wrapper. Yes, I know it's a valid ePub3, but it doesn't need to be ePub3. I think this is being done just so the publishers can say they sell ePub3 eBooks. It's very easy to convert there ePub3 to ePub2, have less code bloat and they still work the same.
With these ePub3, if you read them in a true ePub3 renderer, do you get any functionality over the same eBook being in ePub2?
|
Stop saying "true" epub3. It's making you look foolish. The conversation is not about functionality. What "functionality" did epub2 offer over OEBPS? For that matter, what functionality to epub2 provide over straight-up xhtml/css? Why did we need a special container for the presentation/navigation of html content at all?
Clearly the world at large does not believe that the be-all end-all factor in the decision to adopt new specs/formats is having new "functionality" available. Only you do.
The docx format did not offer me a single advantage in the presentation of multiple paragraphs on a page over the .doc format. Yet nearly all my documents have been updated to the new format.
Oh, and there's no code "bloat" in epub3 when it comes to text-only, reflowable books. In fact, the contents of a text-only book might have less markup when coded as HTML5/Epub3 then it would be as XHTML/Epub2. You're showing your lack of knowledge yet again.