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.

[–] Norgur@fedia.io 0 points 2 years ago (1 children)

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

[–] apoisel@discuss.tchncs.de 1 points 2 years 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.

[–] WhereGrapesMayRule@lemmy.world 1 points 2 years ago (1 children)

I would have sex with this bumper sticker.

[–] Imgonnatrythis@sh.itjust.works 1 points 2 years ago (1 children)

Sir, This is a Wendy's parking lot.

[–] WhereGrapesMayRule@lemmy.world 1 points 2 years ago

You're just making it worse.