DeepL Translation Provider

By Trados AppStore Team

Free

Description

This plugin provides machine translation results from the DeepL Translator found here - https://www.deepl.com/translator.

You will need to purchase a subscription to DeepL Pro and you'll need an API key to use the plugin which you can obtain through DeepL sales.

Pricing for the DeepL service is available through this DeepL website.

Technical details

6.1.3.2 - Trados Studio 2022 (SR1+)

6.0.3.1 - Trados Studio 2022

5.8.28.0 - Trados Studio 2021

4.8.24.0 - SDL Trados Studio 2019

3.8.12.0 - SDL Trados Studio 2017

DeepL MT Provider is an application which retrieves translation results using the DeepL Translation Service. DeepL API is a paid service and you need an API Key to use the translation provider for Trados Studio or Language Cloud. To obtain an API Key from DeepL please visit their website - https://www.deepl.com/pro?cta=header-prices

Also note that glossary support is only available with the DeepL plugin for Trados Studio 2022 and later.

Subscriptions Supporting CAT Tool Integration

Supported: DeepL Advanced and Ultimate subscriptions.

Not Supported: Other subscription types, including DeepL Translator, Starter, DeepL API Free, DeepL API Pro, and DeepL API for Business.

Glossaries in DeepL: Understanding the Distinction

When working with DeepL, it's essential to understand the difference between glossaries created via the DeepL API through a CAT tool integration, and those created directly via the DeepL website or DeepL apps.

Glossaries Created via the DeepL API

Accessibility: These glossaries are only accessible through the specific application, tool, or plugin that created them, such as the DeepL plugin for Trados Studio.

Integration: They are not integrated with or synchronized to the glossaries created through the DeepL website or DeepL apps.

Management: Creation, deletion, and other management must be handled through the API or the specific tool that uses the API. Note that direct editing is not possible; changes require complete deletion of the glossary and recreation.

Glossaries Created via the DeepL Website and Apps

Accessibility: These glossaries are accessible through the DeepL website and DeepL's native apps.

Integration: They are not integrated with or synchronized to the glossaries created via the DeepL API.

Management: Creation, deletion, and other management must be handled through the DeepL website or apps.

Practical Implications

Separation of Resources: Be aware that glossaries created in one context (API or website/apps) are not accessible in the other.

Potential for Confusion: Users expecting a unified experience will need to understand that these glossaries are distinct and independent.

Current Recommendations from DeepL

Taken from this website: https://www.deepl.com/docs-api/glossaries/list-glossary-languages

Glossaries created via the DeepL API are distinct from glossaries created via the DeepL website and DeepL apps. This means API glossaries cannot be used on the website and vice versa.

Note that glossaries are immutable: once created, the glossary entries for a given glossary ID cannot be modified.

As a workaround for effectively editable glossaries, we suggest to identify glossaries by name instead of ID in your application and then use the following procedure for modifications:

download and store the current glossary's entries,
locally modify the glossary entries,
delete the existing glossary,
create a new glossary with the same name.

DeepL API Glossary Feature Support

Glossary Support is now offered via a dropdown based on supported language pair. To access it click on "Manage glossaries" from the settings page:

This will take you to a view where you can start working with glossaries:

The following features are supported

Add new glossary (Alt+A): When creating a glossary, you have an empty database whereby you can manually add new entriesImport glossaries (Alt+Q): Use this feature when managing glossaries between platforms. By default the name of your glossary will match the name of your imported file, but this can be changed using the edit featureExport selected glossaries (Alt+X): Supported formats being *.TSV & *.CSVImport entries into selected glossaries (Alt+D): This supports the import of a file into existing glossariesDelete selected glossaries (Delete): this will delete your selected glossariesEdit glossary (Alt+E): opens a view to edit the selected glossary

Once your glossary has been created, you can't change the name of your glossary. However you can edit term entries

When editing your glossary the following features are supported:

Delete entry
Add entry
Import into Glossary
Edit entry

