RubyGems - glib2 - Versions diffs - 1.1.8-x86-mingw32 → 1.1.9-x86-mingw32 - Mend

glib2 1.1.8-x86-mingw32 → 1.1.9-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 (1810) hide show

data/vendor/local/share/gtk-doc/html/glib/glib-resources.html CHANGED

@@ -3,17 +3,17 @@
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Mailing lists and bug reports</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
 <link rel="home" href="index.html" title="GLib Reference Manual">
 <link rel="up" href="glib.html" title="GLib Overview">
-<link rel="prev" href="glib-regex-syntax.html" title="Regular expression syntax">
+<link rel="prev" href="glib-changes.html" title="Changes to GLib">
 <link rel="next" href="glib-fundamentals.html" title="GLib Fundamentals">
-<meta name="generator" content="GTK-Doc V1.17 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.18 (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="glib-regex-syntax.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="p" href="glib-changes.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
 <td><a accesskey="u" href="glib.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">GLib Reference Manual</th>
@@ -31,7 +31,7 @@ Getting help with GLib
 <td valign="top" align="right"></td>
 </tr></table></div>
 <div class="refsect1">
-<a name="id601716"></a><h2>Filing a bug report or feature request</h2>
+<a name="idp8812608"></a><h2>Filing a bug report or feature request</h2>
 <p>
 If you encounter a bug, misfeature, or missing feature in GLib, please
 file a bug report on
@@ -53,7 +53,7 @@ the way to be sure the GLib developers won't forget about an issue.
 </p>
 </div>
 <div class="refsect1">
-<a name="id599172"></a><h2>Submitting Patches</h2>
+<a name="idp10910960"></a><h2>Submitting Patches</h2>
 <p>
 If you develop a bugfix or enhancement for GLib, please file that in
 Bugzilla as well. Bugzilla allows you to attach files; please attach a
@@ -70,7 +70,7 @@ list and not in Bugzilla, it's likely to slip through the cracks.
 </p>
 </div>
 <div class="refsect1">
-<a name="id636052"></a><h2>Mailing lists</h2>
+<a name="idp10775296"></a><h2>Mailing lists</h2>
 <p>
 There are several mailing lists dedicated to GTK+ and related
 libraries. Discussion of GLib generally takes place on these lists.
@@ -79,8 +79,11 @@ You can subscribe or view the archives of these lists on
 </p>
 <p>
 </p>
-<div class="variablelist"><table border="0">
+<div class="variablelist"><table border="0" class="variablelist">
+<colgroup>
 <col align="left" valign="top">
+<col>
+</colgroup>
 <tbody>
 <tr>
 <td><p><span class="term"><a class="ulink" href="mailto:gtk-list@gnome.org" target="_top">gtk-list@gnome.org</a></span></p></td>
@@ -116,6 +119,6 @@ documentation system (used to document GTK+ and Glib), and for work on the GTK+
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.17</div>
+          Generated by GTK-Doc V1.18</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/glib/glib-running.html CHANGED

@@ -3,12 +3,12 @@
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Running GLib Applications</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
 <link rel="home" href="index.html" title="GLib Reference Manual">
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib-compiling.html" title="Compiling GLib Applications">
 <link rel="next" href="glib-changes.html" title="Changes to GLib">
-<meta name="generator" content="GTK-Doc V1.17 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.18 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -31,155 +31,176 @@ How to run and debug your GLib application
 <td valign="top" align="right"></td>
 </tr></table></div>
 <div class="refsect1">
-<a name="id618406"></a><h2>Running and debugging GLib Applications</h2>
+<a name="idp7452336"></a><h2>Running and debugging GLib Applications</h2>
 <div class="refsect2">
-<a name="id612042"></a><h3>Environment variables</h3>
-<p>
-GLib inspects a few of environment variables in addition to standard
-variables like <code class="envar">LANG</code>, <code class="envar">PATH</code> or <code class="envar">HOME</code>.
+<a name="idp11038096"></a><h3>Environment variables</h3>
+<p>
+  The runtime behaviour of GLib applications can be influenced by a
+  number of environment variables.
 </p>
