What does the software localization process actually look like? What key factors ensure a high-quality end product? Valeriya Sherstoboeva, Head of the Multilingual Translation Department at Logrus IT, answers these and other questions.
Before launching a new software localization project, thorough preparation is essential. Only by selecting the right tools and experts can you optimize results for both speed and quality. It’s also essential to request all the necessary information from the client about their product and working process. The latter is especially important if we’ll be collaborating closely during localization—we need to clearly understand how they work.
Flexibility is key to successful software localization. At Logrus IT, we always adapt to our client’s existing workflows. Smaller companies often provide us with unfinished files, and send edits via email. Larger organizations typically prefer us to integrate into their systems in order to oversee the process.
In practice, we usually encounter one of three collaboration models:
Optimal results in any of these scenarios require solid programming skills and expertise in the latest development, translation, and process management solutions.
We’ve also developed our own proprietary tools to streamline project management and ensure top-quality, efficient localizations. One such tool is the Logrus IT Project Portal, which receives orders from clients, automatically registers them in our systems, and sends them via API to popular TMS platforms.
Software localization is a complex process that varies depending on the product—whether it’s a computer program, game, website, online platform, mobile app, or anything else. At Logrus IT, we localize all these and more.
One common feature of software localization is that rather than just plain text, translators receive so-called “resource files” containing UI elements and other metadata. Before starting work, these files must be properly prepared. For example, technical data that doesn’t require translation is identified and excluded, while core program elements critical for localization are preserved. Also, UI constraints are considered, such as buttons with fixed character limits.
Data export options
Beyond translators and editors, software localization involves technical specialists—localization engineers and programmers, whose tasks include configuring API connections between the client’s systems and Logrus IT tools. This enables system integration, extends CAT tool functionality, and allows workflow automation to save the client time and money.
1. A huge tech stack in development
When localizing software, we always consider which tools the client’s team is using. Today, there’s a vast range of available solutions for development, translation, and process management. Here are just a few examples:
The client’s choice of tools and programming languages determines the file formats we receive for localization. Common formats include XML, HTML, JSON, JS, MD, and DITA. Many development tools also support exporting text to XLIFF (XML Localization Interchange File Format), a bilingual format designed specifically for exchanging localizable data and based on XML markup.
At Logrus IT, we use our proprietary solutions, the latest CAT tools, and TMS platforms that can import and parse all the current file formats.
2. Separating translatable and non-translatable content
Preparing files for localization is rarely straightforward. While there are general best practices for storing user-visible text in software, many developers base decisions on their personal preferences and experience. They might also use uncommon or even custom-built tools. In some cases, smaller teams don’t plan ahead for localization at all, or are unaware that it requires special preparation.
All of this complicates the localization process. For example, text may be hardcoded in a way that makes it untranslatable without modifying the source code, especially since sentence structure and word order vary across languages. Certain symbols may also be encoded differently—for example, angle brackets might appear as the typical < and > in one file, and as escape sequences < and > in another.
Before localization begins, it’s important to identify elements that should not be translated. These can be categorized as follows: structural elements that define where the text belongs in the file; internal elements such as variables that will change dynamically; placeholders such as input hints in forms; and tags that handle formatting. All of these must remain unchanged in the translated file; however, this complicates the translator’s work. For example, tags—especially long ones—may be copied incorrectly, leading to errors in the final localized version.
To avoid such issues and optimize translator workflows, CAT tools include filters and regular expressions. These allow the program to recognize elements like tags based on set rules. Each tag is then turned into a single fixed token that can only be handled as a whole. The system can also automatically check how many of these tokens are present.
3. Interface constraints
In software localization, it’s not just the quality of the translation that matters—it’s also how the text appears in the interface. For example, when translating English into certain languages, the text often expands and no longer fits the UI.
To avoid such problems, you need to:
The most reliable solution is localization testing, which involves reviewing the translation in its final form. In addition, Logrus IT offers a Content Quality Audit service, which evaluates the final product in terms of user experience. Using standard or custom metrics, our auditors assess whether the interface, design, and content will appeal to the target audience, and how user-friendly the program or website is. We also check whether the localization adheres to relevant cultural and legal norms, as well as the client’s quality standards.
Our experience in the industry shows that the most critical factors for successful localization are:
Logrus IT has been localizing software for over 30 years. One of our first major clients in the 1990s was Microsoft, with the Microsoft Office suite. We have the expertise and personnel to adapt to any work environment, as well as proprietary solutions for optimized workflows. That’s why we can guarantee top quality and efficient turnaround in every localization project.
