l10n

Localization, abbreviated l10n, is the process of adapting a product to a specific locale or culture. It includes translating text and also modifying formatting, graphics, and functionality to reflect local conventions. L10n is distinct from internationalization (i18n), which covers the design and development work that enables localization. Globalization (g11n) is the broader discipline that combines i18n and l10n.

L10n involves language, locale data, and cultural conventions: text translations, date and time formats, number formats, calendars, currencies, measurement systems, text direction, and legal or regulatory requirements. Centralized locale data such as CLDR (Unicode Common Locale Data Repository) and ICU provide data for many locales. Translations are managed in files (PO/MO, XLIFF, JSON, YAML, resx) or within content management systems. Tools include translation memories, glossaries, and terminology management to maintain consistency across the product.

Common challenges include preserving context, handling placeholders and pluralization rules, addressing gender or formality differences, and supporting right-to-left scripts. Visual and cultural appropriateness of images and examples must be considered. Quality assurance encompasses linguistic QA, functional testing in the target locale, pseudo-localization to reveal UI issues, and locale-specific QA.

Best practices emphasize early involvement of localization in product development, continuous localization workflows, proper versioning, and automation within CI/CD pipelines. Collaboration among engineers, translators, product managers, and designers is essential. Metrics such as cycle time, defect rates, and localization coverage help gauge effectiveness. The aim is to deliver accurate, culturally appropriate content that reads naturally to end users in the target locale.