+<p><b>Standard variables. </b>
+    GLib reads standard environment variables like <code class="envar">LANG</code>,
+    <code class="envar">PATH</code>, <code class="envar">HOME</code>, <code class="envar">TMPDIR</code>,
+    <code class="envar">TZ</code> and <code class="envar">LOGNAME</code>.
+  </p>
+<p><b>XDG directories. </b>
+    GLib consults the environment variables <code class="envar">XDG_DATA_HOME</code>,
+    <code class="envar">XDG_DATA_DIRS</code>, <code class="envar">XDG_CONFIG_HOME</code>,
+    <code class="envar">XDG_CONFIG_DIRS</code>, <code class="envar">XDG_CACHE_HOME</code> and
+    <code class="envar">XDG_RUNTIME_DIR</code> for the various XDG directories.
+    For more information, see the <a class="ulink" href="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html" target="_top">XDG basedir spec</a>.
+  </p>
 <p><a name="G_FILENAME_ENCODING"></a><b><code class="envar">G_FILENAME_ENCODING</code>. </b>
     This environment variable can be set to a comma-separated list of character
-    set names. GLib assumes that filenames are encoded in the first character
+    set names. GLib assumes that filenames are encoded in the first character
     set from that list rather than in UTF-8. The special token "@locale" can be
     used to specify the character set for the current locale.
   </p>
 <p><a name="G_BROKEN_FILENAMES"></a><b><code class="envar">G_BROKEN_FILENAMES</code>. </b>
-    If this environment variable is set, GLib assumes that filenames are in
+    If this environment variable is set, GLib assumes that filenames are in
     the locale encoding rather than in UTF-8. G_FILENAME_ENCODING takes
-    priority over G_BROKEN_FILENAMES.
+    priority over G_BROKEN_FILENAMES.
   </p>
 <p><a name="G_MESSAGES_PREFIXED"></a><b><code class="envar">G_MESSAGES_PREFIXED</code>. </b>
-    A list of log levels for which messages should be prefixed by the
+    A list of log levels for which messages should be prefixed by the
     program name and PID of the application. The default is to prefix
-    everything except <code class="literal">G_LOG_LEVEL_MESSAGE</code> and <code class="literal">G_LOG_LEVEL_INFO</code>.
+    everything except <code class="literal">G_LOG_LEVEL_MESSAGE</code> and
+    <code class="literal">G_LOG_LEVEL_INFO</code>.
+    The possible values are
+    <code class="literal">error</code>,
+    <code class="literal">warning</code>,
+    <code class="literal">critical</code>,
+    <code class="literal">message</code>,
+    <code class="literal">info</code> and
+    <code class="literal">debug</code>.
+    You can also use the special values
+    <code class="literal">all</code> and
+    <code class="literal">help</code>.
+    This environment variable only affects the default log handler,
+    g_log_default_handler().
+  </p>
+<p><a name="G_MESSAGES_DEBUG"></a><b><code class="envar">G_MESSAGES_DEBUG</code>. </b>
+    A space-separated list of log domains for which informational
+    and debug messages should be printed. By default, these
+    messages are not printed.
+    You can also use the special value <code class="literal">all</code>.
+    This environment variable only affects the default log handler,
+    g_log_default_handler().
   </p>
-<p><a name="G_DEBUG"></a><b><code class="envar">G_DEBUG</code>. </b>
-    If GLib has been configured with <code class="option">--enable-debug=yes</code>,
-    this variable can be set to a list of debug options, which cause GLib
-    to print out different types of debugging information.
+<p><a name="G-DEBUG:CAPS"></a><b><code class="envar">G_DEBUG</code>. </b>
+    This environment variable can be set to a list of debug options,
+    which cause GLib to print out different types of debugging information.
     </p>
-<div class="variablelist"><table border="0">
+<div class="variablelist"><table border="0" class="variablelist">
+<colgroup>
 <col align="left" valign="top">
+<col>
+</colgroup>
 <tbody>
 <tr>
-<td><p><span class="term">fatal_warnings</span></p></td>
+<td><p><span class="term">fatal-warnings</span></p></td>
 <td><p>Causes GLib to abort the program at the first call
-           to <a class="link" href="glib-Message-Logging.html#g-warning" title="g_warning()">g_warning</a>() or
-	   <a class="link" href="glib-Message-Logging.html#g-critical" title="g_critical()">g_critical</a>(). This option is
-           special in that it doesn't require GLib to be configured with
-           debugging support.</p></td>
+           to g_warning() or g_critical().</p></td>
 </tr>
 <tr>
-<td><p><span class="term">fatal_criticals</span></p></td>
+<td><p><span class="term">fatal-criticals</span></p></td>
 <td><p>Causes GLib to abort the program at the first call
-           to <a class="link" href="glib-Message-Logging.html#g-critical" title="g_critical()">g_critical</a>(). This option is
-           special in that it doesn't require GLib to be configured with
-           debugging support.</p></td>
+           to g_critical().</p></td>
 </tr>
 <tr>
 <td><p><span class="term">gc-friendly</span></p></td>
-<td><p>
-		  Newly allocated memory that isn't directly initialized, as well
-		  as memory being freed will be reset to 0. The point here is to
-		  allow memory checkers and similar programs that use bohem GC alike
-		  algorithms to produce more accurate results.
-		  This option is special in that it doesn't require GLib to be
-		  configured with debugging support.
-		</p></td>
+<td><p>Newly allocated memory that isn't directly initialized,
+          as well as memory being freed will be reset to 0. The point here is
+          to allow memory checkers and similar programs that use Boehm GC alike
+          algorithms to produce more accurate results.</p></td>
 </tr>
 <tr>
 <td><p><span class="term">resident-modules</span></p></td>
-<td><p>
-	    All modules loaded by GModule will be made resident. This can be useful
-	    for tracking memory leaks in modules which are later unloaded; but it can
-	    also hide bugs where code is accessed after the module would have normally
-	    been unloaded.
-	    This option is special in that it doesn't require GLib to be
- 	    configured with debugging support.
-	  </p></td>
+<td><p>All modules loaded by GModule will be made resident.
+          This can be useful for tracking memory leaks in modules which are
+          later unloaded; but it can also hide bugs where code is accessed
+          after the module would have normally been unloaded.</p></td>
 </tr>
 <tr>
 <td><p><span class="term">bind-now-modules</span></p></td>
-<td><p>
-	    All modules loaded by GModule will bind their symbols at load time, even
-	    when the code uses %G_MODULE_BIND_LAZY.
-	    This option is special in that it doesn't require GLib to be
- 	    configured with debugging support.
-	  </p></td>
+<td><p>All modules loaded by GModule will bind their symbols
+          at load time, even when the code uses %G_MODULE_BIND_LAZY.</p></td>
 </tr>
 </tbody>
 </table></div>
 <p>
-    The special value all can be used to turn on all debug options.
-    The special value help can be used to print all available options.
+    The special value all can be used to turn on all debug options.
+    The special value help can be used to print all available options.
   </p>
 <p><a name="G_SLICE"></a><b><code class="envar">G_SLICE</code>. </b>
-	  This environment variable allows reconfiguration of the GSlice
-	  memory allocator.
-	  </p>
-<div class="variablelist"><table border="0">
+    This environment variable allows reconfiguration of the GSlice
+    memory allocator.
+    </p>
+<div class="variablelist"><table border="0" class="variablelist">
+<colgroup>
 <col align="left" valign="top">
+<col>
+</colgroup>
 <tbody>
 <tr>
 <td><p><span class="term">always-malloc</span></p></td>
