Fighting Game · Guides & deep dives

V2 Localization Status Dashboard

The report derives status from the registered string inventory, locale files, the extraction catalog, translation QA, and fallback resolution.

3sections1 minread
Markdown source
On this page

This document defines the localization status dashboard for TODOS.phase-72.72.11.1.15. The dashboard is a generated operational report for localization producers, build engineers, and vendor managers.

Dashboard Scope#

V2/ue/Tools/generate-v2-localization-status-dashboard.py writes V2/ue/Content/Localization/V2/Dashboard/LocalizationStatusDashboard_V2.json. The report derives status from the registered string inventory, locale files, the extraction catalog, translation QA, and fallback resolution.

The tracked views are:

  • per-language completion, using the registered string ID inventory as the denominator.
  • strings needing review, including locale entries missing from human or generated target files.
  • recently changed source strings, based on active source entries in StringIdRegistry_V2.json.

en-US is treated as the source locale. Human target locales report translated, reviewed, missing, QA issue, and fallback exposure counts. en-XA reports pseudo-localization coverage so UI overflow checks stay aligned with source inventory.

Regeneration#

Run the generator after changing source strings, locale files, extraction outputs, QA reports, pseudo-localization, or fallback data:

bash
python3 V2/ue/Tools/generate-v2-localization-status-dashboard.py

Verification#

Run this gate after changing dashboard inputs, generated output, docs, or CI wiring:

bash
python3 V2/ue/Tools/check-v2-localization-status-dashboard.py

Required release gates:

  • localization-status-dashboard-contract
  • localization-status-dashboard-report
  • localization-status-dashboard-completion
  • localization-status-dashboard-review-queue
  • localization-status-dashboard-source-changes
  • localization-status-dashboard-ci-wired