RubyGems - glib2 - Versions diffs - 0.90.8-x86-mingw32 → 0.90.9-x86-mingw32 - Mend

glib2 0.90.8-x86-mingw32 → 0.90.9-x86-mingw32

Files changed (620) hide show

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

@@ -8,7 +8,7 @@
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib-running.html" title="Running GLib Applications">
 <link rel="next" href="glib-regex-syntax.html" title="Regular expression syntax">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-regex-syntax.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="refentry" title="Changes to GLib">
+<div class="refentry">
 <a name="glib-changes"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -30,8 +30,8 @@ Incompatible changes made between successing versions of GLib
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsect1" title="Incompatible changes from 2.0 to 2.2">
-<a name="id638729"></a><h2>Incompatible changes from 2.0 to 2.2</h2>
+<div class="refsect1">
+<a name="id426698"></a><h2>Incompatible changes from 2.0 to 2.2</h2>
 <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
 <p>
 GLib changed the seeding algorithm for the pseudo-random number
@@ -55,14 +55,8 @@ with Glib-2.0 that you need to reproduce exactly.
 </p>
 </li></ul></div>
 </div>
-<div class="refsect1" title="Incompatible changes from 1.2 to 2.0">
-<a name="id610044"></a><h2>Incompatible changes from 1.2 to 2.0</h2>
-<p>
-The <a class="ulink" href="http://developer.gnome.org/dotplan/porting/" target="_top">GNOME 2.0
-porting guide</a> on <a class="ulink" href="http://developer.gnome.org" target="_top">http://developer.gnome.org</a>
-has some more detailed discussion of porting from 1.2 to 2.0.
-See the section on GLib.
-</p>
+<div class="refsect1">
+<a name="id441678"></a><h2>Incompatible changes from 1.2 to 2.0</h2>
 <div class="itemizedlist"><ul class="itemizedlist" type="disc">
 <li class="listitem">
 <p>
@@ -154,6 +148,6 @@ Deprecated functions that got removed:
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib-cross-compiling.html" title="Cross-compiling the GLib package">
 <link rel="next" href="glib-running.html" title="Running GLib Applications">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-running.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="refentry" title="Compiling GLib Applications">
+<div class="refentry">
 <a name="glib-compiling"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -30,8 +30,8 @@ How to compile your GLib application
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsect1" title="Compiling GLib Applications on UNIX">
-<a name="id644944"></a><h2>Compiling GLib Applications on UNIX</h2>
+<div class="refsect1">
+<a name="id430781"></a><h2>Compiling GLib Applications on UNIX</h2>
 <p>
 To compile a GLib application, you need to tell the compiler where to
 find the GLib header files and libraries. This is done with the
@@ -113,6 +113,6 @@ by using the command line option <code class="literal">-DG_DISABLE_SINGLE_INCLUD
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="index.html" title="GLib Reference Manual">
 <link rel="prev" href="glib-Atomic-Operations.html" title="Atomic Operations">
 <link rel="next" href="glib-The-Main-Event-Loop.html" title="The Main Event Loop">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-The-Main-Event-Loop.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="chapter" title="GLib Core Application Support">
+<div class="chapter">
 <div class="titlepage"><div><div><h2 class="title">
 <a name="glib-core"></a>GLib Core Application Support</h2></div></div></div>
 <div class="toc"><dl>
@@ -59,6 +59,6 @@
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib-building.html" title="Compiling the GLib package">
 <link rel="next" href="glib-compiling.html" title="Compiling GLib Applications">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-compiling.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="refentry" title="Cross-compiling the GLib package">
+<div class="refentry">
 <a name="glib-cross-compiling"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -30,7 +30,7 @@ How to cross-compile GLib
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsect1" title="Building the Library for a different architecture">
+<div class="refsect1">
 <a name="cross"></a><h2>Building the Library for a different architecture</h2>
 <p>
         Cross-compilation is the process of compiling a program or
@@ -74,9 +74,9 @@ chmod a-w win32.cache   # prevent configure from changing it
          of these won't need to be set in most cases.
       </p>
 </div>
-<div class="refsect1" title="Cache file variables">
+<div class="refsect1">
 <a name="cache-file-variables"></a><h2>Cache file variables</h2>
