The font selection description is misleading and should be updated #3226
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.
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.
The text was updated successfully, but these errors were encountered: