Quote:
Originally Posted by JSWolf
Actually, don't remove the Sigil line in the OPF. It's nice to know what program what used to edit the ePub. The rest of the Calibre OPF additions can go.
|
there is no granularity with the remove option, just like there is no granularity with the websites that reject epubs with this data in it. If you want control like that then you would tweak ePub it.
Quote:
Originally Posted by JSWolf
I mean, why have Calibre modify the ePub's OPF when there is a Calibre OPF that can be used for that. The stuff Calibre puts in is only valid for use with Calibre. So really, it belongs in the other OPF. Not the ePub's.
|
Right, for which I gave the answer above - any tools that you open the ePub with use the internal data, nothing uses calibres opf file except calibre when restoring a library or adding books. And not all of the data updated is calibre specific. For instance the title and author fields. Or the cover. Like I said the net effect is no different to exporting from calibre.
Now arguably someone might want an option to do an update metadata which only does non calibre specific stuff and does not insert all the junk like custom column data. However the calibre code offers no such granularity, which would mean I have to replicate it into this plugin and maintain it. Which I can't be bothered with, since few people on this earth are bothered by metadata cruft, and those that are can choose either not to use the Update metadata option, or can do a Remove non dc: metadata pass after it.