Is this a known issue? If you type in somewhere it will be replaced by

Don’t get me started on how this messes up linux commands and scripts, Is this a me problem or a lemmy problem? I need to study, if this is a known problem, then fine, but if it isn’t then it needs to be reported.

      • Jordan Lund@lemmy.one
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        4
        ·
        1 year ago

        OP noted: “Don’t get me started on how this messes up linux commands and scripts”

        If you’re running linux commands and scripts, you’re not a normal user and should know this already. :) It’s only been the standard for 30 years or so.

        • Big P@feddit.uk
          link
          fedilink
          English
          arrow-up
          8
          arrow-down
          1
          ·
          1 year ago

          “standard” is that the character you input stays as the same character and isn’t transformed. The fact that it’s being shown as & means that either OP is using a client which isn’t correctly decoding html, or its being double sanitised as &. Neither tog those is “standard”, it’s a bug.

          • Jordan Lund@lemmy.one
            link
            fedilink
            English
            arrow-up
            3
            arrow-down
            2
            ·
            1 year ago

            Not in HTML. Never has worked that way.

            Special reserved characters have always been handled this way because you don’t want to accidentally interpret something the wrong way.

            Same for URL encoding. You upload “Clever Name.PDF” to a website and it generates a URL of “Clever%20Name.PDF” because spaces aren’t valid in URLs. %20 is the code for a space.

            • Big P@feddit.uk
              link
              fedilink
              English
              arrow-up
              5
              ·
              1 year ago

              But when you see it on your screen it’s supposed to be converted back into the actual character, otherwise it would be pointless. So if you’re seeing & then the website is messing up.

        • EuphoricPenguin@normalcity.life
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          1
          ·
          1 year ago

          should know this already. :)

          What in the gosh darn condescending non sequitur is that? I have a special kind of dislike for people who, instead of trying to promote learning for anyone and everyone at any stage, instead choose to ridicule people for having missed some trivial detail that has about as much in common with Bash as does COBOL (basically nothing). Web scripting is, unsurprisingly, its own skill, and it’s very, surpassingly, extremely, stupendously, and obviously conceivable that someone could have years of Bash experience but only recently started putting around with scripting for things like API access or HTML parsing. But you should know this already. :)

        • Dandroid@dandroid.app
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          I struggled hard to just post a link the other day because it has an ampersand in it, and it was being replaced.

    • Subject6051OP
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      edit-2
      1 year ago

      thank you! that’s intersting. I have had scripts ruined due to this. I thought markdown did that by default at least when code blocks are on

  • Subject6051OP
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    1 year ago

    I don’t know why, this happens sometimes and doesn’t happen other times. I don’t know the cause of it.

    & & & this didn’t happen now

    • raoulraoul@lemmy.world
      link
      fedilink
      arrow-up
      12
      ·
      1 year ago

      It happens in post titles in lemmy desktop. lemmy apps vary on correct rendering of certain glyphs/entities. Even bold and italic markdown is rendered literally, that is, incorrectly.

      In any case, it’s still a bug.