Comments

• WoodenBleachers@lemmy.basedcount.com ⁨1⁩ ⁨year⁩ ago

  Not sure why the devs have so much trouble with parsing this. I’m not sure if it’s an API thing or a front-end issue

  source

  • dual_sport_dork@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Something somewhere is running an htmlspecialchars() or equivalent on whatever you input, probably as an attempt at “sanitizing” the text entered in titles/posts/comments. You know, to keep me from just inserting into a comment and have it to something naughty to anyone who loads the page.

    I’m certain these are being stored in the database as an &, but they’re not being decoded back into an ampersand character upon display.

    source

    • WoodenBleachers@lemmy.basedcount.com ⁨1⁩ ⁨year⁩ ago

      I know, just sanitize it again. .Replace(“&”, &), Regex.Remove(amp;), if(.Contains(“amp;”))

      source

      • -> View More Comments
    • onion@feddit.de ⁨1⁩ ⁨year⁩ ago

      Theres a git issue on this

      source
  • db2@sopuli.xyz ⁨1⁩ ⁨year⁩ ago

    &

    source
• ChaoticNeutralCzech@feddit.de ⁨1⁩ ⁨year⁩ ago

  Yes, it’s annoying. However, there is a fullwidth ampersand available, as well as lots of other curly characters. I tried adding combining backslashes to those that miss that final stroke of ‘&’ but I gave up as they don’t align consistently across platforms.

  ＆﹠Ֆ𐒒౭𐓯꯴𖩒᱒𝛂̊ɑͦ𝛂ͦ

  source

  • darcy@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    im seeing th last three as alpha-with-circle-above … is this intentional?

    source

    • ChaoticNeutralCzech@feddit.de ⁨1⁩ ⁨year⁩ ago

      Yes. The first one is a standard diacritical circle as seen in Swedish, the other two are a combining “o” above. The middle one is a standard alpha while the others are math script bold alphas. This is an attempt to create an ersatz “&” without the character 0x26 that appears as & in post titles and monospace text. The fullwidth ampersand is obviously the closest but it appears with space around it so “D＆D” looks more like “D & D” than “D&D”. Hence the attempts with weird characters (D𝛂ͦD, D꯴D, D𐓯D…). Unfortunately, some OSs (notably Windows 10) incorrectly draw most combining diacritics offset to the right of the base letter as a zero-width character.

      There is a pair of single (non-combining) characters I can demonstrate it with: a combination of K + combining comma below is supposed to look like Ķ but it looks kinda like Қ on Windows. However, Windows stacks combining diacritics so you can create impressively tall Z̷͍̝̿̈́͂̅͝͝͡͡a̷̢̡̢̙̬͕̯̹͍͖̰͕̦͉̘̪͗͂̑͂̑̾́̀̍͗̾́̄̕͝͝l̵̢̨̢̳̻̩̳̘͖͎͎̘̗̬̞͈͌g̸̨͈̠͔̖͎͇̟̍͗̈́̏̿̍̍͗̕o̷͓͎̙͉̯̱̊́͐͘ ̵̣͓̥͈̗̯̹̭̪͕͓̳̈́͌̐̈́̓̈́͑̌̚͡͝t̶̨̛̩̭̬̲͓̣͔̪̠̙̞͚̒͒̽͟͝ͅe̵̛̘͈̜͖̅͊́̅̌̇̒̐͑̚͠͝x̴͌͗͐͌̏͛̕͡͝ͅt̴̡̤̻̺̣̥̝̤̼̺̦̣͎̟́̊̂̈́̃͑̈́̈̈́ while some other platforms just print them over each other like a typewriter does.

      source

      • -> View More Comments
• Toes@ani.social ⁨1⁩ ⁨year⁩ ago

  Iñtërnâtiônàlizætiøn

  source
• spacecowboy@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  Lol this is clever and quick.

  source
• Black616Angel@feddit.de ⁨1⁩ ⁨year⁩ ago

  It is already fixed an will be rolled out soon.

  github.com/LemmyNet/lemmy/issues/3987

  source
• Illegal_Prime@dmv.social ⁨1⁩ ⁨year⁩ ago

  &&&&&

  source

  • ChaoticNeutralCzech@feddit.de ⁨1⁩ ⁨year⁩ ago

    The problem exists in post titles and fullwidth text.

    Ampersand (＆): &
    Less-than sign (ᐸ) : <
    

    (The characters in parentheses are closest Unicode lookalikes)

    source
• Broodjefissa@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Ah, an En Passant in the wild

  source
• Valmond@lemmy.mindoki.com ⁨1⁩ ⁨year⁩ ago

  Oh yeah! But what about a real encoding problem meme?

  We’re probably dozens who’d appreciate one!

  source
• kewko@lemdro.id ⁨1⁩ ⁨year⁩ ago

  &?

  source

  • ChaoticNeutralCzech@feddit.de ⁨1⁩ ⁨year⁩ ago

    The problem exists in post titles and fullwidth text.

    Ampersand (＆): &
    Less-than sign (ᐸ) : <
    (The characters in parentheses are closest Unicode lookalikes)
    

    source