Major Context Update
The latest June release of Localyzer has some very powerful and exciting features. The localization industry understands the importance of context for accurate translations. This is solved for many content types. But, context has long been a challenge for software translation. When translating the short strings/labels/messages that are part of any U/I, the translator often has little to go on for accuracy and physical space limitations. For instance, is that a coat of pain, or something to keep you warm?
Context Done Right
Lingoport has solved this problem with major improvements to its context gathering. Context gathering and associated U/I string mapping can now be streamlined for web apps, Figma designs, and mobile apps. And it’s been done in a way that removes any burden from developers and translators.
- Simple capture
- Easily in the translation workflow
- Saved time
- Cost and Quality improvements
There’s other features as well for this release, all there to improve the power and speed of your software localization projects. Here’s a quick bullet list:
Figma Context Capture
With Figma plugin version 14+, each design element can now be captured and precisely linked to its associated strings.
From Figma to Translation—With Full Context
Screenshot Association to Strings
Upload screenshots directly in String Manager and associate them with selected strings—bringing visual context to life.
And, here is how to do it with InContext Chrome Extension
Trados Context View Integration
Context View is now fully supported in:
- Trados Enterprise
- Trados Accelerate
- Trados Team
- Trados Studio
New: Localyzer PXML Format
A single, consistent Preview XML (PXML) format replaces multiple resource file types for TMS workflows.
- Enables simplified TMS configuration
- Includes URL-based context where available
- Additional metadata support coming soon (think powerful prompting for AI as one possibility)
String Manager Improvements
- Selective Locale Sending
Choose exactly which strings go to which locales—per string. - Hover Indicators
Instantly view which locales a string has been sent to, or is pending. - Faster Performance
Backend optimizations & database enhancements
New setting: Auto-run String Refresh after Analysis
UI & Usability Enhancements
- Improved indicators for actionable steps (Analyze, Translate, Baseline)
- New icon set for better clarity
- System Events now separated from Logs
- Globalyzer Issue View shows more lines of code and improved layout
- Optional: Disable Daily Analysis
InContext Server v2.0.7
InContext now supports serving visual context from:
- Google Chrome Webapp Extension
- Figma design captures
- Screenshot associations
LocalyzerQA v1.7.3
Simplify in-country translation quality feedback and updates. Take further advantage of context! There are always locales that are particularly challenging and get lots of translation quality feedback from the field. LocalyzerQA helps you put that to work quickly and efficiently.
Clearer error handling! Now shows the actual string from your repository when displaying ‘Error: Not Found’
💬 Questions or want a demo?
Let us walk you through the latest improvements and how they streamline your software localization workflows. Book a call with us.
Going Deeper: Solving the Context Challenge in Software Localization
Providing accurate visual context for UI strings in software applications is technically complex—and for good reason. Translation Management Systems (TMSs) typically rely on resource files as their source of truth. These files, however, are abstracted from the broader codebase and lack critical UI context.
Meanwhile, developers work within repositories such as GitHub, GitLab, or Bitbucket, where the actual application logic and UI structure reside. Bridging the gap between resource files and real UI context requires interacting with that developer “source of truth” in a way that goes far beyond what localization files alone can provide.
Lingoport’s products integrate directly with development repositories, placing us in a unique position to associate UI strings with their corresponding screens and user flows—automatically and at scale.
Making Context Effortless
A core principle behind our context capabilities is simplicity—for developers, localization managers, and translators alike. If gathering context takes significant time or manual effort, it’s unlikely to be adopted at scale. To solve this, we prioritized automation and designed workflows that eliminate friction.
Software user interfaces are inherently dynamic. A single screen can contain multiple layers, with menus, tooltips, error messages, and other UI elements revealed only after specific user interactions. These layers can’t be captured by viewing a top-level screen alone. Our context system is built to account for this complexity, ensuring translators see the strings as they actually appear in the application.
Broad Platform Support
To fully support modern development environments, our solution captures context across web, mobile, and even embedded applications. While Lingoport has long supported context for web applications, we expanded our capabilities to include mobile apps and design environments like Figma—each requiring its own tooling and methodology.
Additionally, capturing screenshots for every string (and every variation) creates a data processing and storage challenge. We optimized our system to streamline this process, ensuring speed and scalability for translation workflows.
How It Works: Context Gathering in Action
For Web Applications:
Developers install the Lingoport InContext Chrome extension. When running the application (i.e. during testing), renderings of the UI screens are captured and passed to Localyzer’s Command Center. That data is then sent to a Lingoport InContext Server, hosted either in the cloud or on-premise.
When translators access strings through a TMS or a translation environment like Trados Studio, relevant screenshots are automatically displayed alongside each string, improving translation accuracy and reducing review cycles.
For Figma and Mobile Applications:
- In Figma, screenshots are captured using the Lingoport Figma plugin.
- For mobile apps, screenshots can be captured and pushed to Localyzer’s Command Center for string association.
As with web projects, FIGMA and screenshot context data is stored on the InContext Server and made available during translation.
💬 Questions or want a demo? Book a call with us.
