View Single Post
Old 04-18-2022, 08:06 AM   #5
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
Calibre uses the drivers to communicate with the devices. Hence, file naming on the device is up to the driver. The built-in KoboTouch driver handles the renaming when sending a kepub from the library. The KoboTouchExtended driver inherits this and hence does exactly the same thing. The renaming of epubs that have been transformed to kepubs by the extended driver is handled separately.

In any case, it is working here with either driver. I can't think of a way it could fail. To take a guess, run calibre in debug mode, send a kepub and post the log. Hopefully it will show there.
davidfor is offline   Reply With Quote