Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 05-23-2013, 07:03 AM   #236
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Leonatus View Post
Indeed, I have almost all my books on SD card. Strange only that this issue appears only since the last few days, the Fw. 2.5.2 beeing installed for a month, I think.

What I thought of last night is trying to delete the books on the SD card, convert them again with Calibre and send again to the card.

What do you mean with "send the covers from calibre when sending the books"? By working out the metadata, I always try to implement a cover image, if not even doing so by formatting with Sigil, the final conversion accomplished with Calibre.

My last question going to ask whether there might be a different way to implement covers.
Covers for epubs are generated by the device from the first page of the book. For sideloaded kepubs, the cover image is extracted from the books based on a statement in the OPF within the book. The extended driver modifies this statement so that the device can find the cover.

With FW2.5.2, the covers for books on the SD card are shown, but not stored on the device. And no cover is used for the sleep cover. But, if the cover images are put on the SD card by some other mechanism, they are used. This includes the sleep cover. The driver includes options to create the covers on the device when a book is sent to the device.

The reason you are seeing the sleep cover problem now, is either you have changed the driver options, or you have sent some new books. With FW2.5.0 and 2.5.1, the cover images for books on the SD card were saved. While you were reading those books, the covers images existed so where used.
davidfor is offline   Reply With Quote