"Probability score": 0.7

"Question improvement suggestion": Please provide more specific examples of the issue you're experiencing, including the source and target languages, and the exact version of Trados Studio you're using. Also, it would be helpful if you could share any error messages you've received, if any.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Anna,

It seems like you're experiencing issues with the Neural Machine Translation (NMT) feature in Trados Studio, particularly with numbers and percentages. This could be due to a variety of factors, including the specific language pair you're working with, the complexity of the text, or even a potential bug in the software.

One potential solution could be to use the TermInjector application from the RWS AppStore. This tool can help you handle numbers and currencies that are not automatically recognized or localized by Trados Studio. You can set up specific rules in TermInjector using regular expressions (regex) to handle different formats of numbers and currencies.

Here's a basic step-by-step guide on how to use TermInjector:

Step 1: Download and install the TermInjector application from the RWS AppStore.

Step 2: Open your project in Trados Studio.

Step 3: Set up a rule in TermInjector using regex to handle the specific number or currency format you're dealing with. For example, you could use a rule like this to handle different currency symbols followed by numbers: ((¥|£|€|$))([0-9,. ]+)

Step 4: Run a Translation Memory lookup for each segment after only translating one segment. The TermInjector should automatically transform the numbers according to your rule and insert them into the Translation Memory match.

Please note that this is a general guide and you might need to adjust the steps based on your specific situation. Also, remember to always back up your work before trying new tools or settings.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

The language pair is Spanish to English, and it's not a problem with most numbers, only percentages within statistical information where it seems to be swapping numbers around.

 Anna Moorby 

It’s probably due to the wrong decimal separator used in Spanish (Spain). If it’s Spanish Mexican it’s right, but the MT engine might not understand it. Which Spanish version are you using? I did a quick text in the free DeepL version availavle at www.DeepL.com and use the wrong decimal separator, and the result was OK. Which MT engine are you using?

I’d pre-process the source file and replace a couple of dot decimal separators (.) with commas (,), and then re-open the prepared document in Trados Studio to check if this time everything was OK. If it’s you know the reason and then you may want to replace all decimal separators before the percentage symbol.

 Anna Moorby 

It’s probably due to the wrong decimal separator used in Spanish (Spain). If it’s Spanish Mexican it’s right, but the MT engine might not understand it. Which Spanish version are you using? I did a quick text in the free DeepL version availavle at www.DeepL.com and use the wrong decimal separator, and the result was OK. Which MT engine are you using?

I’d pre-process the source file and replace a couple of dot decimal separators (.) with commas (,), and then re-open the prepared document in Trados Studio to check if this time everything was OK. If it’s you know the reason and then you may want to replace all decimal separators before the percentage symbol.

Hi there, it's international (Peninsular) Spanish. This doesn't happen with any other numbers, only percentages where there are several numbers within the same sentence which is of a statistical nature. It's absolutely fine converting commas to decimal points with regular numbers and currencies. The MT is just the generic Language Weaver NMT. I never used to have this problem with a previous version of Trados, only with the 2022 version I updated to a few years back. Very strange!

Anna Moorby 

I've tested this with Language Weaver and the culprit is not the decimal separator, but the space before the percentage symbol.

1. In the screenshot below, the 1st segment has a dot as a decimal sperator and a space before % and the MT result is fine.
2. The 2nd segment has the same dot decimal separator, but no space before the percentage symbol. Here Language Weaver goes mad as well.

Using comma as the decimal separator and no space before % gives a different but still wrong result:

The project created was from Spanish (International) to English (UK), Trados Studio 2022, latest build 17.2.12.19268, MT'ed with Language Weaver.

Maybe Paul can tell us something…

BTW, according to international standards, there should be a non-breaking space before symbols, such as the percentage (%). I didn’t know Language Weaver was so picky, when very few people bother to insert that space…

Anna Moorby Jesús Prieto 

Are you using the Language Weaver plugin, or Cloud-based Resources for the Language Weaver MT?  If the plugin can you test with Cloud-based Resources and see if you get the same result... and vice-versa?

Thank you.

Paul   I used Cloud-based Resources.

Now I’ve tried with the plugin in the same project (Cloud-based Resources and old translations removed) and i still get the same thing:

Jesús Prieto 

Thank you... so this looks to be a consistent LW issue.  I'll log it for investigation.

I was using the cloud based resources. I installed the plugin, which caused Trados to crash. I followed the advice on this forum, renaming the plug-in folder and running a repair on Trados, and now the programme won't start at all. I click on it and it seems to be starting up but then it just closes. Help!

OK, had to uninstall and reinstall Trados but it seems to be working ok again now, although the numbers are still all over the place with Language Weaver, but I daren't try the plugin again!