View Single Post
Old 07-03-2019, 02:46 PM   #204
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,961
Karma: 147448039
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 DNSB View Post
I may as well toss in that in an ePub3 document, the NCX ToC is only included for epub2 backwards compatibility and is not needed.

Neither format needs a HTML ToC. Epub2 uses the NCX ToC. Epub3 uses the NAV ToC. The HTML ToC is purely for humans and is not mandated for either epub2 or epub3.
What renderer actually uses the NAV ToC when there is also a NCX ToC?

I do know that you don't need the HTML ToC and I do delete it because it's code bloat with no value.
JSWolf is offline   Reply With Quote