Quote:
Originally Posted by slightfever
When nav.xhtml is used as a table of contents page, it cannot be decorated.
|
Of course, you cannot link to nav.xhml in a toc landmark entry, if it's not in the spine. However, if it
is in the spine,
you can link to it. As for
linear=no I don't know of a single epub2 app that actually honors it, which is not at all surprising, because the
epub2 specs don't strictly require apps to hide spine items with a
linear=no attribute.
If you're interested in creating epub2-compatible epubs for Amazon KDP, you can take advantage of this fact and move the nav document after the cover and add a
linear=no attribute and
toc landmark/guide items. Since all major epub3 apps honor
linear=no, the nav document will only be shown as an HTML TOC in epub2 books.
Quote:
Originally Posted by slightfever
So it is recommended to create another document table of contents and hide nav.xhtml.
|
I disagree. IMHO, an additional HTML TOC with the same TOC links as the NAV document would be redundant.