From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] FreeType unpatented auto-hinter?
Date: Mon, 26 Sep 2011 10:47:47 -0500 [thread overview]
Message-ID: <CAEH5T2ME+xGSmgGBELEDFPzjYYsv0Y8=o=vNK+VxmVJahfdhww@mail.gmail.com> (raw)
In-Reply-To: <4E809692.7050005@nileshgr.com>
On Mon, Sep 26, 2011 at 10:13 AM, Nilesh Govindarajan
<contact@nileshgr.com> 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
>
> What is the difference between this unpatented auto hinter and the
> TrueType BC interpreter?
The "auto-hinter" USE flag enables the old auto-hinter code that was
used before the bytecode interpreter patents expired (which happened
in 2010). The bytecode interpreter is now the default and is
considered to be the best-performing option.
"Since May 2010, all patents related to bytecode hinting have expired
worldwide. It it thus no longer necessary to disable the bytecode
interpreter, and starting with FreeType version 2.4, it is enabled by
default." (according to http://www.freetype.org/patents.html)
I would check with your friend on Twitter to be sure they aren't
talking about pre-freetype-2.4 behavior...
With regard to Ubuntu's actual patches, here they are:
https://launchpadlibrarian.net/76814921/freetype_2.4.4-2ubuntu1.diff.gz
There aren't a lot of apparent changes to the actual freetype engine
(mostly patching the docs, build system and demos). There are
basically no comments, and I can't tell what it's trying to
accomplish.
next prev parent reply other threads:[~2011-09-26 15:50 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 [this message]
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 ` [gentoo-user] " Nikos Chantziaras
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='CAEH5T2ME+xGSmgGBELEDFPzjYYsv0Y8=o=vNK+VxmVJahfdhww@mail.gmail.com' \
--to=paul.hartman+gentoo@gmail.com \
--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