Fix doc format errors

This commit is contained in:
Matthias Clasen 2010-08-13 21:05:05 -04:00
parent 4160c5c74a
commit 63d19f0656
2 changed files with 3 additions and 3 deletions

View File

@ -94,7 +94,7 @@
* that use Glib do the same thing. If you get a file name from
* the file system, for example, from readdir(3) or from g_dir_read_name(),
* and you wish to display the file name to the user, you
* emphasis>will</emphasis> need to convert it into UTF-8. The
* <emphasis>will</emphasis> need to convert it into UTF-8. The
* opposite case is when the user types the name of a file he
* wishes to save: the toolkit will give you that string in
* UTF-8 encoding, and you will need to convert it to the
@ -172,7 +172,7 @@
* characters when <envar>G_FILENAME_ENCODING</envar> is set to
* <literal>ISO-8859-1</literal>, for example.
* </para></listitem>
* orderedlist>
* </orderedlist>
* </refsect3>
* </refsect2>
*/

View File

@ -37,7 +37,7 @@
* SECTION:gregex
* @title: Perl-compatible regular expressions
* @short_description: matches strings against regular expressions
* @see_also: <xref linkend="glib-regex-syntax">
* @see_also: <xref linkend="glib-regex-syntax"/>
*
* The <function>g_regex_*()</function> functions implement regular
* expression pattern matching using syntax and semantics similar to