[Bug 746920] New: autihinting has no effect on DejavuSansMono with freetype 2.4.6 (patch found)

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: autihinting has no effect on DejavuSansMono with freetype 2.4.6 (patch found)

https://bugzilla.redhat.com/show_bug.cgi?id=746920

           Summary: autihinting has no effect on DejavuSansMono with
                    freetype 2.4.6 (patch found)
           Product: Fedora
           Version: rawhide
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: unspecified
          Priority: unspecified
         Component: freetype
        AssignedTo: mkasik at redhat.com
        ReportedBy: alphsteiner at gmail.com
         QAContact: extras-qa at fedoraproject.org
                CC: behdad at fedoraproject.org, kevin at tigcc.ticalc.org,
                    fonts-bugs at lists.fedoraproject.org, mkasik at redhat.com
    Classification: Fedora
      Story Points: ---
              Type: ---


Hello, here is a summary of the problem:
- with freetype 2.4.2, DejavuSansMono is rendered normally;
- with freetype 2.4.6, DejavuSansMono and the other fonts are rendered badly
(badly means here "not in the same way as with 2.4.2"): after some googling, I
have found it is due to the fact that the bytecode interpreter is now enabled,
and the workaround is to use autohinting:
"ln -s /etc/fonts/conf.avail/10-autohint.conf /etc/fonts/conf.d/"

This works great, but not for DejavuSansMono.
After trying freetype 2.4.5 without having any problem, I found it: it is the
patch 
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0962ac34e66052ccfee7996e5468f30d4bd5a72
that is faulty.
Without it, DejavuSansMono is rendered normally using the last 2.4.6 sources
and autohinting.

Regards,
Alphonse

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.