|
Well it wasn't originally clear if that's what I absolutely had to do. I was looking for a simple yes or no answer if this was supported out of the box with a tweak or something but got pointed to the usual stuff about switching to LN, FN within Calibre. You happened to reply while i was already resigned to having to pour thru the source. I misunderstood your reply since it was after mine. Please take no offense. Calibre is great. I love it's management and metadata scraping. I'm just a little nitpicky about the library storage since I find it much easier to copy the few unread books to my device outside of Calibre.
I haven't had a chance to look thru the python source yet (it took too long for bzr to sync it all), but I'm assuming a function is used to convert a book's metadata info fields into a sanatized path. I've already poked through the db schema with sqlite. I figured I'd start with the add to library function, looking in particular at the regexp piece that attempts to pull metadata from source file names and then moving the book into the library hierarchy.
Why is comma not allowed? Every file system I've worked with since 2000 supports comma (FAT32, NTFS, HFS+, ext2/3/4, UFS). NTFS even supports the characters Windows doesn't allow (:/?) when mounted on another OS. Just curious.
|