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?

  • undefined@lemmy.hogru.ch
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    29 days ago

    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…

    • whyNotSquirrel@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      29 days ago

      the last one piss me off so much, especially when they redirect you and you don’t have anyway to load the English version…

      • undefined@lemmy.hogru.ch
        link
        fedilink
        arrow-up
        1
        ·
        29 days ago

        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?

        • EisFrei@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          29 days ago

          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…