View Single Post
Old 08-23-2019, 08:25 PM   #4
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,859
Karma: 6120478
Join Date: Nov 2009
Device: many
Okay, I just pushed some changes to master that allow the epub3 metadata editor to allow editing and creation of unrecognized (primary) meta tags. Those are meta tags whose whose property attributes do not match any of the elements/properties the editor recognizes.

The fix will appear in the next release of Sigil. Until then open the content.opf tab in Sigil and directly edit any metadata meta tags that do not involve refines (ie. are primary).

Thank you for your bug report.

Quote:
I'm running Sigil 0.9.17 and have a problem with the metadata of Epub 3.0-books.

If I open the Metadata-editor, I only see the "Dublin Core"-elements, while at least 1 book had a content.opf with an entry that definitely lookes like a non-DC element: "Sigil Version" (value "0.9.16"). Yet it doesn't show up in the editor. Why?

If I try to add an element: Add Metadata > Custom element, it seems to go Ok. A "Custom Element" appears in the list of metadata-elements, and I can fill in the values. I then exit with an "Ok".

But when I then re-enter the Metadata editor, this custom element has disappeared! It's not in the content.opf either.

So...what gives? Is it a bug or a feature?
KevinH is offline   Reply With Quote