Commit 33b9148a authored by Ran Benita's avatar Ran Benita Committed by Alan Coopersmith

Compose.man: fix escaped hexadecimal char description

The man page says:
    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 "\123" and
    hexadecimal codes as "\0x123a".

But the grammar in the parser and the implementation say:
    ESCAPED_CHAR  ::= ('\\' | '\"' | OCTAL | HEX )
    HEX           ::= '\' (x|X) HEX_CHAR [HEX_CHAR]]
    HEX_CHAR      ::= (0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|a|b|c|d|e|f)

So "\0x123a" -> "\x3a".
Signed-off-by: default avatarRan Benita <ran234@gmail.com>
Signed-off-by: Alan Coopersmith's avatarAlan Coopersmith <alan.coopersmith@oracle.com>
parent d9b2cc35
......@@ -112,7 +112,7 @@ 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\\0x123a\*q\fP.
\fB\*q\\x3a\*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.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment