i18n-localization

原文涵盖的主题

• i18n & Localization
• 1. Core Concepts
• 2. When to Use i18n
• 3. Implementation Patterns
• React (react-i18next)
• Next.js (next-intl)
• Python (gettext)
• 4. File Structure

Internationalization (i18n) and Localization (L10n) best practices. -- | Term | Meaning | |------|---------| | i18n | Internationalization - making app translatable | | L10n | Localization - actual translations | | Locale | Language + Region (en-US, tr-TR) | | RTL | Right-to-left languages (Arabic, Hebrew) | -- | Project Type | i18n Needed? | |--------------|--------------| | Public web app | ✅ Yes | | SaaS product | ✅ Yes | | Internal tool | ⚠️ Maybe | | Single-region app | ⚠️ Consider future | | Personal project | ❌ Optional | -- -- -- Use translation keys, not raw text Namespace translations by feature Support pluralization Handle date/number formats per locale Plan for RTL from the start Use ICU message format for complex strings Hardcode strings in components Concatenate translated strings Assume text length (German is 30% longer) Forget about RTL layout Mix languages in same file -- | Issue | Solution | |-------|----------| | Missing translation | Fallback to default language | | Hardcoded strings | Use linter/checker script | | Date format | Use Intl.DateTimeFormat | | Number format | Use Intl.NumberFormat | | Pluralization | Use ICU message format | -- -- Before shipping: [

这里只展示节选，请以完整原文和当前要求为准。