Quote:
Originally Posted by BetterRed
@rebl - calibre reports on files it knows about in its database, ordinarily it does NOT walk the folder tree. Run Library Maintenance-Check library phases 1 and 2 - resolve any errors in phase 2.
BTW in Windows you cannot have 2 files... filename.doc and FileName.doc... in the same folder. You can in Linux and OSX (maybe not all versions).
BR
|
Thanks BetterRead.
My library is checked and has been checked periodically (doing it right now one more time). It does the vacuum thing, then checking for matching information and files. No errors found. After step 2, no errors, "the files match the information in the database"
In tag browser or format search I see 15660 doc files.
I've done a new save to disk, using {id} in the folder path and the results are surprisingly different than before.
Now I have
- 15660 opf files, 15660 doc files and 26 jpg files.
Windows reports 31346 files in folder properties.
I've deleted the previous export folder with the missing files (which only had 15624 doc files) so I can't go batch the check it in more depth. I also find a small problem in the way I was counting doc files - three of the files had ".doc" in the file names itslef so if not paying attention and searching for .doc I also had three .doc.opf files (but that doesn't explain the missing 36 or possibly 39 doc files).
So my conclusion to this is that it is safer to "uniquify" the save to disk folder naming scheme. If I did this I got the expected result.
When I did not, something wrong happened in the save to this process. Maybe calibre since it also supports linux, is able to produce filename.ext and FileName.ext pairs? I don't know, I can't test it anymore and I've lost a lot of time already to this. I've also seen lots of filename (1).ext and (2) in the same exported book folder... so in theory calibre does produce unique file names but... who knows what happened....