docs: Remove hex escape mention in gvariant-text-format bytestring

bytestring_parse does not actually support hexadecimal escape sequences.
This commit is contained in:
Jan Tojnar 2024-05-19 01:21:18 +02:00 committed by Philip Withnall
parent 460a9c299c
commit c068c1cd74

View File

@ -306,9 +306,9 @@ is no fundamental difference between the two different types of quotes.
Like in strings, the [C-style control sequence escapes][C escape sequences] Like in strings, the [C-style control sequence escapes][C escape sequences]
`\a`, `\b`, `\f`, `\n`, `\r`, `\t` and `\v` are supported. Similarly, `\a`, `\b`, `\f`, `\n`, `\r`, `\t` and `\v` are supported. Similarly,
a `\` before a newline character causes the newline to be ignored. a `\` before a newline character causes the newline to be ignored.
Unlike in strings, you can use octal and hexadecimal escapes Unlike in strings, you can use octal escapes of the form `\nnn`.
of the forms `\nnn` and `\xnn`. Finally, any other character following `\` Finally, any other character following `\` is copied literally
is copied literally (for example, `\"` or `\\`) but for forwards compatibility (for example, `\"` or `\\`) but for forwards compatibility
with future additions you should only use this feature when necessary with future additions you should only use this feature when necessary
for escaping backslashes or quotes. Unlike in strings, Unicode escapes for escaping backslashes or quotes. Unlike in strings, Unicode escapes
are not supported. are not supported.