MPC can't handle unicode default.features

[jwillemsen]

The powershell out-file creates by default an unicode file (https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/out-file?view=powershell-6). For usage on azure-devops/appveyor it would be easier when MPC could handle an unicode default.features file.
As note, out-file is also used for the > redirect, so using this redirect in a powershell script will create an unicode default.features.

[mitza-oci]

Powershell appears to be a tool that's not so well suited to non-.NET development. I don't think it's so unreasonable that a build script generator like MPC uses ASCII/UTF-8, it's not doing internationalized text.

[jwillemsen]

Is there a way to trigger an error within MPC when a file is not ASCII/UTF-8? That would probably save people time who hit the same issue