Game Localization · Glossary
i18n and l10n — Internationalization and Localization in Game Development
i18n (internationalization) and l10n (localization) are two distinct phases of adapting a product for global markets. i18n is engineering work — designing the codebase to support multiple locales without structural changes. l10n is adaptation work — translating and culturally adjusting content for each target locale. The number abbreviations replace the characters between the first and last letter: ‘i’ + 18 characters + ‘n’ = internationalization; ‘l’ + 10 characters + ‘n’ = localization.
Internationalization (i18n) in Game Development
Internationalization is the engineering foundation that makes localization possible without modifying source code. In game development, i18n work includes: String externalization — removing all hardcoded text from source code and UI scenes into string files (.po, .xliff, .json) with unique IDs. UI layout flexibility — designing interfaces that accommodate text expansion (German runs 30–40% longer than English), text contraction (Chinese can express the same meaning in significantly fewer characters), and bidirectional text (Arabic, Hebrew read right to left). Font system configuration — ensuring the game’s font pipeline can render CJK characters, Arabic script, Cyrillic, and other non-Latin writing systems. Date, time, number, and currency formatting — using locale-aware formatting rather than hardcoded Western conventions. Asset pipeline separation — isolating locale-specific art, audio, and video so they can be swapped per locale without recompiling the base game.
Localization (l10n) in Game Development
Localization is the per-locale adaptation work performed once internationalization is complete. l10n work includes: Text translation — translating all externalized strings from the source language into each target language. Voice-over localization — subtitling, dubbing, or replacing audio assets. Cultural adaptation — adjusting idioms, references, humor, and scenarios that would not translate culturally. Art localization — adapting images, UI elements, or promotional materials that contain text or culturally specific content. Compliance — adjusting content for regional ratings requirements (CERO in Japan, USK in Germany). LocQA — testing the localized build in-engine to catch rendering failures, layout breaks, and context-dependent translation errors.
Why i18n Must Come Before l10n
Attempting localization on a game that has not been internationalized causes engineering rework at every step. If text is hardcoded in source files, translators cannot access it without a developer extracting it manually — and every update requires a developer touch. If the UI was designed only for English string lengths, CJK text of different lengths will break layouts. If the font system does not support Arabic, the entire RTL adaptation requires a separate engineering sprint. The cost of internationalization added retroactively is 3–5x the cost of doing it upfront. The rule is absolute: design for i18n before the first string is written; do l10n after i18n is complete.
SandVox and i18n and l10n
SandVox can advise on i18n requirements as part of project scoping — identifying string externalization gaps, font coverage issues, and layout constraints before translation begins. For studios earlier in development, we flag i18n issues that would require re-work if left unaddressed. For studios ready to localize, we handle the full l10n workflow once i18n is in place.
Related terms: What Is Localization · String Externalization · Game Internationalization · Character Encoding · Text Expansion
Frequently Asked Questions
Can I localize a game that hasn’t been fully internationalized?
Yes, but with limitations and extra cost. If strings are partially hardcoded, translators can only work with the externalized strings — a developer must manually extract and re-integrate the rest. If the UI is not flexible, layout testing will reveal breaks that require engineer time to fix. If fonts do not support a target language, a font integration sprint is required before LocQA can begin. The work is possible; it just costs more than if i18n had been done upfront.
What does the ’18’ in i18n stand for?
The ’18’ represents the 18 letters between the ‘i’ and ‘n’ in ‘internationalization.’ The abbreviation was coined in the 1970s/1980s in the software engineering community for use in systems where long technical terms were impractical in variable names or commands. Similarly, l10n = ‘l’ + 10 characters + ‘n’ = ‘localization.’ The abbreviations are standard across the global tech industry.
How do Unreal Engine and Unity handle i18n?
Unreal Engine handles i18n through FText (the localization-aware text type), StringTable assets, and the Localization Dashboard. FText tracks source text changes and flags strings for re-translation when source changes. Unity’s Localization Package (com.unity.localization) handles i18n through String Tables and Asset Tables, with Smart String support for pluralization and locale-sensitive formatting. Both engines require explicit configuration for CJK font rendering and RTL text layout — this configuration is part of the i18n engineering work, not automatic.
Need Expert Game Localization?
SandVox provides end-to-end game localization including i18n and l10n — for narrative games, mobile titles, webtoons, and interactive fiction.