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

I do not like the new text rendering engine #22462

New Issue
Open
opened 2026-01-31 08:14:07 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:14:07 +00:00
Owner
Copy Link

Originally created by @henrijuk on GitHub (Oct 28, 2024).

Windows Terminal version

1.21.2911.0

Windows build number

10.0.22631.4317

Other Software

No response

Steps to reproduce

Use the (default) Cascadia Mono font (size 12) and compare the appearance of text in the terminal between the old renderer (possible to still use in versions prior to 1.21) and the new renderer.

I mostly use 2560x1440 display resolution but this happens on any display resolution with Windows' rendering scale set to default 100%.

(Option to use the old renderer was removed in 1.21.2361.0 as per the release notes.)

(I was still using the option to use the old renderer and now the option to use it is gone. I'm assuming the reason is that 1.21 was recently pushed to all users, including me. I don't know exactly on what version I was before; I was hit by the changed rendering on Oct 25th and then noticed I had 1.21 and the old option was gone.)

Expected Behavior

Expecting to see the same well-proportioned font as before (and not this vertically elongated abnormity).

Actual Behavior

The new engine renders the font differently. Most noticeably tall characters (e.g. capital letters, numbers, lowercase L, etc.) are vertically elongated (pixel or two taller than before), distorting the font proportions. The font also looks generally thicker.

New renderer (1.21, distorted font):
Image

Old renderer (preferred):
Image

The most noticeable difference in the above attached screenshots are the numbers, especially the zeros, and the capital A letter.
Other changes are a lot easier to notice when comparing the images in-place one after the other (center them on full screen with 100% image scale and hit arrows or some other key to switch between them).

For some, this may seem like a minuscule problem but for me this is a big deal. I look at the terminal a lot and a change like this is distracting. The new taller and thicker rendering is more "restless" to me.

Originally created by @henrijuk on GitHub (Oct 28, 2024). ### Windows Terminal version 1.21.2911.0 ### Windows build number 10.0.22631.4317 ### Other Software _No response_ ### Steps to reproduce Use the (default) Cascadia Mono font (size 12) and compare the appearance of text in the terminal between the old renderer (possible to still use in versions prior to 1.21) and the new renderer. I mostly use 2560x1440 display resolution but this happens on any display resolution with Windows' rendering scale set to default 100%. (Option to use the old renderer was removed in 1.21.2361.0 as per the release notes.) (I was still using the option to use the old renderer and now the option to use it is gone. I'm assuming the reason is that 1.21 was recently pushed to all users, including me. I don't know exactly on what version I was before; I was hit by the changed rendering on Oct 25th and then noticed I had 1.21 and the old option was gone.) ### Expected Behavior Expecting to see the same well-proportioned font as before (and not this vertically elongated abnormity). ### Actual Behavior The new engine renders the font differently. Most noticeably tall characters (e.g. capital letters, numbers, lowercase L, etc.) are vertically elongated (pixel or two taller than before), distorting the font proportions. The font also looks generally thicker. New renderer (1.21, distorted font): ![Image](https://github.com/user-attachments/assets/704871f1-4bf6-423c-b676-85825b473d4b) Old renderer (preferred): ![Image](https://github.com/user-attachments/assets/74cb301b-6c59-47fc-9de6-39c2d35e5b5f) The most noticeable difference in the above attached screenshots are the numbers, especially the zeros, and the capital A letter. Other changes are a lot easier to notice when comparing the images in-place one after the other (center them on full screen with 100% image scale and hit arrows or some other key to switch between them). For some, this may seem like a minuscule problem but for me this is a big deal. I look at the terminal a lot and a change like this is distracting. The new taller and thicker rendering is more "restless" to me.
claunia added the Issue-QuestionNeeds-TriageResolution-AnsweredArea-Fonts labels 2026-01-31 08:14:07 +00:00
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-Fonts Issue-Question 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#22462
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?