Quote:
Originally Posted by Hitch
...
Headers are not for looks. Headers are structural. ELEMENTS are structural. A word, for example, is subordinate to a sentence; a sentence is subordinate to a paragraph; the paragraph to the first heading in which it is enclosed, etc. This is one of the first things that Cap taught me, way back, when I first ventured into ePUBs, rather than MOBI. Id' used header styling (for something, it's been so many years, I can't recall now--pre-2010, for a certainty) and I was sternly lectured. Rightly so.
Headers tell documents--I don't care whether we're talking about Word, LibreOffice, OO, Scrivener, Bob's Big Word Processor, ePUBs, MOBI's, etc., that this particular element defines a structural part of a document. An H2, for example, is not necessarily smaller than an H1; but it is subordinate to it in the structure of the document. You can make an H2 LOOK any way you want it to; you could make it twice the size of an H1, for that matter.
...
do not use headings, blockquotes, etc., in lieu of proper styling, just to achieve an appearance. That's incorrect coding.
...
|
So true, so true. There is a big difference between structure and styling. If anything, I feel there is too few structure option for eBooks (although DocBook is way too much).
That is also part of the reason why I detest the <em> and <strong> tags over the <i> and <b> tags. The one is about structure, the other about styling and mean something different. They are not the same! I don't mind the tags themselves, but their incorrect usage.