Michael Fedrowitz <[EMAIL PROTECTED]> writes: > On Sun, 2005-06-12 at 16:39 +0100, Christophe Rhodes wrote: > > 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. > > This doesn't really prove anything.
Well, no, obviously it doesn't /prove/ anything, just as the original bug report didn't prove that it was in fact a bug in Vera -- except that there is a problem in the interaction of Vera and freetype-as-distributed-by-Debian, and that this problem is not present in the interaction of Vera and freetype-not-as-distributed-by-Debian. > It's still just as likely that it's a bug in Vera's hinting, which > while it's generally of very high quality definitely does have a > couple of bugs. I can't estimate these probabilities as accurately as you can. Is it possible to make the freetype people aware of this bug report, nevertheless? If a reassignment isn't the way to do that, maybe a Cc or some similar thing would be? Cheers, Christophe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
