ai-translated-localizationlisted

# AI-Translated Localization ## When to invoke **Scope decisions:** - Starting a new App and deciding which locales to support. - Choosing a string catalog format (`.strings` vs `.xcstrings`). - Planning the translation flow (manual / agency / AI agent). - User asks "are 7 locales too many", "how do translations enter git", "how to handle multi-locale App Store metadata". **Execution:** - Adding new user-facing strings (UI keys, GC titles, ASC metadata, achievement descriptions) and need to fill out their non-source locales. - Refreshing strings whose source language changed (`extractionState: stale` entries in xcstrings). - Auditing whether a release's xcstrings is complete (every key has every locale, no `<TRANSLATE>` placeholders shipping). ## Default decisions ### Default 7 locales | Locale | Code | Notes | |---|---|---| | English | `en` | Catalog `sourceLanguage`; translation source for the fan-out | | Traditional Chinese | `zh-Hant` | Primary language — author-written alongside `en`, never AI-translated | | Japanese | `ja` | Largest adjacent market outside the Chinese sphere | | Simplified Chinese | `zh-Hans` | Converted from `zh-Hant` + Mainland phrasing review | | Spanish | `es` | World's second largest native-speaker base | | Thai | `th` | Southeast Asia representative | | Korean | `ko` | High-penetration Asian market | - Locale codes are the **script-based BCP-47 forms** (`zh-Hant` / `zh-Hans`), not region forms (`zh-TW` / `zh-CN`) — matches the committed c