Quote:
Originally Posted by ProDigit
I was thinking about using a toc like this.
However if I create a toc, based on HTML code (just display it as a page at the beginning like a chapter), I could save a lot of code!
HTML toc's only take up 2 lines per hyperlink, in this toc.ncx file, a hyperlink takes up 3 lines.
I find no reason why I should define an HTML, and then link to the definition, instead of just link to the html file?
|
There is a reason. While I disagree that an inline TOC is not useful, the TOC.NCX file is a must IMHO. I often include both particularly if the inline TOC adds value such as providing additional text that was in the original paper text version or provides an overview that cannot be readily seen in the separate file.
Saving a few bytes is a poor reason to leave out the toc.ncx file. An ePub features it to be able to bring up the TOC at any time while reading a document. This provides for a ready ability to be able to traverse the document as needed by the reader. This is the dominant reason for adding it. It is not, as you presume just a link to the definition. It is the only method defined by the standard for traversing the document by chapters. I believe a file is required even it it has only a single entry.
Dale