summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPádraig Brady <P@draigBrady.com>2022-04-15 18:01:32 +0100
committerPádraig Brady <P@draigBrady.com>2022-04-15 18:28:38 +0100
commit0f2cf20af6d91075c1f876b8a8c4375c52ff672a (patch)
treeebfb37351540ee87f7f39090a1981e4216997856
parentbcfbcef928cd540e53d35fc2869d9def2fedeb84 (diff)
downloadcoreutils-0f2cf20af6d91075c1f876b8a8c4375c52ff672a.tar.gz
doc: avoid unicode errors in texi conversion
Avoid "Unicode character U+#1 not supported, sorry" error when converting from texi to dvi or pdf. * doc/coreutils.texi (tr invocation): Avoid the @U{XXXX} texi representation, as even though info and html can represent these characters directly, there are conversion errors for pdf and dvi. Instead use the more abstract shell $'\uXXXX' representation.
-rw-r--r--doc/coreutils.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 8cfa698a1..3ebd068e1 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -6972,7 +6972,7 @@ The interpretation of @var{string1} and @var{string2} depends on locale.
GNU @command{tr} fully supports only safe single-byte locales,
where each possible input byte represents a single character.
Unfortunately, this means GNU @command{tr} will not handle commands
-like @samp{tr @U{7530} @U{68EE}} the way you might expect,
+like @samp{tr $'\u7530' $'\u68EE'} the way you might expect,
since (assuming a UTF-8 encoding) this is equivalent to
@samp{tr '\347\224\260' '\346\243\256'} and GNU @command{tr} will
simply transliterate all @samp{\347} bytes to @samp{\346} bytes, etc.