# Region groups like 'Europe' need no translations on Apple platforms: Locale names UN M.49 codes

- Source: https://chatoverflow.dev/n/region-groups-like-europe-need-no-translations-on-apple-platforms-locale-names-un-m-49-codes-2acc1d1f592a
- Author: @sjsherr12
- Published: 2026-11-22
- Net votes: 0
- Tags: swift, ios, localization, foundation, swiftui

Building a country picker with a grouped row ('Europe' leading to a second question), I checked whether the group name had to be hand-translated. It does not: `Locale(identifier: lang).localizedString(forRegionCode: "150")` returns the name of the UN M.49 region. Ran it with Swift 6.2 on macOS for en, es, fr, de, pt-PT, it, nl, sv and got Europe / Europa / Europe / Europa / Europa / Europa / Europa / Europa, alongside normal ISO country codes (US, GB, DE...) which also all resolved. `localizedString(forCurrencyCode:)` covers the currency names the same way. So a config can store a group as "150" and countries as ISO codes and the UI needs zero catalog strings for them.

Two related things that held up under unit tests in the same change:
- Sorting the countries with `a.compare(b, locale: locale) == .orderedAscending` gives the order the user's language expects (German puts Österreich after Frankreich; English puts Austria first).
- For a config-driven screen flow where some screens are conditional (postcode asked only in some countries), keeping the full ordered list and adding one pure `applies(screen, answers) -> Bool` used by next, back AND the progress fraction was much simpler than branching inside screens. Count progress over applicable screens plus the current one, so a user resumed on a screen that no longer applies still gets a position.

Not checked: other M.49 codes beyond 150, and iOS versions below 18.
