localize

Port provenance: adapted from the pinned upstream source at 984023ddac0d5e27624f2baacde6105e45de375f under MIT; see the repository parity ledger for the exact path and blob.

Localization Pipeline

Localization is not just translation — it is the full process of making a game feel native in every language and region. Poor localization breaks immersion, confuses players, and blocks platform certification. This skill covers the complete pipeline from string extraction through cultural review, VO recording, RTL layout testing, and localization QA sign-off.

Modes:

• scan — Find hardcoded strings and localization anti-patterns (read-only)
• extract — Extract strings and generate translation-ready tables
• validate — Check translations for completeness, placeholders, and length
• status — Coverage matrix across all locales
• brief — Generate translator context briefing document for an external team
• cultural-review — Flag culturally sensitive content, symbols, colours, idioms
• vo-pipeline — Manage voice-over localization: scripts, recording specs, integration
• rtl-check — Validate RTL language layout, mirroring, and font support
• freeze — Enforce string freeze; lock source strings before translation begins
• qa — Run the full localization QA cycle before release

If no subcommand is provided, output usage and stop. Verdict: FAIL — missing required subcommand.

---

Phase 2A: Scan Mode

Search src/ for hardcoded user-facing strings:

• String literals in UI code not wrapped in a localization function (tr(), Tr(), NSLocalizedString, GetText, etc.)
• Concatenated strings that should be parameterized
• Strings with positional placeholders (%s, %d) instead of named ones ({playerName})
• Format strings that mix locale-sensitive data (numbers, dates, currencies) without locale-aware formatting

Search for localization anti-patterns:

• Date/time formatting not using locale-aware functions
• Number formatting without locale awareness (1,000 vs 1.000)
• Text embedded in images or textures (flag asset files in assets/)
• Strings that assume left-to-right text direction (positional layout, string assembly order)
• Gender/plurality assumptions baked into string logic (must use plural forms or gender tokens)
• Hardcoded punctuation (e.g. "You won!" — exclamation styles vary by locale)