Me too. I upgraded to the latest MultiTerm and Studio and now term recognition does not work at all. I can add a new term and find it under "Termbase Search" but nothing shows up under "Term Recognition".

Hi John,

Ditto - I can find terms under Termbase Search on Studio, but Term Recognition is not working. I created a new termbase file and tested it out on Studio, but nothing changed. Changing settings for term recognition did not work either.

It is a pain, undermining my productivity...

Regards,

Nami 

The only thing I can add is that for old projects (created before the update) term recognition still works for the same termbases but in projects created after the update term recognition only works for two-letter terms.

I hope RWS can offer a solution soon.

Pavel Tsvetkov Nami Matsumoto John Fry LYT LIU 

I spoke to our technical support team this morning to see if they were aware of any reported problems with term recognition and/or verification.  So far they have not got any reports which leads me to believe this isn't a widescale problem with the upgrade in general.  Having said that this doesn't mean you don't have a problem we need to try and get to the bottom of.

So, a good start would be for me to be able to reproduce this issue myself.  Do you have a project that you are able to share that will allow me to try?

In the meantime, what happens if you recreate the offending projects?  Do they work if you set them up again?  I don't have a solid reason for asking this, but since there has been some substantial changes in recent releases under the hood related to how we work with terminology I think it's worth checking... and when you do this don't use old project templates.  Better to create the project again using the default to make sure nothing old gets into the mix to help with troubleshooting the problem.

Pavel Tsvetkov Nami Matsumoto John Fry LYT LIU 

I spoke to our technical support team this morning to see if they were aware of any reported problems with term recognition and/or verification.  So far they have not got any reports which leads me to believe this isn't a widescale problem with the upgrade in general.  Having said that this doesn't mean you don't have a problem we need to try and get to the bottom of.

So, a good start would be for me to be able to reproduce this issue myself.  Do you have a project that you are able to share that will allow me to try?

In the meantime, what happens if you recreate the offending projects?  Do they work if you set them up again?  I don't have a solid reason for asking this, but since there has been some substantial changes in recent releases under the hood related to how we work with terminology I think it's worth checking... and when you do this don't use old project templates.  Better to create the project again using the default to make sure nothing old gets into the mix to help with troubleshooting the problem.

In the meantime, Paul, how can the current version be downgraded to the previous one? Or is a fix coming soon (today)?

Pavel Tsvetkov 

Given the impact of this bug downgrading to CU9 is your best bet.  There will not be a fix today!  The bugs we have logged for this, to make it easier to follow up, are our references CRQ-37440 and CRQ-37564.

To downgrade you should uninstall both Trados Studio and MultiTerm from the windows control panel, and I would also delete the settings.  To do this, after uninstalling close Trados Studio and then rename this folder:

c:\Users\%username%\AppData\Roaming\Trados\Trados Studio\Studio17\

to c:\Users\%username%\AppData\Roaming\Trados\Trados Studio\Studio17_old\

To install the previous versions download from this KB:

https://gateway.sdl.com/apex/communityknowledge?articleName=000012378

Trados Studio SR2 CU9: https://downloadcentercdn.sdl.com/TP/Trados/T2022/Studio/CUs/SR2_CU9/TradosStudio2022_SR2_CU9_18688.zip

MultiTerm SR2 CU2: https://downloadcentercdn.sdl.com/TP/Trados/T2022/MultiTerm/SR2/MultiTermDesktop2022SR2_17.2.2.2737.exe

If you have any problems let us know.

Hi Paul

Windows Security reports the following about the Multiterm exe file that you have linked in your message:

This could of course be a false positive but just so you know.

Pavel

退回上个版本术语库的确可以正常识别了。

I have downgraded Trados Studio and MultiTerm and worked well!

Before uninstallation, I thought I have to setup connections to my projects and files again after installation, however, the connections remain.

Thank you, Paul and Pavel!

Just passing by to say that after downgrading everything seems to be working well.

Also before downgrading I tested other languages termbases (English-Spanish) and worked fine, so I guess it has something to do with Asian languages.

Hi Paul,

1. I have successfully downgraded to the previous versions of Studio and Multiterm.

2. Everything works correctly now.

3. That said, I can still see that the faulty update is offered:

Knowing how many languages are affected and how much time translators in those languages will waste trying to figure out why term recognition has stopped working (trying to fix and/or recreate termbases, etc.), I wonder why the faulty update is still offered.

Best regards,

Pavel

Pavel Tsvetkov 

Pavel Tsvetkov said:

I wonder why the faulty update is still offered.

Like everything context is important.  This problem is most likely outweighed by all the things that were fixed that many customers were waiting for.  Whilst this one is definitely a problem that has a critical priority to fix I can tell you we are not overwhelmed with users complaining.  If we removed it we most likely would.

Downgrading helped me too.
In the affected Russian-Czech termbase (or rather language combination, as the problem was reproduced in a new termbase), only terms written entirely in Latin letters in both languages were recognized, while term recognition in my Czech-Belarusian termbase functioned well in old and new projects.

Thank you Paul for this step by step explanation! I was able to fix the same problem. My language pair is English USA to French Canada.