Open GoogleCodeExporter opened 9 years ago
Not sure this is a bug in Modern. It could have something to do with
transparency in the skin or in settings.
Original comment by sami%mir...@gtempaccount.com
on 6 Nov 2010 at 9:50
That occurred to me too but I haven't found any setting that fixes this. Can
you suggest something in particular I might check or change?
Original comment by dr.dave....@gmail.com
on 6 Nov 2010 at 11:10
Not really because I wasn't able to reproduce this properly. I just remembered
this when I saw something similar with plain white Arial text on a transparent
Modern skin. The color went away after picking a "better" font or some other
color or any effect...
Original comment by sami%mir...@gtempaccount.com
on 6 Nov 2010 at 11:55
Would it be useful for me to send you the font that's producing this result?
Original comment by dr.dave....@gmail.com
on 7 Nov 2010 at 5:39
I don't think it's specific to any one font, but please do tell what it is.
Also a the skin you use, and text style and effect would be good to know.
Original comment by sami%mir...@gtempaccount.com
on 7 Nov 2010 at 11:21
Actually, I think it's specific to pixelated fonts. The one I'm using is
uni_o5_54. The skin is Case though varying the skin or the effect doesn't make
a difference. I did find though, that the effect is strongly present only for
regular and bold, not for italic or bold italic. In fact, I just discovered
that there is an issue with the color spectrum used for smoothing: For the font
I'm using, the spectrum includes a wide range of hues for italic and bold
italic but is entirely in the green and yellow region for regular and bold. For
most fonts (non-pixelated), the spectrum is wide-ranging regardless of style.
The fact is though, there should be no smoothing for a pixelated font. In other
applications like rainmeter, it's possible to turn off smoothing
(anti-aliasing). When you do that, the font is rendered more cleanly without
any color artifacts.
Original comment by dr.dave....@gmail.com
on 7 Nov 2010 at 2:47
Original issue reported on code.google.com by
dr.dave....@gmail.com
on 22 Oct 2010 at 10:45Attachments: