Re: XFT fonts

Mats Lidell writes: A lot. There's something wrong in the Xft algorithms for computing the extent of a glyph, so that Xft often leaves turds on screen. This is definitely in the font rendering engine (perhaps at a lower level than Xft), not in XEmacs, because I've seen the opposite kind of defect in Mozilla (apparently they add a pixel or two to the given extent, because redisplay blots out one pixel from the top of the next line). I've tried adding a pixel but it didn't give very satisfactory results, and didn't even manage to get rid of all turds. So non-trivial work needs to be done on redisplay algorithms to work around this problem. Menus and customize don't respect fontconfig-style font names at all. I've done some work on this (in lisp/fontconfig.el), but not enough to actually get those subsystems working. Optional (but very important IMHO) is to recognize, parse, and appropriately translate the three major dialects of font name (fontconfig, Windows, XLFD -- maybe Mac is a fourth?) to the appropriate dialect expected by the XEmacs instance. Some widgets aren't yet Muleized (tabs, progress gauge), so you get mojibake for non-ASCII characters (I forget whether Latin-1 is mojibake back I think so). Strictly speaking this isn't part of "Xft", but it's closely related. As to how much work this actually includes, neither Aidan, nor I, nor Mike (the strongest advocate of Xft on the board), nor the original coders (some Russian guy and two of Mike's students) were willing to do it. I think that level of avoidance should provide a clue. :) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta