Thread: Replace KA1 header
View Single Post
Old 07-02-2017, 07:46 PM   #15
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 trekk View Post
I rarely use nickel, so I configured the Kobo Touch Extended Driver a long time ago, but kept it updated in Calibre.

I can only repeat that every time I add a epub to my Aura One, automagically a kepub is added to my library! For shalym it seems to be the same.
As I said, the extended driver doesn't add the kepub to the library. But, if there is no suitable format to send to the device, calibre does a conversion when you send the book. The second screenshot shows the list of formats you are allowing to send to the device. As that doesn't include epubs, whenever you send an epub, it will be converted to the first format in that list. That format is kepub. Hence, every time you send a new epub to the device, it is converted to an epub, saved in the library and then sent to the device. And because you are converting the books kepub, you aren't actually using any of the features of the extended driver. Or at least none I can think of.
davidfor is offline   Reply With Quote