branch master updated: * doc/texinfo.texi (Node Line Requirements): add in comment that spaces from @-commands are collapsed too.

[Patrice Dumas]

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

pertusus pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new ebbcf530fc * doc/texinfo.texi (Node Line Requirements): add in comment 
that spaces from @-commands are collapsed too.
ebbcf530fc is described below

commit ebbcf530fc045fdea891814f823719ded49a0fc8
Author: Patrice Dumas <pertusus@free.fr>
AuthorDate: Fri Aug 19 14:58:27 2022 +0200

    * doc/texinfo.texi (Node Line Requirements): add in comment that
    spaces from @-commands are collapsed too.
    
    * doc/texinfo.texi (Node Line Requirements, Menu Parts): add
    a FIXME in comment to remove the constraint on extra space in
    Info as both the standalone and Emacs Info reader handle multiple
    spaces right now.
    
    * doc/texinfo.texi (HTML Xref Node Name Expansion): newlines in
    node names are correctly handled in all the output formats, remove
    the parenthesis stating that it is not the case.
    
    * doc/texinfo.texi (Info Format Menu): add a precision that in menu
    there is * instead of * (N|n)ote in cross-references.
---
 ChangeLog        | 23 ++++++++++++++++++++---
 doc/texinfo.texi | 22 +++++++++++++++-------
 2 files changed, 35 insertions(+), 10 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index d6101c2801..0bed3435d4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,20 @@
+2022-08-19  Patrice Dumas  <pertusus@free.fr>
+
+       * doc/texinfo.texi (Node Line Requirements): add in comment that
+       spaces from @-commands are collapsed too.
+
+       * doc/texinfo.texi (Node Line Requirements, Menu Parts): add
+       a FIXME in comment to remove the constraint on extra space in
+       Info as both the standalone and Emacs Info reader handle multiple
+       spaces right now.
+
+       * doc/texinfo.texi (HTML Xref Node Name Expansion): newlines in
+       node names are correctly handled in all the output formats, remove
+       the parenthesis stating that it is not the case.
+
+       * doc/texinfo.texi (Info Format Menu): add a precision that in menu
+       there is * instead of * (N|n)ote in cross-references.
+
 2022-08-18  Gavin Smith  <gavinsmith0123@gmail.com>
 
        @need
@@ -7,7 +24,7 @@
        reliable results when followed by a section title.  It also
        may work better with footnotes.  Reports from Werner Lemberg.
 
-2022-08-17  Patrice Dumas  <pertusus@free.fr>
+2022-08-18  Patrice Dumas  <pertusus@free.fr>
 
        Consider non ascii spaces to be characters for node name normalization
 
@@ -19,14 +36,14 @@
        * tp/Texinfo/Convert/NodeNameNormalization.pm: remove /o regex
        modifiers.
 
-2022-08-17  Patrice Dumas  <pertusus@free.fr>
+2022-08-18  Patrice Dumas  <pertusus@free.fr>
 
        Multiple consecutive space transformed to one in node normalization
 
        * tp/Texinfo/Convert/NodeNameNormalization.pm (_unicode_to_protected)
        (_unicode_to_file_name): transform multiple spaces to one.
 
-2022-08-17  Patrice Dumas  <pertusus@free.fr>
+2022-08-18  Patrice Dumas  <pertusus@free.fr>
 
        * tp/Texinfo/XS/xspara.c (xspara__add_next),
        tp/Texinfo/Convert/ParagraphNonXS.pm (_add_next): use
diff --git a/doc/texinfo.texi b/doc/texinfo.texi
index d11edd0717..4ec546490f 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -3084,7 +3084,14 @@ single space.  For example:
 @@node  foo  bar ,
 @end example
 
+@c Consistently with the HTML Cross-reference Node Name Expansion
+@c spaces and newlines generated by @-commands should also be
+@c collapsed to a single space.  If we want to be explicit, we
+@c could add a line corresponding to
+@c @node @  foo @: @* bar,
+
 @noindent all define the same node, namely @samp{foo bar}.
+@c FIXME to be removed.  In 2022 both Info readers find the node.
 In menu entries, a single internal space should be used in node
 names or some versions of some Info readers will not find the node.
 @end itemize
@@ -3592,7 +3599,9 @@ it with the first (and all others).  It's up to you.  An 
empty line,
 or the next menu entry, ends a description.
 
 Space characters in a menu are preserved as-is in the Info output; this
-allows you to format the menu as you wish.  Unfortunately you must type
+allows you to format the menu as you wish.
+@c FIXME to be removed.  In 2022 both Info readers find the node.
+Unfortunately you must type
 node names without any extra spaces or some versions of some Info
 readers will not find the node (@pxref{Node Line Requirements}).
 
@@ -18552,9 +18561,7 @@ is the first character of the node name.  In that case, 
see below.
 
 @item
 Multiple consecutive space, tab and newline characters are transformed
-into just one space.  (It's not possible to have newlines in node
-names with the current implementation, but we specify it anyway, just
-in case.)
+into just one space.
 
 @item
 Leading and trailing spaces are removed.
@@ -23919,9 +23926,10 @@ places no restrictions on their location.
 @end example
 
 The parts of a @t{<menu entry>} are also described in @ref{Menu
-Parts}.  They have the same syntax as cross-references (@pxref{Info
-Format Cross Reference}).  Indices extend the menu format to specify the
-destination line; @pxref{Info Format Printindex}.
+Parts}.  They have the same syntax as cross-references, with a leading @samp{*}
+instead of @samp{* (N|n)ote} (@pxref{Info Format Cross Reference}).  Indices
+extend the menu format to specify the destination line; @pxref{Info Format
+Printindex}.
 
 A @t{<menu comment>} is any line not beginning with @samp{*} that
 appears either at the beginning of the menu or is separated from a