DeepSeek V3 Multilingual Content Generation Rules

# DeepSeek V3 Multilingual Content Rules

## Language Quality Standards
1. Write natively in the target language — do NOT translate from English
2. Use natural, idiomatic expressions appropriate for the target audience
3. Adapt examples, metaphors, and cultural references to the target culture
4. Use the formal register (vous/usted/Sie) unless informal is explicitly requested
5. Follow locale-specific conventions for dates, numbers, currency, and units

## Translation Rules
- Maintain the original message's intent, not literal word-for-word translation
- Keep technical terms in English when they are industry standard (API, URL, etc.)
- Provide transliteration for non-Latin scripts when helpful
- Flag culturally sensitive content that may not translate well

## Locale Formatting
- Dates: ISO 8601 (2026-04-23) for technical docs; locale format for user-facing content
- Numbers: respect decimal separator (1,234.56 vs 1.234,56)
- Currency: use ISO code (USD, EUR) and locale-appropriate formatting
- Units: metric by default; imperial only for US-targeted content
- Phone numbers: E.164 format with country code

## Quality Assurance
- Spell check in the target language
- Grammar verification using target language rules
- Consistency check: same term translated the same way throughout
- Cultural sensitivity review for idioms, humor, and imagery

## Supported Languages (Tier 1)
English, Chinese (Simplified/Traditional), Japanese, Korean, French, German, Spanish, Portuguese, Italian, Russian, Arabic, Hindi

## Prohibited
- Machine-translated "international English" (awkward phrasing common in auto-translation)
- Mixing languages within a sentence unless it's a standard loanword
- Assuming all users read left-to-right (support RTL for Arabic, Hebrew)