Glossary Restrictions

Import file format: The format of the import can either be *.TSV & *.CSV (delimited by either a semi colon or comma). The placement of source / target terms within your file, should directly correlate with the supported language direction defined during importCommon Restrictions for All Glossary Formats

Duplicate source entries are not allowed
Neither source nor target entry may be empty
Source and target entries must not contain any C0 or C1 control characters (including, e.g., "\t" or "\n") or any Unicode newline

Limits imposed: You can create up to 1,000 glossaries. Please keep in mind that the maximum size limit for a glossary is 10 MB and each source/target text as well as the name of the glossary is limited to 1024 UTF-8 bytes.Editing existing DeepL API Glossaries is not supported by DeepL. You can implement the edit functionality yourself by creating a new glossary with the modified entries and deleting the old glossary.Language Support: Not all languages supported by the plugin for translation have glossary support. If you have a problem please make sure you check the supported languages here: https://www.deepl.com/docs-api/glossaries

How the plugin works

After the plugin has been installed you can access it in Studio by going to your Project Settings -> All Language Pairs->Translation Memory and Automated Translation and then click on the Use... button to expand the options:

A new window will appear where you can introduce your API Key . The API Key text box is a required field, so if you don't fill it and click OK the window will not close and instead an warning message will appear. It's also worth noting that if you cannot close the window after adding your key it may help to add a space to the end of the key and then delete it. That should activate the OK button:

To close the window use "Cancel" button or "X" from the top right of the window

Troubleshooting:

Sometimes errors can be reported when trying to get a translation result from DeepL. This may be related to firewall restrictions which can be resolved by whitelisting the following domains:

www2.deepl.com

api.deepl.com

For more details on this you may find this link helpful:

https://gateway.sdl.com/apex/communityknowledge?articleName=000013232

Also note that glossary support is only available with the DeepL plugin for Trados Studio 2022 and later.

Subscriptions Supporting CAT Tool Integration

Supported: DeepL Advanced and Ultimate subscriptions.

Not Supported: Other subscription types, including DeepL Translator, Starter, DeepL API Free, DeepL API Pro, and DeepL API for Business.

Glossaries in DeepL: Understanding the Distinction

Glossaries Created via the DeepL API

Accessibility: These glossaries are only accessible through the specific application, tool, or plugin that created them, such as the DeepL plugin for Trados Studio.

Integration: They are not integrated with or synchronized to the glossaries created through the DeepL website or DeepL apps.

Glossaries Created via the DeepL Website and Apps

Accessibility: These glossaries are accessible through the DeepL website and DeepL's native apps.

Integration: They are not integrated with or synchronized to the glossaries created via the DeepL API.

Management: Creation, deletion, and other management must be handled through the DeepL website or apps.

Practical Implications

Separation of Resources: Be aware that glossaries created in one context (API or website/apps) are not accessible in the other.

Potential for Confusion: Users expecting a unified experience will need to understand that these glossaries are distinct and independent.

Current Recommendations from DeepL

Taken from this website: https://www.deepl.com/docs-api/glossaries/list-glossary-languages

Glossaries created via the DeepL API are distinct from glossaries created via the DeepL website and DeepL apps. This means API glossaries cannot be used on the website and vice versa.

Note that glossaries are immutable: once created, the glossary entries for a given glossary ID cannot be modified.

As a workaround for effectively editable glossaries, we suggest to identify glossaries by name instead of ID in your application and then use the following procedure for modifications:

download and store the current glossary's entries,
locally modify the glossary entries,
delete the existing glossary,
create a new glossary with the same name.

DeepL API Glossary Feature Support

Glossary Support is now offered via a dropdown based on supported language pair. To access it click on "Manage glossaries" from the settings page:

This will take you to a view where you can start working with glossaries:

The following features are supported

