Issue with Nested Divs in TOC on Kindle

[euriloco]

Hi,
Sigil automatically generates the TOC with Tools > Table of Contents > Generate HTML from TOC.
The problem is that it generates a TOC structure with nested divs.
I am working with an epub that has 3 levels (h1, h2, h3) in the index, which results in the TOC having 3 nested divs.
The problem I have is that Kindle only supports 2 nested divs. If I add a TOC with 3 nested divs, Kindle displays it as if they are all at the same level (h1).
Is there any way to automatically generate the TOC without nesting divs?
Thanks

[KevinH]

You can run Sigil's toc editor tool and promote, demote or delete (i.e. not include) whatever headers you want. There is also a filter for limiting to the highest level. FWIW, Technically you are ordering ol and li tags not div tags in the nav, I believe.

[democrite]

I also wish the XHTML TOC didn't use nested divs and perhaps instead CSS. Yet not sure if it's too late to change such. I generate one somewhat often as the H2 and H3 section titles can be good for navigating longer works, in place of the provided XHTML toc.

I use AppleScript with BBEdit to change such. There may be other ways.

[KevinH]

I believe thethe TOC the kindle processes is the ncx under epub2 and the nav.xhtml under epub3. Creating an html toc is not the same as either of those.

[BeckyEbook]

I know that Sigil is an editor for EPUB files, but when preparing files for kindle TOC in HTML files is important and Amazon pays attention if it is missing.

[democrite]

Originally Posted by KevinH

I believe thethe TOC the kindle processes is the ncx under epub2 and the nav.xhtml under epub3. Creating an html toc is not the same as either of those.

Yet that it seems that that was what the OP was referring to. Yet maybe such was mis-worded. Seems Kindle TOCs may only support 2 levels. Not sure if that is the issue or if also nested divs could be, yet that would be strange.