Quote:
Originally Posted by kovidgoyal
Neither do divs. In fact nothing in HTML implies a chapter break, since chapters are not a concept the HTML spec addresses.
|
Exactly, which is why the import procedure specifies these interactions. If they were defined somewhere, I wouldn't have needed to specify them.
Quote:
Originally Posted by kovidgoyal
in the context of ePub widely accepted practice is to put each chapter in a separate HTML file.
|
I think you may have lost the jist of this discussion. ePubHub creates separate Xhtml files already.
The ePubHub import feature currently can import existing Xhtml files, which it stores in a separate "document" object which will get rendered during the ePub export function back into a separate Xhtml file. The existing ePubHub Xhtml import feature will also import several Xhtml files at once, again storing each into a separate "document" object.
In order to facilitate importing an entire book stored inside a single Xhtml file while maintaining it's structure, a specification for the use of divs to define chapters/parts/cover-pages was introduced.
By following this specification, a book stored as a single file will then be split into multiple "document" objects, which would be rendered as multiple Xhtml files in an ePub.
What DaleDe believes is that h tags can be used to define the structure of an entire book. Nothing in Html, Xhtml, ePub, Ncx, Opf, Daisy or any other standard that I have come across supports this belief. The ePub specification itself does not even use h tags for constructing the table of contents.