for "en" locale, can i set british date/number formats as defaults?

[stefanprobst]

for "en" locale, can i set british date/number formats as defaults?

[amannn]

Locales allow encoding some information like the numbering system (e.g. ar-u-nu-arab), but I don't think using date/number formats from a specific regional variant is supported with a syntax like that. So practically, this means that you probably want to use en-GB.

Does that present a challenge for your app?

E.g. custom prefixes allow you to still display "en" in the URL if that's a concern for you.

[stefanprobst]

thanks for the quick reply!

i'm less concerned about the url, more about changing the value of locale to "en-GB" because "en" is already used all over the place.

i'd hoped maybe a custom format could be used somehow - but if not no worries i'll just wrap useFormatter.

[amannn]

because "en" is already used all over the place.

Sure, I understand. Hard to say what specifically the impact is for your app, but from an outside perspective it seems like the cleanest option though. I think formats can't be customized to a degree where e.g. you'd flip the month/day ordering of en-US to en-GB (which is quite the point of using the Intl API in JavaScript, not having to know about such details for a given locale).

[stefanprobst]

👍 makes sense.

i guess the issue is that "en" === "en-US".

[stefanprobst]

because "en" is already used all over the place.

looking at this again, i think all i really need in these places is "language" so i'll just:

function useLanguage() {
  const locale = useLocale(); // "en-GB"
  return new Intl.Locale(locale).language; // "en"
}

[amannn]

That sounds like a solid approach, yes! 👏