Unicode char 0x2597 (Quadrant lower right) et al. are not displayed correctly

[marcIhm]

Windows Terminal version

1.18.3181.0

Windows build number

10.0.22635.2841

Other Software

WSL2

Steps to reproduce

printf "\u2597\n" # within wsl2

Expected Behavior

The output should display a glyph with the lower right quadrant filled; just as shown in windows font selection (see screenshot).

Actual Behavior

There is only a thin vertical line (1 pixel wide ?) in the lower right quadrant; most of the rest is unfilled.

Some additional information:

• The behaviour above does not depend on the font chosen for wsl2 (ubuntu); in my case "Ubuntu Mono"; but it looks the same for "Lucida Console"
• The same glyph looks good in font "Segoe UI Symbol" (checked in: Windows Settings -> Fonts, see first screenshot)
• Other Unicode Block Characters are affected in a similar way
• This used to work two weeks ago (wsl2)
• In the meantime, some Windows-Updates happened and I played around with "chafa" (https://github.com/hpjansson/chafa) under wsl2; I assume that such a program should not be able to corrupt the glyph handling within "Windows Terminal" ...
• Background: The output of "figlet -f smblock 12345" within wsl2 looks ugly as a result of this issue (to try, you will need to install figlet first via "sudo apt install figlet toilet")
• Background: No such Problems (of course) when I boot Ubuntu directly and try the same in Gnome Terminal

[DHowett]

Are you, by chance, using the "new text rendering engine"? It's in Settings > Rendering. After you toggle it and save, you'll need to open a new tab or pane.

[237dmitry]

Maybe this is font problem?

[lhecker]

It is possible that this hasn't ever worked correctly in AtlasEngine. The fallback for "▗" comes from Segoe UI Symbol by default (as you've already shown), which doesn't have the same aspect ratio as your chosen font. Due to that the right half of it simply gets clipped off, which is something we currently do intentionally because of this (click play in the top right): #15343 (comment)

#5897 would help a lot with this issue.

[marcIhm]

For my case the problem lies in the "new text rendering engine". If I switch it off, everything is Okay again (at least for my concerns). See:

But interestingly this is only true for my favorite font "Lucida Console".
For other fonts (e.g. "Cascadia Code") things are a tiny bit more rough:

So I agree with lhecker: It does not work perfectly with AtlasEngine either, except from the "Lucida Console"-case (and maybe others), which fortunately applies to me :- )

So, yes, I agree, that #5897 would help a lot, as for example the GnomeTerminal does a very good job on this.
Therefore I hope, that you can fix #5897 before you remove the AtlasEngine.

Thanx a lot for your help !
I am closing this now, because (as you have shown to me), there are other relevant issues which describe the same problem already ...

P.s.: I cannot find this monofur font with "block chars", for that matter. Only some cropped (?) versions without block chars ...