Software localisation follows a structured process that combines technical expertise, linguistic competence and cultural understanding. Understanding how the process works helps software companies plan effectively and ensure quality in the localised product.
Preparation and internationalisation
Before localisation can begin, the software must be internationalised, which means that all translatable text is separated from the source code and the program supports different character encodings and special characters. The interface should also be able to handle text expansion if the translated texts are longer. This is a technical prerequisite that developers must implement. Localisation packages are created including all translatable strings extracted to file formats that translators can work with, together with screenshots and contextual information to help translators understand where text appears. It is also important to include style guides and term lists with key product terminology.
Software localisation – translation and cultural adaptation
Translators with software experience translate user interfaces taking into account technical constraints such as character limits, system messages and error messages, so that they are clear and usable, as well as translating help documentation adapted for the target audience’s technical level. Cultural adaptation includes reviewing icons, colours and images for cultural appropriateness, as well as adapting examples and references to locally relevant alternatives. Copywriters might need to rework marketing text in the software so that messages resonate with the target market. This goes beyond direct translation and requires creative adaptation.
Technical implementation and testing
Translated strings are reintegrated into the software through localisation tools. Technical testing ensures that formats for dates, times, currencies and numbers function correctly, that text expansion does not cause layout problems where text is truncated or overlaps and that special characters and different alphabets display correctly. Functional testing with native speakers tests the localised software in context to verify that all functions work properly, translations are correct in their context and that the user experience feels natural and intuitive for the target market.
Quality assurance and continuous improvement
The four-eyes principle is applied where at least two people review the translations. Local reviewers with product knowledge validate that terminology and tone are correct. User feedback after launch is collected to continuously improve the localisation. For agile development processes, a continuous localisation process is established where new strings and functions are localised on an ongoing basis after release rather than in large batches. An experienced translation partner with localisation expertise works according to ISO standards with ISO-certified system support and uses professional localisation tools that handle different file formats, translators with software experience and technical understanding, software term bases for consistent terminology, functional testing with native speakers and continuous localisation processes that integrate with agile development. Read more about Fluid’s working methods here.
Read more about software localisation in our case study about ESGgo!