why are website language switchers in the current language?
-
Perfectly comprehensible if you speak english, look:
I think i've had a stroke
-
What language would you sort them by?
If everything is displayed in the same language then sort by the displayed language. You don't want to have to search for Spanish near the E letter because it's sorted by the original espanol in the background since that's not what you as the user sees.
-
If everything is displayed in the same language then sort by the displayed language. You don't want to have to search for Spanish near the E letter because it's sorted by the original espanol in the background since that's not what you as the user sees.
And if they're all displayed in their own language?
-
If people really insist then at least have a flag emoji
that's all fine and dandy until you get a porch of geese angry at you for using the brazilian flag or vice versa
-
The scrum master is not a product owner and shouldn't be providing scope or anything for that matter in tickets. No wonder agile is hated and dying, it's been corrupted beyond recognition by people who have no reading comprehension.
The product owner often doesn't understand technology well enough to know that mapping labels and sorting are different. They don't know what they don't know. The SM needs to help bridge that gap.
-
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?
The language selectors in the system I have built are either English or native. And I can tell you, implementing and verifying over 100 languages in their native writing is quite a challenge.
-
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?
In an international context, not everybody speaks English. A Japanese customer wants to switch to French. Which language should the language picker be in?
Alternative is to put the flag of each language next to the name in the picker. That way, whoever doesn't read the current language can at least pick by icon.
-
In an international context, not everybody speaks English. A Japanese customer wants to switch to French. Which language should the language picker be in?
Alternative is to put the flag of each language next to the name in the picker. That way, whoever doesn't read the current language can at least pick by icon.
Which language should the language picker be in?
the language of the listed language. Lots of language switchers do it that way
-
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.
wrote on last edited by [email protected]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.
-
In an international context, not everybody speaks English. A Japanese customer wants to switch to French. Which language should the language picker be in?
Alternative is to put the flag of each language next to the name in the picker. That way, whoever doesn't read the current language can at least pick by icon.
A Japanese customer wants to switch to French. Which language should the language picker be in?
日本語。
-
I've seen language switchers with translated language names that were sorted by the English name. So "Deutsch" was sorted under G.
Out of curiosity, would you put Deutsch before or after 日本語?
-
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.
-
The reality is, it varies.
I just opened the language picker on the first site I had in my browser tabs (happened to be Epic games) and they display the language list using native names for the target language, rather than current language (screenshot attached)
I agree it's much better to do it this way.
As a developer, why it doesn't happen sometimes could just be by accident. If you intentionally set out to localise a site and put all text and menu elements into localisation files to be translated, then the language names are going to end up getting translated too. It takes conscious thought and UX design to realise that it's better for accessibility if that single part of the site is actually just static text, regardless of what language is selected.
And before anyone suggests using country flags in your language picker as a cool solution - please don't, because that sucks too. There isn't a 1:1 relationship between countries and languages and so the flag approach is a flawed compromise at best, and actually insulting at worst.
Yeah okay but imagine clicking the option with an Israeli flag and suddenly the website is in Arabic. That's too funny to pass up.
-
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?
Ive had multiple situations on websites or in games where i accidentally switched the language to like- japanese or something and then had to fumble around trying to switch it back. On websites at least you can translate to find the right option but i recently installed a game on my steamdeck and the input was all screwed up, and while trying to fix it i accidentally switched the language and then navigated away from the menu. Trying to get back to the right setting with broken input and not understanding anything wasnt fun.
-
In an international context, not everybody speaks English. A Japanese customer wants to switch to French. Which language should the language picker be in?
Alternative is to put the flag of each language next to the name in the picker. That way, whoever doesn't read the current language can at least pick by icon.
wrote on last edited by [email protected]The annoying thing is, you can't put an image in the default select from browsers.
So you have two choices :- Make a custom select -> it's complicated and will break on some machines.
- Use emoji flags -> windows do not have an image pack for flag emoji, and chrome didn't bother implementing their own (Firefox did), so it displays the initials instead.
So whatever you do will not be universally supported, thank you Microsoft.
-
In an international context, not everybody speaks English. A Japanese customer wants to switch to French. Which language should the language picker be in?
Alternative is to put the flag of each language next to the name in the picker. That way, whoever doesn't read the current language can at least pick by icon.
Have the language in the current language setting and the target language native tongue so you would get
フランス語 / French
"Alphabetic" sorting would be difficult, so it wouldn't be perfect, but at least a lot more understandable. Still, just having a search option would fix that easily. -
Out of curiosity, would you put Deutsch before or after 日本語?
wrote on last edited by [email protected]Before, since D and G are both before N ("nihongo") and J ("japanese")
-
Yeah okay but imagine clicking the option with an Israeli flag and suddenly the website is in Arabic. That's too funny to pass up.
Probably not so funny other way around hah
-
In an international context, not everybody speaks English. A Japanese customer wants to switch to French. Which language should the language picker be in?
Alternative is to put the flag of each language next to the name in the picker. That way, whoever doesn't read the current language can at least pick by icon.
The label for the language picker is an issue, but the choices themselves? In the target language. You want French? You pick "Français". You want Japanese? You pick "日本語". You want english? You pick "English".
Supposedly, if you'd rather have a website in a given language, you must have some level of understanding of that language, and picking its name should not be a challenge in any case. If you somehow change a site/app to a language you don't know, as long as you can identify the language picker, you'll be able to change to something you understand.
It does leave out the case of a user wanting to change to a language they do not understand, but I do not care for those.
-
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…
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.
