Term Recognition not showing terms found in Termbase Search

Hello!

My issue is simple... the term recognition window is not finding terms that are clearly in the termbase and that can be found if I use the termbase search window. How to solve that?

I'm posting here after talking to the chat support and trying a lot of "solutions", like reorganizing the TB, removing it and adding it again, repairing Trados and Multiterm installation and even reseting windows layout. Nothing helped.

Just for clarification and in case it helps, I'm posting screen shots of my problem.

In the picture below, the highlighted expression in segment 68 is not found in Term Recognition.

Trados Studio screenshot showing segment 68 highlighted with no term recognition results for the expression in the Term Recognition window.

When the expression is copied and pasted in the Termbase Search, it is recognized and found.

Trados Studio screenshot with the Termbase Search window open, displaying the recognized term for the copied expression from segment 68.

Best Regards



Generated Image Alt-Text
[edited by: Trados AI at 12:00 PM (GMT 0) on 29 Feb 2024]
emoji
Parents
  • I have encountered this problem many times with Trados. I solved it by using OmegaT, a free CAT tool.

    It has no problem with large TBs. You have to convert the TB to Excel file by using Glossary Converter and then by using Notepad to a txt file,

    You have to create a project in OmegaT. In the source files folder of the project you copy the Trados bilingual files.

    You copy the notepad termbase file to the glossary folder of the project in OmegaT project folder.

    Then you can work on the files and the term recognition works fine in the glossary window of OmegaT.

    emoji
  • So said to read this, Paraskevas. And unfortunately I think you are right. After one month of not getting any help here, I was also trying to have some support via chat. 

    After two weeks of intense interchange of messages, screen shots, databases etc, the support told me that MAYBE they think this is not a bug or a problem, but what they called "intended design", i.e. The way the program was really designed and the intention is for it to work like this.

    In face of this answer I had to continue using MemoQ. 

    And to finish it with a cherry on the top, when then I told the support that the program lacks a very basic feature and is useless in my point of view despite being very expansive, and therefore I'd like to have a refund, they told me it was not possible because a month has passed (of course, losing time with the support that instead of saying upfront that this was not a bug, kept me asking to do a lot of things and tasks).

    Best Regards 

    emoji
Reply
  • So said to read this, Paraskevas. And unfortunately I think you are right. After one month of not getting any help here, I was also trying to have some support via chat. 

    After two weeks of intense interchange of messages, screen shots, databases etc, the support told me that MAYBE they think this is not a bug or a problem, but what they called "intended design", i.e. The way the program was really designed and the intention is for it to work like this.

    In face of this answer I had to continue using MemoQ. 

    And to finish it with a cherry on the top, when then I told the support that the program lacks a very basic feature and is useless in my point of view despite being very expansive, and therefore I'd like to have a refund, they told me it was not possible because a month has passed (of course, losing time with the support that instead of saying upfront that this was not a bug, kept me asking to do a lot of things and tasks).

    Best Regards 

    emoji
Children