Localized socket error messages are shown as octal numbers

[driver1998]

Troubleshooting steps
https://github.com/PowerShell/Win32-OpenSSH/wiki/Troubleshooting-Steps

Terminal issue? please go through wiki
https://github.com/PowerShell/Win32-OpenSSH/wiki/TTY-PTY-support-in-Windows-OpenSSH

Please answer the following

"OpenSSH for Windows" version
((Get-Item (Get-Command sshd).Source).VersionInfo.FileVersion)
8.1.0.1

Server OperatingSystem
((Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows nt\CurrentVersion\" -Name ProductName).ProductName)
N/A

Client OperatingSystem
Windows 10 Build 20190

What is failing
When I try connecting to a non-exist server, I saw some bizarre error messages.

Expected output
The localized message are shown properly, or just show English ones.

Actual output
The localized message are shown as octal representations.

ssh: Could not resolve hostname nanopim4: \262\273\326\252\265\300\325\342\321\371\265\304\326\367\273\372\241\243

[driver1998]

So that long string of octal numbers translates to this (GBK encoding):

B2BB D6AA B5C0 D5E2 D1F9 B5C4 D6F7 BBFA A1A3
 不   知   道   这   样   的   主   机   。

Which means "don't know the host specified", which makes sense.
But still, a string of numbers mean nothing to an average human being.

Note: My machine is set to Simplified Chinese locale (CP936), hence the GBK encoding.

[walkure]

I met same issue at ja-JP locale.

PS > ssh hoge
ssh: Could not resolve hostname hoge: \202\273\202\314\202\346\202\244\202\310\203z\203X\203g\202\315\225s\226\276\202\305\202\267\201B

So, I decoded by Python.

>>> msg = b"\202\273\202\314\202\346\202\244\202\310\203z\203X\203g\202\315\225s\226\276\202\305\202\267\201B"
>>> print(msg.decode('shift_jis'))
そのようなホストは不明です。 

「そのようなホストは不明です。 」 is Japanese message which means "No such host is known.".

I think that this is because of gai_strerror() referring thread locale(I think gai_strerror() calls FormatMessage internally.).

Supporting non-ASCII logging seems to be slightly difficult ( e.g. fix strvis within logging functions ) , please consider calling SetThreadUILanguage (ex calling within msetlocale()).

At my own environment, self-build ssh.exe calling SetThreadUILanguage within msetlocale() works good.

PS F:\repos\openssh-portable\bin\x64\Release> ./ssh hoge
ssh: Could not resolve hostname hoge: No such host is known.