Quote:
Originally Posted by jackie_w
 ... far be it from me to tell you how to spend your leisure hours  but are you aware that calibre already contains loads of utilities for robust, reliable manipulation of the various innards (opf, html, css, ncx/nav, unpack/pack etc) of an epub? Many things can be done in just a few lines of python code. If they don't currently do everything you may want to do you can mix'n'match existing functions to achieve what you want. |
I do it partly for the learning, and also because I use it as a library. I'm planning to also merge all the duplicate epub-related code in my tools (kepubify, seriesmeta, BookBrowser, etc) into this. As most of it is just consolidating work I've already done, I expect this to take at most 10 hours of additional work in total.
Quote:
|
Even if you don't want to be bothered writing full-blown calibre GUI plugins you can still access all the same functions from simple python scripts outside calibre. Neither do the epubs need to be in a calibre library structure.
|
As I have expressed before, I strongly dislike the calibre* classes and meta tags which are added (I also wish it could be a bit faster). I also do a lot of work with epubs (not all of it is public) and Go, so the time I spend is worth it. In addition, sometimes, I just want to make a quick change to an existing epub from the command line, and it is faster when I can avoid all the extra stuff in calibre.
P.S. I'm also
slightly stubborn about avoiding Calibre too.