Export texts for translation in external tools
Rigi supports the export and import of source texts and translations. The following file formats are supported:
(Preferred) XLIFF (bilingual with states).
XML (monolingual).
Excel (bilingual with states).
XLIFF 1.2 is a bilingual file format. Its purpose is to store localizable data and carry it from one step of the localization process to the other while allowing interoperability between tools. This interoperability is achieved via the trans-unit state attribute. The external tool should, for example, not pre-translate source texts that already have a translation. Rigi, in turn, will import the state as provided by the external tool.
In the project menu, select Texts > Overview.
Click the Export button.
Configure the following settings:
From the Export format dropdown, select XLIFF.
Select the target locales that will be exported.
(Recommended) Lock the string list to ensure that no changes can be made to the translation while this pack is exported.
Click the Next button.
Specify which strings must be exported by selecting status checkboxes.
You can export only the new and modified texts by selecting the Untranslated status. In this case, in Rigi Viewer, the available translations from Rigi (not from the exported XLIFF) will be displayed on previews for all the non-exported strings (Translated, Reviewed, and Validated).
Click the Next button.
Specify whether the exported file must be split.
There are two reasons to split up the exported file:
Project management. A task can be split among multiple translators, ensuring that each translation pack has the same number of translatable strings.
Technical limitations. Some external editors cannot handle large files. It is recommended to use smaller files. For details, see the Rigi connectors for third-party tools guide.
Click the Export button. A ZIP file containing XML file(s) will be downloaded.
Rigi XML is a monolingual file format. Interoperability with external tools is not supported because there is no exchange of state information.
In the project menu, select Texts > Overview.
Click the Export button.
Configure the following settings:
From the Export format dropdown, select XML 1.2.
Select the locales that will be exported (by default, only the source locale is exported).
XML for target locales
Selecting a target locale means that the source texts (!) for that target locale are exported.
A use case is to export source texts for untranslated strings only (see next step) and import them afterward.
(Recommended) Lock the string list to ensure that no changes can be made to the translation while this pack is exported.
Click the Next button.
Specify which strings must be exported by selecting status checkboxes.
You can export only the new and modified texts by selecting the Untranslated status. In this case, in the Rigi Viewer, the available translations from Rigi (not from the exported XLIFF) will be displayed on previews for all the non-exported strings (Translated, Reviewed, and Validated).
Click the Next button.
Specify whether the exported file must be split.
There are two reasons to split up the exported file:
Project management. A task can be split among multiple translators, ensuring that each translation pack has the same number of translatable strings.
Technical limitations. Some external editors cannot handle large files. It is recommended to use smaller files. For details, see the Rigi connectors for third-party tools guide.
Click the Export button. A ZIP file containing XML file(s) will be downloaded.
The exported Excel files contain string identifiers, source texts, target texts, comments, and status values. A typical use case is when the translator does not have a translation editor available and does not want to translate online in Rigi.
In the project menu, select Texts > Overview.
Click the Export button.
Configure the following settings:
From the Export format dropdown, select Excel.
Select the target locales that will be exported.
(Recommended) Lock the string list to ensure that no changes can be made to the translation while this pack is exported.
Click the Next button.
Specify which strings must be exported by selecting status checkboxes.
You can export only the new and modified texts by selecting the Untranslated status.
Click the Export button. A ZIP file containing Excel files will be downloaded.
File format
Do not edit the header!
It is used to reimport the Excel file with translations.
Important
Translators are allowed to edit the following fields:
Target.
Status (untranslated, translated, reviewed, validated).
Signature. The signature is a unique identifier needed to import the translation correctly.
Do not edit signatures
It will corrupt the file, and you will not be able to import it anymore.
String ID. This is a readable string identifier. It can help the translator understand the context from which a text originates.
Source locale (e.g. en-US). This column with the source texts has the locale ID in the header. Do not edit the header!
Target locale (e.g., de-DE). This column with the translation texts has the locale ID in the header. Do not edit the header!
Important
The translator should edit the translations here.
Comment. This column contains an optional comment from the developers.
Status.
Important
The translator should edit the status here.
Allowed values are:
untranslated.
translated.
reviewed.
validated.
Preview URL. This column contains a URL to an HTML preview that indicates how the string is used in context.