Language Cloud is considered as a being a translation provider so you should be able to add it to the project as you would add a file based TM. You can find a sample here. I have to say that I didn't try it until now so please let me know if you already tried this and it didn't work.

Also please keep in mind that at the moment there is no mechanism to specify the language cloud credentials other than the dialog window which guides to user to login in language cloud.

Language Cloud is considered as a being a translation provider so you should be able to add it to the project as you would add a file based TM. You can find a sample here. I have to say that I didn't try it until now so please let me know if you already tried this and it didn't work.

Also please keep in mind that at the moment there is no mechanism to specify the language cloud credentials other than the dialog window which guides to user to login in language cloud.

Hi,

thanks, I tried it, but I'm not sure how to construct the URI. I checked it in an existing project and looks like this (Studio 2017) in the project file:

bmslanguagecloud.https: //lc-api.sdl.com/?languagePairEngineMapping=en-US/de-DE:551cede7c846c55e0f6d1899;en-US/fr-FR:551cede7c846c55e0f6d1898;en-US/ja-JP:551cede7c846c55e0f6d189e

(Added a space at https: // to prevent the editor converting it to a link)

where do these guids come from? are these some kind of language pair IDs from the language cloud? How can I access them?

Thanks,
Tamas

The url language pair mapping has the following structure:

URLEncode({Source Language}/{Target Language}:{Language Cloud Language Pair ID};{Source Language}/{Target Language}:{Language Cloud Language Pair ID}; ...)

Now the problem is that this language pair ids are part of the new Adaptive MT engine released with the Studio 2017 and this MT API is not publicly available so this means that there is now way to obtain the ids using the API unless the user has made the configuration upfront. This is different than the LC provider which was available prior to Studio 2017 release. The old version is no longer available with 2017.