Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to permanently set codepage to 65001 in wt.exe #1852

Closed
rivy opened this issue Jul 6, 2019 · 2 comments
Closed

Unable to permanently set codepage to 65001 in wt.exe #1852

rivy opened this issue Jul 6, 2019 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@rivy
Copy link

rivy commented Jul 6, 2019

Environment

C:\>ver
Microsoft Windows [Version 10.0.18362.175]

C:\>where wt.exe
C:\Users\Roy\AppData\Local\Microsoft\WindowsApps\wt.exe

C:\>echo %LocalAppData%
LOCALAPPDATA=C:\Users\Roy\AppData\Local

Steps to reproduce

Setting "CodePage" within the registry doesn't result in the correct code page within the wt terminal window.

Neither this ...

C:\>C:\Windows\System32\reg.exe add HKCU\Console\%LocalAppData^%_Microsoft_WindowsApps_wt.exe /v CodePage /t REG_DWORD /d 65001 /f
The operation completed successfully.

nor this ...

C:\>C:\Windows\System32\reg.exe add HKCU\Console\C:_Users_Roy_AppData_Local_Microsoft_WindowsApps_wt.exe /v CodePage /t REG_DWORD /d 65001 /f
The operation completed successfully.

result in the correct codepage within the wt terminal window..

Expected behavior

C:>chcp
Active code page: 65001

Actual behavior

C:\>chcp
Active code page: 437
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 6, 2019
@rivy
Copy link
Author

rivy commented Jul 6, 2019

I can force the codepage to 65001 by enabling BETA: Use Unicode UTF-8 for worldwide language support in the "Control Panel \ Clock and Region \ Region \ Administrative \ Change system locale..." dialog box and rebooting.

But, I would expect a less global setting to be available.

@DHowett-MSFT
Copy link
Contributor

This boils down to #1802. You’re unable to set the console codepage for WT using the Console registry keys because wt is not a console application. Those keys only apply to things that run INSIDE consoles, not things that ARE console hosts.

What we need is a way for WT to force its connected console hosts to be in codepage 65001. That’s the essence of 1802.

@DHowett-MSFT DHowett-MSFT added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 6, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants