Trados Studio
Trados Live Essential/Live Team/Enterprise
Trados GroupShare
Trados Business Manager
Passolo
MultiTerm
RWS AppStore
Connectors
Beta Groups
Managed Translation
MultiTrans
TMS
WorldServer
Language Weaver
Language Weaver Connectors
Language Weaver Edge
Tridion Docs
Tridion Sites
LiveContent S1000D
XPP
Language Developers
Tridion Docs Developers
Community Help
RWS User Experience
Internal Trados Ideas Community
Mercury
RWS Community Internal Group
RWS Professional Services
RWS Training & Certification
Style Guides
RWS Campus
RWS Enterprise Technology Partners
Trados Approved Trainers
XyUser Group
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion UK Meetup
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Live Team Ideas
Trados Live Essential Ideas
Trados Live Terminology Ideas
Trados Enterprise Ideas
Trados Online Editor Ideas
Trados Business Manager Ideas
MultiTerm Ideas
Passolo Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
TMS Ideas
WorldServer Ideas
LiveContent S1000D Ideas
Contenta S1000D
XPP Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
Introduction
Language Mappings feature is introduced with SDL Machine Translation Cloud provider, version 3.0.3.2 and is compatible with Studio 2019. This feature allows user to configure the engine selection based on the MT Cloud codes (source and target)-> See also MTCloud codes Wiki section
How to use
1. Install SDL Machine Translation Cloud provider plugin.
2. Add the provider to project.
3. Enter credentials (in case the credentials are not auto populated).
4. Go to Language Mappings tab .
5. The available MTCodes and Models will be loaded for the project Language Pairs.
6. Select the prefered Source MTCode , Target MTCode and Model. (If user wants to receive the translation from the MTCloud server based on a dictionary filter, select an available SDL MT Cloud Dictionary, otherwise select "No dictionary".
7. Press Ok.
8. The provider is ready for the translating process.
Validations and Constraints
1. If user doesn't selects the correct Source MTCode / Target MTCode which corresponds to the selected engine, the translation will not be received from the MTCloud server (see below an example of wrong and valid selection).
2. If the project has a single Language Pair which doesn't have engines supported by the MT Cloud server for the selected Source MTCode / Target MTCode , then provider can not be set.
2. If the project has multiple Language Pairs and one of them doesn't have engines supported by the MT Cloud server for the selected MTCode Source and MTCode Target, then for that specific Language Pair, the setup can not be done.
3. Message validation is retrieved also if the user doesn't go to Language Mappings tab and do the engines setup.
4. User can add a MTCode for the specific language using the MT Codes window, following the below steps:
Reset Language Mappings
All the Language Mappings configurations inside the table can be reset to the default value by clicking on the button "Reset Language Mappings to default". This option can be used also when user removes MTCode(s) from the Add-Ins-> MT Code window (the update it will be reflected inside the Language Mappings grid).
MT Cloud Dictionary
Within the MT Cloud dictionary, user can select the avaiable dictionary for its subscription and the language pairs. The MT Cloud dictionary can be selected from the Language Mappings tab.