practiceEngineering & architecture

Internationalization (i18n)

Internationalization prepares a product’s architecture and content handling so it can support different languages and regional conventions.

Download Markdown (.md)

01What it means

Internationalization, commonly abbreviated i18n, designs a product so localization can occur without fundamental reengineering. It includes character handling, translatable resources, language metadata, layout direction, and locale-sensitive formatting. Localization supplies a particular market’s adaptation; internationalization creates the capability to support it.[1][2]

02Why it matters

Hard-coded text, narrow name fields, and assumptions about date formats create expensive barriers when a product expands. Preparing the shared system reduces repeated engineering work and makes language support more consistent across workflows.

03When to use it

Use it when a product serves or expects to serve multiple language communities or regions. Apply basic robust text handling even before translation. Avoid building a large market-specific system without evidence of need; prepare extensible foundations and test real target cases.

04How it works

  1. Identify target language, script, formatting, and input requirements.
  2. Use suitable character encoding and separate user-facing messages from code.
  3. Provide locale-aware number, date, and plural handling instead of concatenating translated fragments.
  4. Support flexible layouts and right-to-left direction where needed.
  5. Test with expanded strings, mixed scripts, and representative locales before localizing.

05A practical example

Example

A booking product stores messages separately and formats amounts through locale-aware utilities. Testing longer translations reveals clipped buttons before translators begin. Persian testing also exposes direction problems in mixed phone-number and address text.

06Where it breaks

Internationalization does not produce accurate translations or establish market fit. Locale choices can be more nuanced than country or language alone. Retrofitting assumptions in data models, search, and third-party integrations can still be costly.

Common mistakes

  • Equating internationalization with translating a string file.
  • Concatenating fragments whose grammar changes by language.
  • Assuming every user in a country has the same language and formatting preferences.

07Sources

  1. Localization vs. InternationalizationW3C · Technical guidanceLocalization vs. Internationalization
  2. Internationalization Quick Tips for the WebW3C · Technical guidanceInternationalization Quick Tips for the Web
View saved topics

Start typing to search titles, definitions, categories, and frameworks.