View Single Post
Old 05-01-2019, 10:06 PM   #11
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,572
Karma: 169115148
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by pedrovic View Post
Thanks, "DNSB" and "theducks" for the tips.
I tested in Sigil and Kindle Previewer and it's OK.

One more question: can I change <h3> to <h1> for a better HTML semantics?

Best,
Pedrovic
Since I use css classes to control the appearance, my preference is <h1> is used for books in a omnibus/box set, <h2> is used for parts within a book and <h3> is used for chapters. I've occasionally used <h4> for sub-chapters but that's been pretty rare. If I get to the point where I might need <h5> or <h6>, I find myself looking at the book structure instead.

I might ask why using h1 instead of h3 would be better HTML semantics? They should be used for heading levels from h1 to h6. In my case, consistency says a single book would not get a <h1>, a book without parts would not get a <h2>, etc.

Last edited by DNSB; 05-01-2019 at 10:09 PM.
DNSB is offline   Reply With Quote