View Single Post
Old 10-01-2016, 07:56 PM   #14
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,736
Karma: 206739468
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by slowsmile View Post
@Kevin...It's certainly true enough what you say if you are talking about Sigil only -- because the only way that you can insert and TOC and create the relevant and associated XML structure in Sigil is by formatting and marking all TOC headers with h1, h2, h3 etc. But this is not the only way to create a TOC and xml structure in an epub.
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 Sigil ToC editor may not bring up a file dialog to allow you to directly choose which html file you want the chapter entry to link to (like calibre's), but you can still create/delete/edit/nest ToC entries and point them to any page (or any page element's id/anchor) you like. No one HAS to use semantically correct headers to build the ToC (though they really should).

It seems as though you believe h tags are the only way a working ToC can be created using Sigil's tools.
DiapDealer is offline   Reply With Quote