MobileRead Forums - View Single Post

KevinH · 05-26-2022, 09:31 AM

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.

05-26-2022, 09:31 AM	#7
KevinH Sigil Developer Posts: 8,893 Karma: 6120478 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.