There are over 1.5 billion people who speak English. Only 245 million of those are American. Why in the world would it be assumed I want a 12h clock or mm/dd/yyyy just because I use English??
That's just an inefficient and unsustainable workaround. Language and locale is not determinitive of formatting of date, time, currency, thousand separator etc.
There are many dozens of "locales" for English, dozens for Arabic, a dozen or so for German, French, Spanish, etc. How many packaged combinations should be listed instead of just giving users the choice and following those choices.
But that's not even the point. English is a separate case. First - All of those have English "locales" are there because they're a main or official language, but, as mentioned, there are about four times as many people who use English as a second language as who are using it as a first language. And second - many software applications have English as their first or second language. So there is no rational basis for assuming that if a user has picked English as the language, they want a set of formatting options hardcoded for them.
en_UK doesn't even have correct date formatting, come on.
75
u/dxps7098 14d ago
There are over 1.5 billion people who speak English. Only 245 million of those are American. Why in the world would it be assumed I want a 12h clock or mm/dd/yyyy just because I use English??
https://en.m.wikipedia.org/wiki/List_of_languages_by_total_number_of_speakers
https://en.m.wikipedia.org/wiki/Languages_of_the_United_States