Quote:
Originally Posted by helmut25
I already found the solution.
I thought the toc page would be created by default, without an
explicite action.
However I had to create it explicitely by the tool "Create HTML Table of Contents".
nonetheless thanx for your answer.
|
So it was my second guess then.
ToCs are tricky business. HTML tocs are not required by EPUB2 spec, that's why we don't automatically generate one and rely upon the required NCX instead.
Similarly, the NCX is not mandatory in EPUB3 (but is recommended to be backward compatible with EPUB2 reading systems), so we don't automatically create it either (actually... we DO automatically create it whenever a button is pressed -- we just don't automagically
update the non-mandatory NCX document whenever a change to the mandatory NAV document is made).
Then there's the required NAV document in EPUB3 that the novice may think is just a terribly cheesy HTML ToC that needs to be tweaked (without realizing it's a required element that has a special syntax that needs to be followed). It CAN double as an HTML toc, but special care must be taken so as not to break something.
Then there's the various rendering engines that pick and choose what they use for their built-in ToC navigation.
So yes. The only navigation documents that Sigil automagically keeps up to date when changes are made is the mandatory navigation document for that particular EPUB version. The updating of non-mandatory navigation elements is left up to the discretion of the user (but we leave it only a menu item away).