https://bugs.winehq.org/show_bug.cgi?id=37215
Bug ID: 37215 Summary: incorrect starting size of font antialias Product: Wine Version: 1.7.25 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs@winehq.org Reporter: henry.hu.sh@gmail.com
Created attachment 49474 --> https://bugs.winehq.org/attachment.cgi?id=49474 DPI=144, size=6
It seems like that wine incorrectly decides the starting size of which to use antialias. I'm testing with the SimSun font. My desktop DPI is 144. I'm using Xfce and force DPI to be 144 in the appearance settings.
xrdb -query | grep Xft:
Xft.antialias: 1 Xft.hintstyle: hintfull Xft.rgba: rgb Xft.dpi: 144
If I use mousepad (native app) and set the font to be SimSun: Up to size 8, it uses the font's embedded bitmap. With size >= 9, it uses the normal glyphs, awnd enables antialias. The results are always nice.
Next I tested wine's notepad. First, I tested with DPI=144 in winecfg. Up to size 8, it uses the font's embedded bitmap which is good. For 9 <= size <= 12, it uses the font's glyphs, but the antialias is off (!!!), and the text looks ugly. For size >= 14, antialias is on, and the results are good.
Next, I tested with DPI=96 in winecfg. For size=6, it uses anti-aliased glyphs, which is ok. For size=7 & 8, it uses glyphs without anti-alias. The results are ugly. But anyway the text is too small at this size, so that's not important. For size=9, it uses embedded bitmap which looks good. For size=10 & 11, it uses glyphs without anti-alias. The results are ugly. For size=12, it uses embedded bitmap which looks good. For 14 <= size <= 18, it uses glyphs without anti-alias. The results are ugly. For size >= 20, it uses anti-aliased glyphs which looks good.
If I load simsun with fontforge, it says that simsun has bitmap fonts at 12, 14 and 16.
So, is there some problem in calculating when to start using anti-alias?