luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-01-14 08:16:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

GVariant: titlecase ‘Unicode’ in text format docs

Browse Source
This commit is contained in:
Will Thompson 2011-02-11 19:09:48 +00:00
parent c3fe071813
commit dfeb02ee86
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/reference/glib/gvariant-text.xml
View File

@ -18,7 +18,7 @@
<para> <para>
The functions that deal with GVariant text format absolutely always deal in utf-8. Conceptually, GVariant The functions that deal with GVariant text format absolutely always deal in utf-8. Conceptually, GVariant
text format is a string of unicode characters -- not bytes. Non-ASCII but otherwise printable unicode text format is a string of Unicode characters -- not bytes. Non-ASCII but otherwise printable Unicode
characters are not treated any differently from normal ASCII characters. characters are not treated any differently from normal ASCII characters.
</para> </para>
@ -276,10 +276,10 @@
completely equivalent (except for the fact that each one is unable to contain itself unescaped). completely equivalent (except for the fact that each one is unable to contain itself unescaped).
</para> </para>
<para> <para>
Strings are unicode strings with no particular encoding. For example, to specify the character Strings are Unicode strings with no particular encoding. For example, to specify the character
<literal>é</literal>, you just write <literal>'é'</literal>. You could also give the unicode codepoint of <literal>é</literal>, you just write <literal>'é'</literal>. You could also give the Unicode codepoint of
that character (U+E9) as the escape sequence <literal>'\u00e9'</literal>. Since the strings are pure that character (U+E9) as the escape sequence <literal>'\u00e9'</literal>. Since the strings are pure
unicode, you should not attempt to encode the utf-8 byte sequence corresponding to the string using escapes; Unicode, you should not attempt to encode the utf-8 byte sequence corresponding to the string using escapes;
it won't work and you'll end up with the individual characters corresponding to each byte. it won't work and you'll end up with the individual characters corresponding to each byte.
</para> </para>
<para> <para>
@ -293,7 +293,7 @@
</para> </para>
<para> <para>
The usual octal and hexidecimal escapes <literal>\0nnn</literal> and <literal>\xnn</literal> are not The usual octal and hexidecimal escapes <literal>\0nnn</literal> and <literal>\xnn</literal> are not
supported here. Those escapes are used to encode byte values and GVariant strings are unicode. supported here. Those escapes are used to encode byte values and GVariant strings are Unicode.
</para> </para>
<para> <para>
Single-character strings are not interpreted as bytes. Bytes must be specified by their numerical value. Single-character strings are not interpreted as bytes. Bytes must be specified by their numerical value.