Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=891457
--- Comment #47 from Hin-Tak Leung htl10@users.sourceforge.net --- The bottom line of the issue is that cairo used freetype in an unanticipated way - until this report -, and the anticipated usage - i.e. usage exercised by ft-demos (ftview/ftdump) is rarely broken.
But then cairo is used by fontconfig and in turn used by gtk so the only sensible way to test fixes is to put freetype out system-wise and see what breaks. gnome terminal broken was unexpected - OTOH, the screenshot shown was the "nicer" brokenness: the nastier brokenness - my first hand experiences - was when the whole window of the web-browser or that of the terminal stopped refreshing and went blank just because either of them had trouble showing a small portion of its window, which involves some texts in bold.
usage under ftview was only broken in the middle of trying to fix usage under cairo.
I am just think what is a good test/validation plan - generally this involves confirming reported issues are fixed without causing serious regressions; "confirming reported issues are fixed" is easy, but considering how widely cairo and freetype are used, and that the freetype's demos (ftview in particular) does not exercise the part of freetype in the way cairo uses it, trying to confirm proposed patch does not cause regressions on dependent software etc - which in this case means any and every GUI-based application which have some texts displayed - is hard.
(FWIW, I have the patched freetype 2.4.11 system-wide, both 32-bit & 64-bit, just to make sure nothing breaks)