Quote:
Originally Posted by Algiedi
Which was okay because I realized that making a TOC "by hand" (with anchors and links) is very satisfying... except I'm now facing a new problem, which is that Calibre duplicates the TOCs, even when ticking "don't add detected chapters" -.-
|
Are you also selecting "Do not add table of contents to book" in the "MOBI Output" section of the conversion dialog? The combination of those two settings should ensure that Calibre doesn't add a second inline TOC to the MOBI version.
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.