Home › Per Unity Localization + Unreal docs, the SOURCE…
Per Unity Localization + Unreal docs, the SOURCE-OF-TRUTH for translatable strings is most commonly which format?
AHard-coded inline literals in C# or C++ source
BImage-only assets in localised folders only
CString tables / .po / XLIFF translator format
DJSON blobs with keys only on the live server
Answer & Solution
Correct answer: C. String tables / .po / XLIFF translator format
Unity Localization + Unreal i18n + industry: external string tables / XLIFF (XML Localization Interchange File Format) decouple translators from engineers + support context + status.
Related questions
Per public studio postmortems (e.g. Riot, CD Projekt Red), LOC QA is a distinct testing phPer Microsoft + Unity i18n docs, TEXT EXPANSION budgeting reserves how much extra space inPer Unicode CLDR + game studio guidelines, FONT FALLBACK chains are necessary because of wPer CLDR + ICU, FORMATTING dates and numbers must vary by locale because of which class ofPer ICU + ISO 4217 + CLDR currency docs, the LOCALE for 'United States English' is encodedPer Unicode + game text docs, NORMALISATION FORM C (NFC) is recommended for stored game stPer ICU + Unity Localization, the SAFEST way to build a runtime string with a variable couPer ICU MessageFormat (and Unity Localization), PLURALISATION rules for slavic languages (