Software Localisation
UI, strings, online help and software documentation — localised in context, format- and variable-safe, consistent across releases.
What is Software Localisation?
Software localisation is the adaptation of software to the language and conventions of a target market, and goes beyond simply translating the interface texts. What gets localized is the user interface (UI), menus, messages, online help, and documentation.
At the same time, formats for date, time, numbers, currency, and units of measurement, character sets, and the space and context constraints of the interface are all taken into account. This way, the software feels in the target market as if it had been developed there: usable, unambiguous, and consistent across every release.
Localised in context
Strings are checked where they appear. String lengths, abbreviations and interaction logic match the interface, not just the dictionary.
Format- and variable-safe
Placeholders, variables and markup remain untouched; only the content is translated.
Consistent across releases
Translation Memory and terminology ensure consistent naming across versions and platforms.
Distinction from related services
| Area | What it is about | Where we draw the line |
|---|---|---|
| SEO / website localisation | Your website's visibility in the target market | Keyword research, hreflang and meta layer — for discoverability, not for the application itself. |
| Technical translation | Classic technical documentation | Operating instructions, data sheets without a software context: documentation language rather than UI/string context. |
| AI-assisted translations with post-editing | Large text volumes | For large text volumes, AI-assisted translation with post-editing delivers speed and scalability, complemented by our four-eyes principle in line with ISO 17100. |
As a rule of thumb: When it comes to the application itself, such as strings, UI, apps or your software documentation, you are in the right place. If, on the other hand, it's about the website, SEO and website localisation is the right approach.
What we localise
User interface (UI)
- menus, buttons, dialogues
- labels and tooltips
- interaction and navigation logic
Messages and system texts
- error and status messages
- notifications and notices
- validation and help texts
Online help and documentation
- help systems and manuals
- release notes
- tutorials and knowledge base
Data and content
- database records
- shop and catalogue data
- templates and glossaries
App and store
- mobile app strings (iOS/Android)
- app store listings
- screenshots and marketing texts
Web applications
- SaaS and portal interfaces
- configuration and email templates
- forms and workflows
File formats and structure-preserving integration
We work directly in the standard localisation formats. Only the content is translated, with placeholders and markup preserved, and the reviewed target text is fed back into the same place. This makes the workflow reproducible for every update.
Not seeing the format you need? Feel free to get in touch. In most cases, content can be extracted and reintegrated without loss.
The localisation process
Internationalisation check (i18n)
We check that text is clearly separated from code and that there is room for longer languages.
String export
Content is segmented and exported from the source format with location references.
Localisation with TM & terminology
Native-speaker specialised translators carry out localisation, supported by terminology and translation memory.
Length, context and variable checks
Pseudo-localisation in advance where needed; strings fit in buttons and dialogues, and variables stay protected.
Revision according to the four-eyes principle (ISO 17100)
A second qualified translator checks the translation against the source text.
Reintegration
The reviewed target text is fed back into the same place in the source format.
Localisation testing
Final visual check of the live interface on request: Display, line breaks, special characters.
Triple ISO-certified
Localisation in accordance with ISO 17100 revision in the four-eyes principle and post-editing of machine translation in accordance with ISO 18587 and quality management in accordance with ISO 9001. Translation memory and terminology ensure consistency across all releases, as only the changed content is re-localised for updates.
Software localisation or another service?
Software localisation (this page)
UI strings, menus, messages, online help, app and software documentation. Context-, format- and variable-safe and consistent across releases.
Better choose a different service
for websites and search we recommend, SEO translations. For classic documentation without software relevance, we recommend Technical Translations. For very large text volumes, we recommend AI-assisted translations with post-editing.
Related expertise from COMLOGOS
Medical Technology & SaMD
UI texts and online help for software as a medical device, aligned consistently with the device documentation. Learn more
Mechanical Engineering & HMI
User interfaces and control texts for international commissioning. Learn more
Language Technology
Translation memory and terminology as the foundation for consistent localisation. Learn more
Frequently asked questions about software localisation
What is the difference between translation and software localisation?
A translation transfers texts from one language to another. Localisation also adapts the software to the conventions of the target market: date, number and currency formats, units of measurement, character sets, as well as interface's space and contextual constraints. This ensures that the application functions in the target market as if it were developed there.
Which file formats do you handle?
We handle XLIFF, PO/gettext, JSON, Java .properties, .NET RESX/RESW, iOS .strings, Android strings.xml, YAML, XML and HTML, among others. Placeholders, variables and markup are preserved and only the content is translated.
How do you ensure that UI texts are not too long?
We achieve this through context and length checks, pseudo-localisation before translation where necessary, and agreed shortening rules. This ensures that strings fit within buttons, menus, and dialogues without being cut off.
Are variables and placeholders preserved?
Yes. Placeholders, format strings and variables are protected and not translated, and word order is adapted wherever necessary for the target language.
Do you ensure consistency across multiple releases?
A translation memory and a terminology database ensure consistency. For updates, only the changed content is retranslated and the reviewed content remains stable across versions and platforms.
Do you also handle the software documentation?
Yes. We localise online help, manuals and release notes, aligning them with the interface and ensuring consistent terminology and ISO 17100-compliant reviews.
Ready to roll your software out internationally?
Send us a sample package, such as resource files, screenshots or online help. You will receive a concrete assessment of the required format, effort and terminology setup. Initial quote within 24 hours, NDA available on request.
ISO 17100 · ISO 18587 · ISO 9001 · Translation Memory · standard NDA · 24h quote
