Font Glyphs are cut off by the Windows Terminal #7113

@DoCode commented on GitHub (Mar 24, 2020):

No ligatures, but oversized glyphs. But I preserve space for it with one empty char as postfix for each oversized glyph.

But why only Windows Terminal struggled with this?

@DoCode commented on GitHub (Mar 24, 2020): No ligatures, but oversized glyphs. But I preserve space for it with one empty char as postfix for each oversized glyph. But why only Windows Terminal struggled with this?

claunia commented

@fabienheureux commented on GitHub (Mar 24, 2020):

Well, I honestly don't know...but as the v1.0 is not yet released, this is understandable.

@fabienheureux commented on GitHub (Mar 24, 2020): Well, I honestly don't know...but as the v1.0 is not yet released, this is understandable.

claunia commented

@skyline75489 commented on GitHub (Mar 24, 2020):

@DoCode How do you print this kind of 'oversized' glyph, though. I've tried echo -e '\U0001f602' it only gives me a regular sized folder.

@skyline75489 commented on GitHub (Mar 24, 2020): @DoCode How do you print this kind of 'oversized' glyph, though. I've tried `echo -e '\U0001f602'` it only gives me a regular sized folder.

claunia commented

@DoCode commented on GitHub (Mar 24, 2020):

@fabienheureux - ok thanks.
So I hope MS would address this issue for the 1.0 milestone.

@DoCode commented on GitHub (Mar 24, 2020): @fabienheureux - ok thanks. So I hope MS would address this issue for the 1.0 milestone.

claunia commented

@DoCode commented on GitHub (Mar 24, 2020):

@DoCode How do you print this kind of 'oversized' glyph, though. I've tried echo -e '\U0001f602' it only gives me a regular sized folder.

@skyline75489 - I print this kind with simple following a whitespace, like echo -e '\uF07C'' ' to preserve overlapping.

This works on all platforms and terminals, except the new Windows Terminal!

@DoCode commented on GitHub (Mar 24, 2020): > @DoCode How do you print this kind of 'oversized' glyph, though. I've tried `echo -e '\U0001f602'` it only gives me a regular sized folder. @skyline75489 - I print this kind with simple following a whitespace, like `echo -e '\uF07C'' '` to preserve overlapping. > This works on all platforms and terminals, except the new Windows Terminal!

claunia commented

@zadjii-msft commented on GitHub (Mar 24, 2020):

@DoCode could you share what font you're using as well?

Also, are you sure that \uF07C is the glyph you want? I'm pretty sure that's not a valid unicode character. \U0001F5C1 looks a bit like what you want...

@zadjii-msft commented on GitHub (Mar 24, 2020): @DoCode could you share what font you're using as well? Also, are you sure that `\uF07C` is the glyph you want? I'm pretty sure that's [not a valid unicode character](https://www.fileformat.info/info/unicode/char/f07c/index.htm). [`\U0001F5C1`](https://www.fileformat.info/info/unicode/char/1f5c1/index.htm) looks a bit like what you want...

claunia commented

@DoCode commented on GitHub (Mar 24, 2020):

@zadjii-msft yes, \uF07C, that's the glyph I want. It's ported from powerleve10k and this used larger icons. Works like a charm as I said.

Here's the font I used.

@DoCode commented on GitHub (Mar 24, 2020): @zadjii-msft yes, `\uF07C`, that's the glyph I want. It's ported from powerleve10k and this used larger icons. Works like a charm as I said. [Here's](https://github.com/microsoft/terminal/files/4375852/cascadia-nerd-font-complete.zip) the font I used.

claunia commented

@DoCode commented on GitHub (Mar 24, 2020):

FYI, also the integrated VS Code terminal works like a charm:

@DoCode commented on GitHub (Mar 24, 2020): FYI, also the integrated VS Code terminal works like a charm: ![image](https://user-images.githubusercontent.com/1489133/77440470-a2d61200-6de8-11ea-864a-fb7c79c2f507.png)

claunia commented

@jdebp commented on GitHub (Mar 24, 2020):

U+F07C is in the Unicode Private Use Area. Powerline, and "nerd fonts", fill this up with a whole bunch of stuff. Their users are sometimes surprised, in my experience, to learn that Private Use Area really does mean something that does not work the same everywhere. In this case, Windows Terminal is treating the character as a narrow character. The whole Private Use range is marked as "ambiguous" width in the Unicode standard.

U+1F5C1 is a standard character, with narrow width. Amusingly, Unicode version 13 now gives you U+1FBB9 and U+1FBBA for making a wide folder icon in a text display, in the way that computer people used to. (-:

@jdebp commented on GitHub (Mar 24, 2020): U+F07C is in the Unicode Private Use Area. Powerline, and ["nerd fonts"](https://github.com/ryanoasis/nerd-fonts/wiki/Glyph-Sets-and-Code-Points), fill this up with a whole bunch of stuff. Their users are sometimes surprised, in my experience, to learn that Private Use Area _really does mean_ something that does not work the same everywhere. In this case, Windows Terminal is treating the character as a narrow character. The whole Private Use range is marked as "ambiguous" width in the Unicode standard. U+1F5C1 is a standard character, with narrow width. Amusingly, Unicode version 13 now gives you U+1FBB9 and U+1FBBA for making a wide folder icon in a text display, in the way that computer people used to. (-:

claunia commented

@DoCode commented on GitHub (Mar 24, 2020):

@jdebp thanks for the detailed explanation.
I will try your suggestions about unicode version 13.
However, I don't think it's okay that Windows Terminal doesn't behave like all other terminals. This will annoy many users. Windows Terminal is not the first and primary terminal on the market and should be as compatible as possible.

@DoCode commented on GitHub (Mar 24, 2020): @jdebp thanks for the detailed explanation. I will try your suggestions about unicode version 13. However, I don't think it's okay that Windows Terminal doesn't behave like all other terminals. This will annoy many users. Windows Terminal is not the first and primary terminal on the market and should be as compatible as possible.

claunia commented

@waltermaldonado commented on GitHub (Mar 24, 2020):

I can confirm the same behavior here, but it is not present only in the Windows Terminal app. If Iuse WSL with the default terminal app, I get the icons from lsd cut off too.

Look closely to the folder's icons.

@waltermaldonado commented on GitHub (Mar 24, 2020): I can confirm the same behavior here, but it is not present only in the Windows Terminal app. If Iuse WSL with the default terminal app, I get the icons from lsd cut off too. Look closely to the folder's icons. ![image](https://user-images.githubusercontent.com/8573950/77487419-302d5c80-6e11-11ea-853f-412a765cdf6c.png) ![image](https://user-images.githubusercontent.com/8573950/77487464-49cea400-6e11-11ea-82b9-713c00eb55e7.png)

claunia commented