Yes. Create a field in MT termbase called "forbidden". Set it up as a picklist. Then add the term and activate this item.

In Verification settings activate Terminology verification and select this value as forbidden:

Hi Chun-yi, there's an article here that might make it easier to understand.

Hi Chun-yi,

Another tip after setting your termbase with a status field would be to change your termbase hitlist settings in Studio.

You can choose to show the forbidden terms while translating and you can define the font type and colour of your forbidden terms.

Go to termbase hitlist settings from Studio and define the fields to be shown in below window.

Hi Chun-yi,

As Walter says this is imortant because this concept allows a lot of flexibility in how you would like to use forbidden terms. Some tools use a blacklist for terms, but this is really quite restrictive because the terms might be appropriate in one scenario, but not in another.

Using the picklist attributes give you the ability to change the rules for forbidden very easily.  I think once you have this set up you'll find it's not as tricky as you may think right now. And once in place you can add forbidden terms on the fly just as easily as non-forbidden terms.

The field itself doesn't have to be called variant. It can be called whatever you like. I think you are just referring to my example where I used the forbidden term concept to distinguish between US and UK English so you didn't need to have separate termbases. A blacklist would be a lot of work in this scenario, and probably many others.

Hi Chun-yi,

As Walter says this is imortant because this concept allows a lot of flexibility in how you would like to use forbidden terms. Some tools use a blacklist for terms, but this is really quite restrictive because the terms might be appropriate in one scenario, but not in another.

Using the picklist attributes give you the ability to change the rules for forbidden very easily.  I think once you have this set up you'll find it's not as tricky as you may think right now. And once in place you can add forbidden terms on the fly just as easily as non-forbidden terms.

The field itself doesn't have to be called variant. It can be called whatever you like. I think you are just referring to my example where I used the forbidden term concept to distinguish between US and UK English so you didn't need to have separate termbases. A blacklist would be a lot of work in this scenario, and probably many others.