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

Sending unicode character via KEYEVENTF_UNICODE/VK_PACKET in SendInput outputs the wrong characters #17336

New Issue
Closed
opened 2026-01-31 05:39:34 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:39:34 +00:00
Owner
Copy Link

Originally created by @jtroo on GitHub (Apr 25, 2022).

Windows Terminal version

1.12.10982.0

Windows build number

10.0.19043

Other Software

Reproducible in:

  • cmd.exe
  • wsl ubuntu 20.04

powershell just displays ?? , not sure which behaviour is more incorrect

Uses SendInput:
https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-sendinput

Steps to reproduce

Via SendInput, send the unicode character 🙁

E.g. in
https://github.com/jtroo/kanata/blob/master/src/oskbd/windows.rs#L168

Expected Behavior

The correct unicode value gets typed in: 🙁

Actual Behavior

The characters 翿翿 are typed in instead

Additional info

When copy-pasting the unicode character, it's rendered correctly (in cmd/wsl). It's just not typed correctly via SendInput.

Originally created by @jtroo on GitHub (Apr 25, 2022). ### Windows Terminal version 1.12.10982.0 ### Windows build number 10.0.19043 ### Other Software Reproducible in: - cmd.exe - wsl ubuntu 20.04 powershell just displays `?? `, not sure which behaviour is more incorrect Uses SendInput: https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-sendinput ### Steps to reproduce Via SendInput, send the unicode character 🙁 E.g. in https://github.com/jtroo/kanata/blob/master/src/oskbd/windows.rs#L168 ### Expected Behavior The correct unicode value gets typed in: 🙁 ### Actual Behavior The characters `翿翿` are typed in instead ### Additional info When copy-pasting the unicode character, it's rendered correctly (in cmd/wsl). It's just not typed correctly via SendInput.
claunia commented 2026-01-31 05:39:37 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 27, 2022):

For reference:
🙁: https://www.compart.com/en/unicode/U+1F641
翿: https://www.compart.com/en/unicode/U+7FFF

@lhecker commented on GitHub (Apr 27, 2022): For reference: 🙁: https://www.compart.com/en/unicode/U+1F641 翿: https://www.compart.com/en/unicode/U+7FFF
claunia commented 2026-01-31 05:39:37 +00:00
Author
Owner
Copy Link

@miozus commented on GitHub (Jun 18, 2022):

the problem still appear.

，： => 翿

image

@miozus commented on GitHub (Jun 18, 2022): the problem still appear. ，： => 翿 ![image](https://user-images.githubusercontent.com/35659194/174417340-b56df550-d38b-43f1-aa7f-48c870a5fa16.png)
claunia commented 2026-01-31 05:39:38 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 4, 2022):

In conhost (the old terminal) this issue is caused by COOKED_READ_DATA and will take a while to fix (and it's outside of the scope of this issue).

In Windows Terminal I've narrowed this down to being caused by the Win32 Input Mode. You can work around this issue by adding "experimental.input.forceVT": true in your settings.json file (in the global global scope - this setting isn't per profile).

Edit: This is caused by MAX_PARAMETER_VALUE clamping the character parameter to 0x7fff.

@lhecker commented on GitHub (Aug 4, 2022): In conhost (the old terminal) this issue is caused by `COOKED_READ_DATA` and will take a while to fix (and it's outside of the scope of this issue). In Windows Terminal I've narrowed this down to being caused by the Win32 Input Mode. You can work around this issue by adding `"experimental.input.forceVT": true` in your `settings.json` file (in the global global scope - this setting isn't per profile). Edit: This is caused by `MAX_PARAMETER_VALUE` clamping the character parameter to 0x7fff.
claunia commented 2026-01-31 05:39:38 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 18, 2022):

:tada:This issue was addressed in #13667, which has now been successfully released as Windows Terminal v1.14.228.🎉

Handy links:

@ghost commented on GitHub (Aug 18, 2022): :tada:This issue was addressed in #13667, which has now been successfully released as `Windows Terminal v1.14.228`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.14.228) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 05:39:38 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 18, 2022):

:tada:This issue was addressed in #13667, which has now been successfully released as Windows Terminal Preview v1.15.228.🎉

Handy links:

@ghost commented on GitHub (Aug 18, 2022): :tada:This issue was addressed in #13667, which has now been successfully released as `Windows Terminal Preview v1.15.228`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.15.228) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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 Area-Input Area-TerminalControl Issue-Bug Needs-Triage Priority-2 Product-Terminal Resolution-Fix-Committed
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#17336
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?