Commit e7d1fb3142b5e79b83a6267e1a838341b05fc154
2011-02-24T20:01:00
* docs/PROBLEMS: Mention rendering differences on different platforms. Suggested and worded by Jason Owen <jason.a.owen@gmail.com>.
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
diff --git a/ChangeLog b/ChangeLog
index 6d15971..b4ca1fa 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,11 @@
2011-02-24 Werner Lemberg <wl@gnu.org>
+ * docs/PROBLEMS: Mention rendering differences on different
+ platforms.
+ Suggested and worded by Jason Owen <jason.a.owen@gmail.com>.
+
+2011-02-24 Werner Lemberg <wl@gnu.org>
+
[autofit] Comment out unused code.
* src/autofit/aflatin.c, src/autofit/aflatin2.c
diff --git a/docs/PROBLEMS b/docs/PROBLEMS
index 9b59896..40bdc35 100644
--- a/docs/PROBLEMS
+++ b/docs/PROBLEMS
@@ -14,7 +14,7 @@ Running Problems
-----
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
@@ -25,6 +25,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.
+
+
----------------------------------------------------------------------