|
It doesn't matter that calibre (currently) manages its files in a filesystem -- it's not your filesystem. It could name all its files 'George' for all the user cares. It used to use a database, today it uses a filesystem, tomorrow it may do something totally different. Calibre doesn't manage files, it manages books. If you have a book called "How to Read" that book may be in one file or many, it may be in a filesystem, a database, or partly in each, it may be in as many formats as calibre knows about, and none of that matters to the user; all that matters is that the book exists, it is, or can be converted into, certain formats, and if the user wants the file itself (in whatever format) it can be exported wherever and however said user wants. The particular way that calibre (currently) stores any or all of those formats -- which may be different tomorrow -- isn't any part of that.
Yeah, I'm starting to sound a bit testy about this. In the time I've been hanging around MR, every so often (thankfully, not as many times as we used to get) there are people who show up and ask "How can I make calibre not work like calibre?" That's why I wrote the post I reference in my .sig (and the reason it's there). Thankfully, none of the more recent ones have started out by insulting Kovid, but they were doing that for a while, too.
The bottom line, anyway, is that you have two choices: You can use calibre in the way it was intended, as a program to manage books with. Or you can get a program that manages files for you. But you have to pick one. If it's going to be a program to manage files, I wish you good luck; I have no clue what they are, but I'm sure someone here does and can help you. If it's going to be calibre, then you have to accept it managing books, forget about files entirely, and let it do what it does. And one of those things is treating calibre's private library as a black box, pretending it doesn't exist at all, and using the calibre GUI and native functions to interact with your books, instead of trying to have it both ways and treat them as files, too.
|