Skip to main content

Rigi Documentation

Rigi project life cycle

The development team maintains a comprehensive code repository that contains various files requiring localization in multiple languages. Additionally, there can be target files containing translations. 

In Rigi, a project mirrors the evolution of an application throughout its lifecycle.

  1. Subscribers create a project. For details, see the Create a project guide.

    Note

    In some organizations, subscribers can assign other subscribers, although this is typically managed by the Rigi team. For more information, contact the Rigi administrator in your company.

  2. Developers prepare the workspace. For details, see the Set up a workspace guides.

  3. Project managers update the string list. For details, see the Set up a translation project guide.

    When the source files are defined, the next step is to parse them. This parsing process will generate a string list containing all string identifiers, source texts, and target texts. If there were pre-existing strings in the string list, performing an update will include adding new strings, removing non-existing ones, and updating altered strings. The modified strings' translation status will be changed to "untranslated," while their current translations will be retained.

  4. Developers prepare the staging server with Rigi tokens. For details, see the Prepare a staging server with Rigi tokens guide.

    A specific locale must be installed on the staging (test) server to enable Rigi's string recognition functionality. This installation process is similar to adding any other locale. Once this locale is in place, Rigi can identify strings based on their unique string identifiers.

  5. Developers capture HTML previews. For details, see the Capture previews for WPF applications guides.

    ARigi has powerful tools for capturing precise HTML Previews of live applications. These previews accurately reflect the state of the web app at a specific moment, encompassing elements such as the DOM, CSS, fonts, images, and more. It also compiles an index of the string identifiers on the page. This index allows Rigi to associate each string identifier with the HTML preview it appears in within the project, facilitating the substitution of their texts with actual translations. It's worth noting that Rigi also offers solutions for capturing HTML previews in other platforms, including WPF and mobile applications.

    Alternatively, a live application can be used to provide context. For details, see the Capture live links, Translate using live links, and Perform a live review guides.

  6. Project managers create translation tasks and send text for translation. For details, see the Manage the translation of the source texts guides.

  7. Translators translate texts in context. For details, see the Translate in context guides.

  8. Project managers create review packs and send translations for the Language acceptance test. For details, see the Manage reviews (LATs) guides.

  9. Language testers review the translated texts in context and report issues. For details, see the Reviewer guides.

  10. Translators correct the issues in their translation. For details, see the Process feedback from reviewers guide.

  11. Project managers mark tasks and packs as completed.