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?
We're saying, don't translate the language's names at all, use what the speakers call their own language.
English is always "English" regardless of UI language. French is always "Francais", Then you can switch to any language you can read
Yeah, and the comment you just replied to said: why not both? Language name in language up front, and language name in current language in parens. I think it's a neat idea and absolutely would support that as a standard.
My big question would be what would that add? If you speak Japanese, Spanish and French, 日本語, Español and Français would give you all the information you need. Adding the language name in a second language would increase the work to do, while also not really providing any benefit that I can see. If you manage to change the language to Spanish, or are using somebody else's device, "English" is no less helpful for you than "English (Inglés)" would be.
Easy enough. Tells you what languages are supported. Also helps you debug a bad language label. Although does have the disadvantage that you still need the name of every language in every language (the existing state) and you don't get to suddenly sqrt your data requirements for storing that