Quote:
Originally Posted by bkilian
.... My books are stored in separate subdirectory trees for source files and then a tree for each of the readers (We have both Kindles and Sony Readers.). When I get a new book, I put it in the source tree, and the scripts take care of making it available to the device trees.
Keeping this separate is good for regenerating all my LRF or Kindle books when Kovid makes a useful change to the conversion program. It also means I can point the Sony software at my Sony directory and not worry about it catching stray epubs and duplicates.
I use the Sony software to move books onto my device, pretty much sorting by the "Date" column. I have to manually scan to update when new books arrive, but that's a minor issue. I would prefer if it could detect that automatically. I use the software because I prefer not to make the reader do the pagination. It takes too long, and uses up battery I could be using for reading.
I only use LRF on my reader, and will keep doing so until they can get ePub to render correctly (justified, and not crashing)
I really don't like flat, tag based management UI (Like Calibre and iTunes) I much prefer heirarchical organization, even if the heirarchies are arbitrarily chosen. (Like the Windows Media Player UI)
|
So you have created a custom system (as the previous poster) and don't want to do it a different way. That's fine, thanks for the info/explaination.