View Single Post
Old 06-23-2021, 11:14 AM   #9
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 Joliet Jake View Post
I now have some cover problems. I wonder if it's because I'm using Kobo Touch Extended and not just Kobo Touch or Kobo Utilities. (I think KTE uses a different way of transferring the cover. I have to edit the books themselves as it ignores the cover metadata.)
If you are sending covers to the device, then they are handled in exactly the same way. Other than kepub related things, the KoboTouchExtended driver is using KoboTouch driver.

But, covers in kepubs and epubs are handled differently on the device. For epubs, the first page is rendered and used as the cover. For kepubs, the cover image in the book is marked as a cover and extracted. That is one of the things the KoboTouchExtended driver does when changing the book to a kepub, it adds an extra property attribute that the device is expecting to the image marked as a cover. But, if there is no image correctly marked as a cover, that doesn't happen. As you are editing the books to fix this, it means the cover was not marked properly for the driver to see and hence the device to use.
davidfor is offline   Reply With Quote