Creating Hanging TOC for Kindle Menu

[pypo]

Has anyone been successful at creating a TOC for the Kindle MENU that includes hanging indents like this?

1.0 Hello World

1.1 How to do it

1.2 Why not go ahead

2.0 Things That Work

2.1 Making promises

2.2 What is next

2.2.1 Taking action

2.2.2 Seen it all before

2.3 Testing your choices

3.0 Things That Don't Work

3.1 Avoiding bad advice

3.2 Rabbit holes

3.3 How to email a CEO

4.0 Conclusions

[DiapDealer]

I don't see any hanging indents anywhere there. I see an outline (which you should be able to easily achieve with css/style margins, blockquotes, or html lists). If you're talking about an html (inline) toc.

If you're talking about the ncx-based "goto" menu-based toc, you don't really have any control over how those are displayed (other than defining collapsible sections) how the ncx is presented is basically a function of the reading application.

[pypo]

Have another look at the forum post. It didn't format correctly the first try. Now the indents show.

Like I said, I'm not trying to do anything but put the TOC in the Kindle MENU using hanging indents. I know it is possible, because the user manual for Kindle Paperwhite has hanging indents in the Menu TOC. The Menu TOC is not in the body of the document. I don't want a TOC in the body of the document. I just want a TOC in the Kindle MENU and I want that TOC to be consecutively numbered and indented as shown in the example posted here. Maybe I need certain CSS for H1 H2 and H3. Maybe I need some setting for generating the TOC. Maybe something else, I don't know.

If there is a nice way to do all this with Calibre it would be great to hear from someone who has done this before.

[DiapDealer]

Maybe with epub3's nav document?

Spoiler:

Those still aren't hanging indents, btw.

[pypo]

Thanks for the pointer.

http://www.idpf.org/accessibility/gu...nt/nav/toc.php

I'll read up on this.

[theducks]

Looks like a standard 'Table' list item or
What you get using Hierarchical header levels with the TOC generator

<h1

<h2

<h2

<h3

[pypo]

So if I understand correctly, you are saying that if I use h1, h2, h3 css chapter/section tags, that:

1) Calibre TOC generator will allow me (somehow) to generate the indent codes for a proper toc.ncx and

2) those will show up in the flick menu on Kindle devices.

I can try this of course, but I just wonder if I got your point.

[DiapDealer]

Keep in mind that what you want may not even be possible using a calibre-built kindlebook (AZW3/KF8). If it's at all dependent on epub3 features, there's a good chance that building the kindlebook with kindlegen may be a requirement.

I don't have a Paperwhite, so I've no idea how they present the toc/nav info.

[eschwartz]

The issue here I believe is a question of hierarchy, not really indents. (For the Kindle's Go To menu)

Hierarchical ToCs will be created with calibre's ToC generator, if using the appropriate header tags. Or manually editing the ToC of course.

If the EPUB has a hierarchical ToC, either kindlegen or calibre-convert will preserve it into AZW3, and the Go To menu on the Kindle will have a hierarchical ToC. After that it is up to the Kindle to interpret.

You will see exactly what you see with the User Guide from Amazon.

(NOTE: I believe I heard somewhere that a Kindle bug breaks collapsible/hierarchical ToC if the first element has children.)

[kovidgoyal]

IIRC the PW firmware is capable of displaying the inline ToC as HTML in a popup. This is different from the normal NCX view and allows the popup toc to have custom formatting. I have no idea how it is implemented though.

[eschwartz]

Originally Posted by kovidgoyal

IIRC the PW firmware is capable of displaying the inline ToC as HTML in a popup. This is different from the normal NCX view and allows the popup toc to have custom formatting. I have no idea how it is implemented though.

by making the kindle think it is a footnote.

Does it render links inside footnotes???

[DiapDealer]

I'm back to betting on the ePub3 navigation document.

[kovidgoyal]

If you look at the markup in the Kindle user guide it is HTML 4 created from adobe framemaker, and the opf was generated from some kind of boilerplate template. I highly doubt it came from an epub 3 document.

[DiapDealer]

Ah well. I wonder if it's something that gets "turned on" in the Kindlebook for publishers with contracts and the like? I really need to get a Paperwhite some day; if only to check out these special footnote and pop-up inline toc features (although I think it's been determined that the pop-up footnotes are basically a heuristic function of the reading software).

[kovidgoyal]

pop-up footnotes are a heuristic. I have no idea about the popup inline toc though, as the only book I have ever seen it in is the kindle user guide.