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

Box-drawing characters in the Fira Mono font are not connected in the latest preview version of Terminal #17431

New Issue
Closed
opened 2026-01-31 05:42:17 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:42:17 +00:00
Owner
Copy Link

Originally created by @MatejKafka on GitHub (May 9, 2022).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.13.10983.0

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

  1. Download the following font: https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/FiraMono/Regular/complete
  2. Configure both Terminal and Terminal Preview to use this font
  3. Run the following PowerShell command: echo "╦═════════`n╚╣"
  4. Zoom to various scales, compare the rendering in both Terminal versions.

Expected Behavior

In both versions, the glyphs should be connected into uniform lines.

Actual Behavior

Terminal Preview v1.13.10983.0:
disconnected glyphs – the vertical line is always broken, the horizontal line is rendered correctly at some font sizes, and incorrectly at others
Screenshot 2022-05-09 134109

Terminal (Stable) v1.12.10982.0:
rendered correctly
Screenshot 2022-05-09 134133

Originally created by @MatejKafka on GitHub (May 9, 2022). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.13.10983.0 ### Windows build number 10.0.19044.0 ### Other Software _No response_ ### Steps to reproduce 1. Download the following font: https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/FiraMono/Regular/complete 2. Configure both Terminal and Terminal Preview to use this font 3. Run the following PowerShell command: ```echo "╦═════════`n╚╣"``` 4. Zoom to various scales, compare the rendering in both Terminal versions. ### Expected Behavior In both versions, the glyphs should be connected into uniform lines. ### Actual Behavior Terminal Preview v1.13.10983.0: **disconnected glyphs** – the vertical line is always broken, the horizontal line is rendered correctly at some font sizes, and incorrectly at others ![Screenshot 2022-05-09 134109](https://user-images.githubusercontent.com/6414091/167396376-da00158a-c27e-4317-96c2-2bfe66facd92.png) Terminal (Stable) v1.12.10982.0: **rendered correctly** ![Screenshot 2022-05-09 134133](https://user-images.githubusercontent.com/6414091/167396481-5276fcb8-0e25-445a-8aaa-fc2b40f9e421.png)
claunia added the Area-RenderingIssue-BugIn-PRProduct-Terminal labels 2026-01-31 05:42:18 +00:00
claunia commented 2026-01-31 05:42:19 +00:00
Author
Owner
Copy Link

@christianparpart commented on GitHub (May 16, 2022):

Out of curiosity. And you did not update the Fira Code font files in between the WT updates? To me this looks like a metric change. Box drawing characters are never easy to be rendered from font files in a monospaced grid system (TEs), and because of that, most terminals do implement pixel perfect rendering for certain codepoints explicitly, bypassing the font file all along for them.
I am not sure if WT does that (to some degree already), but my point of view is, there's always one font file that has shitty glyphs for box drawing codepoints and will always fail. :)

@christianparpart commented on GitHub (May 16, 2022): Out of curiosity. And you did not update the Fira Code font files in between the WT updates? To me this looks like a metric change. Box drawing characters are never easy to be rendered from font files in a monospaced grid system (TEs), and because of that, most terminals do implement pixel perfect rendering for certain codepoints explicitly, bypassing the font file all along for them. I am not sure if WT does that (to some degree already), but my point of view is, there's always one font file that has shitty glyphs for box drawing codepoints and will always fail. :)
claunia commented 2026-01-31 05:42:19 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 28, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (May 28, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:42:20 +00:00
Author
Owner
Copy Link

@MatejKafka commented on GitHub (Jun 2, 2022):

And you did not update the Fira Code font files in between the WT updates?

Nope, I installed both versions of WT side-by-side and used the same font for both.

@MatejKafka commented on GitHub (Jun 2, 2022): > And you did not update the Fira Code font files in between the WT updates? Nope, I installed both versions of WT side-by-side and used the same font for both.
claunia commented 2026-01-31 05:42:20 +00:00
Author
Owner
Copy Link

@kindermannhubert commented on GitHub (Mar 12, 2023):

I have the same problem with Cascadia Code (I have WT 1.16.10261.0).
image

vs this screenshot from cmd.exe:
image

@kindermannhubert commented on GitHub (Mar 12, 2023): I have the same problem with Cascadia Code (I have WT 1.16.10261.0). ![image](https://user-images.githubusercontent.com/11704036/224552017-1c499d91-f499-4c0d-bb50-d2c93d8239ab.png) vs this screenshot from cmd.exe: ![image](https://user-images.githubusercontent.com/11704036/224552087-bb4f3286-f042-4f1b-bc6b-2280ebe3858f.png)
claunia commented 2026-01-31 05:42:20 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Apr 5, 2023):

This may be fixed definitively by #14959. If not, we'll soon be releasing a preview update that allows you to configure the line height #14255.

@carlos-zamora commented on GitHub (Apr 5, 2023): This may be fixed definitively by #14959. If not, we'll soon be releasing a preview update that allows you to configure the line height #14255.
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 Area-Rendering In-PR Issue-Bug Product-Terminal
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#17431
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?