UTF-8 without BOM [Missing Encoding Option]
Votes from Connect: 4
Original Date Submitted: 10/6/2014 10:15:42 AM
Site Name: PowerShell
Feedback ID: 993163
Frequency: Always Happens
Regression: Yes, this happens in previous released versions
I had an issue recently with generating JSON files that needed to be encoded in 'UTF-8 without BOM.' Cmdlets with the -Encoding parameter do not have this format as a possible encoding option.
It looks like the Unicode standard recommends not using the BOM, either, as mentioned in this conversation:
Here is the Standard documentation:
Quote given from Page 30:
"... Use of a BOM is neither required nor RECOMMENDED for UTF-8, but may be encountered in contexts where UTF-8 data is converted from other encoding forms that use a BOM or where the BOM is used as a UTF-8 signature."
Product Studio item created by Connect Synchronizer due to creation of feedback ID 993163 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=993163).
Use any cmdelt with the -Encoding parameter to see only UTF-8 (which is, by default, WITH the BOM)
That is would, by default, be WITHOUT the BOM -- as it is not required nor recommended by Unicode standard
Internal BugId: 11033
Paul Hey commented
Still and issue in 2018. UTF8 with no BOM should be standard for Powershell.