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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1348) hide show

data/vendor/local/share/gtk-doc/html/gio/async.html DELETED

@@ -1,44 +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>Asynchronous I/O</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="pt02.html" title="Part II. API Reference">
-<link rel="prev" href="GFileMonitor.html" title="GFileMonitor">
-<link rel="next" href="GCancellable.html" title="GCancellable">
-<meta name="generator" content="GTK-Doc V1.15.1 (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="GFileMonitor.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="pt02.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">GIO Reference Manual</th>
-<td><a accesskey="n" href="GCancellable.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="chapter">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="async"></a>Asynchronous I/O</h2></div></div></div>
-<div class="toc"><dl>
-<dt>
-<span class="refentrytitle"><a href="GCancellable.html">GCancellable</a></span><span class="refpurpose"> — Thread-safe Operation Cancellation Stack</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="GAsyncResult.html">GAsyncResult</a></span><span class="refpurpose"> — Asynchronous Function Results</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="gio-GIOScheduler.html">GIOScheduler</a></span><span class="refpurpose"> — I/O Scheduler</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="GSimpleAsyncResult.html">GSimpleAsyncResult</a></span><span class="refpurpose"> — Simple asynchronous results implementation</span>
-</dt>
-</dl></div>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15.1</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/gio/ch01.html DELETED

@@ -1,207 +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>Introduction</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="pt01.html" title="Part I. GIO Overview">
-<link rel="prev" href="pt01.html" title="Part I. GIO Overview">
-<link rel="next" href="ch02.html" title="Compiling GIO applications">
-<meta name="generator" content="GTK-Doc V1.15.1 (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="pt01.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="pt01.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">GIO Reference Manual</th>
-<td><a accesskey="n" href="ch02.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="chapter">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="id320972"></a>Introduction</h2></div></div></div>
-<p>
-    GIO is striving to provide a modern, easy-to-use VFS API that sits
-    at the right level in the library stack. The goal is to overcome the
-    shortcomings of GnomeVFS and provide an API that is so good that
-    developers prefer it over raw POSIX calls. Among other things
-    that means using GObject. It also means not cloning the POSIX
-    API, but providing higher-level, document-centric interfaces.
-  </p>
-<p>
-    The abstract file system model of GIO consists of a number of
-    interfaces and base classes for I/O and files:
-    </p>
-<div class="variablelist"><table border="0">
-<col align="left" valign="top">
-<tbody>
-<tr>
-<td><p><span class="term">GFile</span></p></td>
-<td><p>reference to a file</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GFileInfo</span></p></td>
-<td><p>information about a file or filesystem</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GFileEnumerator</span></p></td>
-<td><p>list files in directories</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GDrive</span></p></td>
-<td><p>represents a drive</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GVolume</span></p></td>
-<td><p>represents a file system in an abstract way</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GMount</span></p></td>
-<td><p>represents a mounted file system</p></td>
-</tr>
-</tbody>
-</table></div>
-<p>
-    Then there is a number of stream classes, similar to the input and
-    output stream hierarchies that can be found in frameworks like Java:
-    </p>
-<div class="variablelist"><table border="0">
-<col align="left" valign="top">
-<tbody>
-<tr>
-<td><p><span class="term">GInputStream</span></p></td>
-<td><p>read data</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GOutputStream</span></p></td>
-<td><p>write data</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GIOStream</span></p></td>
-<td><p>read and write data</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GSeekable</span></p></td>
-<td><p>interface optionally implemented by streams to support seeking</p></td>
-</tr>
-</tbody>
-</table></div>
-<p>
-    There are interfaces related to applications and the types
-    of files they handle:
-    </p>
-<div class="variablelist"><table border="0">
-<col align="left" valign="top">
-<tbody>
-<tr>
-<td><p><span class="term">GAppInfo</span></p></td>
-<td><p>information about an installed application</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GIcon</span></p></td>
-<td><p>abstract type for file and application icons</p></td>
-</tr>
-</tbody>
-</table></div>
-<p>
-    There is a framework for storing and retrieving application settings:
-    </p>
-<div class="variablelist"><table border="0">
-<col align="left" valign="top">
-<tbody><tr>
-<td><p><span class="term">GSettings</span></p></td>
-<td><p>stores and retrieves application settings</p></td>
-</tr></tbody>
-</table></div>
-<p>
-    There is support for network programming, including name resolution, lowlevel socket
-    APIs and highlevel client and server helper classes:
-    </p>
-<div class="variablelist"><table border="0">
-<col align="left" valign="top">
-<tbody>
-<tr>
-<td><p><span class="term">GSocket</span></p></td>
-<td><p>lowlevel platform independent socket object</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GResolver</span></p></td>
-<td><p>asynchronous and cancellable DNS resolver</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GSocketClient</span></p></td>
-<td><p>high-level network client helper</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GSocketService</span></p></td>
-<td><p>high-level network server helper</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GSocketConnection</span></p></td>
-<td><p>network connection stream</p></td>
-</tr>
-</tbody>
-</table></div>
-<p>
-    There is support for connecting to D-Bus,
-    sending and receiving messages, owning and watching bus names,
-    and making objects available on the bus:
-    </p>
-<div class="variablelist"><table border="0">
-<col align="left" valign="top">
-<tbody>
-<tr>
-<td><p><span class="term">GDBusConnection</span></p></td>
-<td><p>a D-Bus connection</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GDBusMethodInvocation</span></p></td>
-<td><p>for handling remove calls</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GDBusServer</span></p></td>
-<td><p>helper for accepting connections</p></td>
-</tr>
-<tr>
-<td><p><span class="term">GDBusProxy</span></p></td>
-<td><p>proxy to access D-Bus interfaces on a remote object</p></td>
-</tr>
-</tbody>
-</table></div>
-<p>
-    Beyond these, GIO provides facilities for file monitoring,
-    asynchronous I/O and filename completion. In addition to the
-    interfaces, GIO provides implementations for the local case.
-    Implementations for various network file systems are provided
-    by the GVFS package as loadable modules.
-  </p>
-<p>
-    Other design choices which consciously break with the GnomeVFS
-    design are to move backends out-of-process, which minimizes the
-    dependency bloat and makes the whole system more robust. The backends
-    are not included in GIO, but in the separate GVFS package. The GVFS
-    package also contains the GVFS daemon, which spawn further mount
-    daemons for each individual connection.
-  </p>
-<div class="figure">
-<a name="gvfs-overview"></a><p class="title"><b>Figure 1. GIO in the GTK+ library stack</b></p>
-<div class="figure-contents"><div><img src="gvfs-overview.png" alt="GIO in the GTK+ library stack"></div></div>
-</div>
-<br class="figure-break"><p>
-    The GIO model of I/O is stateful: if an application establishes e.g.
-    a SFTP connection to a server, it becomes available to all applications
-    in the session; the user does not have to enter his password over
-    and over again.
-  </p>
-<p>
-    One of the big advantages of putting the VFS in the GLib layer
-    is that GTK+ can directly use it, e.g. in the filechooser.
-  </p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15.1</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/gio/ch02.html DELETED

@@ -1,50 +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>Compiling GIO applications</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="pt01.html" title="Part I. GIO Overview">
-<link rel="prev" href="ch01.html" title="Introduction">
-<link rel="next" href="ch03.html" title="Running GIO applications">
-<meta name="generator" content="GTK-Doc V1.15.1 (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="ch01.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="pt01.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">GIO Reference Manual</th>
-<td><a accesskey="n" href="ch03.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="chapter">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="id355892"></a>Compiling GIO applications</h2></div></div></div>
-<p>
-      GIO comes with a <code class="filename">gio-2.0.pc</code> file that you
-      should use together with <code class="literal">pkg-config</code> to obtain
-      the necessary information about header files and libraries. See
-      the <code class="literal">pkg-config</code> man page or the GLib documentation
-      for more information on how to use <code class="literal">pkg-config</code>
-      to compile your application.
-    </p>
-<p>
-      If you are using GIO on UNIX-like systems, you may want to use
-      UNIX-specific GIO interfaces such as <a class="link" href="GUnixInputStream.html" title="GUnixInputStream"><span class="type">GUnixInputStream</span></a>,
-      <a class="link" href="GUnixOutputStream.html" title="GUnixOutputStream"><span class="type">GUnixOutputStream</span></a>, <span class="type">GUnixMount</span> or <a class="link" href="gio-Desktop-file-based-GAppInfo.html#GDesktopAppInfo"><span class="type">GDesktopAppInfo</span></a>.
-      To do so, use the <code class="filename">gio-unix-2.0.pc</code> file
-      instead of <code class="filename">gio-2.0.pc</code>
-    </p>
-<p>
-      Since GIO is based on GObject, you need to call <a href="http://library.gnome.org/devel/gobject/unstable/gobject-Type-Information.html#g-type-init"><code class="function">g_type_init()</code></a>
-      before you can use any GIO functions. If your application uses
-      GTK+, this is already taken care of by <a href="http://library.gnome.org/devel/gtk/unstable/gtk3-General.html#gtk-init"><code class="function">gtk_init()</code></a>.
-    </p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15.1</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/gio/ch03.html DELETED

