Quote:
Originally Posted by Rev. Bob
When you tell Modify to “update metadata” (the green box on the thumbnail) – that can include those identifiers, but only if you’re calling Modify on an ebook you’ve already saved from calibre and have since gone back and made changes to its entry in the calibre library. My normal workflow is to use the “download metadata” feature of calibre proper and straighten all of that out before I save the EPUB elsewhere, so I never even touch that option… but every ID listed in calibre’s metadata dialog gets its own dc:identifier element in the OPF file.
And that’s true even if you never use Modify ePub on the book.
I can edit the book within the standard calibre editor interface, after acquiring metadata but before doing anything else and without ever running Modify on it, and that list of identifiers is already there.
|
Interesting. I re-imported the book to calibre. I then ran ModifyEpub on it. The <dc:identifier opf:scheme="UUID">urn:uuid:e6f8ccbf-f756-4a24-8f2e-7fa9b76df046</dc:identifier> line disappeared. And 4 dc:identifier lines were added to content.opf. So basically, import the epub file to calibre and run ModifyEpub. No updating metadata, no editing in calibre, no polishing, etc. Those lines were added by ModifyEpub likely from metadata extracted from the epub by calibre. I will admit I used Sigil not the calibre editor but that should make no difference.
I will also still disagree that the dc:identifier line that is being removed is a "Adobe resource DRM meta tag" though it is used by Adobe's font obfuscation. After all the blasted epub was downloaded from Kobo as one of their GUID named.epub downloads which says no Adobe ADEPT DRM was being used.