View Single Post
Old 02-10-2023, 05:47 AM   #11
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,289
Karma: 105299897
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
Quote:
Originally Posted by JSWolf View Post
You don't actually need an HTML TOC. You have the NCX file and if it's ePub3, you have the NAV and in most cases the NCX.
Agreed, but it's the toc.ncx the poster is commenting on.

You need the toc.ncx for epub2 ereader/app compatibility. That's why it's recreated. Answer "no".

OTOH there is the odd reader that doesn't display system contents using the toc.ncx. That's why some ebooks have an HTML contents page and link each chapter to it. Also an HTML contents page can have additional information and as many levels as you want, partway between and Index and Contents page. More than two on toc.ncx is inadvisable.
Oddly not all ereaders have search either, or only a convoluted method to input text if no touch or keyboard.

I had one totally dumb ereader that had no search and no ability to select links. I forget if it had the system contents using toc.ncx

Last edited by Quoth; 02-10-2023 at 05:51 AM.
Quoth is offline   Reply With Quote