1 This file describes various problems that have been encountered in |
|
2 compiling, installing and running FreeType 2. Suggestions for |
|
3 additions or other improvements to this file are welcome. |
|
4 |
|
5 ---------------------------------------------------------------------- |
|
6 |
|
7 Running Problems |
|
8 ================ |
|
9 |
|
10 |
|
11 * Some Type 1, Multiple Masters, and CID-keyed PostScript fonts aren't |
|
12 handled correctly. |
|
13 |
|
14 ----- |
|
15 |
|
16 Of course, there might be bugs in FreeType, but some fonts based on |
|
17 the PostScript format can't be handled indeed. The reason is that |
|
18 FreeType doesn't contain a full PostScript interpreter but applies |
|
19 pattern matching instead. In case a font doesn't follow the standard |
|
20 structure of the given font format, FreeType fails. A typical example |
|
21 is Adobe's `Optima' font family which contains extra code to switch |
|
22 between low and high resolution versions of the glyphs. |
|
23 |
|
24 It might be possible to patch FreeType in some situations, though. |
|
25 Please report failing fonts so that we investigate the problem and set |
|
26 up a list of such problematic fonts. |
|
27 |
|
28 |
|
29 * Why do identical FreeType versions render differently on different |
|
30 platforms? |
|
31 |
|
32 ----- |
|
33 |
|
34 Different distributions compile FreeType with different options. The |
|
35 developer version of a distribution's FreeType package, which is |
|
36 needed to compile your program against FreeType, includes the file |
|
37 ftoption.h. Compare each platform's copy of ftoption.h to find the |
|
38 differences. |
|
39 |
|
40 |
|
41 ---------------------------------------------------------------------- |
|
42 |
|
43 |
|
44 Compilation Problems |
|
45 ==================== |
|
46 |
|
47 |
|
48 * I get an `internal compilation error' (ICE) while compiling FreeType |
|
49 2.2.1 with Intel C++. |
|
50 |
|
51 This has been reported for the following compiler version: |
|
52 |
|
53 Intel(R) C++ Compiler for 32-bit applications, |
|
54 Version 9.0 Build 20050430Z Package ID: W_CC_P_9.0.019 |
|
55 |
|
56 ----- |
|
57 |
|
58 The best solution is to update the compiler to version |
|
59 |
|
60 Intel(R) C++ Compiler for 32-bit applications, |
|
61 Version 9.1 Build 20060323Z Package ID: W_CC_P_9.1.022 |
|
62 |
|
63 or newer. If this isn't feasible, apply the following patch. |
|
64 |
|
65 |
|
66 --- src/cache/ftcbasic.c 20 Mar 2006 12:10:24 -0000 1.20 |
|
67 +++ src/cache/ftcbasic.c.patched 15 May 2006 02:51:02 -0000 |
|
68 @@ -252,7 +252,7 @@ |
|
69 */ |
|
70 |
|
71 FT_CALLBACK_TABLE_DEF |
|
72 - const FTC_IFamilyClassRec ftc_basic_image_family_class = |
|
73 + FTC_IFamilyClassRec ftc_basic_image_family_class = |
|
74 { |
|
75 { |
|
76 sizeof ( FTC_BasicFamilyRec ), |
|
77 @@ -266,7 +266,7 @@ |
|
78 |
|
79 |
|
80 FT_CALLBACK_TABLE_DEF |
|
81 - const FTC_GCacheClassRec ftc_basic_image_cache_class = |
|
82 + FTC_GCacheClassRec ftc_basic_image_cache_class = |
|
83 { |
|
84 { |
|
85 ftc_inode_new, |
|
86 |
|
87 |
|
88 ---------------------------------------------------------------------- |
|
89 |
|
90 --- end of PROBLEMS --- |
|