Home › Per CLDR + ICU, FORMATTING dates and numbers mus…
Per CLDR + ICU, FORMATTING dates and numbers must vary by locale because of which class of issues?
ASeparators (1,000.5 vs 1.000,5) + date order
BDifferent time zone IDs per script always
CDifferent floating-point precision per locale
DEndianness of integers across CPUs varies
Answer & Solution
Correct answer: A. Separators (1,000.5 vs 1.000,5) + date order
CLDR + ICU: '1,000.5' (en-US) vs '1.000,5' (de-DE) vs '1 000,5' (fr-FR). 12/03/2024 means March 12 in en-US, December 3 in en-GB. Use locale-aware formatters.
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 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 (