MobileRead Forums - View Single Post

KevinH · 03-06-2016, 02:36 PM

Hi,
Epub3 ebooks require a nav document by present in the ebook and require epub3 style metadata? So you simply can not just change the package version setting? Did you try convert your valid epub2 to epub3 using epub3-itizer? If not, how did you convert it to epub3? There are new epub3 tools (see the menu) to create a nav document from a valid NCX. There is also a tool to properly update the manifest properties to automatically add the "nav" property for the newly created nav document. Unfortunately, Sigil-0.9.3 does not have a metadata gui editor (the next version of Sigil will). So you will have to manually edit the metadata in the content.opf.

A much easier approach if you do not know how to edit epub3 metadata is to stick with epub2, make all of the changes you want, and then invoke the epub3-itizer plugin to convert it all to epub3 for you.

KevinH

03-06-2016, 02:36 PM	#2
KevinH Sigil Developer Posts: 8,491 Karma: 5703586 Join Date: Nov 2009 Device: many	Hi, Epub3 ebooks require a nav document by present in the ebook and require epub3 style metadata? So you simply can not just change the package version setting? Did you try convert your valid epub2 to epub3 using epub3-itizer? If not, how did you convert it to epub3? There are new epub3 tools (see the menu) to create a nav document from a valid NCX. There is also a tool to properly update the manifest properties to automatically add the "nav" property for the newly created nav document. Unfortunately, Sigil-0.9.3 does not have a metadata gui editor (the next version of Sigil will). So you will have to manually edit the metadata in the content.opf. A much easier approach if you do not know how to edit epub3 metadata is to stick with epub2, make all of the changes you want, and then invoke the epub3-itizer plugin to convert it all to epub3 for you. KevinH Last edited by KevinH; 03-06-2016 at 02:38 PM.