[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft] Unexpected Rasterization Differences - static vs. dynamic linki

From: Ben Wagner
Subject: Re: [ft] Unexpected Rasterization Differences - static vs. dynamic linking?
Date: Thu, 5 Jan 2017 09:45:08 -0500

Note that there is no equivalent in the FreeType repository to what is installed on Ubuntu, there are a large number of patches that have been applied by Debian and Ubuntu. Some of these changes will change rendering and metrics. You can probably use the directions in third_party/freetype2/README.chromium and modify them for 14.04 instead of 12.04 to get the same source code.

On Thu, Jan 5, 2017 at 6:57 AM, Dominik Röttsches <address@hidden> wrote:
Hi Werner and others,

I am experimenting with statically linking FreeType in Chromium instead of dynamically linking against the system version of FreeType. Doing this, I get unexpected rendering differences: 

Even if I statically link against the same numerical version of FreeType as it is on my Ubuntu 14.04 system, I get a different rasterization result than when I dynamically link against this system version library. The screenshot I am attaching shows the before - dynamically linked against system - vs. after, statically linked against the same version.

I am not sure I am interpreting the image correctly, but it seems that I am losing hinting somehow. 

Are there any modifications for hinting settings in Ubuntu's FreeType version? Or am I missing building/linkage of certain FreeType modules that affect this? Or are there different defaults and I should set them more explicitly?

Thanks for your help,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]