-<p title="glib_cv_long_long_format=[ll/q/I64]"><b>glib_cv_long_long_format=[ll/q/I64]. </b>
+<p><b>glib_cv_long_long_format=[ll/q/I64]. </b>
            Format used by <code class="function">printf()</code> and
            <code class="function">scanf()</code> for 64 bit integers. "ll" is
            the C99 standard, and what is used by the 'trio' library
@@ -84,68 +84,68 @@ chmod a-w win32.cache   # prevent configure from changing it
            insufficiently capable.
            Doesn't need to be set if you are compiling using trio.
         </p>
-<p title="glib_cv_stack_grows=[yes/no]"><b>glib_cv_stack_grows=[yes/no]. </b>
+<p><b>glib_cv_stack_grows=[yes/no]. </b>
            Whether the stack grows up or down. Most places will want "no",
            A few architectures, such as PA-RISC need "yes".
         </p>
-<p title="glib_cv_working_bcopy=[yes/no]"><b>glib_cv_working_bcopy=[yes/no]. </b>
+<p><b>glib_cv_working_bcopy=[yes/no]. </b>
            Whether your <code class="function">bcopy()</code> can handle overlapping
            copies. Only needs to be set if you don't have
            <code class="function">memmove()</code>. (Very unlikely)
 	</p>
-<p title="glib_cv_sane_realloc=[yes/np]"><b>glib_cv_sane_realloc=[yes/np]. </b>
+<p><b>glib_cv_sane_realloc=[yes/np]. </b>
             Whether your <code class="function">realloc()</code> conforms to ANSI C
             and can handle <code class="literal">NULL</code> as the first argument.
             Defaults to "yes" and probably doesn't need to be set.
 	</p>
-<p title="glib_cv_have_strlcpy=[yes/no]"><b>glib_cv_have_strlcpy=[yes/no]. </b>
+<p><b>glib_cv_have_strlcpy=[yes/no]. </b>
             Whether you have <code class="function">strlcpy()</code> that matches
             OpenBSD. Defaults to "no", which is safe, since GLib uses a
             built-in version in that case.
 	</p>
-<p title="glib_cv_va_val_copy=[yes/no]"><b>glib_cv_va_val_copy=[yes/no]. </b>
+<p><b>glib_cv_va_val_copy=[yes/no]. </b>
             Whether <span class="type">va_list</span> can be copied as a pointer. If set
             to "no", then <code class="function">memcopy()</code> will be used. Only
             matters if you don't have <code class="function">va_copy()</code> or
             <code class="function">__va_copy()</code>. (So, doesn't matter for GCC.)
             Defaults to "yes" which is slightly more common than "no".
 	</p>
-<p title="glib_cv_rtldglobal_broken=[yes/no]"><b>glib_cv_rtldglobal_broken=[yes/no]. </b>
+<p><b>glib_cv_rtldglobal_broken=[yes/no]. </b>
             Whether you have a bug found in OSF/1 v5.0. Defaults to "no".
          </p>
-<p title="glib_cv_uscore=[yes/no]"><b>glib_cv_uscore=[yes/no]. </b>
+<p><b>glib_cv_uscore=[yes/no]. </b>
             Whether an underscore needs to be prepended to symbols when
             looking them up via <code class="function">dlsym()</code>. Only needs to
             be set if your system uses
 	    <code class="function">dlopen()</code>/<code class="function">dlsym()</code>.
 	 </p>
-<p title="ac_cv_func_posix_getpwuid_r=[yes/no]"><b>ac_cv_func_posix_getpwuid_r=[yes/no]. </b>
+<p><b>ac_cv_func_posix_getpwuid_r=[yes/no]. </b>
             Whether you have a getpwuid_r function (in your C library,
 	    not your thread library) that conforms to the POSIX spec.
             (Takes a 'struct passwd **' as the final argument)
          </p>
-<p title="ac_cv_func_nonposix_getpwuid_r=[yes/no]"><b>ac_cv_func_nonposix_getpwuid_r=[yes/no]. </b>
+<p><b>ac_cv_func_nonposix_getpwuid_r=[yes/no]. </b>
             Whether you have some variant of <code class="function">getpwuid_r()</code>
             that doesn't conform to to the POSIX spec, but GLib might be able
             to use (or might segfault.) Only needs to be set if
 	    <code class="literal">ac_cv_func_posix_getpwuid_r</code> is not set. It's
             safest to set this to "no".
          </p>
-<p title="ac_cv_func_posix_getgrgid_r=[yes/no]"><b>ac_cv_func_posix_getgrgid_r=[yes/no]. </b>
+<p><b>ac_cv_func_posix_getgrgid_r=[yes/no]. </b>
             Whether you have a getgrgid_r function that conforms to
             the POSIX spec.
          </p>
-<p title="glib_cv_use_pid_surrogate=[yes/no]"><b>glib_cv_use_pid_surrogate=[yes/no]. </b>
+<p><b>glib_cv_use_pid_surrogate=[yes/no]. </b>
             Whether to use a <code class="function">setpriority()</code> on the PID of
             the thread as a method for setting the priority of threads. This
             only needs to be set when using POSIX threads.
          </p>
-<p title="ac_cv_func_printf_unix98=[yes/no]"><b>ac_cv_func_printf_unix98=[yes/no]. </b>
+<p><b>ac_cv_func_printf_unix98=[yes/no]. </b>
            Whether your <code class="function">printf()</code> family supports Unix98
            style <code class="literal">%N$</code> positional parameters. Defaults to
 	"no".
          </p>
-<p title="ac_cv_func_vsnprintf_c99=[yes/no]"><b>ac_cv_func_vsnprintf_c99=[yes/no]. </b>
+<p><b>ac_cv_func_vsnprintf_c99=[yes/no]. </b>
             Whether you have a <code class="function">vsnprintf()</code> with C99
             semantics. (C99 semantics means returning the number of bytes
             that would have been written had the output buffer had enough
@@ -155,6 +155,6 @@ chmod a-w win32.cache   # prevent configure from changing it
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="index.html" title="GLib Reference Manual">
 <link rel="prev" href="glib-Windows-Compatibility-Functions.html" title="Windows Compatibility Functions">
 <link rel="next" href="glib-Memory-Slices.html" title="Memory Slices">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-Memory-Slices.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="chapter" title="GLib Data Types">
+<div class="chapter">
 <div class="titlepage"><div><div><h2 class="title">
 <a name="glib-data-types"></a>GLib Data Types</h2></div></div></div>
 <div class="toc"><dl>
@@ -111,10 +111,13 @@
 <dt>
 <span class="refentrytitle"><a href="gvariant-format-strings.html">GVariant Format Strings</a></span><span class="refpurpose"></span>
 </dt>
+<dt>
+<span class="refentrytitle"><a href="gvariant-text.html">GVariant Text Format</a></span><span class="refpurpose"></span>
+</dt>
 </dl></div>
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="index.html" title="GLib Reference Manual">
 <link rel="prev" href="glib-resources.html" title="Mailing lists and bug reports">
 <link rel="next" href="glib-Version-Information.html" title="Version Information">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-Version-Information.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="chapter" title="GLib Fundamentals">
+<div class="chapter">
 <div class="titlepage"><div><div><h2 class="title">
 <a name="glib-fundamentals"></a>GLib Fundamentals</h2></div></div></div>
 <div class="toc"><dl>
@@ -54,6 +54,6 @@
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="tools.html" title="GLib Tools">
 <link rel="prev" href="tools.html" title="GLib Tools">
 <link rel="next" href="gtester.html" title="gtester">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="gtester.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div lang="en" class="refentry" title="glib-gettextize">
+<div lang="en" class="refentry">
 <a name="glib-gettextize"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -28,12 +28,12 @@
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsynopsisdiv" title="Synopsis">
+<div class="refsynopsisdiv">
 <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">glib-gettextize</code>  [option...] [directory]</p></div>
 </div>
-<div class="refsect1" title="Description">
-<a name="id860664"></a><h2>Description</h2>
+<div class="refsect1">
+<a name="id443830"></a><h2>Description</h2>
 <p><span class="command"><strong>glib-gettextize</strong></span> helps to prepare a source package for being
 internationalized through <span class="application">gettext</span>.
 It is a variant of the <span class="command"><strong>gettextize</strong></span> that ships with
@@ -46,8 +46,8 @@ from <span class="command"><strong>gettextize</strong></span> in that it doesn't
 <span class="command"><strong>gettextize</strong></span> behave like this when called with the
 <code class="option">--no-changelog</code> option).
 </p>
-<div class="refsect2" title="Options">
-<a name="id753897"></a><h3>Options</h3>
+<div class="refsect2">
+<a name="id432375"></a><h3>Options</h3>
 <div class="variablelist"><table border="0">
 <col align="left" valign="top">
 <tbody>
@@ -79,8 +79,8 @@ force writing of new files even if old ones exist
 </table></div>
 </div>
 </div>
-<div class="refsect1" title="See also">
-<a name="id643899"></a><h2>See also</h2>
+<div class="refsect1">
+<a name="id412014"></a><h2>See also</h2>
 <p>
 <span class="citerefentry"><span class="refentrytitle">gettextize</span>(1)</span>
 </p>
@@ -88,6 +88,6 @@ force writing of new files even if old ones exist
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib-changes.html" title="Changes to GLib">
 <link rel="next" href="glib-resources.html" title="Mailing lists and bug reports">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-resources.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="refentry" title="Regular expression syntax">
+<div class="refentry">
 <a name="glib-regex-syntax"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -30,8 +30,8 @@ Syntax and semantics of the regular expressions supported by GRegex
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsect1" title="GRegex regular expression details">
-<a name="id637399"></a><h2>GRegex regular expression details</h2>
+<div class="refsect1">
+<a name="id430086"></a><h2>GRegex regular expression details</h2>
 <p>
 A regular expression is a pattern that is matched against a
 string from left to right. Most characters stand for themselves in a
@@ -59,7 +59,7 @@ that are recognized in square brackets. Outside square brackets, the
 metacharacters are as follows:
 </p>
 <div class="table">
-<a name="id608603"></a><p class="title"><b>Table 1. Metacharacters outside square brackets</b></p>
+<a name="id436351"></a><p class="title"><b>Table 1. Metacharacters outside square brackets</b></p>
 <div class="table-contents"><table summary="Metacharacters outside square brackets" border="1">
 <colgroup>
 <col align="center">
@@ -126,7 +126,7 @@ Part of a pattern that is in square brackets is called a "character
 class". In a character class the only metacharacters are:
 </p>
 <div class="table">
-<a name="id645119"></a><p class="title"><b>Table 2. Metacharacters inside square brackets</b></p>
+<a name="id412455"></a><p class="title"><b>Table 2. Metacharacters inside square brackets</b></p>
 <div class="table-contents"><table summary="Metacharacters inside square brackets" border="1">
 <colgroup>
 <col align="center">
@@ -162,8 +162,8 @@ class". In a character class the only metacharacters are:
 </div>
 <br class="table-break">
 </div>
-<div class="refsect1" title="Backslash">
-<a name="id607979"></a><h2>Backslash</h2>
+<div class="refsect1">
+<a name="id417983"></a><h2>Backslash</h2>
 <p>
 The backslash character has several uses. Firstly, if it is followed by
 a non-alphanumeric character, it takes away any special meaning that
@@ -197,8 +197,8 @@ you can do so by putting them between \Q and \E.
 The \Q...\E sequence is recognized both inside and outside character
 classes.
 </p>
-<div class="refsect2" title="Non-printing characters">
-<a name="id608018"></a><h3>Non-printing characters</h3>
+<div class="refsect2">
+<a name="id418022"></a><h3>Non-printing characters</h3>
 <p>
 A second use of backslash provides a way of encoding non-printing
 characters in patterns in a visible manner. There is no restriction on the
@@ -208,7 +208,7 @@ editing, it is usually easier to use one of the following escape
 sequences than the binary character it represents:
 </p>
 <div class="table">
-<a name="id608031"></a><p class="title"><b>Table 3. Non-printing characters</b></p>
+<a name="id418035"></a><p class="title"><b>Table 3. Non-printing characters</b></p>
 <div class="table-contents"><table summary="Non-printing characters" border="1">
 <colgroup>
 <col align="center">
@@ -309,7 +309,7 @@ up to three octal digits following the backslash, and uses them to generate
 a data character. Any subsequent digits stand for themselves. For example:
 </p>
 <div class="table">
-<a name="id648715"></a><p class="title"><b>Table 4. Non-printing characters</b></p>
+<a name="id451236"></a><p class="title"><b>Table 4. Non-printing characters</b></p>
 <div class="table-contents"><table summary="Non-printing characters" border="1">
 <colgroup>
 <col align="center">
@@ -372,8 +372,8 @@ Outside a character class, these sequences have different meanings (see below).
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Absolute and relative back references">
-<a name="id648875"></a><h3>Absolute and relative back references</h3>
+<div class="refsect2">
+<a name="id451396"></a><h3>Absolute and relative back references</h3>
 <p>
 The sequence \g followed by a positive or negative number, optionally enclosed
 in braces, is an absolute or relative back reference. Back references are
@@ -381,14 +381,14 @@ discussed later, following the discussion of parenthesized subpatterns.
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Generic character types">
-<a name="id648888"></a><h3>Generic character types</h3>
+<div class="refsect2">
+<a name="id451409"></a><h3>Generic character types</h3>
 <p>
 Another use of backslash is for specifying generic character types.
 The following are always recognized:
 </p>
 <div class="table">
-<a name="id648899"></a><p class="title"><b>Table 5. Generic characters</b></p>
+<a name="id451420"></a><p class="title"><b>Table 5. Generic characters</b></p>
 <div class="table-contents"><table summary="Generic characters" border="1">
 <colgroup>
 <col align="center">
@@ -451,8 +451,8 @@ Characters with values greater than 128 never match \d,
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Newline sequences">
-<a name="id649038"></a><h3>Newline sequences</h3>
+<div class="refsect2">
+<a name="id451559"></a><h3>Newline sequences</h3>
 <p>Outside a character class, the escape sequence \R matches any Unicode
 newline sequence.
 This particular group matches either the two-character sequence CR followed by
@@ -463,14 +463,14 @@ The two-character sequence is treated as a single unit that
 cannot be split. Inside a character class, \R matches the letter "R".</p>
 </div>
 <hr>
-<div class="refsect2" title="Unicode character properties">
-<a name="id649053"></a><h3>Unicode character properties</h3>
+<div class="refsect2">
+<a name="id451574"></a><h3>Unicode character properties</h3>
 <p>
 To support generic character types there are three additional escape
 sequences, they are:
 </p>
 <div class="table">
-<a name="id649064"></a><p class="title"><b>Table 6. Generic character types</b></p>
+<a name="id451585"></a><p class="title"><b>Table 6. Generic character types</b></p>
 <div class="table-contents"><table summary="Generic character types" border="1">
 <colgroup>
 <col align="center">
@@ -537,7 +537,7 @@ documentation for the #GUnicodeType enumeration, the following
 general category property codes are supported:
 </p>
 <div class="table">
-<a name="id649184"></a><p class="title"><b>Table 7. Property codes</b></p>
+<a name="id451703"></a><p class="title"><b>Table 7. Property codes</b></p>
 <div class="table-contents"><table summary="Property codes" border="1">
 <colgroup>
 <col align="center">
@@ -619,8 +619,8 @@ characters. That is why the traditional escape sequences such as \d and
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Simple assertions">
-<a name="id649351"></a><h3>Simple assertions</h3>
+<div class="refsect2">
+<a name="id451871"></a><h3>Simple assertions</h3>
 <p>
 The final use of backslash is for certain simple assertions. An
 assertion specifies a condition that has to be met at a particular point in
@@ -629,7 +629,7 @@ use of subpatterns for more complicated assertions is described below.
 The backslashed assertions are:
 </p>
 <div class="table">
-<a name="id649364"></a><p class="title"><b>Table 8. Simple assertions</b></p>
+<a name="id451883"></a><p class="title"><b>Table 8. Simple assertions</b></p>
 <div class="table-contents"><table summary="Simple assertions" border="1">
 <colgroup>
 <col align="center">
@@ -710,8 +710,8 @@ in the compiled regular expression.
 </p>
 </div>
 </div>
-<div class="refsect1" title="Circumflex and dollar">
-<a name="id649524"></a><h2>Circumflex and dollar</h2>
+<div class="refsect1">
+<a name="id452043"></a><h2>Circumflex and dollar</h2>
 <p>
 Outside a character class, in the default matching mode, the circumflex
 character is an assertion that is true only if the current matching
@@ -768,8 +768,8 @@ end of the string in both modes, and if all branches of a pattern start with
 is set.
 </p>
 </div>
-<div class="refsect1" title="Full stop (period, dot)">
-<a name="id649605"></a><h2>Full stop (period, dot)</h2>
+<div class="refsect1">
+<a name="id452124"></a><h2>Full stop (period, dot)</h2>
 <p>
 Outside a character class, a dot in the pattern matches any one character
 in the string, including a non-printing character, but not (by
@@ -801,8 +801,8 @@ dollar, the only relationship being that they both involve newlines. Dot has no
 special meaning in a character class.
 </p>
 </div>
-<div class="refsect1" title="Matching a single byte">
-<a name="id649648"></a><h2>Matching a single byte</h2>
+<div class="refsect1">
+<a name="id452167"></a><h2>Matching a single byte</h2>
 <p>
 Outside a character class, the escape sequence \C matches any one byte,
 both in and out of UTF-8 mode. Unlike a dot, it always matches any line
@@ -818,8 +818,8 @@ below), because in UTF-8 mode this would make it impossible to calculate
 the length of the lookbehind.
 </p>
 </div>
-<div class="refsect1" title="Square brackets and character classes">
-<a name="id649668"></a><h2>Square brackets and character classes</h2>
+<div class="refsect1">
+<a name="id452187"></a><h2>Square brackets and character classes</h2>
 <p>
 An opening square bracket introduces a character class, terminated by a
 closing square bracket. A closing square bracket on its own is not special. If a closing square bracket is required as a member of the class,
@@ -903,8 +903,8 @@ next section), and the terminating closing square bracket. However,
 escaping other non-alphanumeric characters does no harm.
 </p>
 </div>
