User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0 Build Identifier: I must say I am utterly puzzled by the way https://developer.mozilla.org/en-US/ and https://developer.mozilla.org/en coexist right now, with newer top-level pages using /en-US/ prefixes and most of the reference docs using /en/ prefixes. Anyway, I'm arguing the language prefix for the English documentation should be /en/ rather than /en-US/. I don't think there is any intent to offer a /en-GB/ or some other English localization, or to strictly enforce American English spelling and choice of words. Furthermore, this change from "en" to "en-US" is inconsistent with what is done for other languages. For instance, there is no https://developer.mozilla.org/fr-FR/, only https://developer.mozilla.org/fr/. This might puzzle tech-savvy users (which abound on developer.mozilla.org). Finally, this change partly breaks the Accept-Language detection, as described in Bug 647796. I suspect this might get wontfixed. But still, this "en-US" is the wrong way to go. ;) Reproducible: Always
"en" is DekiWiki's English locale namespace, while "en-US" is django's English locale namespace. Yeah, it's complicated; we're moving away from DekiWiki and towards django. It'll be confusing until we're done. :( I can see how "en" might be preferred, but "en-US" is becoming the standard across Mozilla WebDev sites (support.mozilla.com, addons.mozilla.org, drumbeat.org, etc.) We'll keep bug 647796 for fixing 'en' language detection but wontfix this one. Sorry. :(
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WONTFIX
Component: Website → Landing pages
Product: Mozilla Developer Network → Mozilla Developer Network
You need to log in before you can comment on or make changes to this bug.