Hi there - just as an update, we are currently working to enable this in Trados Studio (in the Trados Team context) for the next cumulative update. So far, Studio was not able to use a translation engine with non-matching language pairs in the cloud TM, for instance. This will be resolved with the next update. So you will be able to, say, use a cloud translation engine with English US - German TMs in English UK to German projects, for example. This should work both in local Studio projects using cloud resources, as well as for cloud projects flowing through Studio, where you will be able to then add such non-matching resources to those projects from Studio. This will initially be a Studio-centric implementation. The cloud platform, and with it Online Editor, will come at a future point in time, as the changes there are more extensive than adapting Studio for this scenario. Thanks, Daniel

Hi there - just as an update, we are currently working to enable this in Trados Studio (in the Trados Team context) for the next cumulative update. So far, Studio was not able to use a translation engine with non-matching language pairs in the cloud TM, for instance. This will be resolved with the next update. So you will be able to, say, use a cloud translation engine with English US - German TMs in English UK to German projects, for example. This should work both in local Studio projects using cloud resources, as well as for cloud projects flowing through Studio, where you will be able to then add such non-matching resources to those projects from Studio. This will initially be a Studio-centric implementation. The cloud platform, and with it Online Editor, will come at a future point in time, as the changes there are more extensive than adapting Studio for this scenario. Thanks, Daniel