i18n and L10n (Internationalization and Localization)
i18n stands for internationalization (the 'i', 18 letters, 'n'). L10n stands for localization ('l', 10 letters, 'n'). Internationalization is the engineering work that makes a product capable of supporting multiple languages. Localization is the content work that actually adapts it for a specific locale.
A well-internationalized application extracts all user-facing strings into locale files (like JSON or PO files), uses Unicode throughout, and avoids hard-coding assumptions like left-to-right text direction, Western date formats, or fixed-width number display. Internationalizing a product that wasn't designed for it is expensive — fixing it retroactively is always harder than building it right from the start.
Localization then fills in those locale files with appropriate translations and locale-specific content. A fully localized product also adapts images (avoiding culturally specific hand gestures or imagery), date/number formats, right-to-left layout for Arabic and Hebrew, and legal/compliance content per jurisdiction.
Key concepts
- i18n = engineering: prepare the product to support any locale (extract strings, Unicode, RTL support)
- L10n = content: actually translate and adapt for a specific locale
- The cost ratio is roughly 1× for i18n, 10× for L10n — invest in i18n first
How Vernacia uses this
Vernacia handles the translation layer of L10n — converting document text into the target language. Engineering concerns (string extraction, locale file management, RTL layout) are separate from document translation.
Related terms
Translate PPTX, PDF, DOCX, and 11 more formats — free to start.
Try Vernacia free