View Single Post
Old 06-23-2021, 12:45 PM   #11
Joliet Jake
Zealot
Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.Joliet Jake ought to be getting tired of karma fortunes by now.
 
Posts: 111
Karma: 3098438
Join Date: Feb 2021
Location: Canada
Device: Kobo Sage
Quote:
Originally Posted by davidfor View Post
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.
Thank you for the clear answer.

For the ones protected by DRM, I will probably delete them from the Kobo, temporarily disable KTE and use KT, then send them that way. (I had to do that once for a book that simply couldn't be transferred with KTE. To be fair, that was just once, and the cover wasn't really an issue there.)
Joliet Jake is offline   Reply With Quote