|
|
|
|
|
|
by bonestamp2
2216 days ago
|
|
|
> Then we should have browser settings for regional dialect 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. |
|
|
Your site is an outlier if you ignore the user's location. Most tend to take the IP address as more important than the browser settings (looking at you Google, Amazon).
The Amazon case is especially weird. I can talk English to Amazon.com, but as soon as I set up a Berlin delivery address it wants me to switch to Amazon.de. Which speaks German to me. There is a switch for language there, but that only works for some parts of the interface, and not things like reviews, etc, which are all still in German. It knows I speak English, because it keeps offering to translate these German reviews into English for me. But if I go to the same product on the .com site, there's a ton of English reviews for the same product. I must admit, I don't understand the logic behind it all.
But the same problem is at the core: assuming that because someone lives in Germany, they speak German. Again, language is a property of people, not places.