http://bugs.winehq.org/show_bug.cgi?id=10342
BlackStar BurnSpamAddress@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |BurnSpamAddress@gmail.com
--- Comment #21 from BlackStar BurnSpamAddress@gmail.com 2008-11-25 06:05:44 --- Maybe this will help clean up the confusion on ClearType vs FreeType:
ClearType is a specific set of proprietary font-rendering algorithms that perform antialiasing, hinting and subpixel rendering. FreeType implements a different set of font-rendering algorithms that also perform antialiasing, hinting and subpixel rendering.
The goal of these algorithms is to improve the appearance of text on the screen. Since the algorithms are different, FreeType output does not exactly match ClearType (some, including me, argue that FreeType provides superior rendering to ClearType).
On modern Linux distributions, the user can select exactly which algorithms FreeType will use. None of these algorithms match ClearType exactly and some of these may be patent-encumbered.
The problem here is that Wine *overrides* the user settings when rendering text and forces either monochrome or grayscale rendering. The point of this bug is to fix Wine so that it renders according to user settings. I have tried to create a patch for this, but failed (it seems that there is code which expects glyphs to be 1- or 8bit pixmaps and cannot cope with 24bpp).
Please note that this fix will not encumber Wine with potentially patented code. This code is contained inside FreeType and has to be explicitly enabled by the user (or the Linux distribution). It will merely allow Wine to follow the rest of the user desktop.