Re: [ft] how to build freetype so that it matches 1 of 2 observed behaviours

[James Cloos]

The top example has vertical stems which are snapped to pixel boundries;
whereas the lower does not.

Sub pixel is off on both.

I suspect that fedora's rpm has ft's subpixel and bytecode options
disabled (patent encumbrance has been claimed for both techniques;
even though some of the alleged patents have expired, fedora may
not have updated their binary distributions).  The freeworld repo
you mentioned probably doesn't worry about such encumberances.

You can tell most fontconfig apps to force autohinting with the
10-autohint.conf file in /etc/fonts/conf.available.  Symlink it
into the conf.d dir.  You might also want to enable ft's light-
autofit feature with:

 <match target="font" >
   <edit mode="assign" name="hintstyle" >
     <const>hintslight</const>
   </edit>
 </match>

Or, look at these options in include/freetype/config/ftoption.h:

  FT_CONFIG_OPTION_SUBPIXEL_RENDERING
  TT_CONFIG_OPTION_BYTECODE_INTERPRETER
  TT_CONFIG_OPTION_UNPATENTED_HINTING

The rpm build script might set or unset any of those outside of the
patches it applies.

-JimC
-- 
James Cloos <address@hidden>         OpenPGP: 1024D/ED7DAEA6