RWS Community
RWS Community
  • Site

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

RWS Training & Certification

To RWS Support

  • User
  • Translate

    Detecting language please wait for.......


    Powered by
  • Search
  • Site
  • Search
  • User
RWS AppStore
  • Product Groups
  • Trados Portfolio
  • RWS AppStore
  • More
  • Cancel
RWS AppStore
Wiki Language Mapping and Dictionary Support
  • Forums
  • Wiki
  • More
  • Cancel
  • New
Show Translation Options

Detecting language please wait for.......


Powered by
Click here to join the RWS AppStore group to be able to participate and post into the forums
  • -RWS AppStore
    • +AdaptiveMT Trainer
    • +Amazon Translate MT provider
    • +Antidote Verifier
    • +Apply Studio Project Template
    • +ApplyTM template
    • +AppNotifications
    • +AutoHotKey Manager (AHK)
    • ChangeLog: InSource
    • +CleanUp Tasks
    • +Community Advanced Display Filter
    • +DeepL Translation Provider
    • +DSI Viewer
    • +Excel Terminology Provider / TermExcelerator
    • +Excel4GroupShare
    • +Trados Studio – Export Analysis Reports
    • +Export To Excel
    • +Fail Safe Task
    • +Google API Validator
    • GroupShare Kit
    • +GroupShare Version Fetch - Authentication options
    • +Hunspell Dictionary Manager
    • +IATE Real-Time Terminology
    • +IRIS PDF OCR Support for Studio
    • +Lingotek TMS plugin for Trados Studio
    • +MEMSOURCE CloudTM Provider
    • +MT Comparison
    • +MT Enhanced Plugin for Trados Studio
    • +MXLIFF File Type Support
    • +PA Admin
    • +Post-Edit Compare
    • +projectTermExtract
    • +Qualitivity
    • +Rapid Add Term
    • +RecordSource TU
    • +Reports Viewer Plus
    • +Trados Data Protection Suite
    • +Trados Freshstart
    • +Trados LegIt!
    • -Language Weaver (former SDL Machine Translation Cloud/ BeGlobal)
      • Changelog - SDL MT Cloud Provider
      • +Language Mapping
      • -Previous Release
        • Language Mapping and Dictionary Support
      • Rating Translations
      • Troubleshooting & known issues
    • +Language Weaver Edge Provider (former SDL ETS)
    • SDL MultiTerm Extract
    • +MultiTrans Plug-in for Trados Studio
    • +Trados Studio InQuote
    • +Trados T-Window for Clipboard
    • +Trados TMBackup
    • +Trados Studio Word Cloud
    • +Trados TTS
    • +SDLTM Import Plus
    • +SDLXLIFF Convertor for MS Office
    • +SDLXLIFF Split / Merge
    • +SDLXLIFF to Legacy Converter
    • +SDLXLIFF Toolkit
    • Signoff Verify Settings
    • +Star Transit (TransitPackage Handler)
    • +Studio Migration Utility
    • +Studio Subtitling
    • +studioViews
    • +Stylesheet Preview
    • +Target Renamer
    • +Trados Copy Tags
    • +Target Word Count
    • +TM Lifting (ReIndex Translation Memories)
    • +TM Optimizer
    • +Trados Analyse
    • +Trados Batch Anonymizer
    • +Trados InSource!
    • +Trados Number Verifier
    • +Trados Transcreate
    • +Wordlight
    • +WorldServer Compatibility Pack for Trados Studio
    • +XLIFF Manager for SDL Trados Studio
    • +XML Reader
    • +#YourProductivity
    • +File Type Definition for Wordfast TXML
    • +File Type for TMX
    • +Jobs
    • +MSWord Grammar Checker
    • +Multilingual Excel Filetype
    • +Multilingual XML FileType
    • +OpenX Hash Generator
    • +RWS Community Inside
    • +SDL Trados Compatibility and Migration Power Pack
    • +SDLTM Repair
    • +SDLXLIFF Compare
    • +Segment Status Switcher
    • +Studio Time Tracker
    • +TermInjector
    • +Trados 2007 Translation Memory Plug-in
    • +Trados QuickInfo
    • +Trados Translation Memory Management Utility
    • +TuToTm
    • +Variables Manager for Trados Studio

Language Mapping and Dictionary Support

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

  • Source MTCode  - represents the available MT Codes (main and locale) for the project source language (the avaialble MT Codes can be seen also by accessing the Add-Ins -> MT Cloud Codes window
  • Target MTCode - represents the available MT Codes (main and locale) for the project target language (the avaialble MT Codes can be seen also by accessing the Add-Ins -> MT Cloud Codes window

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:

  • Go to Add-Ins and click on "MT Cloud Codes" button.
  • Search for needed language.
  • Write the MTCode(main)/ MTCode (locale) for which the engine should be retrieved from MTCloud server.
  • Close the "MT Cloud Codes" window.

  • Go back to SDL Machine Translation Cloud provider settings.
  • Select "Language Mappings" tab.
  • If the model(s) (engines) exists for the new added code, it will be received from the MT Cloud server (see below).

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.

  • The selected dictionary is used to receive the translation from the MTCloud server.
  • In case no dictionary is available, the translations are received without using any dictionary filter.
  • When "No dictionary" option is selected, the text is send to MT Cloud server without any dictionary filter.

  • Share
  • History
  • More
  • Cancel
Related
Recommended
  • Our Terms of Use
  • Copyright
  • Privacy
  • Security
  • Anti-slavery Statement
  • Cookie Notice
  • YouTube