/en-US/ is misleading as it implies that we have an /en-GB/ which we do not. We should instead just use /en/ for localization.
8 years ago
I've been thinking we should do this lately as well. en-US is incorrect for a ton of people that use it. Though I think we'll probably want to add en-GB for marketplace so that we can tie currency (£) to it.
(In reply to comment #1) > cc: firstname.lastname@example.orgI've been thinking we should do this lately as well. > en-US is incorrect for a ton of people that use it. Though I think we'll > probably want to add en-GB for marketplace so that we can tie currency (£) > to it. I'm not sure that's right... /en/ should be language, not locale so much. I think there's a lot of people who speak one language but use a different currency. For example, andy mckay would probably use /en/ (or even /en-GB/) but it would be foolish to assume that he wants his money in £ because he lives in Canada. So somewhere we're going to have to store a user's preferences for currency. In Andy's case racoon fur or beaver pelts or whatever they use in Canada. But maybe we can just have en-GB and have sensible defaults and allow users to override them.
en-US doesn't imply we have en-GB. It says we are using a US variant of English which we are. Wontfixing this.