@@ -1,180 +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>Running GIO applications</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="pt01.html" title="Part I. GIO Overview">
-<link rel="prev" href="ch02.html" title="Compiling GIO applications">
-<link rel="next" href="extending-gio.html" title="Extending GIO">
-<meta name="generator" content="GTK-Doc V1.15.1 (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="ch02.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="pt01.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">GIO Reference Manual</th>
-<td><a accesskey="n" href="extending-gio.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="chapter">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="id355968"></a>Running GIO applications</h2></div></div></div>
-<p>
-      GIO inspects a few of environment variables in addition to the
-      ones used by GLib.
-    </p>
-<p><b><code class="envar">XDG_DATA_HOME</code>, <code class="envar">XDG_DATA_DIRS</code>. </b>
-        GIO uses these environment variables to locate MIME information.
-        For more information, see the <a class="ulink" href="http://freedesktop.org/Standards/shared-mime-info-spec" target="_top">Shared MIME-info Database</a>
-        and the <a class="ulink" href="http://freedesktop.org/Standards/basedir-spec" target="_top">Base Directory Specification</a>.
-      </p>
-<p><b><code class="envar">GVFS_DISABLE_FUSE</code>. </b>
-        This variable can be set to keep <span class="type">Gvfs</span> from starting the fuse backend,
-        which may be unwanted or unnecessary in certain situations.
-      </p>
-<p>
-      The following environment variables are only useful for debugging
-      GIO itself or modules that it loads. They should not be set in a
-      production environment.
-    </p>
-<p><b><code class="envar">GIO_USE_VFS</code>. </b>
-        This environment variable can be set to the name of a <a class="link" href="GVfs.html" title="GVfs"><span class="type">GVfs</span></a>
-        implementation to override the default for debugging purposes.
-        The <a class="link" href="GVfs.html" title="GVfs"><span class="type">GVfs</span></a> implementation for local files that is included in GIO
-        has the name "local", the implementation in the gvfs module has
-        the name "gvfs".
-      </p>
-<p><b><code class="envar">GIO_USE_VOLUME_MONITOR</code>. </b>
-        This variable can be set to the name of a <a class="link" href="GVolumeMonitor.html" title="GVolumeMonitor"><span class="type">GVolumeMonitor</span></a>
-        implementation to override the default for debugging purposes.
-        The <a class="link" href="GVolumeMonitor.html" title="GVolumeMonitor"><span class="type">GVolumeMonitor</span></a> implementation for local files that is included
-        in GIO has the name "unix", the hal-based implementation in the
-        gvfs module has the name "hal".
-      </p>
-<p><b><code class="envar">GIO_USE_URI_ASSOCIATION</code>. </b>
-        This variable can be set to the name of a <a class="link" href="gio-Desktop-file-based-GAppInfo.html#GDesktopAppInfoLookup"><span class="type">GDesktopAppInfoLookup</span></a>
-        implementation to override the default for debugging purposes.
-        GIO does not include a <a class="link" href="gio-Desktop-file-based-GAppInfo.html#GDesktopAppInfoLookup"><span class="type">GDesktopAppInfoLookup</span></a> implementation,
-        the GConf-based implementation in the gvfs module has the name
-        "gconf".
-      </p>
-<p><b><code class="envar">GVFS_INOTIFY_DIAG</code>. </b>
-        When this environment variable is set and GIO has been built
-        with inotify support, a dump of diagnostic inotify information
-        will be written every 20 seconds to a file named
-        <code class="filename">/tmp/gvfsdid.<em class="replaceable"><code>pid</code></em></code>.
-      </p>
-<p><b><code class="envar">GIO_EXTRA_MODULES</code>. </b>
-        When this environment variable is set to a path, or a set of
-        paths separated by a colon, GIO will attempt to load
-        modules from within the path.
-      </p>
-<p><b><code class="envar">GSETTINGS_BACKEND</code>. </b>
-        This variable can be set to the name of a <a class="link" href="GSettingsBackend.html" title="GSettingsBackend"><span class="type">GSettingsBackend</span></a>
-        implementation to override the default for debugging purposes.
-        The memory-based implementation that is included in GIO has
-        the name "memory", the one in dconf has the name "dconf-settings".
-      </p>
-<p><b><code class="envar">GSETTINGS_SCHEMA_DIR</code>. </b>
-        This variable can be set to the name of a directory that is
-        considered in addition to the <code class="filename">glib-2.0/schemas</code>
-        subdirectories of the XDG system data dirs when looking
-        for compiled schemas for <a class="link" href="GSettings.html" title="GSettings"><span class="type">GSettings</span></a>.
-      </p>
-<p><b><code class="envar">DBUS_SYSTEM_BUS_ADDRESS</code>. </b>
-        This variable is consulted to find the address of the D-Bus system
-        bus. For the format of D-Bus addresses, see the D-Bus
-        <a class="ulink" href="http://dbus.freedesktop.org/doc/dbus-specification.html#addresses" target="_top">specification</a>.
-        Setting this variable overrides platform-specific ways of determining
-        the system bus address.
-      </p>
-<p><b><code class="envar">DBUS_SESSION_BUS_ADDRESS</code>. </b>
-        This variable is consulted to find the address of the D-Bus session bus.
-        Setting this variable overrides platform-specific ways of determining
-        the session bus address.
-      </p>
-<p><b><code class="envar">DBUS_STARTER_BUS_TYPE</code>. </b>
-        This variable is consulted to find out the 'starter' bus for an
-        application that has been started via D-Bus activation. The possible
-        values are 'system' or 'session'.
-      </p>
-<p><b><code class="envar">G_DBUS_DEBUG</code>. </b>
-         This variable can be set to a list of debug options, which
-         cause GLib to print out different types of debugging
-         information when using the D-Bus routines.
-         </p>
-<div class="variablelist"><table border="0">
-<col align="left" valign="top">
-<tbody>
-<tr>
-<td><p><span class="term">transport</span></p></td>
-<td><p>Show IO activity (e.g. reads and writes)</p></td>
-</tr>
-<tr>
-<td><p><span class="term">message</span></p></td>
-<td><p>Show all sent and received D-Bus messages</p></td>
-</tr>
-<tr>
-<td><p><span class="term">payload</span></p></td>
-<td><p>Show payload for all sent and received D-Bus messages (implies message)</p></td>
-</tr>
-<tr>
-<td><p><span class="term">call</span></p></td>
-<td><p>Trace <a class="link" href="GDBusConnection.html#g-dbus-connection-call" title="g_dbus_connection_call ()"><code class="function">g_dbus_connection_call()</code></a> and <a class="link" href="GDBusConnection.html#g-dbus-connection-call-sync" title="g_dbus_connection_call_sync ()"><code class="function">g_dbus_connection_call_sync()</code></a> API usage</p></td>
-</tr>
-<tr>
-<td><p><span class="term">signal</span></p></td>
-<td><p>Show when a D-Bus signal is received</p></td>
-</tr>
-<tr>
-<td><p><span class="term">incoming</span></p></td>
-<td><p>Show when an incoming D-Bus method call is received</p></td>
-</tr>
-<tr>
-<td><p><span class="term">return</span></p></td>
-<td><p>Show when a reply is returned via the <a class="link" href="GDBusMethodInvocation.html" title="GDBusMethodInvocation"><span class="type">GDBusMethodInvocation</span></a> API</p></td>
-</tr>
-<tr>
-<td><p><span class="term">emission</span></p></td>
-<td><p>Trace <a class="link" href="GDBusConnection.html#g-dbus-connection-emit-signal" title="g_dbus_connection_emit_signal ()"><code class="function">g_dbus_connection_emit_signal()</code></a> API usage</p></td>
-</tr>
-<tr>
-<td><p><span class="term">authentication</span></p></td>
-<td><p>Show information about connection authentication</p></td>
-</tr>
-<tr>
-<td><p><span class="term">address</span></p></td>
-<td><p>Show information about D-Bus address lookups and autolaunching</p></td>
-</tr>
-</tbody>
-</table></div>
-<p>
-         The special value <code class="literal">all</code> can be used to turn
-         on all debug options. The special value
-         <code class="literal">help</code> can be used to print a list of
-         supported options to standard output.
-      </p>
-<p><b><code class="envar">G_DBUS_COOKIE_SHA1_KEYRING_DIR</code>. </b>
-        Can be used to override the directory used to store the
-        keyring used in the <code class="literal">DBUS_COOKIE_SHA1</code>
-        authentication mechanism. Normally the directory used is
-        <code class="filename">.dbus-keyrings</code> in the user's home
-        directory.
-      </p>
-<p><b><code class="envar">G_DBUS_COOKIE_SHA1_KEYRING_DIR_IGNORE_PERMISSION</code>. </b>
-        If set, the permissions of the directory used to store the
-        keyring used in the <code class="literal">DBUS_COOKIE_SHA1</code>
-        authentication mechanism won't be checked. Normally the
-        directory must be readable only by the user.
-      </p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15.1</div>
-</body>
-</html>