Hi Shaun Murdock,

Please lower the minimum match value from 100 and see if you get results.

Hope it helps!

Regards,

Hi Oana,

Thanks for the suggestion. I tried that but the problem persists.

Shaun

Hi Oana,

Thanks for the suggestion. I tried that but the problem persists.

Shaun

Hi Shaun Murdock,

Shaun Murdock said:

when I click on an individual segment it is populated with the translation result from the MT.

So the Editor has segments populated by MT. Please remove the translated parts or modify them - put them as untranslated, then run the Batch task>pre-translate again.

How does it go?

After removing the translated text from a segment, changing the segment status to "Not Translated" and re-running the Pre-translate batch task, the segment remains untranslated. This time, when I click on the segment, it is NOT populated with the MT result.

Shaun Murdock,

Thank you.

Please remove the MT provider from the Project Settings. Install in alternative the plugin "Language Weaver Cloud" from the integrated AppStore at the top left corner in the software. Add it in Project Settings from the list of the memory providers.

See here the details how to use it please (you should log in with your Studio credentials): https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/3356/language-weaver-cloud-former-sdl-machine-translation-cloud-beglobal 

And run again the pre-translation process.

Let me know if it works alright or else to escalate this further.

Thanks

Many thanks, Oana! That works for me. Do you know what the issue may have been with SDL Language Cloud, and is there any difference between the two MTs?