Experimental text engine renders terminal window larger compared to default setting #18262

Closed
opened 2026-01-31 06:08:31 +00:00 by claunia · 3 comments
Owner

Originally created by @elsaco on GitHub (Aug 22, 2022).

Windows Terminal version

1.15.2002.0

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

Toggle "Enable experimental text rendering engine"

Expected Behavior

Terminal size to be consistent

Actual Behavior

Top is with Atlas engine on, bottom with default setting. No other changes were altered:

wt_experimental_compare

Originally created by @elsaco on GitHub (Aug 22, 2022). ### Windows Terminal version 1.15.2002.0 ### Windows build number 10.0.19044.0 ### Other Software _No response_ ### Steps to reproduce Toggle "Enable experimental text rendering engine" ### Expected Behavior Terminal size to be consistent ### Actual Behavior Top is with Atlas engine on, bottom with default setting. No other changes were altered: ![wt_experimental_compare](https://user-images.githubusercontent.com/3933920/185975569-03a39b30-bd33-44cd-b64a-e7768640703c.png)
Author
Owner

@zadjii-msft commented on GitHub (Aug 23, 2022):

@lhecker lmao someone noticed

@zadjii-msft commented on GitHub (Aug 23, 2022): @lhecker lmao someone noticed
Author
Owner

@lhecker commented on GitHub (Aug 23, 2022):

The previous renderer used round() to determine the width of a single cell in the terminal and then shrank/grew the font size to match that cell width. So you said you want 12pt, but you actually got 11.9945pt or something, which lead to the slightly blurry text in Windows Terminal (blurriness depends on the font family, font size and most importantly on the glyph).

My goal was to stop that font size adjustment and improve text clarity. To ensure glyphs aren't cut off with the possibly larger font size, I used ceil() to determine the cell width instead of round(). But I'm not saying that I'm 100% sure that ceil() is the correct choice there - I was just going by my intuition and I'm open to any and all change suggestions.

That said I don't consider this issue to be a bug, since I did do it intentionally.

@lhecker commented on GitHub (Aug 23, 2022): The previous renderer used `round()` to determine the width of a single cell in the terminal and then shrank/grew the font size to match that cell width. So you said you want 12pt, but you actually got 11.9945pt or something, which lead to the slightly blurry text in Windows Terminal (blurriness depends on the font family, font size and most importantly on the glyph). My goal was to stop that font size adjustment and improve text clarity. To ensure glyphs aren't cut off with the possibly larger font size, I used `ceil()` to determine the cell width instead of `round()`. But I'm not saying that I'm 100% sure that `ceil()` is the correct choice there - I was just going by my intuition and I'm open to any and all change suggestions. That said I don't consider this issue to be a bug, since I did do it intentionally.
Author
Owner

@ghost commented on GitHub (Sep 13, 2022):

:tada:This issue was addressed in #13833, which has now been successfully released as Windows Terminal Preview v1.16.252.🎉

Handy links:

@ghost commented on GitHub (Sep 13, 2022): :tada:This issue was addressed in #13833, which has now been successfully released as `Windows Terminal Preview v1.16.252`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.16.252) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18262