[openstreetmap/openstreetmap-website] Missing American English localization (Issue #4975)

[Andy Allan]

> OK, so en.yml should be in American English, not mostly British English?

Yes, I think it should be. It's similar to the [discussion that we had with portuguese](https://github.com/openstreetmap/openstreetmap-website/issues/3670) where we had to decide if requests for "pt" should be answered with "pt-BR" or "pt-PT" and went with the CLDR recommendation of pt-BR. And I strongly suspect that the equivalent for "en" will be "en-US". Therefore:

|Language|Locales|Files|
|---|---|---|
|American English| en, en-US|en.yml|
|British English|en-GB|en-GB.yml|

So to make this work, all we have to do is to make sure the source translations in en.yml are "en-US" and everything will work as intended (apart from some Brits who might need to update their browsers preferred languages, if they haven't done so already).

> But this codebase also maintains translations for a number of feature tags that would be much less intuitive to an American English speaker.

It's worth noting that many of these feature translation strings are written by non-English speakers, often native German speakers, so it's hard for them to spot any Britishisms, particularly if the British term is more similar to either the tag (traditionally OSM uses en-GB for tag values) and/or if the term is more similar to those used in other European languages.

The other non-tag translation strings in the repo are, as @tomhughes says, more often written by en-GB speakers.




-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/4975#issuecomment-2222363119
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/issues/4975/2222363119 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20240711/80cb8496/attachment.htm>