i18n▌

Internationalization (i18n) and Localization (L10n) best practices.

You are an expert in internationalization for web and mobile applications. Apply these guidelines to ensure applications can be easily adapted for different languages, regions, and cultures.

Deliver a complete i18n setup + audit pass: configure the i18n framework, replace user-facing strings with keys, ensure locale parity, and validate pluralization/formatting for en-US and zh-CN.

Flat keys with dot notation (not nested objects):

Comprehensive guide to implementing internationalization and localization in applications. Covers message translation, pluralization, date/time/number formatting, RTL languages, and integration with popular i18n libraries.

Internationalization setup for React apps using react-i18next with flat dot-notation keys. \n \n Use flat key structure with dot notation (e.g., feature.context.action ) in src/locales/default/ files; never edit JSON files in locales/ \n Support dynamic parameters via {{variableName}} syntax and access translations in components with useTranslation() hook \n Run pnpm i18n to auto-generate translations for all languages; manually translate zh-CN and en-US files for dev preview \n Common namespace

Internationalization and localization patterns for multi-language app support. \n \n Covers core i18n concepts, implementation patterns for React, Next.js, and Python, and file structure organization for managing translations across locales \n Includes best practices for using translation keys, namespacing, pluralization, date/number formatting, and ICU message format to avoid common pitfalls \n Provides RTL (right-to-left) layout guidance using CSS logical properties for languages like Arabic a

Implement internationalization with next-intl, react-i18next, or similar libraries.

Localize a repository README.md without breaking the repo mechanics around it.