Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / freetype / 80b8d77024768b6cc5921173d963c01207818106 / . / docs / BUGS
blob: edcdb711dc509656e0be06a3ae52a3c28aa494be [file] [log] [blame]
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]1List of known FreeType 2 Bugs
2-----------------------------
3
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]4"Identifier" is a string to uniquely identify the bug. A more detailed
5description of the bug is found below the table of opened bugs.
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]6
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]7"Date" is the date when the bug was first reported or entered in this
8document. Dates are in _European_ format, i.e day/month/year.
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]9
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]10"Opened By" is the name of the person who first spotted the bug. Note that
11we can use abbreviations here, like:
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]12
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]13 "David" for David Turner
14 "Werner" for Werner Lemberg
15 etc.
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]16
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]17"Reproduceable" indicates whether the bug could be reproduced by the
18development team or not (it can be specific to a given platform), whether it
19always happens, or only sporadically, etc.
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]20
21
22
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]23I. Opened bugs
24==============
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]25
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]26
27Identifier Date Opened by Reproduceable
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]28------------------------------------------------------------------------------
29NO-CID-CMAPS 13-09-2001 David always
30AUTOHINT-NO-SBITS 13-09-2001 David always
31BAD-TT-RENDERING 12-09-2001 Paul Pedriana ?
32BAD-THIN-LINES 13-09-2001 David ?
David Turnerb3ba40d2001-10-07 13:30:26 +0000[diff] [blame]33NOT-WINDOWS-METRICS 07-10-2001 David always
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]34
35--------------------END-OF-OPENED-BUGS-TABLE----------------------------------
36
37
38
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]39II. Table of closed bugs
40========================
41
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]42
43Identifier Date Closed by Closure date
44------------------------------------------------------------------------------
45BAD-TTNAMEID.H 12-09-2001 Antoine N/A
46
47
48--------------------END-OF-CLOSED-BUGS-TABLE----------------------------------
49
50
51
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]52III. Bug descriptions
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]53=====================
54
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]55
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]56NO-CID-CMAPS
57
58 Not exactly a bug, but the CFF font driver doesn't build a Unicode charmap
59 from the contents of font files, which prevents efficiently using fonts in
60 this format.
61
62
63BAD-TTNAMEID.H
64
65 The file "ttnameid.h" contains various constant macro definitions
66 corresponding to important values defined by the TrueType specification.
67
68 Joe Man <trmetal@yahoo.com.hk> reports that:
69
70 According to the information from TrueType v1.66:
71
72 Platform ID = 3 (Microsoft)
73 the Encoding ID of GB2312 = 4
74 the Encoding ID of big5 = 3
75
76 However, I have found that in ttnameid.h:
77
78 TT_MS_ID_GB2312 = 3
79 TT_MS_ID_BIG_5 = 4
80
81 Which one is correct?
82
83 Antoine replied that this was a bug in the TT 1.66 specification, and that
84 FreeType followed the most recent TrueType/OpenType specification here!
85
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]86
87AUTOHINT-SBITS
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]88
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]89 When trying to load a glyph, with the auto-hinter activated (i.e., when
90 using FT_LOAD_FORCE_AUTOHINT, or when the font driver doesn't provide its
91 own hinter), embedded bitmaps are _never_ loaded, unlike the default
92 behaviour described by the API specification.
93
94 This seems to be a bug in FT_Load_Glyph(), but there is no way to solve it
95 efficiently without making a few important internal changes to the
96 library's design (more importantly, to the font driver interface).
97
98
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]99BAD-TT-RENDERING
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]100
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]101 According to Paul Pedriana <PPedriana@maxis.com>, there is a rather
102 important difference between the rendering of TrueType-hinted glyphs of
103 current FT2 and old betas.
104
105 Tests and comparisons show a _major_ discrepancy of monochrome truetype
106 bytecode-hinted glyphs! Something seems to be really broken here!
David Turner21939452001-10-05 14:23:03 +0000[diff] [blame]107
108
109BAD-THIN-LINES
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]110
111 It seems that the anti-aliased renderer in FreeType has problems rendering
112 extremely thin straight lines correctly, at least when using the
113 FT_Outline_Render() function.
David Turnerb3ba40d2001-10-07 13:30:26 +0000[diff] [blame]114
115
116NOT-WINDOWS-METRICS
Werner Lemberg80b8d772001-10-10 19:56:42 +0000[diff] [blame^]117
118 FreeType doesn't always return the same metrics as Windows for ascender,
119 descender, and text height, depending on character pixel sizes. A lot of
120 testing on Windows is needed to debug this properly. It might be due to a
121 rounding bug when computing the "x_scale" and "y_scale" values.
122
123
124=== end of file ===