MobileRead Forums - View Single Post - Why include only an NCX table of contents?

Turtle91 · 09-06-2021, 09:02 AM

If your reader/app supports ncx ToC then an html ToC is kinda redundant...unless you need some special formatting/decoration of the ToC that is not possible in the ncx, or, some publishing services require the HTML version.

So, if you are making books for sale then it doesn't hurt to do both. If the book is just for you, doesn't need special formatting, or doesn't require an html ToC, then it's just an extra, unnecessary sheet.

edit:
The ncx/dropdown ToC, when used correctly (h1-h6 tags indicating book structure), is better for longer ToCs because they can expand/collapse.

09-06-2021, 09:02 AM	#2
Turtle91 A Hairy Wizard Posts: 3,355 Karma: 20171571 Join Date: Dec 2012 Location: Charleston, SC today Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire	If your reader/app supports ncx ToC then an html ToC is kinda redundant...unless you need some special formatting/decoration of the ToC that is not possible in the ncx, or, some publishing services require the HTML version. So, if you are making books for sale then it doesn't hurt to do both. If the book is just for you, doesn't need special formatting, or doesn't require an html ToC, then it's just an extra, unnecessary sheet. edit: The ncx/dropdown ToC, when used correctly (h1-h6 tags indicating book structure), is better for longer ToCs because they can expand/collapse. Last edited by Turtle91; 09-06-2021 at 09:06 AM.