1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/modules/freetype2/docs/PROBLEMS Wed Dec 31 06:09:35 2014 +0100
1.3 @@ -0,0 +1,90 @@
1.4 +This file describes various problems that have been encountered in
1.5 +compiling, installing and running FreeType 2. Suggestions for
1.6 +additions or other improvements to this file are welcome.
1.7 +
1.8 +----------------------------------------------------------------------
1.9 +
1.10 +Running Problems
1.11 +================
1.12 +
1.13 +
1.14 +* Some Type 1, Multiple Masters, and CID-keyed PostScript fonts aren't
1.15 + handled correctly.
1.16 +
1.17 +-----
1.18 +
1.19 +Of course, there might be bugs in FreeType, but some fonts based on
1.20 +the PostScript format can't be handled indeed. The reason is that
1.21 +FreeType doesn't contain a full PostScript interpreter but applies
1.22 +pattern matching instead. In case a font doesn't follow the standard
1.23 +structure of the given font format, FreeType fails. A typical example
1.24 +is Adobe's `Optima' font family which contains extra code to switch
1.25 +between low and high resolution versions of the glyphs.
1.26 +
1.27 +It might be possible to patch FreeType in some situations, though.
1.28 +Please report failing fonts so that we investigate the problem and set
1.29 +up a list of such problematic fonts.
1.30 +
1.31 +
1.32 +* Why do identical FreeType versions render differently on different
1.33 + platforms?
1.34 +
1.35 +-----
1.36 +
1.37 +Different distributions compile FreeType with different options. The
1.38 +developer version of a distribution's FreeType package, which is
1.39 +needed to compile your program against FreeType, includes the file
1.40 +ftoption.h. Compare each platform's copy of ftoption.h to find the
1.41 +differences.
1.42 +
1.43 +
1.44 +----------------------------------------------------------------------
1.45 +
1.46 +
1.47 +Compilation Problems
1.48 +====================
1.49 +
1.50 +
1.51 +* I get an `internal compilation error' (ICE) while compiling FreeType
1.52 + 2.2.1 with Intel C++.
1.53 +
1.54 + This has been reported for the following compiler version:
1.55 +
1.56 + Intel(R) C++ Compiler for 32-bit applications,
1.57 + Version 9.0 Build 20050430Z Package ID: W_CC_P_9.0.019
1.58 +
1.59 +-----
1.60 +
1.61 +The best solution is to update the compiler to version
1.62 +
1.63 + Intel(R) C++ Compiler for 32-bit applications,
1.64 + Version 9.1 Build 20060323Z Package ID: W_CC_P_9.1.022
1.65 +
1.66 +or newer. If this isn't feasible, apply the following patch.
1.67 +
1.68 +
1.69 +--- src/cache/ftcbasic.c 20 Mar 2006 12:10:24 -0000 1.20
1.70 ++++ src/cache/ftcbasic.c.patched 15 May 2006 02:51:02 -0000
1.71 +@@ -252,7 +252,7 @@
1.72 + */
1.73 +
1.74 + FT_CALLBACK_TABLE_DEF
1.75 +- const FTC_IFamilyClassRec ftc_basic_image_family_class =
1.76 ++ FTC_IFamilyClassRec ftc_basic_image_family_class =
1.77 + {
1.78 + {
1.79 + sizeof ( FTC_BasicFamilyRec ),
1.80 +@@ -266,7 +266,7 @@
1.81 +
1.82 +
1.83 + FT_CALLBACK_TABLE_DEF
1.84 +- const FTC_GCacheClassRec ftc_basic_image_cache_class =
1.85 ++ FTC_GCacheClassRec ftc_basic_image_cache_class =
1.86 + {
1.87 + {
1.88 + ftc_inode_new,
1.89 +
1.90 +
1.91 +----------------------------------------------------------------------
1.92 +
1.93 +--- end of PROBLEMS ---
