Emoji breaks with line breaks #22567

Closed
opened 2026-01-31 08:17:10 +00:00 by claunia · 5 comments
Owner

Originally created by @gcgbarbosa on GitHub (Nov 19, 2024).

Windows Terminal version

1.21.2911.0

Windows build number

10.0.26100.2033

Other Software

zsh 5.8.1 (x86_64-ubuntu-linux-gnu)

Steps to reproduce

  1. Write a sentence with an emoji.
  2. Resize the window horizontally until you get the same behavior in the image below.

Image

Expected Behavior

The emoji should be rendered correctly, either on the same line or next line.

Actual Behavior

The emoji is not displayed correctly. Half of the emoji is rendered on the same line, and ️the other half is an unrecognized symbol.

Originally created by @gcgbarbosa on GitHub (Nov 19, 2024). ### Windows Terminal version 1.21.2911.0 ### Windows build number 10.0.26100.2033 ### Other Software zsh 5.8.1 (x86_64-ubuntu-linux-gnu) ### Steps to reproduce 1. Write a sentence with an emoji. 2. Resize the window horizontally until you get the same behavior in the image below. ![Image](https://github.com/user-attachments/assets/c1e8451b-c03f-4429-b2a9-165d7e7b077e) ### Expected Behavior The emoji should be rendered correctly, either on the same line or next line. ### Actual Behavior The emoji is not displayed correctly. Half of the emoji is rendered on the same line, and ️the other half is an unrecognized symbol.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:17:11 +00:00
Author
Owner

@gcgbarbosa commented on GitHub (Nov 19, 2024):

just found #18167, but maybe this is still relevant?

@gcgbarbosa commented on GitHub (Nov 19, 2024): just found #18167, but maybe this is still relevant?
Author
Owner

@DHowett commented on GitHub (Nov 19, 2024):

Which emoji is that/?

@DHowett commented on GitHub (Nov 19, 2024): Which emoji is that/?
Author
Owner

@gcgbarbosa commented on GitHub (Nov 19, 2024):

☁️, but the problem seems related to UTF-16. I've tested with UTF-8 and it works with no issue.

@gcgbarbosa commented on GitHub (Nov 19, 2024): ☁️, but the problem seems related to UTF-16. I've tested with UTF-8 and it works with no issue.
Author
Owner

@DHowett commented on GitHub (Nov 19, 2024):

FWIW, Terminal stores everything as UTF-16... even if the application writing to it writes UTF-8.

As I can't reproduce this in 1.22 I am guessing it was fixed in #16916, where we rewrote our handling of text that takes multiple code units. I'd encourage you to try it out in Windows Terminal Preview!

/dup #8000

@DHowett commented on GitHub (Nov 19, 2024): FWIW, Terminal stores everything as UTF-16... even if the application writing to it writes UTF-8. As I can't reproduce this in 1.22 I am guessing it was fixed in #16916, where we rewrote our handling of text that takes multiple code units. I'd encourage you to try it out in [Windows Terminal Preview](https://aka.ms/terminal-preview)! /dup #8000
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Nov 19, 2024):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Nov 19, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22567