View Single Post
Old 04-12-2012, 10:17 PM   #35
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,087
Karma: 148029447
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by ProDigit View Post
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?
It's not 2 lines vs 3 lines that should be the deciding factor. In all readers that use ADE, there is a very easy way to get to the ToC that uses toc.ncx. There is no easy way to get to an ToC that's just an XML file made up of links. It's akin to using the ToC link in a properly made Mobi file.

The way to get to the ToC in an ePub uses toc.ncx.
JSWolf is offline   Reply With Quote