shithub: freetype+ttf2subf

Download patch

ref: e7d1fb3142b5e79b83a6267e1a838341b05fc154
parent: 6c28689691e19ce9cbaa86e59adc339399ce4d9d
author: Werner Lemberg <[email protected]>
date: Thu Feb 24 15:01:00 EST 2011

* docs/PROBLEMS: Mention rendering differences on different
platforms.
Suggested and worded by Jason Owen <[email protected]>.

git/fs: mount .git/fs: mount/attach disallowed
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,11 @@
 2011-02-24  Werner Lemberg  <[email protected]>
 
+	* docs/PROBLEMS: Mention rendering differences on different
+	platforms.
+	Suggested and worded by Jason Owen <[email protected]>.
+
+2011-02-24  Werner Lemberg  <[email protected]>
+
 	[autofit] Comment out unused code.
 
 	* src/autofit/aflatin.c, src/autofit/aflatin2.c
--- a/docs/PROBLEMS
+++ b/docs/PROBLEMS
@@ -14,7 +14,7 @@
 -----
 
 Of course,  there might be  bugs in FreeType,  but some fonts based on
-the  PostScript  format can't  behandled indeed.  The  reason  is that
+the  PostScript  format can't  be handled indeed.  The reason  is that
 FreeType  doesn't contain a full  PostScript  interpreter  but applies
 pattern matching instead.  In case a font doesn't follow the  standard
 structure of the given font format, FreeType fails.  A typical example
@@ -24,6 +24,19 @@
 It might be  possible to patch  FreeType in  some situations,  though.
 Please report failing fonts so that we investigate the problem and set
 up a list of such problematic fonts.
+
+
+* Why do identical FreeType  versions render differently  on different
+  platforms?
+
+-----
+
+Different distributions compile FreeType with different options.   The
+developer  version of  a  distribution's  FreeType  package,  which is
+needed to compile  your program  against FreeType,  includes the  file
+ftoption.h.  Compare  each platform's  copy of ftoption.h to  find the
+differences.
+
 
 ----------------------------------------------------------------------