branch master updated: * doc/texinfo.texi (HTML Xref Link Basics): edit text at end of node discussing split/mono links.

[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 f21ef9a652 * doc/texinfo.texi (HTML Xref Link Basics): edit text at 
end of node discussing split/mono links.
f21ef9a652 is described below

commit f21ef9a652189c3015c50148a7d1af665f7243c1
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Sun Oct 13 14:51:59 2024 +0100

    * doc/texinfo.texi (HTML Xref Link Basics): edit text at end of
    node discussing split/mono links.
---
 ChangeLog        |  5 +++++
 doc/texinfo.texi | 27 +++++++++++++--------------
 2 files changed, 18 insertions(+), 14 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 8ee6403959..43ad7c9760 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2024-10-13  Gavin Smith <gavinsmith0123@gmail.com>
+
+       * doc/texinfo.texi (HTML Xref Link Basics): edit text at end of
+       node discussing split/mono links.
+
 2024-10-13  Gavin Smith <gavinsmith0123@gmail.com>
 
        * README-hacking: add note about removing generated gnulib header
diff --git a/doc/texinfo.texi b/doc/texinfo.texi
index 4a4c8c9cab..25d474ed43 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -17619,21 +17619,20 @@ name.
 
 Finally, the @var{target} part is always the expanded node name.
 
-Whether the present manual is split or mono is determined by user
-option; @command{texi2any} defaults to split, with the
+Whether the present manual is output as split or mono is determined by
+how you run @command{texi2any}; the default is to split, with the
 @option{--no-split} option overriding this.
-Whether the referent manual is split or mono, however, is another bit
-of the external information (@pxref{HTML Xref Configuration}).
-
-By default, @command{texi2any} uses the same form of the referent manual as the
-present manual.  Thus, there can be a mismatch between the format of the
-referent manual that the generating software assumes, and the format it's
-actually present in.  If there is no external information, both mono
-and split form should be generated to be sure that the cross-references
-work irrespective of the split option.  This is something the software
-which generated the @emph{referent} manual has to do in advance, it's
-not something the software generating the cross-reference in the present
-manual can control.
+
+By default, @command{texi2any} generates links to a referent manual using
+the same form as as the present manual: if the present manual is generated
+as split, then links to other manuals are to their split forms by default;
+likewise for mono output.
+
+However, the form of the referent manual (mono or split) should usually
+be specified in a configuation file (@pxref{HTML Xref Configuration}).
+This ensures that there is no mismatch between the format of the referent
+manual that the generating software assumes, and the format it's actually
+present in.
 
 
 @node HTML Xref Node Name Expansion