Software localisation
Language that fits the product—and the build.
Interface and software content localised with respect for context, variables, character limits and release workflows.
What the work requires
Good software localisation is part linguistic work and part systems thinking. Strings arrive out of sequence, placeholders carry logic and short labels may have several meanings. Context and technical controls prevent expensive rework.
Project fit
Common product constraints
01
Variables, markup and non-translatable tokens
02
Limited visual context
03
Character limits and responsive layouts
04
Continuous releases and changing source strings
How we approach it
Built for release cycles
01
File analysis
Resource structure, encoding, variables and translatable content are checked before work begins.
02
Contextual translation
Screenshots, developer notes and terminology reduce ambiguity.
03
Linguistic QA
In-context review identifies truncation, layout and functional-language issues.
Typical outputs
A clear delivery package.
Localised resource files
Terminology and style decisions
Query log
LQA findings when in scope
Start a project
Get a quote