EN Dash (U+2013) character causing failure in non English system

[whereisjim]

PSLogging.psm1
line#91
Before:
New-Item -Path $sFullPath –ItemType File
After:
New-Item -Path $sFullPath **-**ItemType File

I happen to run this function under Korean Windows 10 and it failed to create a new-item.

[9to5IT]

This is because the - character most likely gets converted into some different character.

Just trying manually typing -ItemType instead of copy/paste.

[davidthemaster30]

I've been having this issue since switching to Powershell Core 6.1. It works fine with normal Powershell 5. I have a french Windows OS (fr-ca). I put in a pull request to fix it.

[fourthborngoose]

I am having an issue with character translation when I output to the screen. It seems that if there was a way to allow for character translation to enable utf8nobom it would solve the fr-ca issue. I just haven't figured out how to do it.
I just think it might be the answer we are looking for when it comes to non-english log outputs and such.

[EReis0]

The op is correct, I noticed the – being used instead of a -

If you use – (en dash) instead of - (hyphen), PowerShell will not recognize it as a parameter prefix and will throw an error. This is because PowerShell, like most programming languages, expects ASCII characters for its syntax.

When I viewed line #91 in vscode I was able to spot it.
91 New-Item -Path $sFullPath –ItemType File

vscode
New-Item -Path $sFullPath �ItemType File

github
You can notice all of the - are in a different color than the – is used in line #91