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

The font selection description is misleading and should be updated #4507

New Issue
Closed
opened 2026-01-30 23:49:22 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 23:49:22 +00:00
Owner
Copy Link

Originally created by @alabuzhev on GitHub (Oct 16, 2019).

image

TrueType fonts are recommended for high DPI displays as raster fonts may not display clearly.

I agree that TrueType fonts are recommended. However, the motivation is irrelevant and misleading.

It is not a big deal if you have a high DPI display and choose a raster font. The worst thing that could happen is that it will be pixelated (and note - some weirdos even love that).

If someone is not satisfied with the console font, it is pretty clear what to do - just change it.

There's a much bigger problem with raster fonts: they can't display anything outside of the current OEM code page. If your OEM code page is, say, 850 - Multilingual Latin I, with raster fonts you will see ????? instead of Cyrillic абвгд or ?p??s instead of Greek οπρςσ.

It is not clear at all, especially for laypeople, that the problem is in raster fonts. I've seen multiple occasions when people think that such strings are damaged due to bugs in software or that their actual data (file names or content) is corrupted.

This sentence should be rephrased and clearly stress that raster fonts, first of all, cannot display Unicode characters in general, so beware. And only after that, if there's still some space left, it can be mentioned that hey, they can also look ugly sometimes.

Originally created by @alabuzhev on GitHub (Oct 16, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> ![image](https://user-images.githubusercontent.com/11453922/66928265-0897c400-f029-11e9-8735-e90b23712c6d.png) > TrueType fonts are recommended for high DPI displays as raster fonts may not display clearly. I agree that TrueType fonts are recommended. However, the motivation is irrelevant and misleading. It is not a big deal if you have a high DPI display and choose a raster font. The worst thing that could happen is that it will be pixelated (and note - some weirdos even love that). If someone is not satisfied with the console font, **it is pretty clear what to do** - just change it. There's a much bigger problem with raster fonts: they can't display **anything** outside of the current OEM code page. If your OEM code page is, say, 850 - Multilingual Latin I, with raster fonts you will see `?????` instead of Cyrillic `абвгд` or `?p??s` instead of Greek `οπρςσ`. **It is not clear at all, especially for laypeople, that the problem is in raster fonts.** I've seen multiple occasions when people think that such strings are damaged due to bugs in software or that their actual data (file names or content) is corrupted. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> This sentence should be rephrased and clearly stress that raster fonts, first of all, cannot display Unicode characters in general, so beware. And only after that, if there's still some space left, it can be mentioned that hey, they can also look ugly sometimes. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureProduct-ConhostResolution-By-DesignNeeds-Tag-Fix labels 2026-01-30 23:49:22 +00:00
claunia commented 2026-01-30 23:49:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 16, 2019):

If I had my way, it would say:

Please stop using
Raster Fonts, it’s
2019.

(And then, in 2020, we would get rid of them forever. Some console APIs necessarily behave differently when the user’s selected Raster Fonts as their font.)

@DHowett-MSFT commented on GitHub (Oct 16, 2019): If I had my way, it would say: ``` Please stop using Raster Fonts, it’s 2019. ``` (And then, in 2020, we would get rid of them forever. Some console APIs necessarily behave differently when the user’s selected Raster Fonts as their font.)
claunia commented 2026-01-30 23:49:23 +00:00
Author
Owner
Copy Link

@egmontkob commented on GitHub (Oct 16, 2019):

Pango (the font rendering engine used by Linux apps using the GTK widget, including the entire GNOME desktop) just recently dropped bitmap font support. Let's see where it goes, how it will be received by users...

@egmontkob commented on GitHub (Oct 16, 2019): Pango (the font rendering engine used by Linux apps using the GTK widget, including the entire GNOME desktop) just recently [dropped bitmap font support](https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/). Let's see where it goes, how it will be received by users...
claunia commented 2026-01-30 23:49:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 21, 2019):

@alabuzhev Thanks for reporting this. We're not really investing in this dialog or the legacy setting experience right now, and the burden we take on for changing it (which includes getting translation changes for every language Windows supports) is too great for us to countenance. I appreciate that it's wrong, but perhaps it'll just have to be wrong by design. That doesn't mean the design is great 😄.

@DHowett-MSFT commented on GitHub (Oct 21, 2019): @alabuzhev Thanks for reporting this. We're not really investing in this dialog or the legacy setting experience right now, and the burden we take on for changing it (which includes getting translation changes for every language Windows supports) is too great for us to countenance. I appreciate that it's wrong, but perhaps it'll just have to be wrong by design. That doesn't mean the design is great :smile:.
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-Feature Needs-Tag-Fix Product-Conhost Resolution-By-Design
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#4507
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?