2 CHANGES BETWEEN 2.4.8 and 2.4.9
6 - Another round of fixes to better handle invalid fonts. Many of
7 them are vulnerabilities (see CVE-2012-1126 up to CVE-2012-1144
8 and SA48320) so all users should upgrade.
13 - The `ENCODING -1 <n>' format of BDF fonts is now supported.
15 - For BDF fonts, support for the whole Unicode encoding range has
18 - Better TTF support for x_ppem != y_ppem.
20 - `FT_Get_Advances' sometimes returned bogus values.
22 - The demo programs no longer recognize and handle default
23 suffixes; you now have to always specify the complete font name.
25 - Better rendering and LCD mode cycling added to ftview.
28 ======================================================================
30 CHANGES BETWEEN 2.4.7 and 2.4.8
32 I. IMPORTANT BUG FIXES
34 - Some vulnerabilities in handling CID-keyed PostScript fonts have
35 been fixed; see CVE-2011-3439.
40 - Chris Liddell contributed a new API, `FT_Get_PS_Font_Value', to
41 retrieve most of the dictionary keys in Type 1 fonts.
44 ======================================================================
46 CHANGES BETWEEN 2.4.6 and 2.4.7
48 I. IMPORTANT BUG FIXES
50 - Some vulnerabilities in handling Type 1 fonts have been fixed;
56 - FreeType now properly handles ZapfDingbats glyph names while
57 constructing a Unicode character map (for fonts which don't have
61 ======================================================================
63 CHANGES BETWEEN 2.4.5 and 2.4.6
65 I. IMPORTANT BUG FIXES
67 - For TrueType based fonts, the ascender and descender values were
68 incorrect sometimes (off by a pixel if the ppem value was not a
69 multiple of 5). Depending on the use you might now experience
70 a different layout; the change should result in better, more
71 consistent line spacing.
73 - Fix CVE-2011-0226 which causes a vulnerability while handling
76 - BDF fonts containing glyphs with negative values for ENCODING
77 were incorrectly rejected. This bug has been introduced in
78 FreeType version 2.2.0.
80 - David Bevan contributed a major revision of the FreeType stroker
83 . The behaviour of FT_STROKER_LINEJOIN_BEVEL has been corrected.
85 . A new line join style, FT_STROKER_LINEJOIN_MITER_FIXED, has
86 been introduced to support PostScript and PDF miter joins.
88 . FT_STROKER_LINEJOIN_MITER_VARIABLE has been introduced as an
89 alias for FT_STROKER_LINEJOIN_MITER.
91 . Various stroking glitches has been fixed.
96 - SFNT bitmap fonts which contain an outline glyph for `.notdef'
97 only no longer set the FT_FACE_FLAG_SCALABLE flag.
100 ======================================================================
102 CHANGES BETWEEN 2.4.4 and 2.4.5
104 I. IMPORTANT BUG FIXES
106 - A rendering regression for second-order Bézier curves has been
107 fixed, introduced in 2.4.3.
110 II. IMPORTANT CHANGES
112 - If autohinting is not explicitly disabled, FreeType now uses
113 the autohinter if a TrueType based font doesn't contain native
116 - The load flag FT_LOAD_IGNORE_GLOBAL_ADVANCE_WIDTH has been made
117 redundant and is simply ignored; this means that FreeType now
118 ignores the global advance width value in TrueType fonts.
123 - `FT_Sfnt_Table_Info' can now return the number of SFNT tables of
126 - Support for PCF files compressed with bzip2 has been contributed
127 by Joel Klinghed. To make this work, the OS must provide a
130 - Bradley Grainger contributed project and solution files in
131 Visual Studio 2010 format.
133 - Again some fixes to better handle broken fonts.
135 - Some improvements to the B/W rasterizer.
137 - Fixes to the cache module to improve robustness.
139 - Just Fill Bugs contributed (experimental) code to compute blue
140 zones for CJK Ideographs, improving the alignment of horizontal
141 stems at the top or bottom edges.
143 - The `ftgrid' demo program can now display autohinter segments,
144 to be toggled on and off with key `s'.
147 ======================================================================
149 CHANGES BETWEEN 2.4.3 and 2.4.4
151 I. IMPORTANT BUG FIXES
153 - UVS support (TrueType/OpenType cmap format 14) support is fixed.
154 This regression has been introduced in version 2.4.0.
159 - Detect tricky fonts (e.g. MingLiU) by the lengths and checksums
160 of Type42-persistent subtables (`cvt ', `fpgm', and `prep') when
161 a TrueType font without family name is given. The previous fix,
162 introduced in 2.4.3, was too rigorous, causing many subsetted
163 fonts (mainly from PDF files) displayed badly because FreeType
164 forced rendering with the TrueType bytecode engine instead of
167 - Better support for 64bit platforms.
169 - More fixes to improve handling of broken fonts.
172 ======================================================================
174 CHANGES BETWEEN 2.4.2 and 2.4.3
176 I. IMPORTANT BUG FIXES
178 - Fix rendering of certain cubic, S-shaped arcs. This regression
179 has been introduced in version 2.4.0.
184 - To fix the above mentioned rendering issue, a new spline
185 flattening algorithm has been introduced which speeds up both
186 conic and cubic arcs.
188 - Handling of broken fonts has been further improved.
191 ======================================================================
193 CHANGES BETWEEN 2.4.1 and 2.4.2
195 I. IMPORTANT BUG FIXES
197 - A stack overflow in CFF Type2 CharStrings interpreter is fixed.
199 - Handling Type 42 font deallocation was broken; additionally, the
200 library is now more robust against malformed Type 42 fonts.
205 - Two new functions, `FT_Reference_Library' (in FT_MODULE_H) and
206 `FT_Reference_Face' (in FT_FREETYPE_H), have been added to
207 simplify life-cycle management. A counter gets initialized to 1
208 at the time an FT_Library (or FT_Face) structure is created.
209 The two new functions increment the respective counter.
210 `FT_Done_Library' and `FT_Done_Face' then only destroy a library
211 or face if the counter is 1, otherwise they simply decrement the
215 ======================================================================
217 CHANGES BETWEEN 2.4.0 and 2.4.1
221 - A serious bug in the CFF font module prevented display of many
222 glyphs in CFF fonts like `MinionPro-Regular.otf'.
225 ======================================================================
227 CHANGES BETWEEN 2.3.12 and 2.4.0
231 - Since May 2010, all patents regarding the TrueType bytecode
232 interpreter have expired worldwide. Consequently, we now define
233 TT_CONFIG_OPTION_BYTECODE_INTERPRETER by default (and undefine
234 TT_CONFIG_OPTION_UNPATENTED_HINTING).
236 - A new function `FT_Library_SetLcdFilterWeights' is available to
237 adjust the filter weights set by `FT_Library_SetLcdFilter'.
242 - Thanks to many reports from Robert Święcki, FreeType's stability
243 in handling broken or damaged fonts is much improved.
245 - Support for LCD filter control has been added to the demo
246 programs `ftdiff' and `ftview'.
249 ======================================================================
251 CHANGES BETWEEN 2.3.11 and 2.3.12
255 - For `FT_Open_Face', new parameters are available to ignore
256 preferred family names: FT_PARAM_TAG_IGNORE_PREFERRED_FAMILY and
257 FT_PARAM_TAG_IGNORE_PREFERRED_SUBFAMILY.
262 - Support for incremental font loading (controlled with the
263 FT_CONFIG_OPTION_INCREMENTAL macro) is now active by default.
265 - Better support for vertical metrics.
267 - Various minor bug fixes.
270 ======================================================================
272 CHANGES BETWEEN 2.3.10 and 2.3.11
274 I. IMPORTANT BUG FIXES
276 - Version 2.3.10 broke PCF support.
279 ======================================================================
281 CHANGES BETWEEN 2.3.10 and 2.3.9
283 I. IMPORTANT BUG FIXES
285 - If all ASCII digits in a font have the same (unscaled) width,
286 the autohinter respects this and won't change it.
288 - TrueType fonts are now rasterized correctly if the horizontal
289 and vertical resolution differ.
291 - Type 1 fonts are now handled with increased precision internally
292 to avoid serious rounding issues if non-integral coordinates are
295 - Horizontally condensed CFF fonts (using the font matrix) were
296 rendered incorrectly. This bug has been introduced after
300 II. IMPORTANT CHANGES
302 - Support for the SFNT cmap 13 table format (as defined by the new
303 OpenType 1.6 specification) has been added.
305 - B/W rasterization of well-hinted TrueType fonts at small sizes
306 has been greatly improved.
308 - Calculation of vertical metrics in OpenType fonts has been
314 - It is now possible to change the emboldening factor in the
315 `ftview' demo program with keys `e' and `E'.
317 - It is now possible to change the slant value in the `ftview'
318 demo program with keys `s' and `S'.
320 - The 5-levels grayscale mode of the `ftraster' module (which
321 FreeType doesn't use by default) was broken since version 2.3.0.
323 - Compilation of the `ftgrays' and `ftraster' modules was broken
326 - Various fixes for compilation on 64bit and 16bit architectures.
329 ======================================================================
331 CHANGES BETWEEN 2.3.9 and 2.3.8
333 I. IMPORTANT BUG FIXES
335 - Very unfortunately, FreeType 2.3.8 contained a change that broke
336 its official ABI. The end result is that programs compiled
337 against previous versions of the library, but dynamically linked
338 to 2.3.8 can experience memory corruption if they call the
339 `FT_Get_PS_Font_Info' function.
341 We recommend all users to upgrade to 2.3.9 as soon as possible,
342 or to downgrade to a previous release of the library if this is
345 The origin of the bug is that a new field was added to the
346 publicly defined `PS_FontInfoRec' structure. Unfortunately,
347 objects of this type can be stack or heap allocated by callers
348 of `FT_Get_PS_Font_Info', resulting in a memory buffer
349 overwrite with its implementation in 2.3.8.
351 If you want to know whether your code is vulnerable to this
352 issue, simply search for the substrings `PS_FontInfo' and
353 `PS_Font_Info' in your source code. If none is found, your code
354 is safe and is not affected.
356 The FreeType team apologizes for the problem.
358 - The POSIX support of MacOS resource-fork fonts (Suitcase fonts
359 and LaserWriter Type1 PostScript fonts) was broken in 2.3.8. If
360 FreeType2 is built without Carbon framework, these fonts are not
361 handled correctly. Version 2.3.7 didn't have this bug.
363 - `FT_Get_Advance' (and `FT_Get_Advances') returned bad values for
364 almost all font formats except TrueType fonts.
366 - Fix a bug in the SFNT kerning table loader/parser which could
367 crash the engine if certain malformed tables were encountered.
369 - Composite SFNT bitmaps are now handled correctly.
372 II. IMPORTANT CHANGES
374 - The new functions `FT_Get_CID_Is_Internally_CID_keyed' and
375 `FT_Get_CID_From_Glyph_Index' can be used to access CID-keyed
376 CFF fonts via CID values. This code has been contributed by
382 - `FT_Outline_Get_InsideBorder' returns FT_STROKER_BORDER_RIGHT
383 for empty outlines. This was incorrectly documented.
385 - The `ftview' demo program now supports UTF-8 encoded strings.
388 ======================================================================
390 CHANGES BETWEEN 2.3.8 and 2.3.7
392 I. IMPORTANT BUG FIXES
394 - CID-keyed fonts in an SFNT wrapper were not handled correctly.
396 - The smooth renderer produced truncated images (on the right) for
397 outline parts with negative horizontal values. Most fonts don't
398 contain outlines left to the y coordinate axis, but the effect
399 was very noticeable for outlines processed with FT_Glyph_Stroke,
402 - `FT_Get_TrueType_Engine_Type' returned a wrong value if both
403 configuration macros TT_CONFIG_OPTION_BYTECODE_INTERPRETER and
404 TT_CONFIG_OPTION_UNPATENTED_HINTING were defined.
406 - The `face_index' field in the `FT_Face' structure wasn't
407 initialized properly after calling FT_Open_Face and friends with
408 a positive face index for CFFs, WinFNTs, and, most importantly,
409 for TrueType Collections (TTCs).
412 II. IMPORTANT CHANGES
414 - Rudimentary support for Type 1 fonts and CID-keyed Type 1 fonts
415 in an SFNT wrapper has been added -- such fonts are used on the
416 Mac. The core SFNT tables `TYP1' and `CID ' are passed to the
417 PS Type 1 and CID-keyed PS font drivers; other tables (`ALMX',
418 `BBOX', etc.) are not supported yet.
420 - A new interface to extract advance values of glyphs without
421 loading their outlines has been added. The functions are called
422 `FT_Get_Advance' and `FT_Get_Advances'; they are defined in file
423 `ftadvanc.h' (to be accessed as FT_ADVANCES_H).
425 - A new function `FT_Get_FSType_Flags' (in FT_FREETYPE_H) has been
426 contributed by David Bevan to access the embedding and
427 subsetting restriction information of fonts.
432 - FT_MulFix is now an inlined function; by default, assembler code
433 is provided for x86 and ARM. See FT_CONFIG_OPTION_INLINE_MULFIX
434 and FT_CONFIG_OPTION_NO_ASSEMBLER (in ftoption.h) for more.
436 - The handling of `tricky' fonts (this is, fonts which don't work
437 with the autohinter, needing the font format's hinting engine)
438 has been generalized and changed slightly:
440 . A new face flag FT_FACE_FLAG_TRICKY indicates that the font
441 format's hinting engine is necessary for correct rendering.
442 The macro FT_IS_TRICKY can be used to check this flag.
444 . FT_LOAD_NO_HINTING is now ignored for tricky fonts. To really
445 force raw loading of such fonts (without hinting), both
446 FT_LOAD_NO_HINTING and FT_LOAD_NO_AUTOHINT must be used --
447 this is something which you probably never want to do.
449 . Tricky TrueType fonts always use the bytecode interpreter,
450 either the patented or unpatented version.
452 - The function `FT_GlyphSlot_Own_Bitmap' has been moved from
453 FT_SYNTHESIS_H to FT_BITMAP_H; it is now part of the `official'
454 API. (The functions in FT_SYNTHESIS_H are still subject to
457 - In the `ftdiff' demo program you can now toggle the use of
458 FT_LOAD_IGNORE_GLOBAL_ADVANCE_WIDTH with key `a'.
461 ======================================================================
463 CHANGES BETWEEN 2.3.7 and 2.3.6
465 I. IMPORTANT BUG FIXES
467 - If the library was compiled on an i386 platform using gcc, and
468 compiler option -O3 was given, `FT_MulFix' sometimes returned
469 incorrect results which could have caused problems with
470 `FT_Request_Metrics' and `FT_Select_Metrics', returning an
471 incorrect descender size.
473 - Pure CFFs without subfonts were scaled incorrectly if the font
474 matrix was non-standard. This bug has been introduced in
477 - The `style_name' field in the `FT_FaceRec' structure often
478 contained a wrong value for Type 1 fonts. This misbehaviour
479 has been introduced in version 2.3.6 while trying to fix
480 another problem. [Note, however, that this value is
481 informative only since the used algorithm to extract it is
485 II. IMPORTANT CHANGES
487 - Two new macros, FT_OUTLINE_SMART_DROPOUTS and
488 FT_OUTLINE_EXCLUDE_STUBS, have been introduced. Together with
489 FT_OUTLINE_IGNORE_DROPOUTS (which was ignored previously) it is
490 now possible to control the dropout mode of the `raster' module
491 (for B&W rasterization), using the `flags' field in the
492 `FT_Outline' structure.
494 - The TrueType bytecode interpreter now passes the dropout mode to
495 the B&W rasterizer. This greatly increases the output for small
496 ppem values of many fonts like `pala.ttf'.
499 ======================================================================
501 CHANGES BETWEEN 2.3.6 and 2.3.5
503 I. IMPORTANT BUG FIXES
505 - A bunch of potential security problems have been found. All
508 - Microsoft Unicode cmaps in TrueType fonts are now always
509 preferred over Apple cmaps. This is not a bug per se, but there
510 exist some buggy fonts created for MS which have broken Apple
511 cmaps. This affects only the automatic selection of FreeType;
512 it's always possible to manually select an Apple Unicode cmap if
515 - Many bug fixes to the TrueType bytecode interpreter.
517 - Improved Mac support.
519 - Subsetted CID-keyed CFFs are now supported correctly.
521 - CID-keyed CFFs with subfonts which are scaled in a non-standard
522 way are now handled correctly.
524 - A call to FT_Open_Face with `face_index' < 0 crashed FreeType if
525 the font was a Windows (bitmap) FNT/FON.
528 II. IMPORTANT CHANGES
530 - The new function `FT_Get_CID_Registry_Ordering_Supplement' gives
531 access to those fields in a CID-keyed font. The code has been
532 contributed by Derek Clegg.
534 - George Williams contributed code to validate the new `MATH'
535 OpenType table (within the `otvalid' module). The `ftvalid'
536 demo program has been extended accordingly.
538 - An API for cmap 14 support (for Unicode Variant Selectors, UVS)
539 has been contributed by George Williams.
541 - A new face flag FT_FACE_FLAG_CID_KEYED has been added, together
542 with a macro FT_IS_CID_KEYED which evaluates to 1 if the font is
548 - Build support for symbian has been contributed.
550 - Better WGL4 glyph name support, contributed by Sergey Tolstov.
552 - Debugging output of the various FT_TRACEX macros is now sent to
555 - The `ftview' demo program now provides artificial slanting too.
557 - The `ftvalid' demo program has a new option `-f' to select the
561 ======================================================================
563 CHANGES BETWEEN 2.3.5 and 2.3.4
565 I. IMPORTANT BUG FIXES
567 - Some subglyphs in TrueType fonts were handled incorrectly due to
568 a missing graphics state reinitialization.
570 - Large .Z files (as distributed with some X11 packages) weren't
571 handled correctly, making FreeType increase the heap stack in an
574 - A large number of bugs have been fixed to avoid crashes and
575 endless loops with invalid fonts.
578 II. IMPORTANT CHANGES
580 - The two new cache functions `FTC_ImageCache_LookupScaler' and
581 `FTC_SBit_Cache_LookupScaler' have been added to allow lookup of
582 glyphs using an `FTC_Scaler' object; this makes it possible to
583 use fractional pixel sizes in the cache. The demo programs have
584 been updated accordingly to use this feature.
586 - A new API `FT_Get_CMap_Format' has been added to get the cmap
587 format of a TrueType font. This is useful in handling PDF
588 files. The code has been contributed by Derek Clegg.
590 - The auto-hinter now produces better output by default for
591 non-Latin scripts like Indic. This was done by using the CJK
592 hinting module as the default instead of the Latin one. Thanks
593 to Rahul Bhalerao for this suggestion.
595 - A new API `FT_Face_CheckTrueTypePatents' has been added to find
596 out whether a given TrueType font uses patented bytecode
597 instructions. The `ft2demos' bundle contains a new program
598 called `ftpatchk' which demonstrates its usage.
600 - A new API `FT_Face_SetUnpatentedHinting' has been added to
601 enable or disable the unpatented hinter.
603 - Support for Windows FON files in PE format has been contributed
609 - Vincent Richomme contributed Visual C++ project files for Pocket
613 ======================================================================
615 CHANGES BETWEEN 2.3.4 and 2.3.3
617 I. IMPORTANT BUG FIXES
619 - A serious bug in the handling of bitmap fonts (and bitmap
620 strikes of outline fonts) has been introduced in 2.3.3.
623 ======================================================================
625 CHANGES BETWEEN 2.3.3 and 2.3.2
627 I. IMPORTANT BUG FIXES
629 - Remove a serious regression in the TrueType bytecode interpreter
630 that was introduced in version 2.3.2. Note that this does not
631 disable the improvements introduced to the interpreter in
632 version 2.3.2, only some ill cases that occurred with certain
633 fonts (though a few popular ones).
635 - The auto-hinter now ignores single-point contours for computing
636 blue zones. This bug created `wavy' baselines when rendering
637 text with various fonts that use these contours to model
638 mark-attach points (these are points that are never rasterized
639 and are placed outside of the glyph's real outline).
641 - The `rsb_delta' and `lsb_delta' glyph slot fields are now set to
642 zero for mono-spaced fonts. Otherwise code that uses them would
643 essentially ruin the fixed-advance property.
645 - Fix CVE-2007-1351 which can cause an integer overflow while
646 parsing BDF fonts, leading to a potentially exploitable heap
652 - Fixed compilation issues on some 64-bit platforms (see ChangeLog
655 - A new demo program `ftdiff' has been added to compare TrueType
656 hinting, FreeType's auto hinting, and rendering without hinting
660 ======================================================================
662 CHANGES BETWEEN 2.3.2 and 2.3.1
664 I. IMPORTANT BUG FIXES
666 - FreeType returned incorrect kerning information from TrueType
667 fonts when the bytecode interpreter was enabled. This happened
668 due to a typo introduced in version 2.3.0.
670 - Negative kerning values from PFM files are now reported
671 correctly (they were read as 16-bit unsigned values from the
674 - Fixed a small memory leak when `FT_Init_FreeType' failed for
677 - The Postscript hinter placed and sized very thin and ghost stems
680 - The TrueType bytecode interpreter has been fixed to get rid of
681 most of the rare differences seen in comparison to the Windows
685 II. IMPORTANT CHANGES
687 - The auto-hinter now better deals with serifs and corner cases
688 (e.g., glyph '9' in Arial at 9pt, 96dpi). It also improves
689 spacing adjustments and doesn't change widths for non-spacing
692 - Many Mac-specific functions are deprecated (but still
693 available); modern replacements have been provided for them.
694 See the documentation in file `ftmac.h'.
697 ======================================================================
699 CHANGES BETWEEN 2.3.1 and 2.3.0
701 I. IMPORTANT BUG FIXES
703 - The TrueType interpreter sometimes returned incorrect horizontal
704 metrics due to a bug in the handling of the SHZ instruction.
706 - A typo in a security check introduced after version 2.2.1
707 prevented FreeType to render some glyphs in CFF fonts.
710 ======================================================================
712 CHANGES BETWEEN 2.3.0 and 2.2.1
714 I. IMPORTANT BUG FIXES
716 - The PCF font loader is now much more robust while loading
717 malformed font files.
719 - Various memory leaks have been found and fixed.
721 - The TrueType name loader now deals properly with some fonts that
722 encode their names in UTF-16 (the specification was vague, and
723 the code incorrectly assumed UCS-4).
725 - Fixed the TrueType bytecode loader to deal properly with subtle
726 monochrome/gray issues when scaling the CVT. Some fonts
727 exhibited bad rendering artifacts otherwise.
729 - `FT_GlyphSlot_Embolden' now supports vertical layouts correctly
730 (it mangled the vertical advance height).
732 - Fixed byte endian issues of `ftmac.c' to support Mac OS X on
735 - The PFR font loader no longer erroneously tags font files
736 without any outlines as FT_FACE_FLAG_SCALABLE.
739 II. NEW API FUNCTIONS
741 - `FT_Library_SetLcdFilter' allows you to select a special filter
742 to be applied to the bitmaps generated by `FT_Render_Glyph' if
743 one of the FT_RENDER_MODE_LCD and FT_RENDER_MODE_LCD_V modes has
744 been selected. This filter is used to reduce color fringes;
745 several settings are available through the FT_LCD_FILTER_XXX
748 Its declaration and documentation can be found in file
749 `include/freetype/ftlcdfil.h' (to be accessed with macro
752 *IMPORTANT*: This function returns an error
753 (FT_Err_Unimplemented_Feature) in default builds of the library
754 for patent reasons. See below.
756 - `FT_Get_Gasp' allows you to query the flags of the TrueType
757 `gasp' table for a given character pixel size. This is useful
758 to duplicate the text rendering of MS Windows when the native
759 bytecode interpreter is enabled (which isn't the default for
760 other patent reasons).
762 Its declaration and documentation can be found in file
763 `include/freetype/ftgasp.h' (to be accessed with macro
767 III. IMPORTANT CHANGES
769 - The auto-hinter has been tuned a lot to improve its results with
770 serif fonts, resulting in much better font rendering of many web
773 - The unpatented hinter is now part of the default build of the
774 library; we have added code to automatically support `tricky'
777 This means that FreeType should `just work' with certain Asian
778 fonts, like MingLiU, which cannot properly be loaded without a
779 bytecode interpreter, but which fortunately do not use any of
780 the patented bytecode opcodes. We detect these fonts by name,
781 so please report any font file that doesn't seem to work with
782 FreeType, and we shall do what we can to support it in a next
785 Note that the API hasn't changed, so you can still force
786 unpatented hinting with a special parameter to `FT_Open_Face' as
787 well. This might be useful in same cases; for example, a PDF
788 reader might present a user option to activate it to deal with
789 certain `tricky' embedded fonts which cannot be clearly
792 If you are a developer for embedded systems, you might want to
793 *disable* the feature to save code space by undefining
794 TT_CONFIG_OPTION_UNPATENTED_HINTING in file `ftoption.h'.
796 - LCD-optimized rendering is now *disabled* in all default builds
797 of the library, mainly due to patent issues. For more
800 http://lists.gnu.org/archive/html/freetype/2006-09/msg00064.html
802 A new configuration macro FT_CONFIG_OPTION_SUBPIXEL_RENDERING
803 has been introduced in `ftoption.h'; manually define it in this
804 file if you want to re-enable the feature.
806 The change only affects the implementation, not the FreeType
807 API. This means that clients don't need to be modified, because
808 the library still generates LCD decimated bitmaps, but with the
809 added constraint that R=G=B on each triplet.
811 The displayed result should be equal to normal anti-aliased
814 Additionally, if FT_CONFIG_OPTION_SUBPIXEL_RENDERING is not
815 defined, the new `FT_Library_SetLcdFilter' function returns the
816 FT_Err_Unimplemented_Feature error code.
818 - Some computation bugs in the TrueType bytecode interpreter were
819 found, which allow us to get rid of very subtle and rare
820 differences we had experienced with the Windows renderer.
822 - It is now possible to cross-compile the library easily. See the
823 file `docs/INSTALL.CROSS' for details.
825 - The file `src/base/ftmac.c' now contains code for Mac OS X only;
826 its deprecated function `FT_GetFile_From_Mac_Font_Name' always
827 returns an error even if the QuickDraw framework is available.
828 The previous version has been moved to `builds/mac/ftmac.c'.
830 Selecting configure option `--with-quickdraw-carbon' makes the
831 build process use the original `ftmac.c' file instead of the Mac
837 - Various performance and memory footprint optimizations have been
838 performed on the TrueType and CFF font loaders, sometimes with
839 very drastic benefits (e.g., the TrueType loader is now about
840 25% faster; FreeType should use less heap memory under nearly
843 - The anti-aliased rasterizer has been optimized and is now 15% to
844 25% percent faster than in previous versions, depending on
847 - The Type 1 loader has been improved; as an example, it now skips
848 top-level dictionaries properly.
850 - Better support for Mac fonts on POSIX systems, plus compilation
851 fixes for Mac OS X on ppc64 where `ftmac.c' cannot be built.
853 - Configuration without `--with-old-mac-fonts' does not include
854 `ftmac.c' (this was the behaviour in FreeType version 2.1.10).
856 - The TrueTypeGX validator (gxvalid) checks the order of glyph IDs
860 ======================================================================
862 CHANGES BETWEEN 2.2.1 and 2.2
864 I. IMPORTANT BUG FIXES
866 - Various integer overflows have been fixed.
868 - PFB fonts with MacOS resource fork weren't handled correctly on
872 ======================================================================
874 CHANGES BETWEEN 2.2 and 2.1.10
876 (not released officially)
878 I. IMPORTANT BUG FIXES
880 - Vertical metrics for SFNT fonts were incorrect sometimes.
882 - The FT_HAS_KERNING macro always returned 0.
884 - CFF OpenType fonts didn't return correct vertical metrics for
885 glyphs with outlines.
887 - If FreeType was compiled without hinters, all font formats based
888 on PS outlines weren't scaled correctly.
891 II. IMPORTANT CHANGES
893 - Version 2.2 no longer exposes its internals, this is, the header
894 files located in the `include/freetype/internal' directory of
895 the source package are not copied anymore by the `make install'
896 command. Consequently, a number of rogue clients which directly
897 access FreeType's internal functions and structures won't
898 compile without modification.
900 We provide patches for most of those rogue clients. See the
901 following page for more information:
903 http://www.freetype.org/freetype2/patches/rogue-patches.html
905 Note that, as a convenience to our Unix desktop users, version
906 2.2 is *binary* compatible with FreeType 2.1.7, which means that
907 installing this release on an existing distribution shall not
908 break any working desktop.
910 - FreeType's build mechanism has been redesigned. With GNU make
911 it is now sufficient in most cases to edit two files:
912 `modules.cfg', to select the library components, and the
913 configuration file `include/freetype/config/ftoption.h' (which
914 can be copied to the objects directory). Removing unused module
915 directories to prevent its compilation and editing
916 `include/freetype/config/ftmodule.h' is no longer necessary.
918 - The LIGHT hinting algorithm produces more pleasant results.
919 Also, using the FT_LOAD_TARGET_LIGHT flags within FT_Load_Glyph
920 always forces auto-hinting, as a special exception. This allows
921 you to experiment with it even if you have enabled the TrueType
922 bytecode interpreter in your build.
924 - The auto hinter now employs a new algorithm for CJK fonts, based
925 on Akito Hirai's patch. Note that this only works for fonts
926 with a Unicode charmap at the moment.
928 - The following callback function types have changed slightly (by
929 adding the `const' keyword where appropriate):
931 FT_Outline_MoveToFunc
932 FT_Outline_LineToFunc
933 FT_Outline_ConicToFunc
934 FT_Outline_CubicToFunc
938 FT_Glyph_TransformFunc
939 FT_Renderer_RenderFunc
940 FT_Renderer_TransformFunc
942 Note that this doesn't affect binary backward compatibility.
944 - On MacOS, new APIs have been added as replacements for legacy
945 APIs: `FT_New_Face_From_FSRef' for `FT_New_Face_From_FSSpec',
946 and `FT_GetFile_From_Mac_ATS_Name' for
947 `FT_GetFile_From_Mac_Name'. Legacy APIs are still available, if
948 FreeType is built without disabling them.
950 - A new API `FT_Select_Size' has been added to select a bitmap
951 strike by its index. Code using other functions to select
952 bitmap strikes should be updated to use this function.
954 - A new API `FT_Get_SubGlyph_Info' has been added to retrieve
955 subglyph data. This can be used by rogue clients which used to
956 access the internal headers to get the corresponding data.
958 - In 2.1.10, the behaviour of `FT_Set_Pixel_Sizes' was changed for
959 BDF/PCF fonts, and only for them. This causes inconsistency.
960 In this release, we undo the change. The intent of the change
961 in 2.1.10 is to allow size selection through real dimensions,
962 which can now be done through `FT_Request_Size'.
964 - Some security issues were discovered and fixed in the CFF and
965 Type 1 loader, causing crashes of FreeType by malformed font
971 - The documentation for FT_LOAD_TARGET_XXX and FT_RENDER_MODE_XXX
972 values now better reflects its usage and differences: One set is
973 used to specify the hinting algorithm, the other to specify the
974 pixel rendering mode.
976 - `FT_New_Face' and `FT_New_Face_From_FSSpec' in ftmac.c have been
977 changed to count supported scalable faces (sfnt, LWFN) only, and
978 to return the number of available faces via face->num_faces.
979 Unsupported bitmap faces (fbit, NFNT) are ignored.
981 - builds/unix/configure has been improved for MacOS X. It now
982 automatically checks available functions in Carbon library, and
983 prepare to use newest functions by default. Options to specify
984 the dependencies of each Carbon APIs (FSSpec, FSRef, old/new
985 QuickDraw, ATS) are available too. By manual disabling of all
986 QuickDraw functionality, FreeType can be built without
987 `deprecated function' warnings on MacOS 10.4.x, but
988 FT_GetFile_Mac_Name in ftmac.c then is changed to a dummy
989 function, and returns an `unimplemented' error. For details see
992 - SFNT cmap handling has been improved, mainly to run much faster
995 - A new function `FT_Get_TrueType_Engine_Type (declared in
996 `FT_MODULE_H') is provided to determine the status of the
997 TrueType bytecode interpreter compiled into the library
998 (patented, unpatented, unimplemented).
1000 - Vertical metrics of glyphs are synthesized if the font does not
1001 provide such information. You can tell whether the metrics are
1002 synthesized or not by checking the FT_FACE_FLAG_VERTICAL flag of
1005 - The demo programs `ftview' and `ftstring' have been rewritten
1006 for better readability. `ftview' has a new switch `-p' to test
1007 FT_New_Memory_Face (instead of FT_New_Face).
1009 - FreeType now honours bit 1 in the `head' table of TrueType fonts
1010 (meaning `left sidebearing point at x=0'). This helps with some
1013 - Rudimentary support for Adobe's new `SING Glyphlet' format. See
1015 http://www.adobe.com/products/indesign/sing_gaiji.html
1017 for more information.
1019 - The `ftdump' program from the `ft2demos' bundle now shows some
1020 information about charmaps. It also supports a new switch `-v'
1021 to increase verbosity.
1023 - Better AFM support. This includes track kerning support.
1026 ======================================================================
1028 CHANGES BETWEEN 2.1.10 and 2.1.9
1030 I. IMPORTANT BUG FIXES
1032 - The size comparison for BDF and PCF files could fail sometimes.
1034 - Some CFF files were still not loaded correctly. Patch from
1037 - The stroker still had some serious bugs.
1039 - Boris Letocha fixed a bug in the TrueType interpreter: The
1040 NPUSHW instruction wasn't skipped correctly in IF clauses. Some
1041 fonts like `Helvetica 75 Bold' failed.
1043 - Another serious bug in handling TrueType hints caused many
1044 distortions. It has been introduced in version 2.1.8, and it is
1045 highly recommended to upgrade.
1047 - FreeType didn't properly parse empty Type 1 glyphs.
1049 - An unbound dynamic buffer growth was fixed in the PFR loader.
1051 - Several bugs have been fixed in the cache sub-system.
1053 - FreeType behaved incorrectly when resizing two distinct but very
1054 close character pixel sizes through `FT_Set_Char_Size' (Savannah
1057 - The auto-hinter didn't work properly for fonts without a Unicode
1058 charmap -- it even refused to load the glyphs.
1061 II. IMPORTANT CHANGES
1063 - Many fixes have been applied to drastically reduce the amount of
1064 heap memory used by FreeType, especially when using
1065 memory-mapped font files (which is the default on Unix systems
1066 which support them).
1068 - The auto-hinter has been replaced with a new module, called the
1069 `auto-fitter'. It consumes less memory than its predecessor,
1070 and it is prepared to support non-latin scripts better in next
1073 - George Williams contributed code to read kerning data from PFM
1076 - FreeType now uses the TT_NAME_ID_PREFERRED_FAMILY and
1077 TT_NAME_ID_PREFERRED_SUBFAMILY strings (if available) for
1078 setting family and style in SFNT fonts (patch from Kornfeld
1081 - A new API `FT_Sfnt_Table_Info' (in FT_TRUETYPE_TABLES_H) has
1082 been added to retrieve name and size information of SFNT tables.
1084 - A new API `FT_OpenType_Validate' (in FT_OPENTYPE_VALIDATE_H) has
1085 been added to validate OpenType tables (BASE, GDEF, GPOS, GSUB,
1086 JSTF). After validation it is no longer necessary to check
1087 for errors in those tables while accessing them.
1089 Note that this module might be moved to another library in the
1090 future to avoid a tight dependency between FreeType and the
1091 OpenType specification.
1093 - A new API in FT_BITMAP_H (`FT_Bitmap_New', `FT_Bitmap_Convert',
1094 `FT_Bitmap_Copy', `FT_Bitmap_Embolden', `FT_Bitmap_Done') has
1095 been added. Its use is to convert an FT_Bitmap structure in
1096 1bpp, 2bpp, 4bpp, or 8bpp format into another 8bpp FT_Bitmap,
1097 probably using a different pitch, and to further manipulate it.
1099 - A new API `FT_Outline_Embolden' (in FT_OUTLINE_H) gives finer
1100 control how outlines are embolded.
1102 - `FT_GlyphSlot_Embolden' (in FT_SYNTHESIS_H) now handles bitmaps
1103 also (code contributed by Chia I Wu). Note that this function
1104 is still experimental and may be replaced with a better API.
1106 - The method how BDF and PCF bitmap fonts are accessed has been
1107 refined. Formerly, FT_Set_Pixel_Sizes and FT_Set_Char_Size
1108 were synonyms in FreeType's BDF and PCF interface. This has
1109 changed now. FT_Set_Pixel_Sizes should be used to select the
1110 actual font dimensions (the `strike', which is the sum of the
1111 `FONT_ASCENT' and `FONT_DESCENT' properties), while
1112 FT_Set_Char_Size selects the `nominal' size (the `PIXELSIZE'
1113 property). In both functions, the width parameter is ignored.
1118 - The BDF driver no longer converts all returned bitmaps with a
1119 depth of 2bpp or 4bpp to a depth of 8bpp. The documentation has
1120 not mentioned this explicitly, but implementors might have
1121 relied on this after looking into the source files.
1123 - A new option `--ftversion' has been added to freetype-config to
1124 return the FreeType version.
1126 - The memory debugger has been updated to dump allocation
1127 statistics on all allocation sources in the library. This is
1128 useful to spot greedy allocations when loading and processing
1131 - We removed a huge array of constant pointers to constant strings
1132 in the `psnames' module. The problem was that compilations in
1133 PIC mode (i.e., when generating a Unix shared object/dll) put
1134 the array into the non-shared writable section of the library
1135 since absolute pointers are not relocatable by nature.
1137 This reduces the memory consumption by approximately 16KByte per
1138 process linked to FreeType. We now also store the array in a
1139 compressed form (as a trie) which saves about 20KByte of code as
1142 - Kirill Smelkov provided patches to make src/raster/ftraster.c
1143 compile stand-alone again.
1146 ======================================================================
1148 CHANGES BETWEEN 2.1.9 and 2.1.8
1150 I. IMPORTANT BUG FIXES
1152 - The function `FT_Get_CharMap_Index' was only declared, without
1153 any real code. For consistency, it has been renamed to
1154 `FT_Get_Charmap_Index'. (This function is needed to implement
1157 - `FT_Outline_Get_BBox' sometimes returned incorrect values for
1158 conic outlines (e.g., for TrueType fonts).
1160 - Handling of `bhed' table has been fixed.
1162 - The TrueType driver with enabled byte code interpreter sometimes
1163 returned artifacts due to incorrect rounding. This bug has been
1164 introduced after version 2.1.4.
1166 - The BDF driver dropped the last glyph in the font.
1168 - The BDF driver now uses the DEFAULT_CHAR property (if available)
1169 to select a glyph shape for the undefined glyph.
1171 - The stroker failed for closed outlines and single points.
1174 II. IMPORTANT CHANGES
1176 - George Williams contributed code to handle Apple's font
1177 distortion technology found in GX fonts (`avar', `cvar', `fvar',
1178 and `gvar' tables; the Multiple Masters API has been slightly
1179 extended to cope with the new functionality).
1181 - The `FT_GlyphSlotRec' structure has been extended: The elements
1182 `lsb_delta' and `rsb_delta' give the difference between hinted
1183 and unhinted left and right side bearings if autohinting is
1184 active. Using those values can improve the inter-letter spacing
1185 considerably. See the documentation of `FT_GlyphSlotRec' and
1186 the `ftstring' demo program how to use it.
1188 - Loading TrueType and Type 1 fonts has been made much faster.
1190 - The stroker is no longer experimental (but the cache subsystem
1196 - A new documentation file `formats.txt' describes various font
1197 formats supported (and not supported) by FreeType.
1200 ======================================================================
1202 CHANGES BETWEEN 2.1.8 and 2.1.7
1204 I. IMPORTANT BUG FIXES
1206 - The native TrueType hinter contained some bugs which prevented
1207 some fonts to be rendered correctly, most notably Legendum.otf.
1209 - The PostScript hinter now produces improved results.
1211 - The linear advance width and height values were incorrectly
1212 rounded, making them virtually unusable if not loaded with
1213 FT_LOAD_LINEAR_DESIGN.
1215 - Indexing CID-keyed CFF fonts is now working: The glyph index is
1216 correctly treated as a CID, similar to FreeType's CID driver
1217 module. Note that CID CMap support is still missing.
1219 - The FT_FACE_FLAGS_GLYPH_NAMES flag is now set correctly for all
1222 - Some subsetted Type 1 fonts weren't parsed correctly. This bug
1223 has been introduced in 2.1.7. In summary, the Type 1 parser has
1226 - Non-decimal numbers weren't parsed correctly in PS fonts.
1228 - The WinFNT driver now correctly reports FT_ENCODING_NONE for all
1229 but one encoding. Use the new FT_WinFNT_ID_XXX values together
1230 with `FT_Get_WinFNT_Header' to get the WinFNT charset ID.
1232 - The descender metrics (face->size->metrics.descender) for WinFNT
1233 bitmap fonts had the wrong sign.
1235 - The (emulated) `seac' support for CFF fonts was broken.
1237 - The `flex' operator didn't work for CFF fonts.
1239 - PS glyphs which use the `hintmask' operator haven't been
1240 rendered correctly in some cases.
1242 - Metrics for BDF and PCF bitmap font formats have been fixed.
1244 - Autohinting is now disabled for glyphs which are vertically
1245 distorted or mirrored (using a transformation matrix). This
1246 fixes a bug which produced zero-height glyphs.
1248 - The `freetype-config' script now handles --prefix and
1249 --exec-prefix correctly; it also returns the proper --rpath (or
1250 -R) value if FreeType has been built as a shared library.
1253 II. IMPORTANT CHANGES
1255 - Both PCF and BDF drivers now handle the SETWIDTH_NAME and
1256 ADD_STYLE_NAME properties. Values are appended to
1257 face->style_name; example: `Bold SemiCondensed'.
1259 - The PCF driver now handles bitmap fonts compressed with the LZW
1260 algorithm (extension .pcf.Z, compressed with `compress').
1262 - A new API function `FT_Get_CMap_Language_ID' (declared in
1263 `tttables.h') is available to get the language ID of a
1266 - The hexadecimal format of data after the `StartData' command in
1267 CID-keyed Type 1 fonts is now supported. While this can't occur
1268 in file-based fonts, it can happen in document-embedded
1269 resources of PostScript documents.
1271 - Embedded bitmaps in SFNT-based CFF fonts are now supported.
1273 - A simple API is now available to control FreeType's tracing
1274 mechanism if compiled with FT_DEBUG_LEVEL_TRACE. See the file
1275 `ftdebug.h' for more details.
1277 - YAMATO Masatake contributed improved handling of MacOS resource
1278 forks on non-MacOS platforms (for example, Linux can mount MacOS
1281 - Support for MacOS has been improved; there is now a new function
1282 `FT_New_Face_From_FSSpec' similar to `FT_New_Face' except that
1283 it accepts an FSSpec instead of a path.
1285 - The cache sub-system has been rewritten.
1287 - There is now support for deinstallation of faces.
1289 - A new API function `FTC_Manager_RemoveFaceID' has been added
1290 to delete all `idle' nodes that correspond to a given
1291 FTC_FaceID. All `locked' nodes (i.e., those with a reference
1292 count > 0), will be modified to prevent them from appearing in
1293 further lookups (they will be cleaned normally when their
1294 reference count reaches 0).
1296 - There is now support for point scaling (i.e., providing
1297 character sizes in points + dpis, instead of pixels).
1299 - Three abstract cache classes are now available:
1301 FTC_GCache: Used to store one glyph item per cache node,
1302 with the ability to group common attributes into
1303 `families'. This replaces the old
1304 FTC_GlyphCache class.
1306 FTC_ICache: Used to store one FT_Glyph per cache node. This
1307 extends FTC_GCache. Family definition, family
1308 comparison, and glyph loading are however left
1311 FTC_SCache: Used to store up to 16 small bitmaps per cache
1312 node. This extends FTC_GCache. Family
1313 definition, family comparison and glyph loading
1314 are however left to sub-classes.
1316 - The file `src/cache/ftcbasic.c' implements:
1318 FTC_ImageCache: Extends FTC_ICache; implements family
1319 definitions and glyph loading similar to the
1322 FTC_SBitCache: Extends FTC_SCache, implements family
1323 definitions and glyph loading similar to the
1326 Client applications should be able to extend FTC_GCache,
1327 FTC_ICache, or FTC_SCache much more easily (i.e., less code to
1328 write, and less callbacks). For example, one could envision
1329 caches that are capable of storing transformed (obliqued),
1330 stroked, emboldened, or colored glyph images. Use
1331 `ftcbasic.c' as an example.
1333 - All public APIs are now in `include/freetype/ftcache.h', (to
1334 be accessed as `FT_CACHE_H'). The contents of
1335 `include/freetype/cache/' is only needed by applications that
1336 wish to implement their own caches.
1338 - There were some major performance improvements through the use
1339 of various programming tricks. Cache hits are up to 70%
1340 faster than in the old code.
1342 - The FTC_CMapCache has been simplified. Charmaps can only be
1343 accessed by index right now. There is also a new API named
1344 `FT_Charmap_GetIndex' for this purpose.
1346 - The demo programs have been updated to the new code. The
1347 previous versions will not work with the current one.
1349 - Using an invalid face index in FT_Open_Face and friends now
1350 causes an error even if the font contains a single face only.
1355 - Wolfgang Domröse contributed support files for building FreeType
1356 on the Atari using the PureC compiler. Note that the Atari is a
1359 - Vitaliy Pasternak contributed project files for VS.NET 2003.
1362 ======================================================================
1364 CHANGES BETWEEN 2.1.7 and 2.1.6
1366 I. IMPORTANT BUG FIXES
1368 - Updated to newest libtool version, fixing build problems on
1371 - On Unix platforms, `make install' didn't copy the correct
1374 Note that version 2.1.7 contains the same library C source code as
1378 ======================================================================
1380 CHANGES BETWEEN 2.1.6 and 2.1.5
1382 I. IMPORTANT BUG FIXES
1384 - The PFR font driver didn't load kerning tables correctly, and
1385 the functions in FT_PFR_H didn't work at all.
1387 - Type 1 font files in binary format (PFB) with an end-of-file
1388 indicator weren't accepted by the FreeType engine.
1390 - Fonts which contain /PaintType and /StrokeWidth no longer cause
1391 a segfault. This bug has been introduced in version 2.1.5.
1393 - Fonts loaded with FT_LOAD_RENDER no longer cause strange
1394 results. This bug has been introduced in version 2.1.5.
1396 - Some Windows (bitmap) FNT/FON files couldn't be handled
1400 II. IMPORTANT CHANGES
1402 - The internal module API has been heavily changed in favor of
1403 massive simplifications within the font engine. This also means
1404 that authors of third-party modules must adapt their code to the
1407 NOTE: THE NEW SCHEME IS NOT COMPLETED YET. PLEASE WAIT UNTIL A
1410 - The PostScript parser has been enhanced to handle comments and
1411 strings correctly. Additionally, more syntax forms are
1414 - Added the optional unpatented hinting system for TrueType. It
1415 allows typefaces which need hinting to produce correct glyph
1416 forms (e.g., Chinese typefaces from Dynalab) to work acceptably
1417 without infringing Apple patents. This system is compiled only
1418 if TT_CONFIG_OPTION_COMPILE_UNPATENTED_HINTING is defined in
1419 ftoption.h (activated by default).
1424 - There is now a guard in the public header files to protect
1425 against inclusion of freetype.h from FreeType 1.
1427 - Direct inclusion of freetype.h and other public header files no
1428 longer works. You have to use the documented scheme
1430 #include <ft2build.h>
1431 #include FT_FREETYPE_H
1433 to load freetype.h with a symbolic name. This protects against
1434 renaming of public header files (which shouldn't happen but
1435 actually has, avoiding two public header files with the same
1439 ======================================================================
1441 CHANGES BETWEEN 2.1.5 and 2.1.4
1443 I. IMPORTANT BUG FIXES
1445 - Parsing the /CIDFontName field now removes the leading slash to
1446 be in sync with other font drivers.
1448 - gzip support was buggy. Some fonts could not be read.
1450 - Fonts which have nested subglyphs more than one level deep no
1451 longer cause a segfault.
1453 - Creation of synthetic cmaps for fonts in CFF format was broken
1456 - Numeric font dictionary entries for synthetic fonts are no
1459 - The font matrix wasn't applied to the advance width for Type1,
1460 CID, and CFF fonts. This caused problems when loading certain
1461 synthetic Type 1 fonts like `Helvetica Narrow'.
1463 - The test for the charset registry in BDF and PCF fonts is now
1466 - FT_Vector_Rotate sometimes returned strange values due to
1469 - The PCF driver now returns the correct number of glyphs
1470 (including an artificial `notdef' glyph at index 0).
1472 - FreeType now supports buggy CMaps which are contained in many
1473 CJK fonts from Dynalab.
1475 - Opening an invalid font on a Mac caused a segfault due to
1476 double-freeing memory.
1478 - BDF fonts with more than 32768 glyphs weren't supported
1482 II. IMPORTANT CHANGES
1484 - Accessing bitmap font formats has been synchronized. To do that
1485 the FT_Bitmap_Size structure has been extended to contain new
1486 fields `size', `x_ppem', and `y_ppem'.
1488 - The FNT driver now returns multiple faces, not multiple strikes.
1490 - The `psnames' module has been updated to the Adobe Glyph List
1493 - The `psnames' module now understands `uXXXX[X[X]]' glyph names.
1495 - The algorithm for guessing the font style has been improved.
1497 - For fonts in SFNT format, root->height is no longer increased if
1498 the line gap is zero. There exist fonts (containing e.g. form
1499 drawing characters) which intentionally have a zero line gap
1502 - ft_glyph_bbox_xxx flags are now deprecated in favour of
1505 - ft_module_xxx flags are now deprecated in favour of
1508 - FT_ENCODING_MS_{SJIS,GB2312,BIG5,WANSUNG,JOHAB} are now
1509 deprecated in favour of
1510 FT_ENCODING_{SJIS,GB2312,GIB5,WANSONG,JOHAB} -- those encodings
1511 are not specific to Microsoft.
1516 - The autohinter has been further improved; for example, `m'
1517 glyphs now retain its vertical symmetry.
1519 - Partial support of Mac fonts on non-Mac platforms.
1521 - `make refdoc' (after first `make') builds the HTML
1522 documentation. You need Python for this.
1524 - The make build system should now work more reliably on DOS-like
1527 - Support for EMX gcc and Watson C/C++ compilers on MS-DOS has
1530 - Better VMS build support.
1532 - Support for the pkg-config package by providing a `freetype.pc'
1535 - New configure option --with-old-mac-fonts for Darwin.
1537 - Some source files have been renamed (mainly to fit into the 8.3
1541 ======================================================================
1543 CHANGES BETWEEN 2.1.4 and 2.1.3
1545 I. IMPORTANT BUG FIXES
1547 - Updated to newest libtool version, fixing build problems on
1550 - A fix in the Gzip stream reader: It couldn't read certain .gz
1551 files properly due to a small typo. In certain cases, FreeType
1552 could also loop endlessly when trying to load tiny gzipped
1555 - The configure script now tries to use the system-wide zlib when
1556 it finds one (instead of the copy found in src/gzip). And
1557 `freetype-config' has been updated to return relevant flags in
1558 this case when invoked with `--libs' (e.g. `-lzlib').
1560 - Certain fonts couldn't be loaded by 2.1.3 because they lacked a
1561 Unicode charmap (e.g. SYMBOL.TTF). FreeType erroneously
1564 - The CFF loader was modified to accept fonts which only contain a
1565 subset of their reference charset. This prevented the correct
1566 use of PDF-embedded fonts.
1568 - The logic to detect Unicode charmaps has been modified. This is
1569 required to support fonts which include both 16-bit and 32-bit
1570 charmaps (like very recent asian ones) using the new 10 and 12
1573 - The TrueType loader now limits the depth of composite glyphs.
1574 This is necessary to prevent broken fonts to break the engine by
1575 blowing the stack with recursive glyph definitions.
1577 - The CMap cache is now capable of managing UCS-4 character codes
1578 that are mapped through extended charmaps in recent
1579 TrueType/OpenType fonts.
1581 - The cache sub-system now properly manages out-of-memory
1582 conditions instead of blindly reporting them to the caller.
1583 This means that it will try to empty the cache before restarting
1584 its allocations to see if that can help.
1586 - The PFR driver didn't return the list of available embedded
1589 - There was a nasty memory leak when using embedded bitmaps in
1590 certain font formats.
1593 II. IMPORTANT CHANGES
1595 - David Chester contributed some enhancements to the auto-hinter
1596 that significantly increase the quality of its output. The
1597 Postscript hinter was also improved in several ways.
1599 - The FT_RENDER_MODE_LIGHT render mode was implemented.
1601 - A new API function called `FT_Get_BDF_Property' has been added
1602 to FT_BDF_H to retrieve BDF properties from BDF _and_ PCF font
1603 files. THIS IS STILL EXPERIMENTAL, since it hasn't been
1604 properly tested yet.
1606 - A Windows FNT specific API has been added, mostly to access font
1607 headers. This is used by Wine.
1609 - TrueType tables without an `hmtx' table are now tolerated when
1610 an incremental interface is used. This happens for certain
1611 Type42 fonts passed from Ghostscript to FreeType.
1613 - The PFR font driver is now capable of returning the font family
1614 and style names when they are available (instead of the sole
1615 `FontID'). This is performed by parsing an *undocumented*
1616 portion of the font file!
1621 - The path stroker in FT_STROKER_H has entered beta stage. It now
1622 works very well, but its interface might change a bit in the
1623 future. More on this in later releases.
1625 - The documentation for FT_Size_Metrics didn't appear properly in
1628 - The file docs/VERSION.DLL has been updated to explain versioning
1629 with FreeType (i.e., comparing release/libtool/so numbers, and
1630 how to use them in autoconf scripts).
1632 - The installation documentation has been seriously revamped.
1633 Everything is now in the `docs' directory.
1636 ======================================================================
1638 CHANGES BETWEEN 2.1.3 and 2.1.2
1640 I. IMPORTANT BUG FIXES
1642 - FT_Vector_Transform had been incorrectly modified in 2.1.2,
1643 resulting in incorrect transformations being applied (for
1644 example, rotations were processed in opposite angles).
1646 - The format 8 and 12 TrueType charmap enumeration routines have
1647 been fixed (FT_Get_Next_Char returned invalid values).
1649 - The PFR font driver returned incorrect advance widths if the
1650 outline and metrics resolution defined in the font file were
1653 - FT_Glyph_To_Bitmap now returns successfully when called with an
1654 FT_BitmapGlyph argument (it previously returned an error).
1656 - A bug in the Type 1 loader that prevented valid font bounding
1657 boxes to be loaded from multiple master fonts.
1659 - The SFNT validation code has been rewritten. FreeType can now
1660 load `broken' fonts that were usable on Windows, but not with
1661 previous versions of the library.
1663 - The computation of bearings in the BDF driver has been fixed.
1665 - The Postscript hinter crashed when trying to hint certain glyphs
1666 (more precisely, when trying to apply hints to an empty glyph
1669 - The TrueType glyph loader now supports composites in `Apple
1670 format' (they differ slightly from Microsoft/OpenType ones in
1671 the way transformation offsets are computed).
1673 - FreeType was very slow at opening certain asian CID/CFF fonts,
1674 due to fixed increment in dynamic array re-allocations. This
1675 has been changed to exponential behaviour to get acceptable
1680 II. IMPORTANT CHANGES
1682 - The PCF driver now supports gzip-compressed font files natively.
1683 This means that you will be able to use all these bitmap fonts
1684 that come with XFree86 with FreeType (and libXft/libXft2, by
1687 - The automatic and postscript hinters have both been updated.
1688 This results in a relatively important increase of rendering
1689 quality since many nasty defaults have been suppressed. Please
1692 http://www.freetype.org/hinting/smooth-hinting.html
1694 for additional details on this topic.
1696 - The `load_flags' parameter of `FT_Load_Glyph' is now an FT_Int32
1697 (instead of just being an FT_Int). This breaks source and
1698 binary compatibility for 16bit systems only, while retaining
1699 both of them for 32 and 64 bit ones.
1701 Some new flags have been added consequently:
1703 FT_LOAD_NO_AUTOHINT :: Disable the use of the auto-hinter
1704 (but not native format hinters).
1706 FT_LOAD_TARGET_NORMAL :: Hint and render for normal
1707 anti-aliased displays.
1709 FT_LOAD_TARGET_MONO :: Hint and render for 1-bit displays.
1711 FT_LOAD_TARGET_LCD :: Hint and render for horizontal RGB or
1712 BGR sub-pixel displays (like LCD
1713 screens). THIS IS STILL
1716 FT_LOAD_TARGET_LCD_V :: Same as FT_LOAD_TARGET_LCD, for
1717 vertical sub-pixel displays (like
1718 rotated LCD screens). THIS IS STILL
1721 FT_LOAD_MONOCHROME is still supported, but only affects
1722 rendering, not the hinting.
1724 Note that the `ftview' demo program available in the `ft2demos'
1725 package has been updated to support LCD-optimized display on
1726 non-paletted displays (under Win32 and X11).
1728 - The PFR driver now supports embedded bitmaps (all formats
1729 supported), and returns correct kerning metrics for all glyphs.
1731 - The TrueType charmap loader now supports certain `broken' fonts
1732 that load under Windows without problems.
1734 - The cache API has been slightly modified (it's still a beta!):
1736 - The type FTC_ImageDesc has been removed; it is now replaced
1737 by FTC_ImageTypeRec. Note that one of its fields is a
1738 `load_flag' parameter for FT_Load_Glyph.
1740 - The field `num_grays' of FT_SBitRec has been changed to
1741 `max_grays' in order to fit within a single byte. Its
1742 maximum value is thus 255 (instead of 256 as previously).
1747 - Added support for the DESTDIR variable during `make install'.
1748 This simplifies packaging of FreeType.
1750 - Included modified copies of the ZLib sources in `src/gzip' in
1751 order to support gzip-compressed PCF fonts. We do not use the
1752 system-provided zlib for now, though this is a probable
1753 enhancement for future releases.
1755 - The DocMaker tool used to generate the on-line API reference has
1756 been completely rewritten. It is now located in
1757 `src/tools/docmaker/docmaker.py'. Features:
1759 - better cross-referenced output
1760 - more polished output
1761 - uses Python regular expressions (though it didn't speed the
1763 - much more modular structure, which allows for different
1764 `backends' in order to generate HTML, XML, or whatever
1767 One can regenerate the API reference by calling:
1769 python src/tools/docmaker/docmaker.py \
1771 --title=FreeType-2.1.3 \
1772 --output=<outputdirectory>
1773 include/freetype/*.h \
1774 include/freetype/config/*.h \
1775 include/freetype/cache/*.h
1777 - A new, experimental, support for incremental font loading (i.e.,
1778 loading of fonts where the glyphs are not in the font file
1779 itself, but provided by an external component, like a Postscript
1780 interpreter) has been added by Graham Asher. This is still work
1781 in progress, however.
1783 - A new, EXPERIMENTAL, path stroker has been added. It doesn't
1784 suffer from severe rounding errors and treat bezier arcs
1785 directly. Still work in progress (i.e. not part of the official
1786 API). See the file <freetype/ftstroker.h> for some of the
1789 - The massive re-formatting of sources and internal re-design is
1790 still under-way. Many internal functions, constants, and types
1794 ======================================================================
1796 CHANGES BETWEEN 2.1.2 and 2.1.1
1798 I. IMPORTANT BUG FIXES
1800 - Many font drivers didn't select a Unicode charmap by default
1801 when a new face was opened (with the FT_CONFIG_OPTION_USE_CMAPS
1802 options enabled), causing many applications to not be able to
1803 display text correctly with the 2.1.x releases.
1805 - The PFR driver had a bug in its composite loading code that
1806 produces incorrectly placed accents with many fonts.
1808 - The Type42 driver crashed sometimes due to a nasty bug.
1810 - The Type 1 custom encoding charmap didn't handle the case where
1811 the first glyph index wasn't 0.
1813 - A serious typo in the TrueType composite loader produced
1814 incorrectly placed glyphs in fonts like `Wingdings' and a few
1820 - The Win32 Visual C++ project file has been updated to include
1821 the PFR driver as well.
1823 - `freetype.m4' is now installed by default by `make install' on
1826 - The function FT_Get_PS_Font_Info now works with CID and Type42
1830 ======================================================================
1832 CHANGES BETWEEN 2.1.1 and 2.1.0
1834 I. IMPORTANT BUG FIXES
1836 - The `version_info' returned by `freetype-config' in 2.1.0
1837 returned an invalid value. It now returns 9:1:3 (2.0.9 returned
1840 - Version 2.1.0 couldn't be linked against applications on Win32
1841 and Amiga systems due to a new debug function that wasn't
1842 properly propagated to the system-specific directory in
1845 - Various MacOS and Mac OS X specific fixes.
1847 - Fixed a bug in the TrueType charmap validation routines that
1848 made version 2.1.0 too restrictive -- many popular fonts have
1851 - There was still a very small difference between the monochrome
1852 glyph bitmaps produced by FreeType 1.x and FreeType 2.x with the
1853 bytecode interpreter enabled. This was caused by an invalid
1854 flag setting in the TrueType glyph loader, making the rasterizer
1855 change its drop-out control mode. Now the results should
1856 _really_ be completely identical.
1858 - The TrueType name table loader has been improved to support many
1859 popular though buggy Asian fonts. It now ignores empty name
1860 entries, invalid pointer offsets and a few other incorrect
1861 subtleties. Moreover, name strings are now loaded on demand,
1862 which reduces the memory load of many faces (e.g. the ARIAL.TTF
1863 font file contains a 10kByte name table with 70 names).
1865 - Fixed a bug in the Postscript hinter that prevented family blues
1866 substitution to happen correctly.
1871 - Three new font drivers in this release:
1873 * A BDF font driver, contributed by Franco Zappa Nardelli,
1874 heavily modified by Werner Lemberg. It also supports
1875 anti-aliased bitmaps (using a slightly extended BDF format).
1877 * A Type42 font driver, contributed by Roberto Alameda. It is
1878 still experimental but seems to work relatively well.
1880 * A PFR font driver, contributed by David Turner himself. It
1881 doesn't support PFR hinting -- note that BitStream has at
1882 least two patents on this format!
1887 - The cache sub-system has been optimized in important ways.
1888 Cache hits are now significantly faster. For example, using the
1889 CMap cache is about twice faster than calling FT_Get_Char_Index
1890 on most platforms. Similarly, using an SBit cache is about five
1891 times faster than loading the bitmaps from a bitmap file, and
1892 300 to 500 times faster than generating them from a scalable
1895 Note that you should recompile your sources if you designed a
1896 custom cache class for the FT2 Cache subsystem, since the
1897 changes performed are source, but not binary, compatible.
1900 ======================================================================
1902 CHANGES BETWEEN 2.1.0 and 2.0.9
1904 I. IMPORTANT BUG FIXES
1906 - The TrueType bytecode interpreter has been fixed to produce
1907 _exactly_ the same output as FreeType 1.x. Previous differences
1908 were due to slightly distinct fixed-point computation routines
1909 used to perform dot products and vector length measurements.
1911 It seems that native TrueType hinting is _extremely_ sensitive
1912 to rounding errors. The required vector computation routines
1913 have been optimized and placed within the `ttinterp.c' file.
1915 - Fixed the parsing of accelerator tables in the PCF font driver.
1917 - Fixed the Type1 glyph loader routine used to compute the font's
1918 maximum advance width.
1923 - The `configure' script used on Unix systems has been modified to
1924 check that GNU Make is being used to build the library.
1925 Otherwise, it will display a message proposing to use the
1926 GNUMAKE environment variable to name it.
1928 The Unix-specific file README.UNX has been modified accordingly.
1933 - The FreeType License in `docs/FTL.TXT' has been updated to
1934 include a proposed preferred disclaimer. If you are using
1935 FreeType in your products, you are encouraged (but not mandated)
1936 to use the following text in your documentation:
1939 Portions of this software are copyright © 1996-2002 The
1940 FreeType Project (www.freetype.org). All rights reserved.
1943 - The default size of the render pool has been reduced to 16kByte.
1944 This shouldn't result in any noticeable performance penalty,
1945 unless you are using the engine as-is to render very large and
1948 - The FreeType 2 redesign has begun. More information can be
1951 http://www.freetype.org/freetype2/redesign.html
1953 The following internal changes have been performed within the
1954 sources of this release:
1956 - Many internal types have been renamed to increase
1957 consistency. The following should be true, except for
1960 * All structure types have a name ending in `Rec' (short
1963 * A pointer-to-structure type has the same name as the
1964 structure, _without_ the `Rec' suffix.
1968 typedef struct FooRec_
1974 - Many internal macros have been renamed to increase
1975 consistency. The following should be true:
1977 * All macros have a name beginning with `FT_'. This
1978 required a few changes like
1982 REALLOC => FT_REALLOC
1984 * All macros are completely UPPERCASE. This required a
1987 READ_Short => FT_READ_SHORT
1988 NEXT_Short => FT_NEXT_SHORT
1989 GET_ULongLE => FT_GET_ULONG_LE
1990 MEM_Set => FT_MEM_SET
1991 MEM_Copy => FT_MEM_COPY
1994 * Whenever possible, all macro names follow the
1995 FT_<OBJECT>_<METHOD> pattern. For example
1997 ACCESS_Frame => FT_FRAME_ENTER
1998 FORGET_Frame => FT_FRAME_EXIT
1999 EXTRACT_Frame => FT_FRAME_EXTRACT
2000 RELEASE_Frame => FT_FRAME_RELEASE
2002 FILE_Pos => FT_STREAM_POS
2003 FILE_Seek => FT_STREAM_SEEK
2004 FILE_Read => FT_STREAM_READ
2005 FILE_ReadAt => FT_STREAM_READ_AT
2006 READ_Fields => FT_STREAM_READ_FIELDS
2008 - Many internal functions have been renamed to follow the
2009 FT_<Object>_<Method> pattern. For example:
2011 FT_Seek_Stream => FT_Stream_Seek
2012 FT_Read_Stream_At => FT_Stream_ReadAt
2013 FT_Done_Stream => FT_Stream_Close
2014 FT_New_Stream => FT_Stream_Open
2015 FT_New_Memory_Stream => FT_Stream_OpenMemory
2016 FT_Extract_Frame => FT_Stream_ExtractFrame
2018 Note that method names do not contain `_'.
2020 - The FT_ALLOC_ARRAY and FT_REALLOC_ARRAY have been replaced
2021 with FT_NEW_ARRAY and FT_RENEW_ARRAY which do not take a
2022 type as the fourth argument. Instead, the array element
2023 type size is computed automatically from the type of the
2024 target pointer used.
2026 - A new object class, FT_CMap, has been introduced. These
2027 internal objects are used to model character maps. This
2028 eases the support of additional charmap types within the
2031 - A new configuration file named `ftstdlib.h' has been added
2032 to `include/freetype/config'. It is used to define aliases
2033 for _every_ routine of the ISO C library that the font
2034 engine uses. Each aliases has a `ft_' prefix
2035 (e.g. `ft_strlen' is an alias for `strlen').
2037 This is used to ease the porting of FreeType 2 to exotic
2038 runtime environments where the ISO C Library isn't available
2039 (e.g. XFree86 extension modules).
2041 More details are available in the `ChangeLog' file.
2044 ======================================================================
2046 CHANGES BETWEEN 2.0.9 and 2.0.8
2048 I. IMPORTANT BUG FIXES
2050 - Certain fonts like `foxjump.ttf' contain broken name tables with
2051 invalid entries and wild offsets. This caused FreeType to crash
2052 when trying to load them.
2054 The SFNT `name' table loader has been fixed to be able to
2055 support these strange fonts.
2057 Moreover, the code in charge of processing this table has been
2058 changed to always favour Windows-formatted entries over other
2059 ones. Hence, a font that works on Windows but not on the Mac
2060 will load cleanly in FreeType and report accurate values for
2061 Family & PostScript names.
2063 - The CID font driver has been fixed. It unfortunately returned a
2064 Postscript Font name with a leading slash, as in
2065 `/MunhwaGothic-Regular'.
2067 - FreeType 2 should now compile fine on AIX 4.3.3 as a shared
2070 - A bug in the Postscript hinter has been found and fixed,
2071 removing un-even stem widths at small pixel sizes (like 14-17).
2073 This improves the quality of a certain number of Postscript
2079 - A new function named `FT_Library_Version' has been added to
2080 return the current library's major, minor, and patch version
2081 numbers. This is important since the macros FREETYPE_MAJOR,
2082 FREETYPE_MINOR, and FREETYPE_PATCH cannot be used when the
2083 library is dynamically linked by a program.
2085 - Two new APIs have been added: `FT_Get_First_Char' and
2088 Together, these can be used to iterate efficiently over the
2089 currently selected charmap of a given face. Read the API
2090 reference for more details.
2095 - The FreeType sources are under heavy internal re-factoring. As
2096 a consequence, we have created a branch named `STABLE' on the
2097 CVS to hold all future releases/fixes in the 2.0.x family.
2099 The HEAD branch now contains the re-factored sources and
2100 shouldn't be used for testing or packaging new releases. In
2101 case you would like to access the 2.0.9 sources from our CVS
2102 repository, use the tag `VER-2-0-9'.
2105 ======================================================================
2107 CHANGES BETWEEN 2.0.8 and 2.0.7
2109 I. IMPORTANT BUG FIXES
2111 - There was a small but nasty bug in `freetype-config.in' which
2112 caused the `freetype-config' script to fail on Unix.
2114 This didn't prevent the installation of the library or even its
2115 execution, but caused problems when trying to compile many Unix
2116 packages that depend on it.
2118 - Some TrueType or OpenType fonts embedded in PDF documents do not
2119 have a 'cmap', 'post' and 'name' as is required by the
2120 specification. FreeType no longer refuses to load such fonts.
2122 - Various fixes to the PCF font driver.
2125 ======================================================================
2127 CHANGES BETWEEN 2.0.7 and 2.0.6
2129 I. IMPORTANT BUG FIXES
2131 - Fixed two bugs in the Type 1 font driver. The first one
2132 resulted in a memory leak in subtle cases. The other one caused
2133 FreeType to crash when trying to load `.gsf' files (Ghostscript
2134 so-called Postscript fonts).
2136 (This made _many_ KDE applications crash on certain systems.
2137 FreeType _is_ becoming a critical system component on Linux :-)
2139 - Fixed a memory leak in the CFF font driver.
2141 - Fixed a memory leak in the PCF font driver.
2143 - Fixed the Visual C++ project file
2144 `builds/win32/visualc/freetype.dsp' since it didn't include the
2145 Postscript hinter component, causing errors at build time.
2147 - Fixed a small rendering bug in the anti-aliased renderer that
2148 only occurred when trying to draw thin (less than 1 pixel)
2151 - Fixed `builds/unix/freetype2.a4' which is used to generate a
2152 valid `freetype2.m4' for use with autoconf.
2154 - Fixed the OpenVMS Makefiles.
2159 - Added `configure' and `install' scripts to the top-level
2160 directory. A GNU-style installation is thus now easily possible
2163 ./configure <options>
2168 ======================================================================
2170 CHANGES BETWEEN 2.0.6 and 2.0.5
2172 I. IMPORTANT BUG FIXES
2174 - It wasn't possible to load embedded bitmaps when the auto-hinter
2175 was used. This is now fixed.
2177 - The TrueType font driver didn't load some composites properly
2178 (the sub-glyphs were slightly shifted, and this was only
2179 noticeable when using monochrome rendering).
2181 - Various fixes to the auto-hinter. They merely improve the
2182 output of sans-serif fonts. Note that there are still problems
2183 with serifed fonts and composites (accented characters).
2185 - All scalable font drivers erroneously returned un-fitted glyph
2186 advances when hinting was requested. This created problems for
2187 a number of layout applications. This is a very old bug that
2188 got undetected mainly because most test/demo program perform
2189 rounding explicitly or implicitly (through the cache).
2191 - `FT_Glyph_To_Bitmap' did erroneously modify the source glyph in
2194 - `glnames.py' still contained a bug that made FreeType return
2195 invalid names for certain glyphs.
2197 - The library crashed when loading certain Type 1 fonts like
2198 `sadn.pfb' (`Stalingrad Normal'), which appear to contain
2199 pathetic font info dictionaries.
2201 - The TrueType glyph loader is now much more paranoid and checks
2202 everything when loading a given glyph image. This was necessary
2203 to avoid problems (crashes and/or memory overwrites) with broken
2204 fonts that came from a really buggy automatic font converter.
2207 II. IMPORTANT UPDATES AND NEW FEATURES
2209 - Important updates to the Mac-specific parts of the library.
2211 - The caching sub-system has been completely re-designed, and its
2212 API has evolved (the old one is still supported for backward
2215 The documentation for it is not yet completed, sorry. For now,
2216 you are encouraged to continue using the old API. However, the
2217 ftview demo program in the ft2demos package has already been
2218 updated to use the new caching functions.
2220 - A new charmap cache is provided too. See `FTC_CMapCache'. This
2221 is useful to perform character code -> glyph index translations
2222 quickly, without the need for an opened FT_Face.
2224 - A NEW POSTSCRIPT HINTER module has been added to support native
2225 hints in the following formats: PostScript Type 1, PostScript
2228 Please test! Note that the auto-hinter produces better results
2229 for a number of badly-hinted fonts (mostly auto-generated ones)
2232 - A memory debugger is now part of the standard FreeType sources.
2233 To enable it, define FT_DEBUG_MEMORY in
2234 <freetype/config/ftoption.h>, and recompile the library.
2236 Additionally, define the _environment_ variable FT_DEBUG_MEMORY
2237 and run any program using FreeType. When the library is exited,
2238 a summary of memory footprints and possible leaks will be
2241 This works transparently with _any_ program that uses FreeType.
2242 However, you will need a lot of memory to use this (allocated
2243 blocks are never released to the heap to detect double deletes
2249 - We are aware of subtle differences between the output of
2250 FreeType versions 1 and 2 when it comes to monochrome
2251 TrueType-hinted glyphs. These are most probably due to small
2252 differences in the monochrome rasterizers and will be worked out
2253 in an upcoming release.
2255 - We have decided to fork the sources in a `stable' branch, and an
2256 `unstable' one, since FreeType is becoming a critical component
2257 of many Unix systems.
2259 The next bug-fix releases of the library will be named 2.0.7,
2260 2.0.8, etc., while the `2.1' branch will contain a version of
2261 the sources where we will start major reworking of the library's
2262 internals, in order to produce FreeType 2.2.0 (or even 3.0) in a
2263 more distant future.
2265 We also hope that this scheme will allow much more frequent
2266 releases than in the past.
2269 ======================================================================
2271 CHANGES BETWEEN 2.0.5 and 2.0.4
2273 NOTE THAT 2.0.5 DOES NOT CONTAIN THE POSTSCRIPT HINTER. THIS MODULE
2274 WILL BE PART OF THE NEXT RELEASE (EITHER 2.0.6 or 2.1)
2276 - Fixed a bug that made certain glyphs, like `Cacute', `cacute' and
2277 `lslash' unavailable from Unicode charmaps of Postscript fonts.
2278 This prevented the correct display of Polish text, for example.
2280 - The kerning table of Type 1 fonts was loaded by FreeType, when its
2281 AFM file was attached to its face, but the
2282 FT_FACE_FLAG_HAS_KERNING bit flags was not set correctly,
2283 preventing FT_Get_Kerning to return meaningful values.
2285 - Improved SFNT (TrueType & OpenType) charmap support. Slightly
2286 better performance, as well as support for the new formats defined
2287 by the OpenType 1.3 specification (8, 10, and 12)
2289 - Fixed a serious typo in `src/base/ftcalc.c' which caused invalid
2290 computations in certain rare cases, producing ugly artefacts.
2292 - The size of the EM square is computed with a more accurate
2293 algorithm for Postscript fonts. The old one caused slight errors
2294 with embedded fonts found in PDF documents.
2296 - Fixed a bug in the cache manager that prevented normal LRU
2297 behaviour within the cache manager, causing unnecessary reloads
2298 (for FT_Face and FT_Size objects only).
2300 - Added a new function named `FT_Get_Name_Index' to retrieve the
2301 glyph index of a given glyph name, when found in a face.
2303 - Added a new function named `FT_Get_Postscript_Name' to retrieve
2304 the `unique' Postscript font name of a given face.
2306 - Added a new public header size named FT_SIZES_H (or
2307 <freetype/ftsizes.h>) providing new FT_Size-management functions:
2308 FT_New_Size, FT_Activate_Size, FT_Done_Size.
2310 - Fixed a reallocation bug that generated a dangling pointer (and
2311 possibly memory leaks) with Postscript fonts (in
2312 src/psaux/psobjs.c).
2314 - Many fixes for 16-bit correctness.
2316 - Removed many pedantic compiler warnings from the sources.
2318 - Added an Amiga build directory in `builds/amiga'.
2321 ======================================================================
2323 CHANGES BETWEEN 2.0.4 and 2.0.3
2325 - Fixed a rather annoying bug that was introduced in 2.0.3. Namely,
2326 the font transformation set through FT_Set_Transform was applied
2327 twice to auto-hinted glyphs, resulting in incorrectly rotated text
2330 - Fixed _many_ compiler warnings. FT2 should now compile cleanly
2331 with Visual C++'s most pedantic warning level (/W4). It already
2332 compiled fine with GCC and a few other compilers.
2334 - Fixed a bug that prevented the linear advance width of composite
2335 TrueType glyphs to be correctly returned.
2337 - Fixed the Visual C++ project files located in
2338 `builds/win32/visualc' (previous versions used older names of the
2341 - Many 32-bit constants have an `L' appended to their value, in
2342 order to improve the 16-bitness of the code. Someone is actually
2343 trying to use FT2 on an Atari ST machine!
2345 - Updated the `builds/detect.mk' file in order to automatically
2346 build FT2 on AIX systems. AIX uses `/usr/sbin/init' instead of
2347 `/sbin/init' and wasn't previously detected as a Unix platform by
2348 the FreeType build system.
2350 - Updated the Unix-specific portions of the build system (new
2351 libtool version, etc.).
2353 - The SFNT kerning loader now ensures that the table is sorted
2354 (since some problem fonts do not meet this requirement).
2357 =======================================================================
2359 CHANGES BETWEEN 2.0.3 and 2.0.2
2361 I. CHANGES TO THE MODULES / FONT DRIVERS
2363 - THE AUTO-HINTER HAS BEEN SLIGHTLY IMPROVED, in order to fix
2364 several annoying artefacts, mainly:
2366 - Blue zone alignment of horizontal stems wasn't performed
2367 correctly, resulting in artefacts like the `d' being placed
2368 one pixel below the `b' in some fonts like Time New Roman.
2370 - Overshoot thresholding wasn't performed correctly, creating
2371 unpleasant artefacts at large character pixel sizes.
2373 - Composite glyph loading has been simplified. This gets rid
2374 of various artefacts where the components of a composite
2375 glyphs were not correctly spaced.
2377 These are the last changes to the current auto-hinting module.
2378 A new hinting sub-system is currently in the work in order to
2379 support native hints in Type 1 / CFF / OpenType fonts, as well
2380 as globally improve rendering.
2382 - The PCF driver has been fixed. It reported invalid glyph
2383 dimensions for the fonts available on Solaris.
2385 - The Type 1, CID and CFF drivers have been modified to fix the
2386 computation of the EM size.
2388 - The Type 1 driver has been fixed to avoid a dangerous bug that
2389 crashed the library with non-conforming fonts (i.e. ones that do
2390 not place the .notdef glyph at position 0).
2392 - The TrueType driver had a rather subtle bug (dangling pointer
2393 when loading composite glyphs) that could crash the library in
2397 II. HIGH-LEVEL API CHANGES
2399 - The error code enumeration values have been changed. An error
2400 value is decomposed in a generic error code, and a module
2401 number. see <freetype/fterrors.h> for details.
2403 - A new public header file has been introduced, named
2404 FT_TRIGONOMETRY_H (include/freetype/fttrig.h), providing
2405 trigonometric functions to compute sines, cosines, arctangents,
2406 etc. with 16.16 fixed precision. The implementation is based on
2407 the CORDIC algorithm and is very fast while being sufficiently
2413 - Added BeOS-specific files in the old build sub-system. Note
2414 that no changes were required to compile the library with Jam.
2416 - The configuration is now capable of automatically detecting
2417 64-bit integers on a set of predefined compilers (GCC, Visual
2418 C++, Borland C++) and will use them by default. This provides a
2419 small performance boost.
2421 - A small memory leak that happened when opening 0-sized files
2422 (duh!) have been fixed.
2424 - Fixed bezier stack depth bug in the routines provided by the
2425 FT_BBOX_H header file. Also fixed similar bugs in the
2428 - The outline bounding box code has been rewritten to use direct
2429 computations, instead of bezier sub-division, to compute the
2430 exact bounding box of glyphs. This is slightly slower but more
2433 - The build system has been improved and fixed, mainly to support
2434 `make' on Windows 2000 correctly, avoid problems with `make
2435 distclean' on non Unix systems, etc.
2437 - Hexadecimal constants have been suffixed with `U' to avoid
2438 problems with certain compilers on 64-bit platforms.
2440 - A new directory named `src/tools' has been created. It contains
2441 Python scripts and simple unit test programs used to develop the
2444 - The DocMaker tool has been moved from `docs' to `src/tools' and
2445 has been updated with the following:
2447 - Now accepts the `--title=XXXX' or `-t XXXX' option from the
2448 command line to set the project's name in the generated API
2451 - Now accepts the `--output=DIR' or `-o DIR' option from the
2452 command line to set the output directory for all generated
2455 - Now accepts the `--prefix=XXXX' or `-p XXX' option from the
2456 command line to set the file prefix to use for all
2457 generated HTML files.
2459 - Now generates the current time/data on each generated page
2460 in order to distinguish between versions.
2462 DocMaker can be used with other projects now, not only FT2
2463 (e.g. MLib, FTLayout, etc.).
2466 ======================================================================
2468 CHANGES BETWEEN 2.0.2 and 2.0.1
2470 I. CHANGES TO THE MODULES / FONT DRIVERS
2472 - THE TRUETYPE BYTECODE INTERPRETER IS NOW TURNED OFF, in order to
2473 avoid legal problems with the Apple patents. It seems that we
2474 mistakenly turned this option on in previous releases of the
2477 Note that if you want to use the bytecode interpreter in order
2478 to get high-quality TrueType rendering, you will need to toggle
2479 by hand the definition of the
2480 TT_CONFIG_OPTION_BYTECODE_INTERPRETER macro in the file
2481 `include/freetype/config/ftoption.h'.
2483 - The CFF driver has been improved by Tom Kacvinsky and Sander van
2486 * Support for `seac' emulation.
2487 * Support for `dotsection'.
2488 * Support for retrieving glyph names through
2489 `FT_Get_Glyph_Name'.
2491 The first two items are necessary to correctly a large number of
2492 Type 1 fonts converted to the CFF formats by Adobe Acrobat.
2494 - The Type 1 driver was also improved by Tom & others:
2496 * Better EM size computation.
2497 * Better support for synthetic (transformed) fonts.
2498 * The Type 1 driver returns the charstrings corresponding to
2499 each glyph in the `glyph->control_data' field after a call to
2500 `FT_Load_Glyph' (thanks Ha Shao).
2502 - Various other bugfixes, including the following:
2504 * Fixed a nasty memory leak in the Type 1 driver.
2505 * The autohinter and the pcf driver used static writable data
2506 when they shouldn't.
2507 * Many casts were added to make the code more 64-bits safe. It
2508 also now compiles on Windows XP 64-bits without warnings.
2509 * Some incorrect writable statics were removed in the `autohint'
2510 and `pcf' drivers. FreeType 2 now compiles on Epoc again.
2513 II. CHANGES TO THE HIGH-LEVEL API
2515 - The library header files inclusion scheme has been changed. The
2516 old scheme looked like:
2518 #include <freetype/freetype.h>
2519 #include <freetype/ftglyph.h>
2520 #include <freetype/ftcache.h>
2521 #include <freetype/cache/ftimage.h>
2525 #include <ft2build.h>
2526 #include FT_FREETYPE_H
2529 #include FT_CACHE_IMAGE_H
2531 NOTE THAT THE OLD INCLUSION SCHEME WILL STILL WORK WITH THIS
2532 RELEASE. HOWEVER, WE DO NOT GUARANTEE THAT THIS WILL STILL BE
2533 TRUE IN THE NEXT ONE (A.K.A. FREETYPE 2.1).
2535 The file <ft2build.h> is used to define the header filename
2536 macros. The complete and commented list of macros is available
2537 in the API reference under the section name `Header File Macros'
2540 For more information, see section I of the following document:
2542 http://www.freetype.org/
2543 freetype2/docs/tutorial/step1.html
2547 http://freetype.sourceforge.net/
2548 freetype2/docs/tutorial/step1.html
2550 - Many, many comments have been added to the public source file in
2551 order to automatically generate the API Reference through the
2552 `docmaker.py' Python script.
2554 The latter has been updated to support the grouping of sections
2555 in chapters and better index sort. See:
2557 http://www.freetype.org/freetype2/docs/reference/ft2-toc.html
2560 III. CHANGES TO THE BUILD PROCESS
2562 - If you are not building FreeType 2 with its own build system
2563 (but with your own Makefiles or project files), you will need to
2564 be aware that the build process has changed a little bit.
2566 You don't need to put the `src' directory in the include path
2567 when compiling any FT2 component. Instead, simply put the
2568 component's directory in the current include path.
2570 So, if you were doing something like:
2572 cc -c -Iinclude -Isrc src/base/ftbase.c
2576 cc -c -Iinclude -Isrc/base src/base/ftbase.c
2578 If you were doing something like:
2581 cc -c -I../../include -I.. ftbase.c
2586 cc -c -I../../include ftbase.c
2589 ======================================================================
2591 CHANGES BETWEEN 2.0.1 and 2.0
2593 2.0.1 introduces a few changes:
2595 - Fixed many bugs related to the support of CFF / OpenType fonts.
2596 These formats are now much better supported though there is
2597 still work planned to deal with charset tables and PDF-embedded
2598 CFF files that use the old `seac' command.
2600 - The library could not be compiled in debug mode with a very
2601 small number of C compilers whose pre-processors didn't
2602 implement the `##' directive correctly (i.e. per se the ANSI C
2603 specification!) An elegant fix was found.
2605 - Added support for the free Borland command-line C++ Builder
2606 compiler. Use `make setup bcc32'. Also fixed a few source
2607 lines that generated new warnings with BCC32.
2609 - Fixed a bug in FT_Outline_Get_BBox when computing the extrema of
2612 - Updated the INSTALL file to add IDE compilation.
2614 - Other minor bug fixes, from invalid Type 1 style flags to
2615 correct support of synthetic (obliqued) fonts in the
2616 auto-hinter, better support for embedded bitmaps in a SFNT font.
2618 - Fixed some problems with `freetype-config'.
2620 Finally, the `standard' scheme for including FreeType headers is now
2621 gradually changing, but this will be explained in a later release
2624 And very special thanks to Tom Kacvinsky and YAMANO-UCHI Hidetoshi
2625 for their contributions!
2628 ======================================================================
2630 CHANGES BETWEEN beta8 and 2.0
2632 - Changed the default installation path for public headers from
2633 `include/freetype' to `include/freetype2'.
2635 Also added a new `freetype-config' that is automatically generated
2636 and installed on Unix and Cygwin systems. The script itself is
2637 used to retrieve the current install path, C compilation flags as
2638 well as linker flags.
2640 - Fixed several small bugs:
2642 * Incorrect max advance width for fixed-pitch Type 1 fonts.
2643 * Incorrect glyph names for certain TrueType fonts.
2644 * The glyph advance was not copied when FT_Glyph_To_Bitmap was
2646 * The linearHoriAdvance and linearVertAdvance fields were not
2647 correctly returned for glyphs processed by the auto-hinter.
2648 * `type1z' renamed back to `type1'; the old `type1' module has
2651 - Revamped the build system to make it a lot more generic. This
2652 will allow us to re-use nearly un-modified in lots of other
2653 projects (including FreeType Layout).
2655 - Changed `cid' to use `psaux' too.
2657 - Added the cache sub-system. See <freetype/ftcache.h> as well as
2658 the sources in `src/cache'. Note that it compiles but is still
2661 - Updated `docs/docmaker.py', a draft API reference is available at
2662 http://www.freetype.org/ft2api.html.
2664 - Changed `type1' to use `psaux'.
2666 - Created a new module named `psaux' to hold the Type 1 & Type 2
2667 parsing routines. It should be used by `type1', `cid', and `cff'
2670 - Fixed an important bug in `FT_Glyph_Get_CBox'.
2672 - Fixed some compiler warnings that happened since the TrueType
2673 bytecode decoder was deactivated by default.
2675 - Fixed two memory leaks:
2677 * The memory manager (16 bytes) isn't released in
2679 * Using custom input streams, the copy of the original stream was
2682 - Fixed the auto-hinter by performing automatic computation of the
2683 `filling direction' of each glyph. This is done through a simple
2684 and fast approximation, and seems to work (problems spotted by
2685 Werner though). The Arphic fonts are a lot nicer though there are
2686 still a lot of things to do to handle Asian fonts correctly.
2689 ======================================================================
2691 BETA-8 (RELEASE CANDIDATE) CHANGES
2693 - Deactivated the TrueType bytecode interpreter by default.
2695 - Deactivated the `src/type1' font driver. Now `src/type1z' is used
2698 - Updates to the build system. We now compile the library correctly
2699 under Unix system through `configure' which is automatically
2700 called on the first `make' invocation.
2702 - Added the auto-hinting module! Fixing some bugs here and there.
2704 - Found some bugs in the composite loader (seac) of the Type1-based
2707 - Renamed the directory `freetype2/config' to `freetype2/builds' and
2708 updated all relevant files.
2710 - Found a memory leak in the `type1' driver.
2712 - Incorporated Tom's patches to support flex operators correctly in
2713 OpenType/CFF fonts. Now all I need is to support pure CFF and CEF
2714 fonts to be done with this driver :-)
2716 - Added the Windows FNT/FON driver in `src/winfonts'. For now, it
2717 always `simulates' a Unicode charmap, so it shouldn't be
2718 considered completed right now.
2720 It is there to be more a proof of concept than anything else
2721 anyway. The driver is a single C source file, that compiles to 3
2724 I'm still working on the PCF/BDF drivers, but I'm too lazy to
2727 - CHANGES TO THE HIGH-LEVEL API
2729 * FT_Get_Kerning has a new parameter that allows you to select the
2730 coordinates of the kerning vector (font units, scaled, scaled +
2732 * The outline functions are now in <freetype/ftoutln.h> and not
2733 part of <freetype/freetype.h> anymore.
2734 * <freetype/ftmodule.h> now contains declarations for
2735 FT_New_Library, FT_Done_Library, FT_Add_Default_Modules.
2736 * The so-called convenience functions have moved from `ftoutln.c'
2737 to `ftglyph.c', and are thus available with this optional
2738 component of the library. They are declared in
2739 <freetype/ftglyph.h> now.
2740 * Anti-aliased rendering is now the default for FT_Render_Glyph
2741 (i.e. corresponds to render_mode == 0 == ft_render_mode_normal).
2742 To generate a monochrome bitmap, use ft_render_mode_mono, or the
2743 FT_LOAD_MONOCHROME flag in FT_Load_Glyph/FT_Load_Char.
2744 FT_LOAD_ANTI_ALIAS is still defined, but values to 0.
2745 * <freetype/freetype.h> now include <freetype/config/ftconfig.h>,
2746 solving a few headaches :-)
2747 * The type FT_GlyphSlotRec has now a `library' field.
2749 - CHANGES TO THE `ftglyph.h' API
2751 This API has been severely modified in order to make it simpler,
2752 clearer, and more efficient. It certainly now looks like a real
2753 `glyph factory' object, and allows client applications to manage
2754 (i.e. transform, bbox and render) glyph images without ever
2755 knowing their original format.
2757 - Added support for CID-keyed fonts to the CFF driver. Maybe
2758 support for pure CFF + CEF fonts should come in?
2760 - Cleaned up source code in order to avoid two functions with the
2761 same name. Also changed the names of the files in `type1z' from
2762 `t1XXXX' to `z1XXXX' in order to avoid any conflicts.
2764 `make multi' now works well :-)
2766 Also removed the use of `cidafm' for now, even if the source files
2767 are still there. This functionality will certainly go into a
2770 - ADDED SUPPORT FOR THE AUTO-HINTER
2772 It works :-) I have a demo program which simply is a copy of
2773 `ftview' that does a `FT_Add_Module(library,
2774 &autohinter_module_class)' after library initialization, and Type
2775 1 & OpenType/CFF fonts are now hinted.
2777 CID fonts are not hinted, as they include no charmap and the
2778 auto-hinter doesn't include `generic' global metrics computations
2781 Now, I need to release this thing to the FreeType 2 source.
2783 - CHANGES TO THE RENDERER MODULES
2785 The monochrome and smooth renderers are now in two distinct
2786 directories, namely `src/raster1' and `src/smooth'. Note that the
2787 old `src/renderer' is now gone.
2789 I ditched the 5-gray-levels renderers. Basically, it involved a
2790 simple #define toggle in 'src/raster1/ftraster.c'.
2792 FT_Render_Glyph, FT_Outline_Render & FT_Outline_Get_Bitmap now
2793 select the best renderer available, depending on render mode. If
2794 the current renderer for a given glyph image format isn't capable
2795 of supporting the render mode, another one will be found in the
2796 library's list. This means that client applications do not need
2797 to switch or set the renderers themselves (as in the latest
2798 change), they'll get what they want automatically. At last.
2800 Changed the demo programs accordingly.
2802 - MAJOR INTERNAL REDESIGN:
2804 A lot of internal modifications have been performed lately on the
2805 source in order to provide the following enhancements:
2807 * More generic module support:
2809 The FT_Module type is now defined to represent a handle to a
2810 given module. The file <freetype/ftmodule.h> contains the
2811 FT_Module_Class definition, as well as the module-loading public
2814 The FT_Driver type is still defined, and still represents a
2815 pointer to a font driver. Note that FT_Add_Driver is replaced
2816 by FT_Add_Module, FT_Get_Driver by FT_Get_Module, etc.
2818 * Support for generic glyph image types:
2820 The FT_Renderer type is a pointer to a module used to perform
2821 various operations on glyph image.
2823 Each renderer is capable of handling images in a single format
2824 (e.g. ft_glyph_format_outline). Its functions are used to:
2826 - transform an glyph image
2827 - render a glyph image into a bitmap
2828 - return the control box (dimensions) of a given glyph image
2830 The scan converters `ftraster.c' and `ftgrays.c' have been moved
2831 to the new directory `src/renderer', and are used to provide two
2832 default renderer modules.
2834 One corresponds to the `standard' scan-converter, the other to
2837 he current renderer can be set through the new function
2840 The old raster-related function FT_Set_Raster, FT_Get_Raster and
2841 FT_Set_Raster_Mode have now disappeared, in favor of the new:
2846 See the file <freetype/ftrender.h> for more details.
2848 These changes were necessary to properly support different
2849 scalable formats in the future, like bi-color glyphs, etc.
2851 * Glyph loader object:
2853 A new internal object, called a 'glyph loader' has been
2854 introduced in the base layer. It is used by all scalable format
2855 font drivers to load glyphs and composites.
2857 This object has been created to reduce the code size of each
2858 driver, as each one of them basically re-implemented its
2861 See <freetype/internal/ftobjs.h> and the FT_GlyphLoader type for
2864 * FT_GlyphSlot has new fields:
2866 In order to support extended features (see below), the
2867 FT_GlyphSlot structure has a few new fields:
2871 This field gives the linearly scaled (i.e. scaled but
2872 unhinted) advance width for the glyph, expressed as a 16.16
2873 fixed pixel value. This is useful to perform WYSIWYG text.
2876 This field gives the linearly scaled advance height for the
2877 glyph (relevant in vertical glyph layouts only). This is
2878 useful to perform WYSIWYG text.
2880 Note that the two above field replace the removed `metrics2'
2881 field in the glyph slot.
2884 This field is a vector that gives the transformed advance for
2885 the glyph. By default, it corresponds to the advance width,
2886 unless FT_LOAD_VERTICAL_LAYOUT was specified when calling
2887 FT_Load_Glyph or FT_Load_Char.
2890 This field gives the distance in integer pixels from the
2891 current pen position to the left-most pixel of a glyph image
2892 IF IT IS A BITMAP. It is only valid when the `format' field
2893 is set to `ft_glyph_format_bitmap', for example, after calling
2894 the new function FT_Render_Glyph.
2897 This field gives the distance in integer pixels from the
2898 current pen position (located on the baseline) to the top-most
2899 pixel of the glyph image IF IT IS A BITMAP. Positive values
2900 correspond to upwards Y.
2903 This is a new private field for the glyph slot. Client
2904 applications should not touch it.
2907 * Support for transforms and direct rendering in FT_Load_Glyph:
2909 Most of the functionality found in <freetype/ftglyph.h> has been
2910 moved to the core library. Hence, the following:
2912 - A transform can be specified for a face through
2913 FT_Set_Transform. this transform is applied by FT_Load_Glyph
2914 to scalable glyph images (i.e. NOT TO BITMAPS) before the
2915 function returns, unless the bit flag FT_LOAD_IGNORE_TRANSFORM
2916 was set in the load flags.
2918 - Once a glyph image has been loaded, it can be directly
2919 converted to a bitmap by using the new FT_Render_Glyph
2920 function. Note that this function takes the glyph image from
2921 the glyph slot, and converts it to a bitmap whose properties
2922 are returned in `face.glyph.bitmap', `face.glyph.bitmap_left'
2923 and `face.glyph.bitmap_top'. The original native image might
2924 be lost after the conversion.
2926 - When using the new bit flag FT_LOAD_RENDER, the FT_Load_Glyph
2927 and FT_Load_Char functions will call FT_Render_Glyph
2928 automatically when needed.
2930 - Reformatted all modules source code in order to get rid of the
2931 basic data types redifinitions (i.e. `TT_Int' instead of `FT_Int',
2932 `T1_Fixed' instead of `FT_Fixed'). Hence the format-specific
2933 prefixes like `TT_', `T1_', `T2_' and `CID_' are only used for
2934 relevant structures.
2937 ======================================================================
2939 OLD CHANGES FOR BETA 7
2941 - bug-fixed the OpenType/CFF parser. It now loads and displays my
2942 two fonts nicely, but I'm pretty certain that more testing is
2945 - fixed the crummy Type 1 hinter, it now handles accented characters
2946 correctly (well, the accent is not always well placed, but that's
2949 - added the CID-keyed Type 1 driver in `src/cid'. Works pretty well
2950 for only 13 Kb of code ;-) Doesn't read AFM files though, nor the
2951 really useful CMAP files..
2953 - fixed two bugs in the smooth renderer (src/base/ftgrays.c).
2954 Thanks to Boris Letocha for spotting them and providing a fix.
2956 - fixed potential `divide by zero' bugs in ftcalc.c.
2958 - added source code for the OpenType/CFF driver (still incomplete
2961 - modified the SFNT driver slightly to perform more robust header
2962 checks in TT_Load_SFNT_Header. This prevents certain font files
2963 (e.g. some Type 1 Multiple Masters) from being incorrectly
2964 `recognized' as TrueType font files..
2966 - moved a lot of stuff from the TrueType driver to the SFNT module,
2967 this allows greater code re-use between font drivers
2968 (e.g. TrueType, OpenType, Compact-TrueType, etc..)
2970 - added a tiny segment cache to the SFNT Charmap 4 decoder, in order
2971 to minimally speed it up..
2973 - added support for Multiple Master fonts in `type1z'. There is
2974 also a new file named <freetype/ftmm.h> which defines functions to
2975 manage them from client applications.
2977 The new file `src/base/ftmm.c' is also optional to the engine..
2979 - various formatting changes (e.g. EXPORT_DEF -> FT_EXPORT_DEF) +
2980 small bug fixes in FT_Load_Glyph, the `type1' driver, etc..
2982 - a minor fix to the Type 1 driver to let them apply the font matrix
2983 correctly (used for many oblique fonts..)
2985 - some fixes for 64-bit systems (mainly changing some FT_TRACE calls
2986 to use %p instead of %lx). Thanks to Karl Robillard.
2988 - fixed some bugs in the sbit loader (src/base/sfnt/ttsbit.c) +
2989 added a new flag, FT_LOAD_CROP_BITMAP to query that bitmaps be
2990 cropped when loaded from a file (maybe I should move the bitmap
2991 cropper to the base layer ??).
2993 - changed the default number of gray levels of the smooth renderer
2994 to 256 (instead of the previous 128). Of course, the human eye
2995 can't see any difference ;-)
2997 - removed TT_MAX_SUBGLYPHS, there is no static limit on the number
2998 of subglyphs in a TrueType font now..
3001 ======================================================================
3003 OLD CHANGES 16 May 2000
3005 - tagged `BETA-6' in the CVS tree. This one is a serious release
3006 candidate even though it doesn't incorporate the auto-hinter yet..
3008 - various obsolete files were removed, and copyright header updated
3010 - finally updated the standard raster to fix the monochrome
3011 rendering bug + re-enable support for 5-gray levels anti-aliasing
3014 - created new header files, and modified sources accordingly:
3016 <freetype/fttypes.h>
3017 - simple FreeType types, without the API
3018 <freetype/internal/ftmemory.h>
3019 - definition of memory-management macros
3021 - added the `DSIG' (OpenType Digital Signature) tag to
3024 - light update/cleaning of the build system + changes to the sources
3025 in order to get rid of _all_ compiler warnings with three
3028 gcc with `-ansi -pedantic -Wall -W', Visual C++ with `/W3 /WX' and
3031 IMPORTANT NOTE FOR WIN32-LCC USERS:
3033 | It seems the C pre-processor that comes with LCC is broken, it
3034 | doesn't recognize the ANSI standard directives # and ##
3035 | correctly when one of the argument is a macro. Also,
3038 | #define F(x) print##x
3042 | will get incorrectly translated to:
3046 | by its pre-processor. For this reason, you simply cannot build
3047 | FreeType 2 in debug mode with this compiler..
3049 - yet another massive grunt work. I've changed the definition of
3050 the EXPORT_DEF, EXPORT_FUNC, BASE_DEF & BASE_FUNC macros. These
3051 now take an argument, which is the function's return value type.
3053 This is necessary to compile FreeType as a DLL on Windows and
3054 OS/2. Depending on the compiler used, a compiler-specific keyword
3055 like __export or __system must be placed before (VisualC++) or
3056 after (BorlandC++) the type..
3058 Of course, this needed a lot of changes throughout the source code
3059 to make it compile again... All cleaned up now, apparently..
3061 Note also that there is a new EXPORT_VAR macro defined to allow
3062 the _declaration_ of an exportable public (constant)
3063 variable. This is the case of the raster interfaces (see
3064 ftraster.h and ftgrays.h), as well as each module's interface (see
3065 sfdriver.h, psdriver.h, etc..)
3067 - new feature: it is now possible to pass extra parameters to font
3068 drivers when creating a new face object. For now,
3069 this capability is unused. It could however prove to
3070 be useful in a near future..
3072 the FT_Open_Args structure was changes, as well as the internal
3073 driver interface (the specific `init_face' module function has
3074 now a different signature).
3076 - updated the tutorial (not finished though).
3078 - updated the top-level BUILD document
3080 - fixed a potential memory leak that could occur when loading
3083 - added the declaration of FT_New_Memory_Face in
3084 <freetype/freetype.h>, as it was missing from the public header
3085 (the implementation was already in `ftobjs.c').
3087 - the file <freetype/fterrors.h> has been seriously updated in order
3088 to allow the automatic generation of error message tables. See
3089 the comments within it for more information.
3091 - major directory hierarchy re-organisation. This was done for two
3094 * first, to ease the `manual' compilation of the library by
3095 requiring at lot less include paths :-)
3097 * second, to allow external programs to effectively access
3098 internal data fields. For example, this can be extremely
3099 useful if someone wants to write a font producer or a font
3100 manager on top of FreeType.
3102 Basically, you should now use the 'freetype/' prefix for header
3105 #include <freetype/freetype.h>
3106 #include <freetype/ftglyph.h>
3108 Some new include sub-directories are available:
3110 a. the `freetype/config' directory, contains two files used to
3111 configure the build of the library. Client applications
3112 should not need to look at these normally, but they can if
3115 #include <freetype/config/ftoption.h>
3116 #include <freetype/config/ftconfig.h>
3118 b. the `freetype/internal' directory, contains header files that
3119 describes library internals. These are the header files that
3120 were previously found in the `src/base' and `src/shared'
3124 As usual, the build system and the demos have been updated to
3125 reflect the change..
3127 Here's a layout of the new directory hierarchy:
3156 Compiling a module is now much easier, for example, the following
3157 should work when in the TOP_DIR directory on an ANSI build:
3159 gcc -c -I./include -I./src/base src/base/ftbase.c
3160 gcc -c -I./include -I./src/sfnt src/sfnt/sfnt.c
3163 (of course, using -Iconfig/<system> if you provide system-specific
3164 configuration files).
3166 - updated the structure of FT_Outline_Funcs in order to allow direct
3167 coordinate scaling within the outline decomposition routine (this
3168 is important for virtual `on' points with TrueType outlines) +
3169 updates to the rasters to support this..
3171 - updated the OS/2 table loading code in `src/sfnt/ttload.c' in
3172 order to support version 2 of the table (see OpenType 1.2 spec)
3174 - created `include/tttables.h' and `include/t1tables.h' to allow
3175 client applications to access some of the SFNT and T1 tables of a
3176 face with a procedural interface (see `FT_Get_Sfnt_Table') +
3177 updates to internal source files to reflect the change..
3179 - some cleanups in the source code to get rid of warnings when
3180 compiling with the `-Wall -W -ansi -pedantic' options in gcc.
3182 - debugged and moved the smooth renderer to `src/base/ftgrays.c' and
3183 its header to `include/ftgrays.h'
3185 - updated TT_MAX_SUBGLYPHS to 96 as some CJK fonts have composites
3186 with up to 80 sub-glyphs !! Thanks to Werner
3189 ======================================================================
3191 OLD CHANGES - 14-apr-2000
3193 - fixed a bug in the TrueType glyph loader that prevented the
3194 correct loading of some CJK glyphs in mingli.ttf
3196 - improved the standard Type 1 hinter in `src/type1'
3198 - fixed two bugs in the experimental Type 1 driver in `src/type1z'
3199 to handle the new XFree86 4.0 fonts (and a few other ones..)
3201 - the smooth renderer is now complete and supports sub-banding to
3202 render large glyphs at high speed. However, it is still located
3203 in `demos/src/ftgrays.c' and should move to the library itself in
3204 the next beta. NOTE: The smooth renderer doesn't compile in
3205 stand-alone mode anymore, but this should be fixed RSN..
3207 - introduced convenience functions to more easily deal with glyph
3208 images, see `include/ftglyph.h' for more details, as well as the
3209 new demo program named `demos/src/ftstring.c' that demonstrates
3212 - implemented FT_LOAD_NO_RECURSE in both the TrueType and Type 1
3213 drivers (this is required by the auto-hinter to improve its
3216 - changed the raster interface, in order to allow client
3217 applications to provide their own span-drawing callbacks.
3218 However, only the smooth renderer supports this. See
3219 `FT_Raster_Params' in the file `include/ftimage.h'.
3221 - fixed a small bug in FT_MulFix that caused incorrect transform
3224 - Note: The tutorial is out-of-date.
3227 ======================================================================
3229 OLD CHANGES - 12-mar-2000
3231 - changed the layout of configuration files : now, all ANSI
3232 configuration files are located in
3233 `freetype2/config'. System-specific over-rides can be placed in
3234 `freetype2/config/<system>'.
3236 - moved all configuration macros to `config/ftoption.h'
3238 - improvements in the Type 1 driver with AFM support
3240 - changed the fields in the FT_Outline structure : the old `flags'
3241 array is re-named `tags', while all ancient flags are encoded into
3242 a single unsigned int named `flags'.
3244 - introduced new flags in FT_Outline.flags (see
3245 ft_outline_.... enums in `ftimage.h').
3247 - changed outline functions to `FT_Outline_<action>' syntax
3249 - added a smooth anti-alias renderer to the demonstration programs
3251 - added Mac graphics driver (thanks Just)
3253 - FT_Open_Face changed in order to received a pointer to a
3254 FT_Open_Args descriptor..
3256 - various cleanups, a few more API functions implemented (see
3262 ======================================================================
3264 OLD CHANGES - 22-feb-2000
3266 - introduced the `psnames' module. It is used to:
3268 o convert a Postscript glyph name into the equivalent Unicode
3269 character code (used by the Type 1 driver(s) to synthesize on
3270 the fly a Unicode charmap).
3272 o provide an interface to retrieve the Postscript names of the
3273 Macintosh, Adobe Standard & Adobe Expert character codes.
3274 (the Macintosh names are used by the SFNT-module postscript
3275 names support routines, while the other two tables are used by
3276 the Type 1 driver(s)).
3278 - introduced the `type1z' alternate Type 1 driver. This is a (still
3279 experimental) driver for the Type 1 format that will ultimately
3280 replace the one in `src/type1'. It uses pattern matching to load
3281 data from the font, instead of a finite state analyzer. It works
3282 much better than the `old' driver with `broken' fonts. It is also
3283 much smaller (under 15 Kb).
3285 - the Type 1 drivers (both in `src/type1' and `src/type1z') are
3286 nearly complete. They both provide automatic Unicode charmap
3287 synthesis through the `psnames' module. No re-encoding vector is
3288 needed. (note that they still leak memory due to some code
3289 missing, and I'm getting lazy).
3291 Trivial AFM support has been added to read kerning information but
3292 wasn't exactly tested as it should ;-)
3294 - The TrueType glyph loader has been seriously rewritten (see the
3295 file `src/truetype/ttgload.c'. It is now much, much simpler as
3296 well as easier to read, maintain and understand :-) Preliminary
3297 versions introduced a memory leak that has been reported by Jack
3298 Davis, and is now fixed..
3300 - introduced the new `ft_glyph_format_plotter', used to represent
3301 stroked outlines like Windows `Vector' fonts, and certain Type 1
3302 fonts like `Hershey'. The corresponding raster will be written
3305 - FT_New_Memory_Face is gone. Likewise, FT_Open_Face has a new
3306 interface that uses a structure to describe the input stream, the
3307 driver (if required), etc..
3312 - Write FT_Get_Glyph_Bitmap and FT_Load_Glyph_Bitmap
3314 - Add a function like FT_Load_Character(face, char_code, load_flags)
3315 that would really embed a call to FT_Get_Char_Index then
3316 FT_Load_Glyph to ease developer's work.
3318 - Update the tutorial!
3320 - consider adding support for Multiple Master fonts in the Type 1
3323 - Test the AFM routines of the Type 1 drivers to check that kerning
3324 information is returned correctly.
3326 - write a decent auto-gridding component !! We need this to release
3332 - add a CFF/Type2 driver
3334 - add a FNT/PCF/HBF driver
3335 - add a Speedo driver from the X11 sources
3338 ======================================================================
3340 OLDER CHANGES - 27-jan-2000
3342 - updated the `sfnt' module interface to allow several SFNT-based
3343 drivers to co-exist peacefully
3345 - updated the `T1_Face' type to better separate Postscript font
3346 content from the rest of the FT_Face structure. Might be used
3347 later by the CFF/Type2 driver..
3349 - added an experimental replacement Type 1 driver featuring advanced
3350 (and speedy) pattern matching to retrieve the data from postscript
3353 - very minor changes in the implementation of FT_Set_Char_Size and
3354 FT_Set_Pixel_Sizes (they now implement default to lighten the font
3358 ======================================================================
3362 This file summarizes the changes that occurred since the last `beta'
3363 of FreeType 2. Because the list is important, it has been divided into
3368 I High-Level Interface (easier !)
3369 II Directory Structure
3370 III Glyph Image Formats
3376 ----------------------------------------------------------------------
3378 High-Level Interface:
3380 The high-level API has been considerably simplified. Here is how:
3382 - resource objects have disappeared. this means that face objects
3383 can now be created with a single function call (see FT_New_Face
3386 - when calling either FT_New_Face & FT_Open_Face, a size object
3387 and a glyph slot object are automatically created for the face,
3388 and can be accessed through `face->glyph' and `face->size' if
3389 one really needs to. In most cases, there's no need to call
3390 FT_New_Size or FT_New_Glyph.
3392 - similarly, FT_Load_Glyph now only takes a `face' argument
3393 (instead of a glyph slot and a size). Also, its `result'
3394 parameter is gone, as the glyph image type is returned in the
3395 field `face->glyph.format'
3397 - the list of available charmaps is directly accessible through
3398 `face->charmaps', counting `face->num_charmaps' elements. Each
3399 charmap has an 'encoding' field which specifies which known
3400 encoding it deals with. Valid values are, for example:
3402 ft_encoding_unicode (for ASCII, Latin-1 and Unicode)
3403 ft_encoding_apple_roman
3405 ft_encoding_adobe_standard
3406 ft_encoding_adobe_expert
3408 other values may be added in the future. Each charmap still
3409 holds its `platform_id' and `encoding_id' values in case the
3410 encoding is too exotic for the current library
3413 ----------------------------------------------------------------------
3415 Directory Structure:
3417 Should seem obvious to most of you:
3420 config/ -- configuration sub-makefiles
3422 unix/ -- platform-specific configuration files
3427 include/ -- public header files, those to be included
3428 directly by client apps
3430 src/ -- sources of the library
3431 base/ -- the base layer
3432 sfnt/ -- the sfnt `driver' (see the drivers section
3434 truetype/ -- the truetype driver
3435 type1/ -- the type1 driver
3436 shared/ -- some header files shared between drivers
3438 demos/ -- demos/tools
3440 docs/ -- documentation (a bit empty for now)
3443 ----------------------------------------------------------------------
3445 Glyph Image Formats:
3447 Drivers are now able to register new glyph image formats within the
3448 library. For now, the base layer supports of course bitmaps and
3449 vector outlines, but one could imagine something different like
3450 colored bitmaps, bi-color vectors or whatever else (Metafonts anyone
3453 See the file `include/ftimage.h'. Note also that the type
3454 FT_Raster_Map is gone, and is now replaced by FT_Bitmap, which
3455 should encompass all known bitmap types.
3457 Each new image format must provide at least one `raster', i.e. a
3458 module capable of transforming the glyph image into a bitmap. It's
3459 also possible to change the default raster used for a given glyph
3462 The default outline scan-converter now uses 128 levels of grays by
3463 default, which tends to smooth many things. Note that the demo
3464 programs have been updated significantly in order to display these..
3467 ----------------------------------------------------------------------
3471 You still need GNU Make to build the library. The build system has
3472 been very seriously re-vamped in order to provide things like :
3474 - automatic host platform detection (reverting to 'config/ansi' if
3475 it is not detected, with pseudo-standard compilation flags)
3477 - the ability to compile from the Makefiles with very different and
3478 exotic compilers. Note that linking the library can be difficult
3481 For example, the file `config/win32/lcclib.bat' is invoked by the
3482 build system to create the `.lib' file with LCC-Win32 because its
3483 librarian has too many flaws to be invoked directly from the
3486 Here's how it works:
3488 - the first time you type `make', the build system runs a series of
3489 sub-makefiles in order to detect your host platform. It then
3490 dumps what it found, and creates a file called `config.mk' in the
3491 current directory. This is a sub-Makefile used to define many
3492 important Make variables used to build the library.
3494 - the second time, the build system detects the `config.mk' then use
3495 it to build the library. All object files go into 'obj' by
3496 default, as well as the library file, but this can easily be
3499 Note that you can run `make setup' to force another host platform
3500 detection even if a `config.mk' is present in the current
3501 directory. Another solution is simply to delete the file, then
3504 Finally, the default compiler for all platforms is gcc (for now,
3505 this will hopefully changed in the future). You can however specify
3506 a different compiler by specifying it after the 'setup' target as
3509 gnumake setup lcc on Win32 to use the LCC compiler
3510 gnumake setup visualc on Win32 to use Visual C++
3512 See the file `config/<system>/detect.mk' for a list of supported
3513 compilers for your platforms.
3515 It should be relatively easy to write new detection rules files and
3518 Finally, to build the demo programs, go to `demos' and launch GNU
3519 Make, it will use the `config.mk' in the top directory to build the
3523 ----------------------------------------------------------------------
3527 In the previous beta, a single FT_System object was used to
3528 encompass all low-level operations like thread synchronisation,
3529 memory management and i/o access. This has been greatly simplified:
3531 - thread synchronisation has been dropped, for the simple reason
3532 that the library is already re-entrant, and that if you really
3533 need two threads accessing the same FT_Library, you should
3534 really synchronize access to it yourself with a simple mutex.
3536 - memory management is performed through a very simple object
3537 called `FT_Memory', which really is a table containing a table
3538 of pointers to functions like malloc, realloc and free as well
3539 as some user data (closure).
3541 - resources have disappeared (they created more problems than they
3542 solved), and i/o management have been simplified greatly as a
3543 result. Streams are defined through FT_Stream objects, which
3544 can be either memory-based or disk-based.
3546 Note that each face has its own stream, which is closed only
3547 when the face object is destroyed. Hence, a function like
3548 TT_Flush_Face in 1.x cannot be directly supported. However, if
3549 you really need something like this, you can easily tailor your
3550 own streams to achieve the same feature at a lower level (and
3551 use FT_Open_Face instead of FT_New_Face to create the face).
3553 See the file `include/ftsystem.h' for more details, as well as the
3554 implementations found in `config/unix' and `config/ansi'.
3557 ----------------------------------------------------------------------
3561 The Font Driver interface has been modified in order to support
3562 extensions & versioning.
3565 The list of the font drivers that are statically linked to the
3566 library at compile time is managed through a new configuration file
3567 called `config/<platform>/ftmodule.h'.
3569 This file is autogenerated when invoking `make modules'. This
3570 target will parse all sub-directories of 'src', looking for a
3571 `module.mk' rules file, used to describe the driver to the build
3574 Hence, one should call `make modules' each time a font driver is
3575 added or removed from the `src' directory.
3577 Finally, this version provides a `pseudo-driver' in `src/sfnt'.
3578 This driver doesn't support font files directly, but provides
3579 services used by all TrueType-like font drivers. Hence, its code is
3580 shared between the TrueType & OpenType font formats, and possibly
3581 more formats to come if we're lucky..
3584 ----------------------------------------------------------------------
3588 The extensions support is inspired by the one found in 1.x.
3590 Now, each font driver has its own `extension registry', which lists
3591 which extensions are available for the font faces managed by the
3594 Extension ids are now strings, rather than 4-byte tags, as this is
3595 usually more readable.
3598 - some data, associated to each face object
3599 - an interface (table of function pointers)
3601 An extension that is format-specific should simply register itself
3602 to the correct font driver. Here is some example code:
3604 // Registering an extensions
3606 FT_Error FT_Init_XXXX_Extension( FT_Library library )
3608 FT_DriverInterface* tt_driver;
3610 driver = FT_Get_Driver( library, "truetype" );
3611 if (!driver) return FT_Err_Unimplemented_Feature;
3613 return FT_Register_Extension( driver, &extension_class );
3617 // Implementing the extensions
3619 FT_Error FT_Proceed_Extension_XXX( FT_Face face )
3621 FT_XXX_Extension ext;
3622 FT_XXX_Extension_Interface ext_interface;
3624 ext = FT_Get_Extension( face, "extensionid", &ext_interface );
3625 if (!ext) return error;
3627 return ext_interface->do_it(ext);
3630 ------------------------------------------------------------------------
3632 Copyright 2000-2012 by
3633 David Turner, Robert Wilhelm, and Werner Lemberg.
3635 This file is part of the FreeType project, and may only be used,
3636 modified, and distributed under the terms of the FreeType project
3637 license, LICENSE.TXT. By continuing to use, modify, or distribute this
3638 file you indicate that you have read the license and understand and
3643 version-control: never
3647 --- end of CHANGES ---