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.

I have the same problem, but the project where term recognition does not work was created before the update.

 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.

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.

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