Add new glossary (Alt+A): When creating a glossary, you have an empty database whereby you can manually add new entriesImport glossaries (Alt+Q): Use this feature when managing glossaries between platforms. By default the name of your glossary will match the name of your imported file, but this can be changed using the edit featureExport selected glossaries (Alt+X): Supported formats being *.TSV & *.CSVImport entries into selected glossaries (Alt+D): This supports the import of a file into existing glossariesDelete selected glossaries (Delete): this will delete your selected glossariesEdit glossary (Alt+E): opens a view to edit the selected glossary

Once your glossary has been created, you can't change the name of your glossary. However you can edit term entries

When editing your glossary the following features are supported:

Delete entry
Add entry
Import into Glossary
Edit entry

Glossary Restrictions

Import file format: The format of the import can either be *.TSV & *.CSV (delimited by either a semi colon or comma). The placement of source / target terms within your file, should directly correlate with the supported language direction defined during importCommon Restrictions for All Glossary Formats

Duplicate source entries are not allowed
Neither source nor target entry may be empty
Source and target entries must not contain any C0 or C1 control characters (including, e.g., "\t" or "\n") or any Unicode newline

Limits imposed: You can create up to 1,000 glossaries. Please keep in mind that the maximum size limit for a glossary is 10 MB and each source/target text as well as the name of the glossary is limited to 1024 UTF-8 bytes.Editing existing DeepL API Glossaries is not supported by DeepL. You can implement the edit functionality yourself by creating a new glossary with the modified entries and deleting the old glossary.Language Support: Not all languages supported by the plugin for translation have glossary support. If you have a problem please make sure you check the supported languages here: https://www.deepl.com/docs-api/glossaries

How the plugin works

To close the window use "Cancel" button or "X" from the top right of the window

Troubleshooting:

Sometimes errors can be reported when trying to get a translation result from DeepL. This may be related to firewall restrictions which can be resolved by whitelisting the following domains:

www2.deepl.com

api.deepl.com

For more details on this you may find this link helpful:

https://gateway.sdl.com/apex/communityknowledge?articleName=000013232

Checkout other plugins from this developer:

Free

webVTT filetype

By Trados AppStore Team

Filetype support for the webVTT filetype used in subtitling (HTML5). Can work alongside the Studio Subtitling plugin that is available on the RWS Appstore for enhanced context when translating/editing/proofing. Can work alongside the Studio Subtitling plugin that is available on the RWS AppStore for enhanced context when translating/editing/proofing.

Free

studioViews

By Trados AppStore Team

ProblemSometimes there is a need to be able to extract some segments from a file, or multiple files, and send them as a single file to others. Sometimes there is a need to open all the files in a virtual view and then save them as a single file to share with others. Sometimes you don't want to open the files at all, but you might want to split them or merge them to send to others.ResolutionThe solution to all of these requirements is studioViews. This application will not only allow you to export from the files view, filtered selections in the Editor view, or plain and simple segment selection, but it also allows you to import the translated file you exported back into your project and will update your files accordingly. The exported file is an SDLXLIFF and fully supports all the features of SDLXLIFF (segment statuses, match values, tracked changes etc.). To learn how to use this application, please check the Documentation tab.

Free

pub2xml

By Trados AppStore Team

This application is based on the current version of an open source project providing support for the translation of MS Publisher files (*.pub). The application can convert a PUB file into an easily handled XML file. Once translated it can convert the translated XML back to the PUB format. In addition to simply creating XML the application can also generate a PDF of the file in context and this can be included with the XML as a reference file in a Studio Package so the translator has a better idea of what they are translating. The zip file you download also contains a sample sdlftsettings file for this XML as well as instructions on how to use it. Full details of the application can be found in this blog article. Remember, this is an open source project so if you are a developer and you use the code you must credit the project, and if you make any interesting enhancements it would be good if you "paid them forward" and updated the project accordingly. Details of how to access the project are in the ReadMe.pdf downloaded with the app, also in the blog article above.

Free

projectTermExtract

By Trados AppStore Team

