I18n terms
Internationalisation ensures your software can be adapted for any language, region, or culture without engineering rework. This category covers locale handling, Unicode, pluralisation rules, date and number formatting, right-to-left layouts, translation workflows, and the subtle bugs that appear when you assume everyone uses your date format, currency, or alphabet.
More on i18n
History
Internationalization (i18n) emerged in the 1980s as software began crossing borders, initially driven by the need to support multiple languages in operating systems and applications. Early efforts focused on character encoding standards—ASCII's limitations led to multi-byte schemes and eventually Unicode, which became the foundation for handling scripts beyond Latin characters. The 1990s and 2000s saw formalization through standards like RFC 2822 for email, ICU (International Components for Unicode) libraries, and locale frameworks that standardized date, time, number, and currency formatting across regions. Key milestones included Unicode 1.0 (1991), widespread adoption of UTF-8 encoding, and the emergence of translation management systems and plural rule specifications (CLDR). Today, i18n is integral to web development and software design, spanning bidirectional text rendering, timezone handling, collation rules, and cultural adaptation, with practices deeply embedded in frameworks and continuous localization pipelines.
Key concepts
- Unicode Fundamentals
- Character Encoding
- Locale-Aware Formatting
- Bidirectional Text (BiDi)
- Timezone Handling
- Pluralisation Rules Across Languages
- Translation Management
Best references
-
Unicode Standard The authoritative specification for Unicode character encoding, essential for understanding character encoding, bidirectional text, and Unicode fundamentals in internationalization.
-
ICU (International Components for Unicode) Documentation Comprehensive reference for locale-aware formatting, collation, pluralization rules, and the ICU Message Format standard used across multiple programming languages.
-
W3C: Structural Markup and Right-to-left Text in HTML Authoritative W3C guidance on handling bidirectional text and right-to-left language support in web applications.
-
CLDR (Common Locale Data Repository) The primary source for locale-specific data including collation rules, pluralization patterns, number/date formatting conventions, and timezone information across all languages.
-
PHP Internationalization Extension (Intl) Manual Official documentation for PHP's intl extension, covering locale-aware formatting, collation, and internationalization functions built on ICU.
-
IETF BCP 47: Matching of Language Tags The standard specification for language tag syntax and locale identifiers, foundational for all localization and translation management systems.
Typed relationships here
Edges touching a i18n term.
- PHP Intl Extension — Unicode Leverages Unicode Fundamentals 1d
- PHP Intl Extension — Unicode Realizes PHP Intl Extension 2d
- ICU Message Format Often seen in Translation Management 3d
- Right-to-Left Language Support Often seen in PHP Intl Extension 4d
- Right-to-Left Language Support Requires Unicode Fundamentals 4d
🤖 AI Guestbook — i18n educational data only
Timezone Handling
PHP 5.0+