From 4639c4bddba89ebed752a3115b612b32a0db44b6 Mon Sep 17 00:00:00 2001 From: Werner Lemberg Date: Mon, 15 Apr 2002 13:37:29 +0000 Subject: [PATCH] formatting --- ChangeLog | 12 +-- docs/CHANGES | 216 +++++++++++++++++++++++++-------------------------- 2 files changed, 112 insertions(+), 116 deletions(-) diff --git a/ChangeLog b/ChangeLog index 30078a39e..146553401 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,12 +1,14 @@ 2002-04-15 David Turner - * docs/FTL.txt: formatting + * docs/FTL.txt: Formatting. - * include/freetype/config/ftoption.h: changing the size of the - render pool to 16Kb (instead of 32Kb). - - * docs/CHANGES: preparing the 2.1.0 release + * include/freetype/config/ftoption.h: Reduce the size of the + render pool from 32kByte to 16kByte. + * src/pcf/pcfread.c (pcf_seek_to_table_type): Remove compiler + warning. + + * docs/CHANGES: Preparing 2.1.0 release. 2002-04-13 Werner LEMBERG diff --git a/docs/CHANGES b/docs/CHANGES index bcc9d7390..3fc0b6b3a 100644 --- a/docs/CHANGES +++ b/docs/CHANGES @@ -3,152 +3,146 @@ LATEST CHANGES BETWEEN 2.1.0 and 2.0.9 I. IMPORTANT BUG FIXES - The TrueType bytecode interpreter has been fixed to produce - _exactly_ the same output as FreeType 1.x. Previous differences + _exactly_ the same output as FreeType 1.x. Previous differences were due to slightly distinct fixed-point computation routines used to perform dot products and vector length measurements. - + It seems that native TrueType hinting is _extremely_ sensitive - to rounding errors. The required vector computation routines have + to rounding errors. The required vector computation routines have been optimized and placed within the "ttinterp.c" file. II. NEW FEATURES - - The 'configure' script used on Unix systems has been modified to - check that GNU Make is being used to build the library. If not, + - The `configure' script used on Unix systems has been modified to + check that GNU Make is being used to build the library. Otherwise, it will display a message proposing to use the GNUMAKE environment - variable to name it.. - - The Unix-specific file README.UNX has been modified accordingly + variable to name it. + + The Unix-specific file README.UNX has been modified accordingly. + - III. MISCELLANEOUS - - The FreeType License in 'docs/FTL.txt' has been updated to include - a proposed preffered disclaimer. If you're using FreeType in your - products, you're encouraged (but not mandated) to use the following + - The FreeType License in `docs/FTL.txt' has been updated to include + a proposed preferred disclaimer. If you are using FreeType in your + products, you are encouraged (but not mandated) to use the following text in your documentation: - - """ - Portions of this software are copyright © 1996-2002 The FreeType - Project (www.freetype.org). All rights reserved. + + """ + Portions of this software are copyright © 1996-2002 The FreeType + Project (www.freetype.org). All rights reserved. """ + - The default size of the render pool has been reduced to 16kByte. + This shouldn't result in any noticeable performance penalty, unless + you are using the engine as-is to render very large and complex + glyphs. - - The default size of the render pool has been reduced to 16 Kb. This - shouldn't result in any noticeable performance penalty, unless you're - using the engine as-is to render very large and complex glyphs.. + - The FreeType 2 redesign has begun. More information can be found + at this URL: - - - The FreeType 2 Re-Design has begun. More information can be found - at the following web address: - http://www.freetype.org/freetype2/redesign.html - + The following internal changes have been performed within the sources of this release: - - - many internal types have been renamed to increase consistency. - the following should be true, except for public types: - - * all structure types have a name ending in "Rec" (short for - 'record'). - - * a pointer-to-structure type has the same name than the + + - Many internal types have been renamed to increase consistency. + The following should be true, except for public types: + + * All structure types have a name ending in "Rec" (short for + `record'). + + * A pointer-to-structure type has the same name as the structure, _without_ the "Rec" suffix. - - for example: - - typedef struct FooRec_ - { - .... - - } FooRec, *Foo; - - - many internal macros have been renamed to increase consistency. - the following should be true: - - * all macros have a name beginning in "FT_". This required - a few changes like: - - ALLOC => FT_ALLOC - FREE => FT_FREE - REALLOC => FT_REALLOC - - - * all macro are completely UPPERCASE. This required a few + + Example: + + typedef struct FooRec_ + { + ... + + } FooRec, *Foo; + + - Many internal macros have been renamed to increase consistency. + The following should be true: + + * All macros have a name beginning with "FT_". This required + a few changes like + + ALLOC => FT_ALLOC + FREE => FT_FREE + REALLOC => FT_REALLOC + + * All macros are completely UPPERCASE. This required a few changes like: - - READ_Short => FT_READ_SHORT - NEXT_Short => FT_NEXT_SHORT - GET_ULongLE => FT_GET_ULONG_LE - MEM_Set => FT_MEM_SET - MEM_Copy => FT_MEM_COPY - etc.. - - * whenever possible, all macro names follow the FT__ - pattern. For example: - - ACCESS_Frame => FT_FRAME_ENTER - FORGET_Frame => FT_FRAME_EXIT - EXTRACT_Frame => FT_FRAME_EXTRACT - RELEASE_Frame => FT_FRAME_RELEASE - - FILE_Pos => FT_STREAM_POS - FILE_Seek => FT_STREAM_SEEK - FILE_Read => FT_STREAM_READ - FILE_ReadAt => FT_STREAM_READ_AT - READ_Fields => FT_STREAM_READ_FIELDS + READ_Short => FT_READ_SHORT + NEXT_Short => FT_NEXT_SHORT + GET_ULongLE => FT_GET_ULONG_LE + MEM_Set => FT_MEM_SET + MEM_Copy => FT_MEM_COPY + etc. - - many internal functions have been renamed to follow the - FT__ pattern. For example: - - FT_Seek_Stream => FT_Stream_Seek - FT_Read_Stream_At => FT_Stream_ReadAt - FT_Done_Stream => FT_Stream_Close - FT_New_Stream => FT_Stream_Open - FT_New_Memory_Stream => FT_Stream_OpenMemory - FT_Extract_Frame => FT_Stream_ExtractFrame + * Whenever possible, all macro names follow the + FT__ pattern. For example - note that method names do not contain "_". - + ACCESS_Frame => FT_FRAME_ENTER + FORGET_Frame => FT_FRAME_EXIT + EXTRACT_Frame => FT_FRAME_EXTRACT + RELEASE_Frame => FT_FRAME_RELEASE - - the FT_ALLOC_ARRAY and FT_REALLOC_ARRAY have been removed and - are now replaced by FT_NEW_ARRAY and FT_RENEW_ARRAY which do - not take a type as the fourth argument. Instead, the array - element type size is computed automatically from the type - of the target pointer used. - + FILE_Pos => FT_STREAM_POS + FILE_Seek => FT_STREAM_SEEK + FILE_Read => FT_STREAM_READ + FILE_ReadAt => FT_STREAM_READ_AT + READ_Fields => FT_STREAM_READ_FIELDS - - a new object class, named FT_CMap has been introduced. These - internal objects are used to model character maps. This eases - the support of additional charmap types within the engine + - Many internal functions have been renamed to follow the + FT__ pattern. For example: + FT_Seek_Stream => FT_Stream_Seek + FT_Read_Stream_At => FT_Stream_ReadAt + FT_Done_Stream => FT_Stream_Close + FT_New_Stream => FT_Stream_Open + FT_New_Memory_Stream => FT_Stream_OpenMemory + FT_Extract_Frame => FT_Stream_ExtractFrame - - a new configuration file named "ftstdlib.h" has been added - to 'include/freetype/config'. It is used to define aliases + Note that method names do not contain "_". + + - The FT_ALLOC_ARRAY and FT_REALLOC_ARRAY have been replaced + with FT_NEW_ARRAY and FT_RENEW_ARRAY which do not take a type + as the fourth argument. Instead, the array element type size + is computed automatically from the type of the target pointer + used. + + - A new object class, FT_CMap, has been introduced. These + internal objects are used to model character maps. This eases + the support of additional charmap types within the engine. + + - A new configuration file named "ftstdlib.h" has been added + to `include/freetype/config'. It is used to define aliases for _every_ routine of the ISO C library that the font engine - uses. Each aliases has a "ft_" prefix (e.g. "ft_strlen" is an + uses. Each aliases has a "ft_" prefix (e.g. "ft_strlen" is an alias for "strlen"). - - this is used to ease the porting of FT2 to exotic runtime + + This is used to ease the porting of FreeType 2 to exotic runtime environments where the ISO C Library isn't available (e.g. XFree86 extension modules). - - More details are available in the "ChangeLog" file. +============================================================================ + LATEST CHANGES BETWEEN 2.0.9 and 2.0.8 I. IMPORTANT BUG FIXES - + - Certain fonts like "foxjump.ttf" contain broken name tables with invalid entries and wild offsets. This caused FreeType to crash when trying to load them. - + The SFNT `name' table loader has been fixed to be able to support these strange fonts. @@ -165,7 +159,7 @@ LATEST CHANGES BETWEEN 2.0.9 and 2.0.8 - A bug in the Postscript hinter has been found and fixed, removing un-even stem widths at small pixel sizes (like 14-17). - + This improves the quality of a certain number of Postscript fonts. @@ -179,18 +173,18 @@ LATEST CHANGES BETWEEN 2.0.9 and 2.0.8 - Two new APIs have been added: `FT_Get_First_Char' and `FT_Get_Next_Char'. - + Together, these can be used to iterate efficiently over the currently selected charmap of a given face. Read the API reference for more details. III. MISCELLANEOUS - + - The FreeType sources are under heavy internal re-factoring. As a consequence, we have created a branch named "STABLE" on the CVS to hold all future releases/fixes in the 2.0.x family. - + The HEAD branch now contains the re-factored sources and shouldn't be used for testing or packaging new releases. In case you would like to access the 2.0.9 sources from our CVS repository, use the tag @@ -202,20 +196,20 @@ LATEST CHANGES BETWEEN 2.0.9 and 2.0.8 LATEST CHANGES BETWEEN 2.0.8 and 2.0.7 I. IMPORTANT BUG FIXES - + - There was a small but nasty bug in "freetype-config.in" which caused the "freetype-config" script to fail on Unix. - + This didn't prevent the installation of the library or even its execution, but caused problems when trying to compile many Unix packages that depend on it. - + - Some TrueType or OpenType fonts embedded in PDF documents do not have a 'cmap', 'post' and 'name' as is required by the specification. FreeType no longer refuses to load such fonts. - various fixes to the PCF font driver - + ============================================================================