starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Closed
opened 2026-01-31 07:29:08 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 07:29:08 +00:00
Owner
Copy Link

Originally created by @marcIhm on GitHub (Dec 7, 2023).

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).
Screenshot 2023-12-07 074953

Actual Behavior

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

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
Originally created by @marcIhm on GitHub (Dec 7, 2023). ### 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). <img width="960" alt="Screenshot 2023-12-07 074953" src="https://github.com/microsoft/terminal/assets/12209310/b8d79b6d-1cb1-4baa-bd41-016448fc8ab2"> ### Actual Behavior There is only a thin vertical line (1 pixel wide ?) in the lower right quadrant; most of the rest is unfilled. <img width="960" alt="Screenshot 2023-12-07 073806" src="https://github.com/microsoft/terminal/assets/12209310/7d78b182-c5b0-4921-9ff9-b0035151c969"> 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
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:29:09 +00:00
claunia commented 2026-01-31 07:29:10 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 7, 2023):

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:

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

@github-actions[bot] commented on GitHub (Dec 7, 2023): 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 not showing correctly (#8451)](https://github.com/microsoft/terminal/issues/8451), similarity score: 0.82 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:29:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 7, 2023):

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.

@DHowett commented on GitHub (Dec 7, 2023): 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.
claunia commented 2026-01-31 07:29:10 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Dec 7, 2023):

Maybe this is font problem?

Screenshot 2023-12-07 101558

@237dmitry commented on GitHub (Dec 7, 2023): Maybe this is font problem? ![Screenshot 2023-12-07 101558](https://github.com/microsoft/terminal/assets/78153320/9a3b3e32-9080-471e-b8f6-e927c415a419)
claunia commented 2026-01-31 07:29:10 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Dec 7, 2023):

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): https://github.com/microsoft/terminal/pull/15343#issuecomment-1548142384

#5897 would help a lot with this issue.

@lhecker commented on GitHub (Dec 7, 2023): 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): https://github.com/microsoft/terminal/pull/15343#issuecomment-1548142384 #5897 would help a lot with this issue.
claunia commented 2026-01-31 07:29:11 +00:00
Author
Owner
Copy Link

@marcIhm commented on GitHub (Dec 7, 2023):

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:

Screenshot 2023-12-07 213159

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:

Screenshot 2023-12-07 213431

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 ...

@marcIhm commented on GitHub (Dec 7, 2023): 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: <img width="960" alt="Screenshot 2023-12-07 213159" src="https://github.com/microsoft/terminal/assets/12209310/497e614a-9d72-492a-b6a5-5e1cbdfb1a96"> 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: <img width="960" alt="Screenshot 2023-12-07 213431" src="https://github.com/microsoft/terminal/assets/12209310/190f815a-d73e-4a16-9400-d745ff5d04fe"> 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 ...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Attention Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20963
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?