PowerShell 5.1 decodes a BOM-less UTF-8 .ps1 as ANSI/GBK, so non-ASCII becomes bogus parse errors

Domain: windows · Evidence E1 — Maintainer reviewed

powershellwindowsencodingutf8-bomgbkmojibake

Summary

A `.ps1` file that contained non-ASCII text — Chinese comments and Chinese `Write-Host`