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

Console property sheet allows bitmap fonts despite the v2 console _not_ supporting them #6922

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

Originally created by @zadjii-msft on GitHub (Mar 17, 2020).

The "Hellfont Cyr" terminal font is not rendered in v2 console. Instead of its 9x16 typeface, some random 12x16 is chosen.

(Left is ForceV2=0, right is ForceV2=1. Same font settings.)

image

Originally posted by @AnrDaemon in https://github.com/microsoft/terminal/issues/295#issuecomment-600209738

Originally created by @zadjii-msft on GitHub (Mar 17, 2020). The ["Hellfont Cyr"](https://plugring.farmanager.com/plugin.php?pid=164&l=en) terminal font is not rendered in v2 console. Instead of its 9x16 typeface, some random 12x16 is chosen. (Left is ForceV2=0, right is ForceV2=1. Same font settings.) ![image](https://user-images.githubusercontent.com/6532485/76876645-44a6ad80-6883-11ea-8ab2-adb645f97c7b.png) _Originally posted by @AnrDaemon in https://github.com/microsoft/terminal/issues/295#issuecomment-600209738_
claunia added the Product-ConhostArea-SettingsIssue-BugPriority-3 labels 2026-01-31 00:50:33 +00:00
claunia commented 2026-01-31 00:50:34 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 17, 2020):

Yanking triage. Thanks!

@DHowett-MSFT commented on GitHub (Mar 17, 2020): Yanking triage. Thanks!
claunia commented 2026-01-31 00:50:34 +00:00
Author
Owner
Copy Link

@schffp commented on GitHub (May 6, 2020):

Please consider supporting bitmap fonts instead of just removing the option from the menu. Would be a shame if we would not be able to use them..

@schffp commented on GitHub (May 6, 2020): Please consider supporting bitmap fonts instead of just removing the option from the menu. Would be a shame if we would not be able to use them..
claunia commented 2026-01-31 00:50:34 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 6, 2020):

IIRC bitmap fonts in the vintage console were an enormous pain to support. They've got more legacy edge cases than anything else. IIRC one of them actually changed the way one of our APIs behaved as well, so callers would need to know which font the user had selected to know what to expect the result to be. It was mad.

We're not likely to add them back lightly, we'd need a pretty substantial business justification for that.

@zadjii-msft commented on GitHub (May 6, 2020): IIRC bitmap fonts in the vintage console were an _enormous_ pain to support. They've got more legacy edge cases than anything else. IIRC one of them actually changed the way one of our APIs behaved as well, so callers would need to know which font the user had selected to know what to expect the result to be. It was mad. We're not likely to add them back lightly, we'd need a pretty substantial business justification for that.
claunia commented 2026-01-31 00:50:35 +00:00
Author
Owner
Copy Link

@schffp commented on GitHub (May 6, 2020):

That's unfortunate, but I understand your reasoning.

@schffp commented on GitHub (May 6, 2020): That's unfortunate, but I understand your reasoning.
claunia commented 2026-01-31 00:50:35 +00:00
Author
Owner
Copy Link

@AnrDaemon commented on GitHub (May 6, 2020):

I don't see how a file that's not even executable (64-bit Windows can't execute NE binary) could change the program or OS behavior.

@AnrDaemon commented on GitHub (May 6, 2020): I don't see how a file that's not even executable (64-bit Windows can't execute NE binary) could change the program or OS behavior.
claunia commented 2026-01-31 00:50:35 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 6, 2020):

Er, no, it's more like.. The console host had support for bitmap fonts, and applications took a dependency on the API responses the console host returned when bitmap fonts were enabled. And this applies to bitmap fonts of all varieties, not just the "Raster Font" option.

The problem is twofold. Bitmap fonts don't plug well into our renderer, and, we would need to confront the legacy applications that detect whether bitmap fonts are in use and make sure they continue to behave correctly.

@DHowett-MSFT commented on GitHub (May 6, 2020): Er, no, it's more like.. The console host had support for bitmap fonts, and _applications took a dependency on the API responses the console host returned_ when bitmap fonts were enabled. And this applies to bitmap fonts of all varieties, not just the "Raster Font" option. The problem is twofold. Bitmap fonts don't plug well into our renderer, _and_, we would need to confront the legacy applications that detect whether bitmap fonts are in use and make sure they continue to behave correctly.
claunia commented 2026-01-31 00:50:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 6, 2020):

@AnrDaemon So, IIRC, part of it had to do with how the width of certain characters was calculated. For TTF fonts, the API would return one value for some glyphs, but for bitmap fonts we'd calculate an entirely different value. This was all sorted out like 3 years ago, so I'm pretty fuzzy on the details. I'm vaguely remembering something like the API would behave differently if you wrote text with a TTF font selected, then read it with a bitmap font selected, and vice-versa. It was madness. @miniksa wrote some bonkers 256-part test that had 17(yep, 17, an odd number) of actual possibilities in it based on the input variables.

