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

When entering a Chinese punctuation, it acts like keeping hitting the key #5186

New Issue
Closed
opened 2026-01-31 00:06:58 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 00:06:58 +00:00
Owner
Copy Link

Originally created by @wrvsrx on GitHub (Nov 26, 2019).

Environment

Windows build number: 10.0.19030.1
Windows Terminal version: 0.7.3291.0

Steps to reproduce

Hit the key "，" (or other punctuation) in windows terminal with Chinese input method

Expected behavior

Output a "，" (I delete the extra "，" in the following picture manually)

image

Actual behavior

keeps outputting "，" just like I keep hitting the "，"

image

Some other information

  1. I have reproduced it in Windows Terminal using wsl, cmd and powershell7-preview on my two PCs.
  2. Another phenomenon is that Windows Terminal add space behind Chinese character automatically after my inputting one character.
Originally created by @wrvsrx on GitHub (Nov 26, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19030.1 Windows Terminal version: 0.7.3291.0 ``` # Steps to reproduce Hit the key "，" (or other punctuation) in windows terminal with Chinese input method # Expected behavior Output a "，" (I delete the extra "，" in the following picture manually) ![image](https://user-images.githubusercontent.com/42770726/69660038-6f91a980-10ba-11ea-83df-0c8a7181f12d.png) # Actual behavior keeps outputting "，" just like I keep hitting the "，" ![image](https://user-images.githubusercontent.com/42770726/69659737-cd71c180-10b9-11ea-9430-0617081f5b9f.png) # Some other information 1. I have reproduced it in Windows Terminal using wsl, cmd and powershell7-preview on my two PCs. 2. Another phenomenon is that Windows Terminal add space behind Chinese character automatically after my inputting one character.
claunia commented 2026-01-31 00:07:00 +00:00
Author
Owner
Copy Link

@etern commented on GitHub (Nov 27, 2019):

For me, I have to type twice to input one Chinese puncutation, like period(。), I'm also using terminal version 0.7.3291.0

It reminds me this issue #2191 , one Chinese character rendered as two small charactors.
It seems wide character is not handled properly.

@etern commented on GitHub (Nov 27, 2019): For me, I have to type twice to input one Chinese puncutation, like period(。), I'm also using terminal version 0.7.3291.0 It reminds me this issue #2191 , one Chinese character rendered as two small charactors. It seems wide character is not handled properly.
claunia commented 2026-01-31 00:07:01 +00:00
Author
Owner
Copy Link

@ice1000 commented on GitHub (Dec 13, 2019):

I am in the same situation as @etern 's instead of OP's

@ice1000 commented on GitHub (Dec 13, 2019): I am in the same situation as @etern 's instead of OP's
claunia commented 2026-01-31 00:07:02 +00:00
Author
Owner
Copy Link

@Lemmingh commented on GitHub (Dec 16, 2019):

I have the same problem as @etern which has been discussed in #3745

Though looking opposite, I wonder whether these issues are related in some aspect.

Windows build number: 10.0.18363.535
Windows Terminal version : 0.7.3451.0
@Lemmingh commented on GitHub (Dec 16, 2019): I have the same problem as @etern which has been discussed in #3745 Though looking opposite, I wonder whether these issues are related in some aspect. --- ```none Windows build number: 10.0.18363.535 Windows Terminal version : 0.7.3451.0 ```
claunia commented 2026-01-31 00:07:02 +00:00
Author
Owner
Copy Link

@luxrck commented on GitHub (Dec 17, 2019):

I have encountered the same bug @wrvsrx

image

wt version: 0.7.3382.0

@luxrck commented on GitHub (Dec 17, 2019): I have encountered the same bug @wrvsrx ![image](https://user-images.githubusercontent.com/4439100/70957691-e3b7df80-20b1-11ea-8708-176788404255.png) wt version: 0.7.3382.0
claunia commented 2026-01-31 00:07:02 +00:00
Author
Owner
Copy Link

@wrvsrx commented on GitHub (Dec 17, 2019):

Recently, I test it on another PC whose windows build number is 10.0.18363.535, and it behave like what #3745 describes. Comparing this to windows terminal's behavior mentioned above on my PC with windows build number 10.0.19030.1, I think it might be related to the windows version.

@wrvsrx commented on GitHub (Dec 17, 2019): Recently, I test it on another PC whose windows build number is 10.0.18363.535, and it behave like what #3745 describes. Comparing this to windows terminal's behavior mentioned above on my PC with windows build number 10.0.19030.1, I think it might be related to the windows version.
claunia commented 2026-01-31 00:07:03 +00:00
Author
Owner
Copy Link

@luxrck commented on GitHub (Dec 17, 2019):

@wrvsrx And my windows version is: 10.0.19037.1
Seems that it did relate to the win10 version......

@luxrck commented on GitHub (Dec 17, 2019): @wrvsrx And my windows version is: 10.0.19037.1 Seems that it did relate to the win10 version......
claunia commented 2026-01-31 00:07:03 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 14, 2020):

:tada:This issue was addressed in #4140, which has now been successfully released as Windows Terminal Preview v0.8.10091.0.🎉

Handy links:

@ghost commented on GitHub (Jan 14, 2020): :tada:This issue was addressed in #4140, which has now been successfully released as `Windows Terminal Preview v0.8.10091.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.8.10091.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?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 Help Wanted Issue-Bug Priority-1 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#5186
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?