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.
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.