Quote:
Originally Posted by geek1011
I agree about calibre. It is kind of messy. I usually just read the source code, and find out what is done well, what could be done better, and what isn't done at all, then make some standalone tools to do what I want.
My biggest dislikes about calibre is: it's folder structure, how it is hard to version with git, it's meta tags (except for series, and I'm a purist), it's calibre# classes (again, I'm a purist), it's black boxness (I don't know exactly what goes in and out of the db), and it's too many features.
I still use calibre for certain tasks, but then I clean the ebook up afterwards.
For the calibre developers: don't feel bad, I am like this about quite a few other tools. I'm the kind of person who like manually editing ebooks with bash, grep, sed, vim, and vscode. I also still use calibre, a bit in an indirect way.
|
I've found that with Calibre, if you change some of the settings, you can put books in and get them out without Calibre doing any conversion or metadata update. I can also use the editor without any changes except the ones I make. But if you want this behavior, you have to change some of the default settings in Calibre, the Editor, and the Viewer. But I've done it and I can use Calibre the way I want.
I don't convert ePub to anything unless the code is that sloppy that I want to see what Calibre does to with the mess. I don't convert KF8 to ePub. I use the KindleUnpack to format shift the code and then the editor to clean it up.
I have my ways and when I'm done, the ePub code has not been changed except by me.