This always annoys me. I land on a site that's in a language I don't understand (say, Dutch), and I want to switch to something else. I open the language selector and... it's all in Dutch too. So instead of Germany/Deutchland, Romania/România, Great Britain, etc, I get Duitsland and Roemenië and Groot-Brittannië...
How does that make any sense? If I don't speak the language, how am I supposed to know what Roemenië even is? In some situations, it could be easier to figure it out, but in some, not so much. "German" in Polish is "Niemiecki"... :|
Wouldn't it be way more user-friendly to show the names in their native language, like Deutsch, Română, English, Polski, etc?
Is there a reason this is still a thing, or is it just bad UX that nobody bothers to fix?
It would be way more user-friendly to use the language in the HTTP headers. As a web developer the fact that websites are too stupid to do this really grinds my gears. This is just as bad as assuming the language/region from the geolocation of the IP address.
C’mon guys…
the last one piss me off so much, especially when they redirect you and you don't have anyway to load the English version...
It’s like all the developers in the field got handed access to some IP dataset and they’re just looking for reasons to use it. Screw the users I guess?
The customer gets what the customer wants.
I've tried countless times to convince them to just use the browser locale, but most of them somehow keep insisting on using geolocation...
I wonder if they just want some more data they can then sell off to others.
Even worse when a version is actually different. I had to check the US prices in a store once, it decided "nah mate, your IP's not American, clearly you're a bloody idiot, here's your native version" and even when I manually changed the url to US English, as they did languages based on part of the path, it still decided clearly I must not know what I want. I couldn't even try to infer the price, as the product didn't exist on my version of the site.
And aside from that and language pet peeves, what if you're on Holiday? Or live in an area that speaks a lot of languages close together?
As Cousin Mose said, the language is in the header, the fact that some web devs decide the IP address is clearly a better way to figure out what language you want is insane
Yes, apparently I learned Swedish as soon as I stepped off the plane in Stockholm. I'm even logged into your site and you have my home address, you twits.
My Pixel started giving me distances in miles once because I had the system language to English. I needed to change it to English (German) to show me meters. I don't know if they reverted that but at this point I am too afraid to change it.
I have my Google Account set to English, but YouTube still autotranslates all video titles of newer videos to German for some reason...
It's like they are just bad at this. The one device I have where I can't block YouTube's ads is set to route through Tokyo, so the ads are in Japanese, which I barely understand.
That's just how locales work. When you set the language, you also get the associated date/time representation, unit system, etc
But you should be able to set the locale separately from language. You can easily do that on any Unix/Linux system. In your locale.conf, set LANG to your language and all other LC_* variables to your preferred locale.
Systems that do not allow this are badly designed. For a lot of multilingual people, locale and preferred language are independent.
Yeah, Japan as a country uses kilometers, and Rawhide Kobayashi has an easier time reading things on his phone in Japanese, but his heart craves the measurement units of his true home, Texas.
Yeah but it didn't say locale or location, it said system language, that is what i was confused about language =/= location.
And that is just an example of horrible UI. Locales should not be tied to those things. Maybe set the defaults but not forced.
My pixel set to Australian English works fine in metric. I presume you chose British English where they use miles rather than kilometres, of course that works for me as I also want Australian spellings
Accept Language headers are sadly an easy browser fingerprint. I therefor have it set to English even though that's not my native language.
There's also the case where you might have misclicked when changing your language, so your argument isn't really a complete solution. It just helps but doesn't fix the main problem.
If you set your language on a website what’s the difference between them using the header versus using the selected language for fingerprinting?
I understand what you’re saying but even I, a person who splits all their traffic between three different VPN tunnels and goes way too far with DNS blocking don’t really care about fingerprinting based on language.
If the person really cares so much they can set the browser language back to English then manually change it on each website they visit. We shouldn’t punish everyone on such a silly privacy preference.
Edit: Yeah of course just downvote me, don’t bother to engage in any kind of dialog.
I'm pretty sure nobody's doing that based on geoip. Client-side, the browser exposes the user's languages choices. And server side, the HTTP header can help. But geoip is totally unreliable, even a broken salesman would not sell that as a feature.
Well ok they would sell it but get a very heavy glance from the dev team.
Have you used the web and/or VPN lately? I send the language header but am bombarded by content in the wrong language all the time.
YouTube (and Google in general) has been horrible for multilingual users (and users who want to see content in a different language than the default for whatever country they're browsing from) for quite some time, but lately it's getting downright unusable without untranslator browser extensions.
It wouldn't be too much work to hook the request language up to a CMS and then a translation service. You could produce in a couple of popular languages upfront and then when someone with a new language visits a landing page, translate it at high priority (few seconds), then the cascade the next most likely click-throughs in order of popularity (or callout weight if it's new). The translations can then be queued for review, and it will mean you only translate when you need to, and the user only experiences a second or so delay as the translation streams the content above the fold.