Localisation Is Not Just Translation
Translation changes the words. Localisation changes what needs to change so the result fits a place: formats, examples, images and assumptions.
Two different jobs
Translation converts text from one language to another. Localisation adapts a whole product or document so it feels native to a particular region, which often means changing things that are not words at all. A perfectly translated page can still feel foreign, or even break, if only the language was handled.
What localisation touches
- Formats. Dates, times, currencies, decimal marks, phone and address layouts.
- Units. Distance, weight, temperature and paper sizes.
- Examples and names. Sample people, places and prices that make sense locally.
- Images and colour. Pictures and symbols that read differently in different cultures.
- Layout. Text that grows or shrinks when translated, and scripts that run right to left.
Small mistakes, large effects
A date written 03/04 means March in one country and April in another; a form that rejects a valid local postal code loses the customer; a colour that signals celebration in one place signals mourning in another. None of these is a translation error, and all of them are localisation errors.
Test with a real local reader
The surest check is a person who lives in the target market reading the result as a user, not as a proofreader. They notice at once what feels foreign: an example that makes no sense locally, a form that rejects a valid address, a date in the wrong order, a tone that is too blunt or too formal. One such read catches more than a long checklist, because a local reader is testing the whole experience rather than the words alone.
Plan for it early
Localisation is far cheaper when a product is designed to allow it: text kept separate from code, room left for longer words, and no meaning baked into an image that would need redrawing. Retrofitting it later is possible but slow and error-prone.
Leave room for the words to change
A sentence rarely keeps its length when it changes language: some translations run a third longer than the original, others shrink, and a few reverse direction entirely. A layout built tightly around one language breaks when another arrives, with buttons that clip their labels and headings that wrap awkwardly. Designing with slack, flexible boxes, no text baked into images, and a quick check in the longest target language, saves far more work than fixing each overflow by hand later.
A short test
- Would a local reader notice anything was translated?
- Do all the formats, units and examples match local habit?
- Does every form accept valid local input?
- Do the images and symbols carry the intended meaning here?
When the answer to all four is yes, the work is localised, not merely translated, and that is usually the difference between a product people tolerate and one they trust.
Revised 2026-11-10