Quote:
Originally Posted by JSWolf
But you do get a ToC. It's just not at the front. It's at the back. And it is linked via the Table fo Contents link. So really, an internal ToC is useless and a waste of space. I really dislike when the chapter titles are linked to the ToC.
As far as I am concerned, let Amazon fix their conversion software to deal with toc.ncx hoever they want so we don't have to infest the ePub with an internal ToC.
|
@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