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 

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.

Armando Zarate Krista Yabe Nami Matsumoto LYT LIU 

Thanks for confirming your language pairs.  This would be consistent with the bug reports we have now raised (our references CRQ-37440 and CRQ-37564) as the problem manifests itself with non-western scripts.  It's odd it never came up in any of our testing, including the Beta Testing as it was quite a protracted period, but I guess there's always a time constraint for busy professionals.

Hi Paul,

Actually, I have experienced similar issues with JA-EN termbase many times in the past (since 2019 when I started using Studio), but they were not as serious as the current one.

When Term Recognition stopped working, I just created a new termbase file, deleted a few recent entries in the last termbase file (as I assumed that the last entry or two caused the issue), and used the new and old termbase file(s) together on Studio. That way, I managed to cope with the problem and keep going. This caused me to end up having many termbase files (like "Med", "Med_2", "Med_3"...), but I was not bothered.

In other occasions (which occurred a long time ago like c. 2021-2022), a particular termbase file kept on causing Studio to crash when used in conjunction with certain document files. I was able to cope with it by removing the termbase file. I then created a new termbase file for the document files.

It seems that, as you say, non-Western characters may be the culprits.

Hope this information helps provide some insights.

Regards,

Nami

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,

Any updates on the provision of a new version of Trados and Multiterm with the fixes for the term recognition problem? What ETA are we looking at?

Best regards,

Pavel

Pavel Tsvetkov 

Releasing a fix for anything doesn't happen that quickly I'm afraid.  Things can seem as though they are simple to fix but often they are not as the underlying cause can be related to much wider changes in the product that are not easy to resolve in a day or three.  If you like I can add you to our Beta forum and then you'll receive early notification of any fix since it always goes to public Beta prior to release.  Given CU10 was actually in Beta for quite a while and nobody there picked this up (despite having plenty of users that work with affected languages) in addition to ourselves I'd be  happy to have someone in there keen to test it when it arrives?

Pavel Tsvetkov 

Releasing a fix for anything doesn't happen that quickly I'm afraid.  Things can seem as though they are simple to fix but often they are not as the underlying cause can be related to much wider changes in the product that are not easy to resolve in a day or three.  If you like I can add you to our Beta forum and then you'll receive early notification of any fix since it always goes to public Beta prior to release.  Given CU10 was actually in Beta for quite a while and nobody there picked this up (despite having plenty of users that work with affected languages) in addition to ourselves I'd be  happy to have someone in there keen to test it when it arrives?

I would like to test the Beta version too if possible.

Term recognition has always been buggy in Trados Studio but in the past I could always rely on the step Batch Tasks -> Verify Files at the end of the translation process to catch all the non-use of terminology that slipped through during the translation. In this case, however, Verify Files doesn't recognize terms (longer than two characters) either.

OK, please, add me to the beta team.

Pavel Tsvetkov John Fry 

I have added you, so you'll find this under "My Groups" in the main menu at the top of the page.  Just watch out for the notifications when a Beta is available and the necessary instructions for installation.  Typically you can run these alongside your production version.

I would also like to join Beta testing, if possible.

 Armando Zarate 

Done.