principle-i18n

What problem does it solve?

Prevents internationalization bugs that only appear after adding new locales, such as incorrect date/time/number/currency formatting, broken pluralization, and RTL layout issues.

Core Features & Use Cases

• Locale-Aware Formatting: Use proper locale APIs for dates, numbers, and currency, avoiding hard-coded formats or manual string assembly.
• Time Zone Correctness: Persist timestamps in UTC and render in the user’s local time at the display edge to avoid DST and comparison errors.
• Plural, Grammatical, and Catalog Safety: Use CLDR-based plural categories and ICU/gettext-style message catalogs with reorderable placeholders, not concatenated strings.
• Bidirectional Layout & Encoding Hygiene: Ensure right-to-left rendering uses correct directionality, logical CSS, and bidi-safe text isolation; enforce UTF-8 end-to-end.

Quick Start

Audit your UI strings and formatting code so dates, numbers, currency, pluralized messages, and RTL layout all use locale-aware APIs and translation-safe message catalogs before shipping another language.