fdo-mirrors/xorg-libx11
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/xorg/lib/libx11.git synced 2026-05-05 01:48:00 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Compose.man: \\ should be \e in troff markup

Browse source 
Fixes warnings from `mandoc -T lint`:
mandoc: Compose.5:121:27: WARNING: undefined escape, printing literally: \\
mandoc: Compose.5:122:10: WARNING: undefined escape, printing literally: \\
mandoc: Compose.5:129:29: WARNING: undefined escape, printing literally: \\

Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Part-of: <https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/286>
This commit is contained in:
Alan Coopersmith 2025-07-13 10:09:14 -07:00
parent eb400f6fda
commit 0bddfd82d0
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
man/Compose.man
View file

@ -118,17 +118,17 @@ Keysyms are specified without the \fBXK_\fP prefix.
Strings may be direct text encoded in the locale for which the compose file is
to be used, or an escaped octal or hexadecimal character code.
Octal codes
are specified as \fB\*q\\123\*q\fP and hexadecimal codes as
\fB\*q\\x3a\*q\fP.
are specified as \fB\*q\e123\*q\fP and hexadecimal codes as
\fB\*q\ex3a\*q\fP.
It is not necessary to specify in the right part of a rule a locale encoded
string in addition to the keysym name.
If the string is omitted, Xlib
figures it out from the keysym according to the current locale.
I.e., if a rule looks like:
.RS
\fB<dead_grave> <A> : \*q\\300\*q Agrave\fP
\fB<dead_grave> <A> : \*q\e300\*q Agrave\fP
.RE
the result of the composition is always the letter with the "\\300"
the result of the composition is always the letter with the "\e300"
code.
But if the rule is:
.RS