-<div class="refsect1" title="Posix character classes">
-<a name="id649754"></a><h2>Posix character classes</h2>
+<div class="refsect1">
+<a name="id452273"></a><h2>Posix character classes</h2>
 <p>
 GRegex supports the POSIX notation for character classes. This uses names
 enclosed by [: and :] within the enclosing square brackets. For example,
@@ -917,7 +917,7 @@ matches "0", "1", any alphabetic character, or "%". The supported class
 names are
 </p>
 <div class="table">
-<a name="id649774"></a><p class="title"><b>Table 9. Posix classes</b></p>
+<a name="id452293"></a><p class="title"><b>Table 9. Posix classes</b></p>
 <div class="table-contents"><table summary="Posix classes" border="1">
 <colgroup>
 <col align="center">
@@ -1011,8 +1011,8 @@ In UTF-8 mode, characters with values greater than 128 do not match any
 of the POSIX character classes.
 </p>
 </div>
-<div class="refsect1" title="Vertical bar">
-<a name="id650005"></a><h2>Vertical bar</h2>
+<div class="refsect1">
+<a name="id452524"></a><h2>Vertical bar</h2>
 <p>
 Vertical bar characters are used to separate alternative patterns. For
 example, the pattern
@@ -1027,8 +1027,8 @@ string). The matching process tries each alternative in turn, from
 left to right, and the first one that succeeds is used. If the alternatives are within a subpattern (defined below), "succeeds" means matching the rest of the main pattern as well as the alternative in the subpattern.
 </p>
 </div>
