Quote:
Originally Posted by dwig
For performance reasons, calibre does not display either the cover or the metadata that is in the book. Instead, it uses a separate cover file stored beside the book and metadata stored in calilbre's own database. The cover file and the database metadata are extracted from the book when the book is imported into cablire's library so initially they match the contents of the book. Any edits in calibre are to its copies and not the the book itself unless you take special steps to inject the updates and changes into the book itself.
Many ereaders also avoid displaying the book's internal cover until the book is actually opened. Again for performance reasons, they use a separate cover file. Many of these readers won't extract a cover from an imported book and rely instead on the download/sideload service to provide a separate cover file. When calibre provides such files it uses its separate cover file and not the one actually in the book. Again, if you have not taken steps to inject a new cover into the book the external cover file and the internal file in the books won't match so you'll see one cover in the book list and another when you open the book for reading. If you have calibre convert formats when syncing with your device the updated cover will be used for the converted file, deleting the old cover. With some formats, other automated update functions can be configured to update cover and metadata during sync without actually running the book through a conversion process.
|
dwig, thank you very much for the explanation!
Now I know how it works too
