Thread: Replace KA1 header
View Single Post
Old 07-02-2017, 11:22 PM   #20
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 shalym View Post
Yes...and it also saves the kepub in my library. According to you, it shouldn't be doing that.
Wanna bet?

And to state explicitly what will happen:

If the driver is configured to send both epubs and kepubs, if you have an epub and no kepub, the extended driver will transform the book to kepub during the send and not save it in the library.

If you send a book that doesn't have a format in the supported list in the driver, it will be converted to kepub (or the first on the list) and then sent. The driver is not involved in this except to specify the formats. The kepub will be saved in the library as the conversion happens first, then it is sent to the device. For this, it doesn't matter whether you are using the extended driver or the built-in KoboTouch driver. And all the other devices work the same way with the formats they support.

If you have a kepub in your library, it is there because a conversion happened, not because the extended driver did something.
davidfor is offline   Reply With Quote