|
|
|
|
|
by marcus_holmes
2219 days ago
|
|
Then we should have browser settings for regional dialect, because the same thing holds true. I don't stop being a British English speaker just because my IP address is in Toronto. Language is a property of people, not place. edit: Also, I'm an English speaker living in Berlin. This shit happens to me all the time, and it's a trigger. Apologies for blowing my cool. And I'm used to reading any flavour of English. The regional dialects really don't matter. Colour can be color and I'll still understand. I won't understand "Farbe". |
|
We do, and that's what I'm using. Sorry if my example was confusing, I should have worded it better. I am using the regional setting from the browser to determine the correct region for your language, I'm not using your physical location in any way.
My comment was an outline for the right way to do it and I blew it when my example had the person with their region set to mexico actually in mexico (which is true most of the time, and true in my example, but is not how the app logic works because it's not true for everyone all the time). Either way, I think the actual logic agrees with what you would expect -- you get the language your browser is set to regardless of where you're connecting from. Additionally, if you have your region selected, we'll also tune your desired language for the right region of that language too regardless of where you are physically.