* README, docs/CHANGES: updating for the 2.1.3 release
This commit is contained in:
David Turner
parent
b40b8d6eda
commit
df5bc9e1e7
@ -5,6 +5,8 @@
|
||||
to what the auto-hinter does when it comes to stem width computations.
|
||||
However, it produces better results with well-hinted fonts..
|
||||
|
||||
* README, docs/CHANGES: updating for the 2.1.3 release
|
||||
|
||||
2002-08-27 David Turner <david@freetype.org>
|
||||
|
||||
* massive re-formatting changes to many, many source files. I don't
|
||||
|
||||
8
README
8
README
@ -10,7 +10,7 @@
|
||||
is called `libttf'. They are *not* compatible!
|
||||
|
||||
|
||||
FreeType 2.1.2
|
||||
FreeType 2.1.3
|
||||
==============
|
||||
|
||||
Please read the docs/CHANGES file, it contains IMPORTANT
|
||||
@ -22,9 +22,9 @@
|
||||
Note that the FreeType 2 documentation is now available as a
|
||||
separate package from our sites. See:
|
||||
|
||||
ftp://ftp.freetype.org/pub/freetype2/ftdocs-2.1.2.tar.bz2
|
||||
ftp://ftp.freetype.org/pub/freetype2/ftdocs-2.1.2.tar.gz
|
||||
ftp://ftp.freetype.org/pub/freetype2/ftdoc212.zip
|
||||
ftp://ftp.freetype.org/pub/freetype2/ftdocs-2.1.3.tar.bz2
|
||||
ftp://ftp.freetype.org/pub/freetype2/ftdocs-2.1.3.tar.gz
|
||||
ftp://ftp.freetype.org/pub/freetype2/ftdoc213.zip
|
||||
|
||||
|
||||
Reports
|
||||
|
||||
88
docs/CHANGES
88
docs/CHANGES
@ -1,4 +1,82 @@
|
||||
LATEST CHANGES BETWEEN 2.1.1 and 2.1.0
|
||||
LATEST CHANGES BETWEEN 2.1.3 and 2.1.2
|
||||
|
||||
I. IMPORTANT BUG FIXES
|
||||
|
||||
- FT_Vector_Transform had been incorrectly modified in 2.1.2, resulting
|
||||
in incorrect transformations being applied (for example, rotations
|
||||
were processed in opposite angles).
|
||||
|
||||
- the format 8 and 12 TrueType charmap enumeration routines have been
|
||||
fixed (FT_Get_Next_Char returned invalid values)
|
||||
|
||||
- the PFR font driver returned incorrect advance widths when the
|
||||
outline and metrics resolution defined in the font file were
|
||||
different
|
||||
|
||||
- FT_Glyph_To_Bitmap now returnes succesfully when called with
|
||||
a FT_BitmapGlyph argument (it previously returned an error)
|
||||
|
||||
- A bug in the Type 1 loader that prevented valid font bounding
|
||||
boxes to be loaded from multiple master fonts.
|
||||
|
||||
- the SFNT validation code was rewritten. FreeType can now load
|
||||
"broken" fonts that were usable on Windows, but not with previous
|
||||
versions of the library
|
||||
|
||||
- the computation of bearings in the BDF driver has been fixed
|
||||
|
||||
|
||||
II. MISCELLANEOUS
|
||||
|
||||
- the automatic and postscript hinters have both been updated. This
|
||||
results in a relatively important increase of rendering quality
|
||||
since many nasty defaults have been supressed.
|
||||
|
||||
- a new, experimental, support for incremental font loading (i.e.
|
||||
loading of fonts where the glyphs are not in the font file itself,
|
||||
but provided by an external component, like a Postscript interpreter)
|
||||
has been added by Graham Asher. This is still work in progress
|
||||
however.
|
||||
|
||||
- a new, experimental, path stroker has been added. It doesn't suffer
|
||||
from sever rounding errors, and treat bezier arcs directly. Still
|
||||
work in progress
|
||||
|
||||
- the massive re-formatting of sources and internal re-design is still
|
||||
under-way. Many internal functions, constants, and types have been
|
||||
renamed.
|
||||
|
||||
- the "load_flags" parameter of FT_Load_Glyph is now a FT_Int32
|
||||
(instead of just being an FT_Int). This breaks source and binary
|
||||
compatibility for 16bit systems only, while retaining both of them
|
||||
for 32 and 64 bit ones.
|
||||
|
||||
some new flags have been added consequently:
|
||||
|
||||
FT_LOAD_NO_AUTOHINT :: disable the use of the auto-hinter
|
||||
(but not native format hinters)
|
||||
|
||||
FT_LOAD_TARGET_NORMAL :: hint and render for normal anti-aliased
|
||||
displays
|
||||
|
||||
FT_LOAD_TARGET_MONO :: hint and render for 1-bit displays
|
||||
|
||||
FT_LOAD_TARGET_LCD :: hint and render for horizontal RGB or BGR
|
||||
sub-pixel displays (like LCD screens).
|
||||
THIS IS STILL EXPERIMENTAL
|
||||
|
||||
FT_LOAD_TARGET_LCD_V :: same a FT_LOAD_TARGET_LCD, for vertical
|
||||
sub-pixel displays (like rotated LCD screens)
|
||||
THIS IS STILL EXPERIMENTAL
|
||||
|
||||
FT_LOAD_MONOCHROME is still supported, but only affects
|
||||
rendering, not the hinting.
|
||||
|
||||
|
||||
|
||||
========================================================================
|
||||
|
||||
LATEST CHANGES BETWEEN 2.1.2 and 2.1.1
|
||||
|
||||
I. IMPORTANT BUG FIXES
|
||||
|
||||
@ -6,12 +84,12 @@ LATEST CHANGES BETWEEN 2.1.1 and 2.1.0
|
||||
a new face was opened (with the FT_CONFIG_OPTION_USE_CMAPS options
|
||||
enabled), causing many applications to not be able to display text
|
||||
correctly with the 2.1.x releases.
|
||||
|
||||
|
||||
- The PFR driver had a bug in its composite loading code that produces
|
||||
incorrectly placed accents with many fonts.
|
||||
|
||||
|
||||
- The Type42 driver crashed sometimes due to a nasty bug.
|
||||
|
||||
|
||||
- The Type 1 custom encoding charmap didn't handle the case where the
|
||||
first glyph index wasn't 0.
|
||||
|
||||
@ -87,7 +165,7 @@ LATEST CHANGES BETWEEN 2.1.1 and 2.1.0
|
||||
|
||||
- The cache sub-system has been optimized in important ways. Cache hits
|
||||
are now significantly faster. For example, using the CMap cache is
|
||||
about twice faster than calling FT_Get_Char_Index on most platforms.
|
||||
about twice faster than calling FT_Get_Char_Index on most platforms.
|
||||
Similarly, using an SBit cache is about five times faster than loading
|
||||
the bitmaps from a bitmap file, and 300 to 500 times faster than
|
||||
generating them from a scalable format.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user