View Single Post
Old 07-23-2022, 12:13 AM   #7
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 ajkessel View Post
I'm scripting all my syncing using KoboCloud. I gather KoboTouchExtended is just for transferring over a wire. Is there any reason my workflow can't be:

- ebook-convert filename.html to filename.epub
- ebook-polish filename.epub polished.epub
- ebook-convert polished.epub to final.kepub

(and then final.kepub ends up in a cloud storage folder that gets synced to the Kobo device)

I.e. any difference between these steps and transferring to the Kobo over a wire using KoboTouchExtended?
The difference is that the conversion does what the name says, a conversion. Calibre conversions basically work by changing the book to a common format and then converting to the final format. It does a lot of things including rebuilding the CSS, the ToC, splitting files, etc. And in the case of a conversion to kepub, it is actually using the epub conversion then kepubifying that. So a conversion from epub to kepub is really an epub to epub conversion plus what the extended driver does.

Looking at your commands, what is the point of the Polish? The conversion should be able to do all the options that are in the Polish. The steps might make sense when using the GUI. You add the HTML file to calibre with an automatic conversion to epub. Then download metadata followed by the Polish and then a conversion. But, the Polish can be skipped as all options in it are in the conversion. Or done when calibre does a save-to-disk or send-to-device.

And, unless you also want the epub for other reasons, you could probably go directly from the HTML to kepub.

With what you are doing, @DNSB's suggestion to use kepubify for the last step is a good idea. That does basically the same thing as the extended driver when transforming an epub to kepub. The full conversion is not needed, so it will be quicker.
davidfor is offline   Reply With Quote