utf-8 without bom
Bug: Scripts encoded with utf-8 without bom are producing errors when the character "Ä" is used between double quotation marks.
How to reproduce: Create a powershell file with the following contents:
$test = "Ä"
Save it with the encoding "utf-8 without bom" (often just called utf-8. The counterpart, utf-8 with bom, can also be called "utf-8 signature").
Run the file, and you will get the following error:
At C:\location\to\file\test.ps1:1 char:9
+ $test = "Ã„"
The string is missing the terminator: ".
+ CategoryInfo : ParserError: (:) , ParseException
+ FullyQualifiedErrorId : TerminatorExpectedAtEndOfString
How do you propose PowerShell should recognize UTF-8 if file does not have BOM?