Encoding Windows-1252 not supported

[krusch]

Some INI files seem to use Windows-1252 encoding (e.g. mdash as x97), which is not a support output encoding.

[lipkau]

Thank you for reporting this. I will investigate the issue.

But if this is a limitation of Add-Content CmdLet I will not be able to do much about it.

[craibuc]

It's fairly easy to change a file's encoding. See my answer.

[krusch]

@craibuc This is about the encoding of files written by PsIni modules, not about the encoding in the Git repository.

[craibuc]

Yes, I understand that. I was simply demonstrating a technique to change a
file's encoding.

On Sun, Sep 13, 2015 at 9:00 AM, Klaus Johannes Rusch <
notifications@github.com> wrote:

@craibuc https://github.com/craibuc This is about the encoding of files
written by PsIni modules, not about the encoding in the Git repository.

—
Reply to this email directly or view it on GitHub
#21 (comment).

[krusch]

@craibuc thanks, found the magic line on rereading the post. Unfortunately Set-Content
relies on Microsoft.PowerShell.Commands.FileSystemCmdletProviderEncoding, which does not seem to support Windows-1252, valid values are String, Unicode, Byte, BigEndianUnicode, UTF8, UTF7, Ascii.

[lipkau]

As correctly stated, Add-Content is restricts the possible encoding formats to Microsoft.PowerShell.Commands.FileSystemCmdletProviderEncoding (as state in the documentation).

This The Official Scripting Guys Forum! question addresses this issue.