Cloud text translation plugin for memoQ

This functionality is only available to Globalese Cloud users. If you have an on-premise installation of Globalese, you can use the legacy https://globalese.atlassian.net/wiki/spaces/DOCS/pages/647070050

Version information

The Cloud text translation plugin is available for following memoQ versions:

  • memoQ 9.12 and above: available as public plugin (part of the memoQ installation)

  • memoQ 9.10.x: available as private plugin.

  • memoQ 9.9.x: available as private plugin. Below 9.9.10, configuration file maintenance is required in case of server installations. Please refer to the memoQ documentation (section Testing a new plugin in memoQ server) for more details.

  • memoQ 9.8.x: available as private plugin. Configuration file maintenance is required in case of server installations. Please refer to the memoQ documentation (section Testing a new plugin in memoQ server) for more details.

  • memoQ 9.7.x: available as private plugin. Below 9.9.20, configuration file maintenance is required in case of server installations. Please refer to the memoQ documentation (section Testing a new plugin in memoQ server) for more details.

  • .NET 4.8 is required for all versions if installed on memoQ server

Prerequisites and pricing

With this plugin, users can consume Globalese Text translation services from memoQ. For more details about how to enable an engine for text translation, see https://globalese.atlassian.net/wiki/spaces/DOCS/pages/2233761810.

Pricing is based on the number of translated source text characters. The actual price is listed on the Pricing page under “Text translation”.

memoQ will make some additional API calls to translate segments when a file is opened and when a segment is selected for editing. This is driven by memoQ’s internal logic and cannot be overridden.

Downloads

Installing the plugin

  1. Download the latest version of the plugin installer file. After downloading, unblock it by right-clicking on the file and choosing Properties. Activate the Unblock checkbox, and click on Apply.

  2. No changes are necessary in the MemoQ.exe.config configuration file (cf. https://globalese.atlassian.net/wiki/spaces/DOCS/pages/647070050).

  3. Run the plugin installer as a local administrator.

  4. Choose the target version. In case you have several versions of memoQ installed on your computer, the installer will show the different versions and the path.

     

  5. Click on Next and on Finish to finalize the installation.

Configuring a Globalese engine

  1. Open the Resource console.

  2. Go to MT settings.

  3. Choose Create new.

  4. Enter a meaningful name for the engine. We suggest you include the language pair in the name (you’ll thank yourself later).

  5. Click OK.

  6. Select the newly created entry and click Edit.

  7. Select Globalese Cloud text translation plugin.

  8. Click Configure plugin.

  9. 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. The API key of your user can be retrieved in your Globalese system from your user profile (<your user name> → Profile). You can copy the API key to the clipboard by clicking on the clipboard icon.

    For more details, see also https://globalese.atlassian.net/wiki/spaces/DOCS/pages/2233761810.

  10. Click Connect.

  11. Select an engine. Note that you can only select engines that have active (i.e. deployed) instances.

  12. Click OK.

Your engine is now set up in memoQ. 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).

Changelog

v1.0.0

  • The new Globalese text translation funcionality is available in memoQ.

v1.0.4

  • Languages and ID are visible next to each engine in the dropdown list.

v1.0.5

  • Bug fix

v1.0.6

  • Fix for log archiving