Internationalization (i18n) Implementation Guide

You are a localization engineer who implements i18n systems. Design an internationalization strategy for this application.

Application: [WEB / MOBILE / BOTH]
Framework: [REACT / VUE / NEXT.JS / REACT NATIVE]
Target languages: [LIST LANGUAGES]
Content types: [UI / MARKETING / LEGAL / USER-GENERATED]
Existing content volume: [SIZE]
Update frequency: [HOW OFTEN CONTENT CHANGES]

Provide:

**i18n Architecture**
```
/locales
├── en/
│   ├── common.json
│   ├── auth.json
│   └── errors.json
├── es/
└── fr/
```

**Translation Format**
```json
{
  "greeting": "Hello, {{name}}!",
  "items": {
    "one": "{{count}} item",
    "other": "{{count}} items"
  },
  "price": "{{amount, currency}}"
}
```

**Implementation**

```[language]
// i18n configuration
// Provider setup
// Translation hooks
// Language switching
```

**Key Naming Convention**
```
namespace.section.element.variant
auth.login.button.submit
auth.login.error.invalid_credentials
```

**Pluralization**
```[language]
// Plural rules implementation
// ICU format support
// Edge cases (0, 1, 2, few, many, other)
```

**Date/Time/Number Formatting**
```[language]
// Intl.DateTimeFormat
// Intl.NumberFormat
// Relative time formatting
// Timezone handling
```

**RTL Support**
- CSS considerations
- Component adjustments
- Icon mirroring
- Layout changes

**Translation Workflow**
1. Developer adds key
2. Default language text
3. Extract to translation file
4. Send to translators
5. Review and import
6. Deploy

**Quality Assurance**
- Pseudo-localization testing
- String length testing
- Context for translators
- Screenshot references

**Performance**
- Lazy loading translations
- Caching strategy
- Bundle optimization

**SEO for Multilingual**
- URL structure
- hreflang tags
- Sitemap per language
- Language detection

**Tools Integration**
- Crowdin / Lokalise / Phrase
- CI/CD integration
- Translation memory

You are a localization engineer who implements i18n systems. Design an internationalization strategy for this application.

Application: [WEB / MOBILE / BOTH]
Framework: [REACT / VUE / NEXT.JS / REACT NATIVE]
Target languages: [LIST LANGUAGES]
Content types: [UI / MARKETING / LEGAL / USER-GENERATED]
Existing content volume: [SIZE]
Update frequency: [HOW OFTEN CONTENT CHANGES]

Provide:

**i18n Architecture**
```
/locales
├── en/
│   ├── common.json
│   ├── auth.json
│   └── errors.json
├── es/
└── fr/
```

**Translation Format**
```json
{
  "greeting": "Hello, {{name}}!",
  "items": {
    "one": "{{count}} item",
    "other": "{{count}} items"
  },
  "price": "{{amount, currency}}"
}
```

**Implementation**

```[language]
// i18n configuration
// Provider setup
// Translation hooks
// Language switching
```

**Key Naming Convention**
```
namespace.section.element.variant
auth.login.button.submit
auth.login.error.invalid_credentials
```

**Pluralization**
```[language]
// Plural rules implementation
// ICU format support
// Edge cases (0, 1, 2, few, many, other)
```

**Date/Time/Number Formatting**
```[language]
// Intl.DateTimeFormat
// Intl.NumberFormat
// Relative time formatting
// Timezone handling
```

**RTL Support**
- CSS considerations
- Component adjustments
- Icon mirroring
- Layout changes

**Translation Workflow**
1. Developer adds key
2. Default language text
3. Extract to translation file
4. Send to translators
5. Review and import
6. Deploy

**Quality Assurance**
- Pseudo-localization testing
- String length testing
- Context for translators
- Screenshot references

**Performance**
- Lazy loading translations
- Caching strategy
- Bundle optimization

**SEO for Multilingual**
- URL structure
- hreflang tags
- Sitemap per language
- Language detection

**Tools Integration**
- Crowdin / Lokalise / Phrase
- CI/CD integration
- Translation memory