Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
alabuzhev opened this issue Oct 16, 2019 · 3 comments
Closed

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

alabuzhev opened this issue Oct 16, 2019 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Product-Conhost For issues in the Console codebase Resolution-By-Design It's supposed to be this way. Sometimes for compatibility reasons.

Comments

@alabuzhev
Copy link
Contributor

alabuzhev commented 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.

@alabuzhev alabuzhev added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 16, 2019
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 16, 2019
@DHowett-MSFT
Copy link
Contributor

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.)

@egmontkob
Copy link

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...

@DHowett-MSFT DHowett-MSFT added Resolution-By-Design It's supposed to be this way. Sometimes for compatibility reasons. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Oct 21, 2019
@DHowett-MSFT
Copy link
Contributor

@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 😄.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Product-Conhost For issues in the Console codebase Resolution-By-Design It's supposed to be this way. Sometimes for compatibility reasons.
Projects
None yet
Development

No branches or pull requests

4 participants