-<div class="refsect1" title="Internal option setting">
-<a name="id650030"></a><h2>Internal option setting</h2>
+<div class="refsect1">
+<a name="id452549"></a><h2>Internal option setting</h2>
 <p>
 The settings of the <code class="varname">G_REGEX_CASELESS</code>, <code class="varname">G_REGEX_MULTILINE</code>, <code class="varname">G_REGEX_MULTILINE</code>,
 and <code class="varname">G_REGEX_EXTENDED</code> options can be changed from within the pattern by a
@@ -1036,7 +1036,7 @@ sequence of Perl-style option letters enclosed between "(?" and ")". The
 option letters are
 </p>
 <div class="table">
-<a name="id650056"></a><p class="title"><b>Table 10. Option settings</b></p>
+<a name="id452575"></a><p class="title"><b>Table 10. Option settings</b></p>
 <div class="table-contents"><table summary="Option settings" border="1">
 <colgroup>
 <col align="center">
@@ -1109,8 +1109,8 @@ can be changed in the same way as the Perl-compatible options by using
 the characters U, X and J respectively.
 </p>
 </div>
-<div class="refsect1" title="Subpatterns">
-<a name="id650225"></a><h2>Subpatterns</h2>
+<div class="refsect1">
+<a name="id452744"></a><h2>Subpatterns</h2>
 <p>
 Subpatterns are delimited by parentheses (round brackets), which can be
 nested. Turning part of a pattern into a subpattern does two things:
