• Uff@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    11 hours ago

    Yet another anglosaxon government suppressing non anglosaxon culture

    • TheGrandNagus@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 hours ago

      Anglo-Saxon? Lmao what a bizarre way to talk. Not that it even makes sense considering Anglo-Saxon settlers in the US weren’t even close to being the majority.

      It’s down to unicode support. Not a plot from Anglo-Saxons to keep others in their place lol

      • grue@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 hours ago

        To be fair, not considering unicode support a priority is a pretty damn English-language-centric attitude.

  • Maxx0r@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    15 hours ago

    I found this interesting since it’s basically about unicode support, so I did some research. This article seems bullshit, it seems like rhe residents are expected to use the english version of the streetname (Musqueamview) and not the indigenous one with uncommon letters. So, the problems described is totally fabricated. But also: databases shouldn’t forbid uncommon unicode letters if it isn’t called for.

    • Treczoks@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      11 hours ago

      But also: databases shouldn’t forbid uncommon unicode letters if it isn’t called for.

      I stumble across this issue quite often. When you fill out a form for US customs, you are both required to provide exact data and you are only allowed a-z, 0-9, and some punctuation. That you cannot fulfil both because they are mutually exclusive does not cross their blessed little minds.