This is the response the a query about the generation of a mobi toc from an epub from Sigil
Quote:
As far as I know, Kindlegen won't create an HTML table of contents if one doesn't already exist. I haven't seen it do that in practice, and know of no way to make it do that. It uses the NCX file to create a "logical" table of contents that the Kindle device can use to enable section navigation, but that's not the same as an HTML toc which forms part of the book, and which the user can view and access directly, using the "Go To... Table of Contents" Kindle (or other e-reader) menu command.
If the book doesn't already contain an HTML table of contents, you should consider creating one if it's appropriate - a straightforward novel, for example, with 45 chapters called simply "Chapter One", "Chapter Two", etc, would result in a rather tedious and essentially meaningless HTML Table of Contents, although having the NCX navigation file would still be a good idea. You would then need to amend the NCX file to include a navigation point for the HTML Table of Contents, and amend the OPF file as follows:
1. Add an item to the manifest section if the HTML ToC is in a separate HTML file.
2. Add an item to the spine section to reference the HTML ToC in the reading order.
3. Add a type="toc" reference item to the guide section to point to the HTML ToC.
- Donna
|