In my Visual Studio 2012, monospaced fonts does not render correctly, specifically they don't render "monospaced" correctly, ie. the characters are not uniform in width.
Here's an example, this:
// 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
// -|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
renders as this with Consolas 10-point, 100% zoom:
and as this with 101% zoom:
There are other minor problems at 101% zoom, so neither are good. Is there a way for me to configure Visual Studio to render monospaced fonts correctly?
I have tried the following fonts:
Consolas
Courier
Courier New
Terminal
Apparently no monospaced font that I've tried renders correctly in Visual Studio.
If I use the exact same font and font-size in Notepad2, like Consolas:
compare notepad2 and Visual Studio with Consolas
Is there anything I can do?
Details:
Visual Studio 2012 font dialog:
Basically, for a font to be considered monospace, every glyph has to be the same width, right down to the exact same number of units. This includes even glyphs that should normally be zero width, or a certain width (such as em spaces, em dashes, etc).
Monospaced typefaces do reduce legibility, albeit by a margin. In Universal Principles of Design, the entry on legibility states: Proportionally spaced typefaces are preferred over monospaced.
A font can be monospaced even if metadata tells you otherwise. Just look at the with of glyphs. Compare the width of 'i' and 'm' and/or other glyphs.
Compared to proportional fonts, monospaced fonts are harder to read. And because they take up more horizontal space, you'll always get fewer words per page with a monospaced font. In standard body text, there are no good reasons to use monospaced fonts. So don't.
My guess:
10pt = 13.333px and it's problem with correct render for some fonts.
Set 9pt. It's 12px by default and all is ok.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With