[QUOTE=st_albert;1469997
To fix this, globally replace the <p class="whatever"> tags with <h2 class="whatever"> tags (not forgetting the closing tag!) and then in the CSS, change the p.whatever { ... } element to h2.whatever { ...}
Now Sigil will find your chapter headers and create the toc.ncx.[/QUOTE]
Hi Sebastian,
I would suggest care using this method. Let Sigil do a find and count for you (find and replace box) and if you have more hits than you have chapters, either do chapter at a time, a replace one at a time or try inserting <h3 title="Chapter 1"></h3> at the beginning of each chapter. If you use the search and replace method Sigil will put the closing </hx> in for you when you go from CV to BV (code view to book view).
As to creating a table of contents page; you can do it manually or you can cheat. I choose to cheat. I run the epub (with the toc.ncx intact) into Calibre, do a epub to mobi convert and then mobi back to ebup. When you get finished your epub will have both the toc.ncx and the famous Blue TOC.
I suppose you could stop there but I chose to create an additional xhtml file and do a cut and paste of the blue toc data and clean it up. I've attached a zip file with four files Play1.epub, Play2.epub & .mobi and Play3.epub. I started with Play1 and ended with Play3.
I do have another suggestion; try to buy or borrow a Nook and a Kindle so you can see the results of your work. It does NOT look the same as it does on a computer screen. The printed page and PDF files are fixed in space ebups and mobis are not. I think that the reason so many ebooks are so poorly formated is that the print file output is converted to ebook format and then not proofed. And then too, most formatting is ignored by ereaders. Something like expecting a spell checker to catch syntax errors (their/there).
Anyway, good luck.
Regards -John