[Bug 3318] [IcedTea7] Freetype 2.7's TT_CONFIG_OPTION_SUBPIXEL_HINTING=2 and OpenJDK enabled infinality causes missing text in rendering

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3318

--- Comment #3 from hg commits <mercurial at icedtea.classpath.org> ---
details:
http://icedtea.classpath.org//hg/icedtea7-forest/jdk?cmd=changeset;node=52de2c27b131
author: andrew
date: Tue Jan 24 23:02:54 2017 +0000

    PR3318: Fix compatibility with vanilla Fontconfig
    Contributed-by: Matthias Dahl <ml_openjdk-lists at binary-island.eu>

    With vanilla Fontconfig, most text is not rendered.

    The "Infinality"-patched Fontconfig with its own configuration,
    supplies an additional config file that sets the antialias key
    (FC_ANTIALIAS) which is not part of the vanilla Fontconfig and also
    has no default in its source code.

    In the case that FC_ANTIALIAS is not being provided for a given font
    because the font does not contain the appropriate information (which
    is quite common) or a specific config file is missing,
    FcPatternGetBool for the key will return an error and no valid
    result. Thus, ftRenderMode stays uninitialized due to the way its
    initialized in the conditional constructs, eventually causing the text
    rendering anomaly.

    Furthermore, the logic is flawed as well. The specific subpixel
    rendering modes are only properly set if FC_ANTIALIAS is set and true,
    no matter what was requested by the caller (aaType).

    This patch makes the following changes to address those problems:

    1. ftRenderMode is always properly initialized.

    2. FC_ANTIALIAS is only evaluated if antialiasing was requested and only
       used to turn off antialiasing if that is suggested by Fontconfig.

    3. Subpixel rendering modes are properly set according to Fontconfig
       results and only if subpixel rendering was actually requested.

    In order to properly adjust for the "forced off" antialiasing, it is
    necessary to change the signature of readFontconfig and give it full
    access to FTScalerContext, so it can properly set the new aaType.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20170206/63a10eae/attachment.html>