-<td><p>
-		  This will cause all slices allocated through g_slice_alloc() and
-		  released by g_slice_free1() to be actually allocated via direct
-		  calls to g_malloc() and g_free().
-		  This is most useful for memory checkers and similar programs that
-		  use Bohem GC alike algorithms to produce more accurate results.
-		  It can also be in conjunction with debugging features of the system's
-		  malloc implementation such as glibc's MALLOC_CHECK_=2 to debug
-		  erroneous slice allocation code, allthough <code class="literal">debug-blocks</code>
-		  usually is a better suited debugging tool.
-		</p></td>
+<td><p>This will cause all slices allocated through
+          g_slice_alloc() and released by g_slice_free1() to be actually
+          allocated via direct calls to g_malloc() and g_free().
+          This is most useful for memory checkers and similar programs that
+          use Boehm GC alike algorithms to produce more accurate results.
+          It can also be in conjunction with debugging features of the system's
+          malloc() implementation such as glibc's MALLOC_CHECK_=2 to debug
+          erroneous slice allocation code, although
+          <code class="literal">debug-blocks</code> is usually a better suited debugging
+          tool.</p></td>
 </tr>
 <tr>
 <td><p><span class="term">debug-blocks</span></p></td>
 <td>
-<p>
-		  Using this option (present since GLib-2.13) engages extra code
-		  which performs sanity checks on the released memory slices.
-		  Invalid slice adresses or slice sizes will be reported and lead to
-		  a program halt.
-		  This option is for debugging scenarios.
-		  In particular, client packages sporting their own test suite should
-		  <span class="emphasis"><em>always enable this option when running tests</em></span>.
-		  Global slice validation is ensured by storing size and address information
-		  for each allocated chunk, and maintaining a global hash table of that data.
-		  That way, multi-thread scalability is given up, and memory consumption is
-		  increased. However, the resulting code usually performs acceptably well,
-		  possibly better than with comparable memory checking carried out using
-		  external tools. An example of a memory corruption scenario that cannot be
-		  reproduced with <code class="literal">G_SLICE=always-malloc</code>, but will be caught
-		  by <code class="literal">G_SLICE=debug-blocks</code> is as follows:
-		  </p>
+<p>Using this option (present since GLib 2.13) engages
+          extra code which performs sanity checks on the released memory
+          slices. Invalid slice adresses or slice sizes will be reported and
+          lead to a program halt. This option is for debugging scenarios.
+          In particular, client packages sporting their own test suite should
+          <span class="emphasis"><em>always enable this option when running tests</em></span>.
+          Global slice validation is ensured by storing size and address
+          information for each allocated chunk, and maintaining a global
+          hash table of that data. That way, multi-thread scalability is
+          given up, and memory consumption is increased. However, the
+          resulting code usually performs acceptably well, possibly better
+          than with comparable memory checking carried out using external
+          tools.</p>
+<p>An example of a memory corruption scenario that cannot be
+          reproduced with <code class="literal">G_SLICE=always-malloc</code>, but will
+          be caught by <code class="literal">G_SLICE=debug-blocks</code> is as follows:
+          </p>
 <pre class="programlisting">
-		    void *slist = g_slist_alloc(); /* void* gives up type-safety */
-		    g_list_free (slist);           /* corruption: sizeof (GSList) != sizeof (GList) */
-		  </pre>
-<p>
-		</p>
+            void *slist = g_slist_alloc (); /* void* gives up type-safety */
+            g_list_free (slist);            /* corruption: sizeof (GSList) != sizeof (GList) */
+          </pre>
 </td>
 </tr>
 </tbody>
 </table></div>
 <p>
-          The special value all can be used to turn on all options.
-          The special value help can be used to print all available options.
-	</p>
+    The special value all can be used to turn on all options.
+    The special value help can be used to print all available options.
+  </p>
 <p><a name="G_RANDOM_VERSION"></a><b><code class="envar">G_RANDOM_VERSION</code>. </b>
     If this environment variable is set to '2.0', the outdated
     pseudo-random number seeding and generation algorithms from
-    GLib-2.0 are used instead of the new better ones. Use the GLib-2.0
-    algorithms only if you have sequences of numbers generated with
-    Glib-2.0 that you need to reproduce exactly.
+    GLib 2.0 are used instead of the newer, better ones. You should
+    only set this variable if you have sequences of numbers that were
+    generated with Glib 2.0 that you need to reproduce exactly.
   </p>
 <p><a name="LIBCHARSET_ALIAS_DIR"></a><b><code class="envar">LIBCHARSET_ALIAS_DIR</code>. </b>
