Skip to main content

Rigi Documentation

Localize a web application in Rigi

To localize a web application in Rigi, the following steps must be performed by Rigi users with specific roles:

  1. Rigi administrator (subscriber) steps:

    1. Create a new Rigi project (for details, see Create a project).

  2. Developer steps (I):

    1. Set up a workspace on the Rigi server:

      1. From the repository, upload the source resource files that need to be translated to the Rigi project (for details, see Upload files to the workspace).

        To automate upload, download, and translation alignment actions for continuous localization products, we recommend using the Rigi CLI tool. For details, see Rigi CLI tool.

      2. Configure the source file settings: file parsers, target rules for creating target files, and unique file IDs, and assign the source files to the workspace (for details, see Assign source files to the workspace).

    2. Prepare a staging application with Rigi tokens (for details, see Prepare a staging server with Rigi tokens).

    3. Add the Rigi script (RigiJS) to your application to identify translatable strings on the HTML previews (for details, see Include RigiJS in your application).

    4. Capture HTML previews of your application (for details, see Capture HTML previews for web applications).

  3. Localization manager steps:

    1. Update the string list and add target languages (for details, see Manage the translation of the source texts).

      Use the Rigi CLI tool to automate the string list updates (for details, see Rigi CLI tool).

    2. Send strings for in-context translation:

    3. (Optional) After all required texts have been translated, send the translated strings for review (for details, see Create a review pack).

    4. (Optional) Send strings back to translators for corrections (for details, see Manage the correction of issues reported by language testers).

      When the translation is performed in a different tool, such as XTM Cloud, this step can also be managed outside Rigi.

  4. Developer steps (II):

    When all translations have been marked as 'Reviewed', you can generate target files containing translations for your application (for details, see Generate target files).

In this section: