2 CHANGES BETWEEN 2.4.10 and 2.4.11
6 - Some vulnerabilities in the BDF implementation have been fixed.
7 Users of this font format should upgrade.
12 - Subpixel hinting support has been contributed by Infinality,
13 based on Greg Hitchcock's whitepaper at
15 http://www.microsoft.com/typography/cleartype/truetypecleartype.aspx
17 Originally, it was a separate patch available from
19 http://www.infinality.net/blog/
21 and which has been integrated.
23 Note that ClearType support is not completely implemented! In
24 particular, full support for the options `compatible_widths',
25 `symmetrical_smoothing, and `bgr' (via the GETINFO bytecode
26 instruction) is missing.
28 Activation of subpixel hinting support can be controlled with
29 the `TT_CONFIG_OPTION_SUBPIXEL_HINTING' configuration option; it
30 is switched off by default. This feature is still experimental;
31 we welcome test reports!
33 - Support for OpenType collections (OTC) has been added.
35 - Pure CFF fonts within an SFNT wrapper are now supported.
40 - Minor rendering improvements to the auto-hinter.
42 - `FT_GlyphSlot_Oblique' now uses a shear angle of 12°.
44 - Experimental support to handle `property modules', for example
45 to control the behaviour of the auto-hinter. The API consists
46 of two new functions, `FT_Property_Set' and `FT_Property_Get'.
48 The code is still subject to change and should not be used for
51 - The `ftdiff' demo program now supports UTF-8 encoded input files
54 - Using keys `r' and `R', you can now adjust the stroker radius in
55 the `ftview' demo program.
57 - Other, minor fixes and improvements.
60 ======================================================================
62 CHANGES BETWEEN 2.4.9 and 2.4.10
64 I. IMPORTANT BUG FIXES
66 - Incremental glyph loading as needed by ghostscript was broken.
71 - A new function `FT_Outline_EmboldenXY', contributed by Alexei
74 - In the `ftview' demo program, key `e' has been replaced with `x'
75 and `y' to embolden in the horizontal and vertical direction,
78 - The glyph spacing computation in `FT_GlyphSlot_Embolden' (and
79 similar code in `ftview') has been improved.
81 - Minor improvements to the TrueType bytecode interpreter and
82 glyph loader, the auto-hinter, and the B/W rasterizer.
85 ======================================================================
87 CHANGES BETWEEN 2.4.8 and 2.4.9
89 I. IMPORTANT BUG FIXES
91 - Another round of fixes to better handle invalid fonts. Many of
92 them are vulnerabilities (see CVE-2012-1126 up to CVE-2012-1144
93 and SA48320) so all users should upgrade.
98 - The `ENCODING -1 <n>' format of BDF fonts is now supported.
100 - For BDF fonts, support for the whole Unicode encoding range has
103 - Better TTF support for x_ppem != y_ppem.
105 - `FT_Get_Advances' sometimes returned bogus values.
107 - The demo programs no longer recognize and handle default
108 suffixes; you now have to always specify the complete font name.
110 - Better rendering and LCD mode cycling added to `ftview'.
113 ======================================================================
115 CHANGES BETWEEN 2.4.7 and 2.4.8
117 I. IMPORTANT BUG FIXES
119 - Some vulnerabilities in handling CID-keyed PostScript fonts have
120 been fixed; see CVE-2011-3439.
125 - Chris Liddell contributed a new API, `FT_Get_PS_Font_Value', to
126 retrieve most of the dictionary keys in Type 1 fonts.
129 ======================================================================
131 CHANGES BETWEEN 2.4.6 and 2.4.7
133 I. IMPORTANT BUG FIXES
135 - Some vulnerabilities in handling Type 1 fonts have been fixed;
141 - FreeType now properly handles ZapfDingbats glyph names while
142 constructing a Unicode character map (for fonts which don't have
146 ======================================================================
148 CHANGES BETWEEN 2.4.5 and 2.4.6
150 I. IMPORTANT BUG FIXES
152 - For TrueType based fonts, the ascender and descender values were
153 incorrect sometimes (off by a pixel if the ppem value was not a
154 multiple of 5). Depending on the use you might now experience
155 a different layout; the change should result in better, more
156 consistent line spacing.
158 - Fix CVE-2011-0226 which causes a vulnerability while handling
161 - BDF fonts containing glyphs with negative values for ENCODING
162 were incorrectly rejected. This bug has been introduced in
163 FreeType version 2.2.0.
165 - David Bevan contributed a major revision of the FreeType stroker
168 . The behaviour of FT_STROKER_LINEJOIN_BEVEL has been corrected.
170 . A new line join style, FT_STROKER_LINEJOIN_MITER_FIXED, has
171 been introduced to support PostScript and PDF miter joins.
173 . FT_STROKER_LINEJOIN_MITER_VARIABLE has been introduced as an
174 alias for FT_STROKER_LINEJOIN_MITER.
176 . Various stroking glitches has been fixed.
181 - SFNT bitmap fonts which contain an outline glyph for `.notdef'
182 only no longer set the FT_FACE_FLAG_SCALABLE flag.
185 ======================================================================
187 CHANGES BETWEEN 2.4.4 and 2.4.5
189 I. IMPORTANT BUG FIXES
191 - A rendering regression for second-order Bézier curves has been
192 fixed, introduced in 2.4.3.
195 II. IMPORTANT CHANGES
197 - If autohinting is not explicitly disabled, FreeType now uses
198 the autohinter if a TrueType based font doesn't contain native
201 - The load flag FT_LOAD_IGNORE_GLOBAL_ADVANCE_WIDTH has been made
202 redundant and is simply ignored; this means that FreeType now
203 ignores the global advance width value in TrueType fonts.
208 - `FT_Sfnt_Table_Info' can now return the number of SFNT tables of
211 - Support for PCF files compressed with bzip2 has been contributed
212 by Joel Klinghed. To make this work, the OS must provide a
215 - Bradley Grainger contributed project and solution files in
216 Visual Studio 2010 format.
218 - Again some fixes to better handle broken fonts.
220 - Some improvements to the B/W rasterizer.
222 - Fixes to the cache module to improve robustness.
224 - Just Fill Bugs contributed (experimental) code to compute blue
225 zones for CJK Ideographs, improving the alignment of horizontal
226 stems at the top or bottom edges.
228 - The `ftgrid' demo program can now display autohinter segments,
229 to be toggled on and off with key `s'.
232 ======================================================================
234 CHANGES BETWEEN 2.4.3 and 2.4.4
236 I. IMPORTANT BUG FIXES
238 - UVS support (TrueType/OpenType cmap format 14) support is fixed.
239 This regression has been introduced in version 2.4.0.
244 - Detect tricky fonts (e.g. MingLiU) by the lengths and checksums
245 of Type42-persistent subtables (`cvt ', `fpgm', and `prep') when
246 a TrueType font without family name is given. The previous fix,
247 introduced in 2.4.3, was too rigorous, causing many subsetted
248 fonts (mainly from PDF files) displayed badly because FreeType
249 forced rendering with the TrueType bytecode engine instead of
252 - Better support for 64bit platforms.
254 - More fixes to improve handling of broken fonts.
257 ======================================================================
259 CHANGES BETWEEN 2.4.2 and 2.4.3
261 I. IMPORTANT BUG FIXES
263 - Fix rendering of certain cubic, S-shaped arcs. This regression
264 has been introduced in version 2.4.0.
269 - To fix the above mentioned rendering issue, a new spline
270 flattening algorithm has been introduced which speeds up both
271 conic and cubic arcs.
273 - Handling of broken fonts has been further improved.
276 ======================================================================
278 CHANGES BETWEEN 2.4.1 and 2.4.2
280 I. IMPORTANT BUG FIXES
282 - A stack overflow in CFF Type2 CharStrings interpreter is fixed.
284 - Handling Type 42 font deallocation was broken; additionally, the
285 library is now more robust against malformed Type 42 fonts.
290 - Two new functions, `FT_Reference_Library' (in FT_MODULE_H) and
291 `FT_Reference_Face' (in FT_FREETYPE_H), have been added to
292 simplify life-cycle management. A counter gets initialized to 1
293 at the time an FT_Library (or FT_Face) structure is created.
294 The two new functions increment the respective counter.
295 `FT_Done_Library' and `FT_Done_Face' then only destroy a library
296 or face if the counter is 1, otherwise they simply decrement the
300 ======================================================================
302 CHANGES BETWEEN 2.4.0 and 2.4.1
306 - A serious bug in the CFF font module prevented display of many
307 glyphs in CFF fonts like `MinionPro-Regular.otf'.
310 ======================================================================
312 CHANGES BETWEEN 2.3.12 and 2.4.0
316 - Since May 2010, all patents regarding the TrueType bytecode
317 interpreter have expired worldwide. Consequently, we now define
318 TT_CONFIG_OPTION_BYTECODE_INTERPRETER by default (and undefine
319 TT_CONFIG_OPTION_UNPATENTED_HINTING).
321 - A new function `FT_Library_SetLcdFilterWeights' is available to
322 adjust the filter weights set by `FT_Library_SetLcdFilter'.
327 - Thanks to many reports from Robert Święcki, FreeType's stability
328 in handling broken or damaged fonts is much improved.
330 - Support for LCD filter control has been added to the demo
331 programs `ftdiff' and `ftview'.
334 ======================================================================
336 CHANGES BETWEEN 2.3.11 and 2.3.12
340 - For `FT_Open_Face', new parameters are available to ignore
341 preferred family names: FT_PARAM_TAG_IGNORE_PREFERRED_FAMILY and
342 FT_PARAM_TAG_IGNORE_PREFERRED_SUBFAMILY.
347 - Support for incremental font loading (controlled with the
348 FT_CONFIG_OPTION_INCREMENTAL macro) is now active by default.
350 - Better support for vertical metrics.
352 - Various minor bug fixes.
355 ======================================================================
357 CHANGES BETWEEN 2.3.10 and 2.3.11
359 I. IMPORTANT BUG FIXES
361 - Version 2.3.10 broke PCF support.
364 ======================================================================
366 CHANGES BETWEEN 2.3.10 and 2.3.9
368 I. IMPORTANT BUG FIXES
370 - If all ASCII digits in a font have the same (unscaled) width,
371 the autohinter respects this and won't change it.
373 - TrueType fonts are now rasterized correctly if the horizontal
374 and vertical resolution differ.
376 - Type 1 fonts are now handled with increased precision internally
377 to avoid serious rounding issues if non-integral coordinates are
380 - Horizontally condensed CFF fonts (using the font matrix) were
381 rendered incorrectly. This bug has been introduced after
385 II. IMPORTANT CHANGES
387 - Support for the SFNT cmap 13 table format (as defined by the new
388 OpenType 1.6 specification) has been added.
390 - B/W rasterization of well-hinted TrueType fonts at small sizes
391 has been greatly improved.
393 - Calculation of vertical metrics in OpenType fonts has been
399 - It is now possible to change the emboldening factor in the
400 `ftview' demo program with keys `e' and `E'.
402 - It is now possible to change the slant value in the `ftview'
403 demo program with keys `s' and `S'.
405 - The 5-levels grayscale mode of the `ftraster' module (which
406 FreeType doesn't use by default) was broken since version 2.3.0.
408 - Compilation of the `ftgrays' and `ftraster' modules was broken
411 - Various fixes for compilation on 64bit and 16bit architectures.
414 ======================================================================
416 CHANGES BETWEEN 2.3.9 and 2.3.8
418 I. IMPORTANT BUG FIXES
420 - Very unfortunately, FreeType 2.3.8 contained a change that broke
421 its official ABI. The end result is that programs compiled
422 against previous versions of the library, but dynamically linked
423 to 2.3.8 can experience memory corruption if they call the
424 `FT_Get_PS_Font_Info' function.
426 We recommend all users to upgrade to 2.3.9 as soon as possible,
427 or to downgrade to a previous release of the library if this is
430 The origin of the bug is that a new field was added to the
431 publicly defined `PS_FontInfoRec' structure. Unfortunately,
432 objects of this type can be stack or heap allocated by callers
433 of `FT_Get_PS_Font_Info', resulting in a memory buffer
434 overwrite with its implementation in 2.3.8.
436 If you want to know whether your code is vulnerable to this
437 issue, simply search for the substrings `PS_FontInfo' and
438 `PS_Font_Info' in your source code. If none is found, your code
439 is safe and is not affected.
441 The FreeType team apologizes for the problem.
443 - The POSIX support of MacOS resource-fork fonts (Suitcase fonts
444 and LaserWriter Type1 PostScript fonts) was broken in 2.3.8. If
445 FreeType2 is built without Carbon framework, these fonts are not
446 handled correctly. Version 2.3.7 didn't have this bug.
448 - `FT_Get_Advance' (and `FT_Get_Advances') returned bad values for
449 almost all font formats except TrueType fonts.
451 - Fix a bug in the SFNT kerning table loader/parser which could
452 crash the engine if certain malformed tables were encountered.
454 - Composite SFNT bitmaps are now handled correctly.
457 II. IMPORTANT CHANGES
459 - The new functions `FT_Get_CID_Is_Internally_CID_keyed' and
460 `FT_Get_CID_From_Glyph_Index' can be used to access CID-keyed
461 CFF fonts via CID values. This code has been contributed by
467 - `FT_Outline_Get_InsideBorder' returns FT_STROKER_BORDER_RIGHT
468 for empty outlines. This was incorrectly documented.
470 - The `ftview' demo program now supports UTF-8 encoded strings.
473 ======================================================================
475 CHANGES BETWEEN 2.3.8 and 2.3.7
477 I. IMPORTANT BUG FIXES
479 - CID-keyed fonts in an SFNT wrapper were not handled correctly.
481 - The smooth renderer produced truncated images (on the right) for
482 outline parts with negative horizontal values. Most fonts don't
483 contain outlines left to the y coordinate axis, but the effect
484 was very noticeable for outlines processed with FT_Glyph_Stroke,
487 - `FT_Get_TrueType_Engine_Type' returned a wrong value if both
488 configuration macros TT_CONFIG_OPTION_BYTECODE_INTERPRETER and
489 TT_CONFIG_OPTION_UNPATENTED_HINTING were defined.
491 - The `face_index' field in the `FT_Face' structure wasn't
492 initialized properly after calling FT_Open_Face and friends with
493 a positive face index for CFFs, WinFNTs, and, most importantly,
494 for TrueType Collections (TTCs).
497 II. IMPORTANT CHANGES
499 - Rudimentary support for Type 1 fonts and CID-keyed Type 1 fonts
500 in an SFNT wrapper has been added -- such fonts are used on the
501 Mac. The core SFNT tables `TYP1' and `CID ' are passed to the
502 PS Type 1 and CID-keyed PS font drivers; other tables (`ALMX',
503 `BBOX', etc.) are not supported yet.
505 - A new interface to extract advance values of glyphs without
506 loading their outlines has been added. The functions are called
507 `FT_Get_Advance' and `FT_Get_Advances'; they are defined in file
508 `ftadvanc.h' (to be accessed as FT_ADVANCES_H).
510 - A new function `FT_Get_FSType_Flags' (in FT_FREETYPE_H) has been
511 contributed by David Bevan to access the embedding and
512 subsetting restriction information of fonts.
517 - FT_MulFix is now an inlined function; by default, assembler code
518 is provided for x86 and ARM. See FT_CONFIG_OPTION_INLINE_MULFIX
519 and FT_CONFIG_OPTION_NO_ASSEMBLER (in ftoption.h) for more.
521 - The handling of `tricky' fonts (this is, fonts which don't work
522 with the autohinter, needing the font format's hinting engine)
523 has been generalized and changed slightly:
525 . A new face flag FT_FACE_FLAG_TRICKY indicates that the font
526 format's hinting engine is necessary for correct rendering.
527 The macro FT_IS_TRICKY can be used to check this flag.
529 . FT_LOAD_NO_HINTING is now ignored for tricky fonts. To really
530 force raw loading of such fonts (without hinting), both
531 FT_LOAD_NO_HINTING and FT_LOAD_NO_AUTOHINT must be used --
532 this is something which you probably never want to do.
534 . Tricky TrueType fonts always use the bytecode interpreter,
535 either the patented or unpatented version.
537 - The function `FT_GlyphSlot_Own_Bitmap' has been moved from
538 FT_SYNTHESIS_H to FT_BITMAP_H; it is now part of the `official'
539 API. (The functions in FT_SYNTHESIS_H are still subject to
542 - In the `ftdiff' demo program you can now toggle the use of
543 FT_LOAD_IGNORE_GLOBAL_ADVANCE_WIDTH with key `a'.
546 ======================================================================
548 CHANGES BETWEEN 2.3.7 and 2.3.6
550 I. IMPORTANT BUG FIXES
552 - If the library was compiled on an i386 platform using gcc, and
553 compiler option -O3 was given, `FT_MulFix' sometimes returned
554 incorrect results which could have caused problems with
555 `FT_Request_Metrics' and `FT_Select_Metrics', returning an
556 incorrect descender size.
558 - Pure CFFs without subfonts were scaled incorrectly if the font
559 matrix was non-standard. This bug has been introduced in
562 - The `style_name' field in the `FT_FaceRec' structure often
563 contained a wrong value for Type 1 fonts. This misbehaviour
564 has been introduced in version 2.3.6 while trying to fix
565 another problem. [Note, however, that this value is
566 informative only since the used algorithm to extract it is
570 II. IMPORTANT CHANGES
572 - Two new macros, FT_OUTLINE_SMART_DROPOUTS and
573 FT_OUTLINE_EXCLUDE_STUBS, have been introduced. Together with
574 FT_OUTLINE_IGNORE_DROPOUTS (which was ignored previously) it is
575 now possible to control the dropout mode of the `raster' module
576 (for B&W rasterization), using the `flags' field in the
577 `FT_Outline' structure.
579 - The TrueType bytecode interpreter now passes the dropout mode to
580 the B&W rasterizer. This greatly increases the output for small
581 ppem values of many fonts like `pala.ttf'.
584 ======================================================================
586 CHANGES BETWEEN 2.3.6 and 2.3.5
588 I. IMPORTANT BUG FIXES
590 - A bunch of potential security problems have been found. All
593 - Microsoft Unicode cmaps in TrueType fonts are now always
594 preferred over Apple cmaps. This is not a bug per se, but there
595 exist some buggy fonts created for MS which have broken Apple
596 cmaps. This affects only the automatic selection of FreeType;
597 it's always possible to manually select an Apple Unicode cmap if
600 - Many bug fixes to the TrueType bytecode interpreter.
602 - Improved Mac support.
604 - Subsetted CID-keyed CFFs are now supported correctly.
606 - CID-keyed CFFs with subfonts which are scaled in a non-standard
607 way are now handled correctly.
609 - A call to FT_Open_Face with `face_index' < 0 crashed FreeType if
610 the font was a Windows (bitmap) FNT/FON.
613 II. IMPORTANT CHANGES
615 - The new function `FT_Get_CID_Registry_Ordering_Supplement' gives
616 access to those fields in a CID-keyed font. The code has been
617 contributed by Derek Clegg.
619 - George Williams contributed code to validate the new `MATH'
620 OpenType table (within the `otvalid' module). The `ftvalid'
621 demo program has been extended accordingly.
623 - An API for cmap 14 support (for Unicode Variant Selectors, UVS)
624 has been contributed by George Williams.
626 - A new face flag FT_FACE_FLAG_CID_KEYED has been added, together
627 with a macro FT_IS_CID_KEYED which evaluates to 1 if the font is
633 - Build support for symbian has been contributed.
635 - Better WGL4 glyph name support, contributed by Sergey Tolstov.
637 - Debugging output of the various FT_TRACEX macros is now sent to
640 - The `ftview' demo program now provides artificial slanting too.
642 - The `ftvalid' demo program has a new option `-f' to select the
646 ======================================================================
648 CHANGES BETWEEN 2.3.5 and 2.3.4
650 I. IMPORTANT BUG FIXES
652 - Some subglyphs in TrueType fonts were handled incorrectly due to
653 a missing graphics state reinitialization.
655 - Large .Z files (as distributed with some X11 packages) weren't
656 handled correctly, making FreeType increase the heap stack in an
659 - A large number of bugs have been fixed to avoid crashes and
660 endless loops with invalid fonts.
663 II. IMPORTANT CHANGES
665 - The two new cache functions `FTC_ImageCache_LookupScaler' and
666 `FTC_SBit_Cache_LookupScaler' have been added to allow lookup of
667 glyphs using an `FTC_Scaler' object; this makes it possible to
668 use fractional pixel sizes in the cache. The demo programs have
669 been updated accordingly to use this feature.
671 - A new API `FT_Get_CMap_Format' has been added to get the cmap
672 format of a TrueType font. This is useful in handling PDF
673 files. The code has been contributed by Derek Clegg.
675 - The auto-hinter now produces better output by default for
676 non-Latin scripts like Indic. This was done by using the CJK
677 hinting module as the default instead of the Latin one. Thanks
678 to Rahul Bhalerao for this suggestion.
680 - A new API `FT_Face_CheckTrueTypePatents' has been added to find
681 out whether a given TrueType font uses patented bytecode
682 instructions. The `ft2demos' bundle contains a new program
683 called `ftpatchk' which demonstrates its usage.
685 - A new API `FT_Face_SetUnpatentedHinting' has been added to
686 enable or disable the unpatented hinter.
688 - Support for Windows FON files in PE format has been contributed
694 - Vincent Richomme contributed Visual C++ project files for Pocket
698 ======================================================================
700 CHANGES BETWEEN 2.3.4 and 2.3.3
702 I. IMPORTANT BUG FIXES
704 - A serious bug in the handling of bitmap fonts (and bitmap
705 strikes of outline fonts) has been introduced in 2.3.3.
708 ======================================================================
710 CHANGES BETWEEN 2.3.3 and 2.3.2
712 I. IMPORTANT BUG FIXES
714 - Remove a serious regression in the TrueType bytecode interpreter
715 that was introduced in version 2.3.2. Note that this does not
716 disable the improvements introduced to the interpreter in
717 version 2.3.2, only some ill cases that occurred with certain
718 fonts (though a few popular ones).
720 - The auto-hinter now ignores single-point contours for computing
721 blue zones. This bug created `wavy' baselines when rendering
722 text with various fonts that use these contours to model
723 mark-attach points (these are points that are never rasterized
724 and are placed outside of the glyph's real outline).
726 - The `rsb_delta' and `lsb_delta' glyph slot fields are now set to
727 zero for mono-spaced fonts. Otherwise code that uses them would
728 essentially ruin the fixed-advance property.
730 - Fix CVE-2007-1351 which can cause an integer overflow while
731 parsing BDF fonts, leading to a potentially exploitable heap
737 - Fixed compilation issues on some 64-bit platforms (see ChangeLog
740 - A new demo program `ftdiff' has been added to compare TrueType
741 hinting, FreeType's auto hinting, and rendering without hinting
745 ======================================================================
747 CHANGES BETWEEN 2.3.2 and 2.3.1
749 I. IMPORTANT BUG FIXES
751 - FreeType returned incorrect kerning information from TrueType
752 fonts when the bytecode interpreter was enabled. This happened
753 due to a typo introduced in version 2.3.0.
755 - Negative kerning values from PFM files are now reported
756 correctly (they were read as 16-bit unsigned values from the
759 - Fixed a small memory leak when `FT_Init_FreeType' failed for
762 - The Postscript hinter placed and sized very thin and ghost stems
765 - The TrueType bytecode interpreter has been fixed to get rid of
766 most of the rare differences seen in comparison to the Windows
770 II. IMPORTANT CHANGES
772 - The auto-hinter now better deals with serifs and corner cases
773 (e.g., glyph '9' in Arial at 9pt, 96dpi). It also improves
774 spacing adjustments and doesn't change widths for non-spacing
777 - Many Mac-specific functions are deprecated (but still
778 available); modern replacements have been provided for them.
779 See the documentation in file `ftmac.h'.
782 ======================================================================
784 CHANGES BETWEEN 2.3.1 and 2.3.0
786 I. IMPORTANT BUG FIXES
788 - The TrueType interpreter sometimes returned incorrect horizontal
789 metrics due to a bug in the handling of the SHZ instruction.
791 - A typo in a security check introduced after version 2.2.1
792 prevented FreeType to render some glyphs in CFF fonts.
795 ======================================================================
797 CHANGES BETWEEN 2.3.0 and 2.2.1
799 I. IMPORTANT BUG FIXES
801 - The PCF font loader is now much more robust while loading
802 malformed font files.
804 - Various memory leaks have been found and fixed.
806 - The TrueType name loader now deals properly with some fonts that
807 encode their names in UTF-16 (the specification was vague, and
808 the code incorrectly assumed UCS-4).
810 - Fixed the TrueType bytecode loader to deal properly with subtle
811 monochrome/gray issues when scaling the CVT. Some fonts
812 exhibited bad rendering artifacts otherwise.
814 - `FT_GlyphSlot_Embolden' now supports vertical layouts correctly
815 (it mangled the vertical advance height).
817 - Fixed byte endian issues of `ftmac.c' to support Mac OS X on
820 - The PFR font loader no longer erroneously tags font files
821 without any outlines as FT_FACE_FLAG_SCALABLE.
824 II. NEW API FUNCTIONS
826 - `FT_Library_SetLcdFilter' allows you to select a special filter
827 to be applied to the bitmaps generated by `FT_Render_Glyph' if
828 one of the FT_RENDER_MODE_LCD and FT_RENDER_MODE_LCD_V modes has
829 been selected. This filter is used to reduce color fringes;
830 several settings are available through the FT_LCD_FILTER_XXX
833 Its declaration and documentation can be found in file
834 `include/freetype/ftlcdfil.h' (to be accessed with macro
837 *IMPORTANT*: This function returns an error
838 (FT_Err_Unimplemented_Feature) in default builds of the library
839 for patent reasons. See below.
841 - `FT_Get_Gasp' allows you to query the flags of the TrueType
842 `gasp' table for a given character pixel size. This is useful
843 to duplicate the text rendering of MS Windows when the native
844 bytecode interpreter is enabled (which isn't the default for
845 other patent reasons).
847 Its declaration and documentation can be found in file
848 `include/freetype/ftgasp.h' (to be accessed with macro
852 III. IMPORTANT CHANGES
854 - The auto-hinter has been tuned a lot to improve its results with
855 serif fonts, resulting in much better font rendering of many web
858 - The unpatented hinter is now part of the default build of the
859 library; we have added code to automatically support `tricky'
862 This means that FreeType should `just work' with certain Asian
863 fonts, like MingLiU, which cannot properly be loaded without a
864 bytecode interpreter, but which fortunately do not use any of
865 the patented bytecode opcodes. We detect these fonts by name,
866 so please report any font file that doesn't seem to work with
867 FreeType, and we shall do what we can to support it in a next
870 Note that the API hasn't changed, so you can still force
871 unpatented hinting with a special parameter to `FT_Open_Face' as
872 well. This might be useful in same cases; for example, a PDF
873 reader might present a user option to activate it to deal with
874 certain `tricky' embedded fonts which cannot be clearly
877 If you are a developer for embedded systems, you might want to
878 *disable* the feature to save code space by undefining
879 TT_CONFIG_OPTION_UNPATENTED_HINTING in file `ftoption.h'.
881 - LCD-optimized rendering is now *disabled* in all default builds
882 of the library, mainly due to patent issues. For more
885 http://lists.gnu.org/archive/html/freetype/2006-09/msg00064.html
887 A new configuration macro FT_CONFIG_OPTION_SUBPIXEL_RENDERING
888 has been introduced in `ftoption.h'; manually define it in this
889 file if you want to re-enable the feature.
891 The change only affects the implementation, not the FreeType
892 API. This means that clients don't need to be modified, because
893 the library still generates LCD decimated bitmaps, but with the
894 added constraint that R=G=B on each triplet.
896 The displayed result should be equal to normal anti-aliased
899 Additionally, if FT_CONFIG_OPTION_SUBPIXEL_RENDERING is not
900 defined, the new `FT_Library_SetLcdFilter' function returns the
901 FT_Err_Unimplemented_Feature error code.
903 - Some computation bugs in the TrueType bytecode interpreter were
904 found, which allow us to get rid of very subtle and rare
905 differences we had experienced with the Windows renderer.
907 - It is now possible to cross-compile the library easily. See the
908 file `docs/INSTALL.CROSS' for details.
910 - The file `src/base/ftmac.c' now contains code for Mac OS X only;
911 its deprecated function `FT_GetFile_From_Mac_Font_Name' always
912 returns an error even if the QuickDraw framework is available.
913 The previous version has been moved to `builds/mac/ftmac.c'.
915 Selecting configure option `--with-quickdraw-carbon' makes the
916 build process use the original `ftmac.c' file instead of the Mac
922 - Various performance and memory footprint optimizations have been
923 performed on the TrueType and CFF font loaders, sometimes with
924 very drastic benefits (e.g., the TrueType loader is now about
925 25% faster; FreeType should use less heap memory under nearly
928 - The anti-aliased rasterizer has been optimized and is now 15% to
929 25% percent faster than in previous versions, depending on
932 - The Type 1 loader has been improved; as an example, it now skips
933 top-level dictionaries properly.
935 - Better support for Mac fonts on POSIX systems, plus compilation
936 fixes for Mac OS X on ppc64 where `ftmac.c' cannot be built.
938 - Configuration without `--with-old-mac-fonts' does not include
939 `ftmac.c' (this was the behaviour in FreeType version 2.1.10).
941 - The TrueTypeGX validator (gxvalid) checks the order of glyph IDs
945 ======================================================================
947 CHANGES BETWEEN 2.2.1 and 2.2
949 I. IMPORTANT BUG FIXES
951 - Various integer overflows have been fixed.
953 - PFB fonts with MacOS resource fork weren't handled correctly on
957 ======================================================================
959 CHANGES BETWEEN 2.2 and 2.1.10
961 (not released officially)
963 I. IMPORTANT BUG FIXES
965 - Vertical metrics for SFNT fonts were incorrect sometimes.
967 - The FT_HAS_KERNING macro always returned 0.
969 - CFF OpenType fonts didn't return correct vertical metrics for
970 glyphs with outlines.
972 - If FreeType was compiled without hinters, all font formats based
973 on PS outlines weren't scaled correctly.
976 II. IMPORTANT CHANGES
978 - Version 2.2 no longer exposes its internals, this is, the header
979 files located in the `include/freetype/internal' directory of
980 the source package are not copied anymore by the `make install'
981 command. Consequently, a number of rogue clients which directly
982 access FreeType's internal functions and structures won't
983 compile without modification.
985 We provide patches for most of those rogue clients. See the
986 following page for more information:
988 http://www.freetype.org/freetype2/patches/rogue-patches.html
990 Note that, as a convenience to our Unix desktop users, version
991 2.2 is *binary* compatible with FreeType 2.1.7, which means that
992 installing this release on an existing distribution shall not
993 break any working desktop.
995 - FreeType's build mechanism has been redesigned. With GNU make
996 it is now sufficient in most cases to edit two files:
997 `modules.cfg', to select the library components, and the
998 configuration file `include/freetype/config/ftoption.h' (which
999 can be copied to the objects directory). Removing unused module
1000 directories to prevent its compilation and editing
1001 `include/freetype/config/ftmodule.h' is no longer necessary.
1003 - The LIGHT hinting algorithm produces more pleasant results.
1004 Also, using the FT_LOAD_TARGET_LIGHT flags within FT_Load_Glyph
1005 always forces auto-hinting, as a special exception. This allows
1006 you to experiment with it even if you have enabled the TrueType
1007 bytecode interpreter in your build.
1009 - The auto hinter now employs a new algorithm for CJK fonts, based
1010 on Akito Hirai's patch. Note that this only works for fonts
1011 with a Unicode charmap at the moment.
1013 - The following callback function types have changed slightly (by
1014 adding the `const' keyword where appropriate):
1016 FT_Outline_MoveToFunc
1017 FT_Outline_LineToFunc
1018 FT_Outline_ConicToFunc
1019 FT_Outline_CubicToFunc
1021 FT_Raster_RenderFunc
1023 FT_Glyph_TransformFunc
1024 FT_Renderer_RenderFunc
1025 FT_Renderer_TransformFunc
1027 Note that this doesn't affect binary backward compatibility.
1029 - On MacOS, new APIs have been added as replacements for legacy
1030 APIs: `FT_New_Face_From_FSRef' for `FT_New_Face_From_FSSpec',
1031 and `FT_GetFile_From_Mac_ATS_Name' for
1032 `FT_GetFile_From_Mac_Name'. Legacy APIs are still available, if
1033 FreeType is built without disabling them.
1035 - A new API `FT_Select_Size' has been added to select a bitmap
1036 strike by its index. Code using other functions to select
1037 bitmap strikes should be updated to use this function.
1039 - A new API `FT_Get_SubGlyph_Info' has been added to retrieve
1040 subglyph data. This can be used by rogue clients which used to
1041 access the internal headers to get the corresponding data.
1043 - In 2.1.10, the behaviour of `FT_Set_Pixel_Sizes' was changed for
1044 BDF/PCF fonts, and only for them. This causes inconsistency.
1045 In this release, we undo the change. The intent of the change
1046 in 2.1.10 is to allow size selection through real dimensions,
1047 which can now be done through `FT_Request_Size'.
1049 - Some security issues were discovered and fixed in the CFF and
1050 Type 1 loader, causing crashes of FreeType by malformed font
1056 - The documentation for FT_LOAD_TARGET_XXX and FT_RENDER_MODE_XXX
1057 values now better reflects its usage and differences: One set is
1058 used to specify the hinting algorithm, the other to specify the
1059 pixel rendering mode.
1061 - `FT_New_Face' and `FT_New_Face_From_FSSpec' in ftmac.c have been
1062 changed to count supported scalable faces (sfnt, LWFN) only, and
1063 to return the number of available faces via face->num_faces.
1064 Unsupported bitmap faces (fbit, NFNT) are ignored.
1066 - builds/unix/configure has been improved for MacOS X. It now
1067 automatically checks available functions in Carbon library, and
1068 prepare to use newest functions by default. Options to specify
1069 the dependencies of each Carbon APIs (FSSpec, FSRef, old/new
1070 QuickDraw, ATS) are available too. By manual disabling of all
1071 QuickDraw functionality, FreeType can be built without
1072 `deprecated function' warnings on MacOS 10.4.x, but
1073 FT_GetFile_Mac_Name in ftmac.c then is changed to a dummy
1074 function, and returns an `unimplemented' error. For details see
1077 - SFNT cmap handling has been improved, mainly to run much faster
1080 - A new function `FT_Get_TrueType_Engine_Type (declared in
1081 `FT_MODULE_H') is provided to determine the status of the
1082 TrueType bytecode interpreter compiled into the library
1083 (patented, unpatented, unimplemented).
1085 - Vertical metrics of glyphs are synthesized if the font does not
1086 provide such information. You can tell whether the metrics are
1087 synthesized or not by checking the FT_FACE_FLAG_VERTICAL flag of
1090 - The demo programs `ftview' and `ftstring' have been rewritten
1091 for better readability. `ftview' has a new switch `-p' to test
1092 FT_New_Memory_Face (instead of FT_New_Face).
1094 - FreeType now honours bit 1 in the `head' table of TrueType fonts
1095 (meaning `left sidebearing point at x=0'). This helps with some
1098 - Rudimentary support for Adobe's new `SING Glyphlet' format. See
1100 http://www.adobe.com/products/indesign/sing_gaiji.html
1102 for more information.
1104 - The `ftdump' program from the `ft2demos' bundle now shows some
1105 information about charmaps. It also supports a new switch `-v'
1106 to increase verbosity.
1108 - Better AFM support. This includes track kerning support.
1111 ======================================================================
1113 CHANGES BETWEEN 2.1.10 and 2.1.9
1115 I. IMPORTANT BUG FIXES
1117 - The size comparison for BDF and PCF files could fail sometimes.
1119 - Some CFF files were still not loaded correctly. Patch from
1122 - The stroker still had some serious bugs.
1124 - Boris Letocha fixed a bug in the TrueType interpreter: The
1125 NPUSHW instruction wasn't skipped correctly in IF clauses. Some
1126 fonts like `Helvetica 75 Bold' failed.
1128 - Another serious bug in handling TrueType hints caused many
1129 distortions. It has been introduced in version 2.1.8, and it is
1130 highly recommended to upgrade.
1132 - FreeType didn't properly parse empty Type 1 glyphs.
1134 - An unbound dynamic buffer growth was fixed in the PFR loader.
1136 - Several bugs have been fixed in the cache sub-system.
1138 - FreeType behaved incorrectly when resizing two distinct but very
1139 close character pixel sizes through `FT_Set_Char_Size' (Savannah
1142 - The auto-hinter didn't work properly for fonts without a Unicode
1143 charmap -- it even refused to load the glyphs.
1146 II. IMPORTANT CHANGES
1148 - Many fixes have been applied to drastically reduce the amount of
1149 heap memory used by FreeType, especially when using
1150 memory-mapped font files (which is the default on Unix systems
1151 which support them).
1153 - The auto-hinter has been replaced with a new module, called the
1154 `auto-fitter'. It consumes less memory than its predecessor,
1155 and it is prepared to support non-latin scripts better in next
1158 - George Williams contributed code to read kerning data from PFM
1161 - FreeType now uses the TT_NAME_ID_PREFERRED_FAMILY and
1162 TT_NAME_ID_PREFERRED_SUBFAMILY strings (if available) for
1163 setting family and style in SFNT fonts (patch from Kornfeld
1166 - A new API `FT_Sfnt_Table_Info' (in FT_TRUETYPE_TABLES_H) has
1167 been added to retrieve name and size information of SFNT tables.
1169 - A new API `FT_OpenType_Validate' (in FT_OPENTYPE_VALIDATE_H) has
1170 been added to validate OpenType tables (BASE, GDEF, GPOS, GSUB,
1171 JSTF). After validation it is no longer necessary to check
1172 for errors in those tables while accessing them.
1174 Note that this module might be moved to another library in the
1175 future to avoid a tight dependency between FreeType and the
1176 OpenType specification.
1178 - A new API in FT_BITMAP_H (`FT_Bitmap_New', `FT_Bitmap_Convert',
1179 `FT_Bitmap_Copy', `FT_Bitmap_Embolden', `FT_Bitmap_Done') has
1180 been added. Its use is to convert an FT_Bitmap structure in
1181 1bpp, 2bpp, 4bpp, or 8bpp format into another 8bpp FT_Bitmap,
1182 probably using a different pitch, and to further manipulate it.
1184 - A new API `FT_Outline_Embolden' (in FT_OUTLINE_H) gives finer
1185 control how outlines are embolded.
1187 - `FT_GlyphSlot_Embolden' (in FT_SYNTHESIS_H) now handles bitmaps
1188 also (code contributed by Chia I Wu). Note that this function
1189 is still experimental and may be replaced with a better API.
1191 - The method how BDF and PCF bitmap fonts are accessed has been
1192 refined. Formerly, FT_Set_Pixel_Sizes and FT_Set_Char_Size
1193 were synonyms in FreeType's BDF and PCF interface. This has
1194 changed now. FT_Set_Pixel_Sizes should be used to select the
1195 actual font dimensions (the `strike', which is the sum of the
1196 `FONT_ASCENT' and `FONT_DESCENT' properties), while
1197 FT_Set_Char_Size selects the `nominal' size (the `PIXELSIZE'
1198 property). In both functions, the width parameter is ignored.
1203 - The BDF driver no longer converts all returned bitmaps with a
1204 depth of 2bpp or 4bpp to a depth of 8bpp. The documentation has
1205 not mentioned this explicitly, but implementors might have
1206 relied on this after looking into the source files.
1208 - A new option `--ftversion' has been added to freetype-config to
1209 return the FreeType version.
1211 - The memory debugger has been updated to dump allocation
1212 statistics on all allocation sources in the library. This is
1213 useful to spot greedy allocations when loading and processing
1216 - We removed a huge array of constant pointers to constant strings
1217 in the `psnames' module. The problem was that compilations in
1218 PIC mode (i.e., when generating a Unix shared object/dll) put
1219 the array into the non-shared writable section of the library
1220 since absolute pointers are not relocatable by nature.
1222 This reduces the memory consumption by approximately 16KByte per
1223 process linked to FreeType. We now also store the array in a
1224 compressed form (as a trie) which saves about 20KByte of code as
1227 - Kirill Smelkov provided patches to make src/raster/ftraster.c
1228 compile stand-alone again.
1231 ======================================================================
1233 CHANGES BETWEEN 2.1.9 and 2.1.8
1235 I. IMPORTANT BUG FIXES
1237 - The function `FT_Get_CharMap_Index' was only declared, without
1238 any real code. For consistency, it has been renamed to
1239 `FT_Get_Charmap_Index'. (This function is needed to implement
1242 - `FT_Outline_Get_BBox' sometimes returned incorrect values for
1243 conic outlines (e.g., for TrueType fonts).
1245 - Handling of `bhed' table has been fixed.
1247 - The TrueType driver with enabled byte code interpreter sometimes
1248 returned artifacts due to incorrect rounding. This bug has been
1249 introduced after version 2.1.4.
1251 - The BDF driver dropped the last glyph in the font.
1253 - The BDF driver now uses the DEFAULT_CHAR property (if available)
1254 to select a glyph shape for the undefined glyph.
1256 - The stroker failed for closed outlines and single points.
1259 II. IMPORTANT CHANGES
1261 - George Williams contributed code to handle Apple's font
1262 distortion technology found in GX fonts (`avar', `cvar', `fvar',
1263 and `gvar' tables; the Multiple Masters API has been slightly
1264 extended to cope with the new functionality).
1266 - The `FT_GlyphSlotRec' structure has been extended: The elements
1267 `lsb_delta' and `rsb_delta' give the difference between hinted
1268 and unhinted left and right side bearings if autohinting is
1269 active. Using those values can improve the inter-letter spacing
1270 considerably. See the documentation of `FT_GlyphSlotRec' and
1271 the `ftstring' demo program how to use it.
1273 - Loading TrueType and Type 1 fonts has been made much faster.
1275 - The stroker is no longer experimental (but the cache subsystem
1281 - A new documentation file `formats.txt' describes various font
1282 formats supported (and not supported) by FreeType.
1285 ======================================================================
1287 CHANGES BETWEEN 2.1.8 and 2.1.7
1289 I. IMPORTANT BUG FIXES
1291 - The native TrueType hinter contained some bugs which prevented
1292 some fonts to be rendered correctly, most notably Legendum.otf.
1294 - The PostScript hinter now produces improved results.
1296 - The linear advance width and height values were incorrectly
1297 rounded, making them virtually unusable if not loaded with
1298 FT_LOAD_LINEAR_DESIGN.
1300 - Indexing CID-keyed CFF fonts is now working: The glyph index is
1301 correctly treated as a CID, similar to FreeType's CID driver
1302 module. Note that CID CMap support is still missing.
1304 - The FT_FACE_FLAGS_GLYPH_NAMES flag is now set correctly for all
1307 - Some subsetted Type 1 fonts weren't parsed correctly. This bug
1308 has been introduced in 2.1.7. In summary, the Type 1 parser has
1311 - Non-decimal numbers weren't parsed correctly in PS fonts.
1313 - The WinFNT driver now correctly reports FT_ENCODING_NONE for all
1314 but one encoding. Use the new FT_WinFNT_ID_XXX values together
1315 with `FT_Get_WinFNT_Header' to get the WinFNT charset ID.
1317 - The descender metrics (face->size->metrics.descender) for WinFNT
1318 bitmap fonts had the wrong sign.
1320 - The (emulated) `seac' support for CFF fonts was broken.
1322 - The `flex' operator didn't work for CFF fonts.
1324 - PS glyphs which use the `hintmask' operator haven't been
1325 rendered correctly in some cases.
1327 - Metrics for BDF and PCF bitmap font formats have been fixed.
1329 - Autohinting is now disabled for glyphs which are vertically
1330 distorted or mirrored (using a transformation matrix). This
1331 fixes a bug which produced zero-height glyphs.
1333 - The `freetype-config' script now handles --prefix and
1334 --exec-prefix correctly; it also returns the proper --rpath (or
1335 -R) value if FreeType has been built as a shared library.
1338 II. IMPORTANT CHANGES
1340 - Both PCF and BDF drivers now handle the SETWIDTH_NAME and
1341 ADD_STYLE_NAME properties. Values are appended to
1342 face->style_name; example: `Bold SemiCondensed'.
1344 - The PCF driver now handles bitmap fonts compressed with the LZW
1345 algorithm (extension .pcf.Z, compressed with `compress').
1347 - A new API function `FT_Get_CMap_Language_ID' (declared in
1348 `tttables.h') is available to get the language ID of a
1351 - The hexadecimal format of data after the `StartData' command in
1352 CID-keyed Type 1 fonts is now supported. While this can't occur
1353 in file-based fonts, it can happen in document-embedded
1354 resources of PostScript documents.
1356 - Embedded bitmaps in SFNT-based CFF fonts are now supported.
1358 - A simple API is now available to control FreeType's tracing
1359 mechanism if compiled with FT_DEBUG_LEVEL_TRACE. See the file
1360 `ftdebug.h' for more details.
1362 - YAMATO Masatake contributed improved handling of MacOS resource
1363 forks on non-MacOS platforms (for example, Linux can mount MacOS
1366 - Support for MacOS has been improved; there is now a new function
1367 `FT_New_Face_From_FSSpec' similar to `FT_New_Face' except that
1368 it accepts an FSSpec instead of a path.
1370 - The cache sub-system has been rewritten.
1372 - There is now support for deinstallation of faces.
1374 - A new API function `FTC_Manager_RemoveFaceID' has been added
1375 to delete all `idle' nodes that correspond to a given
1376 FTC_FaceID. All `locked' nodes (i.e., those with a reference
1377 count > 0), will be modified to prevent them from appearing in
1378 further lookups (they will be cleaned normally when their
1379 reference count reaches 0).
1381 - There is now support for point scaling (i.e., providing
1382 character sizes in points + dpis, instead of pixels).
1384 - Three abstract cache classes are now available:
1386 FTC_GCache: Used to store one glyph item per cache node,
1387 with the ability to group common attributes into
1388 `families'. This replaces the old
1389 FTC_GlyphCache class.
1391 FTC_ICache: Used to store one FT_Glyph per cache node. This
1392 extends FTC_GCache. Family definition, family
1393 comparison, and glyph loading are however left
1396 FTC_SCache: Used to store up to 16 small bitmaps per cache
1397 node. This extends FTC_GCache. Family
1398 definition, family comparison and glyph loading
1399 are however left to sub-classes.
1401 - The file `src/cache/ftcbasic.c' implements:
1403 FTC_ImageCache: Extends FTC_ICache; implements family
1404 definitions and glyph loading similar to the
1407 FTC_SBitCache: Extends FTC_SCache, implements family
1408 definitions and glyph loading similar to the
1411 Client applications should be able to extend FTC_GCache,
1412 FTC_ICache, or FTC_SCache much more easily (i.e., less code to
1413 write, and less callbacks). For example, one could envision
1414 caches that are capable of storing transformed (obliqued),
1415 stroked, emboldened, or colored glyph images. Use
1416 `ftcbasic.c' as an example.
1418 - All public APIs are now in `include/freetype/ftcache.h', (to
1419 be accessed as `FT_CACHE_H'). The contents of
1420 `include/freetype/cache/' is only needed by applications that
1421 wish to implement their own caches.
1423 - There were some major performance improvements through the use
1424 of various programming tricks. Cache hits are up to 70%
1425 faster than in the old code.
1427 - The FTC_CMapCache has been simplified. Charmaps can only be
1428 accessed by index right now. There is also a new API named
1429 `FT_Charmap_GetIndex' for this purpose.
1431 - The demo programs have been updated to the new code. The
1432 previous versions will not work with the current one.
1434 - Using an invalid face index in FT_Open_Face and friends now
1435 causes an error even if the font contains a single face only.
1440 - Wolfgang Domröse contributed support files for building FreeType
1441 on the Atari using the PureC compiler. Note that the Atari is a
1444 - Vitaliy Pasternak contributed project files for VS.NET 2003.
1447 ======================================================================
1449 CHANGES BETWEEN 2.1.7 and 2.1.6
1451 I. IMPORTANT BUG FIXES
1453 - Updated to newest libtool version, fixing build problems on
1456 - On Unix platforms, `make install' didn't copy the correct
1459 Note that version 2.1.7 contains the same library C source code as
1463 ======================================================================
1465 CHANGES BETWEEN 2.1.6 and 2.1.5
1467 I. IMPORTANT BUG FIXES
1469 - The PFR font driver didn't load kerning tables correctly, and
1470 the functions in FT_PFR_H didn't work at all.
1472 - Type 1 font files in binary format (PFB) with an end-of-file
1473 indicator weren't accepted by the FreeType engine.
1475 - Fonts which contain /PaintType and /StrokeWidth no longer cause
1476 a segfault. This bug has been introduced in version 2.1.5.
1478 - Fonts loaded with FT_LOAD_RENDER no longer cause strange
1479 results. This bug has been introduced in version 2.1.5.
1481 - Some Windows (bitmap) FNT/FON files couldn't be handled
1485 II. IMPORTANT CHANGES
1487 - The internal module API has been heavily changed in favor of
1488 massive simplifications within the font engine. This also means
1489 that authors of third-party modules must adapt their code to the
1492 NOTE: THE NEW SCHEME IS NOT COMPLETED YET. PLEASE WAIT UNTIL A
1495 - The PostScript parser has been enhanced to handle comments and
1496 strings correctly. Additionally, more syntax forms are
1499 - Added the optional unpatented hinting system for TrueType. It
1500 allows typefaces which need hinting to produce correct glyph
1501 forms (e.g., Chinese typefaces from Dynalab) to work acceptably
1502 without infringing Apple patents. This system is compiled only
1503 if TT_CONFIG_OPTION_COMPILE_UNPATENTED_HINTING is defined in
1504 ftoption.h (activated by default).
1509 - There is now a guard in the public header files to protect
1510 against inclusion of freetype.h from FreeType 1.
1512 - Direct inclusion of freetype.h and other public header files no
1513 longer works. You have to use the documented scheme
1515 #include <ft2build.h>
1516 #include FT_FREETYPE_H
1518 to load freetype.h with a symbolic name. This protects against
1519 renaming of public header files (which shouldn't happen but
1520 actually has, avoiding two public header files with the same
1524 ======================================================================
1526 CHANGES BETWEEN 2.1.5 and 2.1.4
1528 I. IMPORTANT BUG FIXES
1530 - Parsing the /CIDFontName field now removes the leading slash to
1531 be in sync with other font drivers.
1533 - gzip support was buggy. Some fonts could not be read.
1535 - Fonts which have nested subglyphs more than one level deep no
1536 longer cause a segfault.
1538 - Creation of synthetic cmaps for fonts in CFF format was broken
1541 - Numeric font dictionary entries for synthetic fonts are no
1544 - The font matrix wasn't applied to the advance width for Type1,
1545 CID, and CFF fonts. This caused problems when loading certain
1546 synthetic Type 1 fonts like `Helvetica Narrow'.
1548 - The test for the charset registry in BDF and PCF fonts is now
1551 - FT_Vector_Rotate sometimes returned strange values due to
1554 - The PCF driver now returns the correct number of glyphs
1555 (including an artificial `notdef' glyph at index 0).
1557 - FreeType now supports buggy CMaps which are contained in many
1558 CJK fonts from Dynalab.
1560 - Opening an invalid font on a Mac caused a segfault due to
1561 double-freeing memory.
1563 - BDF fonts with more than 32768 glyphs weren't supported
1567 II. IMPORTANT CHANGES
1569 - Accessing bitmap font formats has been synchronized. To do that
1570 the FT_Bitmap_Size structure has been extended to contain new
1571 fields `size', `x_ppem', and `y_ppem'.
1573 - The FNT driver now returns multiple faces, not multiple strikes.
1575 - The `psnames' module has been updated to the Adobe Glyph List
1578 - The `psnames' module now understands `uXXXX[X[X]]' glyph names.
1580 - The algorithm for guessing the font style has been improved.
1582 - For fonts in SFNT format, root->height is no longer increased if
1583 the line gap is zero. There exist fonts (containing e.g. form
1584 drawing characters) which intentionally have a zero line gap
1587 - ft_glyph_bbox_xxx flags are now deprecated in favour of
1590 - ft_module_xxx flags are now deprecated in favour of
1593 - FT_ENCODING_MS_{SJIS,GB2312,BIG5,WANSUNG,JOHAB} are now
1594 deprecated in favour of
1595 FT_ENCODING_{SJIS,GB2312,GIB5,WANSONG,JOHAB} -- those encodings
1596 are not specific to Microsoft.
1601 - The autohinter has been further improved; for example, `m'
1602 glyphs now retain its vertical symmetry.
1604 - Partial support of Mac fonts on non-Mac platforms.
1606 - `make refdoc' (after first `make') builds the HTML
1607 documentation. You need Python for this.
1609 - The make build system should now work more reliably on DOS-like
1612 - Support for EMX gcc and Watson C/C++ compilers on MS-DOS has
1615 - Better VMS build support.
1617 - Support for the pkg-config package by providing a `freetype.pc'
1620 - New configure option --with-old-mac-fonts for Darwin.
1622 - Some source files have been renamed (mainly to fit into the 8.3
1626 ======================================================================
1628 CHANGES BETWEEN 2.1.4 and 2.1.3
1630 I. IMPORTANT BUG FIXES
1632 - Updated to newest libtool version, fixing build problems on
1635 - A fix in the Gzip stream reader: It couldn't read certain .gz
1636 files properly due to a small typo. In certain cases, FreeType
1637 could also loop endlessly when trying to load tiny gzipped
1640 - The configure script now tries to use the system-wide zlib when
1641 it finds one (instead of the copy found in src/gzip). And
1642 `freetype-config' has been updated to return relevant flags in
1643 this case when invoked with `--libs' (e.g. `-lzlib').
1645 - Certain fonts couldn't be loaded by 2.1.3 because they lacked a
1646 Unicode charmap (e.g. SYMBOL.TTF). FreeType erroneously
1649 - The CFF loader was modified to accept fonts which only contain a
1650 subset of their reference charset. This prevented the correct
1651 use of PDF-embedded fonts.
1653 - The logic to detect Unicode charmaps has been modified. This is
1654 required to support fonts which include both 16-bit and 32-bit
1655 charmaps (like very recent asian ones) using the new 10 and 12
1658 - The TrueType loader now limits the depth of composite glyphs.
1659 This is necessary to prevent broken fonts to break the engine by
1660 blowing the stack with recursive glyph definitions.
1662 - The CMap cache is now capable of managing UCS-4 character codes
1663 that are mapped through extended charmaps in recent
1664 TrueType/OpenType fonts.
1666 - The cache sub-system now properly manages out-of-memory
1667 conditions instead of blindly reporting them to the caller.
1668 This means that it will try to empty the cache before restarting
1669 its allocations to see if that can help.
1671 - The PFR driver didn't return the list of available embedded
1674 - There was a nasty memory leak when using embedded bitmaps in
1675 certain font formats.
1678 II. IMPORTANT CHANGES
1680 - David Chester contributed some enhancements to the auto-hinter
1681 that significantly increase the quality of its output. The
1682 Postscript hinter was also improved in several ways.
1684 - The FT_RENDER_MODE_LIGHT render mode was implemented.
1686 - A new API function called `FT_Get_BDF_Property' has been added
1687 to FT_BDF_H to retrieve BDF properties from BDF _and_ PCF font
1688 files. THIS IS STILL EXPERIMENTAL, since it hasn't been
1689 properly tested yet.
1691 - A Windows FNT specific API has been added, mostly to access font
1692 headers. This is used by Wine.
1694 - TrueType tables without an `hmtx' table are now tolerated when
1695 an incremental interface is used. This happens for certain
1696 Type42 fonts passed from Ghostscript to FreeType.
1698 - The PFR font driver is now capable of returning the font family
1699 and style names when they are available (instead of the sole
1700 `FontID'). This is performed by parsing an *undocumented*
1701 portion of the font file!
1706 - The path stroker in FT_STROKER_H has entered beta stage. It now
1707 works very well, but its interface might change a bit in the
1708 future. More on this in later releases.
1710 - The documentation for FT_Size_Metrics didn't appear properly in
1713 - The file docs/VERSION.DLL has been updated to explain versioning
1714 with FreeType (i.e., comparing release/libtool/so numbers, and
1715 how to use them in autoconf scripts).
1717 - The installation documentation has been seriously revamped.
1718 Everything is now in the `docs' directory.
1721 ======================================================================
1723 CHANGES BETWEEN 2.1.3 and 2.1.2
1725 I. IMPORTANT BUG FIXES
1727 - FT_Vector_Transform had been incorrectly modified in 2.1.2,
1728 resulting in incorrect transformations being applied (for
1729 example, rotations were processed in opposite angles).
1731 - The format 8 and 12 TrueType charmap enumeration routines have
1732 been fixed (FT_Get_Next_Char returned invalid values).
1734 - The PFR font driver returned incorrect advance widths if the
1735 outline and metrics resolution defined in the font file were
1738 - FT_Glyph_To_Bitmap now returns successfully when called with an
1739 FT_BitmapGlyph argument (it previously returned an error).
1741 - A bug in the Type 1 loader that prevented valid font bounding
1742 boxes to be loaded from multiple master fonts.
1744 - The SFNT validation code has been rewritten. FreeType can now
1745 load `broken' fonts that were usable on Windows, but not with
1746 previous versions of the library.
1748 - The computation of bearings in the BDF driver has been fixed.
1750 - The Postscript hinter crashed when trying to hint certain glyphs
1751 (more precisely, when trying to apply hints to an empty glyph
1754 - The TrueType glyph loader now supports composites in `Apple
1755 format' (they differ slightly from Microsoft/OpenType ones in
1756 the way transformation offsets are computed).
1758 - FreeType was very slow at opening certain asian CID/CFF fonts,
1759 due to fixed increment in dynamic array re-allocations. This
1760 has been changed to exponential behaviour to get acceptable
1765 II. IMPORTANT CHANGES
1767 - The PCF driver now supports gzip-compressed font files natively.
1768 This means that you will be able to use all these bitmap fonts
1769 that come with XFree86 with FreeType (and libXft/libXft2, by
1772 - The automatic and postscript hinters have both been updated.
1773 This results in a relatively important increase of rendering
1774 quality since many nasty defaults have been suppressed. Please
1777 http://www.freetype.org/hinting/smooth-hinting.html
1779 for additional details on this topic.
1781 - The `load_flags' parameter of `FT_Load_Glyph' is now an FT_Int32
1782 (instead of just being an FT_Int). This breaks source and
1783 binary compatibility for 16bit systems only, while retaining
1784 both of them for 32 and 64 bit ones.
1786 Some new flags have been added consequently:
1788 FT_LOAD_NO_AUTOHINT :: Disable the use of the auto-hinter
1789 (but not native format hinters).
1791 FT_LOAD_TARGET_NORMAL :: Hint and render for normal
1792 anti-aliased displays.
1794 FT_LOAD_TARGET_MONO :: Hint and render for 1-bit displays.
1796 FT_LOAD_TARGET_LCD :: Hint and render for horizontal RGB or
1797 BGR sub-pixel displays (like LCD
1798 screens). THIS IS STILL
1801 FT_LOAD_TARGET_LCD_V :: Same as FT_LOAD_TARGET_LCD, for
1802 vertical sub-pixel displays (like
1803 rotated LCD screens). THIS IS STILL
1806 FT_LOAD_MONOCHROME is still supported, but only affects
1807 rendering, not the hinting.
1809 Note that the `ftview' demo program available in the `ft2demos'
1810 package has been updated to support LCD-optimized display on
1811 non-paletted displays (under Win32 and X11).
1813 - The PFR driver now supports embedded bitmaps (all formats
1814 supported), and returns correct kerning metrics for all glyphs.
1816 - The TrueType charmap loader now supports certain `broken' fonts
1817 that load under Windows without problems.
1819 - The cache API has been slightly modified (it's still a beta!):
1821 - The type FTC_ImageDesc has been removed; it is now replaced
1822 by FTC_ImageTypeRec. Note that one of its fields is a
1823 `load_flag' parameter for FT_Load_Glyph.
1825 - The field `num_grays' of FT_SBitRec has been changed to
1826 `max_grays' in order to fit within a single byte. Its
1827 maximum value is thus 255 (instead of 256 as previously).
1832 - Added support for the DESTDIR variable during `make install'.
1833 This simplifies packaging of FreeType.
1835 - Included modified copies of the ZLib sources in `src/gzip' in
1836 order to support gzip-compressed PCF fonts. We do not use the
1837 system-provided zlib for now, though this is a probable
1838 enhancement for future releases.
1840 - The DocMaker tool used to generate the on-line API reference has
1841 been completely rewritten. It is now located in
1842 `src/tools/docmaker/docmaker.py'. Features:
1844 - better cross-referenced output
1845 - more polished output
1846 - uses Python regular expressions (though it didn't speed the
1848 - much more modular structure, which allows for different
1849 `backends' in order to generate HTML, XML, or whatever
1852 One can regenerate the API reference by calling:
1854 python src/tools/docmaker/docmaker.py \
1856 --title=FreeType-2.1.3 \
1857 --output=<outputdirectory>
1858 include/freetype/*.h \
1859 include/freetype/config/*.h \
1860 include/freetype/cache/*.h
1862 - A new, experimental, support for incremental font loading (i.e.,
1863 loading of fonts where the glyphs are not in the font file
1864 itself, but provided by an external component, like a Postscript
1865 interpreter) has been added by Graham Asher. This is still work
1866 in progress, however.
1868 - A new, EXPERIMENTAL, path stroker has been added. It doesn't
1869 suffer from severe rounding errors and treat bezier arcs
1870 directly. Still work in progress (i.e. not part of the official
1871 API). See the file <freetype/ftstroker.h> for some of the
1874 - The massive re-formatting of sources and internal re-design is
1875 still under-way. Many internal functions, constants, and types
1879 ======================================================================
1881 CHANGES BETWEEN 2.1.2 and 2.1.1
1883 I. IMPORTANT BUG FIXES
1885 - Many font drivers didn't select a Unicode charmap by default
1886 when a new face was opened (with the FT_CONFIG_OPTION_USE_CMAPS
1887 options enabled), causing many applications to not be able to
1888 display text correctly with the 2.1.x releases.
1890 - The PFR driver had a bug in its composite loading code that
1891 produces incorrectly placed accents with many fonts.
1893 - The Type42 driver crashed sometimes due to a nasty bug.
1895 - The Type 1 custom encoding charmap didn't handle the case where
1896 the first glyph index wasn't 0.
1898 - A serious typo in the TrueType composite loader produced
1899 incorrectly placed glyphs in fonts like `Wingdings' and a few
1905 - The Win32 Visual C++ project file has been updated to include
1906 the PFR driver as well.
1908 - `freetype.m4' is now installed by default by `make install' on
1911 - The function FT_Get_PS_Font_Info now works with CID and Type42
1915 ======================================================================
1917 CHANGES BETWEEN 2.1.1 and 2.1.0
1919 I. IMPORTANT BUG FIXES
1921 - The `version_info' returned by `freetype-config' in 2.1.0
1922 returned an invalid value. It now returns 9:1:3 (2.0.9 returned
1925 - Version 2.1.0 couldn't be linked against applications on Win32
1926 and Amiga systems due to a new debug function that wasn't
1927 properly propagated to the system-specific directory in
1930 - Various MacOS and Mac OS X specific fixes.
1932 - Fixed a bug in the TrueType charmap validation routines that
1933 made version 2.1.0 too restrictive -- many popular fonts have
1936 - There was still a very small difference between the monochrome
1937 glyph bitmaps produced by FreeType 1.x and FreeType 2.x with the
1938 bytecode interpreter enabled. This was caused by an invalid
1939 flag setting in the TrueType glyph loader, making the rasterizer
1940 change its drop-out control mode. Now the results should
1941 _really_ be completely identical.
1943 - The TrueType name table loader has been improved to support many
1944 popular though buggy Asian fonts. It now ignores empty name
1945 entries, invalid pointer offsets and a few other incorrect
1946 subtleties. Moreover, name strings are now loaded on demand,
1947 which reduces the memory load of many faces (e.g. the ARIAL.TTF
1948 font file contains a 10kByte name table with 70 names).
1950 - Fixed a bug in the Postscript hinter that prevented family blues
1951 substitution to happen correctly.
1956 - Three new font drivers in this release:
1958 * A BDF font driver, contributed by Franco Zappa Nardelli,
1959 heavily modified by Werner Lemberg. It also supports
1960 anti-aliased bitmaps (using a slightly extended BDF format).
1962 * A Type42 font driver, contributed by Roberto Alameda. It is
1963 still experimental but seems to work relatively well.
1965 * A PFR font driver, contributed by David Turner himself. It
1966 doesn't support PFR hinting -- note that BitStream has at
1967 least two patents on this format!
1972 - The cache sub-system has been optimized in important ways.
1973 Cache hits are now significantly faster. For example, using the
1974 CMap cache is about twice faster than calling FT_Get_Char_Index
1975 on most platforms. Similarly, using an SBit cache is about five
1976 times faster than loading the bitmaps from a bitmap file, and
1977 300 to 500 times faster than generating them from a scalable
1980 Note that you should recompile your sources if you designed a
1981 custom cache class for the FT2 Cache subsystem, since the
1982 changes performed are source, but not binary, compatible.
1985 ======================================================================
1987 CHANGES BETWEEN 2.1.0 and 2.0.9
1989 I. IMPORTANT BUG FIXES
1991 - The TrueType bytecode interpreter has been fixed to produce
1992 _exactly_ the same output as FreeType 1.x. Previous differences
1993 were due to slightly distinct fixed-point computation routines
1994 used to perform dot products and vector length measurements.
1996 It seems that native TrueType hinting is _extremely_ sensitive
1997 to rounding errors. The required vector computation routines
1998 have been optimized and placed within the `ttinterp.c' file.
2000 - Fixed the parsing of accelerator tables in the PCF font driver.
2002 - Fixed the Type1 glyph loader routine used to compute the font's
2003 maximum advance width.
2008 - The `configure' script used on Unix systems has been modified to
2009 check that GNU Make is being used to build the library.
2010 Otherwise, it will display a message proposing to use the
2011 GNUMAKE environment variable to name it.
2013 The Unix-specific file README.UNX has been modified accordingly.
2018 - The FreeType License in `docs/FTL.TXT' has been updated to
2019 include a proposed preferred disclaimer. If you are using
2020 FreeType in your products, you are encouraged (but not mandated)
2021 to use the following text in your documentation:
2024 Portions of this software are copyright © 1996-2002 The
2025 FreeType Project (www.freetype.org). All rights reserved.
2028 - The default size of the render pool has been reduced to 16kByte.
2029 This shouldn't result in any noticeable performance penalty,
2030 unless you are using the engine as-is to render very large and
2033 - The FreeType 2 redesign has begun. More information can be
2036 http://www.freetype.org/freetype2/redesign.html
2038 The following internal changes have been performed within the
2039 sources of this release:
2041 - Many internal types have been renamed to increase
2042 consistency. The following should be true, except for
2045 * All structure types have a name ending in `Rec' (short
2048 * A pointer-to-structure type has the same name as the
2049 structure, _without_ the `Rec' suffix.
2053 typedef struct FooRec_
2059 - Many internal macros have been renamed to increase
2060 consistency. The following should be true:
2062 * All macros have a name beginning with `FT_'. This
2063 required a few changes like
2067 REALLOC => FT_REALLOC
2069 * All macros are completely UPPERCASE. This required a
2072 READ_Short => FT_READ_SHORT
2073 NEXT_Short => FT_NEXT_SHORT
2074 GET_ULongLE => FT_GET_ULONG_LE
2075 MEM_Set => FT_MEM_SET
2076 MEM_Copy => FT_MEM_COPY
2079 * Whenever possible, all macro names follow the
2080 FT_<OBJECT>_<METHOD> pattern. For example
2082 ACCESS_Frame => FT_FRAME_ENTER
2083 FORGET_Frame => FT_FRAME_EXIT
2084 EXTRACT_Frame => FT_FRAME_EXTRACT
2085 RELEASE_Frame => FT_FRAME_RELEASE
2087 FILE_Pos => FT_STREAM_POS
2088 FILE_Seek => FT_STREAM_SEEK
2089 FILE_Read => FT_STREAM_READ
2090 FILE_ReadAt => FT_STREAM_READ_AT
2091 READ_Fields => FT_STREAM_READ_FIELDS
2093 - Many internal functions have been renamed to follow the
2094 FT_<Object>_<Method> pattern. For example:
2096 FT_Seek_Stream => FT_Stream_Seek
2097 FT_Read_Stream_At => FT_Stream_ReadAt
2098 FT_Done_Stream => FT_Stream_Close
2099 FT_New_Stream => FT_Stream_Open
2100 FT_New_Memory_Stream => FT_Stream_OpenMemory
2101 FT_Extract_Frame => FT_Stream_ExtractFrame
2103 Note that method names do not contain `_'.
2105 - The FT_ALLOC_ARRAY and FT_REALLOC_ARRAY have been replaced
2106 with FT_NEW_ARRAY and FT_RENEW_ARRAY which do not take a
2107 type as the fourth argument. Instead, the array element
2108 type size is computed automatically from the type of the
2109 target pointer used.
2111 - A new object class, FT_CMap, has been introduced. These
2112 internal objects are used to model character maps. This
2113 eases the support of additional charmap types within the
2116 - A new configuration file named `ftstdlib.h' has been added
2117 to `include/freetype/config'. It is used to define aliases
2118 for _every_ routine of the ISO C library that the font
2119 engine uses. Each aliases has a `ft_' prefix
2120 (e.g. `ft_strlen' is an alias for `strlen').
2122 This is used to ease the porting of FreeType 2 to exotic
2123 runtime environments where the ISO C Library isn't available
2124 (e.g. XFree86 extension modules).
2126 More details are available in the `ChangeLog' file.
2129 ======================================================================
2131 CHANGES BETWEEN 2.0.9 and 2.0.8
2133 I. IMPORTANT BUG FIXES
2135 - Certain fonts like `foxjump.ttf' contain broken name tables with
2136 invalid entries and wild offsets. This caused FreeType to crash
2137 when trying to load them.
2139 The SFNT `name' table loader has been fixed to be able to
2140 support these strange fonts.
2142 Moreover, the code in charge of processing this table has been
2143 changed to always favour Windows-formatted entries over other
2144 ones. Hence, a font that works on Windows but not on the Mac
2145 will load cleanly in FreeType and report accurate values for
2146 Family & PostScript names.
2148 - The CID font driver has been fixed. It unfortunately returned a
2149 Postscript Font name with a leading slash, as in
2150 `/MunhwaGothic-Regular'.
2152 - FreeType 2 should now compile fine on AIX 4.3.3 as a shared
2155 - A bug in the Postscript hinter has been found and fixed,
2156 removing un-even stem widths at small pixel sizes (like 14-17).
2158 This improves the quality of a certain number of Postscript
2164 - A new function named `FT_Library_Version' has been added to
2165 return the current library's major, minor, and patch version
2166 numbers. This is important since the macros FREETYPE_MAJOR,
2167 FREETYPE_MINOR, and FREETYPE_PATCH cannot be used when the
2168 library is dynamically linked by a program.
2170 - Two new APIs have been added: `FT_Get_First_Char' and
2173 Together, these can be used to iterate efficiently over the
2174 currently selected charmap of a given face. Read the API
2175 reference for more details.
2180 - The FreeType sources are under heavy internal re-factoring. As
2181 a consequence, we have created a branch named `STABLE' on the
2182 CVS to hold all future releases/fixes in the 2.0.x family.
2184 The HEAD branch now contains the re-factored sources and
2185 shouldn't be used for testing or packaging new releases. In
2186 case you would like to access the 2.0.9 sources from our CVS
2187 repository, use the tag `VER-2-0-9'.
2190 ======================================================================
2192 CHANGES BETWEEN 2.0.8 and 2.0.7
2194 I. IMPORTANT BUG FIXES
2196 - There was a small but nasty bug in `freetype-config.in' which
2197 caused the `freetype-config' script to fail on Unix.
2199 This didn't prevent the installation of the library or even its
2200 execution, but caused problems when trying to compile many Unix
2201 packages that depend on it.
2203 - Some TrueType or OpenType fonts embedded in PDF documents do not
2204 have a 'cmap', 'post' and 'name' as is required by the
2205 specification. FreeType no longer refuses to load such fonts.
2207 - Various fixes to the PCF font driver.
2210 ======================================================================
2212 CHANGES BETWEEN 2.0.7 and 2.0.6
2214 I. IMPORTANT BUG FIXES
2216 - Fixed two bugs in the Type 1 font driver. The first one
2217 resulted in a memory leak in subtle cases. The other one caused
2218 FreeType to crash when trying to load `.gsf' files (Ghostscript
2219 so-called Postscript fonts).
2221 (This made _many_ KDE applications crash on certain systems.
2222 FreeType _is_ becoming a critical system component on Linux :-)
2224 - Fixed a memory leak in the CFF font driver.
2226 - Fixed a memory leak in the PCF font driver.
2228 - Fixed the Visual C++ project file
2229 `builds/win32/visualc/freetype.dsp' since it didn't include the
2230 Postscript hinter component, causing errors at build time.
2232 - Fixed a small rendering bug in the anti-aliased renderer that
2233 only occurred when trying to draw thin (less than 1 pixel)
2236 - Fixed `builds/unix/freetype2.a4' which is used to generate a
2237 valid `freetype2.m4' for use with autoconf.
2239 - Fixed the OpenVMS Makefiles.
2244 - Added `configure' and `install' scripts to the top-level
2245 directory. A GNU-style installation is thus now easily possible
2248 ./configure <options>
2253 ======================================================================
2255 CHANGES BETWEEN 2.0.6 and 2.0.5
2257 I. IMPORTANT BUG FIXES
2259 - It wasn't possible to load embedded bitmaps when the auto-hinter
2260 was used. This is now fixed.
2262 - The TrueType font driver didn't load some composites properly
2263 (the sub-glyphs were slightly shifted, and this was only
2264 noticeable when using monochrome rendering).
2266 - Various fixes to the auto-hinter. They merely improve the
2267 output of sans-serif fonts. Note that there are still problems
2268 with serifed fonts and composites (accented characters).
2270 - All scalable font drivers erroneously returned un-fitted glyph
2271 advances when hinting was requested. This created problems for
2272 a number of layout applications. This is a very old bug that
2273 got undetected mainly because most test/demo program perform
2274 rounding explicitly or implicitly (through the cache).
2276 - `FT_Glyph_To_Bitmap' did erroneously modify the source glyph in
2279 - `glnames.py' still contained a bug that made FreeType return
2280 invalid names for certain glyphs.
2282 - The library crashed when loading certain Type 1 fonts like
2283 `sadn.pfb' (`Stalingrad Normal'), which appear to contain
2284 pathetic font info dictionaries.
2286 - The TrueType glyph loader is now much more paranoid and checks
2287 everything when loading a given glyph image. This was necessary
2288 to avoid problems (crashes and/or memory overwrites) with broken
2289 fonts that came from a really buggy automatic font converter.
2292 II. IMPORTANT UPDATES AND NEW FEATURES
2294 - Important updates to the Mac-specific parts of the library.
2296 - The caching sub-system has been completely re-designed, and its
2297 API has evolved (the old one is still supported for backward
2300 The documentation for it is not yet completed, sorry. For now,
2301 you are encouraged to continue using the old API. However, the
2302 ftview demo program in the ft2demos package has already been
2303 updated to use the new caching functions.
2305 - A new charmap cache is provided too. See `FTC_CMapCache'. This
2306 is useful to perform character code -> glyph index translations
2307 quickly, without the need for an opened FT_Face.
2309 - A NEW POSTSCRIPT HINTER module has been added to support native
2310 hints in the following formats: PostScript Type 1, PostScript
2313 Please test! Note that the auto-hinter produces better results
2314 for a number of badly-hinted fonts (mostly auto-generated ones)
2317 - A memory debugger is now part of the standard FreeType sources.
2318 To enable it, define FT_DEBUG_MEMORY in
2319 <freetype/config/ftoption.h>, and recompile the library.
2321 Additionally, define the _environment_ variable FT_DEBUG_MEMORY
2322 and run any program using FreeType. When the library is exited,
2323 a summary of memory footprints and possible leaks will be
2326 This works transparently with _any_ program that uses FreeType.
2327 However, you will need a lot of memory to use this (allocated
2328 blocks are never released to the heap to detect double deletes
2334 - We are aware of subtle differences between the output of
2335 FreeType versions 1 and 2 when it comes to monochrome
2336 TrueType-hinted glyphs. These are most probably due to small
2337 differences in the monochrome rasterizers and will be worked out
2338 in an upcoming release.
2340 - We have decided to fork the sources in a `stable' branch, and an
2341 `unstable' one, since FreeType is becoming a critical component
2342 of many Unix systems.
2344 The next bug-fix releases of the library will be named 2.0.7,
2345 2.0.8, etc., while the `2.1' branch will contain a version of
2346 the sources where we will start major reworking of the library's
2347 internals, in order to produce FreeType 2.2.0 (or even 3.0) in a
2348 more distant future.
2350 We also hope that this scheme will allow much more frequent
2351 releases than in the past.
2354 ======================================================================
2356 CHANGES BETWEEN 2.0.5 and 2.0.4
2358 NOTE THAT 2.0.5 DOES NOT CONTAIN THE POSTSCRIPT HINTER. THIS MODULE
2359 WILL BE PART OF THE NEXT RELEASE (EITHER 2.0.6 or 2.1)
2361 - Fixed a bug that made certain glyphs, like `Cacute', `cacute' and
2362 `lslash' unavailable from Unicode charmaps of Postscript fonts.
2363 This prevented the correct display of Polish text, for example.
2365 - The kerning table of Type 1 fonts was loaded by FreeType, when its
2366 AFM file was attached to its face, but the
2367 FT_FACE_FLAG_HAS_KERNING bit flags was not set correctly,
2368 preventing FT_Get_Kerning to return meaningful values.
2370 - Improved SFNT (TrueType & OpenType) charmap support. Slightly
2371 better performance, as well as support for the new formats defined
2372 by the OpenType 1.3 specification (8, 10, and 12)
2374 - Fixed a serious typo in `src/base/ftcalc.c' which caused invalid
2375 computations in certain rare cases, producing ugly artefacts.
2377 - The size of the EM square is computed with a more accurate
2378 algorithm for Postscript fonts. The old one caused slight errors
2379 with embedded fonts found in PDF documents.
2381 - Fixed a bug in the cache manager that prevented normal LRU
2382 behaviour within the cache manager, causing unnecessary reloads
2383 (for FT_Face and FT_Size objects only).
2385 - Added a new function named `FT_Get_Name_Index' to retrieve the
2386 glyph index of a given glyph name, when found in a face.
2388 - Added a new function named `FT_Get_Postscript_Name' to retrieve
2389 the `unique' Postscript font name of a given face.
2391 - Added a new public header size named FT_SIZES_H (or
2392 <freetype/ftsizes.h>) providing new FT_Size-management functions:
2393 FT_New_Size, FT_Activate_Size, FT_Done_Size.
2395 - Fixed a reallocation bug that generated a dangling pointer (and
2396 possibly memory leaks) with Postscript fonts (in
2397 src/psaux/psobjs.c).
2399 - Many fixes for 16-bit correctness.
2401 - Removed many pedantic compiler warnings from the sources.
2403 - Added an Amiga build directory in `builds/amiga'.
2406 ======================================================================
2408 CHANGES BETWEEN 2.0.4 and 2.0.3
2410 - Fixed a rather annoying bug that was introduced in 2.0.3. Namely,
2411 the font transformation set through FT_Set_Transform was applied
2412 twice to auto-hinted glyphs, resulting in incorrectly rotated text
2415 - Fixed _many_ compiler warnings. FT2 should now compile cleanly
2416 with Visual C++'s most pedantic warning level (/W4). It already
2417 compiled fine with GCC and a few other compilers.
2419 - Fixed a bug that prevented the linear advance width of composite
2420 TrueType glyphs to be correctly returned.
2422 - Fixed the Visual C++ project files located in
2423 `builds/win32/visualc' (previous versions used older names of the
2426 - Many 32-bit constants have an `L' appended to their value, in
2427 order to improve the 16-bitness of the code. Someone is actually
2428 trying to use FT2 on an Atari ST machine!
2430 - Updated the `builds/detect.mk' file in order to automatically
2431 build FT2 on AIX systems. AIX uses `/usr/sbin/init' instead of
2432 `/sbin/init' and wasn't previously detected as a Unix platform by
2433 the FreeType build system.
2435 - Updated the Unix-specific portions of the build system (new
2436 libtool version, etc.).
2438 - The SFNT kerning loader now ensures that the table is sorted
2439 (since some problem fonts do not meet this requirement).
2442 =======================================================================
2444 CHANGES BETWEEN 2.0.3 and 2.0.2
2446 I. CHANGES TO THE MODULES / FONT DRIVERS
2448 - THE AUTO-HINTER HAS BEEN SLIGHTLY IMPROVED, in order to fix
2449 several annoying artefacts, mainly:
2451 - Blue zone alignment of horizontal stems wasn't performed
2452 correctly, resulting in artefacts like the `d' being placed
2453 one pixel below the `b' in some fonts like Time New Roman.
2455 - Overshoot thresholding wasn't performed correctly, creating
2456 unpleasant artefacts at large character pixel sizes.
2458 - Composite glyph loading has been simplified. This gets rid
2459 of various artefacts where the components of a composite
2460 glyphs were not correctly spaced.
2462 These are the last changes to the current auto-hinting module.
2463 A new hinting sub-system is currently in the work in order to
2464 support native hints in Type 1 / CFF / OpenType fonts, as well
2465 as globally improve rendering.
2467 - The PCF driver has been fixed. It reported invalid glyph
2468 dimensions for the fonts available on Solaris.
2470 - The Type 1, CID and CFF drivers have been modified to fix the
2471 computation of the EM size.
2473 - The Type 1 driver has been fixed to avoid a dangerous bug that
2474 crashed the library with non-conforming fonts (i.e. ones that do
2475 not place the .notdef glyph at position 0).
2477 - The TrueType driver had a rather subtle bug (dangling pointer
2478 when loading composite glyphs) that could crash the library in
2482 II. HIGH-LEVEL API CHANGES
2484 - The error code enumeration values have been changed. An error
2485 value is decomposed in a generic error code, and a module
2486 number. see <freetype/fterrors.h> for details.
2488 - A new public header file has been introduced, named
2489 FT_TRIGONOMETRY_H (include/freetype/fttrig.h), providing
2490 trigonometric functions to compute sines, cosines, arctangents,
2491 etc. with 16.16 fixed precision. The implementation is based on
2492 the CORDIC algorithm and is very fast while being sufficiently
2498 - Added BeOS-specific files in the old build sub-system. Note
2499 that no changes were required to compile the library with Jam.
2501 - The configuration is now capable of automatically detecting
2502 64-bit integers on a set of predefined compilers (GCC, Visual
2503 C++, Borland C++) and will use them by default. This provides a
2504 small performance boost.
2506 - A small memory leak that happened when opening 0-sized files
2507 (duh!) have been fixed.
2509 - Fixed bezier stack depth bug in the routines provided by the
2510 FT_BBOX_H header file. Also fixed similar bugs in the
2513 - The outline bounding box code has been rewritten to use direct
2514 computations, instead of bezier sub-division, to compute the
2515 exact bounding box of glyphs. This is slightly slower but more
2518 - The build system has been improved and fixed, mainly to support
2519 `make' on Windows 2000 correctly, avoid problems with `make
2520 distclean' on non Unix systems, etc.
2522 - Hexadecimal constants have been suffixed with `U' to avoid
2523 problems with certain compilers on 64-bit platforms.
2525 - A new directory named `src/tools' has been created. It contains
2526 Python scripts and simple unit test programs used to develop the
2529 - The DocMaker tool has been moved from `docs' to `src/tools' and
2530 has been updated with the following:
2532 - Now accepts the `--title=XXXX' or `-t XXXX' option from the
2533 command line to set the project's name in the generated API
2536 - Now accepts the `--output=DIR' or `-o DIR' option from the
2537 command line to set the output directory for all generated
2540 - Now accepts the `--prefix=XXXX' or `-p XXX' option from the
2541 command line to set the file prefix to use for all
2542 generated HTML files.
2544 - Now generates the current time/data on each generated page
2545 in order to distinguish between versions.
2547 DocMaker can be used with other projects now, not only FT2
2548 (e.g. MLib, FTLayout, etc.).
2551 ======================================================================
2553 CHANGES BETWEEN 2.0.2 and 2.0.1
2555 I. CHANGES TO THE MODULES / FONT DRIVERS
2557 - THE TRUETYPE BYTECODE INTERPRETER IS NOW TURNED OFF, in order to
2558 avoid legal problems with the Apple patents. It seems that we
2559 mistakenly turned this option on in previous releases of the
2562 Note that if you want to use the bytecode interpreter in order
2563 to get high-quality TrueType rendering, you will need to toggle
2564 by hand the definition of the
2565 TT_CONFIG_OPTION_BYTECODE_INTERPRETER macro in the file
2566 `include/freetype/config/ftoption.h'.
2568 - The CFF driver has been improved by Tom Kacvinsky and Sander van
2571 * Support for `seac' emulation.
2572 * Support for `dotsection'.
2573 * Support for retrieving glyph names through
2574 `FT_Get_Glyph_Name'.
2576 The first two items are necessary to correctly a large number of
2577 Type 1 fonts converted to the CFF formats by Adobe Acrobat.
2579 - The Type 1 driver was also improved by Tom & others:
2581 * Better EM size computation.
2582 * Better support for synthetic (transformed) fonts.
2583 * The Type 1 driver returns the charstrings corresponding to
2584 each glyph in the `glyph->control_data' field after a call to
2585 `FT_Load_Glyph' (thanks Ha Shao).
2587 - Various other bugfixes, including the following:
2589 * Fixed a nasty memory leak in the Type 1 driver.
2590 * The autohinter and the pcf driver used static writable data
2591 when they shouldn't.
2592 * Many casts were added to make the code more 64-bits safe. It
2593 also now compiles on Windows XP 64-bits without warnings.
2594 * Some incorrect writable statics were removed in the `autohint'
2595 and `pcf' drivers. FreeType 2 now compiles on Epoc again.
2598 II. CHANGES TO THE HIGH-LEVEL API
2600 - The library header files inclusion scheme has been changed. The
2601 old scheme looked like:
2603 #include <freetype/freetype.h>
2604 #include <freetype/ftglyph.h>
2605 #include <freetype/ftcache.h>
2606 #include <freetype/cache/ftimage.h>
2610 #include <ft2build.h>
2611 #include FT_FREETYPE_H
2614 #include FT_CACHE_IMAGE_H
2616 NOTE THAT THE OLD INCLUSION SCHEME WILL STILL WORK WITH THIS
2617 RELEASE. HOWEVER, WE DO NOT GUARANTEE THAT THIS WILL STILL BE
2618 TRUE IN THE NEXT ONE (A.K.A. FREETYPE 2.1).
2620 The file <ft2build.h> is used to define the header filename
2621 macros. The complete and commented list of macros is available
2622 in the API reference under the section name `Header File Macros'
2625 For more information, see section I of the following document:
2627 http://www.freetype.org/
2628 freetype2/docs/tutorial/step1.html
2632 http://freetype.sourceforge.net/
2633 freetype2/docs/tutorial/step1.html
2635 - Many, many comments have been added to the public source file in
2636 order to automatically generate the API Reference through the
2637 `docmaker.py' Python script.
2639 The latter has been updated to support the grouping of sections
2640 in chapters and better index sort. See:
2642 http://www.freetype.org/freetype2/docs/reference/ft2-toc.html
2645 III. CHANGES TO THE BUILD PROCESS
2647 - If you are not building FreeType 2 with its own build system
2648 (but with your own Makefiles or project files), you will need to
2649 be aware that the build process has changed a little bit.
2651 You don't need to put the `src' directory in the include path
2652 when compiling any FT2 component. Instead, simply put the
2653 component's directory in the current include path.
2655 So, if you were doing something like:
2657 cc -c -Iinclude -Isrc src/base/ftbase.c
2661 cc -c -Iinclude -Isrc/base src/base/ftbase.c
2663 If you were doing something like:
2666 cc -c -I../../include -I.. ftbase.c
2671 cc -c -I../../include ftbase.c
2674 ======================================================================
2676 CHANGES BETWEEN 2.0.1 and 2.0
2678 2.0.1 introduces a few changes:
2680 - Fixed many bugs related to the support of CFF / OpenType fonts.
2681 These formats are now much better supported though there is
2682 still work planned to deal with charset tables and PDF-embedded
2683 CFF files that use the old `seac' command.
2685 - The library could not be compiled in debug mode with a very
2686 small number of C compilers whose pre-processors didn't
2687 implement the `##' directive correctly (i.e. per se the ANSI C
2688 specification!) An elegant fix was found.
2690 - Added support for the free Borland command-line C++ Builder
2691 compiler. Use `make setup bcc32'. Also fixed a few source
2692 lines that generated new warnings with BCC32.
2694 - Fixed a bug in FT_Outline_Get_BBox when computing the extrema of
2697 - Updated the INSTALL file to add IDE compilation.
2699 - Other minor bug fixes, from invalid Type 1 style flags to
2700 correct support of synthetic (obliqued) fonts in the
2701 auto-hinter, better support for embedded bitmaps in a SFNT font.
2703 - Fixed some problems with `freetype-config'.
2705 Finally, the `standard' scheme for including FreeType headers is now
2706 gradually changing, but this will be explained in a later release
2709 And very special thanks to Tom Kacvinsky and YAMANO-UCHI Hidetoshi
2710 for their contributions!
2713 ======================================================================
2715 CHANGES BETWEEN beta8 and 2.0
2717 - Changed the default installation path for public headers from
2718 `include/freetype' to `include/freetype2'.
2720 Also added a new `freetype-config' that is automatically generated
2721 and installed on Unix and Cygwin systems. The script itself is
2722 used to retrieve the current install path, C compilation flags as
2723 well as linker flags.
2725 - Fixed several small bugs:
2727 * Incorrect max advance width for fixed-pitch Type 1 fonts.
2728 * Incorrect glyph names for certain TrueType fonts.
2729 * The glyph advance was not copied when FT_Glyph_To_Bitmap was
2731 * The linearHoriAdvance and linearVertAdvance fields were not
2732 correctly returned for glyphs processed by the auto-hinter.
2733 * `type1z' renamed back to `type1'; the old `type1' module has
2736 - Revamped the build system to make it a lot more generic. This
2737 will allow us to re-use nearly un-modified in lots of other
2738 projects (including FreeType Layout).
2740 - Changed `cid' to use `psaux' too.
2742 - Added the cache sub-system. See <freetype/ftcache.h> as well as
2743 the sources in `src/cache'. Note that it compiles but is still
2746 - Updated `docs/docmaker.py', a draft API reference is available at
2747 http://www.freetype.org/ft2api.html.
2749 - Changed `type1' to use `psaux'.
2751 - Created a new module named `psaux' to hold the Type 1 & Type 2
2752 parsing routines. It should be used by `type1', `cid', and `cff'
2755 - Fixed an important bug in `FT_Glyph_Get_CBox'.
2757 - Fixed some compiler warnings that happened since the TrueType
2758 bytecode decoder was deactivated by default.
2760 - Fixed two memory leaks:
2762 * The memory manager (16 bytes) isn't released in
2764 * Using custom input streams, the copy of the original stream was
2767 - Fixed the auto-hinter by performing automatic computation of the
2768 `filling direction' of each glyph. This is done through a simple
2769 and fast approximation, and seems to work (problems spotted by
2770 Werner though). The Arphic fonts are a lot nicer though there are
2771 still a lot of things to do to handle Asian fonts correctly.
2774 ======================================================================
2776 BETA-8 (RELEASE CANDIDATE) CHANGES
2778 - Deactivated the TrueType bytecode interpreter by default.
2780 - Deactivated the `src/type1' font driver. Now `src/type1z' is used
2783 - Updates to the build system. We now compile the library correctly
2784 under Unix system through `configure' which is automatically
2785 called on the first `make' invocation.
2787 - Added the auto-hinting module! Fixing some bugs here and there.
2789 - Found some bugs in the composite loader (seac) of the Type1-based
2792 - Renamed the directory `freetype2/config' to `freetype2/builds' and
2793 updated all relevant files.
2795 - Found a memory leak in the `type1' driver.
2797 - Incorporated Tom's patches to support flex operators correctly in
2798 OpenType/CFF fonts. Now all I need is to support pure CFF and CEF
2799 fonts to be done with this driver :-)
2801 - Added the Windows FNT/FON driver in `src/winfonts'. For now, it
2802 always `simulates' a Unicode charmap, so it shouldn't be
2803 considered completed right now.
2805 It is there to be more a proof of concept than anything else
2806 anyway. The driver is a single C source file, that compiles to 3
2809 I'm still working on the PCF/BDF drivers, but I'm too lazy to
2812 - CHANGES TO THE HIGH-LEVEL API
2814 * FT_Get_Kerning has a new parameter that allows you to select the
2815 coordinates of the kerning vector (font units, scaled, scaled +
2817 * The outline functions are now in <freetype/ftoutln.h> and not
2818 part of <freetype/freetype.h> anymore.
2819 * <freetype/ftmodule.h> now contains declarations for
2820 FT_New_Library, FT_Done_Library, FT_Add_Default_Modules.
2821 * The so-called convenience functions have moved from `ftoutln.c'
2822 to `ftglyph.c', and are thus available with this optional
2823 component of the library. They are declared in
2824 <freetype/ftglyph.h> now.
2825 * Anti-aliased rendering is now the default for FT_Render_Glyph
2826 (i.e. corresponds to render_mode == 0 == ft_render_mode_normal).
2827 To generate a monochrome bitmap, use ft_render_mode_mono, or the
2828 FT_LOAD_MONOCHROME flag in FT_Load_Glyph/FT_Load_Char.
2829 FT_LOAD_ANTI_ALIAS is still defined, but values to 0.
2830 * <freetype/freetype.h> now include <freetype/config/ftconfig.h>,
2831 solving a few headaches :-)
2832 * The type FT_GlyphSlotRec has now a `library' field.
2834 - CHANGES TO THE `ftglyph.h' API
2836 This API has been severely modified in order to make it simpler,
2837 clearer, and more efficient. It certainly now looks like a real
2838 `glyph factory' object, and allows client applications to manage
2839 (i.e. transform, bbox and render) glyph images without ever
2840 knowing their original format.
2842 - Added support for CID-keyed fonts to the CFF driver. Maybe
2843 support for pure CFF + CEF fonts should come in?
2845 - Cleaned up source code in order to avoid two functions with the
2846 same name. Also changed the names of the files in `type1z' from
2847 `t1XXXX' to `z1XXXX' in order to avoid any conflicts.
2849 `make multi' now works well :-)
2851 Also removed the use of `cidafm' for now, even if the source files
2852 are still there. This functionality will certainly go into a
2855 - ADDED SUPPORT FOR THE AUTO-HINTER
2857 It works :-) I have a demo program which simply is a copy of
2858 `ftview' that does a `FT_Add_Module(library,
2859 &autohinter_module_class)' after library initialization, and Type
2860 1 & OpenType/CFF fonts are now hinted.
2862 CID fonts are not hinted, as they include no charmap and the
2863 auto-hinter doesn't include `generic' global metrics computations
2866 Now, I need to release this thing to the FreeType 2 source.
2868 - CHANGES TO THE RENDERER MODULES
2870 The monochrome and smooth renderers are now in two distinct
2871 directories, namely `src/raster1' and `src/smooth'. Note that the
2872 old `src/renderer' is now gone.
2874 I ditched the 5-gray-levels renderers. Basically, it involved a
2875 simple #define toggle in 'src/raster1/ftraster.c'.
2877 FT_Render_Glyph, FT_Outline_Render & FT_Outline_Get_Bitmap now
2878 select the best renderer available, depending on render mode. If
2879 the current renderer for a given glyph image format isn't capable
2880 of supporting the render mode, another one will be found in the
2881 library's list. This means that client applications do not need
2882 to switch or set the renderers themselves (as in the latest
2883 change), they'll get what they want automatically. At last.
2885 Changed the demo programs accordingly.
2887 - MAJOR INTERNAL REDESIGN:
2889 A lot of internal modifications have been performed lately on the
2890 source in order to provide the following enhancements:
2892 * More generic module support:
2894 The FT_Module type is now defined to represent a handle to a
2895 given module. The file <freetype/ftmodule.h> contains the
2896 FT_Module_Class definition, as well as the module-loading public
2899 The FT_Driver type is still defined, and still represents a
2900 pointer to a font driver. Note that FT_Add_Driver is replaced
2901 by FT_Add_Module, FT_Get_Driver by FT_Get_Module, etc.
2903 * Support for generic glyph image types:
2905 The FT_Renderer type is a pointer to a module used to perform
2906 various operations on glyph image.
2908 Each renderer is capable of handling images in a single format
2909 (e.g. ft_glyph_format_outline). Its functions are used to:
2911 - transform an glyph image
2912 - render a glyph image into a bitmap
2913 - return the control box (dimensions) of a given glyph image
2915 The scan converters `ftraster.c' and `ftgrays.c' have been moved
2916 to the new directory `src/renderer', and are used to provide two
2917 default renderer modules.
2919 One corresponds to the `standard' scan-converter, the other to
2922 he current renderer can be set through the new function
2925 The old raster-related function FT_Set_Raster, FT_Get_Raster and
2926 FT_Set_Raster_Mode have now disappeared, in favor of the new:
2931 See the file <freetype/ftrender.h> for more details.
2933 These changes were necessary to properly support different
2934 scalable formats in the future, like bi-color glyphs, etc.
2936 * Glyph loader object:
2938 A new internal object, called a 'glyph loader' has been
2939 introduced in the base layer. It is used by all scalable format
2940 font drivers to load glyphs and composites.
2942 This object has been created to reduce the code size of each
2943 driver, as each one of them basically re-implemented its
2946 See <freetype/internal/ftobjs.h> and the FT_GlyphLoader type for
2949 * FT_GlyphSlot has new fields:
2951 In order to support extended features (see below), the
2952 FT_GlyphSlot structure has a few new fields:
2956 This field gives the linearly scaled (i.e. scaled but
2957 unhinted) advance width for the glyph, expressed as a 16.16
2958 fixed pixel value. This is useful to perform WYSIWYG text.
2961 This field gives the linearly scaled advance height for the
2962 glyph (relevant in vertical glyph layouts only). This is
2963 useful to perform WYSIWYG text.
2965 Note that the two above field replace the removed `metrics2'
2966 field in the glyph slot.
2969 This field is a vector that gives the transformed advance for
2970 the glyph. By default, it corresponds to the advance width,
2971 unless FT_LOAD_VERTICAL_LAYOUT was specified when calling
2972 FT_Load_Glyph or FT_Load_Char.
2975 This field gives the distance in integer pixels from the
2976 current pen position to the left-most pixel of a glyph image
2977 IF IT IS A BITMAP. It is only valid when the `format' field
2978 is set to `ft_glyph_format_bitmap', for example, after calling
2979 the new function FT_Render_Glyph.
2982 This field gives the distance in integer pixels from the
2983 current pen position (located on the baseline) to the top-most
2984 pixel of the glyph image IF IT IS A BITMAP. Positive values
2985 correspond to upwards Y.
2988 This is a new private field for the glyph slot. Client
2989 applications should not touch it.
2992 * Support for transforms and direct rendering in FT_Load_Glyph:
2994 Most of the functionality found in <freetype/ftglyph.h> has been
2995 moved to the core library. Hence, the following:
2997 - A transform can be specified for a face through
2998 FT_Set_Transform. this transform is applied by FT_Load_Glyph
2999 to scalable glyph images (i.e. NOT TO BITMAPS) before the
3000 function returns, unless the bit flag FT_LOAD_IGNORE_TRANSFORM
3001 was set in the load flags.
3003 - Once a glyph image has been loaded, it can be directly
3004 converted to a bitmap by using the new FT_Render_Glyph
3005 function. Note that this function takes the glyph image from
3006 the glyph slot, and converts it to a bitmap whose properties
3007 are returned in `face.glyph.bitmap', `face.glyph.bitmap_left'
3008 and `face.glyph.bitmap_top'. The original native image might
3009 be lost after the conversion.
3011 - When using the new bit flag FT_LOAD_RENDER, the FT_Load_Glyph
3012 and FT_Load_Char functions will call FT_Render_Glyph
3013 automatically when needed.
3015 - Reformatted all modules source code in order to get rid of the
3016 basic data types redifinitions (i.e. `TT_Int' instead of `FT_Int',
3017 `T1_Fixed' instead of `FT_Fixed'). Hence the format-specific
3018 prefixes like `TT_', `T1_', `T2_' and `CID_' are only used for
3019 relevant structures.
3022 ======================================================================
3024 OLD CHANGES FOR BETA 7
3026 - bug-fixed the OpenType/CFF parser. It now loads and displays my
3027 two fonts nicely, but I'm pretty certain that more testing is
3030 - fixed the crummy Type 1 hinter, it now handles accented characters
3031 correctly (well, the accent is not always well placed, but that's
3034 - added the CID-keyed Type 1 driver in `src/cid'. Works pretty well
3035 for only 13 Kb of code ;-) Doesn't read AFM files though, nor the
3036 really useful CMAP files..
3038 - fixed two bugs in the smooth renderer (src/base/ftgrays.c).
3039 Thanks to Boris Letocha for spotting them and providing a fix.
3041 - fixed potential `divide by zero' bugs in ftcalc.c.
3043 - added source code for the OpenType/CFF driver (still incomplete
3046 - modified the SFNT driver slightly to perform more robust header
3047 checks in TT_Load_SFNT_Header. This prevents certain font files
3048 (e.g. some Type 1 Multiple Masters) from being incorrectly
3049 `recognized' as TrueType font files..
3051 - moved a lot of stuff from the TrueType driver to the SFNT module,
3052 this allows greater code re-use between font drivers
3053 (e.g. TrueType, OpenType, Compact-TrueType, etc..)
3055 - added a tiny segment cache to the SFNT Charmap 4 decoder, in order
3056 to minimally speed it up..
3058 - added support for Multiple Master fonts in `type1z'. There is
3059 also a new file named <freetype/ftmm.h> which defines functions to
3060 manage them from client applications.
3062 The new file `src/base/ftmm.c' is also optional to the engine..
3064 - various formatting changes (e.g. EXPORT_DEF -> FT_EXPORT_DEF) +
3065 small bug fixes in FT_Load_Glyph, the `type1' driver, etc..
3067 - a minor fix to the Type 1 driver to let them apply the font matrix
3068 correctly (used for many oblique fonts..)
3070 - some fixes for 64-bit systems (mainly changing some FT_TRACE calls
3071 to use %p instead of %lx). Thanks to Karl Robillard.
3073 - fixed some bugs in the sbit loader (src/base/sfnt/ttsbit.c) +
3074 added a new flag, FT_LOAD_CROP_BITMAP to query that bitmaps be
3075 cropped when loaded from a file (maybe I should move the bitmap
3076 cropper to the base layer ??).
3078 - changed the default number of gray levels of the smooth renderer
3079 to 256 (instead of the previous 128). Of course, the human eye
3080 can't see any difference ;-)
3082 - removed TT_MAX_SUBGLYPHS, there is no static limit on the number
3083 of subglyphs in a TrueType font now..
3086 ======================================================================
3088 OLD CHANGES 16 May 2000
3090 - tagged `BETA-6' in the CVS tree. This one is a serious release
3091 candidate even though it doesn't incorporate the auto-hinter yet..
3093 - various obsolete files were removed, and copyright header updated
3095 - finally updated the standard raster to fix the monochrome
3096 rendering bug + re-enable support for 5-gray levels anti-aliasing
3099 - created new header files, and modified sources accordingly:
3101 <freetype/fttypes.h>
3102 - simple FreeType types, without the API
3103 <freetype/internal/ftmemory.h>
3104 - definition of memory-management macros
3106 - added the `DSIG' (OpenType Digital Signature) tag to
3109 - light update/cleaning of the build system + changes to the sources
3110 in order to get rid of _all_ compiler warnings with three
3113 gcc with `-ansi -pedantic -Wall -W', Visual C++ with `/W3 /WX' and
3116 IMPORTANT NOTE FOR WIN32-LCC USERS:
3118 | It seems the C pre-processor that comes with LCC is broken, it
3119 | doesn't recognize the ANSI standard directives # and ##
3120 | correctly when one of the argument is a macro. Also,
3123 | #define F(x) print##x
3127 | will get incorrectly translated to:
3131 | by its pre-processor. For this reason, you simply cannot build
3132 | FreeType 2 in debug mode with this compiler..
3134 - yet another massive grunt work. I've changed the definition of
3135 the EXPORT_DEF, EXPORT_FUNC, BASE_DEF & BASE_FUNC macros. These
3136 now take an argument, which is the function's return value type.
3138 This is necessary to compile FreeType as a DLL on Windows and
3139 OS/2. Depending on the compiler used, a compiler-specific keyword
3140 like __export or __system must be placed before (VisualC++) or
3141 after (BorlandC++) the type..
3143 Of course, this needed a lot of changes throughout the source code
3144 to make it compile again... All cleaned up now, apparently..
3146 Note also that there is a new EXPORT_VAR macro defined to allow
3147 the _declaration_ of an exportable public (constant)
3148 variable. This is the case of the raster interfaces (see
3149 ftraster.h and ftgrays.h), as well as each module's interface (see
3150 sfdriver.h, psdriver.h, etc..)
3152 - new feature: it is now possible to pass extra parameters to font
3153 drivers when creating a new face object. For now,
3154 this capability is unused. It could however prove to
3155 be useful in a near future..
3157 the FT_Open_Args structure was changes, as well as the internal
3158 driver interface (the specific `init_face' module function has
3159 now a different signature).
3161 - updated the tutorial (not finished though).
3163 - updated the top-level BUILD document
3165 - fixed a potential memory leak that could occur when loading
3168 - added the declaration of FT_New_Memory_Face in
3169 <freetype/freetype.h>, as it was missing from the public header
3170 (the implementation was already in `ftobjs.c').
3172 - the file <freetype/fterrors.h> has been seriously updated in order
3173 to allow the automatic generation of error message tables. See
3174 the comments within it for more information.
3176 - major directory hierarchy re-organisation. This was done for two
3179 * first, to ease the `manual' compilation of the library by
3180 requiring at lot less include paths :-)
3182 * second, to allow external programs to effectively access
3183 internal data fields. For example, this can be extremely
3184 useful if someone wants to write a font producer or a font
3185 manager on top of FreeType.
3187 Basically, you should now use the 'freetype/' prefix for header
3190 #include <freetype/freetype.h>
3191 #include <freetype/ftglyph.h>
3193 Some new include sub-directories are available:
3195 a. the `freetype/config' directory, contains two files used to
3196 configure the build of the library. Client applications
3197 should not need to look at these normally, but they can if
3200 #include <freetype/config/ftoption.h>
3201 #include <freetype/config/ftconfig.h>
3203 b. the `freetype/internal' directory, contains header files that
3204 describes library internals. These are the header files that
3205 were previously found in the `src/base' and `src/shared'
3209 As usual, the build system and the demos have been updated to
3210 reflect the change..
3212 Here's a layout of the new directory hierarchy:
3241 Compiling a module is now much easier, for example, the following
3242 should work when in the TOP_DIR directory on an ANSI build:
3244 gcc -c -I./include -I./src/base src/base/ftbase.c
3245 gcc -c -I./include -I./src/sfnt src/sfnt/sfnt.c
3248 (of course, using -Iconfig/<system> if you provide system-specific
3249 configuration files).
3251 - updated the structure of FT_Outline_Funcs in order to allow direct
3252 coordinate scaling within the outline decomposition routine (this
3253 is important for virtual `on' points with TrueType outlines) +
3254 updates to the rasters to support this..
3256 - updated the OS/2 table loading code in `src/sfnt/ttload.c' in
3257 order to support version 2 of the table (see OpenType 1.2 spec)
3259 - created `include/tttables.h' and `include/t1tables.h' to allow
3260 client applications to access some of the SFNT and T1 tables of a
3261 face with a procedural interface (see `FT_Get_Sfnt_Table') +
3262 updates to internal source files to reflect the change..
3264 - some cleanups in the source code to get rid of warnings when
3265 compiling with the `-Wall -W -ansi -pedantic' options in gcc.
3267 - debugged and moved the smooth renderer to `src/base/ftgrays.c' and
3268 its header to `include/ftgrays.h'
3270 - updated TT_MAX_SUBGLYPHS to 96 as some CJK fonts have composites
3271 with up to 80 sub-glyphs !! Thanks to Werner
3274 ======================================================================
3276 OLD CHANGES - 14-apr-2000
3278 - fixed a bug in the TrueType glyph loader that prevented the
3279 correct loading of some CJK glyphs in mingli.ttf
3281 - improved the standard Type 1 hinter in `src/type1'
3283 - fixed two bugs in the experimental Type 1 driver in `src/type1z'
3284 to handle the new XFree86 4.0 fonts (and a few other ones..)
3286 - the smooth renderer is now complete and supports sub-banding to
3287 render large glyphs at high speed. However, it is still located
3288 in `demos/src/ftgrays.c' and should move to the library itself in
3289 the next beta. NOTE: The smooth renderer doesn't compile in
3290 stand-alone mode anymore, but this should be fixed RSN..
3292 - introduced convenience functions to more easily deal with glyph
3293 images, see `include/ftglyph.h' for more details, as well as the
3294 new demo program named `demos/src/ftstring.c' that demonstrates
3297 - implemented FT_LOAD_NO_RECURSE in both the TrueType and Type 1
3298 drivers (this is required by the auto-hinter to improve its
3301 - changed the raster interface, in order to allow client
3302 applications to provide their own span-drawing callbacks.
3303 However, only the smooth renderer supports this. See
3304 `FT_Raster_Params' in the file `include/ftimage.h'.
3306 - fixed a small bug in FT_MulFix that caused incorrect transform
3309 - Note: The tutorial is out-of-date.
3312 ======================================================================
3314 OLD CHANGES - 12-mar-2000
3316 - changed the layout of configuration files : now, all ANSI
3317 configuration files are located in
3318 `freetype2/config'. System-specific over-rides can be placed in
3319 `freetype2/config/<system>'.
3321 - moved all configuration macros to `config/ftoption.h'
3323 - improvements in the Type 1 driver with AFM support
3325 - changed the fields in the FT_Outline structure : the old `flags'
3326 array is re-named `tags', while all ancient flags are encoded into
3327 a single unsigned int named `flags'.
3329 - introduced new flags in FT_Outline.flags (see
3330 ft_outline_.... enums in `ftimage.h').
3332 - changed outline functions to `FT_Outline_<action>' syntax
3334 - added a smooth anti-alias renderer to the demonstration programs
3336 - added Mac graphics driver (thanks Just)
3338 - FT_Open_Face changed in order to received a pointer to a
3339 FT_Open_Args descriptor..
3341 - various cleanups, a few more API functions implemented (see
3347 ======================================================================
3349 OLD CHANGES - 22-feb-2000
3351 - introduced the `psnames' module. It is used to:
3353 o convert a Postscript glyph name into the equivalent Unicode
3354 character code (used by the Type 1 driver(s) to synthesize on
3355 the fly a Unicode charmap).
3357 o provide an interface to retrieve the Postscript names of the
3358 Macintosh, Adobe Standard & Adobe Expert character codes.
3359 (the Macintosh names are used by the SFNT-module postscript
3360 names support routines, while the other two tables are used by
3361 the Type 1 driver(s)).
3363 - introduced the `type1z' alternate Type 1 driver. This is a (still
3364 experimental) driver for the Type 1 format that will ultimately
3365 replace the one in `src/type1'. It uses pattern matching to load
3366 data from the font, instead of a finite state analyzer. It works
3367 much better than the `old' driver with `broken' fonts. It is also
3368 much smaller (under 15 Kb).
3370 - the Type 1 drivers (both in `src/type1' and `src/type1z') are
3371 nearly complete. They both provide automatic Unicode charmap
3372 synthesis through the `psnames' module. No re-encoding vector is
3373 needed. (note that they still leak memory due to some code
3374 missing, and I'm getting lazy).
3376 Trivial AFM support has been added to read kerning information but
3377 wasn't exactly tested as it should ;-)
3379 - The TrueType glyph loader has been seriously rewritten (see the
3380 file `src/truetype/ttgload.c'. It is now much, much simpler as
3381 well as easier to read, maintain and understand :-) Preliminary
3382 versions introduced a memory leak that has been reported by Jack
3383 Davis, and is now fixed..
3385 - introduced the new `ft_glyph_format_plotter', used to represent
3386 stroked outlines like Windows `Vector' fonts, and certain Type 1
3387 fonts like `Hershey'. The corresponding raster will be written
3390 - FT_New_Memory_Face is gone. Likewise, FT_Open_Face has a new
3391 interface that uses a structure to describe the input stream, the
3392 driver (if required), etc..
3397 - Write FT_Get_Glyph_Bitmap and FT_Load_Glyph_Bitmap
3399 - Add a function like FT_Load_Character(face, char_code, load_flags)
3400 that would really embed a call to FT_Get_Char_Index then
3401 FT_Load_Glyph to ease developer's work.
3403 - Update the tutorial!
3405 - consider adding support for Multiple Master fonts in the Type 1
3408 - Test the AFM routines of the Type 1 drivers to check that kerning
3409 information is returned correctly.
3411 - write a decent auto-gridding component !! We need this to release
3417 - add a CFF/Type2 driver
3419 - add a FNT/PCF/HBF driver
3420 - add a Speedo driver from the X11 sources
3423 ======================================================================
3425 OLDER CHANGES - 27-jan-2000
3427 - updated the `sfnt' module interface to allow several SFNT-based
3428 drivers to co-exist peacefully
3430 - updated the `T1_Face' type to better separate Postscript font
3431 content from the rest of the FT_Face structure. Might be used
3432 later by the CFF/Type2 driver..
3434 - added an experimental replacement Type 1 driver featuring advanced
3435 (and speedy) pattern matching to retrieve the data from postscript
3438 - very minor changes in the implementation of FT_Set_Char_Size and
3439 FT_Set_Pixel_Sizes (they now implement default to lighten the font
3443 ======================================================================
3447 This file summarizes the changes that occurred since the last `beta'
3448 of FreeType 2. Because the list is important, it has been divided into
3453 I High-Level Interface (easier !)
3454 II Directory Structure
3455 III Glyph Image Formats
3461 ----------------------------------------------------------------------
3463 High-Level Interface:
3465 The high-level API has been considerably simplified. Here is how:
3467 - resource objects have disappeared. this means that face objects
3468 can now be created with a single function call (see FT_New_Face
3471 - when calling either FT_New_Face & FT_Open_Face, a size object
3472 and a glyph slot object are automatically created for the face,
3473 and can be accessed through `face->glyph' and `face->size' if
3474 one really needs to. In most cases, there's no need to call
3475 FT_New_Size or FT_New_Glyph.
3477 - similarly, FT_Load_Glyph now only takes a `face' argument
3478 (instead of a glyph slot and a size). Also, its `result'
3479 parameter is gone, as the glyph image type is returned in the
3480 field `face->glyph.format'
3482 - the list of available charmaps is directly accessible through
3483 `face->charmaps', counting `face->num_charmaps' elements. Each
3484 charmap has an 'encoding' field which specifies which known
3485 encoding it deals with. Valid values are, for example:
3487 ft_encoding_unicode (for ASCII, Latin-1 and Unicode)
3488 ft_encoding_apple_roman
3490 ft_encoding_adobe_standard
3491 ft_encoding_adobe_expert
3493 other values may be added in the future. Each charmap still
3494 holds its `platform_id' and `encoding_id' values in case the
3495 encoding is too exotic for the current library
3498 ----------------------------------------------------------------------
3500 Directory Structure:
3502 Should seem obvious to most of you:
3505 config/ -- configuration sub-makefiles
3507 unix/ -- platform-specific configuration files
3512 include/ -- public header files, those to be included
3513 directly by client apps
3515 src/ -- sources of the library
3516 base/ -- the base layer
3517 sfnt/ -- the sfnt `driver' (see the drivers section
3519 truetype/ -- the truetype driver
3520 type1/ -- the type1 driver
3521 shared/ -- some header files shared between drivers
3523 demos/ -- demos/tools
3525 docs/ -- documentation (a bit empty for now)
3528 ----------------------------------------------------------------------
3530 Glyph Image Formats:
3532 Drivers are now able to register new glyph image formats within the
3533 library. For now, the base layer supports of course bitmaps and
3534 vector outlines, but one could imagine something different like
3535 colored bitmaps, bi-color vectors or whatever else (Metafonts anyone
3538 See the file `include/ftimage.h'. Note also that the type
3539 FT_Raster_Map is gone, and is now replaced by FT_Bitmap, which
3540 should encompass all known bitmap types.
3542 Each new image format must provide at least one `raster', i.e. a
3543 module capable of transforming the glyph image into a bitmap. It's
3544 also possible to change the default raster used for a given glyph
3547 The default outline scan-converter now uses 128 levels of grays by
3548 default, which tends to smooth many things. Note that the demo
3549 programs have been updated significantly in order to display these..
3552 ----------------------------------------------------------------------
3556 You still need GNU Make to build the library. The build system has
3557 been very seriously re-vamped in order to provide things like :
3559 - automatic host platform detection (reverting to 'config/ansi' if
3560 it is not detected, with pseudo-standard compilation flags)
3562 - the ability to compile from the Makefiles with very different and
3563 exotic compilers. Note that linking the library can be difficult
3566 For example, the file `config/win32/lcclib.bat' is invoked by the
3567 build system to create the `.lib' file with LCC-Win32 because its
3568 librarian has too many flaws to be invoked directly from the
3571 Here's how it works:
3573 - the first time you type `make', the build system runs a series of
3574 sub-makefiles in order to detect your host platform. It then
3575 dumps what it found, and creates a file called `config.mk' in the
3576 current directory. This is a sub-Makefile used to define many
3577 important Make variables used to build the library.
3579 - the second time, the build system detects the `config.mk' then use
3580 it to build the library. All object files go into 'obj' by
3581 default, as well as the library file, but this can easily be
3584 Note that you can run `make setup' to force another host platform
3585 detection even if a `config.mk' is present in the current
3586 directory. Another solution is simply to delete the file, then
3589 Finally, the default compiler for all platforms is gcc (for now,
3590 this will hopefully changed in the future). You can however specify
3591 a different compiler by specifying it after the 'setup' target as
3594 gnumake setup lcc on Win32 to use the LCC compiler
3595 gnumake setup visualc on Win32 to use Visual C++
3597 See the file `config/<system>/detect.mk' for a list of supported
3598 compilers for your platforms.
3600 It should be relatively easy to write new detection rules files and
3603 Finally, to build the demo programs, go to `demos' and launch GNU
3604 Make, it will use the `config.mk' in the top directory to build the
3608 ----------------------------------------------------------------------
3612 In the previous beta, a single FT_System object was used to
3613 encompass all low-level operations like thread synchronisation,
3614 memory management and i/o access. This has been greatly simplified:
3616 - thread synchronisation has been dropped, for the simple reason
3617 that the library is already re-entrant, and that if you really
3618 need two threads accessing the same FT_Library, you should
3619 really synchronize access to it yourself with a simple mutex.
3621 - memory management is performed through a very simple object
3622 called `FT_Memory', which really is a table containing a table
3623 of pointers to functions like malloc, realloc and free as well
3624 as some user data (closure).
3626 - resources have disappeared (they created more problems than they
3627 solved), and i/o management have been simplified greatly as a
3628 result. Streams are defined through FT_Stream objects, which
3629 can be either memory-based or disk-based.
3631 Note that each face has its own stream, which is closed only
3632 when the face object is destroyed. Hence, a function like
3633 TT_Flush_Face in 1.x cannot be directly supported. However, if
3634 you really need something like this, you can easily tailor your
3635 own streams to achieve the same feature at a lower level (and
3636 use FT_Open_Face instead of FT_New_Face to create the face).
3638 See the file `include/ftsystem.h' for more details, as well as the
3639 implementations found in `config/unix' and `config/ansi'.
3642 ----------------------------------------------------------------------
3646 The Font Driver interface has been modified in order to support
3647 extensions & versioning.
3650 The list of the font drivers that are statically linked to the
3651 library at compile time is managed through a new configuration file
3652 called `config/<platform>/ftmodule.h'.
3654 This file is autogenerated when invoking `make modules'. This
3655 target will parse all sub-directories of 'src', looking for a
3656 `module.mk' rules file, used to describe the driver to the build
3659 Hence, one should call `make modules' each time a font driver is
3660 added or removed from the `src' directory.
3662 Finally, this version provides a `pseudo-driver' in `src/sfnt'.
3663 This driver doesn't support font files directly, but provides
3664 services used by all TrueType-like font drivers. Hence, its code is
3665 shared between the TrueType & OpenType font formats, and possibly
3666 more formats to come if we're lucky..
3669 ----------------------------------------------------------------------
3673 The extensions support is inspired by the one found in 1.x.
3675 Now, each font driver has its own `extension registry', which lists
3676 which extensions are available for the font faces managed by the
3679 Extension ids are now strings, rather than 4-byte tags, as this is
3680 usually more readable.
3683 - some data, associated to each face object
3684 - an interface (table of function pointers)
3686 An extension that is format-specific should simply register itself
3687 to the correct font driver. Here is some example code:
3689 // Registering an extensions
3691 FT_Error FT_Init_XXXX_Extension( FT_Library library )
3693 FT_DriverInterface* tt_driver;
3695 driver = FT_Get_Driver( library, "truetype" );
3696 if (!driver) return FT_Err_Unimplemented_Feature;
3698 return FT_Register_Extension( driver, &extension_class );
3702 // Implementing the extensions
3704 FT_Error FT_Proceed_Extension_XXX( FT_Face face )
3706 FT_XXX_Extension ext;
3707 FT_XXX_Extension_Interface ext_interface;
3709 ext = FT_Get_Extension( face, "extensionid", &ext_interface );
3710 if (!ext) return error;
3712 return ext_interface->do_it(ext);
3715 ------------------------------------------------------------------------
3717 Copyright 2000-2012 by
3718 David Turner, Robert Wilhelm, and Werner Lemberg.
3720 This file is part of the FreeType project, and may only be used,
3721 modified, and distributed under the terms of the FreeType project
3722 license, LICENSE.TXT. By continuing to use, modify, or distribute this
3723 file you indicate that you have read the license and understand and
3728 version-control: never
3732 --- end of CHANGES ---
projects / hornmich / skoda-qr-demo.git / blob