Quote:
Originally Posted by dandman
the way to do things and to gain both sides is to separate data and presentation / transport layers, so the files can be saved wherever and in whatever name, and when indexing / sending - set the proper headers to set a different filename to the kindle or index table,
|
It does. The books in the library are not what the user sees or uses. That's why there is "Send to Device", "treat a directory(folder) as a device" and "Save to disk"
You can sort/organise and name the spreadsheet view of the library however you like.
Filenames when it comes to books or documents just need to be unique. They only need to be human readible when exported for something like KOReader that's like 1970s "management" as it doesn't use metadata browsing but OS filenames. Any decent Library view rather than simply a file viewer uses metadata in a database, not filenames.