[Bug 41639] Wine with freetype 2.7 causes font rendering issues

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=41639

John Found <johnfound at asm32.info> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johnfound at asm32.info

--- Comment #6 from John Found <johnfound at asm32.info> ---
The issue is definitely related to the changes of FreeType algorithms and/or
API after v2.6 or maybe v2.7; The problem exists in Linux as well with FreeType
v2.8; 

On my system it manifest itself by missing sub-pixel antialiasing. Only
grayscale works and only on some fonts, possibly larger than some threshold -
something like 12px.

I will prefix my finding by +/-:

- The suggested workaround does not work at all. 

+ But downgrading to FreeType v2.7 do work; The sub-pixel smoothing works
again. 

- But WINE stopped respect its own settings in the registry for the font
smoothing: HKCU/Control panel/Desktop/FontSmoothing (and FontSmoothingGamma,
FontSmoothingOrientation, FontSmoothingType) does not affect the font rendering
at all. 

+ But the system settings does affect WINE rendering behavior. I can switch
smoothing on/off by changing the system settings from  XFCE appearance applet.

- WINE seems to not respect the fontconfig settings in /etc/fonts and
~/.config/fontconfig/ - I have a font that need not to be smoothed and have the
following file in "~/.config/fontconfig/99-FixedSys.conf":

...
  <match target="font">
    <test name="family" compare="eq" ignore-blanks="true">
      <string>Fixedsys Excelsior 3.01</string>
    </test>
    <edit name="antialias" mode="assign">
      <bool>false</bool>
    </edit>
    <edit name="hintstyle" mode="assign">
      <const>hintnone</const>
    </edit>
    <edit name="rgba" mode="assign">
      <const>none</const>
    </edit>
  </match>
...

So, WINE applications does not respect this .conf file, but the native Linux
applications does.

In general, the native Linux application and the desktop environment are not
affected by these changes in FreeType or was adapted better to the changes.

That is all so far. This issue looks and feels like a complete mess. :) I have
a feeling that the problem is in the way WINE interacts with
FreeType/fontconfig and is not a specific bug/regression but some kind of not
proper interfacing to FreeType after the API changes.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.