View Single Post
Old 07-08-2020, 08:24 PM   #6
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,575
Karma: 172313954
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by hobnail View Post
I did some experiments and it looks like it's because I have it set for epub 3 in the output options. For no particular reason, except for consistency I suppose, since I always use epub3 when starting something in sigil.

It's unfortunate that calibre doesn't also produce the toc.ncx file when the output is set to epub 3. In sigil I always generate one just before the final epubcheck.
For me as well, generating the toc.ncx from the navigation document is one of the last things I do when editing an epub3 with Sigil.

We do have to remember that for an epub3, the toc.ncx is allowed for compatibility with older reader code and is not required.
DNSB is offline   Reply With Quote