memoQ plugin

# Downloads
# Installing on memoQ client
# Installing on memoQ server
# Configuring engines
# Pre-translating files
# Changelog

This plugin provides a way for Globalese users to pretranslate files or entire projects from memoQ version 8 or later.

Limitations and gotchas

  1. Currently memoQ is set by default to allow only up to 10 segments to be sent to any MT provider. This setting needs to be changed manually in the relevant configuration file(s) during installation, and again every time your memoQ client or server gets updated.
  2. MatchPatch must be turned off, otherwise memoQ will instruct the plugin to generate countless tiny jobs that will eventually clog the translation pipeline.

Downloads

To install the Globalese plugin on a memoQ client or server, you will need the installer: Plugin installer

Please do not forget to unblock the file after downloading (by right-clicking on file properties and selecting Unblock).

Installing the plugin on a memoQ client

  1. Run the installer as administrator. The plugin is currently compatible with memoQ versions 8.0 and higher.
  2. Locate the MemoQ.exe.config file on your local computer.
    1. For memoQ 8, look in the C:\Program Files (x86)\Kilgray\memoQ-8 folder.
    2. For memoQ 9, look in the C:\Program Files\memoQ\memoQ-9 folder.
  3. Open the file in your favourite text editor (if you don’t have one, we suggest Notepad++) as administrator.
  4. Find the BatchSize entry.
    memoq_config_batchsize
  5. Increase the value to 100000:
    <add key="BatchSize" value="100000" />
  6. Save the file and exit the text editor.

Installing the plugin on a memoQ server

  1. Stop the memoQ server service.
  2. Run the installer as administrator. The plugin is currently compatible with memoQ versions 8.0 and higher.
  3. Locate the MemoQ Server.exe.config file on your local computer (for memoQ 8, look in the C:\Program Files\Kilgray\Memoq Server folder).
  4. Open the file in your favourite text editor (if you don’t have one, we suggest Notepad++) as administrator.
  5. Find the <appSettings> entry.
    memoq_server_config_batchsize
  6. Insert a new entry under <appSettings>:
    <add key="BatchSize" value="100000" />
  7. Save the file and exit the text editor.
  8. Restart the memoQ server service.

Configuring a Globalese engine in memoQ

You will need to set up as many configurations as the number of Globalese engines you want to use in memoQ.

  1. Choose Options → Default resources → MT Settings in memoQ.
    memoq_options_mt_settings
  2. Choose Create new.
  3. Enter a meaningful name for the engine. We suggest you include the language pair in the name (you’ll thank yourself later).
    memoq_new_mt_settings_resource
  4. Click OK.
  5. Select the newly created entry and click Edit.
  6. Select Globalese MT Plugin.
  7. Click Configure plugin.
    memoq_edit_mt_settings_configure_plugin
  8. Enter the base URL of your Globalese system (which can be found on the About page), your username and corresponding API key (which both can be found in your Globalese user profile).
  9. Click Check login.
  10. Choose a group and an engine, and finally click OK.
    memoq_globalese_mt_plugin_settings
  11. Turn off the MatchPatch feature under Settings.
    memoq_globalese_mt_plugin_settings

Note: Make sure you use local MT configurations locally and online MT configurations for server projects.

See the relevant memoQ documentation here.

Pre-translating files with Globalese from memoQ

  1. In your memoQ project, go to Settings.
  2. Choose MT settings.
  3. Select the Globalese engine(s) you want to use.
    memoq_translation_select_globalese
  4. Use the Pre-Translate option as you normally would.
    Make sure the Perform fragment assembling option is unchecked, and check the Use machine translation if there’s no TM match option.
    memoq_pretranslate_settings

See the relevant memoQ documentation here.

Changelog

v1.2.3

  • Web timeout issue fixed.
  • New option to turn on logging.
  • Engine and project main languages and sublanguages can be combined (e.g. you can use an en-pt engine for an enUS-pt project or an enUS-ptBR engine in an en-pt project).
  • Server setup handled by the installer (no more manual copying & pasting of files). Note: the BatchSize parameter still needs to be changed manually.

v1.2.4

  • Issue fixed where wrong signature file was installed during server installation.