Nested NCX and the Kindle(s)

santosha · 07-05-2013, 02:21 AM

My book contains both parts and chapters (2 levels deep) and when automatically generating an NCX file with Sigil, this gets reflected in a 2-level NCX file with NavPoints nested within NavPoints.

Now, I've read various sources online that indicate that Kindles do not support nested NavPoints in NCX files and am a bit confused as to what exactly "not supported" means, if these sources are correct. (Can't find anything in the official Amazon guidelines about it)

When playing around in the Kindle Previewer with my test-file (with nested NCX, two levels deep) the NCX file shows up in the NCX previewer as nested and working fine (to expand with the plus sign and see all points). Further, when previewing the file on my physical Kindle PW the nested NCX seems to be working fine, with two levels under the "Go To"-button, showing the parts and the chapters contained within them. The "Reading time left in chapter" on the PW also seems to be correctly reading all the points.

The only time it seems to me that the nested NCX is not playing nice is that the chapter markers on the progress bar of the regular Kindle and DX in KP only show markers for the Parts, not the chapters--so I'm guessing this is what the talk about "not supported" is about?

Would you recommend I simply "flatten" the NCX generated by Sigil (which is kind of nice--I like the nested "Go To" menu on the PW) to maximize compatibility and as a best practice? Any other advice in this matter? What is stylistically recommended?

Many thanks in advance!

Santosha

DaleDe · 07-05-2013, 05:21 PM

Personally the nested TOC is more important than the progress bars. I think top level only progress bars is fine. I would suggest you leave it like it is.

Dale

santosha · 07-05-2013, 05:57 PM

Quote:

Originally Posted by DaleDe

Personally the nested TOC is more important than the progress bars. I think top level only progress bars is fine. I would suggest you leave it like it is.

Dale

Thanks for your input. Yes I agree--it seems like a fair trade-off to lose the chapter progress markers in order to have a much more manageable ToC, if that is indeed the only trade-off :-)

codys · 10-16-2018, 11:51 AM

I'm trying to figure out how to get my TOC which has 2 levels of menu (chapters and sections) that works fine in the Epub format to work on the Kindle format.

How do I create a nested / multi-level TOC menu?

Originally I converted the epub to azw3 in Calibre, and later I tried working directly in Kindle Create, but I still can't figure it out.

I've searched but couldn't find an answer - but a link that explains it would be just as helpful.

Thanks!

EDIT: OK, I thought I was created new post. I'll leave this here, and create a new one.

07-05-2013, 02:21 AM	#1
santosha Novice Posts: 14 Karma: 10 Join Date: Jun 2013 Device: Kindle Paperwhite	Nested NCX and the Kindle(s) My book contains both parts and chapters (2 levels deep) and when automatically generating an NCX file with Sigil, this gets reflected in a 2-level NCX file with NavPoints nested within NavPoints. Now, I've read various sources online that indicate that Kindles do not support nested NavPoints in NCX files and am a bit confused as to what exactly "not supported" means, if these sources are correct. (Can't find anything in the official Amazon guidelines about it) When playing around in the Kindle Previewer with my test-file (with nested NCX, two levels deep) the NCX file shows up in the NCX previewer as nested and working fine (to expand with the plus sign and see all points). Further, when previewing the file on my physical Kindle PW the nested NCX seems to be working fine, with two levels under the "Go To"-button, showing the parts and the chapters contained within them. The "Reading time left in chapter" on the PW also seems to be correctly reading all the points. The only time it seems to me that the nested NCX is not playing nice is that the chapter markers on the progress bar of the regular Kindle and DX in KP only show markers for the Parts, not the chapters--so I'm guessing this is what the talk about "not supported" is about? Would you recommend I simply "flatten" the NCX generated by Sigil (which is kind of nice--I like the nested "Go To" menu on the PW) to maximize compatibility and as a best practice? Any other advice in this matter? What is stylistically recommended? Many thanks in advance! Santosha Last edited by santosha; 07-05-2013 at 02:31 AM. Reason: Added question.

10-16-2018, 11:51 AM	#4
codys Junior Member Posts: 6 Karma: 10 Join Date: Oct 2018 Device: Kindle Paperwhite	Kindle - Nested/Multi Level TOC Menu I'm trying to figure out how to get my TOC which has 2 levels of menu (chapters and sections) that works fine in the Epub format to work on the Kindle format. How do I create a nested / multi-level TOC menu? Originally I converted the epub to azw3 in Calibre, and later I tried working directly in Kindle Create, but I still can't figure it out. I've searched but couldn't find an answer - but a link that explains it would be just as helpful. Thanks! EDIT: OK, I thought I was created new post. I'll leave this here, and create a new one. Last edited by codys; 10-16-2018 at 11:52 AM. Reason: oopsie

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
how to generate nested toc.ncx with more than 6 levels?	Tom Wiser	Sigil	20	08-21-2017 05:28 PM
Kindle Family ncx Treatment	KevCal	Amazon Kindle	3	10-17-2012 02:36 PM
Help with NCX file on kindle	Koko	Amazon Kindle	3	04-15-2012 06:04 PM
Does Apple iBooks support nested TOC.ncx?	st_albert	ePub	5	08-24-2011 02:21 PM
NCX creation -- nested or not, css classes	illustrata	ePub	3	08-25-2010 08:56 AM

07-05-2013, 05:21 PM	#2
DaleDe Grand Sorcerer Posts: 11,470 Karma: 13095790 Join Date: Aug 2007 Location: Grass Valley, CA Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7	Personally the nested TOC is more important than the progress bars. I think top level only progress bars is fine. I would suggest you leave it like it is. Dale

Advert