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?
Valid comment to some degree, but putting language options in the selected language is always dumber than providing them in the only world language.
Nobody’s arguing that it’s the right way to do it, we’re just saying that breaking out words like “dumb” after the fact from the comfort of our keyboards, over problems that aren’t necessarily obvious at development time if you’ve not had i18n training, is kind of harsh.
The only thing I know about i18n is that it is an annoying shitload of language installer packages for both firefox and libreoffice ^^ That said, however, how you need training for a localization package to provide a language menu(!) - not the translations, mind you - in English, is beyond me. I can’t follow the point you seem to be trying to make. There’s no reason to not hardcode (in English) a language selection menu, and then display the list of available site languages (and these should be a country flag with the name of language next to it in what may be the language itself)