From d478d5ed5ce7c19a02e11435bcf69e867c6705d9 Mon Sep 17 00:00:00 2001 From: Behdad Esfahbod Date: Fri, 2 Jan 2009 06:48:54 -0500 Subject: [PATCH] [doc] Give a small hint about Twin font Though, the details are not documented yet. I'm not sure how much of it I do want to document. --- src/cairo-toy-font-face.c | 2 +- src/cairo.c | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/src/cairo-toy-font-face.c b/src/cairo-toy-font-face.c index bd1f35735..f51ea251a 100644 --- a/src/cairo-toy-font-face.c +++ b/src/cairo-toy-font-face.c @@ -248,7 +248,7 @@ _cairo_toy_font_face_keys_equal (const void *key_a, * cairo_toy_font_face_get_family(). * * The cairo_select_font_face() function uses this to create font faces. - * See that function for limitations of toy font faces. + * See that function for limitations and other details of toy font faces. * * Return value: a newly created #cairo_font_face_t. Free with * cairo_font_face_destroy() when you are done using it. diff --git a/src/cairo.c b/src/cairo.c index d16adc1d0..4cdf6853c 100644 --- a/src/cairo.c +++ b/src/cairo.c @@ -2619,6 +2619,13 @@ cairo_copy_clip_rectangle_list (cairo_t *cr) * "sans-serif", "cursive", "fantasy", "monospace"), are likely to * work as expected. * + * If @family starts with the string "@cairo:", or if no native font + * backends are compiled in, cairo will use an internal font family. + * The internal font family recognizes many modifiers in the @family + * string, most notably, it recognizes the string "monospace". That is, + * the family name "@cairo:monospace" will use the monospace version of + * the internal font family. + * * For "real" font selection, see the font-backend-specific * font_face_create functions for the font backend you are using. (For * example, if you are using the freetype-based cairo-ft font backend,