View Single Post
Old 03-09-2025, 01:43 PM   #11
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,884
Karma: 6120478
Join Date: Nov 2009
Device: many
The nav need not be called "nav.xhtml". The nav is an xhtml file, not an xml ncx file. One way to identify the epub3 nav document is to mouse over the xhtml files in BookBrowser and see which one has the "nav" property semantic set. Another way is to highlight the suspect file and then right click on it use Sigil's GetInfo menu from the popup. The nav file will have "nav" listed under its Manifest Properties.
KevinH is offline   Reply With Quote