luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-26 15:36:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: Correct octal format in gvariant-text-format

Browse Source 
There is no o or 0 prefix, just one to three octal numbers.
This commit is contained in:
Jan Tojnar 2024-05-19 00:31:25 +02:00
parent 701412530b
commit 56d8f14ab2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/glib/gvariant-text-format.md
View File

@ -92,7 +92,7 @@ following `\` is copied literally (for example, `\"` or `\\`) but for
forwards compatibility with future additions you should only use this forwards compatibility with future additions you should only use this
feature when necessary for escaping backslashes or quotes. feature when necessary for escaping backslashes or quotes.
The usual octal and hexadecimal escapes `\0nnn` and `\xnn` are not supported The usual octal and hexadecimal escapes `\nnn` and `\xnn` are not supported
here. Those escapes are used to encode byte values and `GVariant` strings here. Those escapes are used to encode byte values and `GVariant` strings
are Unicode. are Unicode.
@ -306,7 +306,7 @@ is no fundamental difference between the two different types of quotes.
Bytestrings support the full range of escapes that you would expect (ie: Bytestrings support the full range of escapes that you would expect (ie:
those supported by [`func@GLib.strcompress`]. This includes the normal control those supported by [`func@GLib.strcompress`]. This includes the normal control
sequence escapes (as mentioned in the section on strings) as well as octal sequence escapes (as mentioned in the section on strings) as well as octal
and hexadecimal escapes of the forms `\0nnn` and `\xnn`. and hexadecimal escapes of the forms `\nnn` and `\xnn`.
`b'abc'` is equivalent to `[byte 0x61, 0x62, 0x63, 0]`. `b'abc'` is equivalent to `[byte 0x61, 0x62, 0x63, 0]`.