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

use font in "show all fonts" has render issues #16813

New Issue
Closed
opened 2026-01-31 05:23:47 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 05:23:47 +00:00
Owner
Copy Link

Originally created by @yingking on GitHub (Feb 18, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19042.1466

Other Software

No response

Steps to reproduce

open windows terminal, in settings simply choose "appearance -> Font face",check "Show all fonts",and choose "Ink Free" or some font not in the default font face,like this:
image
and it will render a long whitespace,but i did not type anything......
image
and in vim where are also lot of whitspace,but acturelly where are nothing...
image
I try it in another computer with windows terminal config with powershell,and meet the same issue.

Expected Behavior

right whitespace rendering,seems transparent error too.

Actual Behavior

image
image

Originally created by @yingking on GitHub (Feb 18, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19042.1466 ### Other Software _No response_ ### Steps to reproduce open windows terminal, in settings simply choose "appearance -> Font face",check "Show all fonts",and choose "Ink Free" or some font not in the default font face,like this: ![image](https://user-images.githubusercontent.com/32102128/154673771-5b8a9aa5-19c0-4358-8401-b0205e9f99e3.png) and it will render a long whitespace,but i did not type anything...... ![image](https://user-images.githubusercontent.com/32102128/154673916-e30a84c4-a5ef-4595-adb9-427707628cc2.png) and in vim where are also lot of whitspace,but acturelly where are nothing... ![image](https://user-images.githubusercontent.com/32102128/154674073-f4b3fa58-fab1-4e4b-9f08-61ebd15b35b9.png) I try it in another computer with windows terminal config with powershell,and meet the same issue. ### Expected Behavior right whitespace rendering,seems transparent error too. ### Actual Behavior ![image](https://user-images.githubusercontent.com/32102128/154673916-e30a84c4-a5ef-4595-adb9-427707628cc2.png) ![image](https://user-images.githubusercontent.com/32102128/154674073-f4b3fa58-fab1-4e4b-9f08-61ebd15b35b9.png)
claunia commented 2026-01-31 05:23:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 18, 2022):

Alas, this it probably gonna fall under the category of "play silly games, win silly prizes". Terminals are fundamentally hosting a grid of characters, so they can only reliably work with monospaced fonts. "Ink Face" isn't a monospace font, so its characters aren't entirely filling their grid spaces. So when you see something like:
image
what's happening there is roughly:

  • the terminal renders the '77 ' with gray on a black background
  • the terminal switches to blue on black to render the '/'. It renders that where it believes the character should be in the grid, which is a good distance to the right of the end of the spaces from the previous run. Because nothing was rendered there, the acrylic behind the text is now visible instead.
  • same thing happens again for each of the runs in the row.

I'd stick with monospace fonts for the best experience.

@zadjii-msft commented on GitHub (Feb 18, 2022): Alas, this it probably gonna fall under the category of "play silly games, win silly prizes". Terminals are fundamentally hosting a _grid_ of characters, so they can only reliably work with monospaced fonts. "Ink Face" isn't a monospace font, so its characters aren't entirely filling their grid spaces. So when you see something like: ![image](https://user-images.githubusercontent.com/18356694/154677773-0047c4ee-45ce-4ff4-ae7a-aee38350044f.png) what's happening there is roughly: * the terminal renders the '77 ' with gray on a black background * the terminal switches to blue on black to render the '/'. It renders that where it believes the character should be in the grid, which is a good distance to the right of the end of the spaces from the previous run. Because nothing was rendered there, the acrylic behind the text is now visible instead. * same thing happens again for each of the runs in the row. I'd stick with monospace fonts for the best experience.
claunia commented 2026-01-31 05:23:48 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Mar 1, 2022):

FYI, if you enable the experimental text rendering engine in the advanced profile settings, that does kind of support fonts like this. You don't really get the hand-written effect of the font, because each letter is now aligned on the grid, but it is at least usable. And if we ever get a letter-spacing option as part of #1790, you could probably tweak things to look a bit better.

@j4james commented on GitHub (Mar 1, 2022): FYI, if you enable the _experimental text rendering engine_ in the advanced profile settings, that does kind of support fonts like this. You don't really get the hand-written effect of the font, because each letter is now aligned on the grid, but it is at least usable. And if we ever get a letter-spacing option as part of #1790, you could probably tweak things to look a bit better.
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 Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#16813
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?