michael@0: This  file describes various  problems that  have been  encountered in
michael@0: compiling,  installing  and   running  FreeType  2.   Suggestions  for
michael@0: additions or other improvements to this file are welcome.
michael@0: 
michael@0: ----------------------------------------------------------------------
michael@0: 
michael@0: Running Problems
michael@0: ================
michael@0: 
michael@0: 
michael@0: * Some Type 1, Multiple Masters, and CID-keyed PostScript fonts aren't
michael@0:   handled correctly.
michael@0: 
michael@0: -----
michael@0: 
michael@0: Of course,  there might be  bugs in FreeType,  but some fonts based on
michael@0: the  PostScript  format can't  be handled indeed.  The reason  is that
michael@0: FreeType  doesn't contain a full  PostScript  interpreter  but applies
michael@0: pattern matching instead.  In case a font doesn't follow the  standard
michael@0: structure of the given font format, FreeType fails.  A typical example
michael@0: is Adobe's `Optima'  font family which  contains extra code  to switch
michael@0: between low and high resolution versions of the glyphs.
michael@0: 
michael@0: It might be  possible to patch  FreeType in  some situations,  though.
michael@0: Please report failing fonts so that we investigate the problem and set
michael@0: up a list of such problematic fonts.
michael@0: 
michael@0: 
michael@0: * Why do identical FreeType  versions render differently  on different
michael@0:   platforms?
michael@0: 
michael@0: -----
michael@0: 
michael@0: Different distributions compile FreeType with different options.   The
michael@0: developer  version of  a  distribution's  FreeType  package,  which is
michael@0: needed to compile  your program  against FreeType,  includes the  file
michael@0: ftoption.h.  Compare  each platform's  copy of ftoption.h to  find the
michael@0: differences.
michael@0: 
michael@0: 
michael@0: ----------------------------------------------------------------------
michael@0: 
michael@0: 
michael@0: Compilation Problems
michael@0: ====================
michael@0: 
michael@0: 
michael@0: * I get an `internal compilation error' (ICE) while compiling FreeType
michael@0:   2.2.1 with Intel C++.
michael@0: 
michael@0:   This has been reported for the following compiler version:
michael@0: 
michael@0:     Intel(R) C++ Compiler for 32-bit applications,
michael@0:       Version 9.0 Build 20050430Z Package ID: W_CC_P_9.0.019
michael@0: 
michael@0: -----
michael@0: 
michael@0: The best solution is to update the compiler to version
michael@0: 
michael@0:   Intel(R) C++ Compiler for 32-bit applications,
michael@0:     Version 9.1 Build 20060323Z Package ID: W_CC_P_9.1.022
michael@0: 
michael@0: or newer.  If this isn't feasible, apply the following patch.
michael@0: 
michael@0: 
michael@0: --- src/cache/ftcbasic.c 20 Mar 2006 12:10:24 -0000 1.20
michael@0: +++ src/cache/ftcbasic.c.patched 15 May 2006 02:51:02 -0000
michael@0: @@ -252,7 +252,7 @@
michael@0:    */
michael@0: 
michael@0:    FT_CALLBACK_TABLE_DEF
michael@0: -  const FTC_IFamilyClassRec  ftc_basic_image_family_class =
michael@0: +  FTC_IFamilyClassRec  ftc_basic_image_family_class =
michael@0:    {
michael@0:      {
michael@0:        sizeof ( FTC_BasicFamilyRec ),
michael@0: @@ -266,7 +266,7 @@
michael@0: 
michael@0: 
michael@0:    FT_CALLBACK_TABLE_DEF
michael@0: -  const FTC_GCacheClassRec  ftc_basic_image_cache_class =
michael@0: +  FTC_GCacheClassRec  ftc_basic_image_cache_class =
michael@0:    {
michael@0:      {
michael@0:        ftc_inode_new,
michael@0: 
michael@0: 
michael@0: ----------------------------------------------------------------------
michael@0: 
michael@0: --- end of PROBLEMS ---