Quote:
Originally Posted by Vroni
Ok, more preciously asked: what is the difference between H-Tags and sequential H-Tags?
|
Ducky means doing something like this:
Chapter One (H1)
It Was A Dark And Stormy Night (h2) (or H1)
When you try to format TOCs, automatically, that sort of thing can bollix up the layout AND semantically, it's somewhat wrong. After all, from a structural standpoint, the chapter number-title is a single point; the chapter "head." Right? There isn't outline difference between the two; the title isn't a subhead to the chapter number.
Ducky--I have no problem with how you do that, using spans or whatever. It's "more correct" than using a heading class for it, IMHO. Some people "solve" it by wrapping the entire kit and kaboodle in a heading tag and using a break, but we all know the problems inherent in that.
@Lumpy:
When the goal is to have very short CSS--which is in and of itself, a good goal--you can end up doing what standardebooks.org does, which is using combinators, but there's a huge blind spot there, with the assumption that those will work, no matter what. I'm the first to admit that I'm overly-aware of the older devices, due to my work and constant attention to the older Amazon Kindles, but KF7 devices won't pay a lick of attention to a combined class. I downloaded Sayers' "Whose Body," for example and I see that in their ePUB3 (which was allegedly their ePUB2.0, mind you) they used first-child inside a blockquote coupled with breaks to create two lines of verse.
To me, that's somewhat make-work. Why not use a simple indented paragraph class instead? (Yes, someone could argue that semantically, lines of a poem are more "blockquote" than paragraph, but...c'mon...). They used the same coding for LPW's business card, handed to someone. thus, it's their "go-to" for anything that they feel should be indented and set off with vertical whitespace above and below the cited text.
So...you know, one of the reasons that it's hard for formatting companies to "fix" other businesses' or individuals' formatting is just that--HTML and CSS are very individualized. Sure, a p is a p, and all that, but by the time you figure out what someone else has done, it's cheaper to redo the whole damn book.
Hitch