Quote:
Originally Posted by JSWolf
I didn't associate any cover with the book. Calibre did. Calibre associated the current cover. So your plugin just basically puts that back in. That's of no use to anyone. It should prompt for a new cover image to use. It should not assume that everyone knows how to associate the cover they want with the eBook. It's just not working if all it will do for a lot of people is put back the same cover they didn't want in the first place.
|
Here is some calibre 101 just for you...
When you add a book to calibre, it will only extract the existing cover from the book if in Preferences -> Adding books you have set "Read metadata from file contents rather than file name". In that situation, *if* the book has a cover that calibre is able to detect, it will make that the default cover.
However if you don't have that option checked (or even if you do) many users subsequently use metadata download plugins to pull in corrected, missing or better metadata and covers for a book. Or they use the Search the Internet plugin to use google images and drag/drop in the cover.
I am *not* going to add yet another interactive option to this plugin for choosing a cover - it already exists in multiple places in calibre. If you don't want to use a metadata download or STI plugin, then just hit E to bring up the metadata download dialog and click on the Browse button next to the existing cover image.
The whole point of calibre's cover browser, book details panel etc is to show you the cover associated with a book, independent of what image is currently inside the book. You however are coming from a command line background with ebook-convert, rather than already being used to calibre's existing gui workflow / conversion engine - which incidentally uses exactly the same ingrained expectation of using the cover image a user has associated with the book in the calibre library.
Now as to why a user would extract the existing cover from a book and then use this plugin to put it right back in again... umm, you did it, not me? I will say that what this functionality will do for some ePubs is ensure that the cover being put back into the epub (a) has *all* the manifest entries created perfectly to ensure the cover is correctly identified by a range of devices and software, and (b) that the cover image has been rescaled to match your output device profile, to reduce epub size and possibly render better on that device.
Thanks for the PM'd link btw, I will take a look into why that ePub didn't get kicked out earlier shortly.