@@ -1173,8 +1173,8 @@ subsequent branches, so the above patterns match "SUNDAY" as well as
 "Saturday".
 </p>
 </div>
-<div class="refsect1" title="Named subpatterns">
-<a name="id650310"></a><h2>Named subpatterns</h2>
+<div class="refsect1">
+<a name="id452830"></a><h2>Named subpatterns</h2>
 <p>
 Identifying capturing parentheses by number is simple, but it can be
 very hard to keep track of the numbers in complicated regular expressions.
@@ -1214,8 +1214,8 @@ make a reference to a non-unique named subpattern from elsewhere in the
 pattern, the one that corresponds to the lowest number is used.
 </p>
 </div>
-<div class="refsect1" title="Repetition">
-<a name="id650352"></a><h2>Repetition</h2>
+<div class="refsect1">
+<a name="id452872"></a><h2>Repetition</h2>
 <p>
 Repetition is specified by quantifiers, which can follow any of the
 following items:
@@ -1278,7 +1278,7 @@ For convenience, the three most common quantifiers have single-character
 abbreviations:
 </p>
 <div class="table">
-<a name="id650464"></a><p class="title"><b>Table 11. Abbreviations for quantifiers</b></p>
+<a name="id452985"></a><p class="title"><b>Table 11. Abbreviations for quantifiers</b></p>
 <div class="table-contents"><table summary="Abbreviations for quantifiers" border="1">
 <colgroup>
 <col align="center">