-    Allows to specify a nonstandard location for the
+    Allows to specify a nonstandard location for the
     <code class="filename">charset.aliases</code> file that is used by the
-    character set conversion routines. The default location is the
+    character set conversion routines. The default location is the
     <em class="replaceable"><code>libdir</code></em> specified at compilation time.
   </p>
 <p><a name="TZDIR"></a><b><code class="envar">TZDIR</code>. </b>
@@ -195,7 +216,7 @@ variables like <code class="envar">LANG</code>, <code class="envar">PATH</code>
 <p>
 A number of interfaces in GLib depend on the current locale in which
 an application is running. Therefore, most GLib-using applications should
-call <code class="function">setlocale (LC_ALL, "")</code> to set up the current
+call <code class="function">setlocale (LC_ALL, "")</code> to set up the current
 locale.
 </p>
 <p>
@@ -215,14 +236,14 @@ returned by functions like <code class="function">strftime()</code>.
 </div>
 <hr>
 <div class="refsect2">
-<a name="id599302"></a><h3>Traps and traces</h3>
+<a name="idp5864000"></a><h3>Traps and traces</h3>
 <p>
-Some code portions contain trap variables that can be set during debugging
-time if GLib has been configured with <code class="option">--enable-debug=yes</code>.
-Such traps lead to immediate code halts to examine the current program state
+Some code portions contain trap variables that can be set during debugging
+time if GLib has been configured with <code class="option">--enable-debug=yes</code>.
+Such traps lead to immediate code halts to examine the current program state
 and backtrace.
 </p>
 <p>
@@ -234,11 +255,11 @@ static volatile gulong g_trap_realloc_size;
 static volatile gulong g_trap_malloc_size;
 </pre>
 <p>
-If set to a size &gt; 0, <a class="link" href="glib-Memory-Allocation.html#g-free" title="g_free ()">g_free</a>(),
-<a class="link" href="glib-Memory-Allocation.html#g-realloc" title="g_realloc ()">g_realloc</a>() and
-<a class="link" href="glib-Memory-Allocation.html#g-malloc" title="g_malloc ()">g_malloc</a>() will be intercepted if the size
-matches the size of the corresponding memory block. This will only work with
-<code class="literal">g_mem_set_vtable (glib_mem_profiler_table)</code> upon startup
+If set to a size &gt; 0, <a class="link" href="glib-Memory-Allocation.html#g-free" title="g_free ()">g_free</a>(),
+<a class="link" href="glib-Memory-Allocation.html#g-realloc" title="g_realloc ()">g_realloc</a>() and
+<a class="link" href="glib-Memory-Allocation.html#g-malloc" title="g_malloc ()">g_malloc</a>() will be intercepted if the size
+matches the size of the corresponding memory block. This will only work with
+<code class="literal">g_mem_set_vtable (glib_mem_profiler_table)</code> upon startup
 though, because memory profiling is required to match on the memory block sizes.
 </p>
 <p>
@@ -251,12 +272,12 @@ condition 1 n_bytes == 20
 </pre>
 <p>
 to break only on g_malloc() calls where the size of the allocated memory block
-is 20.
+is 20.
 </p>
 </div>
 <hr>
 <div class="refsect2">
-<a name="id592310"></a><h3>Gdb debugging macros</h3>
+<a name="idp5874000"></a><h3>Gdb debugging macros</h3>
 <p>
 glib ships with a set of python macros for the gdb debugger. These includes pretty
 printers for lists, hashtables and gobject types. It also has a backtrace filter
@@ -287,7 +308,7 @@ Which would print the contents of each widget in a list of widgets.
 </div>
 <hr>
 <div class="refsect2">
-<a name="id592345"></a><h3>SystemTap</h3>
+<a name="idp5878256"></a><h3>SystemTap</h3>
 <p>
 <a class="ulink" href="http://sourceware.org/systemtap/" target="_top">SystemTap</a> is a dynamic whole-system
 analysis toolkit.  GLib ships with a file <code class="filename">glib.stp</code> which defines a
