Quote:
Originally Posted by Jellby
Yes, the question is what does "support" mean exactly. I'm afraid someone could claim that it does not necessarily mean "give the user a convenient interface to view and navigate the TOC".
Anyway, just above that it says:
"It is important to emphasize that these navigation features are intended as a convenience for users who want them, and not a burden to those who do not. The alternative guide to the book may be provided for those users not requiring the navigation features of the NCX."
It also assumes the NCX to be present in addition to an inline TOC. Another advantage of an inline TOC is the possibility of controlling the style and appearance, which one can't quite do with NCX.
Note that, IIRC, the "name" attribute is deprecated, use "id" instead for ePUB (and it does not have to be in an <a> element, you can have <h1 id="01">). |
If you want that inline TOC, there's a perfectly good way to use it. As Valloric says, Sigil is breaking them, but you can still edit the epub more directly. You can open the epub with a Zip app (I use 7zip) open the contents and edit the TOC (I do that with Notetab) Take care to use absoloue adresses instead of anchors (say you have an "#chap1" anchor - that will be say split1.xhtml#chap1). Save.Voilą! Working inline TOC. No big deal, honestly. If you split up your file chapterwise, you do not even need an anchor, just link chapter 1 to split01.html (or whatever 's the name in Sigil, I haven't opened the belly of the monster yet) But Valloric is right, inline TOCs are really not necessary!