Comments in content.opf with Sigil 0.9.2

[turbulent]

Hi,

With Sigil 0.8.x, the file content.opf in the epub from plugin KindleImport contains some comments generated from the metadata of the original mobi/azw3 ebook, as followed:

    <!-- BEGIN INFORMATION ONLY 
<meta name="Cover ThumbNail Image" content="Images/image00253.jpeg" />
<meta name="Drm Ebookbase Book Id" content="0006002627397" />
<meta name="ASIN" content="B00QLSKYGU" />
......
END INFORMATION ONLY -->

After updated to v0.9.2, these comments seems to be automatically cleaned by Sigil. Is there any convenient way to keep them?

[KevinH]

Hi,
Unfortunately not. The opf is parsed and rebuilt from stored data structures to prevent constant reparsing to speed up performance. Comments are not kept as there is no place in the internal datastructures to keep them as comments can be put just about any place. I guess I could create a comment node for every major tag in the opf and collect them from anyplace inside that tag and store them. It just didn't seem to be worth the effort as the opf was meant to be machine readable (which is how it is used in Sigil). This has been true dince the Sigil 0.8.900 pre-releases if you do any operation that requires changes to the opf.

KevinH

Originally Posted by turbulent

Hi,

With Sigil 0.8.x, the file content.opf in the epub from plugin KindleImport contains some comments generated from the metadata of the original mobi/azw3 ebook, as followed:

    <!-- BEGIN INFORMATION ONLY 
<meta name="Cover ThumbNail Image" content="Images/image00253.jpeg" />
<meta name="Drm Ebookbase Book Id" content="0006002627397" />
<meta name="ASIN" content="B00QLSKYGU" />
......
END INFORMATION ONLY -->

After updated to v0.9.2, these comments seems to be automatically cleaned by Sigil. Is there any convenient way to keep them?

[DiapDealer]

Weird timing! I'm thinking about adding a configurable option to KindleImport to preserve that KindleUnpack metadata. It would simply remove the html comment tags so all of those individual metas would remain a part of the opf. It would then be up to the user to delete/keep the data.

[turbulent]

Hi, DiapDealer

That's exactly what I need. And I'm just thinking asking you to consider adding this feature to KindleImport! Well, I'll wait for it.

[DiapDealer]

Originally Posted by turbulent

Hi, DiapDealer

That's exactly what I need. And I'm just thinking asking you to consider adding this feature to KindleImport! Well, I'll wait for it.

KindleImport v0.80.6 should now do what you need. Read the instructions in the plugin's thread for changing the "preserve_kindleunpack_meta" preference to "true" (though it occurs to me that it will only work for AZW3/KF8 books and NOT the old-style mobis ... should be able to add that ability in the next version).