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

Cannot input Hanja(한자) from Korean(한글) IME keyboard. #16537

Closed
3735943886 opened this issue Jan 8, 2024 · 1 comment
Closed

Cannot input Hanja(한자) from Korean(한글) IME keyboard. #16537

3735943886 opened this issue Jan 8, 2024 · 1 comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@3735943886
Copy link

Windows Terminal version

1.18.3181.0

Windows build number

10.0.22631.2861

Other Software

No response

Steps to reproduce

Simply type any completed korean character (at least one consonant + one vowel, ie ㄱ+ㅏ=가).
Press hanja(한자) key.
Select any hanja from pop up.

Expected Behavior

The korean character should be changed to selected hanja chanracter.

Actual Behavior

Nothing.

2024-01-08.144057.mp4
@3735943886 3735943886 added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jan 8, 2024
@lhecker
Copy link
Member

lhecker commented Jan 8, 2024

In #14349 I've come to the realization that we need to replace the IME implementation in Windows Terminal with the one from conhost. That one is much more robust and we expect it to fix issues like yours. While your issue and #14349 aren't exactly the same I'd still like to use #14349 to track this, since it's older and got more history. Your can subscribe to that issue to be notified of my progress on this. Thanks for giving me another test case with which I can test my changes though!

@lhecker lhecker closed this as not planned Won't fix, can't repro, duplicate, stale Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants