Hello nGustavo David ,

You will perhaps find this earlier thread useful and the resolution.

community.sdl.com/.../sdl-language-cloud-is-not-supporting-my-language-pair-arabic-english

Hi, Steven, thanks for your reply, but that was the thread whose title gave me the most hope, and still it didn't help at all. It basically says I should add SDL Machine Translation Cloud Provider after the project has been created and I have the editor open, but it does the same, the same message pops us as you can see below. Also, it explains that the reason for this is that the languate pair is different from the ones in my options, which simply is not the case here, as this is my main language pair and I've working with it forever, both using and not using language cloud.

I also tried to use SDL Gateway, but it seems I need to procure a support contract to get proper support by logging a ticket and whatnot. I never knew this was the case for I got free and easy support in the past.

Could this be an issue because I have the 2017 version? Would uninstalling it altogether help at all maybe?

Hello Gustavo David

I have run a few tests on this, so I want to just run through a few basics.

Can you first ensure Studio is completely up-to-date (Help- Check for Updates)

The latest version should be- .54792

For clarification- are you using the-

(1) 'out of the box' SDL Language Cloud Machine Translation

and/or

(2) SDL Machine Translation cloud provider (and if so ,which version number is this please)

The latest version is available here (ensure the old version is removed first)

appstore.sdl.com/.../

Perhaps you could share an image of your specific language pair project settings?

I have run a number of tests on br_pt and pt language flavours as follows

Perhaps its also worth creating a new project with the default template to rule this out as a possible issue.

Please let me know if this works for you.

Its worth noting that support for Studio 2017 will be retired in just a few weeks time, so this might also be a good time to consider upgrading.

SDL Trados Studio 2021 includes the ability to work in the cloud which might be of interest for you

www.sdltrados.com/.../

Hello Gustavo David

I have run a few tests on this, so I want to just run through a few basics.

Can you first ensure Studio is completely up-to-date (Help- Check for Updates)

The latest version should be- .54792

For clarification- are you using the-

(1) 'out of the box' SDL Language Cloud Machine Translation

and/or

(2) SDL Machine Translation cloud provider (and if so ,which version number is this please)

The latest version is available here (ensure the old version is removed first)

appstore.sdl.com/.../

Perhaps you could share an image of your specific language pair project settings?

I have run a number of tests on br_pt and pt language flavours as follows

Perhaps its also worth creating a new project with the default template to rule this out as a possible issue.

Please let me know if this works for you.

Its worth noting that support for Studio 2017 will be retired in just a few weeks time, so this might also be a good time to consider upgrading.

SDL Trados Studio 2021 includes the ability to work in the cloud which might be of interest for you

www.sdltrados.com/.../

Thanks again, Steven.

To answer your questions, my studio version is up to date and I have the latest SDL Machine Translation cloud provider (your number 2) plugin installed, which is what I've been using for ages now and had been working perfectly up until 2 days ago.

I have done as you asked and tried to create a new project, again to no avail. I simply keep getting the same message. Below you'll find the screenshot of my language pair in project settings. Just as a note, it reads exactly as it's been reading for the longest time. You'll also note that the same is happening for all language pairs, given that the problem before was for PTBR - ENG and this one is for ENG - PTBR.

Thank you for suggesting I update my license to the 2021 version. I've already got in touch with the reseller in Brazil and should be completing this transaction in the near future, but, still, what assurance do I have that the same problem won't happen with the 2021 version?