[Bug 106] freetype-2.1.3

Dagmar d'Surreal no.spam at allowed.here
Mon Jan 6 08:54:53 PST 2003

On Sun, 2003-01-05 at 19:57, Jeroen Coumans wrote:
> On Sunday 05 January 2003 21:08, blfs-bugs at linuxfromscratch.org wrote:
> > http://blfs-bugs.linuxfromscratch.org/show_bug.cgi?id=106
> > ------- Additional Comments From larry at linuxfromscratch.org 
> > 2003-01-05 15:08 ------- 
> > #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER is now commented out 
> > instead of being #undef by default. Will still need to remove comment 
> > symbols to use.
> The documentation now explicitly recommends _not_ to enable the bytecode 
> interpreter, since freetype's own rendering now matches it's quality. 

That's all well and good, but some fonts have different glyphs that will
be used when this is turned on.  Microsoft's Web Fonts in particular
seem to each have a set of hinted bitmap equivalents for most of the
font sizes below ~16 that display with a slightly different, less
blurred look.  (The fonts are still quite anti-aliased, they're just
anti-aliased as if someone did them up carefully with MicroAngelo)

Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe blfs-dev' in the subject header of the message

More information about the blfs-dev mailing list