epub to azw3 Table of Contents flattens-cross post from Calibre

[BKh]

I originally posted about this problem here...
https://www.mobileread.com/forums/sho...d.php?t=279874

Basically, the hard coded toc has its css removed when I convert to azw3 and there are no indents.

This was the advice Kovid gave...

Originally Posted by kovidgoyal

Your HTML ToC is not marked as a ToC in the OPF. You need to create a guide entry for it. And remove the two spurious Table of Contents entries in the ncx.

I'm hoping someone here can tell me what I did wrong when I created the epub in Sigil. I have never had to fiddle with things like this before.

I added semantics to the toc file as a table of contents.

I am using Sigil 0.9.4, Loaded Qt 5.4.2

All of the original and converted files are in the post I linked to above.

[DiapDealer]

Originally Posted by BKh

I added semantics to the toc file as a table of contents.

That's all you can do with Sigil to identify the html toc. I don't convert epubs to AZW3s with calibre, so I can't help in that regard. All I can do is help you make sure your epub meets epub specifications.

[DiapDealer]

Originally Posted by BKh

I added semantics to the toc file as a table of contents.

I checked out your epub from the original post and there is no semantic set for the html toc. The guide section of the OPF clearly shows no toc reference item.

<guide>
    <reference type="copyright-page" title="Copyright Page" href="Text/Rights.xhtml"/>
    <reference type="text" title="Text" href="Text/Title.xhtml"/>
    <reference type="cover" title="Cover" href="Text/Cover.xhtml"/>
</guide>

Try opening the epub in Sigil again and assigning the Table of Content semantic to the Section0001.html file.

Other than that, there's no Sigil related issue here.

[slowsmile]

@BKh...I think the easiest way for you to create a doc TOC and Nav TOC(device TOC) is to load your azw3 version into Calibre and then click on Edit Book. Then click on the Edit TOC button in the Calibre editor toolbar and this will bring up the TOC editor. The TOC editor is very easy to use.

Once you have finished creating your TOC in the TOC editor click OK and all the necessary changes will automatically be updated and saved in the the content.opf and toc.ncx. Then save your azw3 file to your desktop and you're done. Your azw3 file should now have a doc TOC and Nav TOC when you test it.

I must also add that it is not possible to display a multi-level Nav TOC(device TOC) across all Kindle devices. KF8 yes, mobi7 no. On a mobi7 device your multi-level Nav TOC will display as a flat TOC and there's no cure for this because it's the Kindle reader software(mobi7) that flattens the device TOC.