The solution to add all such variants is not really practicable.

Another "problem" that I detected today. Where does Verify get some of its false positives?
"änderbar" is matched as being "Änderung" (present in the TB ), but "changed" does not match "change" (in the TB).

Anthony Rudd

This is indeed problematic.  The new Language Cloud (Trados Live) Terminology can do a better job of identifying words in the source, but not the target.  The verify feature in Trados Studio will look for the source but then doesn't do any linguistic checks on the matching term to see if a variant of the word is there.  I believe there is work going on to look at improving this in the future, but for now you are stuck and the solutions would be things like:

1. regex checks to look for allowable variants with recognised words (not really practical though I know!)
2. add all the variants as separate terms (also not very practical!)
3. consider using something like XBench or Verifika?  I'm not sure how clever these tools are for this but they might be more flexible and could be worth testing at least.

Thanks for the feedback. I do not understand the problems with applying match values to the target - because consistent terminology is critical for good translations, an improvement here would be very desirable. I have tried XBench and CheckTerm, but I personally had problems with them both. I will try Verifika.  

Anthony Rudd

there is nothing to not understand. It just doesn’t do this check and never has. I agree it is absolutely desirable and I am quite surprised we’ve never looked at this before. But we are now.

I now understand.

Verify also seems to have a problem with punctuation characters.