[Bug 106] freetype-2.1.3

Seth W.Klein sk at sethwklein.net
Tue Jan 7 11:06:19 PST 2003

Jeroen Coumans <jeroencoumans at gmx.net> wrote:
> On Monday 06 January 2003 17:54, Dagmar d'Surreal wrote:
> > On Sun, 2003-01-05 at 19:57, Jeroen Coumans wrote:
> > > 
> > > 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)
> I disagree; on my LCD the fonts are clearer and more crisp without the 
> bytecode interpreter. This is IMHO of course; [....]

This discussion has me interested. When you say you prefer no bytecode
interpreter on an LCD, do you mean when viewing the MS Web Fonts
that Dagmar mentioned?

> Btw, instead of sedding the #defines they can also appended 
> like this:
> echo #define BYTE_CODE_BLAH_BLAH >> include/freetype/ftoption.h
> This makes the instructions more clear

That would result in:


#endif /* __FTOPTION_H__ */

/* END */

Which might work but is not correct. I do agree it is difficult to
find elegant instructions, though. I finally just used ed. *shudder*

Seth W. Klein
sk at sethwklein.net                             http://www.sethwklein.net/
Maintainer, LFS FAQ                 http://www.linuxfromscratch.org/faq/
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