[PATCH libX11] Compose.man: fix escaped hexadecimal char description

[Ran Benita]

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: Ran Benita <ran234 at gmail.com>
---
 man/Compose.man | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man/Compose.man b/man/Compose.man
index 13ba705..73f5c12 100644
--- a/man/Compose.man
+++ b/man/Compose.man
@@ -110,7 +110,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.
-- 
1.8.5.3