Hi All,
A few days ago I updated Trados and Multiterm to the latest verstions: TradosStudio2022SR2_17.2.10.19084 and MultiTermDesktop2022_17.2.3.2795
Now, term recognition inside Trados editor seems to not work with certain termbases but in other projects the same termbases seem to work OK.
Reorganizing the termbase does not seem to produce the desired effect in this case.
I understand that the information is not enough as supplied but any suggestions are welcome.
Best regards,
PTs
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
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
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?
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
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.
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.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I would also like to join Beta testing, if possible.
Done.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
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
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
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.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Paul,
Are there any news on when a fix will become available? More than a month has passed since I flagged the issue.
Best regards,
P.
Translate
