Translation, localization, internationalization, culturalization, LQA: what each word actually means

Job postings, vendor pitches, and casual conversation all use translation, localization, internationalization, culturalization, and LQA as if they were synonyms. They are not. Each term names a distinct piece of work, usually done at a different stage and often by a different person. Confusing them is not just a vocabulary problem — it leads to buying the wrong service or assuming a role covers work it does not.

Translation

Translation is converting text from one language to another while preserving meaning. It is the narrowest of these terms and the one most people mean when they say localization casually. A translator's job is the words: does this sentence say the same thing in the target language, in a natural register, without losing nuance.

Translation alone does not touch formatting, layout, or whether the sentence structure will even fit the interface it appears in. A perfectly accurate translation can still break a game if nobody accounted for the space it needs or the placeholders it must preserve.

Internationalization (i18n)

Internationalization is engineering work, not language work, and it usually happens before any translation exists. It means structuring your software so it can support multiple languages at all: separating text from code, supporting Unicode text encoding, avoiding assumptions like fixed string lengths or a single word order, and building in the plumbing (locale switching, string tables, pluralization rules) that translation will later plug into.

A codebase that has not been internationalized cannot be properly localized no matter how good the translation is — the strings are not even in a place a translator can reach, or the UI cannot render what comes back.

Localization (l10n)

Localization is the umbrella process of adapting a product for a specific locale, and it includes translation as one part of a larger set of changes: date and number formats, currency, sorting order, right-to-left layout where applicable, and UI adjustments for text that runs longer or shorter than the source. Localization is what makes a product feel native to a locale, not just readable in its language.

Culturalization

Culturalization goes further than adapting formats — it adapts content itself so it lands correctly with a specific audience, and it usually applies at the level of story, imagery, humor, and references rather than individual sentences. A joke that depends on wordplay in the source language may need to be replaced with a different joke entirely, not translated, because a literal translation would simply not be funny. Culturalization decisions are typically made by someone close to the content — a narrative lead or a specialized localization producer — not by a translator working sentence by sentence.

LQA — localization quality assurance

LQA is the checking stage that comes after translation is integrated into the actual product: playing or reviewing the localized build to catch what text-only review cannot. This includes text that overflows its UI container, broken or missing placeholders, inconsistent terminology between screens, and text that is technically correct but displays incorrectly in context. LQA is distinct from translation review (checking whether the words are accurate) because it checks the words in the environment they actually appear in.

Why the distinctions matter

These are not academic distinctions — they determine who does what and what you are actually buying:

• A vendor quoting 'translation' may not include LQA, formatting adaptation, or culturalization unless you ask specifically
• Internationalization is engineering work your own team has to do before any outside translation service can be effective — no vendor can retrofit a codebase for you
• Culturalization decisions belong with people who understand the content's intent, not with a translator working line by line without context
• LQA needs to happen against the real build, in context — a spreadsheet of translated strings cannot substitute for it