TERM RECOGNITION STILL NOT WORKING

We've had problems for months with the term recognition in Trados Studio. We upgraded to the newest version recently and honestly thought there would be an improvement, but if anything, it's worse.

Here is some info/context:

  • We are a small team of three people
  • We have recently upgraded our three licences to the 2024 SR1 version (Trados and Multiterm).
  • Our termbase is file-based, not on a cloud.
  • We do not share our termbase (each one of us has a local copy).
  • Our language pair is English CA -> French CA.
  • The project and file type have no impact (the problem persists when we try various scenarios).

Currently, one user has no problem, while the other two are getting results ONLY for two-letter terms in the term recognition window. The term search feature always works, though.

Please help! With the amount of money thrown into this software, this is getting frustrating.

Trados Studio options window showing term recognition settings, including sliders for analogy percentage, search length, and term repetition threshold.



Generated Image Alt-Text
[edited by: RWS Community AI at 4:27 PM (GMT 1) on 8 Oct 2025]
emoji
Parents Reply Children
  •  

    So the solution might just be to have the English word "termbase" in the termbase folder?

    I hope not... I just used that name through a lack of imagination!

    I am thinking that the paths, or the termbase name are at play here though.  The package placed the termbase within the project itself and you probably have your termbases outside of that... although when you shared your paths they were inconsistent and not where I initially thought the problem might lie.  I was thinking accented chars, cloud drives etc.  Whilst you did have a couple of accents it wasn't consistent and the accented ones worked!

    So very odd... but if you found a solution that would be the main thing!

    Paul Filkin | RWS Group

    ________________________
    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

    emoji