public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: FreeType unpatented auto-hinter?
Date: Tue, 27 Sep 2011 03:41:09 +0300	[thread overview]
Message-ID: <j5r63g$g48$1@dough.gmane.org> (raw)
In-Reply-To: <4E809692.7050005@nileshgr.com>

On 09/26/2011 06:13 PM, Nilesh Govindarajan wrote:
> Somebody on twitter told me that Ubuntu uses a special patch for
> freetype that improves font rendering manifolds.
>
> So I rebuilt freetype with these useflags: +auto-hinter +bindist

When you emerge freetype, it tells you at the end that the bindist USE 
flag does not longer control the auto-hinter.

Also, as another poster mentioned, this is no longer an issue.  The 
patent expired so the auto-hinter is no longer required.


> What is the difference between this unpatented auto hinter and the
> TrueType BC interpreter?

The main difference is that the auto-hinter doesn't take into account 
the font's hinting instructions, resulting in non-optimal hinting.  In 
short: don't use it.

For best looking fonts, disable both the "auto-hinter" and "bindist" USE 
flags.  The bindist USE flag controls the subpixel-rendering algorithm, 
which is still patented by Microsoft in the USA.

So for best results (which is what Ubuntu uses), you need the BC 
interpreter (you get that by disabling the "auto-hinter" flag) and the 
subpixel renderer (by disabling the "bindist" flag).




      parent reply	other threads:[~2011-09-27  0:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 15:13 [gentoo-user] FreeType unpatented auto-hinter? Nilesh Govindarajan
2011-09-26 15:47 ` Paul Hartman
2011-09-26 15:49 ` pk
2011-09-26 16:13   ` James Broadhead
2011-09-26 18:44     ` pk
2011-09-26 15:50 ` pk
2011-09-27  0:41 ` Nikos Chantziaras [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='j5r63g$g48$1@dough.gmane.org' \
    --to=realnc@arcor.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox