Commit 32b534612db3e6fdb978135cf4a7a86b76c9c425
2002-02-01T01:20:11
Formatting.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111
diff --git a/ChangeLog b/ChangeLog
index 634da05..ec87317 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,8 +1,7 @@
2002-01-31 David Turner <david@freetype.org>
- * README, README.UNX, docs/CHANGES: updating documentation for the
- 2.0.7 release
-
+ * README, README.UNX, docs/CHANGES: Updating documentation for the
+ 2.0.7 release.
2002-01-30 David Turner <david@freetype.org>
diff --git a/docs/CHANGES b/docs/CHANGES
index 7b3a16d..cb2117d 100644
--- a/docs/CHANGES
+++ b/docs/CHANGES
@@ -2,42 +2,41 @@ LATEST CHANGES BETWEEN 2.0.7 and 2.0.6
I. IMPORTANT BUG FIXES
- - Fixed two bugs in the Type 1 font driver. The first one resulted in a
- memory leak in subtle cases. The other one caused FreeType to crash when
- trying to load ".gsf" files (Ghostscript so-called Postscript fonts)
+ - Fixed two bugs in the Type 1 font driver. The first one resulted in a
+ memory leak in subtle cases. The other one caused FreeType to crash
+ when trying to load ".gsf" files (Ghostscript so-called Postscript
+ fonts).
- (this made _many_ KDE application crash on certain systems. FreeType
+ (This made _many_ KDE applications crash on certain systems. FreeType
_is_ becoming a critical system component on Linux :-)
+ - Fixed a memory leak in the CFF font driver.
- - Fixed a memory leak in the CFF font driver
-
- - Fixed a memory leak in the PCF font driver
+ - Fixed a memory leak in the PCF font driver.
- Fixed the Visual C++ project file "builds/win32/visualc/freetype.dsp"
since it didn't include the Postscript hinter component, causing
- errors at build time..
+ errors at build time.
- Fixed a small rendering bug in the anti-aliased renderer that only
- occured when tryong to draw thin (less than 1 pixel) strokes..
-
- - Fixed "builds/unix/freetype2.a4" which is used to generate
- a valid "freetype2.m4" for Autoconf use
+ occurred when trying to draw thin (less than 1 pixel) strokes.
+
+ - Fixed "builds/unix/freetype2.a4" which is used to generate a valid
+ "freetype2.m4" for use with autoconf.
- - Fixed the OpenVMS Makefiles
+ - Fixed the OpenVMS Makefiles.
II. MISCELLANEOUS
- - added "configure" and "install" scripts to the top-level directory.
- a GNU-style installation is thus now easily possible with
-
+ - Added "configure" and "install" scripts to the top-level directory.
+ A GNU-style installation is thus now easily possible with
+
./configure <options>
make
make install
-
============================================================================
LATEST CHANGES BETWEEN 2.0.6 and 2.0.5
@@ -109,7 +108,7 @@ LATEST CHANGES BETWEEN 2.0.6 and 2.0.5
run any program using FreeType. When the library is exited, a summary
of memory footprints and possible leaks will be displayed.
- This works transparently with _any_ program that uses FreeType.
+ This works transparently with _any_ program that uses FreeType.
However, you will need a lot of memory to use this (allocated blocks
are never released to the heap to detect double deletes easily).
@@ -117,20 +116,20 @@ LATEST CHANGES BETWEEN 2.0.6 and 2.0.5
III. MISCELLANEOUS
- We are aware of subtle differences between the output of FreeType
- versions 1 and 2 when it comes to monochrome TrueType-hinted glyphs.
+ versions 1 and 2 when it comes to monochrome TrueType-hinted glyphs.
These are most probably due to small differences in the monochrome
rasterizers and will be worked out in an upcoming release.
- We have decided to fork the sources in a "stable" branch, and an
"unstable" one, since FreeType is becoming a critical component of
many Unix systems.
-
+
The next bug-fix releases of the library will be named 2.0.7, 2.0.8,
etc., while the "2.1" branch will contain a version of the sources
where we will start major reworking of the library's internals, in
order to produce FreeType 2.2.0 (or even 3.0) in a more distant
future.
-
+
We also hope that this scheme will allow much more frequent releases
than in the past.