Quote:
Originally Posted by DiapDealer
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.
|
ePub2, NCX Toc, HTML ToC
ePub3, NCX ToC, HTML ToC, NAV ToC
ePub3, all those extra meta property lines in OPF
ePub2, none
ePub3, span epub:type
ePub2, none
ePub3, iBooks reference in the OPF header
ePub2, nothing to do with iBooks
ePub3, <section></section>
ePub2, none
As for the container, we do not a container to hold all the files together. Imagine the mess we'd have if all eBooks did not have a container and all we had was just the files for the eBook.