Quote:
Originally Posted by JSWolf
I highly disagree with subdirectories such as author based subdirectories because eventually you'll end up with a lot of empty subdirectories. I don't mind book or elib as a directory to place all the books. I have my template when sending to my Kobo as...
Code:
books/{{author} - {series}{series_index:0>2.1f| | - } {Title}
That create one subdirectory that will always have books in it. I will not end up with multiple empty subdirectories. Now if say Kobo Utilizes has the ability to search a directory tree and remove empty subdirectories, that would be different.But it doesn't so I don't want empty subdirectories. |
How are you getting so many empty directories? For the most part, I use calibre to add and delete books from my Kobo ereaders and when I remove the last ebook from a directory using calibre, the directory is deleted as well. That is something that you can easily test.
On a more philosophical note, why do you object to empty subdirectories? It's not as if they consume a mass of storage space. I'm never going to have over 65,534 authors in my calibre libray so I am unlikely to reach the maximum number of directories and I am even more unlikely to reach 268,435,437 files which is the maximum number of files on a FAT32 partition.