Quote:
Originally Posted by Sarmat89
It is obviously better, as it is more clear this way than generic divs/paragraphs with arbitrary classes assigned.
|
But surely using a standardized class is just as good.
So what is really needed is publisher consensus. Or at the absolute worst, an extension to XHTML.
Quote:
|
Once again, (X)HTML was designed for computer manuals, not books.
|
Oh no, whatever shall we do -- Wikipedia is wrong!
https://en.wikipedia.org/wiki/XHTML#Motivation
XHTML is HTML defined as a strictly XML-compliant form, which means it will error out on malformed XML.
It's useful for programmatic parsing, not for specific
genres of
ebooks.
Quote:
|
Take any book and tell me what elements have its semantic representation in HTML: Title page/Title -- none, Dedication -- none, Epigraph -- none, chapter titles -- none again, 'letters' -- none! Everything has to be imitated with the direct formatting!
|
I don't consider "direct formatting" to be a flaw.
TItle pages, dedications, epigraphs, chapters are all
documents, they are separate XHTML pages.
And the EPUB manifest recognizes "type" semantics declared in the <guide>. Like the ones calibre's editor knows how to place, including "title-page", "toc", "index", "glossary", "acknowledgements", "bibliography", "colophon", "copyright-page", "dedication", "epigraph", "foreword", "loi", "lot", "notes, "preface", and "text".