Thread: HTML Table of Contents
View Single Post
Old 01-20-2016, 10:55 AM   #17
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
Quote:
Originally Posted by Toxaris View Post
The DX is no ePUB reader, so why should it use the ncx? I know ePUB3 does not use the ncx anymore, and I feel it is a bad change...

I know some like the HTML TOC, I just don't. I do get annoyed by them, but not enough to remove it from the book first or not to read the book at all. Bad formatting will do that, but not the precense of a HTML TOC.
It is not DX that used NCX but the Amazon converter that will use it to create a Mobi TOC. ePub 3, I believe, is breaking its connection with DAISY by replacing the NCX with a more HTML like syntax. If you hand code your ePub, then ePub 3 is easier to create and it is still used outside the document like the older NCX was. To the eBook Reader they can look the same. There is no requirement in ePub 3 to have an inline TOC.

The presence of an HTML TOC is not the correct term for ePub 3 since both are using HTML syntax although the semantics tags are new to HTML5. Note that similar semantics can be used to create a page list as well.

Dale
DaleDe is offline   Reply With Quote