texinfo-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]


From: Gavin D. Smith
Date: Sat, 9 Nov 2024 14:26:19 -0500 (EST)

branch: master
commit a965d23fcf5f45a92f06bee814469aaedf995856
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Sat Nov 9 19:04:29 2024 +0000

    HTML Output Customization manual edit
    
    * doc/texinfo.texi (HTML Output Structure Customization):
    Mention SPLIT.
---
 ChangeLog        |  7 +++++++
 doc/texinfo.texi | 15 +++++++++++----
 2 files changed, 18 insertions(+), 4 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 12c50b9a4a..8f988c4b76 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2024-11-08  Gavin Smith <gavinsmith0123@gmail.com>
+
+       HTML Output Customization manual edit
+
+       * doc/texinfo.texi (HTML Output Structure Customization):
+       Mention SPLIT.
+
 2024-11-08  Gavin Smith <gavinsmith0123@gmail.com>
 
        HTML Output Customization manual edit
diff --git a/doc/texinfo.texi b/doc/texinfo.texi
index bed6320d84..c90c526d08 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -18122,6 +18122,11 @@ If menus are used for navigation, the table of 
contents is not
 needed at the end of the @code{@@top} section, as
 there should already be a master menu (@pxref{Master Menu Parts}).
 
+@vindex SPLIT @subentry @r{for HTML}
+By default, each node is output in a separate file.  You can change this
+with the @option{--split} command-line option, which is equivalent to
+setting the @code{SPLIT} variable.  @xref{Splitting Output}.
+
 @vindex DO_ABOUT
 @vindex PROGRAM_NAME_IN_ABOUT
 You can add a special @dfn{About} element explaining how to navigate by
@@ -18140,10 +18145,12 @@ As already described, the table of contents location 
may also be tuned with
 @c FIXME only for CONTENTS_OUTPUT_LOCATION=separate_element ??
 
 @vindex USE_NODES @subentry @r{for HTML}
-Elementary units called @dfn{output units} are used for output.  Output
-units contain the content associated with a node or a sectioning command.
-In typical Texinfo document sources, a node command is almost always
-associated with an immediately following sectioning command.
+Elementary units called @dfn{output units} are used for output, with each
+output file containing the content for one or more output units, depending
+on the value of @code{SPLIT}.  Output units contain the content associated
+with a node or a sectioning command. In typical Texinfo document sources,
+a node command is almost always associated with an immediately following
+sectioning command.
 
 The customization variable @code{USE_NODES} determines whether the
 node or the sectioning command is considered to



reply via email to

[Prev in Thread] Current Thread [Next in Thread]