DeepL Translation Provider

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

7.0.5.0 - Trados Studio 2024

Changelog:

  • fix Chinese simplified/traditional recognition issue


Checksum: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Release date: 2024-09-18

6.2.2.0 - Trados Studio 2022 (SR2)

Changelog:

  • fix out of memory exception


Checksum: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Release date: 2024-09-10

6.1.3.2 - Trados Studio 2022 (SR1)

Changelog:

  • support for Studio 2022 SR1 only

Checksum: 1df16071d4235500572d41283205e2358bbf1c9161d03702a4f9beda5d6ee66b

Release date: 2024-07-29

6.0.3.1 - Trados Studio 2022

Changelog:

  • Corrected updated plugin manifest to ensure that the plugin will not attempt to install into Trados Studio 2022 SR1. This is important because the SR1 release contains breaking changes that will cause this version of the plugin to prevent Studio from starting. There will be a further update of this plugin specifically for the 2022 SR1 release either alongside, or shortly after SR1 is made publicly available.


Checksum: fb8465dcf1a0f8d8d18dde05f7b96f87f96bf7a5d5f3ed7e3c17e94bfb198150

Release date: 2023-06-05

5.8.28.0 - Trados Studio 2021

Changelog:

  • Make DeepL accessible from standalone apps.


Checksum: de0e8c83d44e551c64edd74efd4bab4b98f8e56b59128b984f0a1a1fa4a85918

Release date: 2022-12-06

4.8.24.0 - SDL Trados Studio 2019

Changelog:

  • Removed the error 'DeepL does not support any language pair in this project' when clicking OK without an API key being added.


Checksum: d35a23168db23b0412ddae6766595741e28246658b63280ce1dd4d2f182bfff0

Release date: 2021-06-14

3.8.12.0 - SDL Trados Studio 2017

Support website: https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore

Support e-mail:

Shared products:

7.0.5.0 - Trados Studio 2024

  • fix Chinese simplified/traditional recognition issue


7.0.4.3 - Trados Studio 2024

  • fix out of memory exception
  • show correct API version choice in UI


7.0.2.0 - Trados Studio 2024

  • Added support for Tls12 and Tls13


7.0.1.5 - Trados Studio 2024

  • Fix NREs
  • Added tag handling option → set to “none” the ampersand will be handled correctly
  • Added preserve formatting option → set to false, it fixes the capitalization issue
  • Changed select folder window


7.0.1.4 - Trados Studio 2024

  • Fix NRE
  • Added tag handling option → set to “none” the ampersand will be handled correctly
  • Added preserve formatting option → set to false, it fixes the capitalization issue
  • Changed select folder window


7.0.0.4 - Trados Studio 2024

  • updated to support Studio 2024
  • TellMe updated


6.2.3.0 - Trados Studio 2022 (SR2)

  • fix Chinese simplified/traditional recognition issue


6.2.2.0 - Trados Studio 2022 (SR2)

  • fix out of memory exception


6.2.1.0 - Trados Studio 2022 (SR2)

  • Added support for Tls12 and Tls13


6.2.0.0 - Trados Studio 2022 (SR2)

  • Fix NRE
  • Added tag handling option → set to “none” the ampersand will be handled correctly
  • Added preserve formatting option → set to false, it fixes the capitalization issue
  • Changed select folder window


6.1.3.2 - Trados Studio 2022 (SR1)

  • support for Studio 2022 SR1 only

6.1.2.18 - Trados Studio 2022 (SR1)

  • Added support for DeepL glossaries.

6.1.1.0 - Trados Studio 2022 (SR1)

  • Addressed breaking changes 
  • Sdl.Core.Globalization (Modified)
  • Sdl.Core.Globalization.Async (Added)
  • Sdl.Desktop.Platform.Controls.Behaviors.MouseDownBehavior (Deleted)


6.0.3.1 - Trados Studio 2022

  • Corrected updated plugin manifest to ensure that the plugin will not attempt to install into Trados Studio 2022 SR1. This is important because the SR1 release contains breaking changes that will cause this version of the plugin to prevent Studio from starting. There will be a further update of this plugin specifically for the 2022 SR1 release either alongside, or shortly after SR1 is made publicly available.


5.8.28.0 - Trados Studio 2021

  • Make DeepL accessible from standalone apps.


4.8.24.0 - SDL Trados Studio 2019

  • Removed the error 'DeepL does not support any language pair in this project' when clicking OK without an API key being added.


3.8.12.0 - SDL Trados Studio 2017

No related information.

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

  

  1. 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

  1. 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

  1.  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

Checkout other plugins from this developer:
Antidote Verifier

Free

Antidote Verifier

By Trados AppStore Team

