• esa@discuss.tchncs.de
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      4 months ago

      Q. P is a common character across languages. But Q is mostly unused, at least outside the romance languages who appear to spell K that way. But that can be solved by letting the characters have the same code point, and rendering it as K in most regions, and Q in France. I can’t imagine any problems arising from that. :)

      • lad@programming.dev
        link
        fedilink
        English
        arrow-up
        4
        ·
        4 months ago

        If that’s a joke, it’s a good one. Otherwise, well, there are a lot of “this letter isn’t needed let’s throw it away,” in most cases it will not work as good as you think.

        • esa@discuss.tchncs.de
          link
          fedilink
          arrow-up
          4
          ·
          4 months ago

          Yes, I am joking. We probably could do something like the old iso-646 or whatever it was that swapped letters depending on locale (or equivalent), but it’s not something we want to return to.

          It’s also not something we’re entirely free of: Even though it’s mostly gone, apparently Bulgarian locales do something interesting with Cyrillic characters. cf https://tonsky.me/blog/unicode/

          • AnarchistArtificer@slrpnk.net
            link
            fedilink
            English
            arrow-up
            2
            ·
            4 months ago

            Damn, thanks for that link; earlier today I was telling a non techy friend about Unicode quirks earlier and I could vaguely remember that post, but not well enough to remember how to find it. I didn’t try very hard because it wasn’t a big deal, so the serendipity of finding it via your comment was neat.

      • CameronDev@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        4 months ago

        That is quite a unique quip. I love the idea of geo-based rendering, every application that renders text needs location access to be strictly correct :D.

        I’d go further with the codepoint reduction, and delete w (can use uu) instead, and delete k (hard c can take its place)