do you see that? the red line is no anti-aliasing. the blue line is anti-aliasing.
why?
Font and antialising
Author
do you see that? the red line is no anti-aliasing. the blue line is anti-aliasing.
why?
Author
it seem windows no anti aliasing small font and anti aliasing big font. so how does windows decide that?
Generally, the font designer decides that. It has to do with the fact that, as a font gets smaller, anti-aliasing causes it to appear dim and less crisp. So, at a certain minimum size (depending on the font), anti-aliasing is disabled to keep the text readable.
In your picture the 12, 18, and 24 point samples are clearly coming from a completely different font than the higher sizes. Notice how the smaller glyphs are all "slanty" while in the bigger sizes they're straight up and down.
My guess is that you have two different versions of a font called "Symbol" on your machine and that one of them (the one used in the smaller text) is a bitmap font and thus can't be anti-aliased.
The effect doesn't repro on my machine, which only has one symbol font, and that is a truetype font. Everything is anti-aliased.
If this is for your own app you can pass OUT_TT_PRECIS for the fdwOutputPrecision parameter of CreateFont to force use of truetype fonts if they're available.
My guess is that you have two different versions of a font called "Symbol" on your machine and that one of them (the one used in the smaller text) is a bitmap font and thus can't be anti-aliased.
The effect doesn't repro on my machine, which only has one symbol font, and that is a truetype font. Everything is anti-aliased.
If this is for your own app you can pass OUT_TT_PRECIS for the fdwOutputPrecision parameter of CreateFont to force use of truetype fonts if they're available.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
