Quote:
Originally Posted by DMSmillie
Also, just a clarification - the "TOC" that others refer to Sigil creating is not an inline TOC as required in a MOBI file. What Sigil creates is a navigation control XML file (an NCX file) which most/all EPUB readers use to generate a TOC to present to the user. The Kindle device and apps use the NCX file (when one is incorporated into a MOBI file) to provide previous/next chapter navigation (on the Kindle, using the 5-way control button), and to show each navigation point as a small dot or tick mark on the progress bar. In most MOBI readers, and certainly true for the Kindle and Kindle apps, the only kind of TOC that will be presented to the user viewing a MOBI file is an inline TOC, coded as part of the HTML content of the book. That's the TOC referred to in Calibre's conversion dialog when MOBI is selected as the output format.
|
Very true. However, Calibre will take the Sigil TOC and create an inline TOC upon conversion from epub to mobi if a TOC file isn't assigned within the epub. If I have a simple, single level TOC, I typically will let Calibre create it for me when I convert. If you have multiple levels or special formatting desires though, it's best to create your own TOC file in Sigil, mark designate it as TOC and then convert.
- Byron