This functionality is only available to Globalese Cloud users. If you have an on-premise installation of Globalese, you can use the legacy Document translation plugin for Trados Studio
Known issues
Currently, when you pre-translate one or more files with the plugin, segments are not sent in batches but rather one after another. This is not the most efficient way, and may end up taking a longer time than expected. We are working on a remedy, but until we find one, consider using the legacy Document translation plugin for Trados Studio for pre-translating larger project files.
Prerequisites and pricing
Pricing is based on the number of translated source text characters. The actual price is listed on the Pricing page under “Text translation”.
For more details, please refer to Text translation using deployed engines
Studio will make additional API calls when a file is opened and when a segment is selected for editing. This is driven by Studio's internal logic and cannot be overridden completely. By disabling File > Options > Editor > Automation > Enable lookahead, Studio will only send Globalese the currently edited segment after the initial API calls.
Downloads
The plugin can be downloaded from the RWS App Store, or from below (unsigned versions only):
Supported Trados Studio versions
Check out this page about RWS’s support policy for different versions of Trados Studio. In alignment with RWS’s support policy,
Studio 2019 will be continue to be supported until 31 December 2022;
Studio 2017 has reached its end of life and is not supported any more.
Installing the plugin
After running the installer, a new “Globalese Cloud text translation plugin” translation provider will become available.
Configuring a Globalese engine
In a project, open the Project Settings.
Go to Language pairs > <the chosen language pair> > Translation memory and automated translation.
Click Use…, and select the Globalese Cloud text translation provider.
Enter the base URL of your Globalese system (i.e. the URL you use to log in to Globalese in your browser, similar to
https://mycompany.globalese.ai) and your API key (see Text translation using deployed engines for more information).Click Connect.
Select an engine. Note that you can only select engines that have active (i.e. deployed) instances.
Click OK.
Your engine is now set up in Studio. You can use it for segment-based lookup or for pre-translation.
It is typical to have to wait for the first translations coming back from a Globalese engine. This is due to what is called “cold start”, and is related to scaling the deployed engine.
Wait times should come down to normal as soon as you start continuously sending sentences to Globalese (either by working on a file or pre-translating files).
Log file location
The log file can be found in the %TEMP% directory as GlobaleseTpProvider.log.