View Single Post
Old 02-05-2013, 08:08 PM   #7
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: 73,970
Karma: 128903378
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 twedigteam View Post
Hmm, good suggestion, thought that might work but it produces: 'element "navPoint" not allowed yet; missing required element "content"' as an error.

Oh well, I suppose these types of issues will probably be rendered moot on moving to EPUB3 and the nav document.
I've figured out the solution. For the entry that you want as a header for the top level, put in the same file to go to as the first entry in the next level. That way if anyone does use it to go to a ToC entry, it will go to the first one in level 2. So using your example...

Example:
List Title [links to same page as item 1]
List Item 1 [links to page]
List Item 2 [links to page]
List Item 3 [links to page]
JSWolf is offline   Reply With Quote