Subversion Repositories Kolibri OS

Rev

Go to most recent revision | Blame | Last modification | View Log | Download | RSS feed

  1.  
  2. CHANGES BETWEEN 2.4.12 and 2.5
  3.  
  4.   I. IMPORTANT BUG FIXES
  5.  
  6.     - The cache manager function `FTC_Manager_Reset'  didn't flush the
  7.       cache.
  8.  
  9.  
  10.   II. IMPORTANT CHANGES
  11.  
  12.     - Behdad Esfahbod  (on behalf  of Google) contributed  support for
  13.       color embedded bitmaps (eg. color emoji).
  14.  
  15.       A  new  load  flag,  FT_LOAD_COLOR, makes  FreeType  load  color
  16.       embedded-bitmaps, following this draft specification
  17.  
  18.         https://color-emoji.googlecode.com/git/specification/v1.html
  19.  
  20.       which defines two new SFNT  tables, `CBDT' and `CBLC' (named and
  21.       modeled  after  `EBDT'  and `EBLC',  respectively).   The  color
  22.       bitmaps  are  stored in  the  new  FT_PIXEL_MODE_BGRA format  to
  23.       represent BGRA  pre-multiplied sRGB  images.  If PNG  support is
  24.       available,  PNG color  images as  defined in  the same  proposed
  25.       specification are supported also.
  26.  
  27.       Note that  color bitmaps  are converted  to grayscale  if client
  28.       didn't ask for color.
  29.  
  30.     - As  announced in  the  previous release,  the  old FreeType  CFF
  31.       engine  is now  disabled by  default.  It  can be  conditionally
  32.       compiled     by     defining     the     configuration     macro
  33.       CFF_CONFIG_OPTION_OLD_ENGINE.
  34.  
  35.     - As announced in the previous release,  all code related to macro
  36.       FT_CONFIG_OPTION_OLD_INTERNALS  has been removed,  thus becoming
  37.       obsolete.
  38.  
  39.  
  40.   III. MISCELLANEOUS
  41.  
  42.     - The  property API  (`FT_Property_Get' and  `FT_Property_Set') is
  43.       now declared as stable.
  44.  
  45.       The  exception,   however,  are  the   experimental  auto-hinter
  46.       properties `glyph-to-script-map' and `fallback-script' which are
  47.       subject to change in a forthcoming release.
  48.  
  49.     - `ftview' has been updated to  support color embedded bitmaps; it
  50.       can be toggled on and off  with key `c'.  The small cache toggle
  51.       is now key `K'.
  52.  
  53.     - It  is now  possible  to  control the  version  of the  TrueType
  54.       hinting engine  using the new `interpreter-version'  property of
  55.       the  `truetype' module:  Versions 35  and 38  (the default)  are
  56.       supported,  which  roughly  corresponds to  disable  and  enable
  57.       subpixel hinting support, respectively.
  58.  
  59.       In  both  `ftview'  and  `ftdiff',  switching  between  the  two
  60.       versions  can be  done  with  key `H'.   In  the `ftbench'  demo
  61.       program, command line option `-H'  has been extended to activate
  62.       the non-default interpreter version.
  63.  
  64.     - The `ttdebug' program has been further improved.  In particular,
  65.       it accepts a new command line  option `-H' to select the hinting
  66.       engine.
  67.  
  68.     - Another round of TrueType subpixel hinting fixes.
  69.  
  70.     - The `apinames' tool can now create an import file for NetWare.
  71.  
  72.     - 64bit compilation of the new CFF engine was buggy.
  73.  
  74.     - Some fixes to improve robustness in memory-tight situations.
  75.  
  76.  
  77. ======================================================================
  78.  
  79. CHANGES BETWEEN 2.4.11 and 2.4.12
  80.  
  81.     - We have another CFF parsing and hinting engine!  Written by Dave
  82.       Arnold <darnold@adobe.com>,  this work  has been  contributed by
  83.       Adobe in  collaboration with Google.   It is vastly  superior to
  84.       the old CFF engine, and it  will replace it in the next release.
  85.       Right  now,  it  is  still  off by  default,  and  you  have  to
  86.       explicitly select it using  the new `hinting-engine' property of
  87.       the cff driver:
  88.  
  89.         ...
  90.         #include FT_MODULE_H
  91.         #include FT_CFF_DRIVER_H
  92.  
  93.         FT_Library  library;
  94.         int         engine = FT_CFF_HINTING_ADOBE;
  95.  
  96.  
  97.         ...
  98.         FT_Property_Set( library, "cff", "hinting-engine", &engine );
  99.  
  100.       The code has  a (mature) beta status; we encourage  all users to
  101.       test it and report any problems.
  102.  
  103.       In case you want to activate the new CFF engine unconditionally,
  104.       apply this patch:
  105.  
  106. --- snip ---
  107. diff --git a/src/cff/cffobjs.c b/src/cff/cffobjs.c
  108. index ebcf189..3f2ce6b 100644
  109. --- a/src/cff/cffobjs.c
  110. +++ b/src/cff/cffobjs.c
  111. @@ -1056,7 +1056,7 @@
  112.  
  113.  
  114.      /* set default property values */
  115. -    driver->hinting_engine    = FT_CFF_HINTING_FREETYPE;
  116. +    driver->hinting_engine    = FT_CFF_HINTING_ADOBE;
  117.      driver->no_stem_darkening = FALSE;
  118.  
  119.      return FT_Err_Ok;
  120. --- snip ---
  121.  
  122.     - The  macro FT_CONFIG_OPTION_OLD_INTERNALS  is no  longer set  by
  123.       default.  In  the next  release, we  will completely  remove the
  124.       associated code.   Please update your  programs in case  you are
  125.       still using this macro.
  126.  
  127.  
  128.   II. MISCELLANEOUS
  129.  
  130.     - The  (top-level)  `configure'  script   now  respects  the  MAKE
  131.       environment variable to specify a `make' binary.   For backwards
  132.       compatibility, GNUMAKE still overrides MAKE, though.
  133.  
  134.     - The `ftview'  and `ftdiff'  demo programs have  been redesigned,
  135.       showing  more options  permanently  on the  screen, among  other
  136.       minor improvements.
  137.  
  138.     - Using the `H'  key, it is now possible to  select the CFF engine
  139.       in both `ftview' and `ftdiff'.
  140.  
  141.     - The new command line option `-H' for `ftbench' selects the Adobe
  142.       CFF engine.
  143.  
  144.     - It is  now possible  to directly select  the LCD  rendering mode
  145.       with the keys `A'-`F' in  `ftview'.  The key mapping for cycling
  146.       through LCD modes  has been changed from `K' and  `L' to `k' and
  147.       `l', and  toggling custom LCD  filtering is no longer  mapped to
  148.       key `F' but to key `L'.
  149.  
  150.     - In `ftdiff',  key `x' toggles  between layout modes:  Either use
  151.       the  advance width  (this is  new and  now the  default) or  the
  152.       bounding box information to determine line breaks.
  153.  
  154.     - For all demo  tools, the new command line option  `-v' shows the
  155.       version.
  156.  
  157.     - For the demo tools with a GUI, the new command line options `-w'
  158.       and `-h' select  the width and the height of  the output window,
  159.       respectively.
  160.  
  161.     - The `ttdebug' program was broken and has been reactivated.  Note
  162.       that this program is not compiled by default.
  163.  
  164.  
  165. ======================================================================
  166.  
  167. CHANGES BETWEEN 2.4.10 and 2.4.11
  168.  
  169.   I. IMPORTANT BUG FIXES
  170.  
  171.     - Some vulnerabilities in the  BDF implementation have been fixed.
  172.       Users of this font format should upgrade.
  173.  
  174.  
  175.   II. IMPORTANT CHANGES
  176.  
  177.     - Subpixel  hinting support  has been  contributed by  Infinality,
  178.       based on Greg Hitchcock's whitepaper at
  179.  
  180.         http://www.microsoft.com/typography/cleartype/truetypecleartype.aspx
  181.  
  182.       Originally, it was a separate patch available from
  183.  
  184.         http://www.infinality.net/blog/
  185.  
  186.       and which has been integrated.
  187.  
  188.       Note that  ClearType support is not  completely implemented!  In
  189.       particular,  full support  for the  options `compatible_widths',
  190.       `symmetrical_smoothing,  and  `bgr'  (via the  GETINFO  bytecode
  191.       instruction) is missing.
  192.  
  193.       Activation of  subpixel hinting  support can be  controlled with
  194.       the `TT_CONFIG_OPTION_SUBPIXEL_HINTING' configuration option; it
  195.       is switched off by default.  This feature is still experimental;
  196.       we welcome test reports!
  197.  
  198.     - Support for OpenType collections (OTC) has been added.
  199.  
  200.     - Pure CFF fonts within an SFNT wrapper are now supported.
  201.  
  202.  
  203.   III. MISCELLANEOUS
  204.  
  205.     - Minor rendering improvements to the auto-hinter.
  206.  
  207.     - `FT_GlyphSlot_Oblique' now uses a shear angle of 12°.
  208.  
  209.     - Experimental support  to handle `property modules',  for example
  210.       to control the  behaviour of the auto-hinter.   The API consists
  211.       of two new functions, `FT_Property_Set' and `FT_Property_Get'.
  212.  
  213.       The code is  still subject to change and should  not be used for
  214.       production.
  215.  
  216.     - The `ftdiff' demo program now supports UTF-8 encoded input files
  217.       for option `-f'.
  218.  
  219.     - Using keys `r' and `R', you can now adjust the stroker radius in
  220.       the `ftview' demo program.
  221.  
  222.     - Other, minor fixes and improvements.
  223.  
  224.  
  225. ======================================================================
  226.  
  227. CHANGES BETWEEN 2.4.9 and 2.4.10
  228.  
  229.   I. IMPORTANT BUG FIXES
  230.  
  231.     - Incremental glyph loading as needed by ghostscript was broken.
  232.  
  233.  
  234.   II. MISCELLANEOUS
  235.  
  236.     - A new  function `FT_Outline_EmboldenXY',  contributed by  Alexei
  237.       Podtelezhnikov.
  238.  
  239.     - In the `ftview' demo program, key `e' has been replaced with `x'
  240.       and `y' to  embolden in  the horizontal and  vertical direction,
  241.       respectively.
  242.  
  243.     - The glyph  spacing computation  in `FT_GlyphSlot_Embolden'  (and
  244.       similar code in `ftview') has been improved.
  245.  
  246.     - Minor  improvements to  the TrueType  bytecode  interpreter  and
  247.       glyph loader, the auto-hinter, and the B/W rasterizer.
  248.  
  249.  
  250. ======================================================================
  251.  
  252. CHANGES BETWEEN 2.4.8 and 2.4.9
  253.  
  254.   I. IMPORTANT BUG FIXES
  255.  
  256.     - Another round of fixes to better handle invalid fonts.   Many of
  257.       them are vulnerabilities  (see CVE-2012-1126 up to CVE-2012-1144
  258.       and SA48320) so all users should upgrade.
  259.  
  260.  
  261.   II. MISCELLANEOUS
  262.  
  263.     - The `ENCODING -1 <n>' format of BDF fonts is now supported.
  264.  
  265.     - For BDF fonts,  support for the whole Unicode encoding range has
  266.       been added.
  267.  
  268.     - Better TTF support for x_ppem != y_ppem.
  269.  
  270.     - `FT_Get_Advances' sometimes returned bogus values.
  271.  
  272.     - The  demo  programs  no  longer  recognize  and  handle  default
  273.       suffixes; you now have to always specify the complete font name.
  274.  
  275.     - Better rendering and LCD mode cycling added to `ftview'.
  276.  
  277.  
  278. ======================================================================
  279.  
  280. CHANGES BETWEEN 2.4.7 and 2.4.8
  281.  
  282.   I. IMPORTANT BUG FIXES
  283.  
  284.     - Some vulnerabilities in handling CID-keyed PostScript fonts have
  285.       been fixed; see CVE-2011-3439.
  286.  
  287.  
  288.   II. MISCELLANEOUS
  289.  
  290.     - Chris Liddell contributed a new API, `FT_Get_PS_Font_Value',  to
  291.       retrieve most of the dictionary keys in Type 1 fonts.
  292.  
  293.  
  294. ======================================================================
  295.  
  296. CHANGES BETWEEN 2.4.6 and 2.4.7
  297.  
  298.   I. IMPORTANT BUG FIXES
  299.  
  300.     - Some  vulnerabilities in handling Type 1 fonts  have been fixed;
  301.       see CVE-2011-3256.
  302.  
  303.  
  304.   II. MISCELLANEOUS
  305.  
  306.     - FreeType  now properly  handles ZapfDingbats  glyph names  while
  307.       constructing a Unicode character map (for fonts which don't have
  308.       one).
  309.  
  310.  
  311. ======================================================================
  312.  
  313. CHANGES BETWEEN 2.4.5 and 2.4.6
  314.  
  315.   I. IMPORTANT BUG FIXES
  316.  
  317.     - For TrueType based fonts, the ascender and descender values were
  318.       incorrect sometimes  (off by a pixel if the ppem value was not a
  319.       multiple of 5).   Depending on the use you might now  experience
  320.       a different  layout; the  change should  result in  better, more
  321.       consistent line spacing.
  322.  
  323.     - Fix CVE-2011-0226  which causes a  vulnerability while  handling
  324.       Type 1 fonts.
  325.  
  326.     - BDF fonts  containing  glyphs with negative values  for ENCODING
  327.       were  incorrectly  rejected.  This  bug has  been introduced  in
  328.       FreeType version 2.2.0.
  329.  
  330.     - David Bevan contributed a major revision of the FreeType stroker
  331.       code:
  332.  
  333.       . The behaviour of FT_STROKER_LINEJOIN_BEVEL has been corrected.
  334.  
  335.       . A new  line join style,  FT_STROKER_LINEJOIN_MITER_FIXED,  has
  336.         been introduced to support PostScript and PDF miter joins.
  337.  
  338.       . FT_STROKER_LINEJOIN_MITER_VARIABLE  has been introduced  as an
  339.         alias for FT_STROKER_LINEJOIN_MITER.
  340.  
  341.       . Various stroking glitches has been fixed.
  342.  
  343.  
  344.   II. MISCELLANEOUS
  345.  
  346.       - SFNT bitmap fonts which contain an outline glyph for `.notdef'
  347.         only no longer set the FT_FACE_FLAG_SCALABLE flag.
  348.  
  349.  
  350. ======================================================================
  351.  
  352. CHANGES BETWEEN 2.4.4 and 2.4.5
  353.  
  354.   I. IMPORTANT BUG FIXES
  355.  
  356.     - A rendering regression  for second-order Bézier curves  has been
  357.       fixed, introduced in 2.4.3.
  358.  
  359.  
  360.   II. IMPORTANT CHANGES
  361.  
  362.     - If autohinting  is not  explicitly disabled,  FreeType now  uses
  363.       the autohinter if  a TrueType based font doesn't  contain native
  364.       hints.
  365.  
  366.     - The load flag FT_LOAD_IGNORE_GLOBAL_ADVANCE_WIDTH  has been made
  367.       redundant and  is simply ignored;  this means that FreeType  now
  368.       ignores the global advance width value in TrueType fonts.
  369.  
  370.  
  371.   III. MISCELLANEOUS
  372.  
  373.     - `FT_Sfnt_Table_Info' can now return the number of SFNT tables of
  374.       a font.
  375.  
  376.     - Support for PCF files compressed with bzip2 has been contributed
  377.       by Joel  Klinghed.  To  make this  work, the  OS must  provide a
  378.       bzip2 library.
  379.  
  380.     - Bradley  Grainger  contributed  project  and  solution  files in
  381.       Visual Studio 2010 format.
  382.  
  383.     - Again some fixes to better handle broken fonts.
  384.  
  385.     - Some improvements to the B/W rasterizer.
  386.  
  387.     - Fixes to the cache module to improve robustness.
  388.  
  389.     - Just  Fill Bugs contributed (experimental) code to compute  blue
  390.       zones for CJK Ideographs, improving the alignment of  horizontal
  391.       stems at the top or bottom edges.
  392.  
  393.     - The `ftgrid' demo program  can now display  autohinter segments,
  394.       to be toggled on and off with key `s'.
  395.  
  396.  
  397. ======================================================================
  398.  
  399. CHANGES BETWEEN 2.4.3 and 2.4.4
  400.  
  401.   I. IMPORTANT BUG FIXES
  402.  
  403.     - UVS support (TrueType/OpenType cmap format 14) support is fixed.
  404.       This regression has been introduced in version 2.4.0.
  405.  
  406.  
  407.   II. MISCELLANEOUS
  408.  
  409.     - Detect tricky fonts (e.g. MingLiU)  by the lengths and checksums
  410.       of Type42-persistent subtables (`cvt ', `fpgm', and `prep') when
  411.       a TrueType font without family name is given.  The previous fix,
  412.       introduced in 2.4.3,  was too rigorous,  causing many  subsetted
  413.       fonts (mainly  from PDF files) displayed badly  because FreeType
  414.       forced  rendering with  the TrueType bytecode engine  instead of
  415.       the autohinter.
  416.  
  417.     - Better support for 64bit platforms.
  418.  
  419.     - More fixes to improve handling of broken fonts.
  420.  
  421.  
  422. ======================================================================
  423.  
  424. CHANGES BETWEEN 2.4.2 and 2.4.3
  425.  
  426.   I. IMPORTANT BUG FIXES
  427.  
  428.     - Fix rendering of certain cubic, S-shaped arcs.   This regression
  429.       has been introduced in version 2.4.0.
  430.  
  431.  
  432.   II. MISCELLANEOUS
  433.  
  434.     - To  fix  the  above  mentioned  rendering  issue,  a  new spline
  435.       flattening algorithm  has been  introduced which  speeds up both
  436.       conic and cubic arcs.
  437.  
  438.     - Handling of broken fonts has been further improved.
  439.  
  440.  
  441. ======================================================================
  442.  
  443. CHANGES BETWEEN 2.4.1 and 2.4.2
  444.  
  445.   I. IMPORTANT BUG FIXES
  446.  
  447.     - A stack overflow in CFF Type2 CharStrings interpreter is fixed.
  448.  
  449.     - Handling Type 42 font deallocation was broken; additionally, the
  450.       library is now more robust against malformed Type 42 fonts.
  451.  
  452.  
  453.   II. MISCELLANEOUS
  454.  
  455.     - Two new functions,  `FT_Reference_Library' (in FT_MODULE_H)  and
  456.       `FT_Reference_Face'  (in  FT_FREETYPE_H),  have  been  added  to
  457.       simplify life-cycle management.  A counter gets initialized to 1
  458.       at the  time an  FT_Library (or  FT_Face) structure  is created.
  459.       The  two  new   functions  increment  the  respective   counter.
  460.       `FT_Done_Library' and `FT_Done_Face' then only destroy a library
  461.       or face if the counter is 1, otherwise they simply decrement the
  462.       counter.
  463.  
  464.  
  465. ======================================================================
  466.  
  467. CHANGES BETWEEN 2.4.0 and 2.4.1
  468.  
  469.   I. IMPORTANT CHANGES
  470.  
  471.     - A serious bug in the  CFF font module prevented  display of many
  472.       glyphs in CFF fonts like `MinionPro-Regular.otf'.
  473.  
  474.  
  475. ======================================================================
  476.  
  477. CHANGES BETWEEN 2.3.12 and 2.4.0
  478.  
  479.   I. IMPORTANT CHANGES
  480.  
  481.     - Since May  2010, all  patents  regarding  the TrueType  bytecode
  482.       interpreter have expired worldwide.  Consequently, we now define
  483.       TT_CONFIG_OPTION_BYTECODE_INTERPRETER by  default (and  undefine
  484.       TT_CONFIG_OPTION_UNPATENTED_HINTING).
  485.  
  486.     - A new function `FT_Library_SetLcdFilterWeights' is available  to
  487.       adjust the filter weights set by `FT_Library_SetLcdFilter'.
  488.  
  489.  
  490.   II. MISCELLANEOUS
  491.  
  492.     - Thanks to many reports from Robert Święcki, FreeType's stability
  493.       in handling broken or damaged fonts is much improved.
  494.  
  495.     - Support  for LCD  filter  control has  been  added to  the  demo
  496.       programs `ftdiff' and `ftview'.
  497.  
  498.  
  499. ======================================================================
  500.  
  501. CHANGES BETWEEN 2.3.11 and 2.3.12
  502.  
  503.   I. IMPORTANT CHANGES
  504.  
  505.     - For  `FT_Open_Face',  new  parameters  are  available  to ignore
  506.       preferred family names: FT_PARAM_TAG_IGNORE_PREFERRED_FAMILY and
  507.       FT_PARAM_TAG_IGNORE_PREFERRED_SUBFAMILY.
  508.  
  509.  
  510.   II. MISCELLANEOUS
  511.  
  512.     - Support  for  incremental  font  loading  (controlled  with  the
  513.       FT_CONFIG_OPTION_INCREMENTAL macro) is now active by default.
  514.  
  515.     - Better support for vertical metrics.
  516.  
  517.     - Various minor bug fixes.
  518.  
  519.  
  520. ======================================================================
  521.  
  522. CHANGES BETWEEN 2.3.10 and 2.3.11
  523.  
  524.   I. IMPORTANT BUG FIXES
  525.  
  526.     - Version 2.3.10 broke PCF support.
  527.  
  528.  
  529. ======================================================================
  530.  
  531. CHANGES BETWEEN 2.3.10 and 2.3.9
  532.  
  533.   I. IMPORTANT BUG FIXES
  534.  
  535.     - If all  ASCII digits in a  font have the  same (unscaled) width,
  536.       the autohinter respects this and won't change it.
  537.  
  538.     - TrueType fonts  are now  rasterized correctly  if the horizontal
  539.       and vertical resolution differ.
  540.  
  541.     - Type 1 fonts are now handled with increased precision internally
  542.       to avoid serious rounding issues if non-integral coordinates are
  543.       encountered.
  544.  
  545.     - Horizontally  condensed CFF  fonts (using the font  matrix) were
  546.       rendered  incorrectly.   This  bug  has  been  introduced  after
  547.       release 2.3.5.
  548.  
  549.  
  550.   II. IMPORTANT CHANGES
  551.  
  552.     - Support for the SFNT cmap 13 table format (as defined by the new
  553.       OpenType 1.6 specification) has been added.
  554.  
  555.     - B/W rasterization  of well-hinted TrueType  fonts at small sizes
  556.       has been greatly improved.
  557.  
  558.     - Calculation  of  vertical  metrics in  OpenType  fonts has  been
  559.       improved.
  560.  
  561.  
  562.   III. MISCELLANEOUS
  563.  
  564.     - It  is now  possible to  change  the emboldening  factor in  the
  565.       `ftview' demo program with keys `e' and `E'.
  566.  
  567.     - It is  now possible  to change the  slant value in  the `ftview'
  568.       demo program with keys `s' and `S'.
  569.  
  570.     - The  5-levels  grayscale  mode of  the `ftraster'  module (which
  571.       FreeType doesn't use by default) was broken since version 2.3.0.
  572.  
  573.     - Compilation of the  `ftgrays' and `ftraster' modules  was broken
  574.       in stand-alone mode.
  575.  
  576.     - Various fixes for compilation on 64bit and 16bit architectures.
  577.  
  578.  
  579. ======================================================================
  580.  
  581. CHANGES BETWEEN 2.3.9 and 2.3.8
  582.  
  583.   I. IMPORTANT BUG FIXES
  584.  
  585.     - Very unfortunately, FreeType 2.3.8 contained a change that broke
  586.       its  official ABI.  The  end result  is  that programs  compiled
  587.       against previous versions of the library, but dynamically linked
  588.       to  2.3.8 can  experience  memory corruption  if  they call  the
  589.       `FT_Get_PS_Font_Info' function.
  590.  
  591.       We recommend all users to  upgrade to 2.3.9 as soon as possible,
  592.       or to downgrade to a previous  release of the library if this is
  593.       not an option.
  594.  
  595.       The  origin of the  bug is  that a  new field  was added  to the
  596.       publicly  defined  `PS_FontInfoRec'  structure.   Unfortunately,
  597.       objects of this  type can be stack or  heap allocated by callers
  598.       of   `FT_Get_PS_Font_Info',  resulting   in   a  memory   buffer
  599.       overwrite with its implementation in 2.3.8.
  600.  
  601.       If  you want to  know whether  your code  is vulnerable  to this
  602.       issue,  simply  search  for  the  substrings  `PS_FontInfo'  and
  603.       `PS_Font_Info' in your source code.  If none is found, your code
  604.       is safe and is not affected.
  605.  
  606.       The FreeType team apologizes for the problem.
  607.  
  608.     - The POSIX support  of MacOS resource-fork fonts  (Suitcase fonts
  609.       and LaserWriter Type1 PostScript fonts) was broken in 2.3.8.  If
  610.       FreeType2 is built without Carbon framework, these fonts are not
  611.       handled correctly.  Version 2.3.7 didn't have this bug.
  612.  
  613.     - `FT_Get_Advance' (and `FT_Get_Advances') returned bad values for
  614.       almost all font formats except TrueType fonts.
  615.  
  616.     - Fix a bug  in the SFNT  kerning table  loader/parser which could
  617.       crash the engine if certain malformed tables were encountered.
  618.  
  619.     - Composite SFNT bitmaps are now handled correctly.
  620.  
  621.  
  622.   II. IMPORTANT CHANGES
  623.  
  624.     - The   new  functions   `FT_Get_CID_Is_Internally_CID_keyed'  and
  625.       `FT_Get_CID_From_Glyph_Index'  can be  used to  access CID-keyed
  626.       CFF fonts  via CID  values.  This code  has been  contributed by
  627.       Michael Toftdal.
  628.  
  629.  
  630.   III. MISCELLANEOUS
  631.  
  632.     - `FT_Outline_Get_InsideBorder'  returns   FT_STROKER_BORDER_RIGHT
  633.       for empty outlines.  This was incorrectly documented.
  634.  
  635.     - The `ftview' demo program now supports UTF-8 encoded strings.
  636.  
  637.  
  638. ======================================================================
  639.  
  640. CHANGES BETWEEN 2.3.8 and 2.3.7
  641.  
  642.   I. IMPORTANT BUG FIXES
  643.  
  644.     - CID-keyed fonts in an SFNT wrapper were not handled correctly.
  645.  
  646.     - The smooth renderer produced truncated images (on the right) for
  647.       outline parts with negative horizontal values.  Most fonts don't
  648.       contain outlines left  to the y coordinate axis, but  the effect
  649.       was very noticeable for outlines processed with FT_Glyph_Stroke,
  650.       using thick strokes.
  651.  
  652.     - `FT_Get_TrueType_Engine_Type'  returned a  wrong  value if  both
  653.       configuration  macros  TT_CONFIG_OPTION_BYTECODE_INTERPRETER and
  654.       TT_CONFIG_OPTION_UNPATENTED_HINTING were defined.
  655.  
  656.     - The  `face_index'  field  in   the  `FT_Face'  structure  wasn't
  657.       initialized properly after calling FT_Open_Face and friends with
  658.       a positive face index for CFFs,  WinFNTs, and, most importantly,
  659.       for TrueType Collections (TTCs).
  660.  
  661.  
  662.   II. IMPORTANT CHANGES
  663.  
  664.     - Rudimentary support for Type 1  fonts and CID-keyed Type 1 fonts
  665.       in an SFNT wrapper has been  added -- such fonts are used on the
  666.       Mac.  The core  SFNT tables `TYP1' and `CID '  are passed to the
  667.       PS Type 1  and CID-keyed PS font drivers;  other tables (`ALMX',
  668.       `BBOX', etc.) are not supported yet.
  669.  
  670.     - A  new interface  to extract  advance values  of glyphs  without
  671.       loading their outlines has been added.  The functions are called
  672.       `FT_Get_Advance' and `FT_Get_Advances'; they are defined in file
  673.       `ftadvanc.h' (to be accessed as FT_ADVANCES_H).
  674.  
  675.     - A new function `FT_Get_FSType_Flags' (in FT_FREETYPE_H) has been
  676.       contributed  by   David  Bevan  to  access   the  embedding  and
  677.       subsetting restriction information of fonts.
  678.  
  679.  
  680.   III. MISCELLANEOUS
  681.  
  682.     - FT_MulFix is now an inlined function; by default, assembler code
  683.       is provided for x86 and ARM.  See FT_CONFIG_OPTION_INLINE_MULFIX
  684.       and FT_CONFIG_OPTION_NO_ASSEMBLER (in ftoption.h) for more.
  685.  
  686.     - The handling of `tricky' fonts  (this is, fonts which don't work
  687.       with the  autohinter, needing the font  format's hinting engine)
  688.       has been generalized and changed slightly:
  689.  
  690.       . A new  face flag  FT_FACE_FLAG_TRICKY indicates that  the font
  691.         format's  hinting engine is  necessary for  correct rendering.
  692.         The macro FT_IS_TRICKY can be used to check this flag.
  693.  
  694.       . FT_LOAD_NO_HINTING is now ignored for tricky fonts.  To really
  695.         force  raw  loading  of  such fonts  (without  hinting),  both
  696.         FT_LOAD_NO_HINTING  and FT_LOAD_NO_AUTOHINT  must  be used  --
  697.         this is something which you probably never want to do.
  698.  
  699.       . Tricky  TrueType fonts  always use  the  bytecode interpreter,
  700.         either the patented or unpatented version.
  701.  
  702.     - The  function  `FT_GlyphSlot_Own_Bitmap'  has  been  moved  from
  703.       FT_SYNTHESIS_H to FT_BITMAP_H; it  is now part of the `official'
  704.       API.   (The functions  in  FT_SYNTHESIS_H are  still subject  to
  705.       change, however.)
  706.  
  707.     - In the  `ftdiff'  demo  program you  can now  toggle the  use of
  708.       FT_LOAD_IGNORE_GLOBAL_ADVANCE_WIDTH with key `a'.
  709.  
  710.  
  711. ======================================================================
  712.  
  713. CHANGES BETWEEN 2.3.7 and 2.3.6
  714.  
  715.   I. IMPORTANT BUG FIXES
  716.  
  717.     - If the library  was compiled on an i386  platform using gcc, and
  718.       compiler  option -O3 was  given, `FT_MulFix'  sometimes returned
  719.       incorrect  results   which  could  have   caused  problems  with
  720.       `FT_Request_Metrics'   and  `FT_Select_Metrics',   returning  an
  721.       incorrect descender size.
  722.  
  723.     - Pure CFFs without  subfonts were scaled incorrectly  if the font
  724.       matrix  was  non-standard.  This  bug  has  been  introduced  in
  725.       version 2.3.6.
  726.  
  727.     - The  `style_name'  field  in  the  `FT_FaceRec'  structure often
  728.       contained  a wrong  value for  Type 1  fonts.  This misbehaviour
  729.       has been  introduced  in  version  2.3.6  while  trying  to  fix
  730.       another   problem.   [Note,  however,   that   this   value   is
  731.       informative only  since  the  used  algorithm to  extract  it is
  732.       very simplistic.]
  733.  
  734.  
  735.   II. IMPORTANT CHANGES
  736.  
  737.     - Two      new      macros,      FT_OUTLINE_SMART_DROPOUTS     and
  738.       FT_OUTLINE_EXCLUDE_STUBS,  have been introduced.   Together with
  739.       FT_OUTLINE_IGNORE_DROPOUTS (which  was ignored previously) it is
  740.       now possible to control the dropout mode  of the `raster' module
  741.       (for B&W rasterization),   using  the   `flags'  field   in  the
  742.       `FT_Outline' structure.
  743.  
  744.     - The TrueType bytecode interpreter now passes the dropout mode to
  745.       the B&W rasterizer.  This greatly increases the output for small
  746.       ppem values of many fonts like `pala.ttf'.
  747.  
  748.  
  749. ======================================================================
  750.  
  751. CHANGES BETWEEN 2.3.6 and 2.3.5
  752.  
  753.   I. IMPORTANT BUG FIXES
  754.  
  755.     - A  bunch of  potential security  problems have  been found.  All
  756.       users should update.
  757.  
  758.     - Microsoft  Unicode  cmaps  in  TrueType  fonts  are  now  always
  759.       preferred over Apple cmaps.  This is not a bug per se, but there
  760.       exist some buggy  fonts created for MS which  have broken  Apple
  761.       cmaps.  This affects  only the automatic  selection of FreeType;
  762.       it's always possible to manually select an Apple Unicode cmap if
  763.       desired.
  764.  
  765.     - Many bug fixes to the TrueType bytecode interpreter.
  766.  
  767.     - Improved Mac support.
  768.  
  769.     - Subsetted CID-keyed CFFs are now supported correctly.
  770.  
  771.     - CID-keyed CFFs with subfonts which are scaled in a  non-standard
  772.       way are now handled correctly.
  773.  
  774.     - A call to FT_Open_Face with `face_index' < 0 crashed FreeType if
  775.       the font was a Windows (bitmap) FNT/FON.
  776.  
  777.  
  778.   II. IMPORTANT CHANGES
  779.  
  780.     - The new function `FT_Get_CID_Registry_Ordering_Supplement' gives
  781.       access to  those fields in a CID-keyed font.  The code  has been
  782.       contributed by Derek Clegg.
  783.  
  784.     - George Williams  contributed  code  to validate  the new  `MATH'
  785.       OpenType  table (within  the `otvalid'  module).  The  `ftvalid'
  786.       demo program has been extended accordingly.
  787.  
  788.     - An API for cmap 14 support  (for Unicode Variant Selectors, UVS)
  789.       has been contributed by George Williams.
  790.  
  791.     - A new face flag FT_FACE_FLAG_CID_KEYED has been added,  together
  792.       with a macro FT_IS_CID_KEYED which evaluates to 1 if the font is
  793.       CID-keyed.
  794.  
  795.  
  796.   III. MISCELLANEOUS
  797.  
  798.     - Build support for symbian has been contributed.
  799.  
  800.     - Better WGL4 glyph name support, contributed by Sergey Tolstov.
  801.  
  802.     - Debugging output of the  various FT_TRACEX macros is now sent to
  803.       stderr.
  804.  
  805.     - The `ftview' demo program now provides artificial slanting too.
  806.  
  807.     - The `ftvalid' demo  program has a new  option `-f' to select the
  808.       font index.
  809.  
  810.  
  811. ======================================================================
  812.  
  813. CHANGES BETWEEN 2.3.5 and 2.3.4
  814.  
  815.   I. IMPORTANT BUG FIXES
  816.  
  817.     - Some subglyphs in TrueType fonts were handled incorrectly due to
  818.       a missing graphics state reinitialization.
  819.  
  820.     - Large .Z files  (as distributed with some X11  packages) weren't
  821.       handled correctly, making FreeType increase the heap stack in an
  822.       endless loop.
  823.  
  824.     - A large  number of  bugs have  been fixed  to avoid  crashes and
  825.       endless loops with invalid fonts.
  826.  
  827.  
  828.   II. IMPORTANT CHANGES
  829.  
  830.     - The  two new  cache functions  `FTC_ImageCache_LookupScaler' and
  831.       `FTC_SBit_Cache_LookupScaler' have been added to allow lookup of
  832.       glyphs using an  `FTC_Scaler' object;  this makes it possible to
  833.       use fractional pixel sizes in the cache.  The demo programs have
  834.       been updated accordingly to use this feature.
  835.  
  836.     - A new API  `FT_Get_CMap_Format' has been added to  get the  cmap
  837.       format  of a  TrueType font.   This  is useful  in handling  PDF
  838.       files.  The code has been contributed by Derek Clegg.
  839.  
  840.     - The  auto-hinter  now  produces  better  output  by  default for
  841.       non-Latin scripts  like Indic.   This was done by  using the CJK
  842.       hinting module  as the default instead of the Latin one.  Thanks
  843.       to Rahul Bhalerao for this suggestion.
  844.  
  845.     - A new API `FT_Face_CheckTrueTypePatents'  has been added to find
  846.       out  whether  a  given  TrueType  font  uses  patented  bytecode
  847.       instructions.   The  `ft2demos' bundle  contains a  new  program
  848.       called `ftpatchk' which demonstrates its usage.
  849.  
  850.     - A  new  API  `FT_Face_SetUnpatentedHinting'  has  been  added to
  851.       enable or disable the unpatented hinter.
  852.  
  853.     - Support for Windows FON files in PE format  has been contributed
  854.       by Dmitry Timoshkov.
  855.  
  856.  
  857.   III. MISCELLANEOUS
  858.  
  859.     - Vincent Richomme contributed Visual C++ project files for Pocket
  860.       PCs.
  861.  
  862.  
  863. ======================================================================
  864.  
  865. CHANGES BETWEEN 2.3.4 and 2.3.3
  866.  
  867.   I. IMPORTANT BUG FIXES
  868.  
  869.     - A serious  bug  in  the  handling  of bitmap  fonts (and  bitmap
  870.       strikes of outline fonts) has been introduced in 2.3.3.
  871.  
  872.  
  873. ======================================================================
  874.  
  875. CHANGES BETWEEN 2.3.3 and 2.3.2
  876.  
  877.   I. IMPORTANT BUG FIXES
  878.  
  879.     - Remove a serious regression in the TrueType bytecode interpreter
  880.       that was introduced  in version 2.3.2.  Note that  this does not
  881.       disable  the  improvements  introduced  to  the  interpreter  in
  882.       version 2.3.2,  only some ill  cases that occurred  with certain
  883.       fonts (though a few popular ones).
  884.  
  885.     - The auto-hinter now  ignores single-point contours for computing
  886.       blue zones.   This bug  created `wavy' baselines  when rendering
  887.       text  with  various  fonts  that  use these  contours  to  model
  888.       mark-attach points  (these are points that  are never rasterized
  889.       and are placed outside of the glyph's real outline).
  890.  
  891.     - The `rsb_delta' and `lsb_delta' glyph slot fields are now set to
  892.       zero for mono-spaced fonts.  Otherwise code that uses them would
  893.       essentially ruin the fixed-advance property.
  894.  
  895.     - Fix  CVE-2007-1351 which  can  cause an  integer overflow  while
  896.       parsing  BDF fonts,  leading to  a potentially  exploitable heap
  897.       overflow condition.
  898.  
  899.  
  900.   II. MISCELLANEOUS
  901.  
  902.     - Fixed compilation issues on some 64-bit platforms (see ChangeLog
  903.       for details).
  904.  
  905.     - A new demo  program `ftdiff' has been added  to compare TrueType
  906.       hinting, FreeType's auto  hinting, and rendering without hinting
  907.       in three columns.
  908.  
  909.  
  910. ======================================================================
  911.  
  912. CHANGES BETWEEN 2.3.2 and 2.3.1
  913.  
  914.   I. IMPORTANT BUG FIXES
  915.  
  916.     - FreeType  returned incorrect  kerning information  from TrueType
  917.       fonts when the bytecode  interpreter was enabled.  This happened
  918.       due to a typo introduced in version 2.3.0.
  919.  
  920.     - Negative  kerning  values  from   PFM  files  are  now  reported
  921.       correctly  (they were read  as 16-bit  unsigned values  from the
  922.       file).
  923.  
  924.     - Fixed  a small  memory leak  when `FT_Init_FreeType'  failed for
  925.       some reason.
  926.  
  927.     - The Postscript hinter placed and sized very thin and ghost stems
  928.       incorrectly.
  929.  
  930.     - The TrueType bytecode  interpreter has been fixed to  get rid of
  931.       most of the  rare differences seen in comparison  to the Windows
  932.       font loader.
  933.  
  934.  
  935.   II. IMPORTANT CHANGES
  936.  
  937.     - The auto-hinter  now better deals  with serifs and  corner cases
  938.       (e.g.,  glyph '9'  in Arial  at 9pt,  96dpi).  It  also improves
  939.       spacing  adjustments and doesn't  change widths  for non-spacing
  940.       glyphs.
  941.  
  942.     - Many   Mac-specific   functions   are  deprecated   (but   still
  943.       available);  modern replacements  have been  provided  for them.
  944.       See the documentation in file `ftmac.h'.
  945.  
  946.  
  947. ======================================================================
  948.  
  949. CHANGES BETWEEN 2.3.1 and 2.3.0
  950.  
  951.   I. IMPORTANT BUG FIXES
  952.  
  953.     - The TrueType interpreter sometimes returned incorrect horizontal
  954.       metrics due to a bug in the handling of the SHZ instruction.
  955.  
  956.     - A typo  in  a  security  check  introduced  after  version 2.2.1
  957.       prevented FreeType to render some glyphs in CFF fonts.
  958.  
  959.  
  960. ======================================================================
  961.  
  962. CHANGES BETWEEN 2.3.0 and 2.2.1
  963.  
  964.   I. IMPORTANT BUG FIXES
  965.  
  966.     - The  PCF font  loader  is  now much  more  robust while  loading
  967.       malformed font files.
  968.  
  969.     - Various memory leaks have been found and fixed.
  970.  
  971.     - The TrueType name loader now deals properly with some fonts that
  972.       encode their  names in UTF-16 (the specification  was vague, and
  973.       the code incorrectly assumed UCS-4).
  974.  
  975.     - Fixed the TrueType bytecode  loader to deal properly with subtle
  976.       monochrome/gray  issues  when   scaling  the  CVT.   Some  fonts
  977.       exhibited bad rendering artifacts otherwise.
  978.  
  979.     - `FT_GlyphSlot_Embolden' now  supports vertical layouts correctly
  980.       (it mangled the vertical advance height).
  981.  
  982.     - Fixed byte  endian issues  of `ftmac.c' to  support Mac OS  X on
  983.       i386.
  984.  
  985.     - The  PFR  font loader  no  longer  erroneously  tags font  files
  986.       without any outlines as FT_FACE_FLAG_SCALABLE.
  987.  
  988.  
  989.   II. NEW API FUNCTIONS
  990.  
  991.     - `FT_Library_SetLcdFilter' allows you  to select a special filter
  992.       to be  applied to the bitmaps generated  by `FT_Render_Glyph' if
  993.       one of the FT_RENDER_MODE_LCD and FT_RENDER_MODE_LCD_V modes has
  994.       been  selected.  This filter  is used  to reduce  color fringes;
  995.       several  settings are  available  through the  FT_LCD_FILTER_XXX
  996.       enumeration.
  997.  
  998.       Its  declaration   and  documentation  can  be   found  in  file
  999.       `include/freetype/ftlcdfil.h'   (to  be   accessed   with  macro
  1000.       FT_LCD_FILTER_H).
  1001.  
  1002.       *IMPORTANT*:     This      function     returns     an     error
  1003.       (FT_Err_Unimplemented_Feature) in default  builds of the library
  1004.       for patent reasons.  See below.
  1005.  
  1006.     - `FT_Get_Gasp'  allows you  to query  the flags  of  the TrueType
  1007.       `gasp' table for  a given character pixel size.   This is useful
  1008.       to duplicate  the text rendering  of MS Windows when  the native
  1009.       bytecode  interpreter is  enabled (which  isn't the  default for
  1010.       other patent reasons).
  1011.  
  1012.       Its  declaration   and  documentation  can  be   found  in  file
  1013.       `include/freetype/ftgasp.h'   (to   be   accessed   with   macro
  1014.       FT_GASP_H).
  1015.  
  1016.  
  1017.   III. IMPORTANT CHANGES
  1018.  
  1019.     - The auto-hinter has been tuned a lot to improve its results with
  1020.       serif fonts, resulting in much better font rendering of many web
  1021.       pages.
  1022.  
  1023.     - The unpatented  hinter is now part  of the default  build of the
  1024.       library; we  have added  code to automatically  support `tricky'
  1025.       fonts that need it.
  1026.  
  1027.       This means  that FreeType should `just work'  with certain Asian
  1028.       fonts, like  MingLiU, which cannot properly be  loaded without a
  1029.       bytecode interpreter,  but which fortunately  do not use  any of
  1030.       the patented  bytecode opcodes.  We detect these  fonts by name,
  1031.       so please  report any font file  that doesn't seem  to work with
  1032.       FreeType, and  we shall do what we  can to support it  in a next
  1033.       release.
  1034.  
  1035.       Note  that  the API  hasn't  changed,  so  you can  still  force
  1036.       unpatented hinting with a special parameter to `FT_Open_Face' as
  1037.       well.  This  might be useful in  same cases; for  example, a PDF
  1038.       reader might present  a user option to activate  it to deal with
  1039.       certain  `tricky'   embedded  fonts  which   cannot  be  clearly
  1040.       identified.
  1041.  
  1042.       If you are  a developer for embedded systems,  you might want to
  1043.       *disable*  the   feature  to  save  code   space  by  undefining
  1044.       TT_CONFIG_OPTION_UNPATENTED_HINTING in file `ftoption.h'.
  1045.  
  1046.     - LCD-optimized rendering is now  *disabled* in all default builds
  1047.       of  the  library,  mainly   due  to  patent  issues.   For  more
  1048.       information see:
  1049.  
  1050.       http://lists.gnu.org/archive/html/freetype/2006-09/msg00064.html
  1051.  
  1052.       A  new  configuration macro  FT_CONFIG_OPTION_SUBPIXEL_RENDERING
  1053.       has been introduced in  `ftoption.h'; manually define it in this
  1054.       file if you want to re-enable the feature.
  1055.  
  1056.       The  change only  affects the  implementation, not  the FreeType
  1057.       API.  This means that clients don't need to be modified, because
  1058.       the library still generates  LCD decimated bitmaps, but with the
  1059.       added constraint that R=G=B on each triplet.
  1060.  
  1061.       The  displayed result  should  be equal  to normal  anti-aliased
  1062.       rendering.
  1063.  
  1064.       Additionally,  if   FT_CONFIG_OPTION_SUBPIXEL_RENDERING  is  not
  1065.       defined, the new  `FT_Library_SetLcdFilter' function returns the
  1066.       FT_Err_Unimplemented_Feature error code.
  1067.  
  1068.     - Some computation bugs in  the TrueType bytecode interpreter were
  1069.       found,  which  allow us  to  get rid  of  very  subtle and  rare
  1070.       differences we had experienced with the Windows renderer.
  1071.  
  1072.     - It is now possible to cross-compile the library easily.  See the
  1073.       file `docs/INSTALL.CROSS' for details.
  1074.  
  1075.     - The file `src/base/ftmac.c' now contains code for Mac OS X only;
  1076.       its  deprecated function  `FT_GetFile_From_Mac_Font_Name' always
  1077.       returns an  error even if the QuickDraw  framework is available.
  1078.       The previous version has been moved to `builds/mac/ftmac.c'.
  1079.  
  1080.       Selecting  configure option `--with-quickdraw-carbon'  makes the
  1081.       build process use the original `ftmac.c' file instead of the Mac
  1082.       OS X-only version.
  1083.  
  1084.  
  1085.   IV. MISCELLANEOUS
  1086.  
  1087.     - Various performance and memory footprint optimizations have been
  1088.       performed on  the TrueType and CFF font  loaders, sometimes with
  1089.       very drastic  benefits (e.g., the  TrueType loader is  now about
  1090.       25% faster;  FreeType should use  less heap memory  under nearly
  1091.       all conditions).
  1092.  
  1093.     - The anti-aliased rasterizer has been optimized and is now 15% to
  1094.       25%  percent  faster than  in  previous  versions, depending  on
  1095.       content.
  1096.  
  1097.     - The Type 1 loader has been improved; as an example, it now skips
  1098.       top-level dictionaries properly.
  1099.  
  1100.     - Better support for Mac  fonts on POSIX systems, plus compilation
  1101.       fixes for Mac OS X on ppc64 where `ftmac.c' cannot be built.
  1102.  
  1103.     - Configuration  without `--with-old-mac-fonts'  does  not include
  1104.       `ftmac.c' (this was the behaviour in FreeType version 2.1.10).
  1105.  
  1106.     - The TrueTypeGX validator (gxvalid) checks the order of glyph IDs
  1107.       in the kern table.
  1108.  
  1109.  
  1110. ======================================================================
  1111.  
  1112. CHANGES BETWEEN 2.2.1 and 2.2
  1113.  
  1114.   I. IMPORTANT BUG FIXES
  1115.  
  1116.     - Various integer overflows have been fixed.
  1117.  
  1118.     - PFB fonts with MacOS resource fork weren't  handled correctly on
  1119.       non-MacOS platforms.
  1120.  
  1121.  
  1122. ======================================================================
  1123.  
  1124. CHANGES BETWEEN 2.2 and 2.1.10
  1125.  
  1126. (not released officially)
  1127.  
  1128.   I. IMPORTANT BUG FIXES
  1129.  
  1130.     - Vertical metrics for SFNT fonts were incorrect sometimes.
  1131.  
  1132.     - The FT_HAS_KERNING macro always returned 0.
  1133.  
  1134.     - CFF OpenType  fonts didn't  return correct vertical  metrics for
  1135.       glyphs with outlines.
  1136.  
  1137.     - If FreeType was compiled without hinters, all font formats based
  1138.       on PS outlines weren't scaled correctly.
  1139.  
  1140.  
  1141.   II. IMPORTANT CHANGES
  1142.  
  1143.     - Version 2.2 no longer exposes its internals, this is, the header
  1144.       files  located in  the `include/freetype/internal'  directory of
  1145.       the source package are not  copied anymore by the `make install'
  1146.       command.  Consequently, a number of rogue clients which directly
  1147.       access  FreeType's  internal   functions  and  structures  won't
  1148.       compile without modification.
  1149.  
  1150.       We provide  patches for  most of those  rogue clients.   See the
  1151.       following page for more information:
  1152.  
  1153.         http://www.freetype.org/freetype2/patches/rogue-patches.html
  1154.  
  1155.       Note that, as  a convenience to our Unix  desktop users, version
  1156.       2.2 is *binary* compatible with FreeType 2.1.7, which means that
  1157.       installing this  release on  an existing distribution  shall not
  1158.       break any working desktop.
  1159.  
  1160.     - FreeType's build  mechanism has been redesigned.   With GNU make
  1161.       it  is  now  sufficient  in   most  cases  to  edit  two  files:
  1162.       `modules.cfg',  to  select   the  library  components,  and  the
  1163.       configuration  file  `include/freetype/config/ftoption.h' (which
  1164.       can be copied to the objects directory).  Removing unused module
  1165.       directories   to    prevent   its   compilation    and   editing
  1166.       `include/freetype/config/ftmodule.h' is no longer necessary.
  1167.  
  1168.     - The  LIGHT  hinting algorithm  produces  more pleasant  results.
  1169.       Also, using the  FT_LOAD_TARGET_LIGHT flags within FT_Load_Glyph
  1170.       always forces auto-hinting, as a special exception.  This allows
  1171.       you to experiment with it  even if you have enabled the TrueType
  1172.       bytecode interpreter in your build.
  1173.  
  1174.     - The auto hinter now employs a new algorithm for CJK fonts, based
  1175.       on Akito  Hirai's patch.   Note that this  only works  for fonts
  1176.       with a Unicode charmap at the moment.
  1177.  
  1178.     - The following callback function  types have changed slightly (by
  1179.       adding the `const' keyword where appropriate):
  1180.  
  1181.         FT_Outline_MoveToFunc
  1182.         FT_Outline_LineToFunc
  1183.         FT_Outline_ConicToFunc
  1184.         FT_Outline_CubicToFunc
  1185.         FT_SpanFunc
  1186.         FT_Raster_RenderFunc
  1187.  
  1188.         FT_Glyph_TransformFunc
  1189.         FT_Renderer_RenderFunc
  1190.         FT_Renderer_TransformFunc
  1191.  
  1192.       Note that this doesn't affect binary backward compatibility.
  1193.  
  1194.     - On MacOS,  new APIs have  been added as replacements  for legacy
  1195.       APIs:  `FT_New_Face_From_FSRef'  for  `FT_New_Face_From_FSSpec',
  1196.       and              `FT_GetFile_From_Mac_ATS_Name'              for
  1197.       `FT_GetFile_From_Mac_Name'.  Legacy APIs are still available, if
  1198.       FreeType is built without disabling them.
  1199.  
  1200.     - A new  API `FT_Select_Size'  has been added  to select  a bitmap
  1201.       strike  by its  index.   Code using  other  functions to  select
  1202.       bitmap strikes should be updated to use this function.
  1203.  
  1204.     - A  new API  `FT_Get_SubGlyph_Info'  has been  added to  retrieve
  1205.       subglyph data.  This can be  used by rogue clients which used to
  1206.       access the internal headers to get the corresponding data.
  1207.  
  1208.     - In 2.1.10, the behaviour of `FT_Set_Pixel_Sizes' was changed for
  1209.       BDF/PCF fonts,  and only  for them.  This  causes inconsistency.
  1210.       In this release,  we undo the change.  The  intent of the change
  1211.       in 2.1.10  is to allow  size selection through  real dimensions,
  1212.       which can now be done through `FT_Request_Size'.
  1213.  
  1214.     - Some security  issues were discovered  and fixed in the  CFF and
  1215.       Type  1 loader, causing  crashes of  FreeType by  malformed font
  1216.       files.
  1217.  
  1218.  
  1219.   III. MISCELLANEOUS
  1220.  
  1221.     - The documentation  for FT_LOAD_TARGET_XXX and FT_RENDER_MODE_XXX
  1222.       values now better reflects its usage and differences: One set is
  1223.       used to specify the hinting algorithm, the other to specify  the
  1224.       pixel rendering mode.
  1225.  
  1226.     - `FT_New_Face' and `FT_New_Face_From_FSSpec' in ftmac.c have been
  1227.       changed to count supported scalable faces (sfnt, LWFN) only, and
  1228.       to  return the  number of  available faces  via face->num_faces.
  1229.       Unsupported bitmap faces (fbit, NFNT) are ignored.
  1230.  
  1231.     - builds/unix/configure  has been  improved for  MacOS X.   It now
  1232.       automatically checks available  functions in Carbon library, and
  1233.       prepare to use newest  functions by default.  Options to specify
  1234.       the  dependencies of  each Carbon  APIs (FSSpec,  FSRef, old/new
  1235.       QuickDraw, ATS)  are available too.  By manual  disabling of all
  1236.       QuickDraw   functionality,  FreeType   can   be  built   without
  1237.       `deprecated   function'   warnings    on   MacOS   10.4.x,   but
  1238.       FT_GetFile_Mac_Name  in  ftmac.c  then  is changed  to  a  dummy
  1239.       function, and returns an `unimplemented' error.  For details see
  1240.       builds/mac/README.
  1241.  
  1242.     - SFNT cmap handling has been  improved, mainly to run much faster
  1243.       with CJK fonts.
  1244.  
  1245.     - A   new  function   `FT_Get_TrueType_Engine_Type   (declared  in
  1246.       `FT_MODULE_H')  is  provided  to  determine the  status  of  the
  1247.       TrueType   bytecode  interpreter   compiled  into   the  library
  1248.       (patented, unpatented, unimplemented).
  1249.  
  1250.     - Vertical metrics of glyphs are  synthesized if the font does not
  1251.       provide such information.  You can tell whether  the metrics are
  1252.       synthesized or not by checking the FT_FACE_FLAG_VERTICAL flag of
  1253.       the face.
  1254.  
  1255.     - The demo programs  `ftview' and  `ftstring' have been  rewritten
  1256.       for better readability.   `ftview' has a new switch `-p' to test
  1257.       FT_New_Memory_Face (instead of FT_New_Face).
  1258.  
  1259.     - FreeType now honours bit 1 in the `head' table of TrueType fonts
  1260.       (meaning `left sidebearing point at x=0').  This helps with some
  1261.       buggy fonts.
  1262.  
  1263.     - Rudimentary support for Adobe's new `SING Glyphlet' format.  See
  1264.  
  1265.         http://www.adobe.com/products/indesign/sing_gaiji.html
  1266.  
  1267.       for more information.
  1268.  
  1269.     - The `ftdump'  program from the `ft2demos' bundle  now shows some
  1270.       information about charmaps.  It  also supports a new switch `-v'
  1271.       to increase verbosity.
  1272.  
  1273.     - Better AFM support.  This includes track kerning support.
  1274.  
  1275.  
  1276. ======================================================================
  1277.  
  1278. CHANGES BETWEEN 2.1.10 and 2.1.9
  1279.  
  1280.   I. IMPORTANT BUG FIXES
  1281.  
  1282.     - The size comparison for BDF and PCF files could fail sometimes.
  1283.  
  1284.     - Some  CFF files  were still not  loaded  correctly.   Patch from
  1285.       Derek Noonburg.
  1286.  
  1287.     - The stroker still had some serious bugs.
  1288.  
  1289.     - Boris  Letocha  fixed a  bug in  the  TrueType interpreter:  The
  1290.       NPUSHW instruction wasn't skipped correctly in IF clauses.  Some
  1291.       fonts like `Helvetica 75 Bold' failed.
  1292.  
  1293.     - Another  serious  bug  in  handling  TrueType hints  caused many
  1294.       distortions.  It has been introduced in version 2.1.8, and it is
  1295.       highly recommended to upgrade.
  1296.  
  1297.     - FreeType didn't properly parse empty Type 1 glyphs.
  1298.  
  1299.     - An unbound dynamic buffer growth was fixed in the PFR loader.
  1300.  
  1301.     - Several bugs have been fixed in the cache sub-system.
  1302.  
  1303.     - FreeType behaved incorrectly when resizing two distinct but very
  1304.       close character pixel sizes through `FT_Set_Char_Size' (Savannah
  1305.       bug #12263).
  1306.  
  1307.     - The auto-hinter didn't work properly for fonts without a Unicode
  1308.       charmap -- it even refused to load the glyphs.
  1309.  
  1310.  
  1311.   II. IMPORTANT CHANGES
  1312.  
  1313.     - Many fixes have been applied to drastically reduce the amount of
  1314.       heap   memory   used   by   FreeType,   especially   when  using
  1315.       memory-mapped font files  (which is the default on Unix  systems
  1316.       which support them).
  1317.  
  1318.     - The auto-hinter  has been replaced with a new module, called the
  1319.       `auto-fitter'.  It consumes  less memory  than its  predecessor,
  1320.       and it is  prepared to support non-latin scripts  better in next
  1321.       releases.
  1322.  
  1323.     - George Williams  contributed code to read  kerning data from PFM
  1324.       files.
  1325.  
  1326.     - FreeType   now   uses    the   TT_NAME_ID_PREFERRED_FAMILY   and
  1327.       TT_NAME_ID_PREFERRED_SUBFAMILY   strings   (if   available)  for
  1328.       setting  family  and  style in SFNT  fonts  (patch from Kornfeld
  1329.       Eliyahu Peter).
  1330.  
  1331.     - A  new  API `FT_Sfnt_Table_Info'  (in FT_TRUETYPE_TABLES_H)  has
  1332.       been added to retrieve name and size information of SFNT tables.
  1333.  
  1334.     - A new API `FT_OpenType_Validate' (in FT_OPENTYPE_VALIDATE_H) has
  1335.       been added to validate OpenType tables  (BASE, GDEF, GPOS, GSUB,
  1336.       JSTF).   After validation  it is  no longer  necessary to  check
  1337.       for errors in those tables while accessing them.
  1338.  
  1339.       Note that  this module might  be moved to another library in the
  1340.       future  to avoid  a tight  dependency between  FreeType and  the
  1341.       OpenType specification.
  1342.  
  1343.     - A new API in FT_BITMAP_H  (`FT_Bitmap_New', `FT_Bitmap_Convert',
  1344.       `FT_Bitmap_Copy',  `FT_Bitmap_Embolden',  `FT_Bitmap_Done')  has
  1345.       been added.   Its  use is  to convert an  FT_Bitmap structure in
  1346.       1bpp, 2bpp,  4bpp, or 8bpp  format into  another 8bpp FT_Bitmap,
  1347.       probably using a different pitch, and to further manipulate it.
  1348.  
  1349.     - A new  API `FT_Outline_Embolden'  (in FT_OUTLINE_H) gives  finer
  1350.       control how  outlines are embolded.
  1351.  
  1352.     - `FT_GlyphSlot_Embolden' (in FT_SYNTHESIS_H)  now handles bitmaps
  1353.       also (code contributed  by Chia I Wu).  Note that this  function
  1354.       is still experimental and may be replaced with a better API.
  1355.  
  1356.     - The method  how BDF and PCF  bitmap fonts  are accessed has been
  1357.       refined.   Formerly,   FT_Set_Pixel_Sizes  and  FT_Set_Char_Size
  1358.       were  synonyms in  FreeType's  BDF and PCF interface.  This  has
  1359.       changed now.  FT_Set_Pixel_Sizes  should be  used to  select the
  1360.       actual  font dimensions  (the `strike',  which is the sum of the
  1361.       `FONT_ASCENT'    and    `FONT_DESCENT'    properties),     while
  1362.       FT_Set_Char_Size  selects  the  `nominal' size  (the `PIXELSIZE'
  1363.       property).  In both functions, the width parameter is ignored.
  1364.  
  1365.  
  1366.   III. MISCELLANEOUS
  1367.  
  1368.     - The BDF driver  no longer converts  all returned bitmaps  with a
  1369.       depth of 2bpp or 4bpp to a depth of 8bpp.  The documentation has
  1370.       not  mentioned  this  explicitly,  but  implementors  might have
  1371.       relied on this after looking into the source files.
  1372.  
  1373.     - A new option `--ftversion' has been  added to freetype-config to
  1374.       return the FreeType version.
  1375.  
  1376.     - The  memory  debugger  has  been  updated   to  dump  allocation
  1377.       statistics on  all allocation  sources in the library.   This is
  1378.       useful to  spot greedy  allocations when  loading and processing
  1379.       fonts.
  1380.  
  1381.     - We removed a huge array of constant pointers to constant strings
  1382.       in the `psnames' module.   The problem was that  compilations in
  1383.       PIC mode (i.e.,  when generating a  Unix shared object/dll)  put
  1384.       the array  into the non-shared  writable section of  the library
  1385.       since absolute pointers are not relocatable by nature.
  1386.  
  1387.       This reduces the memory consumption by approximately 16KByte per
  1388.       process linked  to FreeType.   We now also store  the array in a
  1389.       compressed form (as a trie) which saves about 20KByte of code as
  1390.       well.
  1391.  
  1392.     - Kirill  Smelkov provided  patches to make  src/raster/ftraster.c
  1393.       compile stand-alone again.
  1394.  
  1395.  
  1396. ======================================================================
  1397.  
  1398. CHANGES BETWEEN 2.1.9 and 2.1.8
  1399.  
  1400.   I. IMPORTANT BUG FIXES
  1401.  
  1402.     - The function  `FT_Get_CharMap_Index' was only declared,  without
  1403.       any  real  code.   For  consistency,  it  has  been  renamed  to
  1404.       `FT_Get_Charmap_Index'.   (This function is needed  to implement
  1405.       cmap caches.)
  1406.  
  1407.     - `FT_Outline_Get_BBox'  sometimes returned  incorrect values  for
  1408.       conic outlines (e.g., for TrueType fonts).
  1409.  
  1410.     - Handling of `bhed' table has been fixed.
  1411.  
  1412.     - The TrueType driver with enabled byte code interpreter sometimes
  1413.       returned artifacts due to incorrect rounding.  This bug has been
  1414.       introduced after version 2.1.4.
  1415.  
  1416.     - The BDF driver dropped the last glyph in the font.
  1417.  
  1418.     - The BDF driver now uses the DEFAULT_CHAR property (if available)
  1419.       to select a glyph shape for the undefined glyph.
  1420.  
  1421.     - The stroker failed for closed outlines and single points.
  1422.  
  1423.  
  1424.   II. IMPORTANT CHANGES
  1425.  
  1426.     - George  Williams   contributed  code  to   handle  Apple's  font
  1427.       distortion technology found in GX fonts (`avar', `cvar', `fvar',
  1428.       and `gvar' tables;  the Multiple Masters  API has been  slightly
  1429.       extended to cope with the new functionality).
  1430.  
  1431.     - The `FT_GlyphSlotRec' structure has been extended:  The elements
  1432.       `lsb_delta' and  `rsb_delta' give the difference  between hinted
  1433.       and  unhinted  left and right  side bearings  if autohinting  is
  1434.       active.  Using those values can improve the inter-letter spacing
  1435.       considerably.   See the documentation of  `FT_GlyphSlotRec'  and
  1436.       the `ftstring' demo program how to use it.
  1437.  
  1438.     - Loading TrueType and Type 1 fonts has been made much faster.
  1439.  
  1440.     - The stroker is  no longer experimental (but the  cache subsystem
  1441.       still is).
  1442.  
  1443.  
  1444.   III. MISCELLANEOUS
  1445.  
  1446.     - A new  documentation file  `formats.txt' describes various  font
  1447.       formats supported (and not supported) by FreeType.
  1448.  
  1449.  
  1450. ======================================================================
  1451.  
  1452. CHANGES BETWEEN 2.1.8 and 2.1.7
  1453.  
  1454.   I. IMPORTANT BUG FIXES
  1455.  
  1456.     - The native  TrueType hinter contained some  bugs which prevented
  1457.       some fonts to be rendered correctly, most notably Legendum.otf.
  1458.  
  1459.     - The PostScript hinter now produces improved results.
  1460.  
  1461.     - The  linear advance  width  and height  values were  incorrectly
  1462.       rounded,  making  them virtually  unusable  if  not loaded  with
  1463.       FT_LOAD_LINEAR_DESIGN.
  1464.  
  1465.     - Indexing CID-keyed CFF fonts is  now working: The glyph index is
  1466.       correctly  treated as a  CID, similar  to FreeType's  CID driver
  1467.       module.  Note that CID CMap support is still missing.
  1468.  
  1469.     - The FT_FACE_FLAGS_GLYPH_NAMES flag is now  set correctly for all
  1470.       font formats.
  1471.  
  1472.     - Some subsetted Type 1  fonts weren't parsed correctly.  This bug
  1473.       has been introduced in 2.1.7.  In summary, the Type 1 parser has
  1474.       become more robust.
  1475.  
  1476.     - Non-decimal numbers weren't parsed correctly in PS fonts.
  1477.  
  1478.     - The WinFNT driver now correctly reports FT_ENCODING_NONE for all
  1479.       but one encoding.  Use  the new FT_WinFNT_ID_XXX values together
  1480.       with `FT_Get_WinFNT_Header' to get the WinFNT charset ID.
  1481.  
  1482.     - The descender metrics (face->size->metrics.descender) for WinFNT
  1483.       bitmap fonts had the wrong sign.
  1484.  
  1485.     - The (emulated) `seac' support for CFF fonts was broken.
  1486.  
  1487.     - The `flex' operator didn't work for CFF fonts.
  1488.  
  1489.     - PS glyphs  which  use  the   `hintmask'  operator  haven't  been
  1490.       rendered correctly in some cases.
  1491.  
  1492.     - Metrics for BDF and PCF bitmap font formats have been fixed.
  1493.  
  1494.     - Autohinting  is now  disabled for  glyphs  which  are vertically
  1495.       distorted  or mirrored  (using a  transformation matrix).   This
  1496.       fixes a bug which produced zero-height glyphs.
  1497.  
  1498.     - The   `freetype-config'   script   now  handles   --prefix   and
  1499.       --exec-prefix correctly; it also  returns the proper --rpath (or
  1500.       -R) value if FreeType has been built as a shared library.
  1501.  
  1502.  
  1503.   II. IMPORTANT CHANGES
  1504.  
  1505.     - Both  PCF  and BDF  drivers  now  handle  the SETWIDTH_NAME  and
  1506.       ADD_STYLE_NAME    properties.     Values    are   appended    to
  1507.       face->style_name; example: `Bold SemiCondensed'.
  1508.  
  1509.     - The PCF driver now handles bitmap  fonts compressed with the LZW
  1510.       algorithm (extension .pcf.Z, compressed with `compress').
  1511.  
  1512.     - A  new  API   function  `FT_Get_CMap_Language_ID'  (declared  in
  1513.       `tttables.h')  is  available  to   get  the  language  ID  of  a
  1514.       TrueType/SFNT cmap.
  1515.  
  1516.     - The hexadecimal format of  data after the `StartData' command in
  1517.       CID-keyed Type 1 fonts is now supported.  While this can't occur
  1518.       in  file-based   fonts,  it  can   happen  in  document-embedded
  1519.       resources of PostScript documents.
  1520.  
  1521.     - Embedded bitmaps in SFNT-based CFF fonts are now supported.
  1522.  
  1523.     - A simple  API is  now available  to control  FreeType's  tracing
  1524.       mechanism if compiled  with FT_DEBUG_LEVEL_TRACE.   See the file
  1525.       `ftdebug.h' for more details.
  1526.  
  1527.     - YAMATO Masatake contributed improved  handling of MacOS resource
  1528.       forks on non-MacOS platforms (for example, Linux can mount MacOS
  1529.       file systems).
  1530.  
  1531.     - Support for MacOS has been improved; there is now a new function
  1532.       `FT_New_Face_From_FSSpec'  similar to `FT_New_Face'  except that
  1533.       it accepts an FSSpec instead of a path.
  1534.  
  1535.     - The cache sub-system has been rewritten.
  1536.  
  1537.       - There is now support for deinstallation of faces.
  1538.  
  1539.       - A new  API function `FTC_Manager_RemoveFaceID'  has been added
  1540.         to  delete  all  `idle'  nodes  that  correspond  to  a  given
  1541.         FTC_FaceID.  All `locked' nodes  (i.e., those with a reference
  1542.         count > 0), will be modified to prevent them from appearing in
  1543.         further  lookups (they  will  be cleaned  normally when  their
  1544.         reference count reaches 0).
  1545.  
  1546.       - There  is  now  support  for point  scaling  (i.e.,  providing
  1547.         character sizes in points + dpis, instead of pixels).
  1548.  
  1549.       - Three abstract cache classes are now available:
  1550.  
  1551.           FTC_GCache:  Used to store  one glyph  item per  cache node,
  1552.                       with the ability to group common attributes into
  1553.                       `families'.      This    replaces     the    old
  1554.                       FTC_GlyphCache class.
  1555.  
  1556.           FTC_ICache: Used to store one FT_Glyph per cache node.  This
  1557.                       extends  FTC_GCache.  Family  definition, family
  1558.                       comparison, and  glyph loading are  however left
  1559.                       to sub-classes.
  1560.  
  1561.           FTC_SCache: Used to  store up to 16 small  bitmaps per cache
  1562.                       node.    This    extends   FTC_GCache.    Family
  1563.                       definition, family  comparison and glyph loading
  1564.                       are however left to sub-classes.
  1565.  
  1566.       - The file `src/cache/ftcbasic.c' implements:
  1567.  
  1568.           FTC_ImageCache: Extends    FTC_ICache;   implements   family
  1569.                           definitions and glyph loading similar to the
  1570.                           old API.
  1571.  
  1572.           FTC_SBitCache: Extends    FTC_SCache,    implements   family
  1573.                          definitions and glyph  loading similar to the
  1574.                          old API
  1575.  
  1576.         Client  applications  should  be  able to  extend  FTC_GCache,
  1577.         FTC_ICache, or FTC_SCache much more easily (i.e., less code to
  1578.         write, and  less callbacks).  For example,  one could envision
  1579.         caches  that are  capable of  storing  transformed (obliqued),
  1580.         stroked,   emboldened,   or   colored   glyph   images.    Use
  1581.         `ftcbasic.c' as an example.
  1582.  
  1583.       - All public  APIs are now  in `include/freetype/ftcache.h', (to
  1584.         be    accessed   as    `FT_CACHE_H').     The   contents    of
  1585.         `include/freetype/cache/' is only  needed by applications that
  1586.         wish to implement their own caches.
  1587.  
  1588.       - There were some major performance improvements through the use
  1589.         of  various programming  tricks.   Cache hits  are  up to  70%
  1590.         faster than in the old code.
  1591.  
  1592.       - The  FTC_CMapCache has  been simplified.  Charmaps can only be
  1593.         accessed by  index right now.  There  is also a  new API named
  1594.         `FT_Charmap_GetIndex' for this purpose.
  1595.  
  1596.       - The  demo programs  have been  updated to  the new  code.  The
  1597.         previous versions will not work with the current one.
  1598.  
  1599.       - Using  an invalid face  index in FT_Open_Face and friends  now
  1600.         causes an error even if the font contains a single face only.
  1601.  
  1602.  
  1603.   III. MISCELLANEOUS
  1604.  
  1605.     - Wolfgang Domröse contributed support files for building FreeType
  1606.       on the Atari using the PureC compiler.  Note that the Atari is a
  1607.       16bit platform.
  1608.  
  1609.     - Vitaliy Pasternak contributed project files for VS.NET 2003.
  1610.  
  1611.  
  1612. ======================================================================
  1613.  
  1614. CHANGES BETWEEN 2.1.7 and 2.1.6
  1615.  
  1616.   I. IMPORTANT BUG FIXES
  1617.  
  1618.     - Updated  to newest  libtool  version, fixing  build problems  on
  1619.       various platforms.
  1620.  
  1621.     - On  Unix  platforms,  `make  install' didn't  copy  the  correct
  1622.       `ftconfig.h' file.
  1623.  
  1624.   Note that version 2.1.7  contains the same library  C source code as
  1625.   version 2.1.6.
  1626.  
  1627.  
  1628. ======================================================================
  1629.  
  1630. CHANGES BETWEEN 2.1.6 and 2.1.5
  1631.  
  1632.   I. IMPORTANT BUG FIXES
  1633.  
  1634.     - The PFR  font driver didn't  load kerning tables  correctly, and
  1635.       the functions in FT_PFR_H didn't work at all.
  1636.  
  1637.     - Type 1 font  files in  binary format  (PFB) with  an end-of-file
  1638.       indicator weren't accepted by the FreeType engine.
  1639.  
  1640.     - Fonts which contain /PaintType  and /StrokeWidth no longer cause
  1641.       a segfault.  This bug has been introduced in version 2.1.5.
  1642.  
  1643.     - Fonts  loaded  with   FT_LOAD_RENDER  no  longer  cause  strange
  1644.       results.  This bug has been introduced in version 2.1.5.
  1645.  
  1646.     - Some  Windows   (bitmap)  FNT/FON  files   couldn't  be  handled
  1647.       correctly.
  1648.  
  1649.  
  1650.   II. IMPORTANT CHANGES
  1651.  
  1652.     - The internal  module API  has been heavily  changed in  favor of
  1653.       massive simplifications within the font engine.  This also means
  1654.       that authors of third-party modules must adapt their code to the
  1655.       new scheme.
  1656.  
  1657.       NOTE:  THE NEW SCHEME IS NOT COMPLETED YET.  PLEASE WAIT UNTIL A
  1658.       FINAL ANNOUNCEMENT!
  1659.  
  1660.     - The PostScript  parser has been enhanced to  handle comments and
  1661.       strings   correctly.   Additionally,   more  syntax   forms  are
  1662.       recognized.
  1663.  
  1664.     - Added the  optional unpatented hinting system  for TrueType.  It
  1665.       allows  typefaces which  need hinting  to produce  correct glyph
  1666.       forms (e.g., Chinese typefaces  from Dynalab) to work acceptably
  1667.       without infringing Apple patents.   This system is compiled only
  1668.       if  TT_CONFIG_OPTION_COMPILE_UNPATENTED_HINTING  is  defined  in
  1669.       ftoption.h (activated by default).
  1670.  
  1671.  
  1672.   III. MISCELLANEOUS
  1673.  
  1674.     - There  is now  a guard  in the  public header  files  to protect
  1675.       against inclusion of freetype.h from FreeType 1.
  1676.  
  1677.     - Direct inclusion of freetype.h  and other public header files no
  1678.       longer works.  You have to use the documented scheme
  1679.  
  1680.         #include <ft2build.h>
  1681.         #include FT_FREETYPE_H
  1682.  
  1683.       to load freetype.h with  a symbolic name.  This protects against
  1684.       renaming  of public  header  files (which  shouldn't happen  but
  1685.       actually  has, avoiding two  public header  files with  the same
  1686.       name).
  1687.  
  1688.  
  1689. ======================================================================
  1690.  
  1691. CHANGES BETWEEN 2.1.5 and 2.1.4
  1692.  
  1693.   I. IMPORTANT BUG FIXES
  1694.  
  1695.     - Parsing the /CIDFontName field  now removes the leading slash to
  1696.       be in sync with other font drivers.
  1697.  
  1698.     - gzip support was buggy.  Some fonts could not be read.
  1699.  
  1700.     - Fonts which  have nested subglyphs  more than one level  deep no
  1701.       longer cause a segfault.
  1702.  
  1703.     - Creation of synthetic  cmaps for fonts in CFF  format was broken
  1704.       partially.
  1705.  
  1706.     - Numeric  font  dictionary entries  for  synthetic  fonts are  no
  1707.       longer overwritten.
  1708.  
  1709.     - The font matrix  wasn't applied to the advance  width for Type1,
  1710.       CID, and  CFF fonts.  This caused problems  when loading certain
  1711.       synthetic Type 1 fonts like `Helvetica Narrow'.
  1712.  
  1713.     - The test  for the charset registry  in BDF and PCF  fonts is now
  1714.       case-insensitive.
  1715.  
  1716.     - FT_Vector_Rotate  sometimes  returned   strange  values  due  to
  1717.       rounding errors.
  1718.  
  1719.     - The  PCF  driver  now  returns  the  correct  number  of  glyphs
  1720.       (including an artificial `notdef' glyph at index 0).
  1721.  
  1722.     - FreeType now  supports buggy CMaps  which are contained  in many
  1723.       CJK fonts from Dynalab.
  1724.  
  1725.     - Opening  an invalid  font  on a  Mac  caused a  segfault due  to
  1726.       double-freeing memory.
  1727.  
  1728.     - BDF  fonts  with  more   than  32768  glyphs  weren't  supported
  1729.       properly.
  1730.  
  1731.  
  1732.   II. IMPORTANT CHANGES
  1733.  
  1734.     - Accessing bitmap font formats has been synchronized.  To do that
  1735.       the FT_Bitmap_Size  structure has  been extended to  contain new
  1736.       fields `size', `x_ppem', and `y_ppem'.
  1737.  
  1738.     - The FNT driver now returns multiple faces, not multiple strikes.
  1739.  
  1740.     - The `psnames'  module has been  updated to the Adobe  Glyph List
  1741.       version 2.0.
  1742.  
  1743.     - The `psnames' module now understands `uXXXX[X[X]]' glyph names.
  1744.  
  1745.     - The algorithm for guessing the font style has been improved.
  1746.  
  1747.     - For fonts in SFNT format, root->height is no longer increased if
  1748.       the line gap  is zero.  There exist fonts  (containing e.g. form
  1749.       drawing  characters) which  intentionally have  a zero  line gap
  1750.       value.
  1751.  
  1752.     - ft_glyph_bbox_xxx  flags   are  now  deprecated   in  favour  of
  1753.       FT_GLYPH_BBOX_XXX.
  1754.  
  1755.     - ft_module_xxx   flags   are   now   deprecated  in   favour   of
  1756.       FT_MODULE_XXX.
  1757.  
  1758.     - FT_ENCODING_MS_{SJIS,GB2312,BIG5,WANSUNG,JOHAB}      are     now
  1759.       deprecated               in               favour              of
  1760.       FT_ENCODING_{SJIS,GB2312,GIB5,WANSONG,JOHAB}  -- those encodings
  1761.       are not specific to Microsoft.
  1762.  
  1763.  
  1764.   III. MISCELLANEOUS
  1765.  
  1766.     - The  autohinter  has been  further  improved;  for example,  `m'
  1767.       glyphs now retain its vertical symmetry.
  1768.  
  1769.     - Partial support of Mac fonts on non-Mac platforms.
  1770.  
  1771.     - `make   refdoc'   (after   first   `make')   builds   the   HTML
  1772.       documentation.  You need Python for this.
  1773.  
  1774.     - The make build system should  now work more reliably on DOS-like
  1775.       platforms.
  1776.  
  1777.     - Support for  EMX gcc  and Watson C/C++  compilers on  MS-DOS has
  1778.       been added.
  1779.  
  1780.     - Better VMS build support.
  1781.  
  1782.     - Support for the pkg-config  package by providing a `freetype.pc'
  1783.       file.
  1784.  
  1785.     - New configure option --with-old-mac-fonts for Darwin.
  1786.  
  1787.     - Some source files have been  renamed (mainly to fit into the 8.3
  1788.       naming scheme).
  1789.  
  1790.  
  1791. ======================================================================
  1792.  
  1793. CHANGES BETWEEN 2.1.4 and 2.1.3
  1794.  
  1795.   I. IMPORTANT BUG FIXES
  1796.  
  1797.     - Updated  to newest  libtool  version, fixing  build problems  on
  1798.       various platforms.
  1799.  
  1800.     - A fix  in the Gzip stream  reader: It couldn't  read certain .gz
  1801.       files properly due to a  small typo.  In certain cases, FreeType
  1802.       could  also loop  endlessly  when trying  to  load tiny  gzipped
  1803.       files.
  1804.  
  1805.     - The configure script now tries  to use the system-wide zlib when
  1806.       it  finds one  (instead of  the  copy found  in src/gzip).   And
  1807.       `freetype-config' has  been updated to return  relevant flags in
  1808.       this case when invoked with `--libs' (e.g. `-lzlib').
  1809.  
  1810.     - Certain fonts couldn't be loaded  by 2.1.3 because they lacked a
  1811.       Unicode   charmap  (e.g.   SYMBOL.TTF).    FreeType  erroneously
  1812.       rejected them.
  1813.  
  1814.     - The CFF loader was modified to accept fonts which only contain a
  1815.       subset of  their reference charset.  This  prevented the correct
  1816.       use of PDF-embedded fonts.
  1817.  
  1818.     - The logic to detect Unicode charmaps has been modified.  This is
  1819.       required to  support fonts which include both  16-bit and 32-bit
  1820.       charmaps (like very  recent asian ones) using the  new 10 and 12
  1821.       SFNT formats.
  1822.  
  1823.     - The TrueType  loader now limits  the depth of  composite glyphs.
  1824.       This is necessary to prevent broken fonts to break the engine by
  1825.       blowing the stack with recursive glyph definitions.
  1826.  
  1827.     - The CMap cache is now  capable of managing UCS-4 character codes
  1828.       that   are   mapped   through   extended  charmaps   in   recent
  1829.       TrueType/OpenType fonts.
  1830.  
  1831.     - The   cache  sub-system   now  properly   manages  out-of-memory
  1832.       conditions  instead of  blindly  reporting them  to the  caller.
  1833.       This means that it will try to empty the cache before restarting
  1834.       its allocations to see if that can help.
  1835.  
  1836.     - The  PFR driver  didn't return  the list  of  available embedded
  1837.       bitmaps properly.
  1838.  
  1839.     - There was  a nasty  memory leak when  using embedded  bitmaps in
  1840.       certain font formats.
  1841.  
  1842.  
  1843.   II. IMPORTANT CHANGES
  1844.  
  1845.     - David Chester  contributed some enhancements  to the auto-hinter
  1846.       that  significantly increase  the  quality of  its output.   The
  1847.       Postscript hinter was also improved in several ways.
  1848.  
  1849.     - The FT_RENDER_MODE_LIGHT render mode was implemented.
  1850.  
  1851.     - A new  API function called `FT_Get_BDF_Property'  has been added
  1852.       to FT_BDF_H to  retrieve BDF properties from BDF  _and_ PCF font
  1853.       files.   THIS  IS  STILL  EXPERIMENTAL,  since  it  hasn't  been
  1854.       properly tested yet.
  1855.  
  1856.     - A Windows FNT specific API has been added, mostly to access font
  1857.       headers.  This is used by Wine.
  1858.  
  1859.     - TrueType tables  without an `hmtx' table are  now tolerated when
  1860.       an  incremental interface  is  used.  This  happens for  certain
  1861.       Type42 fonts passed from Ghostscript to FreeType.
  1862.  
  1863.     - The PFR font driver is  now capable of returning the font family
  1864.       and style  names when  they are available  (instead of  the sole
  1865.       `FontID').   This  is  performed  by parsing  an  *undocumented*
  1866.       portion of the font file!
  1867.  
  1868.  
  1869.   III. MISCELLANEOUS
  1870.  
  1871.     - The path stroker in FT_STROKER_H has entered beta stage.  It now
  1872.       works very  well, but  its interface might  change a bit  in the
  1873.       future.  More on this in later releases.
  1874.  
  1875.     - The documentation for  FT_Size_Metrics didn't appear properly in
  1876.       the API reference.
  1877.  
  1878.     - The file docs/VERSION.DLL has been updated to explain versioning
  1879.       with FreeType  (i.e., comparing release/libtool/so  numbers, and
  1880.       how to use them in autoconf scripts).
  1881.  
  1882.     - The  installation  documentation  has been  seriously  revamped.
  1883.       Everything is now in the `docs' directory.
  1884.  
  1885.  
  1886. ======================================================================
  1887.  
  1888. CHANGES BETWEEN 2.1.3 and 2.1.2
  1889.  
  1890.   I. IMPORTANT BUG FIXES
  1891.  
  1892.     - FT_Vector_Transform  had  been  incorrectly modified  in  2.1.2,
  1893.       resulting  in  incorrect   transformations  being  applied  (for
  1894.       example, rotations were processed in opposite angles).
  1895.  
  1896.     - The format  8 and 12 TrueType charmap  enumeration routines have
  1897.       been fixed (FT_Get_Next_Char returned invalid values).
  1898.  
  1899.     - The  PFR font driver  returned incorrect  advance widths  if the
  1900.       outline  and metrics resolution  defined in  the font  file were
  1901.       different.
  1902.  
  1903.     - FT_Glyph_To_Bitmap now returns  successfully when called with an
  1904.       FT_BitmapGlyph argument (it previously returned an error).
  1905.  
  1906.     - A bug  in the Type 1  loader that prevented  valid font bounding
  1907.       boxes to be loaded from multiple master fonts.
  1908.  
  1909.     - The SFNT  validation code has been rewritten.   FreeType can now
  1910.       load `broken'  fonts that were  usable on Windows, but  not with
  1911.       previous versions of the library.
  1912.  
  1913.     - The computation of bearings in the BDF driver has been fixed.
  1914.  
  1915.     - The Postscript hinter crashed when trying to hint certain glyphs
  1916.       (more precisely,  when trying to  apply hints to an  empty glyph
  1917.       outline).
  1918.  
  1919.     - The  TrueType glyph  loader  now supports  composites in  `Apple
  1920.       format'  (they differ slightly  from Microsoft/OpenType  ones in
  1921.       the way transformation offsets are computed).
  1922.  
  1923.     - FreeType was  very slow at opening certain  asian CID/CFF fonts,
  1924.       due to  fixed increment  in dynamic array  re-allocations.  This
  1925.       has  been changed  to  exponential behaviour  to get  acceptable
  1926.       performance.
  1927.  
  1928.  
  1929.  
  1930.   II. IMPORTANT CHANGES
  1931.  
  1932.     - The PCF driver now supports gzip-compressed font files natively.
  1933.       This means that  you will be able to use  all these bitmap fonts
  1934.       that  come with  XFree86 with  FreeType (and  libXft/libXft2, by
  1935.       extension).
  1936.  
  1937.     - The  automatic and  postscript hinters  have both  been updated.
  1938.       This  results in  a relatively  important increase  of rendering
  1939.       quality since  many nasty defaults have been suppressed.  Please
  1940.       visit the web page:
  1941.  
  1942.         http://www.freetype.org/hinting/smooth-hinting.html
  1943.  
  1944.       for additional details on this topic.
  1945.  
  1946.     - The `load_flags' parameter of `FT_Load_Glyph' is now an FT_Int32
  1947.       (instead  of just  being  an FT_Int).   This  breaks source  and
  1948.       binary  compatibility for  16bit systems  only,  while retaining
  1949.       both of them for 32 and 64 bit ones.
  1950.  
  1951.       Some new flags have been added consequently:
  1952.  
  1953.         FT_LOAD_NO_AUTOHINT   :: Disable the use of the auto-hinter
  1954.                                  (but not native format hinters).
  1955.  
  1956.         FT_LOAD_TARGET_NORMAL :: Hint and render for normal
  1957.                                  anti-aliased displays.
  1958.  
  1959.         FT_LOAD_TARGET_MONO   :: Hint and render for 1-bit displays.
  1960.  
  1961.         FT_LOAD_TARGET_LCD    :: Hint and render for horizontal RGB or
  1962.                                  BGR sub-pixel displays (like LCD
  1963.                                  screens).  THIS IS STILL
  1964.                                  EXPERIMENTAL!
  1965.  
  1966.         FT_LOAD_TARGET_LCD_V  :: Same as FT_LOAD_TARGET_LCD, for
  1967.                                  vertical sub-pixel displays (like
  1968.                                  rotated LCD screens).  THIS IS STILL
  1969.                                  EXPERIMENTAL!
  1970.  
  1971.       FT_LOAD_MONOCHROME   is  still   supported,  but   only  affects
  1972.       rendering, not the hinting.
  1973.  
  1974.       Note that the `ftview'  demo program available in the `ft2demos'
  1975.       package  has been  updated to  support LCD-optimized  display on
  1976.       non-paletted displays (under Win32 and X11).
  1977.  
  1978.     - The  PFR  driver  now  supports embedded  bitmaps  (all  formats
  1979.       supported), and returns correct kerning metrics for all glyphs.
  1980.  
  1981.     - The TrueType charmap loader  now supports certain `broken' fonts
  1982.       that load under Windows without problems.
  1983.  
  1984.     - The cache API has been slightly modified (it's still a beta!):
  1985.  
  1986.        - The type  FTC_ImageDesc has been removed; it  is now replaced
  1987.          by  FTC_ImageTypeRec.   Note that  one  of  its  fields is  a
  1988.          `load_flag' parameter for FT_Load_Glyph.
  1989.  
  1990.        - The  field  `num_grays' of  FT_SBitRec  has  been changed  to
  1991.          `max_grays'  in  order to  fit  within  a  single byte.   Its
  1992.          maximum value is thus 255 (instead of 256 as previously).
  1993.  
  1994.  
  1995.   III. MISCELLANEOUS
  1996.  
  1997.     - Added support  for the  DESTDIR variable during  `make install'.
  1998.       This simplifies packaging of FreeType.
  1999.  
  2000.     - Included modified  copies of the  ZLib sources in  `src/gzip' in
  2001.       order to support  gzip-compressed PCF fonts.  We do  not use the
  2002.       system-provided  zlib  for  now,   though  this  is  a  probable
  2003.       enhancement for future releases.
  2004.  
  2005.     - The DocMaker tool used to generate the on-line API reference has
  2006.       been   completely    rewritten.    It   is    now   located   in
  2007.       `src/tools/docmaker/docmaker.py'.  Features:
  2008.  
  2009.         - better cross-referenced output
  2010.         - more polished output
  2011.         - uses Python regular expressions  (though it didn't speed the
  2012.           program)
  2013.         - much  more  modular structure,  which  allows for  different
  2014.           `backends'  in  order to  generate  HTML,  XML, or  whatever
  2015.           format.
  2016.  
  2017.       One can regenerate the API reference by calling:
  2018.  
  2019.          python src/tools/docmaker/docmaker.py \
  2020.                 --prefix=ft2 \
  2021.                 --title=FreeType-2.1.3 \
  2022.                 --output=<outputdirectory>
  2023.                 include/freetype/*.h \
  2024.                 include/freetype/config/*.h \
  2025.                 include/freetype/cache/*.h
  2026.  
  2027.     - A new, experimental, support for incremental font loading (i.e.,
  2028.       loading  of fonts  where the  glyphs are  not in  the  font file
  2029.       itself, but provided by an external component, like a Postscript
  2030.       interpreter) has been added by Graham Asher.  This is still work
  2031.       in progress, however.
  2032.  
  2033.     - A new,  EXPERIMENTAL, path stroker  has been added.   It doesn't
  2034.       suffer  from  severe  rounding  errors  and  treat  bezier  arcs
  2035.       directly.  Still work in progress (i.e. not part of the official
  2036.       API).   See  the file  <freetype/ftstroker.h>  for  some of  the
  2037.       details.
  2038.  
  2039.     - The massive  re-formatting of sources and  internal re-design is
  2040.       still under-way.  Many  internal functions, constants, and types
  2041.       have been renamed.
  2042.  
  2043.  
  2044. ======================================================================
  2045.  
  2046. CHANGES BETWEEN 2.1.2 and 2.1.1
  2047.  
  2048.   I. IMPORTANT BUG FIXES
  2049.  
  2050.     - Many  font drivers didn't  select a  Unicode charmap  by default
  2051.       when a new face  was opened (with the FT_CONFIG_OPTION_USE_CMAPS
  2052.       options enabled),  causing many applications  to not be  able to
  2053.       display text correctly with the 2.1.x releases.
  2054.  
  2055.     - The  PFR driver had  a bug  in its  composite loading  code that
  2056.       produces incorrectly placed accents with many fonts.
  2057.  
  2058.     - The Type42 driver crashed sometimes due to a nasty bug.
  2059.  
  2060.     - The Type 1 custom encoding  charmap didn't handle the case where
  2061.       the first glyph index wasn't 0.
  2062.  
  2063.     - A  serious  typo  in  the  TrueType  composite  loader  produced
  2064.       incorrectly placed  glyphs in fonts  like `Wingdings' and  a few
  2065.       others.
  2066.  
  2067.  
  2068.   II. MISCELLANEOUS
  2069.  
  2070.     - The Win32  Visual C++ project  file has been updated  to include
  2071.       the PFR driver as well.
  2072.  
  2073.     - `freetype.m4' is  now installed by default by  `make install' on
  2074.       Unix systems.
  2075.  
  2076.     - The function  FT_Get_PS_Font_Info now works with  CID and Type42
  2077.       fonts as well.
  2078.  
  2079.  
  2080. ======================================================================
  2081.  
  2082. CHANGES BETWEEN 2.1.1 and 2.1.0
  2083.  
  2084.   I. IMPORTANT BUG FIXES
  2085.  
  2086.     - The  `version_info'  returned   by  `freetype-config'  in  2.1.0
  2087.       returned an invalid value.  It now returns 9:1:3 (2.0.9 returned
  2088.       9:0:3).
  2089.  
  2090.     - Version 2.1.0  couldn't be linked against  applications on Win32
  2091.       and  Amiga systems  due  to  a new  debug  function that  wasn't
  2092.       properly   propagated  to   the  system-specific   directory  in
  2093.       `builds'.
  2094.  
  2095.     - Various MacOS and Mac OS X specific fixes.
  2096.  
  2097.     - Fixed  a bug in  the TrueType  charmap validation  routines that
  2098.       made version  2.1.0 too restrictive  -- many popular  fonts have
  2099.       been rejected.
  2100.  
  2101.     - There was  still a very small difference  between the monochrome
  2102.       glyph bitmaps produced by FreeType 1.x and FreeType 2.x with the
  2103.       bytecode  interpreter enabled.   This was  caused by  an invalid
  2104.       flag setting in the TrueType glyph loader, making the rasterizer
  2105.       change  its  drop-out   control  mode.   Now  the results should
  2106.       _really_ be completely identical.
  2107.  
  2108.     - The TrueType name table loader has been improved to support many
  2109.       popular  though buggy Asian  fonts.  It  now ignores  empty name
  2110.       entries,  invalid  pointer offsets  and  a  few other  incorrect
  2111.       subtleties.  Moreover,  name strings  are now loaded  on demand,
  2112.       which reduces the memory load  of many faces (e.g. the ARIAL.TTF
  2113.       font file contains a 10kByte name table with 70 names).
  2114.  
  2115.     - Fixed a bug in the Postscript hinter that prevented family blues
  2116.       substitution to happen correctly.
  2117.  
  2118.  
  2119.   II. NEW FEATURES
  2120.  
  2121.     - Three new font drivers in this release:
  2122.  
  2123.       * A  BDF  font driver,  contributed  by  Franco Zappa  Nardelli,
  2124.         heavily  modified   by  Werner  Lemberg.    It  also  supports
  2125.         anti-aliased bitmaps (using a slightly extended BDF format).
  2126.  
  2127.       * A Type42  font driver, contributed by Roberto  Alameda.  It is
  2128.         still experimental but seems to work relatively well.
  2129.  
  2130.       * A PFR  font driver, contributed  by David Turner  himself.  It
  2131.         doesn't  support PFR  hinting --  note that  BitStream  has at
  2132.         least two patents on this format!
  2133.  
  2134.  
  2135.   III. MISCELLANEOUS
  2136.  
  2137.     - The  cache  sub-system has  been  optimized  in important  ways.
  2138.       Cache hits are now significantly faster.  For example, using the
  2139.       CMap cache is about  twice faster than calling FT_Get_Char_Index
  2140.       on most platforms.  Similarly, using an SBit cache is about five
  2141.       times faster  than loading the  bitmaps from a bitmap  file, and
  2142.       300 to  500 times  faster than generating  them from  a scalable
  2143.       format.
  2144.  
  2145.       Note that  you should recompile  your sources if you  designed a
  2146.       custom  cache  class for  the  FT2  Cache  subsystem, since  the
  2147.       changes performed are source, but not binary, compatible.
  2148.  
  2149.  
  2150. ======================================================================
  2151.  
  2152. CHANGES BETWEEN 2.1.0 and 2.0.9
  2153.  
  2154.   I. IMPORTANT BUG FIXES
  2155.  
  2156.     - The  TrueType bytecode  interpreter  has been  fixed to  produce
  2157.       _exactly_ the same output as FreeType 1.x.  Previous differences
  2158.       were due  to slightly distinct  fixed-point computation routines
  2159.       used to perform dot products and vector length measurements.
  2160.  
  2161.       It seems  that native TrueType hinting  is _extremely_ sensitive
  2162.       to  rounding errors.  The  required vector  computation routines
  2163.       have been optimized and placed within the `ttinterp.c' file.
  2164.  
  2165.     - Fixed the parsing of accelerator tables in the PCF font driver.
  2166.  
  2167.     - Fixed the Type1 glyph loader  routine used to compute the font's
  2168.       maximum advance width.
  2169.  
  2170.  
  2171.   II. NEW FEATURES
  2172.  
  2173.     - The `configure' script used on Unix systems has been modified to
  2174.       check  that  GNU  Make  is  being used  to  build  the  library.
  2175.       Otherwise,  it  will display  a  message  proposing  to use  the
  2176.       GNUMAKE environment variable to name it.
  2177.  
  2178.       The Unix-specific file README.UNX has been modified accordingly.
  2179.  
  2180.  
  2181.   III. MISCELLANEOUS
  2182.  
  2183.     - The  FreeType  License in  `docs/FTL.TXT'  has  been updated  to
  2184.       include  a  proposed preferred  disclaimer.   If  you are  using
  2185.       FreeType in your products, you are encouraged (but not mandated)
  2186.       to use the following text in your documentation:
  2187.  
  2188.       """
  2189.         Portions of this software are copyright © 1996-2002 The
  2190.         FreeType Project (www.freetype.org).  All rights reserved.
  2191.       """
  2192.  
  2193.     - The default size of the render pool has been reduced to 16kByte.
  2194.       This  shouldn't result  in any  noticeable  performance penalty,
  2195.       unless you are  using the engine as-is to  render very large and
  2196.       complex glyphs.
  2197.  
  2198.     - The  FreeType 2  redesign has  begun.  More  information  can be
  2199.       found at this URL:
  2200.  
  2201.         http://www.freetype.org/freetype2/redesign.html
  2202.  
  2203.       The following  internal changes  have been performed  within the
  2204.       sources of this release:
  2205.  
  2206.         - Many   internal  types   have  been   renamed   to  increase
  2207.           consistency.   The  following  should  be true,  except  for
  2208.           public types:
  2209.  
  2210.             * All structure  types have a name ending  in `Rec' (short
  2211.               for `record').
  2212.  
  2213.             * A  pointer-to-structure type  has the  same name  as the
  2214.               structure, _without_ the `Rec' suffix.
  2215.  
  2216.               Example:
  2217.  
  2218.                 typedef struct FooRec_
  2219.                 {
  2220.                   ...
  2221.  
  2222.                 } FooRec, *Foo;
  2223.  
  2224.         - Many   internal  macros  have   been  renamed   to  increase
  2225.           consistency.  The following should be true:
  2226.  
  2227.             * All  macros  have a  name  beginning  with `FT_'.   This
  2228.               required a few changes like
  2229.  
  2230.                 ALLOC   => FT_ALLOC
  2231.                 FREE    => FT_FREE
  2232.                 REALLOC => FT_REALLOC
  2233.  
  2234.             * All  macros are completely  UPPERCASE.  This  required a
  2235.               few changes like:
  2236.  
  2237.                 READ_Short  => FT_READ_SHORT
  2238.                 NEXT_Short  => FT_NEXT_SHORT
  2239.                 GET_ULongLE => FT_GET_ULONG_LE
  2240.                 MEM_Set     => FT_MEM_SET
  2241.                 MEM_Copy    => FT_MEM_COPY
  2242.                 etc.
  2243.  
  2244.             * Whenever   possible,   all   macro  names   follow   the
  2245.               FT_<OBJECT>_<METHOD> pattern.  For example
  2246.  
  2247.                 ACCESS_Frame   => FT_FRAME_ENTER
  2248.                 FORGET_Frame   => FT_FRAME_EXIT
  2249.                 EXTRACT_Frame  => FT_FRAME_EXTRACT
  2250.                 RELEASE_Frame  => FT_FRAME_RELEASE
  2251.  
  2252.                 FILE_Pos       => FT_STREAM_POS
  2253.                 FILE_Seek      => FT_STREAM_SEEK
  2254.                 FILE_Read      => FT_STREAM_READ
  2255.                 FILE_ReadAt    => FT_STREAM_READ_AT
  2256.                 READ_Fields    => FT_STREAM_READ_FIELDS
  2257.  
  2258.         - Many  internal functions  have  been renamed  to follow  the
  2259.           FT_<Object>_<Method> pattern.  For example:
  2260.  
  2261.             FT_Seek_Stream       => FT_Stream_Seek
  2262.             FT_Read_Stream_At    => FT_Stream_ReadAt
  2263.             FT_Done_Stream       => FT_Stream_Close
  2264.             FT_New_Stream        => FT_Stream_Open
  2265.             FT_New_Memory_Stream => FT_Stream_OpenMemory
  2266.             FT_Extract_Frame     => FT_Stream_ExtractFrame
  2267.  
  2268.           Note that method names do not contain `_'.
  2269.  
  2270.         - The FT_ALLOC_ARRAY  and FT_REALLOC_ARRAY have  been replaced
  2271.           with  FT_NEW_ARRAY and  FT_RENEW_ARRAY which  do not  take a
  2272.           type  as the  fourth argument.   Instead, the  array element
  2273.           type  size is computed  automatically from  the type  of the
  2274.           target pointer used.
  2275.  
  2276.         - A  new object  class, FT_CMap,  has been  introduced.  These
  2277.           internal  objects are  used to  model character  maps.  This
  2278.           eases  the support  of additional  charmap types  within the
  2279.           engine.
  2280.  
  2281.         - A new  configuration file named `ftstdlib.h'  has been added
  2282.           to `include/freetype/config'.  It  is used to define aliases
  2283.           for  _every_ routine  of the  ISO  C library  that the  font
  2284.           engine   uses.    Each    aliases   has   a   `ft_'   prefix
  2285.           (e.g. `ft_strlen' is an alias for `strlen').
  2286.  
  2287.           This is  used to  ease the porting  of FreeType 2  to exotic
  2288.           runtime environments where the ISO C Library isn't available
  2289.           (e.g.  XFree86 extension modules).
  2290.  
  2291.       More details are available in the `ChangeLog' file.
  2292.  
  2293.  
  2294. ======================================================================
  2295.  
  2296. CHANGES BETWEEN 2.0.9 and 2.0.8
  2297.  
  2298.   I. IMPORTANT BUG FIXES
  2299.  
  2300.     - Certain fonts like `foxjump.ttf' contain broken name tables with
  2301.       invalid entries and wild offsets.  This caused FreeType to crash
  2302.       when trying to load them.
  2303.  
  2304.       The  SFNT `name'  table  loader has  been  fixed to  be able  to
  2305.       support these strange fonts.
  2306.  
  2307.       Moreover, the code  in charge of processing this  table has been
  2308.       changed  to always favour  Windows-formatted entries  over other
  2309.       ones.  Hence,  a font that works  on Windows but not  on the Mac
  2310.       will  load cleanly in  FreeType and  report accurate  values for
  2311.       Family & PostScript names.
  2312.  
  2313.     - The CID font driver has been fixed.  It unfortunately returned a
  2314.       Postscript   Font   name   with   a   leading   slash,   as   in
  2315.       `/MunhwaGothic-Regular'.
  2316.  
  2317.     - FreeType  2 should now  compile fine  on AIX  4.3.3 as  a shared
  2318.       library.
  2319.  
  2320.     - A  bug  in the  Postscript  hinter  has  been found  and  fixed,
  2321.       removing un-even stem widths at small pixel sizes (like 14-17).
  2322.  
  2323.       This  improves the  quality of  a certain  number  of Postscript
  2324.       fonts.
  2325.  
  2326.  
  2327.   II. NEW FEATURES
  2328.  
  2329.     - A  new function  named  `FT_Library_Version' has  been added  to
  2330.       return  the current  library's major,  minor, and  patch version
  2331.       numbers.   This is  important since  the  macros FREETYPE_MAJOR,
  2332.       FREETYPE_MINOR,  and  FREETYPE_PATCH  cannot  be used  when  the
  2333.       library is dynamically linked by a program.
  2334.  
  2335.     - Two   new  APIs   have  been   added:   `FT_Get_First_Char'  and
  2336.       `FT_Get_Next_Char'.
  2337.  
  2338.       Together,  these can  be used  to iterate  efficiently  over the
  2339.       currently  selected  charmap of  a  given  face.   Read the  API
  2340.       reference for more details.
  2341.  
  2342.  
  2343.   III. MISCELLANEOUS
  2344.  
  2345.     - The FreeType sources are  under heavy internal re-factoring.  As
  2346.       a consequence,  we have created  a branch named `STABLE'  on the
  2347.       CVS to hold all future releases/fixes in the 2.0.x family.
  2348.  
  2349.       The  HEAD  branch  now  contains  the  re-factored  sources  and
  2350.       shouldn't  be used for  testing or  packaging new  releases.  In
  2351.       case you  would like  to access the  2.0.9 sources from  our CVS
  2352.       repository, use the tag `VER-2-0-9'.
  2353.  
  2354.  
  2355. ======================================================================
  2356.  
  2357. CHANGES BETWEEN 2.0.8 and 2.0.7
  2358.  
  2359.   I. IMPORTANT BUG FIXES
  2360.  
  2361.     - There was  a small but  nasty bug in  `freetype-config.in' which
  2362.       caused the `freetype-config' script to fail on Unix.
  2363.  
  2364.       This didn't prevent the installation  of the library or even its
  2365.       execution, but caused problems  when trying to compile many Unix
  2366.       packages that depend on it.
  2367.  
  2368.     - Some TrueType or OpenType fonts embedded in PDF documents do not
  2369.       have  a  'cmap',  'post'  and  'name'  as  is  required  by  the
  2370.       specification.  FreeType no longer refuses to load such fonts.
  2371.  
  2372.     - Various fixes to the PCF font driver.
  2373.  
  2374.  
  2375. ======================================================================
  2376.  
  2377. CHANGES BETWEEN 2.0.7 and 2.0.6
  2378.  
  2379.   I. IMPORTANT BUG FIXES
  2380.  
  2381.     - Fixed  two  bugs in  the  Type 1  font  driver.   The first  one
  2382.       resulted in a memory leak in subtle cases.  The other one caused
  2383.       FreeType to crash when  trying to load `.gsf' files (Ghostscript
  2384.       so-called Postscript fonts).
  2385.  
  2386.       (This  made _many_  KDE applications  crash on  certain systems.
  2387.        FreeType _is_ becoming a critical system component on Linux :-)
  2388.  
  2389.     - Fixed a memory leak in the CFF font driver.
  2390.  
  2391.     - Fixed a memory leak in the PCF font driver.
  2392.  
  2393.     - Fixed       the        Visual       C++       project       file
  2394.       `builds/win32/visualc/freetype.dsp' since  it didn't include the
  2395.       Postscript hinter component, causing errors at build time.
  2396.  
  2397.     - Fixed a  small rendering bug  in the anti-aliased  renderer that
  2398.       only  occurred when  trying to  draw  thin (less  than 1  pixel)
  2399.       strokes.
  2400.  
  2401.     - Fixed  `builds/unix/freetype2.a4' which  is used  to  generate a
  2402.       valid `freetype2.m4' for use with autoconf.
  2403.  
  2404.     - Fixed the OpenVMS Makefiles.
  2405.  
  2406.  
  2407.   II. MISCELLANEOUS
  2408.  
  2409.     - Added  `configure'  and   `install'  scripts  to  the  top-level
  2410.       directory.  A GNU-style installation is thus now easily possible
  2411.       with
  2412.  
  2413.         ./configure  <options>
  2414.         make
  2415.         make install
  2416.  
  2417.  
  2418. ======================================================================
  2419.  
  2420. CHANGES BETWEEN 2.0.6 and 2.0.5
  2421.  
  2422.   I. IMPORTANT BUG FIXES
  2423.  
  2424.     - It wasn't possible to load embedded bitmaps when the auto-hinter
  2425.       was used.  This is now fixed.
  2426.  
  2427.     - The TrueType  font driver  didn't load some  composites properly
  2428.       (the  sub-glyphs  were  slightly  shifted,  and  this  was  only
  2429.       noticeable when using monochrome rendering).
  2430.  
  2431.     - Various  fixes  to the  auto-hinter.   They  merely improve  the
  2432.       output of sans-serif fonts.   Note that there are still problems
  2433.       with serifed fonts and composites (accented characters).
  2434.  
  2435.     - All scalable  font drivers erroneously  returned un-fitted glyph
  2436.       advances when hinting was  requested.  This created problems for
  2437.       a number  of layout applications.  This  is a very  old bug that
  2438.       got  undetected mainly  because most  test/demo  program perform
  2439.       rounding explicitly or implicitly (through the cache).
  2440.  
  2441.     - `FT_Glyph_To_Bitmap' did erroneously  modify the source glyph in
  2442.       certain cases.
  2443.  
  2444.     - `glnames.py'  still contained  a bug  that made  FreeType return
  2445.       invalid names for certain glyphs.
  2446.  
  2447.     - The  library crashed  when  loading certain  Type  1 fonts  like
  2448.       `sadn.pfb'  (`Stalingrad  Normal'),   which  appear  to  contain
  2449.       pathetic font info dictionaries.
  2450.  
  2451.     - The TrueType glyph  loader is now much more  paranoid and checks
  2452.       everything when loading a given glyph image.  This was necessary
  2453.       to avoid problems (crashes and/or memory overwrites) with broken
  2454.       fonts that came from a really buggy automatic font converter.
  2455.  
  2456.  
  2457.   II. IMPORTANT UPDATES AND NEW FEATURES
  2458.  
  2459.     - Important updates to the Mac-specific parts of the library.
  2460.  
  2461.     - The caching sub-system has  been completely re-designed, and its
  2462.       API has  evolved (the  old one is  still supported  for backward
  2463.       compatibility).
  2464.  
  2465.       The documentation for it is  not yet completed, sorry.  For now,
  2466.       you are encouraged to continue  using the old API.  However, the
  2467.       ftview  demo program in  the ft2demos  package has  already been
  2468.       updated to use the new caching functions.
  2469.  
  2470.     - A new charmap cache is provided too.  See `FTC_CMapCache'.  This
  2471.       is useful to perform  character code -> glyph index translations
  2472.       quickly, without the need for an opened FT_Face.
  2473.  
  2474.     - A NEW POSTSCRIPT HINTER module  has been added to support native
  2475.       hints in  the following  formats: PostScript Type  1, PostScript
  2476.       CID, and CFF/CEF.
  2477.  
  2478.       Please test!  Note that  the auto-hinter produces better results
  2479.       for a number of  badly-hinted fonts (mostly auto-generated ones)
  2480.       though.
  2481.  
  2482.     - A memory debugger is now  part of the standard FreeType sources.
  2483.       To      enable      it,      define      FT_DEBUG_MEMORY      in
  2484.       <freetype/config/ftoption.h>, and recompile the library.
  2485.  
  2486.       Additionally, define  the _environment_ variable FT_DEBUG_MEMORY
  2487.       and run any program using FreeType.  When the library is exited,
  2488.       a  summary  of memory  footprints  and  possible  leaks will  be
  2489.       displayed.
  2490.  
  2491.       This works transparently with  _any_ program that uses FreeType.
  2492.       However, you  will need a lot  of memory to  use this (allocated
  2493.       blocks are never  released to the heap to  detect double deletes
  2494.       easily).
  2495.  
  2496.  
  2497.   III. MISCELLANEOUS
  2498.  
  2499.     - We  are  aware  of  subtle  differences between  the  output  of
  2500.       FreeType  versions   1  and  2  when  it   comes  to  monochrome
  2501.       TrueType-hinted glyphs.   These are  most probably due  to small
  2502.       differences in the monochrome rasterizers and will be worked out
  2503.       in an upcoming release.
  2504.  
  2505.     - We have decided to fork the sources in a `stable' branch, and an
  2506.       `unstable' one, since FreeType  is becoming a critical component
  2507.       of many Unix systems.
  2508.  
  2509.       The next  bug-fix releases of  the library will be  named 2.0.7,
  2510.       2.0.8, etc.,  while the `2.1'  branch will contain a  version of
  2511.       the sources where we will start major reworking of the library's
  2512.       internals, in order to produce FreeType 2.2.0 (or even 3.0) in a
  2513.       more distant future.
  2514.  
  2515.       We  also hope  that this  scheme will  allow much  more frequent
  2516.       releases than in the past.
  2517.  
  2518.  
  2519. ======================================================================
  2520.  
  2521. CHANGES BETWEEN 2.0.5 and 2.0.4
  2522.  
  2523.   NOTE THAT 2.0.5 DOES NOT CONTAIN THE POSTSCRIPT HINTER.  THIS MODULE
  2524.   WILL BE PART OF THE NEXT RELEASE (EITHER 2.0.6 or 2.1)
  2525.  
  2526.   - Fixed a bug that made  certain glyphs, like `Cacute', `cacute' and
  2527.     `lslash'  unavailable from Unicode  charmaps of  Postscript fonts.
  2528.     This prevented the correct display of Polish text, for example.
  2529.  
  2530.   - The kerning table of Type 1 fonts was loaded by FreeType, when its
  2531.     AFM    file    was    attached    to    its    face,    but    the
  2532.     FT_FACE_FLAG_HAS_KERNING   bit  flags   was  not   set  correctly,
  2533.     preventing FT_Get_Kerning to return meaningful values.
  2534.  
  2535.   - Improved  SFNT (TrueType  & OpenType)  charmap  support.  Slightly
  2536.     better performance, as well as support for the new formats defined
  2537.     by the OpenType 1.3 specification (8, 10, and 12)
  2538.  
  2539.   - Fixed a  serious typo in `src/base/ftcalc.c'  which caused invalid
  2540.     computations in certain rare cases, producing ugly artefacts.
  2541.  
  2542.   - The  size  of the  EM  square is  computed  with  a more  accurate
  2543.     algorithm for Postscript fonts.   The old one caused slight errors
  2544.     with embedded fonts found in PDF documents.
  2545.  
  2546.   - Fixed  a  bug in  the  cache  manager  that prevented  normal  LRU
  2547.     behaviour  within the cache  manager, causing  unnecessary reloads
  2548.     (for FT_Face and FT_Size objects only).
  2549.  
  2550.   - Added  a new  function named  `FT_Get_Name_Index' to  retrieve the
  2551.     glyph index of a given glyph name, when found in a face.
  2552.  
  2553.   - Added  a new function  named `FT_Get_Postscript_Name'  to retrieve
  2554.     the `unique' Postscript font name of a given face.
  2555.  
  2556.   - Added   a   new   public   header  size   named   FT_SIZES_H   (or
  2557.     <freetype/ftsizes.h>) providing  new FT_Size-management functions:
  2558.     FT_New_Size, FT_Activate_Size, FT_Done_Size.
  2559.  
  2560.   - Fixed a  reallocation bug that  generated a dangling  pointer (and
  2561.     possibly    memory    leaks)    with    Postscript    fonts    (in
  2562.     src/psaux/psobjs.c).
  2563.  
  2564.   - Many fixes for 16-bit correctness.
  2565.  
  2566.   - Removed many pedantic compiler warnings from the sources.
  2567.  
  2568.   - Added an Amiga build directory in `builds/amiga'.
  2569.  
  2570.  
  2571. ======================================================================
  2572.  
  2573. CHANGES BETWEEN 2.0.4 and 2.0.3
  2574.  
  2575.   - Fixed a rather annoying bug that was introduced in 2.0.3.  Namely,
  2576.     the font  transformation set through  FT_Set_Transform was applied
  2577.     twice to auto-hinted glyphs, resulting in incorrectly rotated text
  2578.     output.
  2579.  
  2580.   - Fixed _many_  compiler warnings.   FT2 should now  compile cleanly
  2581.     with Visual  C++'s most pedantic warning level  (/W4).  It already
  2582.     compiled fine with GCC and a few other compilers.
  2583.  
  2584.   - Fixed a bug  that prevented the linear advance  width of composite
  2585.     TrueType glyphs to be correctly returned.
  2586.  
  2587.   - Fixed    the    Visual    C++    project    files    located    in
  2588.     `builds/win32/visualc' (previous versions  used older names of the
  2589.     library).
  2590.  
  2591.   - Many  32-bit constants  have an  `L' appended  to their  value, in
  2592.     order to improve the 16-bitness  of the code.  Someone is actually
  2593.     trying to use FT2 on an Atari ST machine!
  2594.  
  2595.   - Updated  the  `builds/detect.mk' file  in  order to  automatically
  2596.     build FT2  on AIX systems.   AIX uses `/usr/sbin/init'  instead of
  2597.     `/sbin/init' and wasn't previously  detected as a Unix platform by
  2598.     the FreeType build system.
  2599.  
  2600.   - Updated  the  Unix-specific  portions  of the  build  system  (new
  2601.     libtool version, etc.).
  2602.  
  2603.   - The  SFNT kerning  loader now  ensures  that the  table is  sorted
  2604.     (since some problem fonts do not meet this requirement).
  2605.  
  2606.  
  2607. =======================================================================
  2608.  
  2609. CHANGES BETWEEN 2.0.3 and 2.0.2
  2610.  
  2611.   I. CHANGES TO THE MODULES / FONT DRIVERS
  2612.  
  2613.     - THE  AUTO-HINTER HAS  BEEN SLIGHTLY  IMPROVED, in  order  to fix
  2614.       several annoying artefacts, mainly:
  2615.  
  2616.         - Blue  zone alignment  of  horizontal stems  wasn't performed
  2617.           correctly, resulting in artefacts  like the `d' being placed
  2618.           one pixel below the `b' in some fonts like Time New Roman.
  2619.  
  2620.         - Overshoot thresholding  wasn't performed correctly, creating
  2621.           unpleasant artefacts at large character pixel sizes.
  2622.  
  2623.         - Composite glyph loading has  been simplified.  This gets rid
  2624.           of  various artefacts  where the  components of  a composite
  2625.           glyphs were not correctly spaced.
  2626.  
  2627.       These are  the last changes to the  current auto-hinting module.
  2628.       A new  hinting sub-system is currently  in the work  in order to
  2629.       support native hints  in Type 1 / CFF /  OpenType fonts, as well
  2630.       as globally improve rendering.
  2631.  
  2632.     - The  PCF  driver has  been  fixed.   It  reported invalid  glyph
  2633.       dimensions for the fonts available on Solaris.
  2634.  
  2635.     - The Type  1, CID and CFF  drivers have been modified  to fix the
  2636.       computation of the EM size.
  2637.  
  2638.     - The Type 1  driver has been fixed to avoid  a dangerous bug that
  2639.       crashed the library with non-conforming fonts (i.e. ones that do
  2640.       not place the .notdef glyph at position 0).
  2641.  
  2642.     - The TrueType  driver had a  rather subtle bug  (dangling pointer
  2643.       when loading  composite glyphs) that could crash  the library in
  2644.       rare occasions!
  2645.  
  2646.  
  2647.   II. HIGH-LEVEL API CHANGES
  2648.  
  2649.     - The error  code enumeration values have been  changed.  An error
  2650.       value  is decomposed  in  a  generic error  code,  and a  module
  2651.       number.  see <freetype/fterrors.h> for details.
  2652.  
  2653.     - A   new  public   header   file  has   been  introduced,   named
  2654.       FT_TRIGONOMETRY_H    (include/freetype/fttrigon.h),    providing
  2655.       trigonometric functions to  compute sines, cosines, arctangents,
  2656.       etc. with 16.16 fixed precision.  The implementation is based on
  2657.       the CORDIC  algorithm and is very fast  while being sufficiently
  2658.       accurate.
  2659.  
  2660.  
  2661.   III. INTERNALS
  2662.  
  2663.     - Added  BeOS-specific files  in the  old build  sub-system.  Note
  2664.       that no changes were required to compile the library with Jam.
  2665.  
  2666.     - The  configuration  is now  capable  of automatically  detecting
  2667.       64-bit integers  on a set  of predefined compilers  (GCC, Visual
  2668.       C++, Borland C++) and will use them by default.  This provides a
  2669.       small performance boost.
  2670.  
  2671.     - A  small memory leak  that happened  when opening  0-sized files
  2672.       (duh!)  have been fixed.
  2673.  
  2674.     - Fixed bezier  stack depth  bug in the  routines provided  by the
  2675.       FT_BBOX_H  header   file.   Also  fixed  similar   bugs  in  the
  2676.       rasterizers.
  2677.  
  2678.     - The outline bounding  box code has been rewritten  to use direct
  2679.       computations,  instead of  bezier sub-division,  to  compute the
  2680.       exact bounding box of glyphs.   This is slightly slower but more
  2681.       accurate.
  2682.  
  2683.     - The build system has been  improved and fixed, mainly to support
  2684.       `make'  on Windows  2000  correctly, avoid  problems with  `make
  2685.       distclean' on non Unix systems, etc.
  2686.  
  2687.     - Hexadecimal  constants  have been  suffixed  with  `U' to  avoid
  2688.       problems with certain compilers on 64-bit platforms.
  2689.  
  2690.     - A new directory named `src/tools' has been created.  It contains
  2691.       Python scripts and simple unit test programs used to develop the
  2692.       library.
  2693.  
  2694.     - The DocMaker tool has been  moved from `docs' to `src/tools' and
  2695.       has been updated with the following:
  2696.  
  2697.          - Now accepts the `--title=XXXX' or `-t XXXX' option from the
  2698.            command line to set the project's name in the generated API
  2699.            reference.
  2700.  
  2701.          - Now accepts the `--output=DIR'  or `-o DIR' option from the
  2702.            command line to set  the output directory for all generated
  2703.            HTML files.
  2704.  
  2705.          - Now accepts the `--prefix=XXXX' or `-p XXX' option from the
  2706.            command  line  to  set  the  file prefix  to  use  for  all
  2707.            generated HTML files.
  2708.  
  2709.          - Now generates the current  time/data on each generated page
  2710.            in order to distinguish between versions.
  2711.  
  2712.       DocMaker  can be  used with  other  projects now,  not only  FT2
  2713.       (e.g. MLib, FTLayout, etc.).
  2714.  
  2715.  
  2716. ======================================================================
  2717.  
  2718. CHANGES BETWEEN 2.0.2 and 2.0.1
  2719.  
  2720.   I. CHANGES TO THE MODULES / FONT DRIVERS
  2721.  
  2722.     - THE TRUETYPE BYTECODE INTERPRETER IS NOW TURNED OFF, in order to
  2723.       avoid legal problems  with the Apple patents.  It  seems that we
  2724.       mistakenly  turned this option  on in  previous releases  of the
  2725.       build.
  2726.  
  2727.       Note that if  you want to use the  bytecode interpreter in order
  2728.       to get high-quality TrueType  rendering, you will need to toggle
  2729.       by        hand        the        definition        of        the
  2730.       TT_CONFIG_OPTION_BYTECODE_INTERPRETER   macro    in   the   file
  2731.       `include/freetype/config/ftoption.h'.
  2732.  
  2733.     - The CFF driver has been improved by Tom Kacvinsky and Sander van
  2734.       der Wal:
  2735.  
  2736.       * Support for `seac' emulation.
  2737.       * Support for `dotsection'.
  2738.       * Support for retrieving glyph names through
  2739.         `FT_Get_Glyph_Name'.
  2740.  
  2741.       The first two items are necessary to correctly a large number of
  2742.       Type 1 fonts converted to the CFF formats by Adobe Acrobat.
  2743.  
  2744.     - The Type 1 driver was also improved by Tom & others:
  2745.  
  2746.       * Better EM size computation.
  2747.       * Better support for synthetic (transformed) fonts.
  2748.       * The  Type 1  driver returns  the charstrings  corresponding to
  2749.         each glyph in the  `glyph->control_data' field after a call to
  2750.         `FT_Load_Glyph' (thanks Ha Shao).
  2751.  
  2752.     - Various other bugfixes, including the following:
  2753.  
  2754.       * Fixed a nasty memory leak in the Type 1 driver.
  2755.       * The autohinter  and the pcf  driver used static  writable data
  2756.         when they shouldn't.
  2757.       * Many casts were added to  make the code more 64-bits safe.  It
  2758.         also now compiles on Windows XP 64-bits without warnings.
  2759.       * Some incorrect writable statics were removed in the `autohint'
  2760.         and `pcf' drivers.  FreeType 2 now compiles on Epoc again.
  2761.  
  2762.  
  2763.   II. CHANGES TO THE HIGH-LEVEL API
  2764.  
  2765.     - The library header files inclusion scheme has been changed.  The
  2766.       old scheme looked like:
  2767.  
  2768.         #include <freetype/freetype.h>
  2769.         #include <freetype/ftglyph.h>
  2770.         #include <freetype/ftcache.h>
  2771.         #include <freetype/cache/ftimage.h>
  2772.  
  2773.       Now you should use:
  2774.  
  2775.         #include <ft2build.h>
  2776.         #include FT_FREETYPE_H
  2777.         #include FT_GLYPH_H
  2778.         #include FT_CACHE_H
  2779.         #include FT_CACHE_IMAGE_H
  2780.  
  2781.       NOTE THAT  THE OLD  INCLUSION SCHEME WILL  STILL WORK  WITH THIS
  2782.       RELEASE.  HOWEVER, WE  DO NOT GUARANTEE THAT THIS  WILL STILL BE
  2783.       TRUE IN THE NEXT ONE (A.K.A. FREETYPE 2.1).
  2784.  
  2785.       The  file <ft2build.h>  is used  to define  the  header filename
  2786.       macros.  The complete and  commented list of macros is available
  2787.       in the API reference under the section name `Header File Macros'
  2788.       in Chapter I.
  2789.  
  2790.       For more information, see section I of the following document:
  2791.  
  2792.         http://www.freetype.org/
  2793.           freetype2/docs/tutorial/step1.html
  2794.  
  2795.       or
  2796.  
  2797.         http://freetype.sourceforge.net/
  2798.           freetype2/docs/tutorial/step1.html
  2799.  
  2800.     - Many, many comments have been added to the public source file in
  2801.       order to  automatically generate  the API Reference  through the
  2802.       `docmaker.py' Python script.
  2803.  
  2804.       The latter has been updated  to support the grouping of sections
  2805.       in chapters and better index sort.  See:
  2806.  
  2807.         http://www.freetype.org/freetype2/docs/reference/ft2-toc.html
  2808.  
  2809.  
  2810.   III. CHANGES TO THE BUILD PROCESS
  2811.  
  2812.     - If you  are not  building FreeType 2  with its own  build system
  2813.       (but with your own Makefiles or project files), you will need to
  2814.       be  aware that  the  build  process has  changed  a little  bit.
  2815.  
  2816.       You don't  need to put the  `src' directory in  the include path
  2817.       when  compiling  any FT2  component.   Instead,  simply put  the
  2818.       component's directory in the current include path.
  2819.  
  2820.       So, if you were doing something like:
  2821.  
  2822.         cc -c -Iinclude -Isrc src/base/ftbase.c
  2823.  
  2824.       change the line to:
  2825.  
  2826.         cc -c -Iinclude -Isrc/base src/base/ftbase.c
  2827.  
  2828.       If you were doing something like:
  2829.  
  2830.         cd src/base
  2831.         cc -c -I../../include -I.. ftbase.c
  2832.  
  2833.       change it to:
  2834.  
  2835.         cd src/base
  2836.         cc -c -I../../include ftbase.c
  2837.  
  2838.  
  2839. ======================================================================
  2840.  
  2841. CHANGES BETWEEN 2.0.1 and 2.0
  2842.  
  2843.   2.0.1 introduces a few changes:
  2844.  
  2845.     - Fixed many bugs related to  the support of CFF / OpenType fonts.
  2846.       These  formats are  now much  better supported  though  there is
  2847.       still work planned to  deal with charset tables and PDF-embedded
  2848.       CFF files that use the old `seac' command.
  2849.  
  2850.     - The  library could not  be compiled  in debug  mode with  a very
  2851.       small  number   of  C  compilers   whose  pre-processors  didn't
  2852.       implement the `##'  directive correctly (i.e. per se  the ANSI C
  2853.       specification!)  An elegant fix was found.
  2854.  
  2855.     - Added  support for  the  free Borland  command-line C++  Builder
  2856.       compiler.   Use `make  setup bcc32'.   Also fixed  a  few source
  2857.       lines that generated new warnings with BCC32.
  2858.  
  2859.     - Fixed a bug in FT_Outline_Get_BBox when computing the extrema of
  2860.       a conic Bezier arc.
  2861.  
  2862.     - Updated the INSTALL file to add IDE compilation.
  2863.  
  2864.     - Other  minor bug  fixes,  from  invalid Type  1  style flags  to
  2865.       correct   support   of  synthetic   (obliqued)   fonts  in   the
  2866.       auto-hinter, better support for embedded bitmaps in a SFNT font.
  2867.  
  2868.     - Fixed some problems with `freetype-config'.
  2869.  
  2870.   Finally, the `standard' scheme for including FreeType headers is now
  2871.   gradually changing,  but this will  be explained in a  later release
  2872.   (probably 2.0.2).
  2873.  
  2874.   And very  special thanks to Tom Kacvinsky  and YAMANO-UCHI Hidetoshi
  2875.   for their contributions!
  2876.  
  2877.  
  2878. ======================================================================
  2879.  
  2880. CHANGES BETWEEN beta8 and 2.0
  2881.  
  2882.   - Changed  the default  installation  path for  public headers  from
  2883.     `include/freetype' to `include/freetype2'.
  2884.  
  2885.     Also added a new `freetype-config' that is automatically generated
  2886.     and installed  on Unix and  Cygwin systems.  The script  itself is
  2887.     used to retrieve the current  install path, C compilation flags as
  2888.     well as linker flags.
  2889.  
  2890.   - Fixed several small bugs:
  2891.  
  2892.     * Incorrect max advance width for fixed-pitch Type 1 fonts.
  2893.     * Incorrect glyph names for certain TrueType fonts.
  2894.     * The  glyph advance  was not  copied when  FT_Glyph_To_Bitmap was
  2895.       called.
  2896.     * The  linearHoriAdvance  and  linearVertAdvance  fields  were not
  2897.       correctly returned for glyphs processed by the auto-hinter.
  2898.     * `type1z'  renamed back to  `type1'; the  old `type1'  module has
  2899.       been removed.
  2900.  
  2901.   - Revamped the  build system  to make it  a lot more  generic.  This
  2902.     will  allow us  to  re-use  nearly un-modified  in  lots of  other
  2903.     projects (including FreeType Layout).
  2904.  
  2905.   - Changed `cid' to use `psaux' too.
  2906.  
  2907.   - Added the  cache sub-system.  See <freetype/ftcache.h>  as well as
  2908.     the sources  in `src/cache'.  Note  that it compiles but  is still
  2909.     untested for now.
  2910.  
  2911.   - Updated `docs/docmaker.py', a draft  API reference is available at
  2912.     http://www.freetype.org/ft2api.html.
  2913.  
  2914.   - Changed `type1' to use `psaux'.
  2915.  
  2916.   - Created a  new module named  `psaux' to hold  the Type 1 &  Type 2
  2917.     parsing routines.  It should be  used by `type1', `cid', and `cff'
  2918.     in the future.
  2919.  
  2920.   - Fixed an important bug in `FT_Glyph_Get_CBox'.
  2921.  
  2922.   - Fixed  some compiler  warnings  that happened  since the  TrueType
  2923.     bytecode decoder was deactivated by default.
  2924.  
  2925.   - Fixed two memory leaks:
  2926.  
  2927.     * The    memory   manager   (16    bytes)   isn't    released   in
  2928.       FT_Done_FreeType!
  2929.     * Using custom input streams, the  copy of the original stream was
  2930.       never released.
  2931.  
  2932.   - Fixed the  auto-hinter by performing automatic  computation of the
  2933.     `filling direction' of each glyph.   This is done through a simple
  2934.     and  fast approximation, and  seems to  work (problems  spotted by
  2935.     Werner though).  The Arphic fonts are a lot nicer though there are
  2936.     still a lot of things to do to handle Asian fonts correctly.
  2937.  
  2938.  
  2939. ======================================================================
  2940.  
  2941. BETA-8 (RELEASE CANDIDATE) CHANGES
  2942.  
  2943.   - Deactivated the TrueType bytecode interpreter by default.
  2944.  
  2945.   - Deactivated the `src/type1' font driver.  Now `src/type1z' is used
  2946.     by default.
  2947.  
  2948.   - Updates to the build system.  We now compile the library correctly
  2949.     under  Unix  system  through  `configure' which  is  automatically
  2950.     called on the first `make' invocation.
  2951.  
  2952.   - Added the auto-hinting module!  Fixing some bugs here and there.
  2953.  
  2954.   - Found some bugs in the  composite loader (seac) of the Type1-based
  2955.     font drivers.
  2956.  
  2957.   - Renamed the directory `freetype2/config' to `freetype2/builds' and
  2958.     updated all relevant files.
  2959.  
  2960.   - Found a memory leak in the `type1' driver.
  2961.  
  2962.   - Incorporated Tom's patches to  support flex operators correctly in
  2963.     OpenType/CFF fonts.  Now all I need is to support pure CFF and CEF
  2964.     fonts to be done with this driver :-)
  2965.  
  2966.   - Added the  Windows FNT/FON driver in `src/winfonts'.   For now, it
  2967.     always  `simulates'   a  Unicode  charmap,  so   it  shouldn't  be
  2968.     considered completed right now.
  2969.  
  2970.     It  is there  to be  more a  proof of  concept than  anything else
  2971.     anyway.  The driver is a single  C source file, that compiles to 3
  2972.     Kb of code.
  2973.  
  2974.     I'm  still working on  the PCF/BDF  drivers, but  I'm too  lazy to
  2975.     finish them now.
  2976.  
  2977.   - CHANGES TO THE HIGH-LEVEL API
  2978.  
  2979.     * FT_Get_Kerning has a new parameter that allows you to select the
  2980.       coordinates of the kerning  vector (font units, scaled, scaled +
  2981.       grid-fitted).
  2982.     * The  outline functions are  now in <freetype/ftoutln.h>  and not
  2983.       part of <freetype/freetype.h> anymore.
  2984.     * <freetype/ftmodule.h>    now     contains    declarations    for
  2985.        FT_New_Library, FT_Done_Library, FT_Add_Default_Modules.
  2986.     * The so-called convenience  functions have moved from `ftoutln.c'
  2987.       to  `ftglyph.c',  and  are  thus available  with  this  optional
  2988.       component    of   the   library.     They   are    declared   in
  2989.       <freetype/ftglyph.h> now.
  2990.     * Anti-aliased  rendering is now  the default  for FT_Render_Glyph
  2991.       (i.e. corresponds to render_mode == 0 == ft_render_mode_normal).
  2992.       To generate a monochrome bitmap, use ft_render_mode_mono, or the
  2993.       FT_LOAD_MONOCHROME     flag    in    FT_Load_Glyph/FT_Load_Char.
  2994.       FT_LOAD_ANTI_ALIAS is still defined, but values to 0.
  2995.     * <freetype/freetype.h>  now include <freetype/config/ftconfig.h>,
  2996.       solving a few headaches :-)
  2997.     * The type FT_GlyphSlotRec has now a `library' field.
  2998.  
  2999.   - CHANGES TO THE `ftglyph.h' API
  3000.  
  3001.     This API has  been severely modified in order  to make it simpler,
  3002.     clearer, and more  efficient.  It certainly now looks  like a real
  3003.     `glyph factory'  object, and allows client  applications to manage
  3004.     (i.e.  transform,  bbox  and  render) glyph  images  without  ever
  3005.     knowing their original format.
  3006.  
  3007.   - Added  support  for CID-keyed  fonts  to  the  CFF driver.   Maybe
  3008.     support for pure CFF + CEF fonts should come in?
  3009.  
  3010.   - Cleaned up  source code in order  to avoid two  functions with the
  3011.     same name.  Also  changed the names of the  files in `type1z' from
  3012.     `t1XXXX' to `z1XXXX' in order to avoid any conflicts.
  3013.  
  3014.     `make multi' now works well :-)
  3015.  
  3016.     Also removed the use of `cidafm' for now, even if the source files
  3017.     are  still there.  This  functionality will  certainly  go into  a
  3018.     specific module.
  3019.  
  3020.   - ADDED SUPPORT FOR THE AUTO-HINTER
  3021.  
  3022.     It  works :-) I  have a  demo program  which simply  is a  copy of
  3023.     `ftview'       that      does       a      `FT_Add_Module(library,
  3024.     &autohinter_module_class)' after  library initialization, and Type
  3025.     1 & OpenType/CFF fonts are now hinted.
  3026.  
  3027.     CID  fonts are  not hinted,  as they  include no  charmap  and the
  3028.     auto-hinter doesn't include  `generic' global metrics computations
  3029.     yet.
  3030.  
  3031.     Now, I need to release this thing to the FreeType 2 source.
  3032.  
  3033.   - CHANGES TO THE RENDERER MODULES
  3034.  
  3035.     The  monochrome  and smooth  renderers  are  now  in two  distinct
  3036.     directories, namely `src/raster1' and `src/smooth'.  Note that the
  3037.     old `src/renderer' is now gone.
  3038.  
  3039.     I ditched  the 5-gray-levels renderers.  Basically,  it involved a
  3040.     simple #define toggle in 'src/raster1/ftraster.c'.
  3041.  
  3042.     FT_Render_Glyph,  FT_Outline_Render  &  FT_Outline_Get_Bitmap  now
  3043.     select the best renderer  available, depending on render mode.  If
  3044.     the current renderer for a  given glyph image format isn't capable
  3045.     of supporting  the render mode, another  one will be  found in the
  3046.     library's list.   This means that client applications  do not need
  3047.     to  switch or  set  the  renderers themselves  (as  in the  latest
  3048.     change), they'll get what they want automatically.  At last.
  3049.  
  3050.     Changed the demo programs accordingly.
  3051.  
  3052.   - MAJOR INTERNAL REDESIGN:
  3053.  
  3054.     A lot of internal modifications  have been performed lately on the
  3055.     source in order to provide the following enhancements:
  3056.  
  3057.     * More generic module support:
  3058.  
  3059.       The FT_Module  type is  now defined to  represent a handle  to a
  3060.       given  module.   The  file  <freetype/ftmodule.h>  contains  the
  3061.       FT_Module_Class definition, as well as the module-loading public
  3062.       API.
  3063.  
  3064.       The  FT_Driver type  is still  defined, and  still  represents a
  3065.       pointer to  a font driver.  Note that  FT_Add_Driver is replaced
  3066.       by FT_Add_Module, FT_Get_Driver by FT_Get_Module, etc.
  3067.  
  3068.     * Support for generic glyph image types:
  3069.  
  3070.       The FT_Renderer  type is a pointer  to a module  used to perform
  3071.       various operations on glyph image.
  3072.  
  3073.       Each renderer is  capable of handling images in  a single format
  3074.       (e.g. ft_glyph_format_outline).  Its functions are used to:
  3075.  
  3076.       - transform an glyph image
  3077.       - render a glyph image into a bitmap
  3078.       - return the control box (dimensions) of a given glyph image
  3079.  
  3080.       The scan converters `ftraster.c' and `ftgrays.c' have been moved
  3081.       to the new directory `src/renderer', and are used to provide two
  3082.       default renderer modules.
  3083.  
  3084.       One corresponds  to the `standard' scan-converter,  the other to
  3085.       the `smooth' one.
  3086.  
  3087.       he  current  renderer  can  be  set  through  the  new  function
  3088.       FT_Set_Renderer.
  3089.  
  3090.       The old raster-related function FT_Set_Raster, FT_Get_Raster and
  3091.       FT_Set_Raster_Mode have now disappeared, in favor of the new:
  3092.  
  3093.         FT_Get_Renderer
  3094.         FT_Set_Renderer
  3095.  
  3096.       See the file <freetype/ftrender.h> for more details.
  3097.  
  3098.       These  changes  were  necessary  to properly  support  different
  3099.       scalable formats in the future, like bi-color glyphs, etc.
  3100.  
  3101.     * Glyph loader object:
  3102.  
  3103.       A  new  internal  object,  called  a  'glyph  loader'  has  been
  3104.       introduced in the base layer.  It is used by all scalable format
  3105.       font drivers to load glyphs and composites.
  3106.  
  3107.       This object  has been  created to reduce  the code size  of each
  3108.       driver,  as  each  one  of  them  basically  re-implemented  its
  3109.       functionality.
  3110.  
  3111.       See <freetype/internal/ftobjs.h> and the FT_GlyphLoader type for
  3112.       more information.
  3113.  
  3114.     * FT_GlyphSlot has new fields:
  3115.  
  3116.       In  order   to  support  extended  features   (see  below),  the
  3117.       FT_GlyphSlot structure has a few new fields:
  3118.  
  3119.       linearHoriAdvance:
  3120.  
  3121.         This  field  gives  the   linearly  scaled  (i.e.  scaled  but
  3122.         unhinted) advance  width for the  glyph, expressed as  a 16.16
  3123.         fixed pixel value.  This is useful to perform WYSIWYG text.
  3124.  
  3125.       linearVertAdvance:
  3126.         This field  gives the linearly  scaled advance height  for the
  3127.         glyph  (relevant in  vertical  glyph layouts  only).  This  is
  3128.         useful to perform WYSIWYG text.
  3129.  
  3130.         Note that  the two above field replace  the removed `metrics2'
  3131.         field in the glyph slot.
  3132.  
  3133.       advance:
  3134.         This field is a vector  that gives the transformed advance for
  3135.         the glyph.   By default, it corresponds to  the advance width,
  3136.         unless  FT_LOAD_VERTICAL_LAYOUT  was  specified  when  calling
  3137.         FT_Load_Glyph or FT_Load_Char.
  3138.  
  3139.       bitmap_left:
  3140.         This  field gives  the  distance in  integer  pixels from  the
  3141.         current pen position  to the left-most pixel of  a glyph image
  3142.         IF IT IS  A BITMAP.  It is only valid  when the `format' field
  3143.         is set to `ft_glyph_format_bitmap', for example, after calling
  3144.         the new function FT_Render_Glyph.
  3145.  
  3146.       bitmap_top:
  3147.         This  field gives  the  distance in  integer  pixels from  the
  3148.         current pen position (located on the baseline) to the top-most
  3149.         pixel of the  glyph image IF IT IS  A BITMAP.  Positive values
  3150.         correspond to upwards Y.
  3151.  
  3152.       loader:
  3153.         This  is a  new  private  field for  the  glyph slot.   Client
  3154.         applications should not touch it.
  3155.  
  3156.  
  3157.     * Support for transforms and direct rendering in FT_Load_Glyph:
  3158.  
  3159.       Most of the functionality found in <freetype/ftglyph.h> has been
  3160.       moved to the core library.  Hence, the following:
  3161.  
  3162.       - A   transform   can   be   specified  for   a   face   through
  3163.         FT_Set_Transform.  this transform  is applied by FT_Load_Glyph
  3164.         to  scalable glyph  images (i.e.  NOT TO  BITMAPS)  before the
  3165.         function returns, unless the bit flag FT_LOAD_IGNORE_TRANSFORM
  3166.         was set in the load flags.
  3167.  
  3168.       - Once  a  glyph image  has  been  loaded,  it can  be  directly
  3169.         converted  to  a  bitmap  by  using  the  new  FT_Render_Glyph
  3170.         function.  Note that this  function takes the glyph image from
  3171.         the glyph slot,  and converts it to a  bitmap whose properties
  3172.         are returned  in `face.glyph.bitmap', `face.glyph.bitmap_left'
  3173.         and `face.glyph.bitmap_top'.  The  original native image might
  3174.         be lost after the conversion.
  3175.  
  3176.       - When using the new  bit flag FT_LOAD_RENDER, the FT_Load_Glyph
  3177.         and   FT_Load_Char   functions   will   call   FT_Render_Glyph
  3178.         automatically when needed.
  3179.  
  3180.   - Reformatted all  modules source  code in order  to get rid  of the
  3181.     basic data types redifinitions (i.e. `TT_Int' instead of `FT_Int',
  3182.     `T1_Fixed'  instead  of  `FT_Fixed').  Hence  the  format-specific
  3183.     prefixes like  `TT_', `T1_',  `T2_' and `CID_'  are only  used for
  3184.     relevant structures.
  3185.  
  3186.  
  3187. ======================================================================
  3188.  
  3189. OLD CHANGES FOR BETA 7
  3190.  
  3191.   - bug-fixed the  OpenType/CFF parser.  It  now loads and displays my
  3192.     two  fonts nicely,  but I'm  pretty certain  that more  testing is
  3193.     needed :-)
  3194.  
  3195.   - fixed the crummy Type 1 hinter, it now handles accented characters
  3196.     correctly (well, the accent is  not always well placed, but that's
  3197.     another problem..)
  3198.  
  3199.   - added the CID-keyed Type 1 driver in `src/cid'.  Works pretty well
  3200.     for only 13 Kb of code  ;-) Doesn't read AFM files though, nor the
  3201.     really useful CMAP files..
  3202.  
  3203.   - fixed  two  bugs  in  the  smooth  renderer  (src/base/ftgrays.c).
  3204.     Thanks to Boris Letocha for spotting them and providing a fix.
  3205.  
  3206.   - fixed potential `divide by zero' bugs in ftcalc.c.
  3207.  
  3208.   - added source  code for  the OpenType/CFF driver  (still incomplete
  3209.     though..)
  3210.  
  3211.   - modified the  SFNT driver slightly  to perform more  robust header
  3212.     checks  in TT_Load_SFNT_Header.  This prevents certain  font files
  3213.     (e.g.  some  Type  1  Multiple  Masters)  from  being  incorrectly
  3214.     `recognized' as TrueType font files..
  3215.  
  3216.   - moved a lot of stuff from  the TrueType driver to the SFNT module,
  3217.     this   allows   greater   code   re-use   between   font   drivers
  3218.     (e.g. TrueType, OpenType, Compact-TrueType, etc..)
  3219.  
  3220.   - added a tiny segment cache to the SFNT Charmap 4 decoder, in order
  3221.     to minimally speed it up..
  3222.  
  3223.   - added  support for  Multiple Master  fonts in  `type1z'.  There is
  3224.     also a new file named <freetype/ftmm.h> which defines functions to
  3225.     manage them from client applications.
  3226.  
  3227.     The new file `src/base/ftmm.c' is also optional to the engine..
  3228.  
  3229.   - various  formatting changes (e.g.  EXPORT_DEF ->  FT_EXPORT_DEF) +
  3230.     small bug fixes in FT_Load_Glyph, the `type1' driver, etc..
  3231.  
  3232.   - a minor fix to the Type 1 driver to let them apply the font matrix
  3233.     correctly (used for many oblique fonts..)
  3234.  
  3235.   - some fixes for 64-bit systems (mainly changing some FT_TRACE calls
  3236.     to use %p instead of %lx).  Thanks to Karl Robillard.
  3237.  
  3238.   - fixed  some bugs  in  the sbit  loader (src/base/sfnt/ttsbit.c)  +
  3239.     added  a new flag,  FT_LOAD_CROP_BITMAP to  query that  bitmaps be
  3240.     cropped when  loaded from a file  (maybe I should  move the bitmap
  3241.     cropper to the base layer ??).
  3242.  
  3243.   - changed the default  number of gray levels of  the smooth renderer
  3244.     to 256  (instead of  the previous 128).  Of course, the  human eye
  3245.     can't see any difference ;-)
  3246.  
  3247.   - removed TT_MAX_SUBGLYPHS,  there is no static limit  on the number
  3248.     of subglyphs in a TrueType font now..
  3249.  
  3250.  
  3251. ======================================================================
  3252.  
  3253. OLD CHANGES 16 May 2000
  3254.  
  3255.   - tagged `BETA-6'  in the  CVS tree.  This one is a  serious release
  3256.     candidate even though it doesn't incorporate the auto-hinter yet..
  3257.  
  3258.   - various obsolete files were removed, and copyright header updated
  3259.  
  3260.   - finally  updated  the  standard   raster  to  fix  the  monochrome
  3261.     rendering bug + re-enable  support for 5-gray levels anti-aliasing
  3262.     (suck, suck..)
  3263.  
  3264.   - created new header files, and modified sources accordingly:
  3265.  
  3266.      <freetype/fttypes.h>
  3267.        - simple FreeType types, without the API
  3268.      <freetype/internal/ftmemory.h>
  3269.        - definition of memory-management macros
  3270.  
  3271.   - added   the   `DSIG'   (OpenType   Digital   Signature)   tag   to
  3272.     <freetype/tttags.h>
  3273.  
  3274.   - light update/cleaning of the build system + changes to the sources
  3275.     in  order  to  get  rid  of _all_  compiler  warnings  with  three
  3276.     compilers, i.e:
  3277.  
  3278.     gcc with `-ansi -pedantic -Wall -W', Visual C++ with `/W3 /WX' and
  3279.     LCC
  3280.  
  3281.     IMPORTANT NOTE FOR WIN32-LCC USERS:
  3282.     |
  3283.     |  It seems the C pre-processor  that comes with LCC is broken, it
  3284.     |  doesn't  recognize  the  ANSI  standard  directives  #  and  ##
  3285.     |  correctly   when  one  of   the  argument  is  a  macro.  Also,
  3286.     |  something like:
  3287.     |
  3288.     |     #define F(x)  print##x
  3289.     |
  3290.     |     F(("hello"))
  3291.     |
  3292.     |  will get incorrectly translated to:
  3293.     |
  3294.     |     print "hello")
  3295.     |
  3296.     |  by its pre-processor.  For this reason, you simply cannot build
  3297.     |  FreeType 2 in debug mode with this compiler..
  3298.  
  3299.   - yet  another massive grunt work.  I've  changed the  definition of
  3300.     the EXPORT_DEF,  EXPORT_FUNC, BASE_DEF &  BASE_FUNC macros.  These
  3301.     now take an argument, which is the function's return value type.
  3302.  
  3303.     This  is necessary to  compile FreeType  as a  DLL on  Windows and
  3304.     OS/2.  Depending on the compiler used, a compiler-specific keyword
  3305.     like  __export or __system  must be  placed before  (VisualC++) or
  3306.     after (BorlandC++) the type..
  3307.  
  3308.     Of course, this needed a lot of changes throughout the source code
  3309.     to make it compile again...  All cleaned up now, apparently..
  3310.  
  3311.     Note also  that there is a  new EXPORT_VAR macro  defined to allow
  3312.     the   _declaration_    of   an   exportable    public   (constant)
  3313.     variable.  This  is  the   case  of  the  raster  interfaces  (see
  3314.     ftraster.h and ftgrays.h), as well as each module's interface (see
  3315.     sfdriver.h, psdriver.h, etc..)
  3316.  
  3317.   - new feature: it  is now possible to pass  extra parameters to font
  3318.                  drivers  when creating  a new  face object.  For now,
  3319.                  this capability is unused.  It could however prove to
  3320.                  be useful in a near future..
  3321.  
  3322.       the FT_Open_Args structure was  changes, as well as the internal
  3323.       driver interface  (the specific `init_face'  module function has
  3324.       now a different signature).
  3325.  
  3326.   - updated the tutorial (not finished though).
  3327.  
  3328.   - updated the top-level BUILD  document
  3329.  
  3330.   - fixed  a  potential memory  leak  that  could  occur when  loading
  3331.     embedded bitmaps.
  3332.  
  3333.   - added     the     declaration     of     FT_New_Memory_Face     in
  3334.     <freetype/freetype.h>, as  it was  missing from the  public header
  3335.     (the implementation was already in `ftobjs.c').
  3336.  
  3337.   - the file <freetype/fterrors.h> has been seriously updated in order
  3338.     to allow  the automatic generation  of error message tables.   See
  3339.     the comments within it for more information.
  3340.  
  3341.   - major directory  hierarchy re-organisation.  This was done for two
  3342.     things:
  3343.  
  3344.       * first,  to ease  the `manual'  compilation of  the  library by
  3345.         requiring at lot less include paths :-)
  3346.  
  3347.       * second,  to  allow  external  programs to  effectively  access
  3348.         internal  data  fields.  For example,  this  can be  extremely
  3349.         useful if  someone wants  to write a  font producer or  a font
  3350.         manager on top of FreeType.
  3351.  
  3352.     Basically, you  should now use  the 'freetype/' prefix  for header
  3353.     inclusion, as in:
  3354.  
  3355.         #include <freetype/freetype.h>
  3356.         #include <freetype/ftglyph.h>
  3357.  
  3358.     Some new include sub-directories are available:
  3359.  
  3360.      a. the  `freetype/config' directory,  contains two files  used to
  3361.         configure  the  build  of  the  library.  Client  applications
  3362.         should  not need  to look  at these  normally, but they can if
  3363.         they want.
  3364.  
  3365.         #include <freetype/config/ftoption.h>
  3366.         #include <freetype/config/ftconfig.h>
  3367.  
  3368.      b. the `freetype/internal'  directory, contains header files that
  3369.         describes library  internals.  These are the header files that
  3370.         were  previously  found  in  the `src/base'  and  `src/shared'
  3371.         directories.
  3372.  
  3373.  
  3374.     As  usual, the build  system and  the demos  have been  updated to
  3375.     reflect the change..
  3376.  
  3377.     Here's a layout of the new directory hierarchy:
  3378.  
  3379.     TOP_DIR
  3380.       include/
  3381.          freetype/
  3382.             freetype.h
  3383.             ...
  3384.             config/
  3385.               ftoption.h
  3386.               ftconfig.h
  3387.               ftmodule.h
  3388.  
  3389.             internal/
  3390.               ftobjs.h
  3391.               ftstream.h
  3392.               ftcalc.h
  3393.               ...
  3394.  
  3395.       src/
  3396.          base/
  3397.             ...
  3398.  
  3399.          sfnt/
  3400.          psnames/
  3401.          truetype/
  3402.          type1/
  3403.          type1z/
  3404.  
  3405.  
  3406.     Compiling a module is now  much easier, for example, the following
  3407.     should work when in the TOP_DIR directory on an ANSI build:
  3408.  
  3409.        gcc -c -I./include -I./src/base src/base/ftbase.c
  3410.        gcc -c -I./include -I./src/sfnt src/sfnt/sfnt.c
  3411.        etc..
  3412.  
  3413.     (of course, using -Iconfig/<system> if you provide system-specific
  3414.      configuration files).
  3415.  
  3416.   - updated the structure of FT_Outline_Funcs in order to allow direct
  3417.     coordinate scaling within  the outline decomposition routine (this
  3418.     is  important for virtual  `on' points  with TrueType  outlines) +
  3419.     updates to the rasters to support this..
  3420.  
  3421.   - updated  the OS/2  table  loading code  in `src/sfnt/ttload.c'  in
  3422.     order to support version 2 of the table (see OpenType 1.2 spec)
  3423.  
  3424.   - created  `include/tttables.h'  and  `include/t1tables.h' to  allow
  3425.     client applications to access some of  the SFNT and T1 tables of a
  3426.     face  with  a  procedural  interface (see  `FT_Get_Sfnt_Table')  +
  3427.     updates to internal source files to reflect the change..
  3428.  
  3429.   - some  cleanups in  the source  code to  get rid  of  warnings when
  3430.     compiling with the `-Wall -W -ansi -pedantic' options in gcc.
  3431.  
  3432.   - debugged and moved the smooth renderer to `src/base/ftgrays.c' and
  3433.     its header to `include/ftgrays.h'
  3434.  
  3435.   - updated TT_MAX_SUBGLYPHS  to 96 as some CJK  fonts have composites
  3436.     with up to 80 sub-glyphs !! Thanks to Werner
  3437.  
  3438.  
  3439. ======================================================================
  3440.  
  3441. OLD CHANGES - 14-apr-2000
  3442.  
  3443.   - fixed  a bug  in  the  TrueType glyph  loader  that prevented  the
  3444.     correct loading of some CJK glyphs in mingli.ttf
  3445.  
  3446.   - improved the standard Type 1 hinter in `src/type1'
  3447.  
  3448.   - fixed two bugs  in the experimental Type 1  driver in `src/type1z'
  3449.     to handle the new XFree86 4.0 fonts (and a few other ones..)
  3450.  
  3451.   - the smooth  renderer is now  complete and supports  sub-banding to
  3452.     render large glyphs  at high speed.  However, it is still  located
  3453.     in `demos/src/ftgrays.c' and should move to the  library itself in
  3454.     the next  beta.  NOTE: The  smooth  renderer  doesn't  compile  in
  3455.     stand-alone mode anymore, but this should be fixed RSN..
  3456.  
  3457.   - introduced convenience  functions to  more easily deal  with glyph
  3458.     images, see  `include/ftglyph.h' for more details, as  well as the
  3459.     new  demo program  named `demos/src/ftstring.c'  that demonstrates
  3460.     its use
  3461.  
  3462.   - implemented  FT_LOAD_NO_RECURSE in  both the  TrueType and  Type 1
  3463.     drivers  (this  is required  by  the  auto-hinter  to improve  its
  3464.     results).
  3465.  
  3466.   - changed   the  raster   interface,  in   order  to   allow  client
  3467.     applications  to   provide  their   own  span-drawing   callbacks.
  3468.     However,   only   the   smooth   renderer   supports   this.   See
  3469.     `FT_Raster_Params' in the file `include/ftimage.h'.
  3470.  
  3471.   - fixed  a small bug  in FT_MulFix  that caused  incorrect transform
  3472.     computation!
  3473.  
  3474.   - Note: The tutorial is out-of-date.
  3475.  
  3476.  
  3477. ======================================================================
  3478.  
  3479. OLD CHANGES - 12-mar-2000
  3480.  
  3481.   - changed  the  layout  of  configuration  files  :  now,  all  ANSI
  3482.     configuration         files         are         located         in
  3483.     `freetype2/config'.  System-specific over-rides  can be  placed in
  3484.     `freetype2/config/<system>'.
  3485.  
  3486.   - moved all configuration macros to `config/ftoption.h'
  3487.  
  3488.   - improvements in the Type 1 driver with AFM support
  3489.  
  3490.   - changed the fields  in the FT_Outline structure :  the old `flags'
  3491.     array is re-named `tags', while all ancient flags are encoded into
  3492.     a single unsigned int named `flags'.
  3493.  
  3494.   - introduced     new      flags     in     FT_Outline.flags     (see
  3495.     ft_outline_.... enums in `ftimage.h').
  3496.  
  3497.   - changed outline functions to `FT_Outline_<action>' syntax
  3498.  
  3499.   - added a smooth anti-alias renderer to the demonstration programs
  3500.  
  3501.   - added Mac graphics driver (thanks Just)
  3502.  
  3503.   - FT_Open_Face  changed  in  order   to  received  a  pointer  to  a
  3504.     FT_Open_Args descriptor..
  3505.  
  3506.   - various  cleanups,  a  few  more API  functions  implemented  (see
  3507.     FT_Attach_File)
  3508.  
  3509.   - updated some docs
  3510.  
  3511.  
  3512. ======================================================================
  3513.  
  3514. OLD CHANGES - 22-feb-2000
  3515.  
  3516.   - introduced the `psnames' module.  It is used to:
  3517.  
  3518.       o convert  a Postscript glyph  name into the  equivalent Unicode
  3519.         character code (used by the  Type 1 driver(s) to synthesize on
  3520.         the fly a Unicode charmap).
  3521.  
  3522.       o provide an  interface to retrieve the Postscript  names of the
  3523.         Macintosh,  Adobe  Standard &  Adobe  Expert character  codes.
  3524.         (the Macintosh  names are  used by the  SFNT-module postscript
  3525.         names support routines, while the other two tables are used by
  3526.         the Type 1 driver(s)).
  3527.  
  3528.   - introduced the `type1z' alternate Type 1 driver.  This is a (still
  3529.     experimental) driver  for the Type  1 format that  will ultimately
  3530.     replace the one  in `src/type1'.  It uses pattern matching to load
  3531.     data from the font, instead of a finite  state analyzer.  It works
  3532.     much better than the `old' driver with `broken' fonts.  It is also
  3533.     much smaller (under 15 Kb).
  3534.  
  3535.   - the  Type 1  drivers (both  in `src/type1'  and  `src/type1z') are
  3536.     nearly  complete.  They  both  provide automatic  Unicode  charmap
  3537.     synthesis through  the `psnames' module.  No re-encoding vector is
  3538.     needed.  (note  that they  still  leak  memory  due to  some  code
  3539.     missing, and I'm getting lazy).
  3540.  
  3541.     Trivial AFM support has been added to read kerning information but
  3542.     wasn't exactly tested as it should ;-)
  3543.  
  3544.   - The TrueType  glyph loader has  been seriously rewritten  (see the
  3545.     file  `src/truetype/ttgload.c'.  It is now  much, much  simpler as
  3546.     well as  easier to read,  maintain and understand  :-) Preliminary
  3547.     versions introduced a  memory leak that has been  reported by Jack
  3548.     Davis, and is now fixed..
  3549.  
  3550.   - introduced  the new  `ft_glyph_format_plotter', used  to represent
  3551.     stroked outlines  like Windows `Vector' fonts, and  certain Type 1
  3552.     fonts  like `Hershey'.  The corresponding  raster will  be written
  3553.     soon.
  3554.  
  3555.   - FT_New_Memory_Face  is  gone.  Likewise,  FT_Open_Face has  a  new
  3556.     interface that uses a structure  to describe the input stream, the
  3557.     driver (if required), etc..
  3558.  
  3559.  
  3560. TODO
  3561.  
  3562.   - Write FT_Get_Glyph_Bitmap and FT_Load_Glyph_Bitmap
  3563.  
  3564.   - Add a function like FT_Load_Character(face, char_code, load_flags)
  3565.     that  would   really  embed  a  call   to  FT_Get_Char_Index  then
  3566.     FT_Load_Glyph to ease developer's work.
  3567.  
  3568.   - Update the tutorial!
  3569.  
  3570.   - consider adding  support for Multiple  Master fonts in the  Type 1
  3571.     drivers.
  3572.  
  3573.   - Test the AFM routines of the  Type 1 drivers to check that kerning
  3574.     information is returned correctly.
  3575.  
  3576.   - write a decent auto-gridding component  !! We need this to release
  3577.     FreeType 2.0 gold !
  3578.  
  3579.  
  3580. less urgent needs:
  3581.  
  3582.   - add a CFF/Type2 driver
  3583.   - add a BDF driver
  3584.   - add a FNT/PCF/HBF driver
  3585.   - add a Speedo driver from the X11 sources
  3586.  
  3587.  
  3588. ======================================================================
  3589.  
  3590. OLDER CHANGES - 27-jan-2000
  3591.  
  3592.   - updated the  `sfnt' module  interface to allow  several SFNT-based
  3593.     drivers to co-exist peacefully
  3594.  
  3595.   - updated  the `T1_Face'  type  to better  separate Postscript  font
  3596.     content  from the  rest of  the FT_Face  structure.  Might be used
  3597.     later by the CFF/Type2 driver..
  3598.  
  3599.   - added an experimental replacement Type 1 driver featuring advanced
  3600.     (and speedy) pattern matching to retrieve the data from postscript
  3601.     fonts.
  3602.  
  3603.   - very minor  changes in the implementation  of FT_Set_Char_Size and
  3604.     FT_Set_Pixel_Sizes (they now implement default to lighten the font
  3605.     driver's code).
  3606.  
  3607.  
  3608. ======================================================================
  3609.  
  3610. OLD MESSAGE
  3611.  
  3612. This file summarizes the changes  that occurred  since the last `beta'
  3613. of FreeType 2. Because the list is important, it has been divided into
  3614. separate sections:
  3615.  
  3616. Table Of Contents:
  3617.  
  3618.     I   High-Level Interface (easier !)
  3619.    II   Directory Structure
  3620.   III   Glyph Image Formats
  3621.    IV   Build System
  3622.     V   Portability
  3623.    VI   Font Drivers
  3624.  
  3625.  
  3626. ----------------------------------------------------------------------
  3627.  
  3628. High-Level Interface:
  3629.  
  3630.   The high-level API has been considerably simplified.  Here is how:
  3631.  
  3632.     - resource objects have disappeared.  this means that face objects
  3633.       can now be created with  a single function call (see FT_New_Face
  3634.       and FT_Open_Face)
  3635.  
  3636.     - when calling  either FT_New_Face  & FT_Open_Face, a  size object
  3637.       and a glyph slot object  are automatically created for the face,
  3638.       and can  be accessed  through `face->glyph' and  `face->size' if
  3639.       one really  needs to.   In most cases,  there's no need  to call
  3640.       FT_New_Size or FT_New_Glyph.
  3641.  
  3642.     - similarly,  FT_Load_Glyph  now  only  takes  a  `face'  argument
  3643.       (instead  of a  glyph  slot  and a  size).  Also,  its  `result'
  3644.       parameter is  gone, as the glyph  image type is  returned in the
  3645.       field `face->glyph.format'
  3646.  
  3647.     - the list  of available  charmaps is directly  accessible through
  3648.       `face->charmaps', counting `face->num_charmaps'  elements.  Each
  3649.       charmap  has an  'encoding'  field which  specifies which  known
  3650.       encoding it deals with.  Valid values are, for example:
  3651.  
  3652.           ft_encoding_unicode      (for ASCII, Latin-1 and Unicode)
  3653.           ft_encoding_apple_roman
  3654.           ft_encoding_sjis
  3655.           ft_encoding_adobe_standard
  3656.           ft_encoding_adobe_expert
  3657.  
  3658.       other  values may  be added  in the  future.  Each charmap still
  3659.       holds  its `platform_id'  and `encoding_id'  values in  case the
  3660.       encoding is too exotic for the current library
  3661.  
  3662.  
  3663. ----------------------------------------------------------------------
  3664.  
  3665. Directory Structure:
  3666.  
  3667.   Should seem obvious to most of you:
  3668.  
  3669.      freetype/
  3670.          config/        -- configuration sub-makefiles
  3671.             ansi/
  3672.             unix/       -- platform-specific configuration files
  3673.             win32/
  3674.             os2/
  3675.             msdos/
  3676.  
  3677.          include/       -- public header  files, those to  be included
  3678.                            directly by client apps
  3679.  
  3680.          src/           -- sources of the library
  3681.            base/        -- the base layer
  3682.            sfnt/        -- the sfnt `driver'  (see the drivers section
  3683.                            below)
  3684.            truetype/    -- the truetype driver
  3685.            type1/       -- the type1 driver
  3686.            shared/      -- some header files shared between drivers
  3687.  
  3688.          demos/         -- demos/tools
  3689.  
  3690.          docs/          -- documentation (a bit empty for now)
  3691.  
  3692.  
  3693. ----------------------------------------------------------------------
  3694.  
  3695. Glyph Image Formats:
  3696.  
  3697.   Drivers are now able to  register new glyph image formats within the
  3698.   library.  For  now, the  base layer supports  of course  bitmaps and
  3699.   vector  outlines, but  one  could imagine  something different  like
  3700.   colored bitmaps, bi-color vectors or whatever else (Metafonts anyone
  3701.   ??).
  3702.  
  3703.   See  the   file  `include/ftimage.h'.   Note  also  that   the  type
  3704.   FT_Raster_Map  is gone,  and  is now  replaced  by FT_Bitmap,  which
  3705.   should encompass all known bitmap types.
  3706.  
  3707.   Each new  image format  must provide at  least one `raster',  i.e. a
  3708.   module capable of  transforming the glyph image into a bitmap.  It's
  3709.   also possible  to change the default  raster used for  a given glyph
  3710.   image format.
  3711.  
  3712.   The default outline  scan-converter now uses 128 levels  of grays by
  3713.   default,  which tends  to smooth  many  things.  Note that the  demo
  3714.   programs have been updated significantly in order to display these..
  3715.  
  3716.  
  3717. ----------------------------------------------------------------------
  3718.  
  3719. Build system:
  3720.  
  3721.   You still need  GNU Make to build the library.  The build system has
  3722.   been very seriously re-vamped in order to provide things like :
  3723.  
  3724.    - automatic host platform  detection (reverting to 'config/ansi' if
  3725.      it is not detected, with pseudo-standard compilation flags)
  3726.  
  3727.    - the ability to compile from the Makefiles with very different and
  3728.      exotic compilers.  Note that linking the library can be difficult
  3729.      for some platforms.
  3730.  
  3731.      For example, the file `config/win32/lcclib.bat' is invoked by the
  3732.      build system to create the `.lib' file with LCC-Win32 because its
  3733.      librarian  has too  many flaws  to be  invoked directly  from the
  3734.      Makefile.
  3735.  
  3736.   Here's how it works:
  3737.  
  3738.   - the first time you type `make',  the build system runs a series of
  3739.     sub-makefiles  in order  to detect  your host  platform.  It  then
  3740.     dumps what it found, and creates a file called `config.mk' in  the
  3741.     current  directory.  This is a  sub-Makefile used  to  define many
  3742.     important Make variables used to build the library.
  3743.  
  3744.   - the second time, the build system detects the `config.mk' then use
  3745.     it  to  build the  library.  All object  files  go  into 'obj'  by
  3746.     default,  as well  as the  library file,  but this  can  easily be
  3747.     changed.
  3748.  
  3749.   Note that  you can run `make  setup' to force  another host platform
  3750.   detection  even   if  a  `config.mk'  is  present   in  the  current
  3751.   directory.  Another solution  is  simply to  delete  the file,  then
  3752.   re-run make.
  3753.  
  3754.   Finally, the  default compiler  for all platforms  is gcc  (for now,
  3755.   this will hopefully changed in the future).  You can however specify
  3756.   a different  compiler by specifying  it after the 'setup'  target as
  3757.   in:
  3758.  
  3759.       gnumake setup lcc         on Win32 to use the LCC compiler
  3760.       gnumake setup visualc     on Win32 to use Visual C++
  3761.  
  3762.   See  the file  `config/<system>/detect.mk' for  a list  of supported
  3763.   compilers for your platforms.
  3764.  
  3765.   It should be relatively easy  to write new detection rules files and
  3766.   config.mk..
  3767.  
  3768.   Finally, to  build the demo programs,  go to `demos'  and launch GNU
  3769.   Make, it will use the `config.mk'  in the top directory to build the
  3770.   test programs..
  3771.  
  3772.  
  3773. ----------------------------------------------------------------------
  3774.  
  3775. Portability:
  3776.  
  3777.   In  the  previous  beta,  a  single FT_System  object  was  used  to
  3778.   encompass  all  low-level  operations like  thread  synchronisation,
  3779.   memory management and i/o access.  This has been greatly simplified:
  3780.  
  3781.     - thread synchronisation  has been dropped, for  the simple reason
  3782.       that the library  is already re-entrant, and that  if you really
  3783.       need  two  threads accessing  the  same  FT_Library, you  should
  3784.       really synchronize access to it yourself with a simple mutex.
  3785.  
  3786.     - memory  management is  performed  through a  very simple  object
  3787.       called `FT_Memory',  which really is a table  containing a table
  3788.       of pointers to  functions like malloc, realloc and  free as well
  3789.       as some user data (closure).
  3790.  
  3791.     - resources have disappeared (they created more problems than they
  3792.       solved), and  i/o management have  been simplified greatly  as a
  3793.       result.  Streams are  defined through  FT_Stream objects,  which
  3794.       can be either memory-based or disk-based.
  3795.  
  3796.       Note that  each face  has its own  stream, which is  closed only
  3797.       when  the  face object  is  destroyed.  Hence,  a function  like
  3798.       TT_Flush_Face in 1.x cannot be directly  supported.  However, if
  3799.       you really need something like  this, you can easily tailor your
  3800.       own streams  to achieve the same  feature at a  lower level (and
  3801.       use FT_Open_Face instead of FT_New_Face to create the face).
  3802.  
  3803.   See the file  `include/ftsystem.h' for more details, as  well as the
  3804.   implementations found in `config/unix' and `config/ansi'.
  3805.  
  3806.  
  3807. ----------------------------------------------------------------------
  3808.  
  3809. Font Drivers:
  3810.  
  3811.   The  Font Driver  interface has  been modified  in order  to support
  3812.   extensions & versioning.
  3813.  
  3814.  
  3815.   The  list of  the font  drivers that  are statically  linked  to the
  3816.   library at compile time is  managed through a new configuration file
  3817.   called `config/<platform>/ftmodule.h'.
  3818.  
  3819.   This  file is  autogenerated  when  invoking  `make modules'.   This
  3820.   target  will  parse  all  sub-directories  of  'src', looking  for a
  3821.   `module.mk' rules  file, used  to describe  the driver to  the build
  3822.   system.
  3823.  
  3824.   Hence, one  should call  `make modules' each  time a font  driver is
  3825.   added or removed from the `src' directory.
  3826.  
  3827.   Finally, this  version  provides  a `pseudo-driver'  in  `src/sfnt'.
  3828.   This  driver  doesn't  support  font  files  directly, but  provides
  3829.   services used by all TrueType-like font drivers.  Hence, its code is
  3830.   shared between  the TrueType & OpenType  font formats,  and possibly
  3831.   more formats to come if we're lucky..
  3832.  
  3833.  
  3834. ----------------------------------------------------------------------
  3835.  
  3836. Extensions support:
  3837.  
  3838.   The extensions support is inspired by the one found in 1.x.
  3839.  
  3840.   Now, each font driver has  its own `extension registry', which lists
  3841.   which extensions  are available  for the font  faces managed  by the
  3842.   driver.
  3843.  
  3844.   Extension ids are  now strings, rather than 4-byte  tags, as this is
  3845.   usually more readable.
  3846.  
  3847.   Each extension has:
  3848.     - some data, associated to each face object
  3849.     - an interface (table of function pointers)
  3850.  
  3851.   An extension  that is format-specific should  simply register itself
  3852.   to the correct font driver.  Here is some example code:
  3853.  
  3854.    // Registering an extensions
  3855.    //
  3856.    FT_Error  FT_Init_XXXX_Extension( FT_Library  library )
  3857.    {
  3858.      FT_DriverInterface*  tt_driver;
  3859.  
  3860.      driver = FT_Get_Driver( library, "truetype" );
  3861.      if (!driver) return FT_Err_Unimplemented_Feature;
  3862.  
  3863.      return FT_Register_Extension( driver, &extension_class );
  3864.    }
  3865.  
  3866.  
  3867.    // Implementing the extensions
  3868.    //
  3869.    FT_Error  FT_Proceed_Extension_XXX( FT_Face  face )
  3870.    {
  3871.      FT_XXX_Extension            ext;
  3872.      FT_XXX_Extension_Interface  ext_interface;
  3873.  
  3874.      ext = FT_Get_Extension( face, "extensionid", &ext_interface );
  3875.      if (!ext) return error;
  3876.  
  3877.      return ext_interface->do_it(ext);
  3878.    }
  3879.  
  3880. ------------------------------------------------------------------------
  3881.  
  3882. Copyright 2000-2013 by
  3883. David Turner, Robert Wilhelm, and Werner Lemberg.
  3884.  
  3885. This  file  is  part  of the  FreeType  project, and may  only be  used,
  3886. modified,  and  distributed  under  the  terms of  the FreeType  project
  3887. license, LICENSE.TXT.   By continuing to use, modify, or distribute this
  3888. file you  indicate that  you have  read the  license and understand  and
  3889. accept it fully.
  3890.  
  3891.  
  3892. Local Variables:
  3893. version-control: never
  3894. coding: utf-8
  3895. End:
  3896.  
  3897. --- end of CHANGES ---
  3898.