René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Common encoding pattern for Utility Cmdlets","articleBody":"Current encodings in Utility Cmdlets:\r\n\r\nCmdlet | Encodings\r\n-| -\r\nCVSCommands.cs ([1](https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/CSVCommands.cs#L210) and [2](https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/CSVCommands.cs#L575)) | \"Unicode\", \"UTF7\", \"UTF8\", \"ASCII\", \"UTF32\", \"BigEndianUnicode\", \"Default\", \"OEM\"\r\n[Format-Hex.cs](https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/FormatAndOutput/format-hex/Format-Hex.cs#L56) | \"Unicode\", \"BigEndianUnicode\", \"Utf8\", \"Utf7\", \"Utf32\", \"Ascii\"\r\n[Out-File.cs](https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/FormatAndOutput/out-file/Out-File.cs#L87) | \"Unknown\", \"String\", \"Unicode\", \"BigEndianUnicode\", \"Utf8\", \"Utf7\", \"Utf32\", \"Ascii\", \"Default\", \"OEM\"\r\n[ImplicitRemotingCommands.cs](https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/ImplicitRemotingCommands.cs#L81) | \"Unicode\", \"UTF7\", \"UTF8\", \"ASCII\", \"UTF32\", \"BigEndianUnicode\", \"Default\", \"OEM\"\r\n[MatchString.cs](https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/MatchString.cs#L1213) | \"Unicode\", \"UTF7\", \"UTF8\", \"ASCII\", \"UTF32\", \"BigEndianUnicode\", \"Default\", \"OEM\"\r\n[XmlCommands.cs](https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/XmlCommands.cs#L111) |  \"Unicode\", \"UTF7\", \"UTF8\", \"ASCII\", \"UTF32\", \"BigEndianUnicode\", \"Default\", \"OEM\"\r\n\r\n\r\nIt seems we can safely migrate to a common pattern \"Unicode\", \"UTF7\", \"UTF8\", \"ASCII\", \"UTF32\", \"BigEndianUnicode\", \"Default\", \"OEM\".\r\n\r\nFormat-Hex was converted from function to cmdlet. I believe we can enhance it.\r\n\r\nOut-File. My understanding is that \"Unknown\" and \"String\" encodings is _output_ encodings and don't be used as _input_ encodings. So we can and should remove them from Out-File cmdlet.","author":{"url":"https://github.com/iSazonov","@type":"Person","name":"iSazonov"},"datePublished":"2017-04-23T08:25:36.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/3628/PowerShell/issues/3628"}