Thread: Multiple Table of Contents
View Single Post
Old 08-29-2019, 03:30 PM   #11
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: 79,935
Karma: 146918083
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 DiapDealer View Post
An html toc doesn't have to be defined as a NAV document to be a ToC that a user can use to navigate the epub in question. There are tons of commercial EPUB3 books out there that use the NAV document as a sort of "mini-toc"--complete with a landmark that is a link to a more complex (and navigable) table of contents. Much like KevinH mentioned, each of your landmarks in the NAV could be a link to a more useful html toc. Those additional html tocs just can't be created as NAV documents.
You are forgetting the NCX ToC.
JSWolf is offline   Reply With Quote