172
175
by documented ./configure options.
177
Collection of problems/issues with new unicode-aware fonts as of 2005-03-21.
178
All these are in the would-be-nice category with some/all taking major effort
180
****************************************************************************
182
I. Font problems associated with plfreetype.c which is called by gd.c which
183
implements the png, gif, or jpeg devices. (These issues were discovered
186
* The default -drvopt smooth=1 option does not work (lots of cmap0 index
187
errors) if there is any user change to cmap0. This problem is triggered
188
if you attempt to run example 2 with -dev png. Andrew Roach thinks he
189
knows a small redesign that will fix it.
191
* There are still problems with vertical alignment of symbols for
192
plfreetype.c. See results from
194
examples/c/x06c -dev png -o test.png
196
where on line 100 the characters move up or down depending on whether they
197
have an ascender, descender or neither. There are similar problems for
200
N.B. This is only a problem for plpoin (example 6) and plsym (example 7),
201
but not a problem for plmtex. So there is probably some issue with the way
202
plhrsh (called by plpoin and plsym) sets up the call to the code in
203
plfreetype.c that is not present for plmtex.
205
* The above problem may be related to the xform setting in plhrsh (plsym.c)
206
which is a kludge. if you define TEST_FOR_MISSING_GLYPHS,
207
it quits working (all the symbols are twisted by 90 deg).
209
* -drvopt 24bit problems. If this option is turned on (and only in this
210
case), Example 9 and 22 second and subsequent pages have rectangular
211
viewports with no box or tick marks. Furthermore, with Example 19 the
212
second and 3rd pages turn black. If you use -bg FFFFFF, you can see the
213
problem is a cmap0 one, somehow 24bit turns the default red colour into
214
black which doesn't show against the normal black background, but which
215
does show against a white background as with -bg FFFFFF.
217
* text clipping does not work (see example 9). There is a clipping method
218
in libgd, but the preferred solution (since it will apply to every device
219
driver that uses plfreetype.c) is to use the libfreetype clipping
220
method which Andrew Ross found in the freetype documentation.
222
* We need to build in fontconfig support into plfreetype.c for truetype
223
fonts. This well-known library by Keith Packard is available for both
224
Linux and windows and should allow truetype font selection by name rather
225
than by filename, and font substitution on both Linux and windows if the
226
requested named font is not available.
228
II. Font problems associated with ps.c and either -dev psc or -dev ps.
230
* Bounding box is still too large for ps.c results. We will need some help
231
from somebody with postscript expertise to get this right.
233
* The overall size of the text is systematically smaller than for Hershey or
236
* ./x06c -dev psc -o test.ps -drvopt hrshsym=0
238
shows that symbols are positioned consistently too high when postscript
239
fonts are used for them (hrshsym=0). The same problem exists for example
240
7 as well. At the same time, the two examples show that text positioning
241
(the labels on the outside of the matrix of symbols) are positioned fine.
243
III. Other font problems/issues.
245
* Both pstex.c and xfig.c currently use EscText so they presumably need some
246
work to utilize the new core unicode font handling.
248
* We should enable additional device drivers for unicode. In particular,
249
our two most heavily used interactive device drivers, xwin and tk, should
250
give some outstanding looking results once they are unicode-enabled.
251
I nominate Maurice to make this happen.... :-)
added
removed
PROBLEMS
