Passolo 2022 doesn't display multiple matches when pre-translating with Trados TM

Hi all,

I'm currently testing a migration from Passolo glossaries to a Trados TM and stumbled across a weird behavior. Maybe you can help or confirm the behavior:

When pre-translating a project in Passolo 2022 (22.0.183.0) with a Trados TM connected via the Trados Studio Add-in, I don't get a pop-up for the strings that have multiple translations in the TM. When pre-translating with glossaries, you get a pop-up asking you which translation you want to use or if you want to leave the string untranslated.

Instead, one of the multiple translations is chosen (I assume the newer one) and inserted as a 100% match.

I played around with the Passolo settings, but even if I choose the "If multiple matches are found, don't translate the string" option, one of the duplicates is inserted as a 100% match.

Even if it is not possible to show the duplicate translations during pre-translation with a TM, I would expect the "Multiple translation penalty" in the Trados Studio Add-in settings to avoid a pre-translation.

When searching for fuzzy-matches in the editor for the string with duplicate translations, the penalty works and the two translation variants are shown as 99% matches.

Do you know if this is a bug? Have you encountered the same behavior?

Thanks in advance for any tips on how to avoid pre-translation for strings with duplicate translations. If you want additional context/descriptions, just let me know.

Kind regards,

Thilo

emoji
Parents
  • I have carried out some tests and can confirm the behavior. However, I was also able to reproduce this behavior with much older Passolo versions. Even without debugging the code, I currently assume that this is an intended behavior. 

    When using glossaries or the internal project TM, the option Display all matches is taken into account; when using Trados as an external TM, the situation is different. Here Passolo has to use various Trados Studio SDK functions. For performance reasons, only function calls that return a single translation are used for pre-translating lists or the whole project. Only when interactively looking for fuzzy matches, multiple 100% matches will be displayed.

    Screenshot of Trados Studio showing two 100% match results for the source text '&Save' with translations 'Sichern' and 'Speichern' from the 'Trados Studio: Duplicate Demo' origin.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 6:03 AM (GMT 0) on 5 Mar 2024]
Reply
  • I have carried out some tests and can confirm the behavior. However, I was also able to reproduce this behavior with much older Passolo versions. Even without debugging the code, I currently assume that this is an intended behavior. 

    When using glossaries or the internal project TM, the option Display all matches is taken into account; when using Trados as an external TM, the situation is different. Here Passolo has to use various Trados Studio SDK functions. For performance reasons, only function calls that return a single translation are used for pre-translating lists or the whole project. Only when interactively looking for fuzzy matches, multiple 100% matches will be displayed.

    Screenshot of Trados Studio showing two 100% match results for the source text '&Save' with translations 'Sichern' and 'Speichern' from the 'Trados Studio: Duplicate Demo' origin.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 6:03 AM (GMT 0) on 5 Mar 2024]
Children
No Data