Hi Idolse, Thanks for all the feedback.
I decided as per the screenshot I may as well offer the "tweaking" of soundex fuzziness. As I said the values I picked were purely arbitrary so others can if they want do multiple passes with smaller or larger values.
Thanks for the heads up on the decode function. Actually right now I don't do any conversion of those values, I just ignore them! So it was purely by coincidence (that i and e have the same soundex values and were following each other) that it worked for you in this case.
However your suggestion to use this for all comparisons I think is an inspired idea. Not I think on the "identical" matches, but on every other kind of match I think it makes sense? Obviously I don't know the downside if any to that function - is there any reason not to use it everywhere other than performance which isn't really much of a concern imho versus the improved matching?
In terms of exempting your nopub tags. You can do this already, by setting a restriction at the time you do your duplicate search. Duplicate search respects any restrictions applied, so just put "not tags:Nopub" as a restriction and you should be good to go.
For the keyboard shortcut - you can configure one yourself in the plugin configuration screen for that function. As promised earlier in this thread I am going to remove the default I have in there currently of next/previous match. If someone has a brilliant suggestion for next/previous that doesn't conflict with existing calibre shortcuts I am all ears. The best I have seen suggested was Ctrl+N (with maybe Ctrl+Shift+N for previous). If people want that then I will put that in otherwise you can just configure your own.
The "last set" wonkiness sounds very odd and I haven't been able to replicate it. Was that showing one group at a time or all at once? You said finishing "all/most" - which was it? When did it go wonky - how many sets were remaining?
|