Hi Christopher Köbel

unfortunately, this is a weakness, and although there might be workarounds using Regex checks, I agree it should work "out-of-the-box". The same topic came up only a few days ago here.

There are suggestions to implement this, but they need more upvotes:

• https://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/when-checking-for-non-usage-of-target-terms-accept-if-one-target-term-is-used
• This idea corresponds exactly to the issue you struggle with: https://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/studio-behaviour-with-forbidden-terms
• And since we are at it, this is also a very useful feature request regarding how forbidden terms are handled: https://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/exclude-forbidden-terms-from-automation-autosuggestfuzzy-repair-etc

I hope you can have a look at these and upvote them.

Daniel

Hi Daniel,

my search-fu this morning seems to have lost me. Sorry then, for opening a slightly superfluous thread.
Thanks for the pointers, I shall see what I can do with regular expressions in the meantime and also have a look at the "ideas" threads you mentioned.

Christopher Köbel

If you have a fairly small number of forbidden terms to check in the fashoin you outlined above, Regex might work for you. If you have a big TB full of terms with allowed and forbidden translations, I think you will find it difficult.

One of the issues is that the built-in term recognition has a degree of fuzziness (for MultiTerm Desktop) or some linguistic AI (MultiTerm Cloud) to recognize variantions of a word (Listeneintrag - die Listeneinträge, des Listeneintrags etc.). This would be hard to do with Regex for a large number of entries. Same for the recognition of words in the target segment.

If you had a dictionary with all valid variations of words or an AI that could produce that, you could probably automate the generation of either a word list or regex rules. Having said this, this should be a built-in functionality.

Don't worry about opening a new thread. The other one was four years old. Time to start afresh.

Daniel

Paul

Could you give us an idea whether this issue might be solved relatively soon? This would influence whether I might invest time in finding a workaround or just wait for it to be solved in the product. Thank you.

Daniel

I'm not sure... Daniel Brockmann might be able to shed more light on that.

Hi there - not relatively soon, but I have bookmarked it for consideration - Loredana Stoia FYI also. Thanks, Daniel