Hi, I believe in fact that this problem is a bug in libfreetype. You can see my analysis, such as it is, at <https://bugzilla.ubuntu.com/show_bug.cgi?id=11695>; the executive summary is that rebuilding libfreetype not to use the bytecode interpreter causes this rendering problem to go away.
Should this bug be reassigned to freetype? (and maybe go to that upstream?) Cheers, Christophe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
