View Single Post
Old 10-13-2019, 07:18 PM   #1304
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,213
Karma: 170056770
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Rev. Bob View Post
I will also remind you that calibre itself has seen a major update (to 4.x) recently, which is a considerably more likely culprit. Once again, this is not a calibre bug thread. It is a Modify ePub thread.
I went back to the oldest version of ModifyEpub that I have kicking around in my archives that would work with Calibre 4 and the issue persisted. I did a quick and dirty test that imported set_metadata and executed it and bye bye dc:identifier.

If it works (it's been a bit since I filed a calibre bug report), I've created a bug report for the issue.

As for ModifyEpub 1.40, I have to say it was an innocent bystander. Of course, in the spirit of Kovid working around bugs in QT, etc., have you no desire to work around a bug in calibre?

Last edited by DNSB; 10-13-2019 at 07:21 PM.
DNSB is offline   Reply With Quote