MobileRead Forums - View Single Post

KevinH · 03-05-2016, 02:23 PM

Your content.opf file is mixing epub2 style dc metadata with epub3 style dc metadata with refines. So unless there is a bug in epub3-itizer that no one else has hit (always a possibility) something has converted the epub3 dc creator, dc title and dc identifier schemes back to epub2. Sigil version 0.9.3 will not do this since it literally prevents the metadata editor from being invoked under epub3. But earlier versions of Sigil will if you invoke the Metadata Editor gui. What else touched the file after epub3-itizer output it? Was it a Sigil version earlier than Sigil-0.9.3?

If need be I can walk you through fixing the metadata for epub3 by hand, removing all of the calibre introduced pieces and properly creating epub3 metadata.

Just let me know.

KevinH

03-05-2016, 02:23 PM	#7
KevinH Sigil Developer Posts: 8,467 Karma: 5703586 Join Date: Nov 2009 Device: many	Your content.opf file is mixing epub2 style dc metadata with epub3 style dc metadata with refines. So unless there is a bug in epub3-itizer that no one else has hit (always a possibility) something has converted the epub3 dc creator, dc title and dc identifier schemes back to epub2. Sigil version 0.9.3 will not do this since it literally prevents the metadata editor from being invoked under epub3. But earlier versions of Sigil will if you invoke the Metadata Editor gui. What else touched the file after epub3-itizer output it? Was it a Sigil version earlier than Sigil-0.9.3? If need be I can walk you through fixing the metadata for epub3 by hand, removing all of the calibre introduced pieces and properly creating epub3 metadata. Just let me know. KevinH Last edited by KevinH; 03-05-2016 at 02:47 PM.