summaryrefslogtreecommitdiff
path: root/man/systemd.syntax.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-03-01 20:53:22 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-03-01 20:57:36 +0100
commit1447d87a47db0d0c522e633b45c495635e8e7606 (patch)
treed8acd30a8211b8ec0379b2f0b7e5c7bf76456cbf /man/systemd.syntax.xml
parent07dc08c2692a4503cc95e89138c9dfbd9d9c3060 (diff)
downloadsystemd-1447d87a47db0d0c522e633b45c495635e8e7606.tar.gz
man: document \u and \U, say that utf-8 is allowed
Diffstat (limited to 'man/systemd.syntax.xml')
-rw-r--r--man/systemd.syntax.xml20
1 files changed, 14 insertions, 6 deletions
diff --git a/man/systemd.syntax.xml b/man/systemd.syntax.xml
index 5f207912b9..e900747ae7 100644
--- a/man/systemd.syntax.xml
+++ b/man/systemd.syntax.xml
@@ -136,14 +136,14 @@ KeyThree=value 3\
single quotes ('…') may be used to wrap a whole item (the opening quote may appear only at the beginning
or after whitespace that is not quoted, and the closing quote must be followed by whitespace or the end
of line), in which case everything until the next matching quote becomes part of the same item. Quotes
- themselves are removed. C-style escapes are also supported. The table below contains the list of known
- escape patterns. Only escape patterns which match the syntax in the table are allowed; other patterns may
- be added in the future and unknown patterns will result in a warning. In particular, any backslashes
- should be doubled. Finally, a trailing backslash (<literal>\</literal>) may be used to merge lines, as
- described above.</para>
+ themselves are removed. C-style escapes are supported. The table below contains the list of known escape
+ patterns. Only escape patterns which match the syntax in the table are allowed; other patterns may be
+ added in the future and unknown patterns will result in a warning. In particular, any backslashes should
+ be doubled. Finally, a trailing backslash (<literal>\</literal>) may be used to merge lines, as described
+ above. UTF-8 is accepted, and hence typical unicode characters do not need to be escaped.</para>
<table>
- <title>Supported C escapes</title>
+ <title>Supported escapes</title>
<tgroup cols='2'>
<colspec colname='escape' />
<colspec colname='meaning' />
@@ -206,6 +206,14 @@ KeyThree=value 3\
<entry><literal>\<replaceable>nnn</replaceable></literal></entry>
<entry>character number <replaceable>nnn</replaceable> in octal encoding</entry>
</row>
+ <row>
+ <entry><literal>\u<replaceable>nnnn</replaceable></literal></entry>
+ <entry>unicode code point <replaceable>nnnn</replaceable> in hexadecimal encoding</entry>
+ </row>
+ <row>
+ <entry><literal>\U<replaceable>nnnnnnnn</replaceable></literal></entry>
+ <entry>unicode code point <replaceable>nnnnnnnn</replaceable> in hexadecimal encoding</entry>
+ </row>
</tbody>
</tgroup>
</table>