From 0f2cf20af6d91075c1f876b8a8c4375c52ff672a Mon Sep 17 00:00:00 2001 From: =?utf8?q?P=C3=A1draig=20Brady?= Date: Fri, 15 Apr 2022 18:01:32 +0100 Subject: [PATCH] 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. --- doc/coreutils.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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. -- 2.47.2