Latest API Changes - maybe a Release Candidate ??

[David Turner]

Hello,

  I've just commited some new, relatively important, changes
  to FreeType 2 (I know some of you are going to hate me.. :-)

  What has changed is mainly the "ftglyph.h" interface, but here's
  the list taken from freetype2/CHANGES:

---------------------------------------------------------------------------
  - CHANGES TO THE HIGH-LEVEL API
  
    o FT_Get_Kerning has a new parameter that allows you to select
      the coordinates of the kerning vector ( font units, scaled,
      scaled + grid-fitted ).
      
    o anti-aliased rendering is now the default for FT_Render_Glyph
      (i.e. corresponds to render_mode == 0 == ft_render_mode_normal).
      To generate a monochrome bitmap, use ft_render_mode_mono, or the
      FT_LOAD_MONOCHROME flag in FT_Load_Glyph/FT_Load_Char.
      
      FT_LOAD_ANTI_ALIAS is still defined, but values to 0.
      
    o <freetype/freetype.h> now include <freetype/config/ftconfig.h>,
      solving a few headaches :-)

    o the so-called convenience functions have moved from "ftoutln.c"
      to "ftglyph.c", and are thus available with this optional component
      of the library. They are declared in <freetype/ftglyph.h> now..

    o the outline functions are now declared in <freetype/ftoutln.h>
      and not in <freetype/freetype.h> anymore.
      
    o <freetype/ftmodule.h> now contains declarations for
       FT_New_Library, FT_Done_Library, FT_Add_Default_Modules.

    o the type FT_GlyphSlotRec has now a "library" field.



  - CHANGES TO THE "ftglyph.h" API
  
    This API has been severely modified in order to make it simpler,
    clearer, and more efficient. It certainly now looks like a real
    "glyph factory" object, and allows client applications to manage
    (i.e. transform, bbox and render) glyph images without ever knowing
    their original format.

    See comments in the source code, it's pretty easy to understand..

--------------------------------------------------------------------------

  All demonstration programs have been cleaned to use the new APIs.
  "ftstring" is now much smaller, renders better (no rounding errors
  in the position of the string center) and faster (it only draws
  what it needs to, uses less memory..).

  I would like to know your opinion on the new "ftglyph.h", see the
  source code in "demos/src/ftstring.c" to see how it is used..

  Support for the auto-hinter has been included, and works well with
  the module. I hope to add it to the source hierarchy real soon now..

  I BELIEVE THAT THIS VERSION HAS EVERYTHING NEEDED FOR A "FINAL"
  RELEASE CANDIDATE, SO EXPECT A NEW BETA SOON NOW !! 

  Meanwhile, I'll be gathering your suggestions and try to fix a few
  of the more horrible bugs in the current snapshot, things like:

    - apparently an incorrect Unicode charmap is generated for Type 1
      fonts using the StandardEncoding. For example, the "T" is seen
      as a "S" with "^".

    - unscaled/unhinted loading of Type 1 composite glyphs doesn't
      work well (the base glyph is translated vertically ??)

    - some metrics are not always computed correctly in some drivers..

  I'll also continue the tutorial..

Best regards to all,

- David

PS: Thanks to Werner for his latest formatting efforts :-)