texinfo-commits
[Top][All Lists]
Advanced

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

[6017] correct statement about indirect table values


From: Gavin D. Smith
Subject: [6017] correct statement about indirect table values
Date: Fri, 02 Jan 2015 18:12:04 +0000

Revision: 6017
          http://svn.sv.gnu.org/viewvc/?view=rev&root=texinfo&revision=6017
Author:   gavin
Date:     2015-01-02 18:12:03 +0000 (Fri, 02 Jan 2015)
Log Message:
-----------
correct statement about indirect table values

Modified Paths:
--------------
    trunk/ChangeLog
    trunk/doc/texinfo.texi

Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog     2015-01-02 11:07:49 UTC (rev 6016)
+++ trunk/ChangeLog     2015-01-02 18:12:03 UTC (rev 6017)
@@ -1,3 +1,9 @@
+2015-01-02  Gavin Smith  <address@hidden>
+
+       * doc/texinfo.texi (Info Format Indirect Table): Value in 
+       indirect table is for first node in file, not start of file 
+       itself.
+
 2015-01-01  Karl Berry  <address@hidden>
 
        * doc/texinfo.texi (Output Formats, Generating HTML): be rather

Modified: trunk/doc/texinfo.texi
===================================================================
--- trunk/doc/texinfo.texi      2015-01-02 11:07:49 UTC (rev 6016)
+++ trunk/doc/texinfo.texi      2015-01-02 18:12:03 UTC (rev 6017)
@@ -23902,10 +23902,11 @@
 @end example
 
 The indirect table is written to the main file in the case of split
-output only.  It specifies, as a decimal integer, the starting byte position
-(zero-based) that each subfile would have if the subfiles were concatenated
-together in order, not including the top-level file.  The first node
-of actual content is pointed to by the first entry.
+output only.  It specifies, as a decimal integer, the starting byte 
+position (zero-based) that the first node of each subfile would have if 
+the subfiles were concatenated together in order, not including the 
+top-level file.  The first node of actual content is pointed to by the 
+first entry.
 
 As an example, suppose split output is generated for the GDB manual.
 The top-level file @file{gdb.info} will contain something like this:




reply via email to

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