dotnet cli produces `?`s in output

Steps to reproduce

Run dotnet --help

Expected behavior

Readable text should output.

Actual behavior

????????? ????????? ?????? .NET (2.0.2)
?????????????: dotnet [runtime-options] [path-to-application]
?????????????: dotnet [sdk-options] [command] [arguments] [command-options]

path-to-application:
  ???? ? DLL-????? ??????????, ??????? ?????????? ?????????.

??????? SDK:
  new              ????????????? ???????? .NET.
  restore          ?????????????? ????????????, ????????? ? ???????? .NET.
  run              ?????????? ? ??????????? ?????????? ??????? .NET.
  build            ?????? ??????? .NET.
  publish          ?????????? ??????? .NET ??? ????????????? (??????? ????? ??????????).
  test             ?????????? ?????? ? ??????? ???????? ?????????? ??????, ?????????? ? ???????.
  pack             ???????? ?????? NuGet.
  migrate          ???????? ??????? ?? ?????? project.json ? ?????? ?? ?????? msbuild.
  clean            ??????? ???????? ?????? ??????.
  sln              ????????? ?????? ??????? (SLN).
  add              ?????????? ?????? ? ??????.
  remove           ???????? ?????? ?? ???????.
  list             ?????? ?????? ? ???????.
  nuget            ?????????????? ?????????????? ?????? NuGet.
  msbuild          ?????? Microsoft Build Engine (MSBuild).
  vstest           ?????? ????????? ????????? ?????? ?????????? ??? ?????????? ??????.

????? ?????????:
  -v|--verbosity        ????????? ?????? ??????????? ??? ???????. ?????????? ????????: q[uiet], m[inimal], n[ormal], d[etailed] ? diag[nostic].
  -h|--help             ???????? ???????.

????????? ??????? "dotnet ??????? --help" ??? ????????? ?????????????? ?????????? ? ???????.

sdk-options:
  --version        ??????????? ?????? ?????? SDK ??? .NET Core.
  --info           ??????????? ???????? ? .NET Core.
  -d|--diagnostics ????????? ???????? ?????? ???????????.

runtime-options:
  --additionalprobingpath <path>    ???? ? ???????? ???????? ? ??????????? ???????.
  --fx-version <version>            ?????? ????????????? ????? ?????????, ??????? ??????? ???????????? ??? ??????? ??????????.
  --roll-forward-on-no-candidate-fx ???? ????????????? ????? ????????? ?? ????????, ??????????? ?????.
  --additional-deps <path>          ???? ? ??????????????? ????? deps.json.

Environment data

dotnet --info output:

????????? ????????? ?????? .NET (2.0.2)

Product Information:
 Version:            2.0.2
 Commit SHA-1 hash:  a04b4bf512

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.15063
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.0.2\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

[nguerrera]

To summarize and add more detail, this issue can happen if you’re “language for non-Unicode programs” (console counts as one of those) / “System locale” does not match the Windows display language.

To fix that:

1. Start ->Control Panel
2. Clock, Language and Region
3. Region
4. Administrative tab
5. Language for non-Unicode programs -> Change system locale
6. Pick a language that matches Windows’ display language

Also check that your command prompt is using a font that supports the characters in your display language:

1. Start -> Command Prompt
2. Click on command prompt icon in top left of window
3. Properties
4. Select an appropriate font

Alternatively, to force the CLI to English set environment variable DOTNET_CLI_UI_LANGUAGE=en-US

[yangsfang]

Hi. Coming from dotnet/cli#8685

What I don’t understand is why is non-unicode setting getting involved? Fall back to English would be nice, but doesn’t the dotnet cli print unicode characters, which could also display Russian or Japanese or any other character? I may be too inexperienced in character encoding to understand what the right solution is. Changing the non-unicode setting seems like a workaround and not a permanent solution. Powershell should have no problem handling unicode character at this age.