Microsoft Machine Translation Provider for RWS Language Cloud
By Trados AppStore Team
Free
Description
This add-on enables users working in the cloud (through Trados Studio, Trados Team or Trados Enterprise) to receive machine translation results from the Microsoft Translator - https://www.microsoft.com/en-us/translator/.
You can directly install the Microsoft Translator Machine Translation Provider from within your cloud account. Simply select your account icon in the top right hand corner of the screen> RWS AppStore.
Please note: You will need to purchase a subscription to the Microsoft Translator and you'll need an API key to use the add-on which you can obtain through Microsoft sales. Pricing for the Microsoft Translator service is available through this Microsoft website.
Technical details
1.0.12 - Trados Studio cloud capabilities, Trados Accelerate, Trados Team, Trados Enterprise
Support website: https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore
Shared products:
No related information.
Requirements
1. An Azure Subscription with an active Resource Translator Service Plan.
See Microsoft Documentation for further information
2. For custom models, then you require a number of prerequisites.
See Microsoft Documentation for further information
Installing Microsoft Machine Translation Provider AddOn
It can be installed in 2 ways:
1. Within your Language Cloud tenant.
Access your account settings and from the drop down menu, select RWS AppStore. From the AddOn’s listed select Microsoft Machine Translation Provider to install.
2. Alternatively you can install it via the RWS AppStore
Configuring Microsoft Machine Translation Provider
1.Subscription Key
This is a mandatory field. It requires your Named Translator Resource API key. This can be found by looking at all your Named Translator Resources >- Manage Keys
2.EndPoint
This is an optional field. EndPoint would be the URL that translation requests are sent to. Default value is preset.
3.Subscription Region
This is the location of the Translator Resource. Default value is set to Global. Can be confirmed via: Resource (Type Translator) > Resource Management > Keys & Endpoint within your Azure Portal
4.Category
This is an optional field. This parameter is used to support customised translations. Default value is set to general. The Category field can be reconfirmed by accessing your Azure Workspace
5.Allow Fallback
This is an optional field. Specified that the serice is allowed to fall back to a general system when a custom system does not exist. Possible values are: true or false. Default set to true
6.Overriding Settings
The only required field is the Subscription Key field. Endpoint, Subscription Region, category, and Allow Fallback are all optional values, and determine details of how Microsoft Machine Translation Provider will perform your translation. The Overriding Settings value allows you to specify different values for all the above settings, depending on the language pair being translated. This is managed by entering a JSON Strings. See See **Override JASON examples below.**
7.Custom Model Settings
This is required when using custom models. You need to specify the resources' names associated with the custom translators. This can be found by looking at all your Named Translator Resources. This is implemented by entering a JSON Strings as seen below.
[
{
"ResourceName":"NAME",
"SubscriptionKey":"SUBSCRIPTION_KEY"
}
]
If the subscription key you want to use is not different from the default one, you don't need to specify it. As a result the JSON String would be:
[
{
"ResourceName":"NAME"
}
]
After successfully authentication and configuring your Microsoft Translator AddOn, the list of custom models will be displayed when adding a machine translation model against the language pairs supported.
**Override JASON examples below. **
This is controlled by entering a json string in the following format. In this example only the language pairs (e.g. en>zh-CN) and the EXAMPLE fields would need to be updated according to your needs.
{
"OverridingSettings": [
{
"ValueProvider": "LanguagePairValueProvider",
"ValueProviderVariable": "Unused",
"Matches": [
{
"MatchValue": "en>zh-CN",
"Settings": [
{
"SettingName": "SUBSCRIPTION_KEY",
"SettingValue": "EXAMPLE"
},
{
"SettingName": "ENDPOINT",
"SettingValue": "EXAMPLE"
},
{
"SettingName": "SUBSCRIPTION_REGION",
"SettingValue": "EXAMPLE"
},
{
"SettingName": "CATEGORY",
"SettingValue": "EXAMPLE"
},
{
"SettingName": "ALLOW_FALLBACK",
"SettingValue": "EXAMPLE"
}
]
},
{
"MatchValue": "en>ro",
"Settings": [
{
"SettingName": "SUBSCRIPTION_KEY",
"SettingValue": "EXAMPLE"
},
{
"SettingName": "ENDPOINT",
"SettingValue": "EXAMPLE"
},
{
"SettingName": "SUBSCRIPTION_REGION",
"SettingValue": "EXAMPLE"
},
{
"SettingName": "CATEGORY",
"SettingValue": "EXAMPLE"
},
{
"SettingName": "ALLOW_FALLBACK",
"SettingValue": "EXAMPLE"
}
]
}
]
}
// NOTE: Not yet implemented, do not use
//,
//{
// "ValueProvider": "ProjectCustomFieldValueProvider",
// "ValueProviderVariable": "MT Flavour to use",
// "Matches": [
// {
// "MatchValue": "technical",
// "Settings": [
// {
// "SettingName": "CATEGORY",
// "SettingValue": "MyTechnicalCategory"
// }
// ]
// }
// ]
//}
]
}
The number of languages specified and the configuration fields they override can be changed, so that only relevant fields are specified, for example:
{
"OverridingSettings": [
{
"ValueProvider": "LanguagePairValueProvider",
"ValueProviderVariable": "Unused",
"Matches": [
{
"MatchValue": "en>zh-CN",
"Settings": [
{
"SettingName": "SUBSCRIPTION_REGION",
"SettingValue": "Asia"
}
]
}
]
}
]
}
