Rigi and Transifex can be connected in different ways depending on where your localization content is managed and where you want translators to work.

This guide is divided into two separate workflows:

Sending Rigi content to Transifex and use Rigi viewer
Use this workflow when your source content is managed in Rigi and you want translators to translate it in Transifex with in-context previews available through the Rigi Viewer.
Use Rigi viewer with content stored only on Transifex
Use this workflow when your source content is managed only in Transifex and you want to use Rigi viewer for visual context.

Workflow 1: Send Rigi content to Transifex

Rigi's integration with Transifex lets translators view strings in their product UI context directly from the Transifex Editor using the Rigi Viewer.

In this workflow, Rigi sends source content to Transifex as Rigi XLIFF files. These files include the metadata required for the Rigi Viewer to display the selected string in its correct UI context during translation.

Prerequisites

Before you begin, make sure you have the following in place:

A Rigi tenant and user account.
A Transifex organization with a file-based project already set up.
Transifex API credentials for the user who will connect Rigi to Transifex.
Source files ready to upload to the Rigi project, or a pre-existing Rigi project with files already uploaded.

Prepare your Rigi project

Sign in to Rigi and choose an existing or create a new Web App project for the content you want to localize.
If starting a new project, upload your source files and set the source and target languages.
Approve the uploaded content in Rigi to generate the string list that will sync to Transifex.
Run the Capture Previews process. Previews are stored in your project and will be accessible through the Rigi Viewer during translation.

Connect Rigi to Transifex

In Transifex, open your user profile and copy or generate your API token.
In your Rigi project, open the TMS Connection under your settings, select Transifex from the dropdown, enter your API credentials, and select the Transifex rproject you want to send content to.
Configure language mappings in the connector. Review these carefully before translation begins.
You're ready to send your strings to Transifex.

Rigi uploads your source files to Transifex as Rigi XLIFF files. These files contain the metadata that the Rigi Viewer needs to highlight the correct strings during translation.

📝Note: You can find more details about generating a Transifex APi token here.

Translate with in-context previews

Translators open a Rigi XLIFF file in the Transifex Editor and select a string.
They click the Preview button to open the Rigi Viewer, which displays the string in its UI context.
Translations are completed in the Editor as normal. When a target language is 100% translated, translations are automatically sent back to Rigi.

Workflow 2: Use directly Rigi viewer keeping source content only in Transifex

Use this workflow when your source content is managed in Transifex and you want to connect it to Rigi so translators can use visual context while translating in the Transifex Editor.

Rigi uses pseudo-language files and captured previews to connect each string with its location in the product or website UI.

Once configured, translators can open the Rigi Previewer directly from the Transifex Editor and see where each string appears for visual context.

Prerequisites

Before you begin, make sure you have the following in place:

A Rigi environment and access to a Rigi account.
A Rigi project already created.
A Transifex account with a file-based project already configured.
The source file uploaded to Transifex and ready for localization.
The same target languages configured in both Transifex and Rigi.
The Rigi add-on enabled on your Transifex subscription.
The Rigi Injector plugin installed from the Chrome Web Store.

📝Note: If a Transifex target language is not configured in the Rigi project, the Rigi Viewer will not load for that language.

Prepare your Rigi project

Sign in to Rigi and choose an existing Web App project or create a new one for the content you want to connect with Transifex.
Create a new access token under Settings -> Access

Then set the rights for this token to Tokenize Strings from Authorizations.

Connect Transifex to Rigi

In Transifex, go to the project dashboard and select Project Settings > Context by Rigi.
Click Link.
Add the Rigi access token you generated in Rigi.Click Validate.
The Rigi tenant URL and Rigi project URL fields are automatically filled in using the information contained in the access token.
Configure the language mappings between Transifex and Rigi. Most language mappings may be prefilled automatically. Review the suggestions carefully before continuing. Please note that all language mappings must be completed before you can move to the next step.
In the Select content step, choose the source file you want to sync with Rigi and click Link. Note that only file formats supported by Rigi are shown in this step.
The system navigates back to the Context by Rigi tab. The setup is complete.

📝 Note: If an error appears in step 4, confirm that the Rigi access token is correct and that it includes the required authorization.

Show sync status

After the project is linked, the Context by Rigi tab shows Rigi as linked.

If syncing is still in progress, a message appears indicating that the sync is running. Refresh the page to check whether the sync has completed. When the sync finishes, the latest sync status is displayed.

Download and deploy the pseudo-language file

In the Context by Rigi tab, click the three-dot menu and select Download pseudo-language.
Select the resource and request the .zip file.
Unzip the file and rename the pseudo-language file using the original JSON filename and the Rigi pseudo-language code. For example, if the original filename is products.en.json, rename it to products.rg_RG.json
Deploy the renamed pseudo-language file to the website or web app environment. Ideally, this file should only be used in the staging environment. Its purpose is to store Rigi tokens so Rigi can capture previews and connect the Transifex strings with their visual context.

Capture previews in Rigi

Open Rigi and go to the Rigi project dashboard, select Context > Previews from the left menu, and click Capture previews.
Add the web server or staging environment URL and click Start capture.
When the next page opens, we recommend opening your website side by side and going through it page by page, capturing a preview for each page. Rigi will capture the visual context for the synced Transifex strings, and these previews will be available in the Rigi Viewer during translation.

Translate with in-context previews

Translators open a synced resource in the Transifex Editor and select a string.
They open the Preview panel and select Rigi Previewer, and the Rigi Viewer displays the selected string in its UI context.
Translations are completed in the Editor as normal. Translators can also use Transifex review tasks, comments, and issues as part of their review process.

Review cycles

Review cycles are performed in Transifex using review tasks, comments, and issues.

If new strings are added to the website or web app in already-linked files, repeat the process starting from the pseudo-language file download and preview capture steps.

If new localization files are added to the website or web app, you will need to go again to the Transifex project dashboard, select Project Settings > Context by Rigi, and click Manage. Then select the new files to sync with Rigi and repeat the setup flow for those files.