This projectTermExtract plugin adds a very neat feature to Studio allowing you to extract term candidates from your Project, or specific files within a project. The plugin works by adding a file containing the terms to Studio for translation, and then converts the file to a termbase and adds it to your project.The plugin also provides for some simple refining of the extraction using a very simple and visual interface that makes the process of term extraction incredibly simple, and enjoyable to work with.If you want to use these terms in your own termbase then this can be easily achieved by using the Glossary Converter, or alternatively you can provide the termbase as a MultiTerm termbase or in another format as a nice value add solution for your customer.To learn how to use this application, please check the Documentation tab.

Free

applyTM Template

By Trados AppStore Team

ProblemDo you maintain many file-based Translation Memories? Have you ever had to update the segmentation rules, abbreviation lists, variable lists, or ordinal follower lists in Trados Studio? Have you ever wondered how to get all of these details from a Language Resource Template? If you have, then you'll be familiar with the effort that is required to make changes as they need to be applied across all of your Translation Memories one at a time; and with the inability to get at these resources once they are part of a template.SolutionThe applyTM Template application removes the repetitive effort that is required to make these changes. Now you can maintain one Language Resource Template and apply the changes to all of your Translation Memories in one go!It works by selecting the template and then adding all of your TMs (browse or drag and drop) in one go; check the resources you wish to be updated based on your template; then click apply. You can maintain resources for multiple languages in the same template, and the application will show you visually which languages were changed or not.You can also export these resources to Excel where it might be easier to carry out maintenance and then import them back into your template afterwards. And of course, you can import the resources from your Translation Memories into a Language Resource Template.To learn how to use this application, please check the Documentation tab.

Free

YourProductivity

By Trados AppStore Team

RWS's #YourProductivity app counts the keystrokes you save with Trados Studio's many productivity-boosting features, and converts them into points. These points were originally used as part of a competition RWS ran for prizes but that was finished a while ago. We decided to keep the application because the concepts are quite interesting if you wanted to see how much you can increase your points by making more use of the productivity features available. Something for you to use, to improve your personal techniques when operating Studio technology.

Free

XML Reader

By Trados AppStore Team

This XML Reader application provides a simple way to convert the XML analysis reports generated by Studio to Excel.Sometimes translators are sent the XML files alongside the sdlxliff files and no project package which means they are unable to easily read the analysis. This application supports a simple drag and drop of the xml files and conversion to excel of as many reports as you like.To learn how to use this application, please check the Documentation tab.

Free

XLIFF Manager for Trados Studio

By Trados AppStore Team

The ProblemYou need to share files for translation or review and the people you are sharing with don't use Studio, they can't support SDLXLIFF, and they want to use a CAT tool. You also do so much of this you need to have a better way of managing the process. You want to be able to share one XLIFF on a multi-lingual project and have the translators complete the target language.The SolutionThe XLIFF Manager is the solution to this problem as it provides the following core features:- export your Studio projects as vanilla XLIFF 1.2 files- export your Studio projects as Google Polyglot XLIFF files- choose whether the target language should be set or not on export- choose whether you export all the segments in your files or not- import the translated XLIFF files back into Studio and update your Studio projects- map unsupported languages from your clients system in support of the import- generate reports of the changed work- be in control of the end to end process with a project management view in StudioPlanned Enhancements for the future updates- progress bars while waiting for the export/import. Useful for large projects- support for tracked changes in the import- add support for an XLIFF 2.1 export- add support for an SDLXLIFF export (to help with the management of an SDLXLIFF file workflow outside of a package)- we're open to suggestions in the RWS Community!To learn how to use this application, please please check the Documentation tab.

Free

WorldServer Compatibility Pack for Trados Studio

By Trados AppStore Team

This app is only required with Trados Studio 2021 and above. Install it to work with bilingual files and packages originating from WorldServer versions 11.x and 10.4.x. Besides bilingual files, WorldServer packages can contain resources such as TMs, including live TM connections, and termbases for you to work with.