<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - cairo quartz font broken in ios 8" href="https://bugs.freedesktop.org/show_bug.cgi?id=84324#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - cairo quartz font broken in ios 8" href="https://bugs.freedesktop.org/show_bug.cgi?id=84324">bug 84324</a> from <a class="email" href="mailto:freedesktop@behdad.org" title="Behdad Esfahbod <freedesktop@behdad.org>"> Behdad Esfahbod</a> <pre>(In reply to Andrea Canciani from <a href="show_bug.cgi?id=84324#c2">comment #2</a>) > (In reply to Behdad Esfahbod from <a href="show_bug.cgi?id=84324#c1">comment #1</a>) > > Looks good to me. Anyone can commit this please? > > I raised some concerns about the patch in the discussion on the mailing list. > Are we ok with dropping support for 10.4? (This would also enable some more > cleanup in quartz, but at the very least we should mention it) I wouldn't mind if we don't support 10.5 or 10.6 either. 10.4 is definitely a no-brainer to me. > Should we go for a CoreText font backend? Not quite sure. Only if we have to. Remove the old ATSU stuff. Start adding CoreText when it makes sense. Right now the backend does without CoreText because what we need is very simple to do with CGFont (scale by em-size). This works because OS X almost fully supports subpixel-positioned text, so there's little hinting to worry about. > For a handle to the thread in the mailing list, see > <a href="http://lists.cairographics.org/archives/cairo/2014-July/025348.html">http://lists.cairographics.org/archives/cairo/2014-July/025348.html</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>