| blob | cb662c7062e48e912b2b0c9f4249edf4a6bcdcb5 |
1 CHANGES BETWEEN 2.3.7 and 2.3.6
3 I. IMPORTANT BUG FIXES
5 - If the library was compiled on an i386 platform using gcc, and
6 compiler option -O3 was given, `FT_MulFix' sometimes returned
7 incorrect results which could have caused problems with
8 `FT_Request_Metrics' and `FT_Select_Metrics', returning an
9 incorrect descender size.
11 - Pure CFFs without subfonts were scaled incorrectly if the font
12 matrix was non-standard. This bug has been introduced in
13 version 2.3.6.
15 - The `style_name' field in the `FT_FaceRec' structure often
16 contained a wrong value for Type 1 fonts. This misbehaviour
17 has been introduced in version 2.3.6 while trying to fix
18 another problem. [Note, however, that this value is
19 informative only since the used algorithm to extract it is
20 very simplistic.]
23 II. IMPORTANT CHANGES
25 - Two new macros, FT_OUTLINE_SMART_DROPOUTS and
26 FT_OUTLINE_EXCLUDE_STUBS, have been introduced. Together with
27 FT_OUTLINE_IGNORE_DROPOUTS (which was ignored previously) it is
28 now possible to control the dropout mode of the `raster' module
29 (for B&W rasterization), using the `flags' field in the
30 `FT_Outline' structure.
32 - The TrueType bytecode interpreter now passes the dropout mode to
33 the B&W rasterizer. This greatly increases the output for small
34 ppem values of many fonts like `pala.ttf'.
37 ======================================================================
39 CHANGES BETWEEN 2.3.6 and 2.3.5
41 I. IMPORTANT BUG FIXES
43 - A bunch of potential security problems have been found. All
44 users should update.
46 - Microsoft Unicode cmaps in TrueType fonts are now always
47 preferred over Apple cmaps. This is not a bug per se, but there
48 exist some buggy fonts created for MS which have broken Apple
49 cmaps. This affects only the automatic selection of FreeType;
50 it's always possible to manually select an Apple Unicode cmap if
51 desired.
53 - Many bug fixes to the TrueType bytecode interpreter.
55 - Improved Mac support.
57 - Subsetted CID-keyed CFFs are now supported correctly.
59 - CID-keyed CFFs with subfonts which are scaled in a non-standard
60 way are now handled correctly.
62 - A call to FT_Open_Face with `face_index' < 0 crashed FreeType if
63 the font was a Windows (bitmap) FNT/FON.
66 II. IMPORTANT CHANGES
68 - The new function `FT_Get_CID_Registry_Ordering_Supplement' gives
69 access to those fields in a CID-keyed font. The code has been
70 contributed by Derek Clegg.
72 - George Williams contributed code to validate the new `MATH'
73 OpenType table (within the `otvalid' module). The `ftvalid'
74 demo program has been extended accordingly.
76 - An API for cmap 14 support (for Unicode Variant Selectors, UVS)
77 has been contributed by George Williams.
79 - A new face flag FT_FACE_FLAG_CID_KEYED has been added, together
80 with a macro FT_IS_CID_KEYED which evaluates to 1 if the font is
81 CID-keyed.
84 III. MISCELLANEOUS
86 - Build support for symbian has been contributed.
88 - Better WGL4 glyph name support, contributed by Sergey Tolstov.
90 - Debugging output of the various FT_TRACEX macros is now sent to
91 stderr.
93 - The `ftview' demo program now provides artificial slanting too.
95 - The `ftvalid' demo program has a new option `-f' to select the
96 font index.
99 ======================================================================
101 CHANGES BETWEEN 2.3.5 and 2.3.4
103 I. IMPORTANT BUG FIXES
105 - Some subglyphs in TrueType fonts were handled incorrectly due to
106 a missing graphics state reinitialization.
108 - Large .Z files (as distributed with some X11 packages) weren't
109 handled correctly, making FreeType increase the heap stack in an
110 endless loop.
112 - A large number of bugs have been fixed to avoid crashes and
113 endless loops with invalid fonts.
116 II. IMPORTANT CHANGES
118 - The two new cache functions `FTC_ImageCache_LookupScaler' and
119 `FTC_SBit_Cache_LookupScaler' have been added to allow lookup of
120 glyphs using an `FTC_Scaler' object; this makes it possible to
121 use fractional pixel sizes in the cache. The demo programs have
122 been updated accordingly to use this feature.
124 - A new API `FT_Get_CMap_Format' has been added to get the cmap
125 format of a TrueType font. This is useful in handling PDF
126 files. The code has been contributed by Derek Clegg.
128 - The auto-hinter now produces better output by default for
129 non-Latin scripts like Indic. This was done by using the CJK
130 hinting module as the default instead of the Latin one. Thanks
131 to Rahul Bhalerao for this suggestion.
133 - A new API `FT_Face_CheckTrueTypePatents' has been added to find
134 out whether a given TrueType font uses patented bytecode
135 instructions. The `ft2demos' bundle contains a new program
136 called `ftpatchk' which demonstrates its usage.
138 - A new API `FT_Face_SetUnpatentedHinting' has been added to
139 enable or disable the unpatented hinter.
141 - Support for Windows FON files in PE format has been contributed
142 by Dmitry Timoshkov.
145 III. MISCELLANEOUS
147 - Vincent Richomme contributed Visual C++ project files for Pocket
148 PCs.
151 ======================================================================
153 CHANGES BETWEEN 2.3.4 and 2.3.3
155 I. IMPORTANT BUG FIXES
157 - A serious bug in the handling of bitmap fonts (and bitmap
158 strikes of outline fonts) has been introduced in 2.3.3.
161 ======================================================================
163 CHANGES BETWEEN 2.3.3 and 2.3.2
165 I. IMPORTANT BUG FIXES
167 - Remove a serious regression in the TrueType bytecode interpreter
168 that was introduced in version 2.3.2. Note that this does not
169 disable the improvements introduced to the interpreter in
170 version 2.3.2, only some ill cases that occurred with certain
171 fonts (though a few popular ones).
173 - The auto-hinter now ignores single-point contours for computing
174 blue zones. This bug created `wavy' baselines when rendering
175 text with various fonts that use these contours to model
176 mark-attach points (these are points that are never rasterized
177 and are placed outside of the glyph's real outline).
179 - The `rsb_delta' and `lsb_delta' glyph slot fields are now set to
180 zero for mono-spaced fonts. Otherwise code that uses them would
181 essentially ruin the fixed-advance property.
183 - Fix CVE-2007-1351 which can cause an integer overflow while
184 parsing BDF fonts, leading to a potentially exploitable heap
185 overflow condition.
188 II. MISCELLANEOUS
190 - Fixed compilation issues on some 64-bit platforms (see ChangeLog
191 for details).
193 - A new demo program `ftdiff' has been added to compare TrueType
194 hinting, FreeType's auto hinting, and rendering without hinting
195 in three columns.
198 ======================================================================
200 CHANGES BETWEEN 2.3.2 and 2.3.1
202 I. IMPORTANT BUG FIXES
204 - FreeType returned incorrect kerning information from TrueType
205 fonts when the bytecode interpreter was enabled. This happened
206 due to a typo introduced in version 2.3.0.
208 - Negative kerning values from PFM files are now reported
209 correctly (they were read as 16-bit unsigned values from the
210 file).
212 - Fixed a small memory leak when `FT_Init_FreeType' failed for
213 some reason.
215 - The Postscript hinter placed and sized very thin and ghost stems
216 incorrectly.
218 - The TrueType bytecode interpreter has been fixed to get rid of
219 most of the rare differences seen in comparison to the Windows
220 font loader.
223 II. IMPORTANT CHANGES
225 - The auto-hinter now better deals with serifs and corner cases
226 (e.g., glyph '9' in Arial at 9pt, 96dpi). It also improves
227 spacing adjustments and doesn't change widths for non-spacing
228 glyphs.
230 - Many Mac-specific functions are deprecated (but still
231 available); modern replacements have been provided for them.
232 See the documentation in file `ftmac.h'.
235 ======================================================================
237 CHANGES BETWEEN 2.3.1 and 2.3.0
239 I. IMPORTANT BUG FIXES
241 - The TrueType interpreter sometimes returned incorrect horizontal
242 metrics due to a bug in the handling of the SHZ instruction.
244 - A typo in a security check introduced after version 2.2.1
245 prevented FreeType to render some glyphs in CFF fonts.
248 ======================================================================
250 CHANGES BETWEEN 2.3.0 and 2.2.1
252 I. IMPORTANT BUG FIXES
254 - The PCF font loader is now much more robust while loading
255 malformed font files.
257 - Various memory leaks have been found and fixed.
259 - The TrueType name loader now deals properly with some fonts that
260 encode their names in UTF-16 (the specification was vague, and
261 the code incorrectly assumed UCS-4).
263 - Fixed the TrueType bytecode loader to deal properly with subtle
264 monochrome/gray issues when scaling the CVT. Some fonts
265 exhibited bad rendering artifacts otherwise.
267 - `FT_GlyphSlot_Embolden' now supports vertical layouts correctly
268 (it mangled the vertical advance height).
270 - Fixed byte endian issues of `ftmac.c' to support Mac OS X on
271 i386.
273 - The PFR font loader no longer erroneously tags font files
274 without any outlines as FT_FACE_FLAG_SCALABLE.
277 II. NEW API FUNCTIONS
279 - `FT_Library_SetLcdFilter' allows you to select a special filter
280 to be applied to the bitmaps generated by `FT_Render_Glyph' if
281 one of the FT_RENDER_MODE_LCD and FT_RENDER_MODE_LCD_V modes has
282 been selected. This filter is used to reduce color fringes;
283 several settings are available through the FT_LCD_FILTER_XXX
284 enumeration.
286 Its declaration and documentation can be found in file
287 `include/freetype/ftlcdfil.h' (to be accessed with macro
288 FT_LCD_FILTER_H).
290 *IMPORTANT*: This function returns an error
291 (FT_Err_Unimplemented_Feature) in default builds of the library
292 for patent reasons. See below.
294 - `FT_Get_Gasp' allows you to query the flags of the TrueType
295 `gasp' table for a given character pixel size. This is useful
296 to duplicate the text rendering of MS Windows when the native
297 bytecode interpreter is enabled (which isn't the default for
298 other patent reasons).
300 Its declaration and documentation can be found in file
301 `include/freetype/ftgasp.h' (to be accessed with macro
302 FT_GASP_H).
305 III. IMPORTANT CHANGES
307 - The auto-hinter has been tuned a lot to improve its results with
308 serif fonts, resulting in much better font rendering of many web
309 pages.
311 - The unpatented hinter is now part of the default build of the
312 library; we have added code to automatically support `tricky'
313 fonts that need it.
315 This means that FreeType should `just work' with certain Asian
316 fonts, like MingLiU, which cannot properly be loaded without a
317 bytecode interpreter, but which fortunately do not use any of
318 the patented bytecode opcodes. We detect these fonts by name,
319 so please report any font file that doesn't seem to work with
320 FreeType, and we shall do what we can to support it in a next
321 release.
323 Note that the API hasn't changed, so you can still force
324 unpatented hinting with a special parameter to `FT_Open_Face' as
325 well. This might be useful in same cases; for example, a PDF
326 reader might present a user option to activate it to deal with
327 certain `tricky' embedded fonts which cannot be clearly
328 identified.
330 If you are a developer for embedded systems, you might want to
331 *disable* the feature to save code space by undefining
332 TT_CONFIG_OPTION_UNPATENTED_HINTING in file `ftoption.h'.
334 - LCD-optimized rendering is now *disabled* in all default builds
335 of the library, mainly due to patent issues. For more
336 information see:
338 http://lists.gnu.org/archive/html/freetype/2006-09/msg00064.html
340 A new configuration macro FT_CONFIG_OPTION_SUBPIXEL_RENDERING
341 has been introduced in `ftoption.h'; manually define it in this
342 file if you want to re-enable the feature.
344 The change only affects the implementation, not the FreeType
345 API. This means that clients don't need to be modified, because
346 the library still generates LCD decimated bitmaps, but with the
347 added constraint that R=G=B on each triplet.
349 The displayed result should be equal to normal anti-aliased
350 rendering.
352 Additionally, if FT_CONFIG_OPTION_SUBPIXEL_RENDERING is not
353 defined, the new `FT_Library_SetLcdFilter' function returns the
354 FT_Err_Unimplemented_Feature error code.
356 - Some computation bugs in the TrueType bytecode interpreter were
357 found, which allow us to get rid of very subtle and rare
358 differences we had experienced with the Windows renderer.
360 - It is now possible to cross-compile the library easily. See the
361 file `docs/INSTALL.CROSS' for details.
363 - The file `src/base/ftmac.c' now contains code for Mac OS X only;
364 its deprecated function `FT_GetFile_From_Mac_Font_Name' always
365 returns an error even if the QuickDraw framework is available.
366 The previous version has been moved to `builds/mac/ftmac.c'.
368 Selecting configure option `--with-quickdraw-carbon' makes the
369 build process use the original `ftmac.c' file instead of the Mac
370 OS X-only version.
373 IV. MISCELLANEOUS
375 - Various performance and memory footprint optimizations have been
376 performed on the TrueType and CFF font loaders, sometimes with
377 very drastic benefits (e.g., the TrueType loader is now about
378 25% faster; FreeType should use less heap memory under nearly
379 all conditions).
381 - The anti-aliased rasterizer has been optimized and is now 15% to
382 25% percent faster than in previous versions, depending on
383 content.
385 - The Type 1 loader has been improved; as an example, it now skips
386 top-level dictionaries properly.
388 - Better support for Mac fonts on POSIX systems, plus compilation
389 fixes for Mac OS X on ppc64 where `ftmac.c' cannot be built.
391 - Configuration without `--with-old-mac-fonts' does not include
392 `ftmac.c' (this was the behaviour in FreeType version 2.1.10).
394 - The TrueTypeGX validator (gxvalid) checks the order of glyph IDs
395 in the kern table.
398 ======================================================================
400 CHANGES BETWEEN 2.2.1 and 2.2
402 I. IMPORTANT BUG FIXES
404 - Various integer overflows have been fixed.
406 - PFB fonts with MacOS resource fork weren't handled correctly on
407 non-MacOS platforms.
410 ======================================================================
412 CHANGES BETWEEN 2.2 and 2.1.10
414 (not released officially)
416 I. IMPORTANT BUG FIXES
418 - Vertical metrics for SFNT fonts were incorrect sometimes.
420 - The FT_HAS_KERNING macro always returned 0.
422 - CFF OpenType fonts didn't return correct vertical metrics for
423 glyphs with outlines.
425 - If FreeType was compiled without hinters, all font formats based
426 on PS outlines weren't scaled correctly.
429 II. IMPORTANT CHANGES
431 - Version 2.2 no longer exposes its internals, this is, the header
432 files located in the `include/freetype/internal' directory of
433 the source package are not copied anymore by the `make install'
434 command. Consequently, a number of rogue clients which directly
435 access FreeType's internal functions and structures won't
436 compile without modification.
438 We provide patches for most of those rogue clients. See the
439 following page for more information:
441 http://www.freetype.org/freetype2/patches/rogue-patches.html
443 Note that, as a convenience to our Unix desktop users, version
444 2.2 is *binary* compatible with FreeType 2.1.7, which means that
445 installing this release on an existing distribution shall not
446 break any working desktop.
448 - FreeType's build mechanism has been redesigned. With GNU make
449 it is now sufficient in most cases to edit two files:
450 `modules.cfg', to select the library components, and the
451 configuration file `include/freetype/config/ftoption.h' (which
452 can be copied to the objects directory). Removing unused module
453 directories to prevent its compilation and editing
454 `include/freetype/config/ftmodule.h' is no longer necessary.
456 - The LIGHT hinting algorithm produces more pleasant results.
457 Also, using the FT_LOAD_TARGET_LIGHT flags within FT_Load_Glyph
458 always forces auto-hinting, as a special exception. This allows
459 you to experiment with it even if you have enabled the TrueType
460 bytecode interpreter in your build.
462 - The auto hinter now employs a new algorithm for CJK fonts, based
463 on Akito Hirai's patch. Note that this only works for fonts
464 with a Unicode charmap at the moment.
466 - The following callback function types have changed slightly (by
467 adding the `const' keyword where appropriate):
469 FT_Outline_MoveToFunc
470 FT_Outline_LineToFunc
471 FT_Outline_ConicToFunc
472 FT_Outline_CubicToFunc
473 FT_SpanFunc
474 FT_Raster_RenderFunc
476 FT_Glyph_TransformFunc
477 FT_Renderer_RenderFunc
478 FT_Renderer_TransformFunc
480 Note that this doesn't affect binary backward compatibility.
482 - On MacOS, new APIs have been added as replacements for legacy
483 APIs: `FT_New_Face_From_FSRef' for `FT_New_Face_From_FSSpec',
484 and `FT_GetFile_From_Mac_ATS_Name' for
485 `FT_GetFile_From_Mac_Name'. Legacy APIs are still available, if
486 FreeType is built without disabling them.
488 - A new API `FT_Select_Size' has been added to select a bitmap
489 strike by its index. Code using other functions to select
490 bitmap strikes should be updated to use this function.
492 - A new API `FT_Get_SubGlyph_Info' has been added to retrieve
493 subglyph data. This can be used by rogue clients which used to
494 access the internal headers to get the corresponding data.
496 - In 2.1.10, the behaviour of `FT_Set_Pixel_Sizes' was changed for
497 BDF/PCF fonts, and only for them. This causes inconsistency.
498 In this release, we undo the change. The intent of the change
499 in 2.1.10 is to allow size selection through real dimensions,
500 which can now be done through `FT_Request_Size'.
502 - Some security issues were discovered and fixed in the CFF and
503 Type 1 loader, causing crashes of FreeType by malformed font
504 files.
507 III. MISCELLANEOUS
509 - The documentation for FT_LOAD_TARGET_XXX and FT_RENDER_MODE_XXX
510 values now better reflects its usage and differences: One set is
511 used to specify the hinting algorithm, the other to specify the
512 pixel rendering mode.
514 - `FT_New_Face' and `FT_New_Face_From_FSSpec' in ftmac.c have been
515 changed to count supported scalable faces (sfnt, LWFN) only, and
516 to return the number of available faces via face->num_faces.
517 Unsupported bitmap faces (fbit, NFNT) are ignored.
519 - builds/unix/configure has been improved for MacOS X. It now
520 automatically checks available functions in Carbon library, and
521 prepare to use newest functions by default. Options to specify
522 the dependencies of each Carbon APIs (FSSpec, FSRef, old/new
523 QuickDraw, ATS) are available too. By manual disabling of all
524 QuickDraw functionality, FreeType can be built without
525 `deprecated function' warnings on MacOS 10.4.x, but
526 FT_GetFile_Mac_Name in ftmac.c then is changed to a dummy
527 function, and returns an `unimplemented' error. For details see
528 builds/mac/README.
530 - SFNT cmap handling has been improved, mainly to run much faster
531 with CJK fonts.
533 - A new function `FT_Get_TrueType_Engine_Type (declared in
534 `FT_MODULE_H') is provided to determine the status of the
535 TrueType bytecode interpreter compiled into the library
536 (patented, unpatented, unimplemented).
538 - Vertical metrics of glyphs are synthesized if the font does not
539 provide such information. You can tell whether the metrics are
540 synthesized or not by checking the FT_FACE_FLAG_VERTICAL flag of
541 the face.
543 - The demo programs `ftview' and `ftstring' have been rewritten
544 for better readability. `ftview' has a new switch `-p' to test
545 FT_New_Memory_Face (instead of FT_New_Face).
547 - FreeType now honours bit 1 in the `head' table of TrueType fonts
548 (meaning `left sidebearing point at x=0'). This helps with some
549 buggy fonts.
551 - Rudimentary support for Adobe's new `SING Glyphlet' format. See
553 http://www.adobe.com/products/indesign/sing_gaiji.html
555 for more information.
557 - The `ftdump' program from the `ft2demos' bundle now shows some
558 information about charmaps. It also supports a new switch `-v'
559 to increase verbosity.
561 - Better AFM support. This includes track kerning support.
564 ======================================================================
566 CHANGES BETWEEN 2.1.10 and 2.1.9
568 I. IMPORTANT BUG FIXES
570 - The size comparison for BDF and PCF files could fail sometimes.
572 - Some CFF files were still not loaded correctly. Patch from
573 Derek Noonburg.
575 - The stroker still had some serious bugs.
577 - Boris Letocha fixed a bug in the TrueType interpreter: The
578 NPUSHW instruction wasn't skipped correctly in IF clauses. Some
579 fonts like `Helvetica 75 Bold' failed.
581 - Another serious bug in handling TrueType hints caused many
582 distortions. It has been introduced in version 2.1.8, and it is
583 highly recommended to upgrade.
585 - FreeType didn't properly parse empty Type 1 glyphs.
587 - An unbound dynamic buffer growth was fixed in the PFR loader.
589 - Several bugs have been fixed in the cache sub-system.
591 - FreeType behaved incorrectly when resizing two distinct but very
592 close character pixel sizes through `FT_Set_Char_Size' (Savannah
593 bug #12263).
595 - The auto-hinter didn't work properly for fonts without a Unicode
596 charmap -- it even refused to load the glyphs.
599 II. IMPORTANT CHANGES
601 - Many fixes have been applied to drastically reduce the amount of
602 heap memory used by FreeType, especially when using
603 memory-mapped font files (which is the default on Unix systems
604 which support them).
606 - The auto-hinter has been replaced with a new module, called the
607 `auto-fitter'. It consumes less memory than its predecessor,
608 and it is prepared to support non-latin scripts better in next
609 releases.
611 - George Williams contributed code to read kerning data from PFM
612 files.
614 - FreeType now uses the TT_NAME_ID_PREFERRED_FAMILY and
615 TT_NAME_ID_PREFERRED_SUBFAMILY strings (if available) for
616 setting family and style in SFNT fonts (patch from Kornfeld
617 Eliyahu Peter).
619 - A new API `FT_Sfnt_Table_Info' (in FT_TRUETYPE_TABLES_H) has
620 been added to retrieve name and size information of SFNT tables.
622 - A new API `FT_OpenType_Validate' (in FT_OPENTYPE_VALIDATE_H) has
623 been added to validate OpenType tables (BASE, GDEF, GPOS, GSUB,
624 JSTF). After validation it is no longer necessary to check
625 for errors in those tables while accessing them.
627 Note that this module might be moved to another library in the
628 future to avoid a tight dependency between FreeType and the
629 OpenType specification.
631 - A new API in FT_BITMAP_H (`FT_Bitmap_New', `FT_Bitmap_Convert',
632 `FT_Bitmap_Copy', `FT_Bitmap_Embolden', `FT_Bitmap_Done') has
633 been added. Its use is to convert an FT_Bitmap structure in
634 1bpp, 2bpp, 4bpp, or 8bpp format into another 8bpp FT_Bitmap,
635 probably using a different pitch, and to further manipulate it.
637 - A new API `FT_Outline_Embolden' (in FT_OUTLINE_H) gives finer
638 control how outlines are embolded.
640 - `FT_GlyphSlot_Embolden' (in FT_SYNTHESIS_H) now handles bitmaps
641 also (code contributed by Chia I Wu). Note that this function
642 is still experimental and may be replaced with a better API.
644 - The method how BDF and PCF bitmap fonts are accessed has been
645 refined. Formerly, FT_Set_Pixel_Sizes and FT_Set_Char_Size
646 were synonyms in FreeType's BDF and PCF interface. This has
647 changed now. FT_Set_Pixel_Sizes should be used to select the
648 actual font dimensions (the `strike', which is the sum of the
649 `FONT_ASCENT' and `FONT_DESCENT' properties), while
650 FT_Set_Char_Size selects the `nominal' size (the `PIXELSIZE'
651 property). In both functions, the width parameter is ignored.
654 III. MISCELLANEOUS
656 - The BDF driver no longer converts all returned bitmaps with a
657 depth of 2bpp or 4bpp to a depth of 8bpp. The documentation has
658 not mentioned this explicitly, but implementors might have
659 relied on this after looking into the source files.
661 - A new option `--ftversion' has been added to freetype-config to
662 return the FreeType version.
664 - The memory debugger has been updated to dump allocation
665 statistics on all allocation sources in the library. This is
666 useful to spot greedy allocations when loading and processing
667 fonts.
669 - We removed a huge array of constant pointers to constant strings
670 in the `psnames' module. The problem was that compilations in
671 PIC mode (i.e., when generating a Unix shared object/dll) put
672 the array into the non-shared writable section of the library
673 since absolute pointers are not relocatable by nature.
675 This reduces the memory consumption by approximately 16KByte per
676 process linked to FreeType. We now also store the array in a
677 compressed form (as a trie) which saves about 20KByte of code as
678 well.
680 - Kirill Smelkov provided patches to make src/raster/ftraster.c
681 compile stand-alone again.
684 ======================================================================
686 CHANGES BETWEEN 2.1.9 and 2.1.8
688 I. IMPORTANT BUG FIXES
690 - The function `FT_Get_CharMap_Index' was only declared, without
691 any real code. For consistency, it has been renamed to
692 `FT_Get_Charmap_Index'. (This function is needed to implement
693 cmap caches.)
695 - `FT_Outline_Get_BBox' sometimes returned incorrect values for
696 conic outlines (e.g., for TrueType fonts).
698 - Handling of `bhed' table has been fixed.
700 - The TrueType driver with enabled byte code interpreter sometimes
701 returned artifacts due to incorrect rounding. This bug has been
702 introduced after version 2.1.4.
704 - The BDF driver dropped the last glyph in the font.
706 - The BDF driver now uses the DEFAULT_CHAR property (if available)
707 to select a glyph shape for the undefined glyph.
709 - The stroker failed for closed outlines and single points.
712 II. IMPORTANT CHANGES
714 - George Williams contributed code to handle Apple's font
715 distortion technology found in GX fonts (`avar', `cvar', `fvar',
716 and `gvar' tables; the Multiple Masters API has been slightly
717 extended to cope with the new functionality).
719 - The `FT_GlyphSlotRec' structure has been extended: The elements
720 `lsb_delta' and `rsb_delta' give the difference between hinted
721 and unhinted left and right side bearings if autohinting is
722 active. Using those values can improve the inter-letter spacing
723 considerably. See the documentation of `FT_GlyphSlotRec' and
724 the `ftstring' demo program how to use it.
726 - Loading TrueType and Type 1 fonts has been made much faster.
728 - The stroker is no longer experimental (but the cache subsystem
729 still is).
732 III. MISCELLANEOUS
734 - A new documentation file `formats.txt' describes various font
735 formats supported (and not supported) by FreeType.
738 ======================================================================
740 CHANGES BETWEEN 2.1.8 and 2.1.7
742 I. IMPORTANT BUG FIXES
744 - The native TrueType hinter contained some bugs which prevented
745 some fonts to be rendered correctly, most notably Legendum.otf.
747 - The PostScript hinter now produces improved results.
749 - The linear advance width and height values were incorrectly
750 rounded, making them virtually unusable if not loaded with
751 FT_LOAD_LINEAR_DESIGN.
753 - Indexing CID-keyed CFF fonts is now working: The glyph index is
754 correctly treated as a CID, similar to FreeType's CID driver
755 module. Note that CID CMap support is still missing.
757 - The FT_FACE_FLAGS_GLYPH_NAMES flag is now set correctly for all
758 font formats.
760 - Some subsetted Type 1 fonts weren't parsed correctly. This bug
761 has been introduced in 2.1.7. In summary, the Type 1 parser has
762 become more robust.
764 - Non-decimal numbers weren't parsed correctly in PS fonts.
766 - The WinFNT driver now correctly reports FT_ENCODING_NONE for all
767 but one encoding. Use the new FT_WinFNT_ID_XXX values together
768 with `FT_Get_WinFNT_Header' to get the WinFNT charset ID.
770 - The descender metrics (face->size->metrics.descender) for WinFNT
771 bitmap fonts had the wrong sign.
773 - The (emulated) `seac' support for CFF fonts was broken.
775 - The `flex' operator didn't work for CFF fonts.
777 - PS glyphs which use the `hintmask' operator haven't been
778 rendered correctly in some cases.
780 - Metrics for BDF and PCF bitmap font formats have been fixed.
782 - Autohinting is now disabled for glyphs which are vertically
783 distorted or mirrored (using a transformation matrix). This
784 fixes a bug which produced zero-height glyphs.
786 - The `freetype-config' script now handles --prefix and
787 --exec-prefix correctly; it also returns the proper --rpath (or
788 -R) value if FreeType has been built as a shared library.
791 II. IMPORTANT CHANGES
793 - Both PCF and BDF drivers now handle the SETWIDTH_NAME and
794 ADD_STYLE_NAME properties. Values are appended to
795 face->style_name; example: `Bold SemiCondensed'.
797 - The PCF driver now handles bitmap fonts compressed with the LZW
798 algorithm (extension .pcf.Z, compressed with `compress').
800 - A new API function `FT_Get_CMap_Language_ID' (declared in
801 `tttables.h') is available to get the language ID of a
802 TrueType/SFNT cmap.
804 - The hexadecimal format of data after the `StartData' command in
805 CID-keyed Type 1 fonts is now supported. While this can't occur
806 in file-based fonts, it can happen in document-embedded
807 resources of PostScript documents.
809 - Embedded bitmaps in SFNT-based CFF fonts are now supported.
811 - A simple API is now available to control FreeType's tracing
812 mechanism if compiled with FT_DEBUG_LEVEL_TRACE. See the file
813 `ftdebug.h' for more details.
815 - YAMATO Masatake contributed improved handling of MacOS resource
816 forks on non-MacOS platforms (for example, Linux can mount MacOS
817 file systems).
819 - Support for MacOS has been improved; there is now a new function
820 `FT_New_Face_From_FSSpec' similar to `FT_New_Face' except that
821 it accepts an FSSpec instead of a path.
823 - The cache sub-system has been rewritten.
825 - There is now support for deinstallation of faces.
827 - A new API function `FTC_Manager_RemoveFaceID' has been added
828 to delete all `idle' nodes that correspond to a given
829 FTC_FaceID. All `locked' nodes (i.e., those with a reference
830 count > 0), will be modified to prevent them from appearing in
831 further lookups (they will be cleaned normally when their
832 reference count reaches 0).
834 - There is now support for point scaling (i.e., providing
835 character sizes in points + dpis, instead of pixels).
837 - Three abstract cache classes are now available:
839 FTC_GCache: Used to store one glyph item per cache node,
840 with the ability to group common attributes into
841 `families'. This replaces the old
842 FTC_GlyphCache class.
844 FTC_ICache: Used to store one FT_Glyph per cache node. This
845 extends FTC_GCache. Family definition, family
846 comparison, and glyph loading are however left
847 to sub-classes.
849 FTC_SCache: Used to store up to 16 small bitmaps per cache
850 node. This extends FTC_GCache. Family
851 definition, family comparison and glyph loading
852 are however left to sub-classes.
854 - The file `src/cache/ftcbasic.c' implements:
856 FTC_ImageCache: Extends FTC_ICache; implements family
857 definitions and glyph loading similar to the
858 old API.
860 FTC_SBitCache: Extends FTC_SCache, implements family
861 definitions and glyph loading similar to the
862 old API
864 Client applications should be able to extend FTC_GCache,
865 FTC_ICache, or FTC_SCache much more easily (i.e., less code to
866 write, and less callbacks). For example, one could envision
867 caches that are capable of storing transformed (obliqued),
868 stroked, emboldened, or colored glyph images. Use
869 `ftcbasic.c' as an example.
871 - All public APIs are now in `include/freetype/ftcache.h', (to
872 be accessed as `FT_CACHE_H'). The contents of
873 `include/freetype/cache/' is only needed by applications that
874 wish to implement their own caches.
876 - There were some major performance improvements through the use
877 of various programming tricks. Cache hits are up to 70%
878 faster than in the old code.
880 - The FTC_CMapCache has been simplified. Charmaps can only be
881 accessed by index right now. There is also a new API named
882 `FT_Charmap_GetIndex' for this purpose.
884 - The demo programs have been updated to the new code. The
885 previous versions will not work with the current one.
887 - Using an invalid face index in FT_Open_Face and friends now
888 causes an error even if the font contains a single face only.
891 III. MISCELLANEOUS
893 - Wolfgang Domröse contributed support files for building FreeType
894 on the Atari using the PureC compiler. Note that the Atari is a
895 16bit platform.
897 - Vitaliy Pasternak contributed project files for VS.NET 2003.
900 ======================================================================
902 CHANGES BETWEEN 2.1.7 and 2.1.6
904 I. IMPORTANT BUG FIXES
906 - Updated to newest libtool version, fixing build problems on
907 various platforms.
909 - On Unix platforms, `make install' didn't copy the correct
910 `ftconfig.h' file.
912 Note that version 2.1.7 contains the same library C source code as
913 version 2.1.6.
916 ======================================================================
918 CHANGES BETWEEN 2.1.6 and 2.1.5
920 I. IMPORTANT BUG FIXES
922 - The PFR font driver didn't load kerning tables correctly, and
923 the functions in FT_PFR_H didn't work at all.
925 - Type 1 font files in binary format (PFB) with an end-of-file
926 indicator weren't accepted by the FreeType engine.
928 - Fonts which contain /PaintType and /StrokeWidth no longer cause
929 a segfault. This bug has been introduced in version 2.1.5.
931 - Fonts loaded with FT_LOAD_RENDER no longer cause strange
932 results. This bug has been introduced in version 2.1.5.
934 - Some Windows (bitmap) FNT/FON files couldn't be handled
935 correctly.
938 II. IMPORTANT CHANGES
940 - The internal module API has been heavily changed in favor of
941 massive simplifications within the font engine. This also means
942 that authors of third-party modules must adapt their code to the
943 new scheme.
945 NOTE: THE NEW SCHEME IS NOT COMPLETED YET. PLEASE WAIT UNTIL A
946 FINAL ANNOUNCEMENT!
948 - The PostScript parser has been enhanced to handle comments and
949 strings correctly. Additionally, more syntax forms are
950 recognized.
952 - Added the optional unpatented hinting system for TrueType. It
953 allows typefaces which need hinting to produce correct glyph
954 forms (e.g., Chinese typefaces from Dynalab) to work acceptably
955 without infringing Apple patents. This system is compiled only
956 if TT_CONFIG_OPTION_COMPILE_UNPATENTED_HINTING is defined in
957 ftoption.h (activated by default).
960 III. MISCELLANEOUS
962 - There is now a guard in the public header files to protect
963 against inclusion of freetype.h from FreeType 1.
965 - Direct inclusion of freetype.h and other public header files no
966 longer works. You have to use the documented scheme
968 #include <ft2build.h>
969 #include FT_FREETYPE_H
971 to load freetype.h with a symbolic name. This protects against
972 renaming of public header files (which shouldn't happen but
973 actually has, avoiding two public header files with the same
974 name).
977 ======================================================================
979 CHANGES BETWEEN 2.1.5 and 2.1.4
981 I. IMPORTANT BUG FIXES
983 - Parsing the /CIDFontName field now removes the leading slash to
984 be in sync with other font drivers.
986 - gzip support was buggy. Some fonts could not be read.
988 - Fonts which have nested subglyphs more than one level deep no
989 longer cause a segfault.
991 - Creation of synthetic cmaps for fonts in CFF format was broken
992 partially.
994 - Numeric font dictionary entries for synthetic fonts are no
995 longer overwritten.
997 - The font matrix wasn't applied to the advance width for Type1,
998 CID, and CFF fonts. This caused problems when loading certain
999 synthetic Type 1 fonts like `Helvetica Narrow'.
1001 - The test for the charset registry in BDF and PCF fonts is now
1002 case-insensitive.
1004 - FT_Vector_Rotate sometimes returned strange values due to
1005 rounding errors.
1007 - The PCF driver now returns the correct number of glyphs
1008 (including an artificial `notdef' glyph at index 0).
1010 - FreeType now supports buggy CMaps which are contained in many
1011 CJK fonts from Dynalab.
1013 - Opening an invalid font on a Mac caused a segfault due to
1014 double-freeing memory.
1016 - BDF fonts with more than 32768 glyphs weren't supported
1017 properly.
1020 II. IMPORTANT CHANGES
1022 - Accessing bitmap font formats has been synchronized. To do that
1023 the FT_Bitmap_Size structure has been extended to contain new
1024 fields `size', `x_ppem', and `y_ppem'.
1026 - The FNT driver now returns multiple faces, not multiple strikes.
1028 - The `psnames' module has been updated to the Adobe Glyph List
1029 version 2.0.
1031 - The `psnames' module now understands `uXXXX[X[X]]' glyph names.
1033 - The algorithm for guessing the font style has been improved.
1035 - For fonts in SFNT format, root->height is no longer increased if
1036 the line gap is zero. There exist fonts (containing e.g. form
1037 drawing characters) which intentionally have a zero line gap
1038 value.
1040 - ft_glyph_bbox_xxx flags are now deprecated in favour of
1041 FT_GLYPH_BBOX_XXX.
1043 - ft_module_xxx flags are now deprecated in favour of
1044 FT_MODULE_XXX.
1046 - FT_ENCODING_MS_{SJIS,GB2312,BIG5,WANSUNG,JOHAB} are now
1047 deprecated in favour of
1048 FT_ENCODING_{SJIS,GB2312,GIB5,WANSONG,JOHAB} -- those encodings
1049 are not specific to Microsoft.
1052 III. MISCELLANEOUS
1054 - The autohinter has been further improved; for example, `m'
1055 glyphs now retain its vertical symmetry.
1057 - Partial support of Mac fonts on non-Mac platforms.
1059 - `make refdoc' (after first `make') builds the HTML
1060 documentation. You need Python for this.
1062 - The make build system should now work more reliably on DOS-like
1063 platforms.
1065 - Support for EMX gcc and Watson C/C++ compilers on MS-DOS has
1066 been added.
1068 - Better VMS build support.
1070 - Support for the pkg-config package by providing a `freetype.pc'
1071 file.
1073 - New configure option --with-old-mac-fonts for Darwin.
1075 - Some source files have been renamed (mainly to fit into the 8.3
1076 naming scheme).
1079 ======================================================================
1081 CHANGES BETWEEN 2.1.4 and 2.1.3
1083 I. IMPORTANT BUG FIXES
1085 - Updated to newest libtool version, fixing build problems on
1086 various platforms.
1088 - A fix in the Gzip stream reader: It couldn't read certain .gz
1089 files properly due to a small typo. In certain cases, FreeType
1090 could also loop endlessly when trying to load tiny gzipped
1091 files.
1093 - The configure script now tries to use the system-wide zlib when
1094 it finds one (instead of the copy found in src/gzip). And
1095 `freetype-config' has been updated to return relevant flags in
1096 this case when invoked with `--libs' (e.g. `-lzlib').
1098 - Certain fonts couldn't be loaded by 2.1.3 because they lacked a
1099 Unicode charmap (e.g. SYMBOL.TTF). FreeType erroneously
1100 rejected them.
1102 - The CFF loader was modified to accept fonts which only contain a
1103 subset of their reference charset. This prevented the correct
1104 use of PDF-embedded fonts.
1106 - The logic to detect Unicode charmaps has been modified. This is
1107 required to support fonts which include both 16-bit and 32-bit
1108 charmaps (like very recent asian ones) using the new 10 and 12
1109 SFNT formats.
1111 - The TrueType loader now limits the depth of composite glyphs.
1112 This is necessary to prevent broken fonts to break the engine by
1113 blowing the stack with recursive glyph definitions.
1115 - The CMap cache is now capable of managing UCS-4 character codes
1116 that are mapped through extended charmaps in recent
1117 TrueType/OpenType fonts.
1119 - The cache sub-system now properly manages out-of-memory
1120 conditions instead of blindly reporting them to the caller.
1121 This means that it will try to empty the cache before restarting
1122 its allocations to see if that can help.
1124 - The PFR driver didn't return the list of available embedded
1125 bitmaps properly.
1127 - There was a nasty memory leak when using embedded bitmaps in
1128 certain font formats.
1131 II. IMPORTANT CHANGES
1133 - David Chester contributed some enhancements to the auto-hinter
1134 that significantly increase the quality of its output. The
1135 Postscript hinter was also improved in several ways.
1137 - The FT_RENDER_MODE_LIGHT render mode was implemented.
1139 - A new API function called `FT_Get_BDF_Property' has been added
1140 to FT_BDF_H to retrieve BDF properties from BDF _and_ PCF font
1141 files. THIS IS STILL EXPERIMENTAL, since it hasn't been
1142 properly tested yet.
1144 - A Windows FNT specific API has been added, mostly to access font
1145 headers. This is used by Wine.
1147 - TrueType tables without an `hmtx' table are now tolerated when
1148 an incremental interface is used. This happens for certain
1149 Type42 fonts passed from Ghostscript to FreeType.
1151 - The PFR font driver is now capable of returning the font family
1152 and style names when they are available (instead of the sole
1153 `FontID'). This is performed by parsing an *undocumented*
1154 portion of the font file!
1157 III. MISCELLANEOUS
1159 - The path stroker in FT_STROKER_H has entered beta stage. It now
1160 works very well, but its interface might change a bit in the
1161 future. More on this in later releases.
1163 - The documentation for FT_Size_Metrics didn't appear properly in
1164 the API reference.
1166 - The file docs/VERSION.DLL has been updated to explain versioning
1167 with FreeType (i.e., comparing release/libtool/so numbers, and
1168 how to use them in autoconf scripts).
1170 - The installation documentation has been seriously revamped.
1171 Everything is now in the `docs' directory.
1174 ======================================================================
1176 CHANGES BETWEEN 2.1.3 and 2.1.2
1178 I. IMPORTANT BUG FIXES
1180 - FT_Vector_Transform had been incorrectly modified in 2.1.2,
1181 resulting in incorrect transformations being applied (for
1182 example, rotations were processed in opposite angles).
1184 - The format 8 and 12 TrueType charmap enumeration routines have
1185 been fixed (FT_Get_Next_Char returned invalid values).
1187 - The PFR font driver returned incorrect advance widths if the
1188 outline and metrics resolution defined in the font file were
1189 different.
1191 - FT_Glyph_To_Bitmap now returns successfully when called with an
1192 FT_BitmapGlyph argument (it previously returned an error).
1194 - A bug in the Type 1 loader that prevented valid font bounding
1195 boxes to be loaded from multiple master fonts.
1197 - The SFNT validation code has been rewritten. FreeType can now
1198 load `broken' fonts that were usable on Windows, but not with
1199 previous versions of the library.
1201 - The computation of bearings in the BDF driver has been fixed.
1203 - The Postscript hinter crashed when trying to hint certain glyphs
1204 (more precisely, when trying to apply hints to an empty glyph
1205 outline).
1207 - The TrueType glyph loader now supports composites in `Apple
1208 format' (they differ slightly from Microsoft/OpenType ones in
1209 the way transformation offsets are computed).
1211 - FreeType was very slow at opening certain asian CID/CFF fonts,
1212 due to fixed increment in dynamic array re-allocations. This
1213 has been changed to exponential behaviour to get acceptable
1214 performance.
1218 II. IMPORTANT CHANGES
1220 - The PCF driver now supports gzip-compressed font files natively.
1221 This means that you will be able to use all these bitmap fonts
1222 that come with XFree86 with FreeType (and libXft/libXft2, by
1223 extension).
1225 - The automatic and postscript hinters have both been updated.
1226 This results in a relatively important increase of rendering
1227 quality since many nasty defaults have been suppressed. Please
1228 visit the web page:
1230 http://www.freetype.org/hinting/smooth-hinting.html
1232 for additional details on this topic.
1234 - The `load_flags' parameter of `FT_Load_Glyph' is now an FT_Int32
1235 (instead of just being an FT_Int). This breaks source and
1236 binary compatibility for 16bit systems only, while retaining
1237 both of them for 32 and 64 bit ones.
1239 Some new flags have been added consequently:
1241 FT_LOAD_NO_AUTOHINT :: Disable the use of the auto-hinter
1242 (but not native format hinters).
1244 FT_LOAD_TARGET_NORMAL :: Hint and render for normal
1245 anti-aliased displays.
1247 FT_LOAD_TARGET_MONO :: Hint and render for 1-bit displays.
1249 FT_LOAD_TARGET_LCD :: Hint and render for horizontal RGB or
1250 BGR sub-pixel displays (like LCD
1251 screens). THIS IS STILL
1252 EXPERIMENTAL!
1254 FT_LOAD_TARGET_LCD_V :: Same as FT_LOAD_TARGET_LCD, for
1255 vertical sub-pixel displays (like
1256 rotated LCD screens). THIS IS STILL
1257 EXPERIMENTAL!
1259 FT_LOAD_MONOCHROME is still supported, but only affects
1260 rendering, not the hinting.
1262 Note that the `ftview' demo program available in the `ft2demos'
1263 package has been updated to support LCD-optimized display on
1264 non-paletted displays (under Win32 and X11).
1266 - The PFR driver now supports embedded bitmaps (all formats
1267 supported), and returns correct kerning metrics for all glyphs.
1269 - The TrueType charmap loader now supports certain `broken' fonts
1270 that load under Windows without problems.
1272 - The cache API has been slightly modified (it's still a beta!):
1274 - The type FTC_ImageDesc has been removed; it is now replaced
1275 by FTC_ImageTypeRec. Note that one of its fields is a
1276 `load_flag' parameter for FT_Load_Glyph.
1278 - The field `num_grays' of FT_SBitRec has been changed to
1279 `max_grays' in order to fit within a single byte. Its
1280 maximum value is thus 255 (instead of 256 as previously).
1283 III. MISCELLANEOUS
1285 - Added support for the DESTDIR variable during `make install'.
1286 This simplifies packaging of FreeType.
1288 - Included modified copies of the ZLib sources in `src/gzip' in
1289 order to support gzip-compressed PCF fonts. We do not use the
1290 system-provided zlib for now, though this is a probable
1291 enhancement for future releases.
1293 - The DocMaker tool used to generate the on-line API reference has
1294 been completely rewritten. It is now located in
1295 `src/tools/docmaker/docmaker.py'. Features:
1297 - better cross-referenced output
1298 - more polished output
1299 - uses Python regular expressions (though it didn't speed the
1300 program)
1301 - much more modular structure, which allows for different
1302 `backends' in order to generate HTML, XML, or whatever
1303 format.
1305 One can regenerate the API reference by calling:
1307 python src/tools/docmaker/docmaker.py \
1308 --prefix=ft2 \
1309 --title=FreeType-2.1.3 \
1310 --output=<outputdirectory>
1311 include/freetype/*.h \
1312 include/freetype/config/*.h \
1313 include/freetype/cache/*.h
1315 - A new, experimental, support for incremental font loading (i.e.,
1316 loading of fonts where the glyphs are not in the font file
1317 itself, but provided by an external component, like a Postscript
1318 interpreter) has been added by Graham Asher. This is still work
1319 in progress, however.
1321 - A new, EXPERIMENTAL, path stroker has been added. It doesn't
1322 suffer from severe rounding errors and treat bezier arcs
1323 directly. Still work in progress (i.e. not part of the official
1324 API). See the file <freetype/ftstroker.h> for some of the
1325 details.
1327 - The massive re-formatting of sources and internal re-design is
1328 still under-way. Many internal functions, constants, and types
1329 have been renamed.
1332 ======================================================================
1334 CHANGES BETWEEN 2.1.2 and 2.1.1
1336 I. IMPORTANT BUG FIXES
1338 - Many font drivers didn't select a Unicode charmap by default
1339 when a new face was opened (with the FT_CONFIG_OPTION_USE_CMAPS
1340 options enabled), causing many applications to not be able to
1341 display text correctly with the 2.1.x releases.
1343 - The PFR driver had a bug in its composite loading code that
1344 produces incorrectly placed accents with many fonts.
1346 - The Type42 driver crashed sometimes due to a nasty bug.
1348 - The Type 1 custom encoding charmap didn't handle the case where
1349 the first glyph index wasn't 0.
1351 - A serious typo in the TrueType composite loader produced
1352 incorrectly placed glyphs in fonts like `Wingdings' and a few
1353 others.
1356 II. MISCELLANEOUS
1358 - The Win32 Visual C++ project file has been updated to include
1359 the PFR driver as well.
1361 - `freetype.m4' is now installed by default by `make install' on
1362 Unix systems.
1364 - The function FT_Get_PS_Font_Info now works with CID and Type42
1365 fonts as well.
1368 ======================================================================
1370 CHANGES BETWEEN 2.1.1 and 2.1.0
1372 I. IMPORTANT BUG FIXES
1374 - The `version_info' returned by `freetype-config' in 2.1.0
1375 returned an invalid value. It now returns 9:1:3 (2.0.9 returned
1376 9:0:3).
1378 - Version 2.1.0 couldn't be linked against applications on Win32
1379 and Amiga systems due to a new debug function that wasn't
1380 properly propagated to the system-specific directory in
1381 `builds'.
1383 - Various MacOS and Mac OS X specific fixes.
1385 - Fixed a bug in the TrueType charmap validation routines that
1386 made version 2.1.0 too restrictive -- many popular fonts have
1387 been rejected.
1389 - There was still a very small difference between the monochrome
1390 glyph bitmaps produced by FreeType 1.x and FreeType 2.x with the
1391 bytecode interpreter enabled. This was caused by an invalid
1392 flag setting in the TrueType glyph loader, making the rasterizer
1393 change its drop-out control mode. Now the results should
1394 _really_ be completely identical.
1396 - The TrueType name table loader has been improved to support many
1397 popular though buggy Asian fonts. It now ignores empty name
1398 entries, invalid pointer offsets and a few other incorrect
1399 subtleties. Moreover, name strings are now loaded on demand,
1400 which reduces the memory load of many faces (e.g. the ARIAL.TTF
1401 font file contains a 10kByte name table with 70 names).
1403 - Fixed a bug in the Postscript hinter that prevented family blues
1404 substitution to happen correctly.
1407 II. NEW FEATURES
1409 - Three new font drivers in this release:
1411 * A BDF font driver, contributed by Franco Zappa Nardelli,
1412 heavily modified by Werner Lemberg. It also supports
1413 anti-aliased bitmaps (using a slightly extended BDF format).
1415 * A Type42 font driver, contributed by Roberto Alameda. It is
1416 still experimental but seems to work relatively well.
1418 * A PFR font driver, contributed by David Turner himself. It
1419 doesn't support PFR hinting -- note that BitStream has at
1420 least two patents on this format!
1423 III. MISCELLANEOUS
1425 - The cache sub-system has been optimized in important ways.
1426 Cache hits are now significantly faster. For example, using the
1427 CMap cache is about twice faster than calling FT_Get_Char_Index
1428 on most platforms. Similarly, using an SBit cache is about five
1429 times faster than loading the bitmaps from a bitmap file, and
1430 300 to 500 times faster than generating them from a scalable
1431 format.
1433 Note that you should recompile your sources if you designed a
1434 custom cache class for the FT2 Cache subsystem, since the
1435 changes performed are source, but not binary, compatible.
1438 ======================================================================
1440 CHANGES BETWEEN 2.1.0 and 2.0.9
1442 I. IMPORTANT BUG FIXES
1444 - The TrueType bytecode interpreter has been fixed to produce
1445 _exactly_ the same output as FreeType 1.x. Previous differences
1446 were due to slightly distinct fixed-point computation routines
1447 used to perform dot products and vector length measurements.
1449 It seems that native TrueType hinting is _extremely_ sensitive
1450 to rounding errors. The required vector computation routines
1451 have been optimized and placed within the `ttinterp.c' file.
1453 - Fixed the parsing of accelerator tables in the PCF font driver.
1455 - Fixed the Type1 glyph loader routine used to compute the font's
1456 maximum advance width.
1459 II. NEW FEATURES
1461 - The `configure' script used on Unix systems has been modified to
1462 check that GNU Make is being used to build the library.
1463 Otherwise, it will display a message proposing to use the
1464 GNUMAKE environment variable to name it.
1466 The Unix-specific file README.UNX has been modified accordingly.
1469 III. MISCELLANEOUS
1471 - The FreeType License in `docs/FTL.TXT' has been updated to
1472 include a proposed preferred disclaimer. If you are using
1473 FreeType in your products, you are encouraged (but not mandated)
1474 to use the following text in your documentation:
1476 """
1477 Portions of this software are copyright © 1996-2002 The
1478 FreeType Project (www.freetype.org). All rights reserved.
1479 """
1481 - The default size of the render pool has been reduced to 16kByte.
1482 This shouldn't result in any noticeable performance penalty,
1483 unless you are using the engine as-is to render very large and
1484 complex glyphs.
1486 - The FreeType 2 redesign has begun. More information can be
1487 found at this URL:
1489 http://www.freetype.org/freetype2/redesign.html
1491 The following internal changes have been performed within the
1492 sources of this release:
1494 - Many internal types have been renamed to increase
1495 consistency. The following should be true, except for
1496 public types:
1498 * All structure types have a name ending in `Rec' (short
1499 for `record').
1501 * A pointer-to-structure type has the same name as the
1502 structure, _without_ the `Rec' suffix.
1504 Example:
1506 typedef struct FooRec_
1507 {
1508 ...
1510 } FooRec, *Foo;
1512 - Many internal macros have been renamed to increase
1513 consistency. The following should be true:
1515 * All macros have a name beginning with `FT_'. This
1516 required a few changes like
1518 ALLOC => FT_ALLOC
1519 FREE => FT_FREE
1520 REALLOC => FT_REALLOC
1522 * All macros are completely UPPERCASE. This required a
1523 few changes like:
1525 READ_Short => FT_READ_SHORT
1526 NEXT_Short => FT_NEXT_SHORT
1527 GET_ULongLE => FT_GET_ULONG_LE
1528 MEM_Set => FT_MEM_SET
1529 MEM_Copy => FT_MEM_COPY
1530 etc.
1532 * Whenever possible, all macro names follow the
1533 FT_<OBJECT>_<METHOD> pattern. For example
1535 ACCESS_Frame => FT_FRAME_ENTER
1536 FORGET_Frame => FT_FRAME_EXIT
1537 EXTRACT_Frame => FT_FRAME_EXTRACT
1538 RELEASE_Frame => FT_FRAME_RELEASE
1540 FILE_Pos => FT_STREAM_POS
1541 FILE_Seek => FT_STREAM_SEEK
1542 FILE_Read => FT_STREAM_READ
1543 FILE_ReadAt => FT_STREAM_READ_AT
1544 READ_Fields => FT_STREAM_READ_FIELDS
1546 - Many internal functions have been renamed to follow the
1547 FT_<Object>_<Method> pattern. For example:
1549 FT_Seek_Stream => FT_Stream_Seek
1550 FT_Read_Stream_At => FT_Stream_ReadAt
1551 FT_Done_Stream => FT_Stream_Close
1552 FT_New_Stream => FT_Stream_Open
1553 FT_New_Memory_Stream => FT_Stream_OpenMemory
1554 FT_Extract_Frame => FT_Stream_ExtractFrame
1556 Note that method names do not contain `_'.
1558 - The FT_ALLOC_ARRAY and FT_REALLOC_ARRAY have been replaced
1559 with FT_NEW_ARRAY and FT_RENEW_ARRAY which do not take a
1560 type as the fourth argument. Instead, the array element
1561 type size is computed automatically from the type of the
1562 target pointer used.
1564 - A new object class, FT_CMap, has been introduced. These
1565 internal objects are used to model character maps. This
1566 eases the support of additional charmap types within the
1567 engine.
1569 - A new configuration file named `ftstdlib.h' has been added
1570 to `include/freetype/config'. It is used to define aliases
1571 for _every_ routine of the ISO C library that the font
1572 engine uses. Each aliases has a `ft_' prefix
1573 (e.g. `ft_strlen' is an alias for `strlen').
1575 This is used to ease the porting of FreeType 2 to exotic
1576 runtime environments where the ISO C Library isn't available
1577 (e.g. XFree86 extension modules).
1579 More details are available in the `ChangeLog' file.
1582 ======================================================================
1584 CHANGES BETWEEN 2.0.9 and 2.0.8
1586 I. IMPORTANT BUG FIXES
1588 - Certain fonts like `foxjump.ttf' contain broken name tables with
1589 invalid entries and wild offsets. This caused FreeType to crash
1590 when trying to load them.
1592 The SFNT `name' table loader has been fixed to be able to
1593 support these strange fonts.
1595 Moreover, the code in charge of processing this table has been
1596 changed to always favour Windows-formatted entries over other
1597 ones. Hence, a font that works on Windows but not on the Mac
1598 will load cleanly in FreeType and report accurate values for
1599 Family & PostScript names.
1601 - The CID font driver has been fixed. It unfortunately returned a
1602 Postscript Font name with a leading slash, as in
1603 `/MunhwaGothic-Regular'.
1605 - FreeType 2 should now compile fine on AIX 4.3.3 as a shared
1606 library.
1608 - A bug in the Postscript hinter has been found and fixed,
1609 removing un-even stem widths at small pixel sizes (like 14-17).
1611 This improves the quality of a certain number of Postscript
1612 fonts.
1615 II. NEW FEATURES
1617 - A new function named `FT_Library_Version' has been added to
1618 return the current library's major, minor, and patch version
1619 numbers. This is important since the macros FREETYPE_MAJOR,
1620 FREETYPE_MINOR, and FREETYPE_PATCH cannot be used when the
1621 library is dynamically linked by a program.
1623 - Two new APIs have been added: `FT_Get_First_Char' and
1624 `FT_Get_Next_Char'.
1626 Together, these can be used to iterate efficiently over the
1627 currently selected charmap of a given face. Read the API
1628 reference for more details.
1631 III. MISCELLANEOUS
1633 - The FreeType sources are under heavy internal re-factoring. As
1634 a consequence, we have created a branch named `STABLE' on the
1635 CVS to hold all future releases/fixes in the 2.0.x family.
1637 The HEAD branch now contains the re-factored sources and
1638 shouldn't be used for testing or packaging new releases. In
1639 case you would like to access the 2.0.9 sources from our CVS
1640 repository, use the tag `VER-2-0-9'.
1643 ======================================================================
1645 CHANGES BETWEEN 2.0.8 and 2.0.7
1647 I. IMPORTANT BUG FIXES
1649 - There was a small but nasty bug in `freetype-config.in' which
1650 caused the `freetype-config' script to fail on Unix.
1652 This didn't prevent the installation of the library or even its
1653 execution, but caused problems when trying to compile many Unix
1654 packages that depend on it.
1656 - Some TrueType or OpenType fonts embedded in PDF documents do not
1657 have a 'cmap', 'post' and 'name' as is required by the
1658 specification. FreeType no longer refuses to load such fonts.
1660 - Various fixes to the PCF font driver.
1663 ======================================================================
1665 CHANGES BETWEEN 2.0.7 and 2.0.6
1667 I. IMPORTANT BUG FIXES
1669 - Fixed two bugs in the Type 1 font driver. The first one
1670 resulted in a memory leak in subtle cases. The other one caused
1671 FreeType to crash when trying to load `.gsf' files (Ghostscript
1672 so-called Postscript fonts).
1674 (This made _many_ KDE applications crash on certain systems.
1675 FreeType _is_ becoming a critical system component on Linux :-)
1677 - Fixed a memory leak in the CFF font driver.
1679 - Fixed a memory leak in the PCF font driver.
1681 - Fixed the Visual C++ project file
1682 `builds/win32/visualc/freetype.dsp' since it didn't include the
1683 Postscript hinter component, causing errors at build time.
1685 - Fixed a small rendering bug in the anti-aliased renderer that
1686 only occurred when trying to draw thin (less than 1 pixel)
1687 strokes.
1689 - Fixed `builds/unix/freetype2.a4' which is used to generate a
1690 valid `freetype2.m4' for use with autoconf.
1692 - Fixed the OpenVMS Makefiles.
1695 II. MISCELLANEOUS
1697 - Added `configure' and `install' scripts to the top-level
1698 directory. A GNU-style installation is thus now easily possible
1699 with
1701 ./configure <options>
1702 make
1703 make install
1706 ======================================================================
1708 CHANGES BETWEEN 2.0.6 and 2.0.5
1710 I. IMPORTANT BUG FIXES
1712 - It wasn't possible to load embedded bitmaps when the auto-hinter
1713 was used. This is now fixed.
1715 - The TrueType font driver didn't load some composites properly
1716 (the sub-glyphs were slightly shifted, and this was only
1717 noticeable when using monochrome rendering).
1719 - Various fixes to the auto-hinter. They merely improve the
1720 output of sans-serif fonts. Note that there are still problems
1721 with serifed fonts and composites (accented characters).
1723 - All scalable font drivers erroneously returned un-fitted glyph
1724 advances when hinting was requested. This created problems for
1725 a number of layout applications. This is a very old bug that
1726 got undetected mainly because most test/demo program perform
1727 rounding explicitly or implicitly (through the cache).
1729 - `FT_Glyph_To_Bitmap' did erroneously modify the source glyph in
1730 certain cases.
1732 - `glnames.py' still contained a bug that made FreeType return
1733 invalid names for certain glyphs.
1735 - The library crashed when loading certain Type 1 fonts like
1736 `sadn.pfb' (`Stalingrad Normal'), which appear to contain
1737 pathetic font info dictionaries.
1739 - The TrueType glyph loader is now much more paranoid and checks
1740 everything when loading a given glyph image. This was necessary
1741 to avoid problems (crashes and/or memory overwrites) with broken
1742 fonts that came from a really buggy automatic font converter.
1745 II. IMPORTANT UPDATES AND NEW FEATURES
1747 - Important updates to the Mac-specific parts of the library.
1749 - The caching sub-system has been completely re-designed, and its
1750 API has evolved (the old one is still supported for backward
1751 compatibility).
1753 The documentation for it is not yet completed, sorry. For now,
1754 you are encouraged to continue using the old API. However, the
1755 ftview demo program in the ft2demos package has already been
1756 updated to use the new caching functions.
1758 - A new charmap cache is provided too. See `FTC_CMapCache'. This
1759 is useful to perform character code -> glyph index translations
1760 quickly, without the need for an opened FT_Face.
1762 - A NEW POSTSCRIPT HINTER module has been added to support native
1763 hints in the following formats: PostScript Type 1, PostScript
1764 CID, and CFF/CEF.
1766 Please test! Note that the auto-hinter produces better results
1767 for a number of badly-hinted fonts (mostly auto-generated ones)
1768 though.
1770 - A memory debugger is now part of the standard FreeType sources.
1771 To enable it, define FT_DEBUG_MEMORY in
1772 <freetype/config/ftoption.h>, and recompile the library.
1774 Additionally, define the _environment_ variable FT_DEBUG_MEMORY
1775 and run any program using FreeType. When the library is exited,
1776 a summary of memory footprints and possible leaks will be
1777 displayed.
1779 This works transparently with _any_ program that uses FreeType.
1780 However, you will need a lot of memory to use this (allocated
1781 blocks are never released to the heap to detect double deletes
1782 easily).
1785 III. MISCELLANEOUS
1787 - We are aware of subtle differences between the output of
1788 FreeType versions 1 and 2 when it comes to monochrome
1789 TrueType-hinted glyphs. These are most probably due to small
1790 differences in the monochrome rasterizers and will be worked out
1791 in an upcoming release.
1793 - We have decided to fork the sources in a `stable' branch, and an
1794 `unstable' one, since FreeType is becoming a critical component
1795 of many Unix systems.
1797 The next bug-fix releases of the library will be named 2.0.7,
1798 2.0.8, etc., while the `2.1' branch will contain a version of
1799 the sources where we will start major reworking of the library's
1800 internals, in order to produce FreeType 2.2.0 (or even 3.0) in a
1801 more distant future.
1803 We also hope that this scheme will allow much more frequent
1804 releases than in the past.
1807 ======================================================================
1809 CHANGES BETWEEN 2.0.5 and 2.0.4
1811 NOTE THAT 2.0.5 DOES NOT CONTAIN THE POSTSCRIPT HINTER. THIS MODULE
1812 WILL BE PART OF THE NEXT RELEASE (EITHER 2.0.6 or 2.1)
1814 - Fixed a bug that made certain glyphs, like `Cacute', `cacute' and
1815 `lslash' unavailable from Unicode charmaps of Postscript fonts.
1816 This prevented the correct display of Polish text, for example.
1818 - The kerning table of Type 1 fonts was loaded by FreeType, when its
1819 AFM file was attached to its face, but the
1820 FT_FACE_FLAG_HAS_KERNING bit flags was not set correctly,
1821 preventing FT_Get_Kerning to return meaningful values.
1823 - Improved SFNT (TrueType & OpenType) charmap support. Slightly
1824 better performance, as well as support for the new formats defined
1825 by the OpenType 1.3 specification (8, 10, and 12)
1827 - Fixed a serious typo in `src/base/ftcalc.c' which caused invalid
1828 computations in certain rare cases, producing ugly artefacts.
1830 - The size of the EM square is computed with a more accurate
1831 algorithm for Postscript fonts. The old one caused slight errors
1832 with embedded fonts found in PDF documents.
1834 - Fixed a bug in the cache manager that prevented normal LRU
1835 behaviour within the cache manager, causing unnecessary reloads
1836 (for FT_Face and FT_Size objects only).
1838 - Added a new function named `FT_Get_Name_Index' to retrieve the
1839 glyph index of a given glyph name, when found in a face.
1841 - Added a new function named `FT_Get_Postscript_Name' to retrieve
1842 the `unique' Postscript font name of a given face.
1844 - Added a new public header size named FT_SIZES_H (or
1845 <freetype/ftsizes.h>) providing new FT_Size-management functions:
1846 FT_New_Size, FT_Activate_Size, FT_Done_Size.
1848 - Fixed a reallocation bug that generated a dangling pointer (and
1849 possibly memory leaks) with Postscript fonts (in
1850 src/psaux/psobjs.c).
1852 - Many fixes for 16-bit correctness.
1854 - Removed many pedantic compiler warnings from the sources.
1856 - Added an Amiga build directory in `builds/amiga'.
1859 ======================================================================
1861 CHANGES BETWEEN 2.0.4 and 2.0.3
1863 - Fixed a rather annoying bug that was introduced in 2.0.3. Namely,
1864 the font transformation set through FT_Set_Transform was applied
1865 twice to auto-hinted glyphs, resulting in incorrectly rotated text
1866 output.
1868 - Fixed _many_ compiler warnings. FT2 should now compile cleanly
1869 with Visual C++'s most pedantic warning level (/W4). It already
1870 compiled fine with GCC and a few other compilers.
1872 - Fixed a bug that prevented the linear advance width of composite
1873 TrueType glyphs to be correctly returned.
1875 - Fixed the Visual C++ project files located in
1876 `builds/win32/visualc' (previous versions used older names of the
1877 library).
1879 - Many 32-bit constants have an `L' appended to their value, in
1880 order to improve the 16-bitness of the code. Someone is actually
1881 trying to use FT2 on an Atari ST machine!
1883 - Updated the `builds/detect.mk' file in order to automatically
1884 build FT2 on AIX systems. AIX uses `/usr/sbin/init' instead of
1885 `/sbin/init' and wasn't previously detected as a Unix platform by
1886 the FreeType build system.
1888 - Updated the Unix-specific portions of the build system (new
1889 libtool version, etc.).
1891 - The SFNT kerning loader now ensures that the table is sorted
1892 (since some problem fonts do not meet this requirement).
1895 =======================================================================
1897 CHANGES BETWEEN 2.0.3 and 2.0.2
1899 I. CHANGES TO THE MODULES / FONT DRIVERS
1901 - THE AUTO-HINTER HAS BEEN SLIGHTLY IMPROVED, in order to fix
1902 several annoying artefacts, mainly:
1904 - Blue zone alignment of horizontal stems wasn't performed
1905 correctly, resulting in artefacts like the `d' being placed
1906 one pixel below the `b' in some fonts like Time New Roman.
1908 - Overshoot thresholding wasn't performed correctly, creating
1909 unpleasant artefacts at large character pixel sizes.
1911 - Composite glyph loading has been simplified. This gets rid
1912 of various artefacts where the components of a composite
1913 glyphs were not correctly spaced.
1915 These are the last changes to the current auto-hinting module.
1916 A new hinting sub-system is currently in the work in order to
1917 support native hints in Type 1 / CFF / OpenType fonts, as well
1918 as globally improve rendering.
1920 - The PCF driver has been fixed. It reported invalid glyph
1921 dimensions for the fonts available on Solaris.
1923 - The Type 1, CID and CFF drivers have been modified to fix the
1924 computation of the EM size.
1926 - The Type 1 driver has been fixed to avoid a dangerous bug that
1927 crashed the library with non-conforming fonts (i.e. ones that do
1928 not place the .notdef glyph at position 0).
1930 - The TrueType driver had a rather subtle bug (dangling pointer
1931 when loading composite glyphs) that could crash the library in
1932 rare occasions!
1935 II. HIGH-LEVEL API CHANGES
1937 - The error code enumeration values have been changed. An error
1938 value is decomposed in a generic error code, and a module
1939 number. see <freetype/fterrors.h> for details.
1941 - A new public header file has been introduced, named
1942 FT_TRIGONOMETRY_H (include/freetype/fttrig.h), providing
1943 trigonometric functions to compute sines, cosines, arctangents,
1944 etc. with 16.16 fixed precision. The implementation is based on
1945 the CORDIC algorithm and is very fast while being sufficiently
1946 accurate.
1949 III. INTERNALS
1951 - Added BeOS-specific files in the old build sub-system. Note
1952 that no changes were required to compile the library with Jam.
1954 - The configuration is now capable of automatically detecting
1955 64-bit integers on a set of predefined compilers (GCC, Visual
1956 C++, Borland C++) and will use them by default. This provides a
1957 small performance boost.
1959 - A small memory leak that happened when opening 0-sized files
1960 (duh!) have been fixed.
1962 - Fixed bezier stack depth bug in the routines provided by the
1963 FT_BBOX_H header file. Also fixed similar bugs in the
1964 rasterizers.
1966 - The outline bounding box code has been rewritten to use direct
1967 computations, instead of bezier sub-division, to compute the
1968 exact bounding box of glyphs. This is slightly slower but more
1969 accurate.
1971 - The build system has been improved and fixed, mainly to support
1972 `make' on Windows 2000 correctly, avoid problems with `make
1973 distclean' on non Unix systems, etc.
1975 - Hexadecimal constants have been suffixed with `U' to avoid
1976 problems with certain compilers on 64-bit platforms.
1978 - A new directory named `src/tools' has been created. It contains
1979 Python scripts and simple unit test programs used to develop the
1980 library.
1982 - The DocMaker tool has been moved from `docs' to `src/tools' and
1983 has been updated with the following:
1985 - Now accepts the `--title=XXXX' or `-t XXXX' option from the
1986 command line to set the project's name in the generated API
1987 reference.
1989 - Now accepts the `--output=DIR' or `-o DIR' option from the
1990 command line to set the output directory for all generated
1991 HTML files.
1993 - Now accepts the `--prefix=XXXX' or `-p XXX' option from the
1994 command line to set the file prefix to use for all
1995 generated HTML files.
1997 - Now generates the current time/data on each generated page
1998 in order to distinguish between versions.
2000 DocMaker can be used with other projects now, not only FT2
2001 (e.g. MLib, FTLayout, etc.).
2004 ======================================================================
2006 CHANGES BETWEEN 2.0.2 and 2.0.1
2008 I. CHANGES TO THE MODULES / FONT DRIVERS
2010 - THE TRUETYPE BYTECODE INTERPRETER IS NOW TURNED OFF, in order to
2011 avoid legal problems with the Apple patents. It seems that we
2012 mistakenly turned this option on in previous releases of the
2013 build.
2015 Note that if you want to use the bytecode interpreter in order
2016 to get high-quality TrueType rendering, you will need to toggle
2017 by hand the definition of the
2018 TT_CONFIG_OPTION_BYTECODE_INTERPRETER macro in the file
2019 `include/freetype/config/ftoption.h'.
2021 - The CFF driver has been improved by Tom Kacvinsky and Sander van
2022 der Wal:
2024 * Support for `seac' emulation.
2025 * Support for `dotsection'.
2026 * Support for retrieving glyph names through
2027 `FT_Get_Glyph_Name'.
2029 The first two items are necessary to correctly a large number of
2030 Type 1 fonts converted to the CFF formats by Adobe Acrobat.
2032 - The Type 1 driver was also improved by Tom & others:
2034 * Better EM size computation.
2035 * Better support for synthetic (transformed) fonts.
2036 * The Type 1 driver returns the charstrings corresponding to
2037 each glyph in the `glyph->control_data' field after a call to
2038 `FT_Load_Glyph' (thanks Ha Shao).
2040 - Various other bugfixes, including the following:
2042 * Fixed a nasty memory leak in the Type 1 driver.
2043 * The autohinter and the pcf driver used static writable data
2044 when they shouldn't.
2045 * Many casts were added to make the code more 64-bits safe. It
2046 also now compiles on Windows XP 64-bits without warnings.
2047 * Some incorrect writable statics were removed in the `autohint'
2048 and `pcf' drivers. FreeType 2 now compiles on Epoc again.
2051 II. CHANGES TO THE HIGH-LEVEL API
2053 - The library header files inclusion scheme has been changed. The
2054 old scheme looked like:
2056 #include <freetype/freetype.h>
2057 #include <freetype/ftglyph.h>
2058 #include <freetype/ftcache.h>
2059 #include <freetype/cache/ftimage.h>
2061 Now you should use:
2063 #include <ft2build.h>
2064 #include FT_FREETYPE_H
2065 #include FT_GLYPH_H
2066 #include FT_CACHE_H
2067 #include FT_CACHE_IMAGE_H
2069 NOTE THAT THE OLD INCLUSION SCHEME WILL STILL WORK WITH THIS
2070 RELEASE. HOWEVER, WE DO NOT GUARANTEE THAT THIS WILL STILL BE
2071 TRUE IN THE NEXT ONE (A.K.A. FREETYPE 2.1).
2073 The file <ft2build.h> is used to define the header filename
2074 macros. The complete and commented list of macros is available
2075 in the API reference under the section name `Header File Macros'
2076 in Chapter I.
2078 For more information, see section I of the following document:
2080 http://www.freetype.org/
2081 freetype2/docs/tutorial/step1.html
2083 or
2085 http://freetype.sourceforge.net/
2086 freetype2/docs/tutorial/step1.html
2088 - Many, many comments have been added to the public source file in
2089 order to automatically generate the API Reference through the
2090 `docmaker.py' Python script.
2092 The latter has been updated to support the grouping of sections
2093 in chapters and better index sort. See:
2095 http://www.freetype.org/freetype2/docs/reference/ft2-toc.html
2098 III. CHANGES TO THE BUILD PROCESS
2100 - If you are not building FreeType 2 with its own build system
2101 (but with your own Makefiles or project files), you will need to
2102 be aware that the build process has changed a little bit.
2104 You don't need to put the `src' directory in the include path
2105 when compiling any FT2 component. Instead, simply put the
2106 component's directory in the current include path.
2108 So, if you were doing something like:
2110 cc -c -Iinclude -Isrc src/base/ftbase.c
2112 change the line to:
2114 cc -c -Iinclude -Isrc/base src/base/ftbase.c
2116 If you were doing something like:
2118 cd src/base
2119 cc -c -I../../include -I.. ftbase.c
2121 change it to:
2123 cd src/base
2124 cc -c -I../../include ftbase.c
2127 ======================================================================
2129 CHANGES BETWEEN 2.0.1 and 2.0
2131 2.0.1 introduces a few changes:
2133 - Fixed many bugs related to the support of CFF / OpenType fonts.
2134 These formats are now much better supported though there is
2135 still work planned to deal with charset tables and PDF-embedded
2136 CFF files that use the old `seac' command.
2138 - The library could not be compiled in debug mode with a very
2139 small number of C compilers whose pre-processors didn't
2140 implement the `##' directive correctly (i.e. per se the ANSI C
2141 specification!) An elegant fix was found.
2143 - Added support for the free Borland command-line C++ Builder
2144 compiler. Use `make setup bcc32'. Also fixed a few source
2145 lines that generated new warnings with BCC32.
2147 - Fixed a bug in FT_Outline_Get_BBox when computing the extrema of
2148 a conic Bezier arc.
2150 - Updated the INSTALL file to add IDE compilation.
2152 - Other minor bug fixes, from invalid Type 1 style flags to
2153 correct support of synthetic (obliqued) fonts in the
2154 auto-hinter, better support for embedded bitmaps in a SFNT font.
2156 - Fixed some problems with `freetype-config'.
2158 Finally, the `standard' scheme for including FreeType headers is now
2159 gradually changing, but this will be explained in a later release
2160 (probably 2.0.2).
2162 And very special thanks to Tom Kacvinsky and YAMANO-UCHI Hidetoshi
2163 for their contributions!
2166 ======================================================================
2168 CHANGES BETWEEN beta8 and 2.0
2170 - Changed the default installation path for public headers from
2171 `include/freetype' to `include/freetype2'.
2173 Also added a new `freetype-config' that is automatically generated
2174 and installed on Unix and Cygwin systems. The script itself is
2175 used to retrieve the current install path, C compilation flags as
2176 well as linker flags.
2178 - Fixed several small bugs:
2180 * Incorrect max advance width for fixed-pitch Type 1 fonts.
2181 * Incorrect glyph names for certain TrueType fonts.
2182 * The glyph advance was not copied when FT_Glyph_To_Bitmap was
2183 called.
2184 * The linearHoriAdvance and linearVertAdvance fields were not
2185 correctly returned for glyphs processed by the auto-hinter.
2186 * `type1z' renamed back to `type1'; the old `type1' module has
2187 been removed.
2189 - Revamped the build system to make it a lot more generic. This
2190 will allow us to re-use nearly un-modified in lots of other
2191 projects (including FreeType Layout).
2193 - Changed `cid' to use `psaux' too.
2195 - Added the cache sub-system. See <freetype/ftcache.h> as well as
2196 the sources in `src/cache'. Note that it compiles but is still
2197 untested for now.
2199 - Updated `docs/docmaker.py', a draft API reference is available at
2200 http://www.freetype.org/ft2api.html.
2202 - Changed `type1' to use `psaux'.
2204 - Created a new module named `psaux' to hold the Type 1 & Type 2
2205 parsing routines. It should be used by `type1', `cid', and `cff'
2206 in the future.
2208 - Fixed an important bug in `FT_Glyph_Get_CBox'.
2210 - Fixed some compiler warnings that happened since the TrueType
2211 bytecode decoder was deactivated by default.
2213 - Fixed two memory leaks:
2215 * The memory manager (16 bytes) isn't released in
2216 FT_Done_FreeType!
2217 * Using custom input streams, the copy of the original stream was
2218 never released.
2220 - Fixed the auto-hinter by performing automatic computation of the
2221 `filling direction' of each glyph. This is done through a simple
2222 and fast approximation, and seems to work (problems spotted by
2223 Werner though). The Arphic fonts are a lot nicer though there are
2224 still a lot of things to do to handle Asian fonts correctly.
2227 ======================================================================
2229 BETA-8 (RELEASE CANDIDATE) CHANGES
2231 - Deactivated the TrueType bytecode interpreter by default.
2233 - Deactivated the `src/type1' font driver. Now `src/type1z' is used
2234 by default.
2236 - Updates to the build system. We now compile the library correctly
2237 under Unix system through `configure' which is automatically
2238 called on the first `make' invocation.
2240 - Added the auto-hinting module! Fixing some bugs here and there.
2242 - Found some bugs in the composite loader (seac) of the Type1-based
2243 font drivers.
2245 - Renamed the directory `freetype2/config' to `freetype2/builds' and
2246 updated all relevant files.
2248 - Found a memory leak in the `type1' driver.
2250 - Incorporated Tom's patches to support flex operators correctly in
2251 OpenType/CFF fonts. Now all I need is to support pure CFF and CEF
2252 fonts to be done with this driver :-)
2254 - Added the Windows FNT/FON driver in `src/winfonts'. For now, it
2255 always `simulates' a Unicode charmap, so it shouldn't be
2256 considered completed right now.
2258 It is there to be more a proof of concept than anything else
2259 anyway. The driver is a single C source file, that compiles to 3
2260 Kb of code.
2262 I'm still working on the PCF/BDF drivers, but I'm too lazy to
2263 finish them now.
2265 - CHANGES TO THE HIGH-LEVEL API
2267 * FT_Get_Kerning has a new parameter that allows you to select the
2268 coordinates of the kerning vector (font units, scaled, scaled +
2269 grid-fitted).
2270 * The outline functions are now in <freetype/ftoutln.h> and not
2271 part of <freetype/freetype.h> anymore.
2272 * <freetype/ftmodule.h> now contains declarations for
2273 FT_New_Library, FT_Done_Library, FT_Add_Default_Modules.
2274 * The so-called convenience functions have moved from `ftoutln.c'
2275 to `ftglyph.c', and are thus available with this optional
2276 component of the library. They are declared in
2277 <freetype/ftglyph.h> now.
2278 * Anti-aliased rendering is now the default for FT_Render_Glyph
2279 (i.e. corresponds to render_mode == 0 == ft_render_mode_normal).
2280 To generate a monochrome bitmap, use ft_render_mode_mono, or the
2281 FT_LOAD_MONOCHROME flag in FT_Load_Glyph/FT_Load_Char.
2282 FT_LOAD_ANTI_ALIAS is still defined, but values to 0.
2283 * <freetype/freetype.h> now include <freetype/config/ftconfig.h>,
2284 solving a few headaches :-)
2285 * The type FT_GlyphSlotRec has now a `library' field.
2287 - CHANGES TO THE `ftglyph.h' API
2289 This API has been severely modified in order to make it simpler,
2290 clearer, and more efficient. It certainly now looks like a real
2291 `glyph factory' object, and allows client applications to manage
2292 (i.e. transform, bbox and render) glyph images without ever
2293 knowing their original format.
2295 - Added support for CID-keyed fonts to the CFF driver. Maybe
2296 support for pure CFF + CEF fonts should come in?
2298 - Cleaned up source code in order to avoid two functions with the
2299 same name. Also changed the names of the files in `type1z' from
2300 `t1XXXX' to `z1XXXX' in order to avoid any conflicts.
2302 `make multi' now works well :-)
2304 Also removed the use of `cidafm' for now, even if the source files
2305 are still there. This functionality will certainly go into a
2306 specific module.
2308 - ADDED SUPPORT FOR THE AUTO-HINTER
2310 It works :-) I have a demo program which simply is a copy of
2311 `ftview' that does a `FT_Add_Module(library,
2312 &autohinter_module_class)' after library initialization, and Type
2313 1 & OpenType/CFF fonts are now hinted.
2315 CID fonts are not hinted, as they include no charmap and the
2316 auto-hinter doesn't include `generic' global metrics computations
2317 yet.
2319 Now, I need to release this thing to the FreeType 2 source.
2321 - CHANGES TO THE RENDERER MODULES
2323 The monochrome and smooth renderers are now in two distinct
2324 directories, namely `src/raster1' and `src/smooth'. Note that the
2325 old `src/renderer' is now gone.
2327 I ditched the 5-gray-levels renderers. Basically, it involved a
2328 simple #define toggle in 'src/raster1/ftraster.c'.
2330 FT_Render_Glyph, FT_Outline_Render & FT_Outline_Get_Bitmap now
2331 select the best renderer available, depending on render mode. If
2332 the current renderer for a given glyph image format isn't capable
2333 of supporting the render mode, another one will be found in the
2334 library's list. This means that client applications do not need
2335 to switch or set the renderers themselves (as in the latest
2336 change), they'll get what they want automatically. At last.
2338 Changed the demo programs accordingly.
2340 - MAJOR INTERNAL REDESIGN:
2342 A lot of internal modifications have been performed lately on the
2343 source in order to provide the following enhancements:
2345 * More generic module support:
2347 The FT_Module type is now defined to represent a handle to a
2348 given module. The file <freetype/ftmodule.h> contains the
2349 FT_Module_Class definition, as well as the module-loading public
2350 API.
2352 The FT_Driver type is still defined, and still represents a
2353 pointer to a font driver. Note that FT_Add_Driver is replaced
2354 by FT_Add_Module, FT_Get_Driver by FT_Get_Module, etc.
2356 * Support for generic glyph image types:
2358 The FT_Renderer type is a pointer to a module used to perform
2359 various operations on glyph image.
2361 Each renderer is capable of handling images in a single format
2362 (e.g. ft_glyph_format_outline). Its functions are used to:
2364 - transform an glyph image
2365 - render a glyph image into a bitmap
2366 - return the control box (dimensions) of a given glyph image
2368 The scan converters `ftraster.c' and `ftgrays.c' have been moved
2369 to the new directory `src/renderer', and are used to provide two
2370 default renderer modules.
2372 One corresponds to the `standard' scan-converter, the other to
2373 the `smooth' one.
2375 he current renderer can be set through the new function
2376 FT_Set_Renderer.
2378 The old raster-related function FT_Set_Raster, FT_Get_Raster and
2379 FT_Set_Raster_Mode have now disappeared, in favor of the new:
2381 FT_Get_Renderer
2382 FT_Set_Renderer
2384 See the file <freetype/ftrender.h> for more details.
2386 These changes were necessary to properly support different
2387 scalable formats in the future, like bi-color glyphs, etc.
2389 * Glyph loader object:
2391 A new internal object, called a 'glyph loader' has been
2392 introduced in the base layer. It is used by all scalable format
2393 font drivers to load glyphs and composites.
2395 This object has been created to reduce the code size of each
2396 driver, as each one of them basically re-implemented its
2397 functionality.
2399 See <freetype/internal/ftobjs.h> and the FT_GlyphLoader type for
2400 more information.
2402 * FT_GlyphSlot has new fields:
2404 In order to support extended features (see below), the
2405 FT_GlyphSlot structure has a few new fields:
2407 linearHoriAdvance:
2409 This field gives the linearly scaled (i.e. scaled but
2410 unhinted) advance width for the glyph, expressed as a 16.16
2411 fixed pixel value. This is useful to perform WYSIWYG text.
2413 linearVertAdvance:
2414 This field gives the linearly scaled advance height for the
2415 glyph (relevant in vertical glyph layouts only). This is
2416 useful to perform WYSIWYG text.
2418 Note that the two above field replace the removed `metrics2'
2419 field in the glyph slot.
2421 advance:
2422 This field is a vector that gives the transformed advance for
2423 the glyph. By default, it corresponds to the advance width,
2424 unless FT_LOAD_VERTICAL_LAYOUT was specified when calling
2425 FT_Load_Glyph or FT_Load_Char.
2427 bitmap_left:
2428 This field gives the distance in integer pixels from the
2429 current pen position to the left-most pixel of a glyph image
2430 IF IT IS A BITMAP. It is only valid when the `format' field
2431 is set to `ft_glyph_format_bitmap', for example, after calling
2432 the new function FT_Render_Glyph.
2434 bitmap_top:
2435 This field gives the distance in integer pixels from the
2436 current pen position (located on the baseline) to the top-most
2437 pixel of the glyph image IF IT IS A BITMAP. Positive values
2438 correspond to upwards Y.
2440 loader:
2441 This is a new private field for the glyph slot. Client
2442 applications should not touch it.
2445 * Support for transforms and direct rendering in FT_Load_Glyph:
2447 Most of the functionality found in <freetype/ftglyph.h> has been
2448 moved to the core library. Hence, the following:
2450 - A transform can be specified for a face through
2451 FT_Set_Transform. this transform is applied by FT_Load_Glyph
2452 to scalable glyph images (i.e. NOT TO BITMAPS) before the
2453 function returns, unless the bit flag FT_LOAD_IGNORE_TRANSFORM
2454 was set in the load flags.
2456 - Once a glyph image has been loaded, it can be directly
2457 converted to a bitmap by using the new FT_Render_Glyph
2458 function. Note that this function takes the glyph image from
2459 the glyph slot, and converts it to a bitmap whose properties
2460 are returned in `face.glyph.bitmap', `face.glyph.bitmap_left'
2461 and `face.glyph.bitmap_top'. The original native image might
2462 be lost after the conversion.
2464 - When using the new bit flag FT_LOAD_RENDER, the FT_Load_Glyph
2465 and FT_Load_Char functions will call FT_Render_Glyph
2466 automatically when needed.
2468 - Reformatted all modules source code in order to get rid of the
2469 basic data types redifinitions (i.e. `TT_Int' instead of `FT_Int',
2470 `T1_Fixed' instead of `FT_Fixed'). Hence the format-specific
2471 prefixes like `TT_', `T1_', `T2_' and `CID_' are only used for
2472 relevant structures.
2475 ======================================================================
2477 OLD CHANGES FOR BETA 7
2479 - bug-fixed the OpenType/CFF parser. It now loads and displays my
2480 two fonts nicely, but I'm pretty certain that more testing is
2481 needed :-)
2483 - fixed the crummy Type 1 hinter, it now handles accented characters
2484 correctly (well, the accent is not always well placed, but that's
2485 another problem..)
2487 - added the CID-keyed Type 1 driver in `src/cid'. Works pretty well
2488 for only 13 Kb of code ;-) Doesn't read AFM files though, nor the
2489 really useful CMAP files..
2491 - fixed two bugs in the smooth renderer (src/base/ftgrays.c).
2492 Thanks to Boris Letocha for spotting them and providing a fix.
2494 - fixed potential `divide by zero' bugs in ftcalc.c.
2496 - added source code for the OpenType/CFF driver (still incomplete
2497 though..)
2499 - modified the SFNT driver slightly to perform more robust header
2500 checks in TT_Load_SFNT_Header. This prevents certain font files
2501 (e.g. some Type 1 Multiple Masters) from being incorrectly
2502 `recognized' as TrueType font files..
2504 - moved a lot of stuff from the TrueType driver to the SFNT module,
2505 this allows greater code re-use between font drivers
2506 (e.g. TrueType, OpenType, Compact-TrueType, etc..)
2508 - added a tiny segment cache to the SFNT Charmap 4 decoder, in order
2509 to minimally speed it up..
2511 - added support for Multiple Master fonts in `type1z'. There is
2512 also a new file named <freetype/ftmm.h> which defines functions to
2513 manage them from client applications.
2515 The new file `src/base/ftmm.c' is also optional to the engine..
2517 - various formatting changes (e.g. EXPORT_DEF -> FT_EXPORT_DEF) +
2518 small bug fixes in FT_Load_Glyph, the `type1' driver, etc..
2520 - a minor fix to the Type 1 driver to let them apply the font matrix
2521 correctly (used for many oblique fonts..)
2523 - some fixes for 64-bit systems (mainly changing some FT_TRACE calls
2524 to use %p instead of %lx). Thanks to Karl Robillard.
2526 - fixed some bugs in the sbit loader (src/base/sfnt/ttsbit.c) +
2527 added a new flag, FT_LOAD_CROP_BITMAP to query that bitmaps be
2528 cropped when loaded from a file (maybe I should move the bitmap
2529 cropper to the base layer ??).
2531 - changed the default number of gray levels of the smooth renderer
2532 to 256 (instead of the previous 128). Of course, the human eye
2533 can't see any difference ;-)
2535 - removed TT_MAX_SUBGLYPHS, there is no static limit on the number
2536 of subglyphs in a TrueType font now..
2539 ======================================================================
2541 OLD CHANGES 16 May 2000
2543 - tagged `BETA-6' in the CVS tree. This one is a serious release
2544 candidate even though it doesn't incorporate the auto-hinter yet..
2546 - various obsolete files were removed, and copyright header updated
2548 - finally updated the standard raster to fix the monochrome
2549 rendering bug + re-enable support for 5-gray levels anti-aliasing
2550 (suck, suck..)
2552 - created new header files, and modified sources accordingly:
2554 <freetype/fttypes.h>
2555 - simple FreeType types, without the API
2556 <freetype/internal/ftmemory.h>
2557 - definition of memory-management macros
2559 - added the `DSIG' (OpenType Digital Signature) tag to
2560 <freetype/tttags.h>
2562 - light update/cleaning of the build system + changes to the sources
2563 in order to get rid of _all_ compiler warnings with three
2564 compilers, i.e:
2566 gcc with `-ansi -pedantic -Wall -W', Visual C++ with `/W3 /WX' and
2567 LCC
2569 IMPORTANT NOTE FOR WIN32-LCC USERS:
2570 |
2571 | It seems the C pre-processor that comes with LCC is broken, it
2572 | doesn't recognize the ANSI standard directives # and ##
2573 | correctly when one of the argument is a macro. Also,
2574 | something like:
2575 |
2576 | #define F(x) print##x
2577 |
2578 | F(("hello"))
2579 |
2580 | will get incorrectly translated to:
2581 |
2582 | print "hello")
2583 |
2584 | by its pre-processor. For this reason, you simply cannot build
2585 | FreeType 2 in debug mode with this compiler..
2587 - yet another massive grunt work. I've changed the definition of
2588 the EXPORT_DEF, EXPORT_FUNC, BASE_DEF & BASE_FUNC macros. These
2589 now take an argument, which is the function's return value type.
2591 This is necessary to compile FreeType as a DLL on Windows and
2592 OS/2. Depending on the compiler used, a compiler-specific keyword
2593 like __export or __system must be placed before (VisualC++) or
2594 after (BorlandC++) the type..
2596 Of course, this needed a lot of changes throughout the source code
2597 to make it compile again... All cleaned up now, apparently..
2599 Note also that there is a new EXPORT_VAR macro defined to allow
2600 the _declaration_ of an exportable public (constant)
2601 variable. This is the case of the raster interfaces (see
2602 ftraster.h and ftgrays.h), as well as each module's interface (see
2603 sfdriver.h, psdriver.h, etc..)
2605 - new feature: it is now possible to pass extra parameters to font
2606 drivers when creating a new face object. For now,
2607 this capability is unused. It could however prove to
2608 be useful in a near future..
2610 the FT_Open_Args structure was changes, as well as the internal
2611 driver interface (the specific `init_face' module function has
2612 now a different signature).
2614 - updated the tutorial (not finished though).
2616 - updated the top-level BUILD document
2618 - fixed a potential memory leak that could occur when loading
2619 embedded bitmaps.
2621 - added the declaration of FT_New_Memory_Face in
2622 <freetype/freetype.h>, as it was missing from the public header
2623 (the implementation was already in `ftobjs.c').
2625 - the file <freetype/fterrors.h> has been seriously updated in order
2626 to allow the automatic generation of error message tables. See
2627 the comments within it for more information.
2629 - major directory hierarchy re-organisation. This was done for two
2630 things:
2632 * first, to ease the `manual' compilation of the library by
2633 requiring at lot less include paths :-)
2635 * second, to allow external programs to effectively access
2636 internal data fields. For example, this can be extremely
2637 useful if someone wants to write a font producer or a font
2638 manager on top of FreeType.
2640 Basically, you should now use the 'freetype/' prefix for header
2641 inclusion, as in:
2643 #include <freetype/freetype.h>
2644 #include <freetype/ftglyph.h>
2646 Some new include sub-directories are available:
2648 a. the `freetype/config' directory, contains two files used to
2649 configure the build of the library. Client applications
2650 should not need to look at these normally, but they can if
2651 they want.
2653 #include <freetype/config/ftoption.h>
2654 #include <freetype/config/ftconfig.h>
2656 b. the `freetype/internal' directory, contains header files that
2657 describes library internals. These are the header files that
2658 were previously found in the `src/base' and `src/shared'
2659 directories.
2662 As usual, the build system and the demos have been updated to
2663 reflect the change..
2665 Here's a layout of the new directory hierarchy:
2667 TOP_DIR
2668 include/
2669 freetype/
2670 freetype.h
2671 ...
2672 config/
2673 ftoption.h
2674 ftconfig.h
2675 ftmodule.h
2677 internal/
2678 ftobjs.h
2679 ftstream.h
2680 ftcalc.h
2681 ...
2683 src/
2684 base/
2685 ...
2687 sfnt/
2688 psnames/
2689 truetype/
2690 type1/
2691 type1z/
2694 Compiling a module is now much easier, for example, the following
2695 should work when in the TOP_DIR directory on an ANSI build:
2697 gcc -c -I./include -I./src/base src/base/ftbase.c
2698 gcc -c -I./include -I./src/sfnt src/sfnt/sfnt.c
2699 etc..
2701 (of course, using -Iconfig/<system> if you provide system-specific
2702 configuration files).
2704 - updated the structure of FT_Outline_Funcs in order to allow direct
2705 coordinate scaling within the outline decomposition routine (this
2706 is important for virtual `on' points with TrueType outlines) +
2707 updates to the rasters to support this..
2709 - updated the OS/2 table loading code in `src/sfnt/ttload.c' in
2710 order to support version 2 of the table (see OpenType 1.2 spec)
2712 - created `include/tttables.h' and `include/t1tables.h' to allow
2713 client applications to access some of the SFNT and T1 tables of a
2714 face with a procedural interface (see `FT_Get_Sfnt_Table') +
2715 updates to internal source files to reflect the change..
2717 - some cleanups in the source code to get rid of warnings when
2718 compiling with the `-Wall -W -ansi -pedantic' options in gcc.
2720 - debugged and moved the smooth renderer to `src/base/ftgrays.c' and
2721 its header to `include/ftgrays.h'
2723 - updated TT_MAX_SUBGLYPHS to 96 as some CJK fonts have composites
2724 with up to 80 sub-glyphs !! Thanks to Werner
2727 ======================================================================
2729 OLD CHANGES - 14-apr-2000
2731 - fixed a bug in the TrueType glyph loader that prevented the
2732 correct loading of some CJK glyphs in mingli.ttf
2734 - improved the standard Type 1 hinter in `src/type1'
2736 - fixed two bugs in the experimental Type 1 driver in `src/type1z'
2737 to handle the new XFree86 4.0 fonts (and a few other ones..)
2739 - the smooth renderer is now complete and supports sub-banding to
2740 render large glyphs at high speed. However, it is still located
2741 in `demos/src/ftgrays.c' and should move to the library itself in
2742 the next beta. NOTE: The smooth renderer doesn't compile in
2743 stand-alone mode anymore, but this should be fixed RSN..
2745 - introduced convenience functions to more easily deal with glyph
2746 images, see `include/ftglyph.h' for more details, as well as the
2747 new demo program named `demos/src/ftstring.c' that demonstrates
2748 its use
2750 - implemented FT_LOAD_NO_RECURSE in both the TrueType and Type 1
2751 drivers (this is required by the auto-hinter to improve its
2752 results).
2754 - changed the raster interface, in order to allow client
2755 applications to provide their own span-drawing callbacks.
2756 However, only the smooth renderer supports this. See
2757 `FT_Raster_Params' in the file `include/ftimage.h'.
2759 - fixed a small bug in FT_MulFix that caused incorrect transform
2760 computation!
2762 - Note: The tutorial is out-of-date.
2765 ======================================================================
2767 OLD CHANGES - 12-mar-2000
2769 - changed the layout of configuration files : now, all ANSI
2770 configuration files are located in
2771 `freetype2/config'. System-specific over-rides can be placed in
2772 `freetype2/config/<system>'.
2774 - moved all configuration macros to `config/ftoption.h'
2776 - improvements in the Type 1 driver with AFM support
2778 - changed the fields in the FT_Outline structure : the old `flags'
2779 array is re-named `tags', while all ancient flags are encoded into
2780 a single unsigned int named `flags'.
2782 - introduced new flags in FT_Outline.flags (see
2783 ft_outline_.... enums in `ftimage.h').
2785 - changed outline functions to `FT_Outline_<action>' syntax
2787 - added a smooth anti-alias renderer to the demonstration programs
2789 - added Mac graphics driver (thanks Just)
2791 - FT_Open_Face changed in order to received a pointer to a
2792 FT_Open_Args descriptor..
2794 - various cleanups, a few more API functions implemented (see
2795 FT_Attach_File)
2797 - updated some docs
2800 ======================================================================
2802 OLD CHANGES - 22-feb-2000
2804 - introduced the `psnames' module. It is used to:
2806 o convert a Postscript glyph name into the equivalent Unicode
2807 character code (used by the Type 1 driver(s) to synthesize on
2808 the fly a Unicode charmap).
2810 o provide an interface to retrieve the Postscript names of the
2811 Macintosh, Adobe Standard & Adobe Expert character codes.
2812 (the Macintosh names are used by the SFNT-module postscript
2813 names support routines, while the other two tables are used by
2814 the Type 1 driver(s)).
2816 - introduced the `type1z' alternate Type 1 driver. This is a (still
2817 experimental) driver for the Type 1 format that will ultimately
2818 replace the one in `src/type1'. It uses pattern matching to load
2819 data from the font, instead of a finite state analyzer. It works
2820 much better than the `old' driver with `broken' fonts. It is also
2821 much smaller (under 15 Kb).
2823 - the Type 1 drivers (both in `src/type1' and `src/type1z') are
2824 nearly complete. They both provide automatic Unicode charmap
2825 synthesis through the `psnames' module. No re-encoding vector is
2826 needed. (note that they still leak memory due to some code
2827 missing, and I'm getting lazy).
2829 Trivial AFM support has been added to read kerning information but
2830 wasn't exactly tested as it should ;-)
2832 - The TrueType glyph loader has been seriously rewritten (see the
2833 file `src/truetype/ttgload.c'. It is now much, much simpler as
2834 well as easier to read, maintain and understand :-) Preliminary
2835 versions introduced a memory leak that has been reported by Jack
2836 Davis, and is now fixed..
2838 - introduced the new `ft_glyph_format_plotter', used to represent
2839 stroked outlines like Windows `Vector' fonts, and certain Type 1
2840 fonts like `Hershey'. The corresponding raster will be written
2841 soon.
2843 - FT_New_Memory_Face is gone. Likewise, FT_Open_Face has a new
2844 interface that uses a structure to describe the input stream, the
2845 driver (if required), etc..
2848 TODO
2850 - Write FT_Get_Glyph_Bitmap and FT_Load_Glyph_Bitmap
2852 - Add a function like FT_Load_Character(face, char_code, load_flags)
2853 that would really embed a call to FT_Get_Char_Index then
2854 FT_Load_Glyph to ease developer's work.
2856 - Update the tutorial!
2858 - consider adding support for Multiple Master fonts in the Type 1
2859 drivers.
2861 - Test the AFM routines of the Type 1 drivers to check that kerning
2862 information is returned correctly.
2864 - write a decent auto-gridding component !! We need this to release
2865 FreeType 2.0 gold !
2868 less urgent needs:
2870 - add a CFF/Type2 driver
2871 - add a BDF driver
2872 - add a FNT/PCF/HBF driver
2873 - add a Speedo driver from the X11 sources
2876 ======================================================================
2878 OLDER CHANGES - 27-jan-2000
2880 - updated the `sfnt' module interface to allow several SFNT-based
2881 drivers to co-exist peacefully
2883 - updated the `T1_Face' type to better separate Postscript font
2884 content from the rest of the FT_Face structure. Might be used
2885 later by the CFF/Type2 driver..
2887 - added an experimental replacement Type 1 driver featuring advanced
2888 (and speedy) pattern matching to retrieve the data from postscript
2889 fonts.
2891 - very minor changes in the implementation of FT_Set_Char_Size and
2892 FT_Set_Pixel_Sizes (they now implement default to lighten the font
2893 driver's code).
2896 ======================================================================
2898 OLD MESSAGE
2900 This file summarizes the changes that occurred since the last `beta'
2901 of FreeType 2. Because the list is important, it has been divided into
2902 separate sections:
2904 Table Of Contents:
2906 I High-Level Interface (easier !)
2907 II Directory Structure
2908 III Glyph Image Formats
2909 IV Build System
2910 V Portability
2911 VI Font Drivers
2914 ----------------------------------------------------------------------
2916 High-Level Interface:
2918 The high-level API has been considerably simplified. Here is how:
2920 - resource objects have disappeared. this means that face objects
2921 can now be created with a single function call (see FT_New_Face
2922 and FT_Open_Face)
2924 - when calling either FT_New_Face & FT_Open_Face, a size object
2925 and a glyph slot object are automatically created for the face,
2926 and can be accessed through `face->glyph' and `face->size' if
2927 one really needs to. In most cases, there's no need to call
2928 FT_New_Size or FT_New_Glyph.
2930 - similarly, FT_Load_Glyph now only takes a `face' argument
2931 (instead of a glyph slot and a size). Also, its `result'
2932 parameter is gone, as the glyph image type is returned in the
2933 field `face->glyph.format'
2935 - the list of available charmaps is directly accessible through
2936 `face->charmaps', counting `face->num_charmaps' elements. Each
2937 charmap has an 'encoding' field which specifies which known
2938 encoding it deals with. Valid values are, for example:
2940 ft_encoding_unicode (for ASCII, Latin-1 and Unicode)
2941 ft_encoding_apple_roman
2942 ft_encoding_sjis
2943 ft_encoding_adobe_standard
2944 ft_encoding_adobe_expert
2946 other values may be added in the future. Each charmap still
2947 holds its `platform_id' and `encoding_id' values in case the
2948 encoding is too exotic for the current library
2951 ----------------------------------------------------------------------
2953 Directory Structure:
2955 Should seem obvious to most of you:
2957 freetype/
2958 config/ -- configuration sub-makefiles
2959 ansi/
2960 unix/ -- platform-specific configuration files
2961 win32/
2962 os2/
2963 msdos/
2965 include/ -- public header files, those to be included
2966 directly by client apps
2968 src/ -- sources of the library
2969 base/ -- the base layer
2970 sfnt/ -- the sfnt `driver' (see the drivers section
2971 below)
2972 truetype/ -- the truetype driver
2973 type1/ -- the type1 driver
2974 shared/ -- some header files shared between drivers
2976 demos/ -- demos/tools
2978 docs/ -- documentation (a bit empty for now)
2981 ----------------------------------------------------------------------
2983 Glyph Image Formats:
2985 Drivers are now able to register new glyph image formats within the
2986 library. For now, the base layer supports of course bitmaps and
2987 vector outlines, but one could imagine something different like
2988 colored bitmaps, bi-color vectors or whatever else (Metafonts anyone
2989 ??).
2991 See the file `include/ftimage.h'. Note also that the type
2992 FT_Raster_Map is gone, and is now replaced by FT_Bitmap, which
2993 should encompass all known bitmap types.
2995 Each new image format must provide at least one `raster', i.e. a
2996 module capable of transforming the glyph image into a bitmap. It's
2997 also possible to change the default raster used for a given glyph
2998 image format.
3000 The default outline scan-converter now uses 128 levels of grays by
3001 default, which tends to smooth many things. Note that the demo
3002 programs have been updated significantly in order to display these..
3005 ----------------------------------------------------------------------
3007 Build system:
3009 You still need GNU Make to build the library. The build system has
3010 been very seriously re-vamped in order to provide things like :
3012 - automatic host platform detection (reverting to 'config/ansi' if
3013 it is not detected, with pseudo-standard compilation flags)
3015 - the ability to compile from the Makefiles with very different and
3016 exotic compilers. Note that linking the library can be difficult
3017 for some platforms.
3019 For example, the file `config/win32/lcclib.bat' is invoked by the
3020 build system to create the `.lib' file with LCC-Win32 because its
3021 librarian has too many flaws to be invoked directly from the
3022 Makefile.
3024 Here's how it works:
3026 - the first time you type `make', the build system runs a series of
3027 sub-makefiles in order to detect your host platform. It then
3028 dumps what it found, and creates a file called `config.mk' in the
3029 current directory. This is a sub-Makefile used to define many
3030 important Make variables used to build the library.
3032 - the second time, the build system detects the `config.mk' then use
3033 it to build the library. All object files go into 'obj' by
3034 default, as well as the library file, but this can easily be
3035 changed.
3037 Note that you can run `make setup' to force another host platform
3038 detection even if a `config.mk' is present in the current
3039 directory. Another solution is simply to delete the file, then
3040 re-run make.
3042 Finally, the default compiler for all platforms is gcc (for now,
3043 this will hopefully changed in the future). You can however specify
3044 a different compiler by specifying it after the 'setup' target as
3045 in:
3047 gnumake setup lcc on Win32 to use the LCC compiler
3048 gnumake setup visualc on Win32 to use Visual C++
3050 See the file `config/<system>/detect.mk' for a list of supported
3051 compilers for your platforms.
3053 It should be relatively easy to write new detection rules files and
3054 config.mk..
3056 Finally, to build the demo programs, go to `demos' and launch GNU
3057 Make, it will use the `config.mk' in the top directory to build the
3058 test programs..
3061 ----------------------------------------------------------------------
3063 Portability:
3065 In the previous beta, a single FT_System object was used to
3066 encompass all low-level operations like thread synchronisation,
3067 memory management and i/o access. This has been greatly simplified:
3069 - thread synchronisation has been dropped, for the simple reason
3070 that the library is already re-entrant, and that if you really
3071 need two threads accessing the same FT_Library, you should
3072 really synchronize access to it yourself with a simple mutex.
3074 - memory management is performed through a very simple object
3075 called `FT_Memory', which really is a table containing a table
3076 of pointers to functions like malloc, realloc and free as well
3077 as some user data (closure).
3079 - resources have disappeared (they created more problems than they
3080 solved), and i/o management have been simplified greatly as a
3081 result. Streams are defined through FT_Stream objects, which
3082 can be either memory-based or disk-based.
3084 Note that each face has its own stream, which is closed only
3085 when the face object is destroyed. Hence, a function like
3086 TT_Flush_Face in 1.x cannot be directly supported. However, if
3087 you really need something like this, you can easily tailor your
3088 own streams to achieve the same feature at a lower level (and
3089 use FT_Open_Face instead of FT_New_Face to create the face).
3091 See the file `include/ftsystem.h' for more details, as well as the
3092 implementations found in `config/unix' and `config/ansi'.
3095 ----------------------------------------------------------------------
3097 Font Drivers:
3099 The Font Driver interface has been modified in order to support
3100 extensions & versioning.
3103 The list of the font drivers that are statically linked to the
3104 library at compile time is managed through a new configuration file
3105 called `config/<platform>/ftmodule.h'.
3107 This file is autogenerated when invoking `make modules'. This
3108 target will parse all sub-directories of 'src', looking for a
3109 `module.mk' rules file, used to describe the driver to the build
3110 system.
3112 Hence, one should call `make modules' each time a font driver is
3113 added or removed from the `src' directory.
3115 Finally, this version provides a `pseudo-driver' in `src/sfnt'.
3116 This driver doesn't support font files directly, but provides
3117 services used by all TrueType-like font drivers. Hence, its code is
3118 shared between the TrueType & OpenType font formats, and possibly
3119 more formats to come if we're lucky..
3122 ----------------------------------------------------------------------
3124 Extensions support:
3126 The extensions support is inspired by the one found in 1.x.
3128 Now, each font driver has its own `extension registry', which lists
3129 which extensions are available for the font faces managed by the
3130 driver.
3132 Extension ids are now strings, rather than 4-byte tags, as this is
3133 usually more readable.
3135 Each extension has:
3136 - some data, associated to each face object
3137 - an interface (table of function pointers)
3139 An extension that is format-specific should simply register itself
3140 to the correct font driver. Here is some example code:
3142 // Registering an extensions
3143 //
3144 FT_Error FT_Init_XXXX_Extension( FT_Library library )
3145 {
3146 FT_DriverInterface* tt_driver;
3148 driver = FT_Get_Driver( library, "truetype" );
3149 if (!driver) return FT_Err_Unimplemented_Feature;
3151 return FT_Register_Extension( driver, &extension_class );
3152 }
3155 // Implementing the extensions
3156 //
3157 FT_Error FT_Proceed_Extension_XXX( FT_Face face )
3158 {
3159 FT_XXX_Extension ext;
3160 FT_XXX_Extension_Interface ext_interface;
3162 ext = FT_Get_Extension( face, "extensionid", &ext_interface );
3163 if (!ext) return error;
3165 return ext_interface->do_it(ext);
3166 }
3168 ------------------------------------------------------------------------
3170 Copyright 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by
3171 David Turner, Robert Wilhelm, and Werner Lemberg.
3173 This file is part of the FreeType project, and may only be used,
3174 modified, and distributed under the terms of the FreeType project
3175 license, LICENSE.TXT. By continuing to use, modify, or distribute this
3176 file you indicate that you have read the license and understand and
3177 accept it fully.
3180 Local Variables:
3181 version-control: never
3182 coding: utf-8
3183 End:
3185 --- end of CHANGES ---