@zadjii-msft commented on GitHub (May 6, 2020): @AnrDaemon So, IIRC, part of it had to do with how the width of certain characters was calculated. For TTF fonts, the API would return one value for some glyphs, but for bitmap fonts we'd calculate an entirely different value. This was all sorted out like 3 years ago, so I'm pretty fuzzy on the details. I'm vaguely remembering something like the API would behave differently if you _wrote_ text with a TTF font selected, then _read_ it with a bitmap font selected, and vice-versa. It was madness. @miniksa wrote some bonkers 256-part test that had 17(yep, 17, an _odd_ number) of actual possibilities in it based on the input variables.
claunia commented 2026-01-31 00:50:35 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 6, 2020):

Nope, it wasn't even the widths or anything. The text coming in through WriteConsole* and returning through ReadConsole* is selectively garbled depending on many things, including whether or not the font is raster or TrueType. The garbled values are useless and cannot be resynthesized into the correct original text, but somehow absurdly some applications depended on the behavior in the decades between the bug being introduced and when I figured it out and fixed it and had to revert it.

@miniksa commented on GitHub (May 6, 2020): Nope, it wasn't even the widths or anything. The text coming in through `WriteConsole*` and returning through `ReadConsole*` is selectively garbled depending on many things, including whether or not the font is raster or TrueType. The garbled values are useless and cannot be resynthesized into the correct original text, but somehow absurdly some applications depended on the behavior in the decades between the bug being introduced and when I figured it out and fixed it and had to revert it.
claunia commented 2026-01-31 00:50:35 +00:00
Author
Owner
Copy Link

@AnrDaemon commented on GitHub (May 6, 2020):

How about we stop worrying about badly written applications and get normal TTY terminal already?
Font selection is tangential to it.

@AnrDaemon commented on GitHub (May 6, 2020): How about we stop worrying about badly written applications and get normal TTY terminal already? Font selection is tangential to it.
claunia commented 2026-01-31 00:50:36 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 7, 2020):

If we could easily knife application compatibility in the back, we would probably not start with "adding support for bitmap fonts" and instead start with "deleting the Win32 console APIs and going back to the basics," but... to each their own 😄

@DHowett-MSFT commented on GitHub (May 7, 2020): If we could easily knife application compatibility in the back, we would probably not start with "adding support for bitmap fonts" and instead start with "deleting the Win32 console APIs and going back to the basics," but... to each their own :smile:
claunia commented 2026-01-31 00:50:36 +00:00
Author
Owner
Copy Link

@schffp commented on GitHub (May 7, 2020):

Maybe you could allow bitmap fonts for WSL-Terminal only?^^ That would dodge the backwards compatibility issue

Again, I totally understand your reasoning, but for people who do want to use bitmap fonts this could be a big enough downside, to switch to something like mintty which does support them

@schffp commented on GitHub (May 7, 2020): Maybe you could allow bitmap fonts for WSL-Terminal only?^^ That would dodge the backwards compatibility issue Again, I totally understand your reasoning, but for people who do want to use bitmap fonts this could be a big enough downside, to switch to something like mintty which does support them
claunia commented 2026-01-31 00:50:36 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 8, 2020):

The Terminal leverages DirectWrite for most of its font loading/querying capability. I don't believe DirectWrite supports bitmap fonts. So it would require writing a bitmap font loader/parser and then holding the bitmaps and laying them out ourselves on the Direct2D surface. It's totally possible, but I don't believe that the quantity of affected customers in this scenario is high enough for us to allocate resources to it yet versus some of our other feature requests. We leave the issues open on the tracker to recognize that customers do exist for the scenario and continue to track if the affected population rises high enough to recalibrate our rankings. If a community member is really passionate about this and steps up to contribute something before we get around to working on it, we'd dutifully review it like any other submission.

@miniksa commented on GitHub (May 8, 2020): The Terminal leverages DirectWrite for most of its font loading/querying capability. I don't believe DirectWrite supports bitmap fonts. So it would require writing a bitmap font loader/parser and then holding the bitmaps and laying them out ourselves on the Direct2D surface. It's totally possible, but I don't believe that the quantity of affected customers in this scenario is high enough for us to allocate resources to it yet versus some of our other feature requests. We leave the issues open on the tracker to recognize that customers do exist for the scenario and continue to track if the affected population rises high enough to recalibrate our rankings. If a community member is really passionate about this and steps up to contribute something before we get around to working on it, we'd dutifully review it like any other submission.
claunia commented 2026-01-31 00:50:36 +00:00
Author
Owner
Copy Link

@AnrDaemon commented on GitHub (May 8, 2020):

Implement Console IO in PTY? ? :D

@AnrDaemon commented on GitHub (May 8, 2020): Implement Console IO in PTY? ? :D
claunia commented 2026-01-31 00:50:37 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 8, 2020):

Implement Console IO in PTY? ? :D

Bud, you just keep asking for more and more expensive fixes. I feel your excitement, but trust us. We'll do whatever we can to make the maximum amount of people happy as quickly as we can for as few resources as possible.

@miniksa commented on GitHub (May 8, 2020): > Implement Console IO in PTY? ? :D Bud, you just keep asking for more and more expensive fixes. I feel your excitement, but trust us. We'll do whatever we can to make the maximum amount of people happy as quickly as we can for as few resources as possible.
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-Settings Issue-Bug Priority-3 Product-Conhost
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#6922
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?