[Loc]With .NET 7 Preview 3 SDK zip installed on local OS, some garbled characters appear when installing wasm-tools for the first time

[WenJunJi01]

Environment: .NET SDK 7.0.100-preview.3.22179.4(runtime-7.0.0-preview.3.22175.4)

Repro steps:

1. Set up a clean local OS machine with .NET SDK 7.0.100-preview.3.22179.4 zip installation
2. Run dotnet workload install wasm-tools --source https://pkgs.dev.azure.com/dnceng/public/_packaging/7.0.100-preview.3.22179.4-shipping-1/nuget/v3/index.json

Expected Result: wasm-tools workload install successfully in CLI and strings are localized well.

Actual Result: Some garbled characters appear when installing wasm-tools for the first time. SC: DE: TK:

Note: After uninstalling and reinstalling it, the localized characters can be displayed normally.

Dotnet info: .NET SDK (gemäß "global.json"): Version: 7.0.100-preview.3.22179.4 Commit: c48f2c30ee

Laufzeitumgebung: OS Name: Windows OS Version: 10.0.22000 OS Platform: Windows RID: win10-x64 Base Path: C:\tt\sdk\7.0.100-preview.3.22179.4\

Host (useful for support): Version: 7.0.0-preview.3.22175.4 Commit: 162f83657c

.NET SDKs installed: 7.0.100-preview.3.22179.4 [C:\tt\sdk]

.NET runtimes installed: Microsoft.AspNetCore.App 7.0.0-preview.3.22178.4 [C:\tt\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 7.0.0-preview.3.22175.4 [C:\tt\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 7.0.0-preview.3.22177.1 [C:\tt\shared\Microsoft.WindowsDesktop.App]

To install additional .NET runtimes or SDKs: https://aka.ms/dotnet-download

[WenJunJi01]

This issue can not repro with .NET 7 Preview 4 from main branch of https://github.com/dotnet/installer SDK version: 7.0.100-preview.4.22219.19(runtime-7.0.0-preview.4.22217.5) TK:

[vdanche]

The issue repro again with .net7 preview 5 coherent build-7.0.100-preview.5.22307.18 (runtime- 7.0.0-preview.5.22301.12 ) e.g JP

[vdanche]

this issue also happens when using dotnet pack for the first time. JP: SC:

[vdanche]

Still repro on .net 7 RC1 SDK when dotnet build project for the first time. E.g JP

[baronfel]

@vdanche @WenJunJi01 what terminal applications are you using? is this cmd shell, powershell, or something else entirely?

[nagilson]

Confirming this is reproable in the VS 2022 cmd for ja

[vdanche]

It's in cmd

[vdanche]

Still repro on NET7 RC2 SDK(7.0.100-rc.2.22471.15) e.g TK

[v-maylei6]

On the CHS OS, this issue still repro on the latest Dev17.5 preview 2 build(install form main branch), also repro on Dev17.5 preview 1 and Dev17.4 GA.

[nagilson]

It is quite strange how this could happen. Let's follow up @baronfel tomorrow to see if the fact that it's CMD is of any help.

[drasticactions]

@nagilson This also happened for me with Powershell Core and CMD; it did not matter which.

[nagilson]

The first CHCP page is set to 437 for me, but then when we set it manually by using the command chcp 65001 the symbols become ungarbled. Maybe we can manually force UTF-8 charsets at the beginning of the SDK invocation if DOTNET_CLI_UI_LANGUAGE differs and we don't interfere with UICulture.

[nagilson]

It appears this too is actually a duplicate of https://github.com/dotnet/sdk/issues/8833. Looking into a fix.

[nagilson]

A change has been merged and we expect this to be fixed in preview 1 of .NET 8.

[vdanche]

A change has been merged and we expect this to be fixed in preview 1 of .NET 8.

Checked on non-ENU OS(German/Janpanese) with NET SDK 8.0.100-alpha.1.23077.6 installed, this issue not repro. Thanks. German Japanese

[nagilson]

Heck yeah, thanks for confirming.

[vdanche]

@nagilson Currently this issue still repro on 7.0.200. There will be a fix on 7.0.20x, right?

[nagilson]

7.0.2xx is already closed for changes unfortunately, maybe we can port it to 7.0.300 though, or port it to 7.0.200 next month.

[vdanche]

7.0.2xx is already closed for changes unfortunately, maybe we can port it to 7.0.300 though, or port it to 7.0.200 next month. Ok, Thanks, currently repro on 7.0.300 preview sdk, we'll keep tracking.