From: Pádraig Brady <P@draigBrady.com>
Date: Fri, 15 Apr 2022 17:01:32 +0000 (+0100)
Subject: doc: avoid unicode errors in texi conversion
X-Git-Tag: v9.1~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0f2cf20af6d91075c1f876b8a8c4375c52ff672a;p=thirdparty%2Fcoreutils.git

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.
---

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 8cfa698a1c..3ebd068e16 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.