[cairo] Renaming ATSUI font to Quartz font
behdad at behdad.org
Sun Mar 16 16:18:47 PDT 2008
On Sun, 2008-03-16 at 16:24 -0400, Vladimir Vukicevic wrote:
> Here's a patch that renames the current ATSUI font backend to a Quartz
> font backend, in preparation for eventually dropping the ATSUI
> dependancy internally and using CGFont directly.
> This patch makes --
> enable-quartz give you both quartz surface and quartz font support;
> otherwise, I would've needed to use "cairo-quartz-font.h", breaking
> the usual pattern. I also can't think of a reason to compile with
> just one of those -- even if you only use one or the other, it won't
> hurt to have them both available (since they have the exact same
I don't like that part. Just copy from what we do with win32. That is:
CAIRO_BACKEND_ENABLE(win32_font, Microsoft Windows font, win32-font, WIN32_FONT, auto, [
And there are reasons to build without quartz font backend: testing, for
> The font creation function cairo_atsui_font_create_for_atsu_font_id
> was renamed to cairo_quartz_font_create_for_atsu_font_id -- the same
> API entry point can be supported even after the CGFont switch
> internally. Also, CAIRO_FONT_TYPE_ATSUI is now
> CAIRO_FONT_TYPE_QUARTZ. There was some mention of adding two #defines
> for the old names to cairo-obosolete.h -- but I don't see a cairo-
> obsolete.h in the current trunk dev branch. Should I create one?
cairo-deprecated.h that is. Carl and I decided that it would be Ok to
also leave the old symbol in the binary... The main reason for trying
hard to not break anyone's system is the release of pango-1.20.0 just
last week. If it wasn't for that, we didn't have to maintain any
Can you also prepare a patch for Pango please?
> behdad, cworth, does this seem reasonable?
Yes, of course.
> - Vlad
"Those who would give up Essential Liberty to purchase a little
Temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin, 1759
More information about the cairo