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.

Sign up for GitHub

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

Jump to bottom

Bug Report. Cannot type korean language to the console. #2402

Closed
JuhoKang opened this issue Aug 12, 2019 · 4 comments
Closed

Bug Report. Cannot type korean language to the console. #2402

JuhoKang opened this issue Aug 12, 2019 · 4 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@JuhoKang
Copy link

English is good but I can't type anything with Korean. I can copy and paste the text, but cannot type it. It feels like it just doesn't support Korean input. I can see text output so maybe it would not be a problem with fonts.

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.267]
Windows Terminal version (if applicable): Windows Terminal (Preview) 0.3.2171.0

The font was Consolas.

Steps to reproduce

  1. Open any type of terminal.
  2. change system language like usual
  3. (with 한/영 key (language change key), or click the language change button on the taskbar)
  4. write some text.

Expected behavior

I can write Korean text to the terminal

Actual behavior

I cannot write Korean text to the terminal
@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 Aug 12, 2019
@fangjue
Copy link

fangjue commented Aug 12, 2019

Duplicate of issue #2213.

@zadjii-msft
Copy link
Member

I'm inclined to agree this is a dupe of #2213, save for one bit:

  1. Open any type of terminal.

@JuhoKang does this not work with conhost (cmd.exe, powershell.exe, wsl.exe)? Or is this only happening with the Windows Terminal?

I believe this scenario should work in conhost, and shouldn't have regressed recently.

@zadjii-msft zadjii-msft added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Aug 12, 2019
@CookieHCl
Copy link

CookieHCl commented Aug 12, 2019 •
edited
Loading

@zadjii-msft I'm not author, but I have same issue.
cmd, powershell, powershell core without windows terminal doesn't have issue, but cmd, powershell, powershell core with windows terminal won't get input with Korean.

@DHowett-MSFT
Copy link
Contributor

Okay, so this is #2213.

@DHowett-MSFT DHowett-MSFT added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Aug 12, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@fangjue @JuhoKang @DHowett-MSFT @zadjii-msft @CookieHCl