Hello Pascal,

To ensure certain words are treated as non-translatable, use the Brands or Dictionary features in Language Weaver.

Brands

1. In Language Weaver, navigate to Settings > Brands.

2. Add your non-translatable terms to the Brands list.

Terms added here are automatically recognized as non-translatable across all language directions. The Brands list is applied to translations in the LW portal and in other integrated applications such as Trados Studio. 

Dictionary

If you need to treat certain terms as non-translatable in some languages while allowing translations in others, use the Dictionary feature instead.

1. In Language Weaver, go to Settings > Dictionary. 

2. Create a dictionary for the language direction where the terms should be treated as non-translatable.

3. Add the non-translatable terms to the dictionary, ensuring the translation matches the source term.  

Please note that the Brands list is always "on", whereas the Dictionary feature can be activated or deactivated as needed.

For more information about the Brands and Dictionary features, please refer to the Language Weaver Documentation. 

Best regards,

Lenka

Hello Lenka,

As I said, unfortunately that’s not an option as the terms are in a tool of our own (some kind of term injector) and lists are not available for export. We have to flag terms on the fly before we forward them to any MT tool.

And the question also stated to flag them before they are sent to LW.

Edit: Is there some kind of strings LW will not touch at all, e.g. terms with underscores or alphanumeric strings? That way we could convert terms from our list into such strings.

I might have found a solution under Brands in LW: you can use Regex there, so we can alter the text on our side to match a single Regex rule in order to make LW ignore these strings.

Hello Pascal,

yes, this is what I was going to suggest after reading your response. I did a test that worked but my Regex needed further improvement. Using Regex will require testing and finetuning, and possibly an additional step to remove the text alteration on the translation side. 

Best regards,

Lenka 

Hello Lenka,

The removal step before using the strings before they are forwarded to Trados or whatever tool is no problem at all as it would be the same rule we already use for internal DNT strings flagging and later removing of the flags. Our tool is fully regex based and contains way trickier regex rules than this one. We even had to expand regex handling for our tool as it misses some basic (for our need) features and we have more additions to be added. ^^

I’m pretty sure, my programmer hates me for always pushing everything to the limits so he has to do some reworking of the programming. O:)

Best regards,

Pascal

Hello Lenka,

The removal step before using the strings before they are forwarded to Trados or whatever tool is no problem at all as it would be the same rule we already use for internal DNT strings flagging and later removing of the flags. Our tool is fully regex based and contains way trickier regex rules than this one. We even had to expand regex handling for our tool as it misses some basic (for our need) features and we have more additions to be added. ^^

I’m pretty sure, my programmer hates me for always pushing everything to the limits so he has to do some reworking of the programming. O:)

Best regards,

Pascal