Rigi.io is a software localization platform that differs from all other solutions by offering dynamic visual context to translators and in-country reviewers. The need for context is not always recognized in localization-teams, until projects grow bigger and a roll-out to more countries is on the roadmap. The context in which a string is used is not always clear at first sight for translators, resulting in guesses or queries.

Software localization is at its core similar to many other localization projects. Strings or segments that need to be localized are supplied by a project manager, and then presented to a translator in a language management tool. But where copy for a website is mostly self-explanatory, strings in a software application are short and, in many cases, ambiguous. These strings are part of menus or error-notices, or maybe even refer to technical terms. Without context, a translator is lost.

Translators will submit queries for unclear texts. A developer or product owner can then answer the question and often creates a screenshot of the page where the string is used. This process usually does not scale for various reasons, like the size of translations, amount of target languages, number of software updates, etc. You can imagine that this procedure is becoming impracticable and may not be in line with your international ambitions.

Rigi.io identified this problem and built a cloud-platform around the concept of dynamic HTML-previews. This platform uses ID-based strings, a characteristic that virtually any software application has. The strings are “riginized”, after which strings can be recognized in previews of the application. Rigi identifies all strings by their string identifiers in pages that Rigi captures and builds a cross-index. When a translator selects a text in the editor, then Rigi will immediately show the preview where all current translations are visible. No matter if you use the built-in editor of Rigi or a third-party platform for which we offer connectors.

Dynamic HTML previews vs. static screenshots

Where things get complicated, translators and in-country reviewers need context to be able to deliver quality translations. This can be done with static screenshots on demand, but with Rigi’s dynamic HTML previews you take a few giant steps in efficiency and insight for your team:

Static screenshots do not include string information and need to be connected manually to strings in your translation project. Rigi’s previews connect automatically, even when you upload new previews later.

  • Static screenshots do not show your translations. Translated texts will only be visible in the actual application after deployment of the translated language files. Rigi shows translations instantly in a dynamic view of your application, what-you-see-is-what-you-get (WYSIWYG).
  • Static screenshots for testing by in-country reviewers must be captured for every single language. Rigi’s HTML previews that can present any desired language at any moment.
  • Static screenshots for documentation need to be captured for each separate language. Rigi generates them all at once, based on a single HTML preview and all available translations.

Added value of dynamic visual context

Few localization projects offer visual context from the start. The main reason is mostly that developers do not want to invest the time in making screenshots. Also project managers guess it might not be necessary and postpone this task until requested. This might turn out as an effective strategy. Although in many cases you end up making screenshots anyway because the queries from translators and reviewers are coming in.

Rigi.io has done its utmost to make the process of creating dynamic visual context as easy as possible. With the auto-capture feature all previews are created while navigating through your application. If you run automated UI-tests, you can even connect this auto-capture to your development workflow. Your developers do not need to change a single line of code.

Rigi.io has done a benchmark in using dynamic previews with one of our bigger clients. This software company with applications in more than 40 languages and over 100.000 strings got 70% (!) fewer queries from translators, leading to faster translations with better quality.

  • Fewer queries means fewer interruptions for developers and project managers to make screenshots on demand.
  • Fewer errors in primary translations means fewer findings by in-country reviewers and fewer corrections later in the process.
  • Faster translations mean faster time-to-market for every software update, in-sync with your release cycle.

This is also possible for you! Request a demo to find out more.

Related articles

Software Localization: 4 tips for success

How to Integrate localization into your entire development workflow?

Read more >

How to properly translate UI texts with visual context

Why translators need visual context and how to create it.

Read more >

How to properly translate UI texts with ID-based localization

Why a TM-based approach does not work for software localization?

Read more >