Quote:
Originally Posted by DNSB
I would disagree that the tag is solely an Adobe resource DRM meta tag though it is used for that purpose. It is after all one of the few registered Identifier Schemes.
|
Uh, no. That’s not even
remotely connected to my diagnosis. See the attached thumbnail – the same one you posted, but now with a bonus red box to highlight the option where you’re telling Modify to break your fonts.
Quote:
Originally Posted by DNSB
ModifyEpub can and does add multiple dc:identifier tags most of which I find relatively useless.
Code:
<dc:identifier id="uid">3502494312</dc:identifier>
<dc:identifier opf:scheme="calibre">3ef7f9c4-ada8-4147-8dfb-4c97c03a767f</dc:identifier>
<dc:identifier opf:scheme="AMAZON">B07NPX4L18</dc:identifier>
<dc:identifier opf:scheme="ISBN">1988891003</dc:identifier>
<dc:identifier opf:scheme="KOBO">book_title_3</dc:identifier>
|
Modify ePub doesn’t generate those. Those come from calibre.
EDIT TO CLARIFY:
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.