• wizardbeard@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 months ago

      Only if it’s enabled by default, or the dev knows to enable it.

      I had a lot of weird problems processing some info with names in Powershell until I found out that Powershell doesn’t default to unicode format when shoving output into files. You can easily specify the encoding, but if you don’t it replaces any non-ascii characters with “?” by default, so it’s not even immediately obvious that there’s an incorrect character, as it just silently substitutes a valid one.

      • voxel@sopuli.xyz
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        it uses big-endian utf-16 with BOM by default unless you upgrade to PowerShell 7

    • Norgur@fedia.io
      link
      fedilink
      arrow-up
      0
      ·
      8 months ago

      No it hasn’t. It has just pushed them out of sight for English natives.

      • apoisel@discuss.tchncs.de
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        Can’t confirm that. In the 90s encodings were a nightmare. ISO-8859-1, ISO-8859-15, CP1252, IBM850, … If you tried to build a website with an upload form, you’d get the most bizarre encodings and there was no way to reliably distinguish them. I’m not an English native, my world is full of umlauts and s-z ligatures. Things got A LOT better in the last years, thanks to Unicode encodings.