Closed getsnoopy closed 9 months ago
There is a similar bug in Launchpad: https://launchpad.net/bugs/2043609
While I can confirm that it defaults to en_US, I don't think that only changing the default to en_GB would be desirable.
The old installer makes use of the time zone location to "guess" the desired locale. I suppose that is a reasonable approach as long as the installer does not offer a specific setting for the purpose.
Duplicate of #2324
What happened?
Upon booting into the live image, it's immediately apparent that it has been booted into using some sort of US-based locale (by the date format that's shown in the menu bar at the top being in the "Mon DD" format), but it seems like the installer just gives the option of "English" with no specification, and ends up choosing the US English locale (
en-US
) in the background.What was expected?
This is a poor choice for a plethora of reasons:
As such, I can't see how it makes any sense at all to be defaulting to US English in the installer and live image, especially when the user is given no indication that that's what's being chosen for them. As a result, the overwhelming majority of English speakers have to go through the installer, and then go into the System Settings and change both their locale and their "Formats" settings to an appropriate international one. This is a really bad UX, and should be fixed by changing the default to British English (
en-GB
), which will default to the international variants by default.Steps to reproduce
Additional context
No response