@@ -1418,8 +1418,8 @@ For example, after
 matches "aba" the value of the second captured substring is "b".
 </p>
 </div>
-<div class="refsect1" title="Atomic grouping and possessive quantifiers">
-<a name="id650692"></a><h2>Atomic grouping and possessive quantifiers</h2>
+<div class="refsect1">
+<a name="id453213"></a><h2>Atomic grouping and possessive quantifiers</h2>
 <p>
 With both maximizing ("greedy") and minimizing ("ungreedy" or "lazy")
 repetition, failure of what follows normally causes the repeated
@@ -1536,8 +1536,8 @@ group, like this:
 sequences of non-digits cannot be broken, and failure happens quickly.
 </p>
 </div>
-<div class="refsect1" title="Back references">
-<a name="id653186"></a><h2>Back references</h2>
+<div class="refsect1">
+<a name="id455849"></a><h2>Back references</h2>
 <p>
 Outside a character class, a backslash followed by a digit greater than
 0 (and possibly further digits) is a back reference to a capturing subpattern
@@ -1645,8 +1645,8 @@ to match the back reference. This can be done using alternation, as in
 the example above, or by a quantifier with a minimum of zero.
 </p>
 </div>
-<div class="refsect1" title="Assertions">
-<a name="id653313"></a><h2>Assertions</h2>
+<div class="refsect1">
+<a name="id455976"></a><h2>Assertions</h2>
 <p>
 An assertion is a test on the characters following or preceding the
 current matching point that does not actually consume any characters.
@@ -1669,8 +1669,8 @@ subpatterns in the whole pattern. However, substring capturing is carried
 out only for positive assertions, because it does not make sense for
 negative assertions.
 </p>