Antidote is a spelling and grammar checking tool from Druide informatique inc that integrates with MSWord and a variety of other applications.This free plugin adds the Antidote toolbar you'll find in MSWord into Studio under the review ribbon, so you can work with this application interactively as you translate or review.The Antidote Verifier plugin is free, but if you wish to use this, you must have a copy of Antidote installed, otherwise nothing is going to happen!For more details on how the plugin works with Studio refer to this article : https://multifarious.filkin.com/2016/09/08/antidote/.For further information about Antidote refer to this website: http://www.antidote.info/.
Studio Subtitling

Free

Studio Subtitling

By Trados AppStore Team

The Problem this app addressesThe volume of audio visual content for localization is growing rapidly. Turnaround times are getting shorter and many of those working in the industry are feeling increased price pressures in dealing with this sort of content. Translation tools today lack proper context for subtitlers, offering poor support for the variety of file formats.The Solution this app providesThe Studio Subtitling plugin supports enhanced features for audio visual translation, editing, proofing and works synchronously with the Studio editor in support of the following filetypes:- ASS (available here on the RWS AppStore)- SRT (supported out of the box in Trados Studio 2021/2022/2024)- webVTT (supported out of the box in Trados Studio 2021/2022/2024)- STL (available here on the RWS AppStore)- SBV (supported out of the box in Trados Studio 2021/2022/2024)- TTML (supported out of the box in Trados Studio 2021/2022/2024)NOTE:The plugin does not work with single document projects, resulting in errors. To use it properly, you need to create standard projects.It is not possible to use the numpad for non-subtitling files if this plugin is installed. This is a limitation of Studio. The workaround is to remove the keyboard shortcuts for numpad in the Studio options. They can be reset when needed by using "Reset to Defaults" in the Subtitling Keyboard shortcut list.Click here to download the TQA model for Trados Studio that is also supported by this plugin.
ASS File Type

Free

ASS File Type

By Trados AppStore Team

Filetype support for the ASS/SSA (Advanced SubStation Alpha) filetype used in subtitling. Can work alongside the Studio Subtitling plugin that is available on the RWS Appstore for enhanced context when translating/editing/proofing.
STL File Type

Free

STL File Type

By Trados AppStore Team

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

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.
Language Weaver

Free

Language Weaver

By Trados AppStore Team

This app is not longer being maintained. Please use the Language Weaver Provider app if you want to rely on the latest supported features and enhancements Language Weaver Cloud is the cloud deployment of the award-winning RWS Machine Translation software that is made for enterprises. It combines RWS's Neural Machine Translation (NMT) capabilities with Linguistic AI™ to remove language barriers in content-intensive business functions.Language Weaver Cloud addresses the needs that businesses have for a reliable, cloud-based, enterprise-grade machine translation solution with the assurance of content privacy.Language Weaver Cloud is powered by RWS's state-of-the-art machine learning algorithms and supports a large number of languages.Notes on authentication:The Client ID and Secret can be retrieved by an admin user from the Language Weaver Cloud user interface. The Username and Password are the same as the RWS ID you use for the Language Weaver Cloud user interface.
studioViews

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.
Multilingual XML FileType

Free

Multilingual XML FileType

By Trados AppStore Team

- to learn more about the app itself please look in the Multilingual XML FileType wikiThe ProblemSometimes you receive XLIFF files with large dumps of html in CDATA sections, or invalid XLIFF files (still well formed but not recognised as valid XLIFF by Trados Studio), partially translated bilingual XML files, multilingual XML files and all the work this entails in creating settings for each language pair and then attempting to piece them altogether afterwards or even needing to use an html embedded content processor AND regex rules for placeables. If you can recognise these sort of problems then this filetype will bring some welcome relief!The SolutionThe Multilingual XML FileType solves all of these problems and more. Some common usecases for it would be:create bilingual or multilingual projects from an XML file containing at least two languages handle large CDATA dumps in XLIFF files correctly handling well formed, but invalid XLIFF files that Trados Studio will not handle out of the box handle bilingual or multilingual XML files without the need to copy the source into the target element and translate the target element only. handle partially translated bilingual or multilingual XML filesYou can learn more about the app itself in the Multilingual XML FileType wiki.
Post-Edit Compare

Free

Post-Edit Compare

By Trados AppStore Team

Post-Edit Compare is a tool designed to report translation modifications during the post-edit phases of a translation workflow. The tool works by comparing two versions of the same SDLXLIFF file (before and after changes were applied); the files with changes are highlighted and all modifications are included in a comparison report. The comparison report is formatted in a way that simplifies the understanding of what changes were applied from one version of the file to the other, along with a full break down of the modifications and related cost analysis. Improved handling for TERp analysis, much improved and simplified reporting process from the main Studio Projects View, ability to save reports in Excel