Print period unlimited in Chinese input method #5813

Closed
opened 2026-01-31 00:22:26 +00:00 by claunia · 3 comments
Owner

Originally created by @Discreater on GitHub (Jan 7, 2020).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 0.7.3451.0

Steps to reproduce

  1. Open the terminal (powershell)
  2. Use Chinese input method
  3. Type c d or any other characters
  4. Type comma , or period .

Expected behavior

In the default powershell, it behaves normally. It printed “成都。” or something other else.
powershellNoBug

Actual behavior

But in this Terminal. It printed "成都。。。。。。。。。。...". The period after "成都“ was printed unlimited and I can't delete or change input method with keyboard until I changed
the input method with mouse.
terminalBug

Addition

The same thing happened to wsl. And in cmd, after I did the same thing, it print nothing but any character typed later wasn't displayed until I change the input method.

Originally created by @Discreater on GitHub (Jan 7, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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.19041.0 Windows Terminal version (if applicable): 0.7.3451.0 ``` # Steps to reproduce 1. Open the terminal (`powershell`) 2. **Use Chinese input method** 3. Type `c` `d` or any other characters 4. Type comma `,` or period `.` <!-- A description of how to trigger this bug. --> # Expected behavior In the default powershell, it behaves normally. It printed “成都。” or something other else. ![powershellNoBug](https://user-images.githubusercontent.com/41231596/71926258-de8c1300-31cd-11ea-94e8-42b6142d1c19.gif) <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior But in this Terminal. It printed "成都。。。。。。。。。。...". The period `。` after "成都“ was printed **unlimited** and I can't delete or change input method with keyboard until I changed the input method with mouse. ![terminalBug](https://user-images.githubusercontent.com/41231596/71925998-4beb7400-31cd-11ea-8d18-cc5657764ff1.gif) <!-- What's actually happening? --> # Addition The same thing happened to `wsl`. And in `cmd`, after I did the same thing, it print nothing but any character typed later wasn't displayed until I change the input method.
claunia added the Resolution-Duplicate label 2026-01-31 00:22:26 +00:00
Author
Owner

@j4james commented on GitHub (Jan 7, 2020):

I think this could be a duplicate of #3706.

@j4james commented on GitHub (Jan 7, 2020): I think this could be a duplicate of #3706.
Author
Owner

@zadjii-msft commented on GitHub (Jan 7, 2020):

Sure looks like a dupe to me. Thanks @j4james!

/dup #3706

@zadjii-msft commented on GitHub (Jan 7, 2020): Sure looks like a dupe to me. Thanks @j4james! /dup #3706
Author
Owner

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

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jan 7, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5813