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?

  • tiramichu@sh.itjust.works
    36·
    1 day ago

    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.