summaryrefslogtreecommitdiff
path: root/docs/CHANGES
diff options
context:
space:
mode:
authorWerner Lemberg <wl@gnu.org>2015-08-08 08:39:45 +0200
committerWerner Lemberg <wl@gnu.org>2015-08-08 08:39:45 +0200
commitbd75a517dcf87b620e8dd7fcd07992b881f0e234 (patch)
treee86c40f0e9570af4ee2e96a537f00dccbb7e9421 /docs/CHANGES
parente5f4469359560913da8a87cf4831e3e5dee30f93 (diff)
downloadfreetype2-bd75a517dcf87b620e8dd7fcd07992b881f0e234.tar.gz
[type42] Fix glyph access.
This is a severe bug: We've missed one level of indirection, as described in the Type 42 specification. As a result, ftview sometimes showed incorrect glyphs for given glyph names, and even displayed `error 0x0006' (invalid argument!) in case the number of glyph indices differed between the Type 42 font and the embedded TTF. Apparently, noone ever noticed it; this shows how much Type 42 fonts are in use... * src/type42/t42objs.c (T42_GlyphSlot_Load): Map Type 42 glyph index to embedded TTF's glyph index.
Diffstat (limited to 'docs/CHANGES')
-rw-r--r--docs/CHANGES13
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/CHANGES b/docs/CHANGES
index 113fbdf1a..022e6b4e7 100644
--- a/docs/CHANGES
+++ b/docs/CHANGES
@@ -8,6 +8,10 @@ CHANGES BETWEEN 2.6 and 2.6.1
you are using CFFs; otherwise you get cropped glyphs with GUI
interfaces like GTK or Qt.
+ - Accessing Type 42 fonts returned incorrect results if the glyph
+ order of the embedded TrueType font differs from the glyph order
+ of the Type 42 charstrings table.
+
II. IMPORTANT CHANGES
@@ -30,6 +34,15 @@ CHANGES BETWEEN 2.6 and 2.6.1
don't need any change to the source code.
+ III. MISCELLANEOUS
+
+ - The auto-hinter's Arabic script support has been enhanced.
+
+ - The TrueType bytecode interpreter now runs slightly faster.
+
+ - Improved support for builds with cmake.
+
+
======================================================================
CHANGES BETWEEN 2.5.5 and 2.6