That appears to be a change in 2.59. The change list includes:
Quote:
EPUB metadata: When setting a cover image for an EPUB file that has no metadata cover image defined, add the new cover image as a pure metadata cover instead of aborting.
|
Calibre has always update the cover when updating the metadata. But, this means it is also adding a cover image when there isn't already one. That might be good, but I have a large set of books that do not have a separate cover. The first page is a simple cover with the title and the author. This change means calibre is generating a cover from the first page and then adding it to the book later when updating the metadata. As it is updated when editing (as theducks pointed out, this can be turned off) or when the book is sent to the device.
Apart from adding a file that is useless to me (the Kobo devices render the first page for the cover), the problem I have is the cover image calibre adds no longer represents what I consider to be the cover. If I fiddle with that page after the book is added to calibre and that cover image is added to the file, updating the cover that calibre shows in the library means I have to delete that cover image from the book first. Personally, I'd like an option to turn this off without turning off the other metadata update.
There does seem to be a problem. Some of these books have the following in manifest:
Code:
<item id="cover" href="cover.xhtml" media-type="application/xhtml+xml"/>
When the image is added, the above is still there, but the following is added:
Code:
<item href="OEBPS/cover.jpg" id="-1.cover" media-type="image/jpeg"/>
Looking at the directory structure in the book, the "cover.xhtml" is in "OEBPS" and the "cover.jpg" is in "OEPBS/OEBPS".