Quote:
Originally Posted by kpw
Just to clarify though, do you see this issue when you configure "Device Collections" or "Library Query"? For the collections approach, the plugin just looks at books on the device and doesn't do any matching with anything in the library, so I think things should work there (assuming the plugboard support sets the book title in the device book file to the updated value - this is part of what I'll be researching  ). For the query approach, I can see that the plugin would fail to find matches between the library query results and the device since I'm assuming exact matches between titles in the library and titles on the device (and I think this assumption falls apart when plugboards come into the picture). |
You're right, I'm actually using a library query, not device collections (#status:=Reading). Perhaps it would possible to feed the library title to the plugboard component, which then returns the converted title? But of course that's from someone who doesn't know the first thing about Calibre's inner workings
On a similar note, I always use library restrictions to switch between read/unread and fiction/non-fiction, keeping the tag browser closed. Might it be possible to give the plugin an option to perform its library query on the entire library, not the restricted one? I often read a fiction and a non-fiction book at the same time (so both have #status:=Reading), but keep my view restricted to fiction - so the plugin only sees one.