Unexpected rendering behavior with U+1xxxx Unicode characters

[sba923]

Windows Terminal version

1.20.10572.0

Windows build number

10.0.22621.0

Other Software

PowerShell 7.4.1
PSReadLine 2.3.4

Steps to reproduce

1. Define the PSReadLine chord handler at Enable Alt+x to type in Unicode characters PowerShell/PSReadLine#3578 (comment)
2. Enter

'1f369 and hit Alt+x

Expected Behavior

I would expect

Actual Behavior

The emoji is rendered only after typing a closing '

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• Unicode characters not rendering correctly (#6136), similarity score: 0.93
• Unicode characters not rendering correctly in console (#222), similarity score: 0.86
• Unicode font rendering problem (#2711), similarity score: 0.85
• Inconsistent rendering of characters (#14232), similarity score: 0.81
• Unicode characters become ? at input but ok at output (#14894), similarity score: 0.78

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[elsaco]

Alacritty does it also:

[lhecker]

Unfortunately, PSReadLine doesn't support supplementary Unicode planes (= U+1xxxx) to begin with so this cannot be fixed in Windows Terminal. For instance, try pasting 🍩 and then backspace. You'll have to backspace twice, presumably because PowerShell internally sees it as the surrogate pair U+D83C U+DF69 and it doesn't know what a surrogate pair is. But just to be sure, I've debugged your repro test and sure enough, PowerShell sends us a literal "??" string.

It may be worth mentioning that Windows Terminal also has poor Unicode support. While it does support supplementary Unicode planes, it fails to support zero width joiners and marks, which means that emojis right now look like this:

The upcoming version 1.21 is planned to fix this and it'll then look like this:

[sba923]

Thanks for the clarification.

This was triggered by checking out https://github.com/StartAutomating/Emoji.

Probably doable to live with some limitations...