I agree that there are a number of ways to force the metadata but I would like it to update automatically on "Save to" and "Send to".
That said I have diagnosed the problem and determined that when the embedded description in the .opf section of a source .epub is of the form
Quote:
|
<description xmlns="http://purl.org/dc/elements/1.1/"><The must-have ....
|
rather than
Quote:
|
<dc:description><The must-have ....
|
, caliber will correctly create its .opf file containing <dc:description><The must-have .... however it will not correct the .opf section in the exported .epub file.
I think this qualifies as a bug since calibre correctly identifies the epub/opf <description and corrects it to <dc:description in its own .opf but not in the exported epub.
However, I also note that the epub viewer also fails to load these <description(s) into its Comments box, whereas it does load <dc:description(s) correctly, and Moon Reader also fails to accept <description as a valid description, so I conclude the real problem is with the use of <description in these epub source files over which I have no control, however I would expect Calibre to output the valid <dc:description format from its corrected .opf in the exported epubs.
In support of this request, I note that if the <dc:description field in a source epub is changed, that the change is not only reflected in the caliber .opf file but that the .opf content is also used to update the .opf in the exported epub. Hence the mechanism exists to reflect the <dc:description label change as well in the exported epub.
I have many downloaded source epubs that utilize <description rather than <dc:description so its not a minor requirement for me.
Should I raise a bug report?