> The rationale (which I still don't agree with) was that many browsers would send "en-US" by default, and so it wasn't a reliable indication of the user's actual language.
Sounds like a potential workaround is to set your language to another flavour of English like "en-CA" or "en-GB".
Sounds like a potential workaround is to set your language to another flavour of English like "en-CA" or "en-GB".