Custom Termbase format does not display terms in Trados Studio Editor due to Windows OS version.

Since Trados Studio 2017, our company has relied on a custom-made termbase format (.mltb, built on SQL) rather than on the traditional (.sdltb, built on old ACCESS DB). Users need to have our termbase plugin installed to see terms from a .mltb file.

Everything has historically worked fine, terms were displayed as normal, up until RWS released Trados 2022 SR2.

If a user has Trados Studio 2022 SR2 or anything newer, and their Windows OS is not English, then the editor term recognition window will not display target terms. Trados Studio 2022 SR1 works fine.

We notice that in the termbase settings we send out, the display languages are localized for English, as our project management team creates our termbases in English.

So our termbases will have settings for example "English (United States) to Polish (Poland)" but it seems that Trados, likely using System.Globalization to get the culture info from the Windows OS is looking for "Angielski (Stany Zjednoczone) na Polski (Polska) " so no terms are found.

We have done much testing to isolate the issues.

-If we send the same project to the same person on the same computer using Polish Windows OS and using our plugin in both Trados 2021 and Trados 2024, the .mltb will display terms for the 2021 version but not the 2024 version

-If we send the same project to the same person using two different computers, one using Trados 2024 on Windows OS in Polish, the other using Windows OS in English in Trados 2024, the English one displays terms, the Polish one does not

We have seen this same behavior for Italian, French, Russian, Spanish, and German so far, the language of the Windows OS itself doesn't seem to matter as long as it is "not English, United States" then it breaks. We even had one user that had their OS in "English (Germany)" and that also was a problem....no terms.

Parents
  • Hello Tyler,

    Thanks a lot for contacting us with this query. I have discussed this with the team internally, especially   and  . Our first question would be if, after Studio 2022 SR2, you adapted your code to the new language handling that was introduced there. You can find more information here - How to update plugins to Trados Studio 2022 SR2. You might well have done this, but just to check if those changes included language related changes. (We did significant refactoring in that release when it comes to language support across our platform; those changes carried on to Studio 2024 and later).

    If you did this fully and it still does not work as expected, we may need a sample custom termbase plus the relevant code snippets to see if we can advise what else would need changing. Perhaps we can start this conversation here, but then also take it offline to email or other methods as required.

    Thanks for your support and patience in this matter, best regards,
    Daniel 

    Daniel Brockmann
    Team Trados @ RWS

Reply
  • Hello Tyler,

    Thanks a lot for contacting us with this query. I have discussed this with the team internally, especially   and  . Our first question would be if, after Studio 2022 SR2, you adapted your code to the new language handling that was introduced there. You can find more information here - How to update plugins to Trados Studio 2022 SR2. You might well have done this, but just to check if those changes included language related changes. (We did significant refactoring in that release when it comes to language support across our platform; those changes carried on to Studio 2024 and later).

    If you did this fully and it still does not work as expected, we may need a sample custom termbase plus the relevant code snippets to see if we can advise what else would need changing. Perhaps we can start this conversation here, but then also take it offline to email or other methods as required.

    Thanks for your support and patience in this matter, best regards,
    Daniel 

    Daniel Brockmann
    Team Trados @ RWS

Children
No Data