I'd like the matches displayed on the matchboard to be displayed in a sane order.
I'd like to have the most likely results (exact glossary matches, exact memory matchs, prefix glossary matches) at the top and the speculative ones (fuzzy and virtual memory matches [what's the difference?]) hidden away out of sight at the bottom.
Right-click at the Matchboard and uncheck Sort matches alphabetically. Then CafeTran sorts by quality with source duplicate grouping.
Virtual matches are fuzzy fragments with higher probability of the accurate match. You can control this option via Edit > Preferences > Memory tab > Subsegment to Virtual match threshold.
Then if you use any of the recent CafeTran 2017 updates, you should have the expected Matchboard sorting - the exact fragment matches at the top (just below full segment exact and fuzzy matches). Note that with source duplicate matches, CafeTran groups them all, along with the exact fragment duplicate.
Just re-animating this conversation:
The matchboard is unflexible and does not reflect the usual order. This would be:
Fragments & segments
Fragments & segments
Any chances to have a rather conveniently ordered Matchboard soon? Not to forget such a trivial thing as "Sort by appearance in source".
This still doesn't work as it should.
I'm set to 'Sort by quality', but I have exact matches from the project TM (priority set to high) right right at the bottom the (very long), after dozens of speculative 'hits' (whatever that means).
Also one comment on the fuzzy algorithm – from the frequency with which it decides that common words are matches for something completely spurious, I assume this looks only at positives, and takes no account of negatives.
I'll illustrate what I mean by an example:
My TM tab currently lists the following match (indeed it's the top match):
My impression (which may be mistaken) is that CT takes no account of the large number of segments which contain 'diese' but do not contain 'processing', which should cause it to discard this as a match.
Would it be possible to correct this behaviour – i.e. allow the presence of even modest numbers of non-matches to negate the presence of large numbers of matches. I appreciate that this would slow things down a little, but it would vastly improve the results.
> after dozens of speculative 'hits' (whatever that means).
It depends on your TM settings (e.g. "Prefix matching" option on for the given TM). You should be able to see the type of the match (e.g. Exact, Virtual, Prefix) in the Matchboard. A Matchboard screenshot of the issue would be clearer.