manybooks : fix typo.
This commit is contained in:
parent
5ec0c51494
commit
ef62ebb7fe
|
@ -11,7 +11,7 @@ Second one is, obviously, search. Each archive ends up being a single Calibre li
|
|||
Third one is optional, but storing one big file is much easier than storing thousands of smaller ones. Here is where archival tools come up handy.
|
||||
|
||||
## Solutions.
|
||||
As for grouping, I've tried to keep things look the same as they came to me. Those archives I got were named in ranges, like `000000-134445.zip`. So I kept this numbering with a little chage. I was horrified by a thought that one day they will release books past 1 million, and it will create an extra digit. It'd ruin alphabetical sorting!! And I just added prefixes like `000001_000000-134445`. I can process and store a million books, but no way I can do this for a million of such groups! Even this collection is about 400 GB compressed. This is *"good enough"* for a forseable future.
|
||||
As for grouping, I've tried to keep things look the same as they came to me. Those archives I got were named in ranges, like `000000-134445.zip`. So I kept this numbering with a little change. I was horrified by a thought that one day they will release books past 1 million, and it will create an extra digit. It'd ruin alphabetical sorting!! And I just added prefixes like `000001_000000-134445`. I can process and store a million books, but no way I can do this for a million of such groups! Even this collection is about 400 GB compressed. This is *"good enough"* for a forseable future.
|
||||
|
||||
Second issue is search. You can export Calibre database in CSV by running this command: `$ calibredb catalog index.csv` inside your Calibre library. This will put a file called `index.csv` inside it. Rename it to group's name like `000001_000000-134445.csv` and store in a separate directory. Later you can do something like `$ rg "Война и Мир"`, and it'll show you something like this:
|
||||
```csv
|
||||
|
|
Loading…
Reference in a new issue