Keeping localisation in step with product development

The challenge 

Preparing UI content for localisation at scale

As LexisNexis Intellectual Property Solutions continued to evolve its products, the localisation team faced a growing challenge. User interface texts needed to be cleaned up and prepared for localisation across multiple languages, while development continued at pace.

UI content included reused strings, concatenations, and short segments that carried different meanings depending on context. Without clear visibility into where text appeared in the interface, translators had to raise questions, slowing progress and increasing back-and-forth with developers.

The team needed a way to improve translation accuracy and consistency while handling a high volume of new UI text, without becoming a blocker to development.

Why Rigi by XTM

Giving linguists the context they need, upfront

LexisNexis Intellectual Property Solutions chose Rigi to address the core problem: lack of context during UI localisation. Rather than relying on explanations or developer input after the fact, Rigi makes context visible from the start.

By introducing Rigi as part of their localisation workflow, the team could detect concatenations, identify reused strings with different meanings, and prepare UI text properly before translation began. This reduced ambiguity and set translators up for success without requiring deep product knowledge.

The solution

Localisation that runs alongside development

With Rigi in place, UI texts are cleaned, validated, and prepared for localisation in parallel with development sprints. Automated language suggestions help accelerate preparation, while clear status tracking gives the localisation team full visibility into progress.

Translators work directly in their CAT tools while viewing UI context through the Rigi Viewer. Reviewers use the Rigi Editor and previews to validate translations visually, rather than guessing how strings will appear in the product.

As a result, localisation is no longer dependent on developers answering questions or providing explanations. Translations are ready earlier, validated with confidence, and aligned with development timelines.

As Maryla Obszarski, Localization Manager at LexisNexis Intellectual Property Solutions, explains:

“With Rigi in place, our translators and reviewers are much more efficient. No longer do they need in depth product training to understand the context of our translations. Translators now just open their CAT tools, launch the Rigi Viewer, and there they have it! Our reviewers work directly in the Rigi Editor and also benefit from the Rigi previews. It saves us lots of time and resources.”