Quote:
Originally Posted by DiapDealer
Ah yes. That would be the nav document. It's required in an epub3. As such, it cannot be deleted (any more than the content.opf can be deleted). The nav document is identified by manifest properties in the opf. It could have any kind of name whatsoever in the Book Browser.
When using Sigil's ToC editing tools, it's the ncx being modified when in an epub2. But those same tools modify the nav document when editing an epub3.
|
ok - mark it down to my lack of epub3 knowledge then. I just assume that anything toc-looking near the top of the xhtml list is some inline version of the real toc so I habitually zap all such & tell sigil to generate a "proper" one if necessary
as for Js
converting TO epub3 is silly comment, one reason I have seen posted (maybe by you) is that it facilitates use of the Bookari epub3 reader