formatting

This commit is contained in:
Werner Lemberg 2002-04-15 13:37:29 +00:00
parent 39e1b17aa6
commit 4639c4bddb
2 changed files with 112 additions and 116 deletions

View File

@ -1,12 +1,14 @@
2002-04-15 David Turner <david@freetype.org>
* 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).
* include/freetype/config/ftoption.h: Reduce the size of the
render pool from 32kByte to 16kByte.
* docs/CHANGES: preparing the 2.1.0 release
* src/pcf/pcfread.c (pcf_seek_to_table_type): Remove compiler
warning.
* docs/CHANGES: Preparing 2.1.0 release.
2002-04-13 Werner LEMBERG <wl@gnu.org>

View File

@ -14,19 +14,19 @@ LATEST CHANGES BETWEEN 2.1.0 and 2.0.9
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..
variable to name it.
The Unix-specific file README.UNX has been modified accordingly
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:
"""
@ -34,49 +34,47 @@ LATEST CHANGES BETWEEN 2.1.0 and 2.0.9
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 Re-Design has begun. More information can be found
at the following web address:
- The FreeType 2 redesign has begun. More information can be found
at this URL:
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:
- 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').
* All structure types have a name ending in "Rec" (short for
`record').
* a pointer-to-structure type has the same name than the
* A pointer-to-structure type has the same name as the
structure, _without_ the "Rec" suffix.
for example:
Example:
typedef struct FooRec_
{
....
...
} FooRec, *Foo;
- many internal macros have been renamed to increase consistency.
the following should be true:
- 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:
* All macros have a name beginning with "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
* All macros are completely UPPERCASE. This required a few
changes like:
READ_Short => FT_READ_SHORT
@ -84,10 +82,10 @@ LATEST CHANGES BETWEEN 2.1.0 and 2.0.9
GET_ULongLE => FT_GET_ULONG_LE
MEM_Set => FT_MEM_SET
MEM_Copy => FT_MEM_COPY
etc..
etc.
* whenever possible, all macro names follow the FT_<OBJECT>_<METHOD>
pattern. For example:
* Whenever possible, all macro names follow the
FT_<OBJECT>_<METHOD> pattern. For example
ACCESS_Frame => FT_FRAME_ENTER
FORGET_Frame => FT_FRAME_EXIT
@ -100,8 +98,7 @@ LATEST CHANGES BETWEEN 2.1.0 and 2.0.9
FILE_ReadAt => FT_STREAM_READ_AT
READ_Fields => FT_STREAM_READ_FIELDS
- many internal functions have been renamed to follow the
- Many internal functions have been renamed to follow the
FT_<Object>_<Method> pattern. For example:
FT_Seek_Stream => FT_Stream_Seek
@ -111,36 +108,33 @@ LATEST CHANGES BETWEEN 2.1.0 and 2.0.9
FT_New_Memory_Stream => FT_Stream_OpenMemory
FT_Extract_Frame => FT_Stream_ExtractFrame
note that method names do not contain "_".
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.
- 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.
- a new object class, named FT_CMap has been introduced. These
- 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
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
- 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
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