On Tue, 2005-01-04 at 02:20, Bill Kendrick wrote: > I've added a "--nosysfonts" option to Tux Paint > (and corresponding control in Tux Paint Config) which disables any attempts > to load fonts from 'outside' Tux Paint. > > This allows _me_ to keep running the app, until we can figure out what > the problem is with the font grouping code in the latest CVS. ;^)
Try now, without that option. Tux Paint now tries to render both 'A' and 'a' for each font. It then compares them to see if they are the same or not. I commented out the blacklist for now. The X11 "Cursor" font won't render. This seems to be a serious undocumented bug in the library. In fact, no error return is even documented. I had to guess that a NULL might be returned. The library should be supplying an image of a box to represent the failure, as it does with other bad fonts, or it should have a documented error code. Several other fonts return generic box images. I have Tux Paint discard any font that has 'a' match 'A'. Probably I should also discard the font if 'a' matches 'z' or if 'A' matches 'Z'. So, what is your bad font? _______________________________________________ Tuxpaint-dev mailing list [email protected] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
