Thanks for explanation. It seems that Moon+ Reader didn't fully EPUB3 standard-compliant and will always use .ncx if exist. I've forward this message to the author.
But if the presence of .ncx is for backward compatibility, Sigil should sync it with nav automatically if both files are existed, isn't it?
Quote:
Originally Posted by DiapDealer
Yes. That's exactly what it means.
Technically you could, but the existence of a toc.ncx is still tightly entwined with Sigil's internals, so Sigil includes one (though it's empty unless you generate/edit the contents). And any epub2 rendering system that attempts to open your epub3 will use the ncx if present.
You can leave it: and Epub3 readers will ignore it. Or if you want to remove it, I've written an output plugin that will save the epub3 without the toc.ncx.
The best practice in my opinion is to wait until editing is complete, and then run "Generate NCX from Nav" if you're making an epub3 that will be readable in epub2 reading systems. Otherwise, ignore the ncx completely. |