Translation Is Not Localisation

9 July 2026 · 2 min read

blog contents
  1. What the words hide
  2. Text that grows and text that shrinks
  3. Strings belong outside the code
  4. The parts machines still get wrong

read

Translation swaps the words. Localisation changes the assumptions underneath them: currencies, name and address formats, dates, reading direction, what counts as polite, and which examples make sense at all. A perfectly translated page can still feel foreign, and that feeling costs conversions long before anyone can name why. The parts that break are rarely the sentences.

What the words hide

A form expecting a first name and a last name will fail people whose names do not split that way. A date written as digits is read two different ways depending on where the reader lives.

None of this is a translation error, and all of it is visible to the visitor within seconds of arriving.

Text that grows and text that shrinks

Copy translated out of English usually gets longer, sometimes by a third. Interfaces built to fit the original break: buttons wrap, tables push sideways, headings collide with whatever sits beside them.

The cheap fix is to design for the longest language you plan to ship rather than the one you happened to write first.

Strings belong outside the code

If text lives inside the code, every language is a development task and every typo is a deployment. If it lives in files, translation becomes a content job and adding a market stops being an engineering project.

This one decision determines whether the second language costs a fraction of the first or the same again.

  • Every visible string in a file, not in the source
  • One key per phrase, not one per screen
  • Plurals handled by the language, not by joining strings
  • A record of what was translated, so the next update is a diff

The parts machines still get wrong

Machine translation is genuinely good at volume and genuinely bad at exactly the places that matter: the button people press, the error shown when something breaks, the legal line.

A sensible split is machine for bulk content and a person for anything a user will act on or be bound by.

questions

Can we launch with machine translation?

For documentation and long content, often yes. For the interface, the pricing page and anything legal, no. Those are short, heavily read and unforgiving, which is exactly where a person is cheapest.

Which language should we add first?

The one where you already see traffic you cannot serve. Support tickets and site search terms will tell you before any market study does, and they cost nothing to read.

How do we keep versions in sync?

Treat the original as the source and everything else as derived from it. When a string changes, its translations get marked stale automatically instead of silently drifting out of date.

More on this track

  1. What You Own When a Project Ends Handover is the clause nobody reads until they need it. A complete one is four things: source code in a repository you control, accounts and domains registered to you, documentation a new developer can start from, and a period where the previous team still answers questions. If any of the four is missing, you are renting your own product. 12 August 2026 · 4 min read
  2. Build or Buy, Decided Before Anyone Codes Build when the process is the thing you compete on. Buy when the process is ordinary and you have just never standardised it. Most requests for custom software are really requests to avoid changing how the company works, which is the most expensive possible reason to build anything. The honest test: could a competitor copy your workflow from a screenshot and gain nothing? 28 July 2026 · 2 min read
  3. Why Your MVP Keeps Growing An MVP grows because nobody wrote down what it was for. Without a single task it has to support, every request sounds equally reasonable and the honest answer to each one is yes. The fix is not discipline, it is a definition: name the one task a real user must be able to finish, then judge every request by whether that task works without it. 24 June 2026 · 2 min read