On physical epub readers with user line-height, like a Kobo, it's fixed if it's set in the ebook. If there is no setting, then the user can change it easily from no spacing to more than double spaced. The font metrics set larger relative spacing for larger fonts.
Also you see the absolute space is different on different fonts of the same size.
There is less control on a Kindle, but none if the line-height is set.
I forget what the iRiver, Sony, Nook etc do.
Different Andriod apps behave differently.
KOReader can override CSS like line-height. Many apps won't.
I don't like naked tags. I think it's less error prone that at least <p> and <hx> have classes in the CSS.
This is a good point:
Quote:
|
On the other hand, if your stylesheet only referenced .chapterheader {}, then it doesn't matter if that class name is in an h1, an h2 or even a p, it will still get applied.
|
You want to be able to change the tag (semantics if you like) without unexpectedly changing the visual rendering.