-<div class="refsect2" title="Lookahead assertions">
-<a name="id653338"></a><h3>Lookahead assertions</h3>
+<div class="refsect2">
+<a name="id456000"></a><h3>Lookahead assertions</h3>
 <p>
 Lookahead assertions start with (?= for positive assertions and (?! for
 negative assertions. For example,
@@ -1706,8 +1706,8 @@ string must always fail.
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Lookbehind assertions">
-<a name="id653388"></a><h3>Lookbehind assertions</h3>
+<div class="refsect2">
+<a name="id456051"></a><h3>Lookbehind assertions</h3>
 <p>
 Lookbehind assertions start with (?&lt;= for positive assertions and (?&lt;!
 for negative assertions. For example,
@@ -1795,8 +1795,8 @@ processing time.
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Using multiple assertions">
-<a name="id653503"></a><h3>Using multiple assertions</h3>
+<div class="refsect2">
+<a name="id456166"></a><h3>Using multiple assertions</h3>
 <p>
 Several assertions (of any sort) may occur in succession. For example,
 </p>
@@ -1840,8 +1840,8 @@ three characters that are not "999".
 </p>
 </div>
 </div>
-<div class="refsect1" title="Conditional subpatterns">
-<a name="id653566"></a><h2>Conditional subpatterns</h2>
+<div class="refsect1">
+<a name="id456229"></a><h2>Conditional subpatterns</h2>
 <p>
 It is possible to cause the matching process to obey a subpattern
 conditionally or to choose between two alternative subpatterns, depending
@@ -1861,8 +1861,8 @@ in the subpattern, a compile-time error occurs.
 There are four kinds of condition: references to subpatterns, references to
 recursion, a pseudo-condition called DEFINE, and assertions.
 </p>
-<div class="refsect2" title="Checking for a used subpattern by number">
-<a name="id653595"></a><h3>Checking for a used subpattern by number</h3>
+<div class="refsect2">
+<a name="id456258"></a><h3>Checking for a used subpattern by number</h3>
 <p>
 If the text between the parentheses consists of a sequence of digits, the
 condition is true if the capturing subpattern of that number has previously
@@ -1890,8 +1890,8 @@ optionally enclosed in parentheses.
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Checking for a used subpattern by name">
-<a name="id653631"></a><h3>Checking for a used subpattern by name</h3>
+<div class="refsect2">
+<a name="id456294"></a><h3>Checking for a used subpattern by name</h3>
 <p>
 Perl uses the syntax (?(&lt;name&gt;)...) or (?('name')...) to test for a used
 subpattern by name, the Python syntax (?(name)...) is also recognized. However,
@@ -1909,8 +1909,8 @@ Rewriting the above example to use a named subpattern gives this:
 </pre>
 </div>
 <hr>
-<div class="refsect2" title="Checking for pattern recursion">
-<a name="id653656"></a><h3>Checking for pattern recursion</h3>
+<div class="refsect2">
+<a name="id456319"></a><h3>Checking for pattern recursion</h3>
 <p>
 If the condition is the string (R), and there is no subpattern with the name R,
 the condition is true if a recursive call to the whole pattern or any
@@ -1932,8 +1932,8 @@ patterns are described below.
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Defining subpatterns for use by reference only">
-<a name="id653685"></a><h3>Defining subpatterns for use by reference only</h3>
+<div class="refsect2">
+<a name="id456348"></a><h3>Defining subpatterns for use by reference only</h3>
 <p>
 If the condition is the string (DEFINE), and there is no subpattern with the
 name DEFINE, the condition is always false. In this case, there may be only one
@@ -1960,8 +1960,8 @@ each end.
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Assertion conditions">
-<a name="id653718"></a><h3>Assertion conditions</h3>
+<div class="refsect2">
+<a name="id456381"></a><h3>Assertion conditions</h3>
 <p>
 If the condition is not in any of the above formats, it must be an
 assertion. This may be a positive or negative lookahead or lookbehind
@@ -1983,8 +1983,8 @@ letters and dd are digits.
 </p>
 </div>
 </div>
-<div class="refsect1" title="Comments">
-<a name="id653746"></a><h2>Comments</h2>
+<div class="refsect1">
+<a name="id456409"></a><h2>Comments</h2>
 <p>
 The sequence (?# marks the start of a comment that continues up to the
 next closing parenthesis. Nested parentheses are not permitted. The
@@ -1997,8 +1997,8 @@ character outside a character class introduces a comment that continues to
 immediately after the next newline in the pattern.
 </p>
 </div>
-<div class="refsect1" title="Recursive patterns">
-<a name="id653768"></a><h2>Recursive patterns</h2>
+<div class="refsect1">
+<a name="id456431"></a><h2>Recursive patterns</h2>
 <p>
 Consider the problem of matching a string in parentheses, allowing for
 unlimited nested parentheses. Without the use of recursion, the best
@@ -2129,8 +2129,8 @@ two different alternatives for the recursive and non-recursive cases.
 The (?R) item is the actual recursive call.
 </p>
 </div>
-<div class="refsect1" title="Subpatterns as subroutines">
-<a name="id653925"></a><h2>Subpatterns as subroutines</h2>
+<div class="refsect1">
+<a name="id456588"></a><h2>Subpatterns as subroutines</h2>
 <p>
 If the syntax for a recursive subpattern reference (either by number or
 by name) is used outside the parentheses to which it refers, it operates
@@ -2171,8 +2171,8 @@ It matches "abcabc". It does not match "abcABC" because the change of
 processing option does not affect the called subpattern.
 </p>
 </div>
-<div class="refsect1" title="Copyright">
-<a name="id653999"></a><h2>Copyright</h2>
+<div class="refsect1">
+<a name="id456662"></a><h2>Copyright</h2>
 <p>
 This document was copied and adapted from the PCRE documentation,
 specifically from the man page for pcrepattern.
@@ -2212,6 +2212,6 @@ POSSIBILITY OF SUCH DAMAGE.
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>