@@ -298,15 +319,15 @@ are in your shared SystemTap scripts directory.
 </div>
 <hr>
 <div class="refsect2">
-<a name="id592381"></a><h3>Memory statistics</h3>
+<a name="idp5882608"></a><h3>Memory statistics</h3>
 <p>
 g_mem_profile() will output a summary g_malloc() memory usage, if memory
-profiling has been enabled by calling
+profiling has been enabled by calling
 <code class="literal">g_mem_set_vtable (glib_mem_profiler_table)</code> upon startup.
 </p>
 <p>
 If GLib has been configured with <code class="option">--enable-debug=yes</code>,
-then g_slice_debug_tree_statistics() can be called in a debugger to
+then g_slice_debug_tree_statistics() can be called in a debugger to
 output details about the memory usage of the slice allocator.
 </p>
 </div>
@@ -314,6 +335,6 @@ output details about the memory usage of the slice allocator.
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.17</div>
+          Generated by GTK-Doc V1.18</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/glib/glib-utilities.html CHANGED

@@ -3,12 +3,12 @@
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>GLib Utilities</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
 <link rel="home" href="index.html" title="GLib Reference Manual">
 <link rel="up" href="index.html" title="GLib Reference Manual">
 <link rel="prev" href="glib-Message-Logging.html" title="Message Logging">
 <link rel="next" href="glib-String-Utility-Functions.html" title="String Utility Functions">
-<meta name="generator" content="GTK-Doc V1.17 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.18 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -20,23 +20,27 @@
 <td><a accesskey="n" href="glib-String-Utility-Functions.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="glib-utilities"></a>GLib Utilities</h2></div></div></div>
+<div class="titlepage"><div><div><h1 class="title">
+<a name="glib-utilities"></a>GLib Utilities</h1></div></div></div>
 <div class="toc"><dl>
 <dt>
 <span class="refentrytitle"><a href="glib-String-Utility-Functions.html">String Utility Functions</a></span><span class="refpurpose"> — various string-related functions</span>
 </dt>
 <dt>
-<span class="refentrytitle"><a href="glib-Character-Set-Conversion.html">Character Set Conversion</a></span><span class="refpurpose"> — Convert strings between different character sets</span>
+<span class="refentrytitle"><a href="glib-Character-Set-Conversion.html">Character Set Conversion</a></span><span class="refpurpose"> — convert strings between different character sets</span>
 </dt>
 <dt>
-<span class="refentrytitle"><a href="glib-Unicode-Manipulation.html">Unicode Manipulation</a></span><span class="refpurpose"> — functions operating on Unicode characters and UTF-8 strings</span>
+<span class="refentrytitle"><a href="glib-Unicode-Manipulation.html">Unicode Manipulation</a></span><span class="refpurpose"> — functions operating on Unicode characters and
+    UTF-8 strings</span>
 </dt>
 <dt>
 <span class="refentrytitle"><a href="glib-Base64-Encoding.html">Base64 Encoding</a></span><span class="refpurpose"> — encodes and decodes data in Base64 format</span>
 </dt>
 <dt>
-<span class="refentrytitle"><a href="glib-Data-Checksums.html">Data Checksums</a></span><span class="refpurpose"> — Computes the checksum for data</span>
+<span class="refentrytitle"><a href="glib-Data-Checksums.html">Data Checksums</a></span><span class="refpurpose"> — computes the checksum for data</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-Data-HMACs.html">Secure HMAC Digests</a></span><span class="refpurpose"> — computes the HMAC for data</span>
 </dt>
 <dt>
 <span class="refentrytitle"><a href="glib-I18N.html">Internationalization</a></span><span class="refpurpose"> — gettext support macros</span>
@@ -45,10 +49,10 @@
 <span class="refentrytitle"><a href="glib-Date-and-Time-Functions.html">Date and Time Functions</a></span><span class="refpurpose"> — calendrical calculations and miscellaneous time stuff</span>
 </dt>
 <dt>
-<span class="refentrytitle"><a href="glib-GTimeZone.html">GTimeZone</a></span><span class="refpurpose"> — A structure representing a time zone</span>
+<span class="refentrytitle"><a href="glib-GTimeZone.html">GTimeZone</a></span><span class="refpurpose"> — a structure representing a time zone</span>
 </dt>
 <dt>
