Trados 2019 - English translation of terms not showing

Term recognition is working, but only the source language term is displayed. I have tried selecting everything in the hitlist settings. If I click "View term details" the English translation is there. How do I make it show up??

Parents Reply Children
  • Hi 

    I was going to suggest you try clicking on Reset Window Layout here with the document open for translation/review/sign-off, whichever mode you're having this problem in:

    Trados Studio interface showing the 'Reset Window Layout' option highlighted in the View tab.

    That is still worth trying but it sounds as if your termbase is not connecting to your translation in Studio now.

    Can you still see your terms in MultiTerm? Is MultiTerm the latest version as here?

    SDL MultiTerm version information highlighted, showing version 2019 - 15.0.6.56482.

    Also... it may be that you unticked something in the hitlist settings that only took effect after you closed Studio down.

    So, how do your project settings look here:

    Project settings in Trados Studio with search settings visible, no errors or warnings shown.

    and most important do you have this box ticked here:

    Project settings in Trados Studio with verification settings visible, 'Check for possible source text of the target text' option ticked.

    in your project settings for the translation you're having these problems with.

    If your termbase is corrupt, it is possible to export it and import it into a new termbase but let's look at the above first...

    All the best,

    Ali :)

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 2:19 PM (GMT 0) on 28 Feb 2024]
  • Hi Ali

    Thanks so much for trying to help me, it is hugely appreciated :)

    I have done all of the above checks, and my settings are all as you suggest. All of the terms appear if I load the termbases in Multiterm, and if I click on "View term".

    However, poking around this morning, I have discovered that the problem seems to be, because the project has two termbases. A project-specific one, and a general one that the agency uses.

    In this case, the terms that are being found, are being found in the TB that is NOT the default.

    If I move it up and make it the default, they display.

    So I do at least have terms displaying from one TB. And term recognition is working, so if I see that a term has been recognised in the lower priority TB, I can click on it to view the translation.

    Far from ideal behaviour, though. Any other ideas?

    I have taken some screenshots for you now:

    How the results are appearing in the Term Recognition window

    Screenshot of Trados Studio's Term Recognition window showing a list of German terms without their English translations.

    Clicking "View term" shows that the English translations are available

    Screenshot of Trados Studio's Termbase Viewer window displaying a German term 'Bedienungsanleitung' with its English translation 'operating instructions'.

    And my settings:

    Screenshot of Trados Studio's Project Settings window with Search Settings showing minimum match value and search depth sliders.

    Screenshot of Trados Studio's Hitlist Settings window with options for term recognition display in sequential and parallel mode previews.

    Screenshot of Trados Studio's Verification Settings window with options for term consistency checks and minimum match value settings.

    Screenshot of Trados Studio's Hitlist Settings window with Field Selection for 'flag_gloss_DE-EN' checked.

    Francesca

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 2:06 PM (GMT 0) on 28 Feb 2024]
  • Hi  

    can you check that the languages are all mapped here:

    Screenshot of Trados Studio showing the Termbases section with a default termbase 'FC' mapped to English and Italian in the Project Language section.

    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


    Generated Image Alt-Text
    [edited by: Trados AI at 2:06 PM (GMT 0) on 28 Feb 2024]
  • Hi Paul

    I've checked both termbases, and they are mapped correctly as shown above.

    What is really strange, is that suddenly, I am getting the message "This termbase has been created with an older version of MultiTerm and needs to be updated" message, which just keeps reappearing when I click "Yes" to "Continue opening termbases?".

    I've tried the MultiTerm Convert wizard, but it doesn't find the termbases (as they are not the old version it's designed for).

    So now I can't use the termbases at all.
  • Hi Francesca

    A couple of questions...

    Have you followed Jerzy's advice in one of your other threads and tried the solutions suggested here?:

    Studio Reset etc

    Perform the Windows Repair on MultiTerm 2019 Core and Desktop also. Are the instructions simple enough?

    Second question - does the termbase behave correctly if you're working on the same project in Studio 2017?

    As an aside, I see you translate for the wonderful company I do most of my work for :-)
    I usually blank out anything that gives that away ;-)) 

    Have a wonderful weekend, despite the weather. I'm going to be working but I love my work so that's no hardship!

    All the best,

    Ali [:D]