MobileRead Forums - View Single Post

DiapDealer · 03-06-2016, 02:47 PM

EDIT: KevinH posted in the time I took to compose mine. There may be some overlapping stuff.

It sounds as if something overwrote the metadata section of the opf file with EPUB2 metadata. Did you edit the EPUB3 with anything other than Sigil v0.9.3?

Points to consider: Sigil v0.9.3 does not allow the editing of an EPUB3's metadata with the graphical Metadata Editor (as you noticed). Did you manually add metadata to the OPF file in Code View? I only ask because you specify you're creating new epubs as EPUB3s with Sigil: which means there should be no metadata in the opf (other than a dc:identifier), so I need to understand how those metadata elements are getting populated in the first place.

Also, are you adding existing files to the new EPUB3 with Sigil? If so, there's a bug in Sigil v0.9.3 that can cause EPUB3 metadata in the OPF to be corrupted as a result (reverted back to EPUB2). I'll let Kevin answer more definitively, but I would think there would have to be some existing EPUB3 metadata to get corrupted in the first place, though. I could be wrong on that.

If you ARE adding external files to a new EPUB3, you may want to take a different approach until the next version of Sigil is released (in which the bug is gone, and metadata can be edited "normally.")

My recommendation (until Sigil v0.9.4) would be creating your epubs as EPUB2s. Then add whatever files you need; edit your metadata, and when all is well (and validating), use the ePub3-itizer plugin to convert it to an EPUB3. Once you have your EPUB3, do not use Sigil v0.9.3 to add any existing external files or the metadata could get corrupted again.

03-06-2016, 02:47 PM	#3
DiapDealer Grand Sorcerer Posts: 28,373 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	EDIT: KevinH posted in the time I took to compose mine. There may be some overlapping stuff. It sounds as if something overwrote the metadata section of the opf file with EPUB2 metadata. Did you edit the EPUB3 with anything other than Sigil v0.9.3? Points to consider: Sigil v0.9.3 does not allow the editing of an EPUB3's metadata with the graphical Metadata Editor (as you noticed). Did you manually add metadata to the OPF file in Code View? I only ask because you specify you're creating new epubs as EPUB3s with Sigil: which means there should be no metadata in the opf (other than a dc:identifier), so I need to understand how those metadata elements are getting populated in the first place. Also, are you adding existing files to the new EPUB3 with Sigil? If so, there's a bug in Sigil v0.9.3 that can cause EPUB3 metadata in the OPF to be corrupted as a result (reverted back to EPUB2). I'll let Kevin answer more definitively, but I would think there would have to be some existing EPUB3 metadata to get corrupted in the first place, though. I could be wrong on that. If you ARE adding external files to a new EPUB3, you may want to take a different approach until the next version of Sigil is released (in which the bug is gone, and metadata can be edited "normally.") My recommendation (until Sigil v0.9.4) would be creating your epubs as EPUB2s. Then add whatever files you need; edit your metadata, and when all is well (and validating), use the ePub3-itizer plugin to convert it to an EPUB3. Once you have your EPUB3, do not use Sigil v0.9.3 to add any existing external files or the metadata could get corrupted again. Last edited by DiapDealer; 03-06-2016 at 02:58 PM.