-<span class="refentrytitle"><a href="glib-GDateTime.html">GDateTime</a></span><span class="refpurpose"> — A structure representing Date and Time</span>
+<span class="refentrytitle"><a href="glib-GDateTime.html">GDateTime</a></span><span class="refpurpose"> — a structure representing Date and Time</span>
 </dt>
 <dt>
 <span class="refentrytitle"><a href="glib-Random-Numbers.html">Random Numbers</a></span><span class="refpurpose"> — pseudo-random number generator</span>
@@ -63,10 +67,6 @@
 <span class="refentrytitle"><a href="glib-Lexical-Scanner.html">Lexical Scanner</a></span><span class="refpurpose"> — a general purpose lexical scanner</span>
 </dt>
 <dt>
-<span class="refentrytitle"><a href="glib-Automatic-String-Completion.html">Automatic String Completion</a></span><span class="refpurpose"> — support for automatic completion using a group
-                    of target strings</span>
-</dt>
-<dt>
 <span class="refentrytitle"><a href="glib-Timers.html">Timers</a></span><span class="refpurpose"> — keep track of elapsed time</span>
 </dt>
 <dt>
@@ -76,7 +76,7 @@
 <span class="refentrytitle"><a href="glib-File-Utilities.html">File Utilities</a></span><span class="refpurpose"> — various file-related functions</span>
 </dt>
 <dt>
-<span class="refentrytitle"><a href="glib-URI-Functions.html">URI Functions</a></span><span class="refpurpose"> — URI Functions</span>
+<span class="refentrytitle"><a href="glib-URI-Functions.html">URI Functions</a></span><span class="refpurpose"> — manipulating URIs</span>
 </dt>
 <dt>
 <span class="refentrytitle"><a href="glib-Hostname-Utilities.html">Hostname Utilities</a></span><span class="refpurpose"> — Internet hostname utilities</span>
@@ -95,10 +95,15 @@
 <span class="refentrytitle"><a href="glib-Perl-compatible-regular-expressions.html">Perl-compatible regular expressions</a></span><span class="refpurpose"> — matches strings against regular expressions</span>
 </dt>
 <dt>
+<span class="refentrytitle"><a href="glib-regex-syntax.html">Regular expression syntax</a></span><span class="refpurpose"> —
+syntax and semantics of regular expressions supported by GRegex
+</span>
+</dt>
+<dt>
 <span class="refentrytitle"><a href="glib-Simple-XML-Subset-Parser.html">Simple XML Subset Parser</a></span><span class="refpurpose"> — parses a subset of XML</span>
 </dt>
 <dt>
-<span class="refentrytitle"><a href="glib-Key-value-file-parser.html">Key-value file parser</a></span><span class="refpurpose"> — parses <code class="filename">.ini</code>-like config files</span>
+<span class="refentrytitle"><a href="glib-Key-value-file-parser.html">Key-value file parser</a></span><span class="refpurpose"> — parses .ini-like config files</span>
 </dt>
 <dt>
 <span class="refentrytitle"><a href="glib-Bookmark-file-parser.html">Bookmark file parser</a></span><span class="refpurpose"> — parses files containing bookmarks</span>
@@ -107,12 +112,15 @@
 <span class="refentrytitle"><a href="glib-Testing.html">Testing</a></span><span class="refpurpose"> — a test framework</span>
 </dt>
 <dt>
+<span class="refentrytitle"><a href="glib-UNIX-specific-utilities-and-integration.html">UNIX-specific utilities and integration</a></span><span class="refpurpose"> — pipes, signal handling</span>
+</dt>
+<dt>
 <span class="refentrytitle"><a href="glib-Windows-Compatibility-Functions.html">Windows Compatibility Functions</a></span><span class="refpurpose"> — UNIX emulation on Windows</span>
 </dt>
 </dl></div>
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.17</div>
+          Generated by GTK-Doc V1.18</div>
 </body>
 </html>