RubyGems - pango - Versions diffs - 0.90.5-x86-mingw32 → 0.90.6-x86-mingw32 - Mend

pango 0.90.5-x86-mingw32 → 0.90.6-x86-mingw32

Files changed (1348) hide show

data/vendor/local/share/gtk-doc/html/cairo/bindings-patterns.html DELETED

@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Patterns</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="Cairo: A Vector Graphics Library">
-<link rel="up" href="language-bindings.html" title="Appendix A. Creating a language binding for cairo">
-<link rel="prev" href="bindings-errors.html" title="Error handling">
-<link rel="next" href="bindings-surfaces.html" title="Surfaces">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="bindings-errors.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="language-bindings.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">Cairo: A Vector Graphics Library</th>
-<td><a accesskey="n" href="bindings-surfaces.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="sect1" title="Patterns">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="bindings-patterns"></a>Patterns</h2></div></div></div>
-<p>
-      The cairo C API allows for creating a number of different types
-      of patterns. All of these different types of patterns map to
-      <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-t" title="cairo_pattern_t"><span class="type">cairo_pattern_t</span></a>
-      in C, but in an object oriented language, there should instead
-      be a hierarchy of types. (The functions that should map to
-      constructors or static methods for the various types are listed
-      after the type, methods on that type are listed below. Note that
-      cairo_pattern_create_rgb() and cairo_pattern_create_rgba()
-      should not be overloaded with each other as a SolidPattern()
-      constructor, but should appear as static methods instead.  This
-      is to maintain code clarity by making it clear how the arguments
-      relate to color components.)
-    </p>
-<pre class="programlisting">
-cairo_pattern_t
-      <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-set-matrix" title="cairo_pattern_set_matrix ()"><code class="function">cairo_pattern_set_matrix()</code></a>
-      <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-get-matrix" title="cairo_pattern_get_matrix ()"><code class="function">cairo_pattern_get_matrix()</code></a>
-   cairo_solid_pattern_t (<a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-create-rgb" title="cairo_pattern_create_rgb ()"><code class="function">cairo_pattern_create_rgb()</code></a> and <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-create-rgba" title="cairo_pattern_create_rgba ()"><code class="function">cairo_pattern_create_rgba()</code></a>)
-   cairo_surface_pattern_t (<a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-create-for-surface" title="cairo_pattern_create_for_surface ()"><code class="function">cairo_pattern_create_for_surface()</code></a>)
-         <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-set-extend" title="cairo_pattern_set_extend ()"><code class="function">cairo_pattern_set_extend()</code></a>
-         <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-get-extend" title="cairo_pattern_get_extend ()"><code class="function">cairo_pattern_get_extend()</code></a>
-         <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-set-filter" title="cairo_pattern_set_filter ()"><code class="function">cairo_pattern_set_filter()</code></a>
-         <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-get-filter" title="cairo_pattern_get_filter ()"><code class="function">cairo_pattern_get_filter()</code></a>
-   cairo_gradient_t
-         <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-add-color-stop-rgb" title="cairo_pattern_add_color_stop_rgb ()"><code class="function">cairo_pattern_add_color_stop_rgb()</code></a>
-         <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-add-color-stop-rgba" title="cairo_pattern_add_color_stop_rgba ()"><code class="function">cairo_pattern_add_color_stop_rgba()</code></a>
-      cairo_linear_gradient_t (<a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-create-linear" title="cairo_pattern_create_linear ()"><code class="function">cairo_pattern_create_linear()</code></a>)
-      cairo_radial_gradient_t (<a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-create-radial" title="cairo_pattern_create_radial ()"><code class="function">cairo_pattern_create_radial()</code></a>)
-    </pre>
-<p>
-    </p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/cairo/bindings-return-values.html DELETED

@@ -1,120 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Multiple return values</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="Cairo: A Vector Graphics Library">
-<link rel="up" href="language-bindings.html" title="Appendix A. Creating a language binding for cairo">
-<link rel="prev" href="bindings-memory.html" title="Memory management">
-<link rel="next" href="bindings-overloading.html" title="Overloading and optional arguments">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="bindings-memory.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="language-bindings.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">Cairo: A Vector Graphics Library</th>
-<td><a accesskey="n" href="bindings-overloading.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="sect1" title="Multiple return values">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="bindings-return-values"></a>Multiple return values</h2></div></div></div>
-<p>
-      There are a number of functions in the cairo API that have
-      multiple <em class="firstterm">out parameters</em> or
-      <em class="firstterm">in-out parameters</em>. In some languages
-      these can be translated into multiple return values. In Python,
-      what is:
-    </p>
-<pre class="programlisting">
-cairo_user_to_device (cr, &amp;x, &amp;y);</pre>
-<p>
-      can by mapped to:
-    </p>
-<pre class="programlisting">
-(x, y) = cr.user_to_device (cr, x, y);</pre>
-<p>
-      but many languages don't have provisions for multiple return
-      values, so it is necessary to introduce auxiliary types.
-      Most of the functions that require the auxiliary types
-      require a type that would, in C, look like
-    </p>
-<pre class="programlisting">
-typedef struct _cairo_point cairo_point_t;
-struct _cairo_point {
-    double x;
-    double y;
-}</pre>
-<p>
-      The same type should be used both for functions that use a pair
-      of coordinates as an absolute position, and functions that use
-      a pair of coordinates as a displacement. While an argument could
-      be made that having a separate “distance” type is more correct,
-      it is more likely just to confuse users.
-    </p>
-<pre class="programlisting">
-void
-cairo_user_to_device (cairo_t *cr, double *x, double *y);
-void
-cairo_user_to_device_distance (cairo_t *cr, double *dx, double *dy);
-void
-cairo_device_to_user (cairo_t *cr, double *x, double *y);
-void
-cairo_device_to_user_distance (cairo_t *cr, double *dx, double *dy);
-void
-cairo_matrix_transform_distance (cairo_matrix_t *matrix, double *dx, double *dy);
-void
-cairo_matrix_transform_point (cairo_matrix_t *matrix, double *x, double *y);
-void
-cairo_get_current_point (cairo_t *cr, double *x, double *y);
-    </pre>
-<p>
-      There are also a couple of functions that return four values
-      representing a rectangle. These should be mapped to a
-      “rectangle” type that looks like:
-    </p>
-<pre class="programlisting">
-typedef struct _cairo_rectangle cairo_rectangle_t;
-struct _cairo_rectangle {
-    double x;
-    double y;
-    double width;
-    double height;
-}</pre>
-<p>
-      The C function returns the rectangle as a set of two points to
-      facilitate rounding to integral extents, but this isn't worth
-      adding a “box” type to go along with the more obvious
-      “rectangle” representation.
-    </p>
-<p class="remark"><i><span class="remark">
-      Q: Would it make sense here to define a standard
-      <code class="function">cairo_rectangle_round()</code> method
-      that language bindings should map?
-    </span></i></p>
-<pre class="programlisting">
-void
-cairo_stroke_extents (cairo_t *cr,
-		      double *x1, double *y1,
-		      double *x2, double *y2);
-void
-cairo_fill_extents (cairo_t *cr,
-		    double *x1, double *y1,
-		    double *x2, double *y2);
-    </pre>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/cairo/bindings-streams.html DELETED

@@ -1,92 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Streams and File I/O</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="Cairo: A Vector Graphics Library">
-<link rel="up" href="language-bindings.html" title="Appendix A. Creating a language binding for cairo">
-<link rel="prev" href="bindings-overloading.html" title="Overloading and optional arguments">
-<link rel="next" href="bindings-errors.html" title="Error handling">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="bindings-overloading.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="language-bindings.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">Cairo: A Vector Graphics Library</th>
-<td><a accesskey="n" href="bindings-errors.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="sect1" title="Streams and File I/O">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="bindings-streams"></a>Streams and File I/O</h2></div></div></div>
-<p>
-      Various places in the cairo API deal with reading and writing
-      data, whether from and to files, or to other sources and
-      destinations. In these cases, what is typically provided in the
-      C API is a simple version that just takes a filename, and a
-      complex version that takes a callback function.
-      An example is the PNG handling functions:
-    </p>
-<pre class="programlisting">
-cairo_surface_t *
-cairo_image_surface_create_from_png (const char	*filename);
-cairo_surface_t *
-cairo_image_surface_create_from_png_stream (cairo_read_func_t read_func,
-					    void             *closure);
-cairo_status_t
-cairo_surface_write_to_png (cairo_surface_t	*surface,
-			    const char		*filename);
-cairo_status_t
-cairo_surface_write_to_png_stream (cairo_surface_t	*surface,
-				   cairo_write_func_t	write_func,
-				   void			*closure);</pre>
-<p>
-      The expectation is that the filename version will be mapped
-      literally in the language binding, but the callback version
-      will be mapped to a version that takes a language stream
-      object. For example, in Java, the four functions above
-      might be mapped to:
-    </p>
-<pre class="programlisting">
-static public ImageSurface createFromPNG (String filename) throws IOException;
-static public ImageSurface createFromPNG (InputStream stream) throws IOException;
-public void writeToPNG (String filename) throws IOException;
-public void writeToPNG (OutputStream stream) throws IOException;
-</pre>
-<p>
-      In many cases, it will be better to
-      implement the filename version internally
-      using the stream version, rather than building it on top of the
-      filename version in C. The reason for this is that will
-      naturally give a more standard handling of file errors for
-      the language, as seen in the above Java example, where
-      <code class="methodname">createFromPNG()</code> is marked as raising
-      an exception. Propagating exceptions from inside the callback
-      function to the caller will pose a challenge to the language
-      binding implementor, since an exception must not propagate
-      through the Cairo code. A technique that will be useful in
-      some cases is to catch the exception in the callback,
-      store the exception object inside a structure pointed to by
-      <em class="parameter"><code>closure</code></em>, and then rethrow it once
-      the function returns.
-    </p>
-<p class="remark"><i><span class="remark">
-      I'm not sure how to handle this for
-      <code class="function">cairo_pdf_surface_create_for_callback()</code>.
-      Other than keep a “exception to rethrow” thread-specific
-      variable
-      that is checked after <span class="emphasis"><em>every</em></span> call to a Cairo
-      function.
-    </span></i></p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/cairo/bindings-surfaces.html DELETED

@@ -1,93 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Surfaces</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="Cairo: A Vector Graphics Library">
-<link rel="up" href="language-bindings.html" title="Appendix A. Creating a language binding for cairo">
-<link rel="prev" href="bindings-patterns.html" title="Patterns">
-<link rel="next" href="bindings-fonts.html" title="Fonts">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="bindings-patterns.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="language-bindings.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">Cairo: A Vector Graphics Library</th>
-<td><a accesskey="n" href="bindings-fonts.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="sect1" title="Surfaces">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="bindings-surfaces"></a>Surfaces</h2></div></div></div>
-<p>
-      Like patterns, surfaces, which use only the
-      <a class="link" href="cairo-cairo-surface-t.html#cairo-surface-t" title="cairo_surface_t"><span class="type">cairo_surface_t</span></a>
-      type in the C API should be broken up into a hierarchy of types
-      in a language binding.
-    </p>
-<pre class="programlisting">
-cairo_surface_t
-    cairo_image_surface_t
-    cairo_atsui_surface_t
-    cairo_win32_surface_t
-    cairo_xlib_surface_t
-    cairo_beos_surface_t
-    </pre>
-<p>
-      Unlike patterns, the constructors and methods on these types are
-      clearly named, and can be trivially associated with the
-      appropriate subtype. Many language bindings will want to avoid
-      binding the platform-specific subtypes at all, since the
-      methods on these types are not useful without passing in native
-      C types. Unless there is a language binding for Xlib available,
-      there is no way to represent a XLib <span class="type">Display</span> * in
-      that language.
-    </p>
-<p>
-      This doesn't mean that platform-specific surface types can't
-      be used in a language binding that doesn't bind the constructor.
-      A very common situation is to use a cairo language binding in
-      combination with a binding for a higher level system like
-      the <a class="ulink" href="http://www.gtk.org/" target="_top">GTK+</a> widget
-      toolkit. In such a situation, the higher level toolkit provides
-      ways to get references to platform specific surfaces.
-    </p>
-<p>
-      The <a class="link" href="cairo-cairo-surface-t.html#cairo-surface-set-user-data" title="cairo_surface_set_user_data ()"><code class="function">cairo_surface_set_user_data()</code></a>,
-      and <a class="link" href="cairo-cairo-surface-t.html#cairo-surface-get-user-data" title="cairo_surface_get_user_data ()"><code class="function">cairo_surface_get_user_data()</code></a>
-      methods are provided for use in language bindings, and should
-      not be directly exposed to applications. One example of the use
-      of these functions in a language binding is creating a binding for:
-    </p>
-<pre class="programlisting">
-cairo_surface_t *
-<a class="link" href="cairo-Image-Surfaces.html#cairo-image-surface-create-for-data" title="cairo_image_surface_create_for_data ()"><code class="function">cairo_image_surface_create_for_data</code></a> (unsigned char	       *data,
-				     cairo_format_t		format,
-				     int			width,
-				     int			height,
-				     int			stride);
-</pre>
-<p>
-      The memory block passed in for <em class="parameter"><code>data</code></em> must be
-      kept around until the surface is destroyed, so the language
-      binding must have some way of determining when that happens. The
-      way to do this is to use the <em class="parameter"><code>destroy</code></em>
-      argument to <code class="function">cairo_surface_set_user_data()</code>.
-    </p>
-<p class="remark"><i><span class="remark">
-      Some languages may not have a suitable “pointer to a block of
-      data” type to pass in for <em class="parameter"><code>data</code></em>. And even
-      where a language does have such a type, the user will be
-      frequently able to cause the backing store to be reallocated
-      to a different location or truncated. Should we recommend a
-      standard type name and binding for a buffer object here?
-    </span></i></p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/cairo/cairo-Error-handling.html DELETED

@@ -1,373 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Error handling</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="Cairo: A Vector Graphics Library">
-<link rel="up" href="cairo-support.html" title="Utilities">
-<link rel="prev" href="cairo-cairo-matrix-t.html" title="cairo_matrix_t">
-<link rel="next" href="cairo-Version-Information.html" title="Version Information">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2">
-<tr valign="middle">
-<td><a accesskey="p" href="cairo-cairo-matrix-t.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="cairo-support.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">Cairo: A Vector Graphics Library</th>
-<td><a accesskey="n" href="cairo-Version-Information.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr>
-<tr><td colspan="5" class="shortcuts">
-<a href="#cairo-Error-handling.synopsis" class="shortcut">Top</a>
-                   |
-                  <a href="#cairo-Error-handling.description" class="shortcut">Description</a>
-</td></tr>
-</table>
-<div class="refentry" title="Error handling">
-<a name="cairo-Error-handling"></a><div class="titlepage"></div>
-<div class="refnamediv"><table width="100%"><tr>
-<td valign="top">
-<h2><span class="refentrytitle"><a name="cairo-Error-handling.top_of_page"></a>Error handling</span></h2>
-<p>Error handling — Decoding cairo's status</p>
-</td>
-<td valign="top" align="right"></td>
-</tr></table></div>
-<div class="refsynopsisdiv" title="Synopsis">
-<a name="cairo-Error-handling.synopsis"></a><h2>Synopsis</h2>
-<pre class="synopsis">enum                <a class="link" href="cairo-Error-handling.html#cairo-status-t" title="enum cairo_status_t">cairo_status_t</a>;
-const <span class="returnvalue">char</span> *        <a class="link" href="cairo-Error-handling.html#cairo-status-to-string" title="cairo_status_to_string ()">cairo_status_to_string</a>              (<em class="parameter"><code><a class="link" href="cairo-Error-handling.html#cairo-status-t" title="enum cairo_status_t"><span class="type">cairo_status_t</span></a> status</code></em>);
-<span class="returnvalue">void</span>                <a class="link" href="cairo-Error-handling.html#cairo-debug-reset-static-data" title="cairo_debug_reset_static_data ()">cairo_debug_reset_static_data</a>       (<em class="parameter"><code><span class="type">void</span></code></em>);
-</pre>
-</div>
-<div class="refsect1" title="Description">
-<a name="cairo-Error-handling.description"></a><h2>Description</h2>
-<p>
-Cairo uses a single status type to represent all kinds of errors.  A status
-value of <a class="link" href="cairo-Error-handling.html#CAIRO-STATUS-SUCCESS:CAPS"><code class="literal">CAIRO_STATUS_SUCCESS</code></a> represents no error and has an integer value
-of zero.  All other status values represent an error.
-</p>
-<p>
-Cairo's error handling is designed to be easy to use and safe.  All major
-cairo objects <em class="firstterm">retain</em> an error status internally which
-can be queried anytime by the users using cairo*_status() calls.  In
-the mean time, it is safe to call all cairo functions normally even if the
-underlying object is in an error status.  This means that no error handling
-code is required before or after each individual cairo function call.
-</p>
-</div>
-<div class="refsect1" title="Details">
-<a name="cairo-Error-handling.details"></a><h2>Details</h2>
-<div class="refsect2" title="enum cairo_status_t">
-<a name="cairo-status-t"></a><h3>enum cairo_status_t</h3>
-<pre class="programlisting">typedef enum _cairo_status {
-    CAIRO_STATUS_SUCCESS = 0,
-    CAIRO_STATUS_NO_MEMORY,
-    CAIRO_STATUS_INVALID_RESTORE,
-    CAIRO_STATUS_INVALID_POP_GROUP,
-    CAIRO_STATUS_NO_CURRENT_POINT,
-    CAIRO_STATUS_INVALID_MATRIX,
-    CAIRO_STATUS_INVALID_STATUS,
-    CAIRO_STATUS_NULL_POINTER,
-    CAIRO_STATUS_INVALID_STRING,
-    CAIRO_STATUS_INVALID_PATH_DATA,
-    CAIRO_STATUS_READ_ERROR,
-    CAIRO_STATUS_WRITE_ERROR,
-    CAIRO_STATUS_SURFACE_FINISHED,
-    CAIRO_STATUS_SURFACE_TYPE_MISMATCH,
-    CAIRO_STATUS_PATTERN_TYPE_MISMATCH,
-    CAIRO_STATUS_INVALID_CONTENT,
-    CAIRO_STATUS_INVALID_FORMAT,
-    CAIRO_STATUS_INVALID_VISUAL,
-    CAIRO_STATUS_FILE_NOT_FOUND,
-    CAIRO_STATUS_INVALID_DASH,
-    CAIRO_STATUS_INVALID_DSC_COMMENT,
-    CAIRO_STATUS_INVALID_INDEX,
-    CAIRO_STATUS_CLIP_NOT_REPRESENTABLE,
-    CAIRO_STATUS_TEMP_FILE_ERROR,
-    CAIRO_STATUS_INVALID_STRIDE,
-    CAIRO_STATUS_FONT_TYPE_MISMATCH,
-    CAIRO_STATUS_USER_FONT_IMMUTABLE,
-    CAIRO_STATUS_USER_FONT_ERROR,
-    CAIRO_STATUS_NEGATIVE_COUNT,
-    CAIRO_STATUS_INVALID_CLUSTERS,
-    CAIRO_STATUS_INVALID_SLANT,
-    CAIRO_STATUS_INVALID_WEIGHT,
-    CAIRO_STATUS_INVALID_SIZE,
-    CAIRO_STATUS_USER_FONT_NOT_IMPLEMENTED,
-    CAIRO_STATUS_DEVICE_TYPE_MISMATCH,
-    CAIRO_STATUS_DEVICE_ERROR,
-    CAIRO_STATUS_LAST_STATUS
-} cairo_status_t;
-</pre>
-<p>
-<a class="link" href="cairo-Error-handling.html#cairo-status-t" title="enum cairo_status_t"><span class="type">cairo_status_t</span></a> is used to indicate errors that can occur when
-using Cairo. In some cases it is returned directly by functions.
-but when using <a class="link" href="cairo-cairo-t.html#cairo-t" title="cairo_t"><span class="type">cairo_t</span></a>, the last error, if any, is stored in
-the context and can be retrieved with <a class="link" href="cairo-cairo-t.html#cairo-status" title="cairo_status ()"><code class="function">cairo_status()</code></a>.
-</p>
-<p>
-New entries may be added in future versions.  Use <a class="link" href="cairo-Error-handling.html#cairo-status-to-string" title="cairo_status_to_string ()"><code class="function">cairo_status_to_string()</code></a>
-to get a human-readable representation of an error message.
-</p>
-<div class="variablelist"><table border="0">
-<col align="left" valign="top">
-<tbody>
-<tr>
-<td><p><a name="CAIRO-STATUS-SUCCESS:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_SUCCESS</code></span></p></td>
-<td>no error has occurred
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-NO-MEMORY:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_NO_MEMORY</code></span></p></td>
-<td>out of memory
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-RESTORE:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_RESTORE</code></span></p></td>
-<td>cairo_restore() called without matching <a class="link" href="cairo-cairo-t.html#cairo-save" title="cairo_save ()"><code class="function">cairo_save()</code></a>
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-POP-GROUP:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_POP_GROUP</code></span></p></td>
-<td>no saved group to pop, i.e. <a class="link" href="cairo-cairo-t.html#cairo-pop-group" title="cairo_pop_group ()"><code class="function">cairo_pop_group()</code></a> without matching <a class="link" href="cairo-cairo-t.html#cairo-push-group" title="cairo_push_group ()"><code class="function">cairo_push_group()</code></a>
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-NO-CURRENT-POINT:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_NO_CURRENT_POINT</code></span></p></td>
-<td>no current point defined
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-MATRIX:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_MATRIX</code></span></p></td>
-<td>invalid matrix (not invertible)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-STATUS:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_STATUS</code></span></p></td>
-<td>invalid value for an input <a class="link" href="cairo-Error-handling.html#cairo-status-t" title="enum cairo_status_t"><span class="type">cairo_status_t</span></a>
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-NULL-POINTER:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_NULL_POINTER</code></span></p></td>
-<td>
-<a href="http://library.gnome.org/devel/glib/unstable/glib-Standard-Macros.html#NULL:CAPS"><code class="literal">NULL</code></a> pointer
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-STRING:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_STRING</code></span></p></td>
-<td>input string not valid UTF-8
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-PATH-DATA:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_PATH_DATA</code></span></p></td>
-<td>input path data not valid
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-READ-ERROR:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_READ_ERROR</code></span></p></td>
-<td>error while reading from input stream
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-WRITE-ERROR:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_WRITE_ERROR</code></span></p></td>
-<td>error while writing to output stream
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-SURFACE-FINISHED:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_SURFACE_FINISHED</code></span></p></td>
-<td>target surface has been finished
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-SURFACE-TYPE-MISMATCH:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_SURFACE_TYPE_MISMATCH</code></span></p></td>
-<td>the surface type is not appropriate for the operation
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-PATTERN-TYPE-MISMATCH:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_PATTERN_TYPE_MISMATCH</code></span></p></td>
-<td>the pattern type is not appropriate for the operation
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-CONTENT:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_CONTENT</code></span></p></td>
-<td>invalid value for an input <a class="link" href="cairo-cairo-surface-t.html#cairo-content-t" title="enum cairo_content_t"><span class="type">cairo_content_t</span></a>
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-FORMAT:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_FORMAT</code></span></p></td>
-<td>invalid value for an input <a class="link" href="cairo-Image-Surfaces.html#cairo-format-t" title="enum cairo_format_t"><span class="type">cairo_format_t</span></a>
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-VISUAL:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_VISUAL</code></span></p></td>
-<td>invalid value for an input Visual*
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-FILE-NOT-FOUND:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_FILE_NOT_FOUND</code></span></p></td>
-<td>file not found
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-DASH:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_DASH</code></span></p></td>
-<td>invalid value for a dash setting
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-DSC-COMMENT:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_DSC_COMMENT</code></span></p></td>
-<td>invalid value for a DSC comment (Since 1.2)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-INDEX:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_INDEX</code></span></p></td>
-<td>invalid index passed to getter (Since 1.4)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-CLIP-NOT-REPRESENTABLE:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_CLIP_NOT_REPRESENTABLE</code></span></p></td>
-<td>clip region not representable in desired format (Since 1.4)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-TEMP-FILE-ERROR:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_TEMP_FILE_ERROR</code></span></p></td>
-<td>error creating or writing to a temporary file (Since 1.6)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-STRIDE:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_STRIDE</code></span></p></td>
-<td>invalid value for stride (Since 1.6)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-FONT-TYPE-MISMATCH:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_FONT_TYPE_MISMATCH</code></span></p></td>
-<td>the font type is not appropriate for the operation (Since 1.8)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-USER-FONT-IMMUTABLE:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_USER_FONT_IMMUTABLE</code></span></p></td>
-<td>the user-font is immutable (Since 1.8)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-USER-FONT-ERROR:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_USER_FONT_ERROR</code></span></p></td>
-<td>error occurred in a user-font callback function (Since 1.8)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-NEGATIVE-COUNT:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_NEGATIVE_COUNT</code></span></p></td>
-<td>negative number used where it is not allowed (Since 1.8)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-CLUSTERS:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_CLUSTERS</code></span></p></td>
-<td>input clusters do not represent the accompanying text and glyph array (Since 1.8)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-SLANT:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_SLANT</code></span></p></td>
-<td>invalid value for an input <a class="link" href="cairo-text.html#cairo-font-slant-t" title="enum cairo_font_slant_t"><span class="type">cairo_font_slant_t</span></a> (Since 1.8)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-WEIGHT:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_WEIGHT</code></span></p></td>
-<td>invalid value for an input <a class="link" href="cairo-text.html#cairo-font-weight-t" title="enum cairo_font_weight_t"><span class="type">cairo_font_weight_t</span></a> (Since 1.8)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-INVALID-SIZE:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_INVALID_SIZE</code></span></p></td>
-<td>invalid value (typically too big) for the size of the input (surface, pattern, etc.) (Since 1.10)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-USER-FONT-NOT-IMPLEMENTED:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_USER_FONT_NOT_IMPLEMENTED</code></span></p></td>
-<td>user-font method not implemented (Since 1.10)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-DEVICE-TYPE-MISMATCH:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_DEVICE_TYPE_MISMATCH</code></span></p></td>
-<td>the device type is not appropriate for the operation (Since 1.10)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-DEVICE-ERROR:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_DEVICE_ERROR</code></span></p></td>
-<td>an operation to the device caused an unspecified error (Since 1.10)
-</td>
-</tr>
-<tr>
-<td><p><a name="CAIRO-STATUS-LAST-STATUS:CAPS"></a><span class="term"><code class="literal">CAIRO_STATUS_LAST_STATUS</code></span></p></td>
-<td>this is a special value indicating the number of
-  status values defined in this enumeration.  When using this value, note
-  that the version of cairo at run-time may have additional status values
-  defined than the value of this symbol at compile-time. (Since 1.10)
-</td>
-</tr>
-</tbody>
-</table></div>
-</div>
-<hr>
-<div class="refsect2" title="cairo_status_to_string ()">
-<a name="cairo-status-to-string"></a><h3>cairo_status_to_string ()</h3>
-<pre class="programlisting">const <span class="returnvalue">char</span> *        cairo_status_to_string              (<em class="parameter"><code><a class="link" href="cairo-Error-handling.html#cairo-status-t" title="enum cairo_status_t"><span class="type">cairo_status_t</span></a> status</code></em>);</pre>
-<p>
-Provides a human-readable description of a <a class="link" href="cairo-Error-handling.html#cairo-status-t" title="enum cairo_status_t"><span class="type">cairo_status_t</span></a>.
-</p>
-<div class="variablelist"><table border="0">
-<col align="left" valign="top">
-<tbody>
-<tr>
-<td><p><span class="term"><em class="parameter"><code>status</code></em> :</span></p></td>
-<td>a cairo status
-</td>
-</tr>
-<tr>
-<td><p><span class="term"><span class="emphasis"><em>Returns</em></span> :</span></p></td>
-<td> a string representation of the status
-</td>
-</tr>
-</tbody>
-</table></div>
-</div>
-<hr>
-<div class="refsect2" title="cairo_debug_reset_static_data ()">
-<a name="cairo-debug-reset-static-data"></a><h3>cairo_debug_reset_static_data ()</h3>
-<pre class="programlisting"><span class="returnvalue">void</span>                cairo_debug_reset_static_data       (<em class="parameter"><code><span class="type">void</span></code></em>);</pre>
-<p>
-Resets all static data within cairo to its original state,
-(ie. identical to the state at the time of program invocation). For
-example, all caches within cairo will be flushed empty.
-</p>
-<p>
-This function is intended to be useful when using memory-checking
-tools such as valgrind. When valgrind's memcheck analyzes a
-cairo-using program without a call to <a class="link" href="cairo-Error-handling.html#cairo-debug-reset-static-data" title="cairo_debug_reset_static_data ()"><code class="function">cairo_debug_reset_static_data()</code></a>,
-it will report all data reachable via cairo's static objects as
-"still reachable". Calling <a class="link" href="cairo-Error-handling.html#cairo-debug-reset-static-data" title="cairo_debug_reset_static_data ()"><code class="function">cairo_debug_reset_static_data()</code></a> just prior
-to program termination will make it easier to get squeaky clean
-reports from valgrind.
-</p>
-<p>
-WARNING: It is only safe to call this function when there are no
-active cairo objects remaining, (ie. the appropriate destroy
-functions have been called as necessary). If there are active cairo
-objects, this call is likely to cause a crash, (eg. an assertion
-failure due to a hash table being destroyed when non-empty).
-</p>
-</div>
-</div>
-<div class="refsect1" title="See Also">
-<a name="cairo-Error-handling.see-also"></a><h2>See Also</h2>
-cairo_status(), <a class="link" href="cairo-cairo-surface-t.html#cairo-surface-status" title="cairo_surface_status ()"><code class="function">cairo_surface_status()</code></a>, <a class="link" href="cairo-cairo-pattern-t.html#cairo-pattern-status" title="cairo_pattern_status ()"><code class="function">cairo_pattern_status()</code></a>,
-           <a class="link" href="cairo-cairo-font-face-t.html#cairo-font-face-status" title="cairo_font_face_status ()"><code class="function">cairo_font_face_status()</code></a>, <a class="link" href="cairo-cairo-scaled-font-t.html#cairo-scaled-font-status" title="cairo_scaled_font_status ()"><code class="function">cairo_scaled_font_status()</code></a>,
-           <a class="link" href="cairo-Regions.html#cairo-region-status" title="cairo_region_status ()"><code class="function">cairo_region_status()</code></a>
-</div>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15</div>
-</body>
-</html>