https://bugs.winehq.org/show_bug.cgi?id=41639
--- Comment #39 from Byeongsik Jeon bsjeon@hanmail.net --- (In reply to Nikolay Sivov from comment #38)
(In reply to Byeongsik Jeon from comment #34)
OK.
This is the freetype build option problem. You need to build a Freetype library with #define FT_CONFIG_OPTION_SUBPIXEL_RENDERING
Or, the latest Freetype library will solve the problem.
Why would it matter if using same binary with different engine mode works?
Maybe, this.
(In reply to Hugo from comment #35)
Sadly, I cannot change the Freetype version or recompile it because its bundled with XQuartz in MacOS. I could compile the entire xorg-server with the latest freetype but in Mac everyone just downloads the latest XQuartz, so a fix would be really appreciated!
Meanwhile, I am trying to force interpreter-version:35 inside freetype.c,
And why subpixel mode would matter for b/w bitmaps?
My patch is for analyzing this problem. It's literally a temporary patch.
I wanted to make sure that the Freetype of XQuartz 2.7.11 was something special modification. It doesn't seem like it. Now, this problem can be simulated exactly on my Linux box.
I think the XQuartz update is the right solution. However I think it is registered as a bug because it is not possible for some reason.