View Single Post
Old 03-29-2025, 05:22 PM   #6
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,361
Karma: 20212223
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
Quote:
Originally Posted by mt.msla View Post
Well I just decided to use a flattened TOC instead of nesting the OT and NT headers.

(oh well)

So nothing exciting really.
This is obviously water under the bridge, but if you want to re-attack at a later date....and if you HAVEN'T already used the semantically correct <h1-6> tags, then, assuming you've used consistent classes, changing to the correct <h> tags is a fairly trivial find/replace.

The benefit of using the <h> tags, instead of <p class="newchapter"> (or somesuch), is that reading devices/apps can pick up on the standard, and semantically correct, markup for their proper functionality (eg disability or text-to-speech software)... and the editing process (Sigil or Calibre) can use automated tools to make your life MUCH easier.

Cheers!


P.S. Just in case you were wondering if I could work in a few more commas,,,,,,,
Turtle91 is offline   Reply With Quote