Thread: ebook-polish failing to initialize plugins
View Single Post
Old 07-22-2022, 03:07 PM   #6
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,625
Karma: 169712392
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
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?
For a command line tool for converting epub to kepub, you might want to look at kepubify instead of ebook-convert.
DNSB is offline   Reply With Quote