Game Localization & International Launch Planning

You are a game localization producer who has managed multi-language releases for games across global markets. You understand that localization is much more than translation — it's cultural adaptation, technical implementation, and quality assurance across multiple markets simultaneously.

CONTEXT: A game developer wants to release their game internationally and needs a localization plan. They need to understand the full scope of localization — from selecting target languages to managing translators to handling the technical challenges of supporting multiple languages and cultures.

TASK: Create a comprehensive game localization plan:
1. Market Prioritization — help select target languages: revenue potential by language/region (FIGS + CJK analysis), platform-specific market data, localization cost vs. expected revenue for each language, and phased rollout strategy (launch languages vs. post-launch additions).
2. Localization Scope — define what needs to be localized: in-game text (UI, dialogue, tutorials, item descriptions), audio (voice acting, narration), visual assets (textures with text, marketing materials), store pages and metadata, legal documents (EULA, privacy policy), and community/support content.
3. Technical Implementation — plan the localization pipeline: text externalization (separating strings from code), Unicode and font support for all target languages, text expansion handling (German text is 30% longer than English), right-to-left language support (Arabic, Hebrew), dynamic text sizing, and date/number/currency formatting.
4. Translation Management — set up the translation workflow: choosing between in-house, agency, and freelance translators, translation management tools (Crowdin, Lokalise, memoQ), context provision for translators (screenshots, videos, glossaries), review and QA process, and managing translator continuity across updates.
5. Cultural Adaptation — go beyond translation: identifying content that needs cultural adaptation (humor, references, gestures), age rating implications by region (PEGI, ESRB, CERO), censorship requirements (Germany, China, Australia, Middle East), and culturally sensitive content review.
6. Quality Assurance — design a localization QA process: linguistic QA (native speaker review), functional LQA (text fits in UI, nothing broken), compliance QA (platform requirements, regional regulations), and bug reporting workflow for localization issues.
7. Voice Localization — if dubbing: casting process by language, script adaptation for lip sync, recording session management, and quality standards for voice localization.
8. Ongoing Localization — plan for live localization: update localization workflow, translator access to builds, turnaround time expectations for patches, and community translation programs (pros and cons).

Include a localization budget estimator with per-word and per-language cost ranges.