SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
In case you found this wiki page without coming through the plugin, or the appstore, you can find the plugin here:
To use the Amazon Translate Trados Plugin the first thing you must do is create an AWS account. Once you have done that you need to configure your account locally and to do this you need to download and install the AWS CLI (Command Line Interface). You can find more information on how to do this here in the AWS Documentation.
Once you have installed the AWS CLI you can run it by opening a windows command prompt and type in aws configure:
The first time you do this you will be prompted for four pieces of information (this is an example and not anything you should copy and type in!):
All of this information can be found in your own AWS account settings. It's recommended that you use the documentation provided by Amazon to get this information as they have explained in detail how to set this up here. They could also change the process so it's better to go back to AWS if you have any problems.
When you have completed all of this you will see something like the following if you run the aws configure command again:
Once you have set up your Amazon account correctly you can activate the plugin for your project. The steps are as follows:
In your Translation Memory and Automated Translation settings (Project Settings or File -> Options) add the provider by selecting it from here:
Choose AWS auth type and select the authentication method you intend to use.
All of these details need to be added or the plugin will fail to work:
Click on OK and the plugin will be added to your settings. Now you should be able to receive machine translation results from the Amazon Translate service:
This method provides a way to easily maintain different profiles based on a configuration saved locally on your computer. To use this method you simply choose the Local AWS profile option and add the name of your profile in the Locally configured AWS profile field.
In this example we have used a profile called myprofile. The name of the profile can be whatever you wish and you can create as many as you like. But to use this you need to set this up in two files that are stored here:
These files will be created when you install the Command Line Interface and you can add the necessary information manually or by running this command in a command prompt (you would enter the name of your profile, here we used myprofile):
aws configure --profile myprofile
Add the appropriate information when prompted in exactly the same interface as earlier and the configuration files will be updated accordingly. If you wish to do this manually then the content of the config and credentials files would look something like this:
The plugin supports a few other options in a simlar way to those provided by the MT Enhanced plugin that is also available on the SDL AppStore:
Taken from the articles prepared by Patrick Porter in the original MT Enhanced plugin
How to create the necessary xml structure in a text file for batch find/replace lists?
You can use a text editor (e.g. Notepad) to create files containing the necessary xml structure for use as batch find/replace lists.
The plugin will apply these lists to the source text before sending to the machine translation service and/or to the returned translated text, depending on the options configured in the plugin settings form.
The files can be saved with any file extension. They must have the following structure:
The first node is <EditCollection>. It contains a list of <Items>.
The items list contains EditItem elements, each of which has two attributes Enabled and EditItemType.
The acceptable values for Enabled are true or false. If Enabled is “false” the plugin will ignore the pair. This parameter allows you to temporarily disable a find/replace pair without having to delete it from the file.
The acceptable values for EditItemType are plain_text and regular_expression. You can use regular expression matching/replacement by setting the EditItemType to regular_expression. For simple plain text replacements, it is best to set it to plain_text to avoid unexpected behavior or the need to insert any special regular expression escape characters. The plugin uses .NET regular expressions.
Each EditItem has two elements: <FindText> and <ReplaceText>. They represent the text to find and the replacement text, respectively.
If you need to search and replace things like HTML tags, or any other text containing the < and/or > bracket character, the brackets must be ‘escaped’ with < for <, and > for >. Also, the ampersand character (&) must be escaped with & to avoid problems. Escaping single quotes (') and double quotes (") in the text values is not absolutely mandatory, but it is a good idea in order to avoid any unexpected errors. Some XML editor programs will automatically escape these characters for you when saving the file.
After the list of EditItems nodes, the other nodes are closed with the corresponding closing tags: and .
The following is a complete example of the content for a find/replace list file:
Here, there is one plain text pair specifying to find the string “Hello World” and replace it with “Hello world!”. There is also a regular expression pair specifying to find the regular expression “\bhello\b” (a whole-word match for “hello”) and replace it with “Hello!”.
You can copy and paste the example xml into a text file and modify it as needed. Add EditItem blocks for additional pairs and set the attributes and elements accordingly.
Keep in mind:
It's worth noting that Spiros Doikas has created a blog post on how to create the find/replace files using Excel here: https://metafrastis.wordpress.com/2016/05/06/customise-machine-translation-in-sdl-studio/
Tell Me feature
Starting with Studio 2019 version, users are allowed to access the following actions using TellMe feature from Studio: