Issues with TOC of mobi file after sending it to kindle

[kindlehater]

I have a mobi file with 2 level - table of contents when it is opened by Calibre as the image below.


Then, I send this file to my kindle by sendtokindle app on my pc.
After that, the TOC is messed up as the image below. All links are jammed into "Front Matter".


Anyone knows why and how to fix it?
Thanks!

[hobnail]

The MOBI format is only necessary for very old Kindle devices. If your kindle isn't ancient try using Calibre and convert the MOBI to AZW3 and see how that comes out. You can use Calibre to send the book to your Kindle if it's connected to your computer with a USB cable. On the Kindle delete the MOBI format of the book before you send the AZW3 format to avoid confusion of having the book in multiple formats. You can also do that deleting with Calibre.

[Hitch]

Originally Posted by hobnail

The MOBI format is only necessary for very old Kindle devices. If your kindle isn't ancient try using Calibre and convert the MOBI to AZW3 and see how that comes out. You can use Calibre to send the book to your Kindle if it's connected to your computer with a USB cable. On the Kindle delete the MOBI format of the book before you send the AZW3 format to avoid confusion of having the book in multiple formats. You can also do that deleting with Calibre.

That's fine, for individual eBooks that will never be published at Amazon, but be advised that recently, we're getting books returned to us, with KQNs (Kindle Qualit5y Notices) REQUIRING that multi-level TOCs be altered to single-level only, to facilitate the customer view on K4PC.

Be aware!

Hitch

[hobnail]

Originally Posted by Hitch

That's fine, for individual eBooks that will never be published at Amazon, but be advised that recently, we're getting books returned to us, with KQNs (Kindle Qualit5y Notices) REQUIRING that multi-level TOCs be altered to single-level only, to facilitate the customer view on K4PC.

Be aware!

Hitch

Does that mean simply changing all of your h3 tags to h2? That would kind of suck if you prefer the visual clue of the h3 text being smaller than h2 text. Or is there a way to keep multi levels of h tags but meet their requirements? Besides something wonky like having different classes on the h2 tags that were previously h3 tags.

[Hitch]

Originally Posted by hobnail

Does that mean simply changing all of your h3 tags to h2? That would kind of suck if you prefer the visual clue of the h3 text being smaller than h2 text. Or is there a way to keep multi levels of h tags but meet their requirements? Besides something wonky like having different classes on the h2 tags that were previously h3 tags.

You're conflating the toc.html and the ncx. For the NCX, it basically means ALL h1 tags, which makes me about as happy as you can imagine (not).

IF you build your NCX using the toc.html, yes, that's what that means.

Don't use headings to size your text; headings are STRUCTURAL, not decorative. If you choose to use your heading CSS to make one larger than the next, that's your prerogative, but text sizing, font, font decoration or enhancement (like bold, italic) should be done in CSS.

Hitch

[hobnail]

Originally Posted by Hitch

You're conflating the toc.html and the ncx. For the NCX, it basically means ALL h1 tags, which makes me about as happy as you can imagine (not).

What I'm really conflating/thinking about is what I see when I click on the Generate Table of Contents button in Sigil. After I do that then I do the EPUB3 tools thing to generate the NCX.

Don't use headings to size your text; headings are STRUCTURAL, not decorative. If you choose to use your heading CSS to make one larger than the next, that's your prerogative, but text sizing, font, font decoration or enhancement (like bold, italic) should be done in CSS.

Agreed.

[kindlehater]

Originally Posted by Hitch

That's fine, for individual eBooks that will never be published at Amazon, but be advised that recently, we're getting books returned to us, with KQNs (Kindle Qualit5y Notices) REQUIRING that multi-level TOCs be altered to single-level only, to facilitate the customer view on K4PC.

Be aware!

Hitch

So, no more multi-level books, is that right? It really irritates me.
Do you know why single level TOC would facilitate the customer view on K4PC?

[kindlehater]

I tried send another mobi file with multi-level TOC to my kindle by sendtokindle. My kindle does show this file's multi-level TOC.

So, what causing the conflated TOC is in the mobi file.

[Hitch]

Originally Posted by kindlehater

I tried send another mobi file with multi-level TOC to my kindle by sendtokindle. My kindle does show this file's multi-level TOC.

So, what causing the conflated TOC is in the mobi file.

Do you know WHICH TOC you are seeing? The NCX or the toc.html? I daresay you don't.

Hitch

[kindlehater]

I'm talking about the TOC in the image below. I think it is NCX TOC, right?

[Hitch]

Originally Posted by kindlehater

I'm talking about the TOC in the image below. I think it is NCX TOC, right?

I have no way of answering that. You need to tell us. Put something in the NCX that doesn't match what's in the toc.html, like changing Matthew to Matthew1 and then when you use the GoTo, you'll know.

I agree, it should be the NCX--but there's only one way to be sure. Bear in mind--even if this works here and now, you're going to run into the same problem on K4PC/Mac.

Hitch