Hello Ed,

It seems like you're experiencing an issue with the F8 quality check in Trados Studio not flagging incorrect terms. This could be due to a few reasons. Here are some steps you can take to troubleshoot this issue:

Step 1: Check the language settings in your termbase. If the source term is added for a different sub-language than the one used in your project, it might not be recognized. For example, if the term is added for English UK, but your source language is English US, the term might not be flagged.

Step 2: Make sure the term is not set as forbidden in the target language. If it is, it might not be flagged as incorrect.

Step 3: If the above steps don't resolve the issue, you might want to consider creating a termbase without sub-languages. This can help avoid issues with terms not being recognized due to differences in sub-languages.

Remember, these are just suggestions and the actual solution might vary depending on the specific settings and conditions of your project. If the problem persists, you might want to consider reaching out to the client to clarify the project settings.

I hope this helps! Let me know if you have any other questions.

Best regards,

RWS Community AI

Hello Ed,

It seems like you're experiencing an issue with the F8 quality check in Trados Studio not flagging incorrect terms. This could be due to a few reasons. Here are some steps you can take to troubleshoot this issue:

Step 1: Check the language settings in your termbase. If the source term is added for a different sub-language than the one used in your project, it might not be recognized. For example, if the term is added for English UK, but your source language is English US, the term might not be flagged.

Step 2: Make sure the term is not set as forbidden in the target language. If it is, it might not be flagged as incorrect.

Step 3: If the above steps don't resolve the issue, you might want to consider creating a termbase without sub-languages. This can help avoid issues with terms not being recognized due to differences in sub-languages.

Remember, these are just suggestions and the actual solution might vary depending on the specific settings and conditions of your project. If the problem persists, you might want to consider reaching out to the client to clarify the project settings.

I hope this helps! Let me know if you have any other questions.

Best regards,

RWS Community AI

The term is recognised during translation but not during F8. The issue clearly lies with how F8 finds terms.

Hi Edward Bradburn 

Please see this post here:Terminology verification in Trados Studio 2022 is unreliable

And see if you feel you are having the same ill fate of terminology verification basically being unreliable?
If yes, then please take note we plan to schedule a fix in the next few months.

Lyds 

Hi Lydia,

Many thanks for getting back to me on this.

I can confirm the EXACT same behaviour as for Michael.

The only reason my issue is phrased differently is because I do not use Trados for editing but for QA (which is now ofc a little pointless) and therefore I was not aware that the issue occurs during editing as well.

I have just checked things using the same client file and can confirm that:

• Term matches in source language are ALWAYS found (in the search box)
• Term matches in source language are NOT CONSISTENTLY flagged if they are incorrect in the target language

As I was only using the term flagging as part of the F8 QA check, I only noticed this problem at that point. If I had been editing, I would have noticed this before.

I am using the very latest patched TRADOS (Trados Studio 2022 SR2 - 17.2.9.18688), so this is not an old version issue.

Indeed, as Michael says, it's a new version issue.

Great to hear a fix is coming!

Thx

Ed