Translation is replacing words. Localization is adapting the complete experience.
When I came to Japan as a student, there was often a translation available, but 'I still didn't get it'. The words were Japanese, but the cultural context was missing. Because of that experience, I made it my job to remove 'language barriers'.
What I focus on (English/Japanese/Dutch)
1. Readability: Short sentences, a calm tone
If information is chaotic, people disengage. I deliver only the essential info, without detours.
2. Style and Register: The right tone for the context
School forms, UI text, help articles, or official documents: I choose the right form of address and style for the reader.
3. Technical Limits: Does it fit in the button?
I take character limits in the interface into account and prevent the layout from breaking. Design and language go hand in hand.
4. Consistency: Using the same or similar terms
Inconsistency causes confusion. I build a terminology list (glossary) to ensure this.
5. Human Review: Reading aloud and checking by 'feel'
AI tools are useful, but the final check is human work. Only a person can properly judge cultural nuances and natural language.
What's the difference (example)?
- Example 1: “Submit” Button
- Direct translation: Indienen (Submit)
- Localization: Register / Send (depending on context)
- Example 2: Help text (long explanation)
- Direct translation: Converting the entire wall of text
- Localization: Shortening it to the core, and making the 'call to action' clear (e.g.: "You can..." → "Do...")
- Example 3: Official documents
- Direct translation: A literal, often wooden style
- Localization: Polite, clear, and avoiding ambiguity (with extra explanations or footnotes if necessary)
Tools and a realistic approach
I use simple tools, but the final check is always manual. For websites, I weave localization into the structure phase so that the content and design don't get in each other's way.
The checklist when in doubt
If you are debating between 'translation' or 'localization', think about the reader and the environment:
- Who is reading this? (An expert? Someone from a different background? Someone with limited technical knowledge?)
- Where are they reading this? (On a smartphone? In an app? On an official form?)
- What do they need to do? (Understand something? Sign up? Follow a procedure?)
The answer determines how deep the adaptation needs to go.
Removing the 'language barrier' and ensuring the user understands the message without getting lost. That is my definition of localization.