Hello everybody,

I understand that the frustration in my original post is evident, and I will admit to being frustrated. Ever since Trados Studio 2022 SR1 was released, there have been problems with how terminology is handled inside the editor. Whether it's this, or the "duplicate false positive" issue in another thread, it does not seem that anything is being done about it.

If there is something on my end that might be causing this discrepancy, please let me know things I can check. Things like that are always possible.

But if this is an error in Trados Studio, it's a grave error - something that was working before and got broke. And left unrepaired. The fact is, if you use terminology verification, you may be missing terms without even realizing it. We were just lucky to have caught this.

The only workaround I have to consistently achieve reliable terminology verification is to verify a project in Trados Studio 2021 after translating it in 2022. It's like having to go back to Microsoft Word 2003 to open a .DOC file when you know you shouldn't (and don't) have to.

Still, I am thankful at least that there is a workaround, even though it unnecessarily costs me time and effort. I am politely asking RWS to escalate/elevate this issue because, ultimately, part of my job depends not only on productivity but also on ensuring that terms are translated correctly, and this used to be one of the pillars on which I could always count.

Michael Schroeder 

Thank you for your clear recording which illustrates perfectly the problem. I agree as awful as it sounds, you are right in describing it as unreliable.
You are right in comparing 2021 and 2022 because as of 2022 things related to MultiTerm was shifting and changing.

From the cases being reported however, I want to stress that it seems to impact some users more than others (not that it helps you)
What is helpful to know is that we do have a development item being worked on: CRQ-35141
We have an estimated time line for a fix and it will be within the next couple of months. 

Good to have this post - as others may refer back to it

Lyds 

Michael Schroeder 

Thank you for your clear recording which illustrates perfectly the problem. I agree as awful as it sounds, you are right in describing it as unreliable.
You are right in comparing 2021 and 2022 because as of 2022 things related to MultiTerm was shifting and changing.

From the cases being reported however, I want to stress that it seems to impact some users more than others (not that it helps you)
What is helpful to know is that we do have a development item being worked on: CRQ-35141
We have an estimated time line for a fix and it will be within the next couple of months. 

Good to have this post - as others may refer back to it

Lyds 

Lydia Simplicio 

Thank you for your response; it is definitely nice to know that someone is listening

And also very good to know and makes me feel a whole lot better knowing that the bug might be zapped within just a few months.

Thanks again!

Michael Schroeder No problem as its awful if you feel isolated and its nice to have the Communities to get the info you need. Even better to know we are on a path to a fix