You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pipelining of commands fails using PowerShell because the output encoding of the records written to stdout is changed by the shell. Running each command separatly and write an output file, which will be read of the second command, works fine. I already tried to change the $OutputEncoding setting to UTF-8, but this seems not to fix the problem.
Unless it is possbile to describe how to fix this issue, the documention should recommend cmd.exe instead of PowerShell.
Pipelining of commands fails using
PowerShell
because the output encoding of the records written tostdout
is changed by the shell. Running each command separatly and write an output file, which will be read of the second command, works fine. I already tried to change the$OutputEncoding
setting toUTF-8
, but this seems not to fix the problem.Unless it is possbile to describe how to fix this issue, the documention should recommend
cmd.exe
instead ofPowerShell
.CC: @a-wendler
The text was updated successfully, but these errors were encountered: