Closed ClaireCJS closed 1 week ago
Possible duplicate of #18145 if this is the reason you can also do this:
There are 2 reasons this happens
You're using U+2764 ❤ in its "unqualified" version. This means it gets 1 cell and it's up to the text renderer to decide how it should look like. Our text rasterizer (DirectWrite) uses color in that case. This way you end up with a colored emoji that gets only 1 cell and thus ends up overlapping surrounding glyphs/characters.
The solution is for you to use ❤️ (U+2764 U+FE0F) instead of ❤ (U+2764) and to use Windows Terminal 1.22 or later which has support for grapheme clusters (= can detect such pairs of U+FE0F).
Let me know if you have any other questions!
FWIW, if it seems weird that they can overlap... this is the "social standard" way that other terminal emulators have chosen to render them as well. Apple's Terminal.app
does the same.
The ability to trivially overlap glyphs is a prerequisite for proper rendering of Arabic, Devanagari, Sinhala and others. :)
Windows Terminal version
1.21.2911.0
Windows build number
10.0.19045.5011
Other Software
I'm just echoing characters to the console from my command line (TCC)
Steps to reproduce
In TCC:
In CMD:
(but it is possible it is not encoded correctly here in the comment, as it is not rendered red. Grab the ones from the subject line instead, those appear rendered correctly. Maybe it makes no difference.)
Expected Behavior
I was expecting
Actual Behavior
What?!?!?! A ligature of hearts????
Is this intentional?
Is there a list of all the emoji ligatures? [I lost the ligature list and can't find it]
Do you accept user-contributed artwork of new emoji-combination-ligatures, if they are up to visual quality standards?