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 

 Nami Matsumoto John Fry Natalja Jampílková Pavel Tsvetkov 

Pavel sent me a project to test and I was able to reproduce this on his project.  I could also reproduce it on a new termbase I created with just two entries, and also a file with just a few sentences.  So no need to send me anything more.

I would be interested to know what language pairs you are translating with though?

Thank you for getting back to us, Paul.

I work on Japanese - English (both directions).

Pavel Pavel  Thank you for sending Paul a test project file.

Regards,

Nami

I am experiencing the exact same issue, working with Japanese to English, and it is consistent across multiple computers (two with UK English Windows, and the other with Japanese). I have also spoken to several other people who are having the issue, and know of two different companies who have apparently reported the issue (and stopped updating or rolled back to the previous version for the time being based on advice they received). So it surprises me to see that IT hadn't heard about it! 

It is heartening to see that it is being looked into now. Hopefully there will be a fix soon.

日语->简体中文

I am experiencing exactly the same issue. Currently working around with using cloud-based term base by uploading the unrecognized local term bases, however, there is another issue... Recognized terms are not updated when I add a new term to the cloud-based term base.

Thank you very much Paul and technical support team for your hard work on solving this issue.

I have the same issue and as I see the responses it might have to do with Asian languages, my pairs are Chinese to Spanish. These couple of days have been driving me crazy haha. If it helps anyone I had to use the online editor, even though I don't like it much but I was able to get the terms. I'm planning to check other pairs like English to Spanish and see what happens.

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,

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