branch master updated: * doc/texinfo.texi (@documentencoding): Mention possibility of ASCII transliteration. Don't say "UTF-8 character in the output encoding", as this can only mean one encoding (UTF-8). Reorder to say "8-bit character in the output encoding".

[Gavin D. Smith]

This is an automated email from the git hooks/post-receive script.

gavin pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new 64a6f442bc * doc/texinfo.texi (@documentencoding): Mention possibility 
of ASCII transliteration.  Don't say "UTF-8 character in the output encoding", 
as this can only mean one encoding (UTF-8). Reorder to say "8-bit character in 
the output encoding".
64a6f442bc is described below

commit 64a6f442bc8bd93bafb05e5a6ffdc58b72ca73ab
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Tue Nov 1 17:44:43 2022 +0000

    * doc/texinfo.texi (@documentencoding): Mention possibility
    of ASCII transliteration.  Don't say "UTF-8 character in
    the output encoding", as this can only mean one encoding (UTF-8).
    Reorder to say "8-bit character in the output encoding".
    
    (Internationalization of Document Strings): State accent commands
    have to be used in us-ascii translations, but that these may
    be inconvenient.
---
 ChangeLog        | 12 ++++++++++++
 doc/texinfo.texi | 25 ++++++++++++++++---------
 2 files changed, 28 insertions(+), 9 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 4f91694882..d91cd2d65a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,15 @@
+2022-11-01  Patrice Dumas  <pertusus@free.fr>, and
+            Gavin Smith  <gavinsmith0123@gmail.com>
+
+       * doc/texinfo.texi (@documentencoding): Mention possibility
+       of ASCII transliteration.  Don't say "UTF-8 character in
+       the output encoding", as this can only mean one encoding (UTF-8).
+       Reorder to say "8-bit character in the output encoding".
+
+       (Internationalization of Document Strings): State accent commands
+       have to be used in us-ascii translations, but that these may
+       be inconvenient.
+
 2022-10-29  Gavin Smith  <gavinsmith0123@gmail.com>
 
        pretest 6.8.91
diff --git a/doc/texinfo.texi b/doc/texinfo.texi
index f92b6f86df..3be9e677af 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -12441,11 +12441,12 @@ coding: UTF-8
 End:
 @end example
 
-Also, in Info and plain text output, unless the option
-@option{--disable-encoding} is given to @command{texi2any}, accent
-constructs and special characters, such as @code{@@'e}, are output as
-the actual 8-bit or UTF-8 character in the output encoding where
-possible.
+By default, for Info and plain text output, @command{texi2any} outputs
+accent constructs and special characters (such as @code{@@'e})
+as the actual UTF-8 sequence or 8-bit character in the output
+encoding where possible.  If this is not possible, or if the option
+@option{--disable-encoding} is given, an ASCII transliteration is
+used instead.
 
 @cindex HTML output, and encodings
 @cindex @code{http-equiv}, and charset specification
@@ -12463,9 +12464,10 @@ this:
 
 In HTML and @LaTeX{} output, if the option @option{--enable-encoding} is given
 to @command{texi2any}, accent constructs and special characters, such as
-@code{@@'e} or @code{``}, are output as the actual 8-bit or UTF-8 character in
-the output encoding where possible.  Otherwise HTML entities are used for those
-characters in HTML, and @LaTeX{} macros are used in @LaTeX{}.
+lcode{@@'e} or @code{``}, are output as the actual UTF-8 sequence or
+8-bit character in the output encoding where possible.  Otherwise, HTML
+entities are used for those characters in HTML, and @LaTeX{} macros
+are used in @LaTeX{}.
 
 In DocBook output, if the encoding is different from UTF-8,
 an @code{encoding} attribute is added to the XML declaration.
@@ -17139,6 +17141,11 @@ any encoding, since all the Latin@tie{}1 characters 
have associated
 @code{ja.utf-8}, since there are no @@-commands for Japanese
 characters.
 
+The @code{us-ascii} locales are not needed much now that
+UTF-8 is used for most documents.  Note that accented characters
+are required to be expressed as @@-commands in the @code{us-ascii} locales,
+which may be inconvenient for translators.
+
 @item Next, the string is expanded as Texinfo, and converted.
 The arguments are substituted; for example, @samp{@{arg_name@}} is
 replaced by the corresponding actual argument.
@@ -17164,7 +17171,7 @@ format---yet still be language-dependent.  For example, 
the
 @samp{@@pxref} translation string can be like this:
 
 @example
-see @{node_file_href@} section `@{section@}\' in @@cite@{@{book@}@}
+see @{node_file_href@} section `@{section@}' in @@cite@{@{book@}@}
 @end example
 
 @noindent