[slowsmile]

DiapDealer said:
You DO know that you can create and edit the ncx (or nav in an EPUB3) using Sigil's TOC editor, right? The proper header structure is only necessary if you want to generate the NCX (or nav) automatically. But just like calibre, there's a ToC editor you can use in Sigil.

You can certainly create the doc TOC and a Logical TOC(Device toc) using Sigil -- you can even create a multi-level doc TOC. You can also do the same in Calibre -- except you do not have to mark your headers with a heading style first -- in Calibre you just choose a page for each TOC header.

DiapDealer said:
You DO know that you can create and edit the ncx (or nav in an EPUB3) using Sigil's TOC editor, right? The proper header structure is only necessary if you want to generate the NCX (or nav) automatically. But just like calibre, there's a ToC editor you can use in Sigil.

The majority of ebooks out there are epub 2. And would you really expect an indie author to know how to manually and safely format his toc.nx or content.opf? That's a wide assumption and a bad road for any indie author to take (I'm not talking about developers here). And if you manually edit the xml within say the toc.ncx then Sigil does not automatically update the content.opf sections for epub 2 ebooks. If you use Calibre and if you do manually change the formatting in the toc.ncx or the content.opf then it automatically gets updated everywhere in the epub whenever you click Calibre editor's OK button. I love Sigil dearly, but for both TOC creation and XML editing, I prefer the Calibre way because its easier and faster. My hat off to Kovid Goyal for developing such a useful editor.