Quote:
Originally Posted by Mister L
When the TOC is made, Sigil already knows what each TOC entry should say and what part of the document it is linked to (whether it harvested the info from title attributes or otherwise).
|
The problem is that heading formats aren't predictable. You yourself gave two examples. In the first example, the heading consisted of two
<h1> tags and in the second example it consisted of
<h1> and
<h2> tags.
BTW, both problems can be easily fixed with the right regular expressions. For example, you could use the following expressions to merge the two <h1> tags:
Find:<h1 epub:type="title" class="part_n"><span>(\d+)</span></h1>\s+<h1 epub:type="title" class="part_tit"><span>(.*?)</span></h1>
Replace:<h1 epub:type="title" class="part_n" title="\1: \2"><span>\1</span><br /><span class="part_tit">\2</span></h1>
If you process the first heading format with it and then generate the TOC, Sigil will add the following entry:
4: The Whale speaks of what she has learned about humans