Pasting text in powershell session drops unicode punctuation #12930

Closed
opened 2026-01-31 03:29:14 +00:00 by claunia · 2 comments
Owner

Originally created by @wuqiling97 on GitHub (Mar 9, 2021).

Environment

Windows build number: 10.0.19042.0
Windows Terminal version (if applicable): 1.7.572.0

powershell 5.1 and 7.1.2

Steps to reproduce

  1. Open freshly installed windows terminal from MS Store
  2. Paste string containing unicode punctuation, like “”‘’〈〉《》「」『』!"#$%&'()*+,-./[\]^_`

Expected behavior

String will be pasted normally

Actual behavior

Only the unicode punctuation at the head of string will be preserved. ASCII punctuation will always be preserved

For example

  • “”‘’〈〉《》 will turn into
  • “,”,‘’,〈,〉《》 -> “,,,,
  • a“b”c‘d’〈〉《》 -> abcd

CMD in windows terminal does not have this bug

Originally created by @wuqiling97 on GitHub (Mar 9, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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.19042.0 Windows Terminal version (if applicable): 1.7.572.0 powershell 5.1 and 7.1.2 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open freshly installed windows terminal from MS Store 2. Paste string containing unicode punctuation, like `“”‘’〈〉《》「」『』!"#$%&'()*+,-./[\]^_`` # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> String will be pasted normally # Actual behavior <!-- What's actually happening? --> Only the unicode punctuation at the head of string will be preserved. ASCII punctuation will always be preserved For example - `“”‘’〈〉《》` will turn into `“` - `“,”,‘’,〈,〉《》` -> `“,,,,` - `a“b”c‘d’〈〉《》` -> `abcd` CMD in windows terminal does not have this bug
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:29:14 +00:00
Author
Owner

@skyline75489 commented on GitHub (Mar 9, 2021):

I think this is the same as #9263

@skyline75489 commented on GitHub (Mar 9, 2021): I think this is the same as #9263
Author
Owner

@wuqiling97 commented on GitHub (Mar 9, 2021):

I think this is the same as #9263

Oh that's right, thank you

@wuqiling97 commented on GitHub (Mar 9, 2021): > I think this is the same as #9263 Oh that's right, thank you
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12930