Open JustinGrote opened 3 years ago
Adding [console]::OutputEncoding = [Text.Encoding]::UTF8
fixed it, maybe make this part of the invocation script?
@JustinGrote makes sense to me! Wanna submit a quick PR?
I may not only because I noticed it happened in my local wt console too, so it may give a false impression of "OK" behavior that will fail in the real world. The weird thing is why debug didn't do it, does the integrated console set this output encoding?
It does. Though, it sets it to UTF8...
Debug:
Run:
The glyph that didn't match is ✨ Probably just typical Powershell OutputEncoding issues.