In general, I recommend reading the manual. There's
a section for the TOC editor.
Quote:
Originally Posted by Kivgaen
Hmm...
So what if your .epub document was generated with automatic styles, and uses the following code:
Code:
<p class="h1"> Heading 1</p>
<p class="h2">Heading 2</p>
<p class="tf">First paragraph without any indent</p>
<p class="tx">Second paragraph, with indent.</p>
with associated styles already generated...
If I already have the above structure, and I don't want to screw it up or mess with the way my document looks, THEN how would I generate a TOC? |
With Sigil, you wouldn't be able to use that markup to create a TOC. On a related note, using paragraph elements for headings with "h1" classes is... not a good idea. Far from it. It would be much simpler to just use
Code:
<h1> Heading 1</h1>
with the styles applied to the "h1" class applied for all h1 elements. This approach also uses nice semantic markup.
You could easily convert to this scheme with a regex search&replace operation.