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 ee06f30cfab2f95ace624bdd2d02f885fc4633ae
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Sat Nov 9 19:10:37 2024 +0000

    HTML Output Customization manual edit
    
    * doc/texinfo.texi (HTML Output Structure Customization):
    Move discussion of USE_NODES immediately after discussion of
    SPLIT.
---
 ChangeLog        |  8 ++++++++
 doc/texinfo.texi | 39 +++++++++++++++++++--------------------
 2 files changed, 27 insertions(+), 20 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 8f988c4b76..16ad65f5d9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2024-11-09  Gavin Smith <gavinsmith0123@gmail.com>
+
+       HTML Output Customization manual edit
+
+       * doc/texinfo.texi (HTML Output Structure Customization):
+       Move discussion of USE_NODES immediately after discussion of
+       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 c90c526d08..06ad991ecb 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -18127,34 +18127,16 @@ 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
-setting @code{DO_ABOUT}, set to 0 in the default case (no About element).
-If @code{PROGRAM_NAME_IN_ABOUT} is also set, output the program name and
-miscellaneous related information in the About special element; default
-false.
-
-@vindex MONOLITHIC
-In the case of non-split output, by default only one file is output
-including any tables of contents or About elements.
-If you prefer such special elements to be separate,
-set @code{MONOLITHIC} to 0 to output special elements to separate files.
-As already described, the table of contents location may also be tuned with
-@code{CONTENTS_OUTPUT_LOCATION}.
-@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, 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,
+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
-be the main command.
+node or the sectioning command is considered to be the main command.
 By default, nodes are used as the main component for the separation of
 output units.  You can set @code{USE_NODES} to false to preferentially
 use sectioning to decide where output units are separated.
@@ -18166,6 +18148,23 @@ components of output units, isolated sections not 
associated with nodes
 are associated with the previous node, and isolated nodes are
 output units.
 
+@vindex DO_ABOUT
+@vindex PROGRAM_NAME_IN_ABOUT
+You can add a special @dfn{About} element explaining how to navigate by
+setting @code{DO_ABOUT}, set to 0 in the default case (no About element).
+If @code{PROGRAM_NAME_IN_ABOUT} is also set, output the program name and
+miscellaneous related information in the About special element; default
+false.
+
+@vindex MONOLITHIC
+In the case of non-split output, by default only one file is output
+including any tables of contents or About elements.
+If you prefer such special elements to be separate,
+set @code{MONOLITHIC} to 0 to output special elements to separate files.
+As already described, the table of contents location may also be tuned with
+@code{CONTENTS_OUTPUT_LOCATION}.
+@c FIXME only for CONTENTS_OUTPUT_LOCATION=separate_element ??
+
 @vindex USE_NEXT_HEADING_FOR_LONE_NODE
 In Texinfo code, a @code{@@node} command is usually followed by a
 sectioning command, providing a heading for the node.  By default, a



reply via email to

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