Home › Per Microsoft + Unity i18n docs, TEXT EXPANSION …
Per Microsoft + Unity i18n docs, TEXT EXPANSION budgeting reserves how much extra space in UI for translated strings?
A~30% above English source length on average
BNo extra space at all (font scales)
CAbout 10% smaller than English usually
DAlways exactly 2× English length
Answer & Solution
Correct answer: A. ~30% above English source length on average
Microsoft Globalization docs + IBM design guidelines: German + Finnish translations of English UI grow ~30% on average. UI must not truncate or overflow.
Related questions
Per public studio postmortems (e.g. Riot, CD Projekt Red), LOC QA is a distinct testing phPer 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 Unity Localization + Unreal docs, the SOURCE-OF-TRUTH for translatable strings is mostPer 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 (