starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Closed
opened 2026-01-31 07:32:14 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 07:32:14 +00:00
Owner
Copy Link

Originally created by @3735943886 on GitHub (Jan 8, 2024).

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.

https://github.com/microsoft/terminal/assets/9522390/82fcf5b3-fe87-4083-9179-1b661705bcbf

Originally created by @3735943886 on GitHub (Jan 8, 2024). ### 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. https://github.com/microsoft/terminal/assets/9522390/82fcf5b3-fe87-4083-9179-1b661705bcbf
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:32:15 +00:00
claunia commented 2026-01-31 07:32:16 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (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 commented on GitHub (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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21069
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?