Quote:
Originally Posted by Hitch
@JSWolf: we may be speaking at cross-purposes. Having an ncx in an epub and dropping it on KindleGen doesn't create a user-visible toc, at the back or elsewhere. While the 5-way button may be able to make use of the ncx, to jump from chapter to chapter, the human reader can't "see" an NCX in a Kindle device through the simple expedient of running it through KG or Previewer (unless someone is running it through Calibre). Only a MBPC-created TOC (which is still an html.toc) shows up at the back in a quasi-automated fashion. That's the TOC that's linked via the TOC link--that IS an html.toc; the ncx is not directly linked to the TOC "button" or menu item, as bizarre as that all sounds. The TOC that is linked to the TOC menu button is an html-toc--NOT the toc.ncx, FWIW.
HTH,
Hitch
|
We should not have an internal ToC just to appease Amazon. They could design KindleGen to take toc.ncx and generate an internal ToC. No reason they cannot. And Calibre generates a linked ToC. Sure, it's at the back, but that's OK. An internal ToC (at the front) just makes us have to turn more pages to get past it.