05-24-2022, 06:08 AM | #1 |
Enthusiast
Posts: 31
Karma: 2578352
Join Date: May 2022
Device: tolino 2HD
|
Toc page does not appear in ebook
Hello,
I just created a little Test epub with Sigil but unfortunately the toc page does not appear in my e-reader (tolino). In the Sigil-GUI however the toc does appear with correct entries on the right side and executing the validity check no error appears. So what's wrong here? any help would be appreciated. thanx, Helmut |
05-24-2022, 08:16 AM | #2 |
Enthusiast
Posts: 31
Karma: 2578352
Join Date: May 2022
Device: tolino 2HD
|
Deleted. Solution found!
|
Advert | |
|
05-24-2022, 10:25 AM | #3 |
Grand Sorcerer
Posts: 27,553
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Care to share?
Was it an EPUB3 book that needed to have an NCX generated to be backward compatible with EPUB2 rendering engines? Or did you simply need to generate an HTML ToC (from the NCX) in an EPUB2? |
05-24-2022, 02:18 PM | #4 |
Junior Member
Posts: 2
Karma: 10
Join Date: Nov 2021
Device: none
|
This got me the on first epub I made.
Make sure that you check the spine section of the content.opf file. If it says the following: <spine> ... <itemref idref="nav.xhtml" linear="no"/> ... </spine> you need to delete the linear="no" to make the TOC visible. |
05-26-2022, 08:17 AM | #5 | |
Enthusiast
Posts: 31
Karma: 2578352
Join Date: May 2022
Device: tolino 2HD
|
Quote:
I thought the toc page would be created by default, without an explicite action. However I had to create it explicitely by the tool "Create HTML Table of Contents". nonetheless thanx for your answer. |
|
Advert | |
|
05-26-2022, 09:24 AM | #6 | |
Grand Sorcerer
Posts: 27,553
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
ToCs are tricky business. HTML tocs are not required by EPUB2 spec, that's why we don't automatically generate one and rely upon the required NCX instead. Similarly, the NCX is not mandatory in EPUB3 (but is recommended to be backward compatible with EPUB2 reading systems), so we don't automatically create it either (actually... we DO automatically create it whenever a button is pressed -- we just don't automagically update the non-mandatory NCX document whenever a change to the mandatory NAV document is made). Then there's the required NAV document in EPUB3 that the novice may think is just a terribly cheesy HTML ToC that needs to be tweaked (without realizing it's a required element that has a special syntax that needs to be followed). It CAN double as an HTML toc, but special care must be taken so as not to break something. Then there's the various rendering engines that pick and choose what they use for their built-in ToC navigation. So yes. The only navigation documents that Sigil automagically keeps up to date when changes are made is the mandatory navigation document for that particular EPUB version. The updating of non-mandatory navigation elements is left up to the discretion of the user (but we leave it only a menu item away). |
|
05-26-2022, 09:31 AM | #7 |
Sigil Developer
Posts: 7,654
Karma: 5433388
Join Date: Nov 2009
Device: many
|
Edit: DiapDealer beat me to it! Again!
.... Under epub3, rebuilding the TOC only impacts the NAV. The NAV is a pure html file that must always be machine readable and thus must follow a specific format. As explained earlier if you remove linear="no" in the spine on its NAV entry, it can serve double duty serving as a machine readable TOC (just like epub2's NCX) and a user friendly TOC. Or alternatively, as you found out, you can create a separate HTML TOC as was typically used under epub to further define or refine the NCX/NAV. Last edited by KevinH; 05-26-2022 at 09:34 AM. |
05-26-2022, 04:12 PM | #8 | |
Wizard
Posts: 1,104
Karma: 4911876
Join Date: Sep 2021
Location: Australia
Device: Kobo Libra 2
|
Quote:
I am looking at the last two books I converted to epub3 and the nav is not listed there. But I do have nav.xhtml with a generated toc. Spoiler:
|
|
05-26-2022, 04:57 PM | #9 |
Sigil Developer
Posts: 7,654
Karma: 5433388
Join Date: Nov 2009
Device: many
|
Technically it does not have to be part of the spine but when it is not listed in the spine, then further rules on the link used in the landmarks section of the nav apply.
See for example: https://github.com/w3c/epubcheck/issues/545 |
05-26-2022, 05:24 PM | #10 |
Wizard
Posts: 1,104
Karma: 4911876
Join Date: Sep 2021
Location: Australia
Device: Kobo Libra 2
|
Ok, thanks @KevinH
|
Tags |
toc |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
TOC Page Numbers? | 93terp | Kobo Reader | 56 | 06-20-2020 08:16 AM |
How to generate a TOC as a page in the eBook? | alegriadelarte | Editor | 11 | 05-23-2018 09:16 AM |
TOC with Page # | odedta | ePub | 34 | 12-30-2013 05:45 AM |
More than one page of TOC? | Steven630 | Recipes | 5 | 03-14-2013 11:01 AM |
Generated TOC links back to TOC page in the book | Caleb666 | Sigil | 7 | 08-17-2011 11:58 AM |