TOC nesting not working correct (Apple Books)

Martin Leclercq · 05-12-2023, 05:58 AM

Hello Forum!

I've designed a ePub with a nested TOC. The problem I run into is that Apple Books is showing the levels incorrectly in the TOC. This is only happening with Apple Books. Other platforms seem OK as far as I can see.

The problem occurs when jumping 1 level back from a nested level. The program immediately jumps back to the beginning (main level) and not 1 level back. Thus showing the Paragraph heading in Bold. Thinking it's a chapter and not a Paragraph.

Some images to explain (sorry, it's in Dutch language):

TOC as shown in the print version:
pagina in boek.png (294.2 KB)

TOC as shown in ePub Apple Books:
png.gif inhoudsopgave via menu.png (218.9 KB)

Here is an image of the toc.xhtml code:
png.gif Screenshot 2023-05-12 at 10.45.22.png (342.6 KB)

Hope somebody knows what I'm doing wrong.

With regards,
Martin

Jellby · 05-12-2023, 01:16 PM

I'd recommend not using lists, but simple nested <div>s, or level-specific classes.

DNSB · 05-12-2023, 02:51 PM

If he's using epub3, the nav.xhtml file uses lists.

Martin Leclercq · 05-13-2023, 04:56 AM

I am using ePub 3.

KevinH · 05-13-2023, 10:39 AM

Edit: Skip this response, see my later responses below:

Open the epub in Sigil or Calibre's editor. Then navigate to the actual nav xhtml file. Does it exhibit the same issue? If not, then perhaps Books is finding an older incorrect toc.ncx (NCX) and displaying that instead of the NAV. In addition, the book may have an html toc xhtml file that was meant to be read by the user just like book content that is separate from the NAV and/or NCX that might be the issue. If so try loading that file in Sigil or Calibre's editor to verify it is correct.

If all possible sources for the info shown in the reader's TOC window are correct, then you know the bug is in the reader's code that parses the NAV or NCX.

KevinH · 05-13-2023, 11:31 AM

Did a quick web search and found this bug report from 2016.

https://discussions.apple.com/thread/7419388

It had no answer. It appears to be exactly the same bug you are asking about. So my guess is this is a very long standing bug in how Books builds its toc from the NAV that Apple has no interest in fixing.

You might try simplifying it to be a 2-level level or just a 1-level NAV, then create a non-NAV xhtml table of contents to show the user that is more complete.

KevinH · 05-13-2023, 11:37 AM

FWIW, I personally never use Apple Books.app as it is non-standard (does not meet the epub3 spec) and has bugs. On Apple Desktops I use many different e-readers including the latest Thorium Reader, the Kobo Desktop reader, and ADE 4.x. Calibre's reader is quite good also.

On iOS devices, I strongly recommend the Bluefire Reader as the most compliant e-reader available with the Kobo Reader next.

Hope something here helps.

Martin Leclercq · 05-17-2023, 08:21 AM

Hello KevinH,

Thanks for the tips! That old bug is exactly what I'm running into. Thanks for sharing.
I'll try the other readers and see if the TOC works correct. I also try to simplify the TOC.

lcocea · 08-13-2025, 05:57 PM

The bug limiting the indentation of the TOC to two levels in Apple Books remains unfixed. Interestingly, Apple Books can correctly display TOCs deeper than two levels. If you create a test document in Pages with a three-level table of contents and export it to EPUB, you'll initially only see two levels due to wrong indentation of the 3rd level. But if you edit the TOC in Sigil or Calibre to indent the third level, Apple Books will display it correctly.

05-12-2023, 05:58 AM	#1
Martin Leclercq Junior Member Posts: 3 Karma: 10 Join Date: May 2023 Device: Apple Books	TOC nesting not working correct (Apple Books) Hello Forum! I've designed a ePub with a nested TOC. The problem I run into is that Apple Books is showing the levels incorrectly in the TOC. This is only happening with Apple Books. Other platforms seem OK as far as I can see. The problem occurs when jumping 1 level back from a nested level. The program immediately jumps back to the beginning (main level) and not 1 level back. Thus showing the Paragraph heading in Bold. Thinking it's a chapter and not a Paragraph. Some images to explain (sorry, it's in Dutch language): TOC as shown in the print version: pagina in boek.png (294.2 KB) TOC as shown in ePub Apple Books: png.gif inhoudsopgave via menu.png (218.9 KB) Here is an image of the toc.xhtml code: png.gif Screenshot 2023-05-12 at 10.45.22.png (342.6 KB) Hope somebody knows what I'm doing wrong. With regards, Martin Attached Thumbnails

05-13-2023, 10:39 AM	#5
KevinH Sigil Developer Posts: 9,072 Karma: 6361556 Join Date: Nov 2009 Device: many	Edit: Skip this response, see my later responses below: Open the epub in Sigil or Calibre's editor. Then navigate to the actual nav xhtml file. Does it exhibit the same issue? If not, then perhaps Books is finding an older incorrect toc.ncx (NCX) and displaying that instead of the NAV. In addition, the book may have an html toc xhtml file that was meant to be read by the user just like book content that is separate from the NAV and/or NCX that might be the issue. If so try loading that file in Sigil or Calibre's editor to verify it is correct. If all possible sources for the info shown in the reader's TOC window are correct, then you know the bug is in the reader's code that parses the NAV or NCX. Last edited by KevinH; 05-13-2023 at 01:24 PM.

05-13-2023, 11:31 AM	#6
KevinH Sigil Developer Posts: 9,072 Karma: 6361556 Join Date: Nov 2009 Device: many	Did a quick web search and found this bug report from 2016. https://discussions.apple.com/thread/7419388 It had no answer. It appears to be exactly the same bug you are asking about. So my guess is this is a very long standing bug in how Books builds its toc from the NAV that Apple has no interest in fixing. You might try simplifying it to be a 2-level level or just a 1-level NAV, then create a non-NAV xhtml table of contents to show the user that is more complete. Last edited by KevinH; 05-13-2023 at 11:50 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Epub -> AZW3 conversion. Kindle displays incorrect chapter, but TOC is correct	greenskye	Conversion	9	07-28-2022 06:32 PM
TOC not working on AZW3 books?	cager	Editor	2	07-24-2014 12:22 PM
Adding working TOC onto free Mobipocket books in Calibre	crich70	Calibre	0	05-16-2012 02:09 AM
Making a TOC for LRFs? Issues with Calibre + LRF TOC editor not working	Magitek	LRF	0	05-06-2009 02:25 PM
Books not in correct category	bbrotherton	Sony Reader	0	11-25-2008 07:43 PM

05-12-2023, 01:16 PM	#2
Jellby frumious Bandersnatch Posts: 7,570 Karma: 20150435 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	I'd recommend not using lists, but simple nested <div>s, or level-specific classes.

05-12-2023, 02:51 PM	#3
DNSB Bibliophagist Posts: 48,175 Karma: 174315444 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	If he's using epub3, the nav.xhtml file uses lists.

05-13-2023, 04:56 AM	#4
Martin Leclercq Junior Member Posts: 3 Karma: 10 Join Date: May 2023 Device: Apple Books	I am using ePub 3.

05-13-2023, 11:37 AM	#7
KevinH Sigil Developer Posts: 9,072 Karma: 6361556 Join Date: Nov 2009 Device: many	FWIW, I personally never use Apple Books.app as it is non-standard (does not meet the epub3 spec) and has bugs. On Apple Desktops I use many different e-readers including the latest Thorium Reader, the Kobo Desktop reader, and ADE 4.x. Calibre's reader is quite good also. On iOS devices, I strongly recommend the Bluefire Reader as the most compliant e-reader available with the Kobo Reader next. Hope something here helps.

05-17-2023, 08:21 AM	#8
Martin Leclercq Junior Member Posts: 3 Karma: 10 Join Date: May 2023 Device: Apple Books	Hello KevinH, Thanks for the tips! That old bug is exactly what I'm running into. Thanks for sharing. I'll try the other readers and see if the TOC works correct. I also try to simplify the TOC.

08-13-2025, 05:57 PM	#9
lcocea Junior Member Posts: 8 Karma: 10 Join Date: Jun 2025 Device: Apple Books, Thorium Reader	The bug limiting the indentation of the TOC to two levels in Apple Books remains unfixed. Interestingly, Apple Books can correctly display TOCs deeper than two levels. If you create a test document in Pages with a three-level table of contents and export it to EPUB, you'll initially only see two levels due to wrong indentation of the 3rd level. But if you edit the TOC in Sigil or Calibre to indent the third level, Apple Books will display it correctly.

Advert

Advert