Rigi for memoQ
Project managers can send Rigi XLIFF or XML to translators. Translators can localize UI texts in memoQ using the in-context Rigi Viewer.
Important
memoQ 9.13 or higher is required to support the Rigi Viewer.
memoQ versions 9.13 and higher support the Rigi Viewer for translation in context. Although it is possible to edit Rigi XLIFF in older versions of memoQ, the Rigi Viewer will not be available.
The Rigi XLIFF file contains source texts, translations, and statuses.
There is no need to pre-translate strings having status translated or higher. You only need to take care of the untranslated strings. Therefore, this process is fast and accurate.
From your Rigi project, export an XLIFF file (for details, see the export an XLIFF file guide).
(Optional) Test whether you can install the plugin for memoQ and see the previews. For details, see the Install the Rigi plugin for memoQ guide.
For details, see the guide.
Import the XLIFF file into Rigi. For details, see the Import translation files guide.
Language test
As a next step, you can conduct a Language test, in which language testers review translations in context and provide feedback. For details, see the Manage reviews (LATs) guides.
After this step, the translators can correct the review comments in the current project.
Important
Use XLIFF if your translators use memoQ version 9.13 or higher.
memoQ versions 9.12 and lower only support in-context localization of Rigi XML files.
Pre-translation is not ideal for software localization
A Rigi XML file is monolingual and only contains source texts. When developers send a new version of the source files, all strings must be pre-translated. This process can take a long time (depending on the number of strings and languages). If a source text has multiple translations, the wrong translation may be used.
Consequently, this process can be slow and result in inaccurate pre-translation results.
There is no need to pre-translate strings having status translated or higher.
From your Rigi project, export an XML file (for details, see the export an XLIFF file guide).
pre-translation is not ideal for software localization!
The Rigi XML file contains source segments without the status values. MemoQ pre-translates all segments and uses the string ID as metadata.
There is a minor risk of mismatches if the TM contains multiple translations for the same source text and ID. A workaround is to only export untranslated strings to the XML file for translators.
(Optional) Test whether you can install the plugin for memoQ and see the previews. For details, see the Install the Rigi plugin for memoQ guide.
Translators perform the translation in memoQ. For details, see the Translate in memoQ guide.
Import the XML file into Rigi. For details, see the Import translation files guide.
Language test
As a next step, you can conduct a Language test, in which language testers review translations in context and provide feedback. For details, see the Manage reviews (LATs) guides.
After this step, the translators can correct the review comments in the current project.