texinfo update (Sun Jul 9 19:52:01 EDT 2006)

[Karl Berry]

Index: ChangeLog
===================================================================
RCS file: /sources/texinfo/texinfo/ChangeLog,v
retrieving revision 1.622
retrieving revision 1.623
diff -u -r1.622 -r1.623
--- ChangeLog   9 Jul 2006 22:37:55 -0000       1.622
+++ ChangeLog   9 Jul 2006 23:34:02 -0000       1.623
@@ -1,3 +1,8 @@
+2006-07-09  Karl Berry  <address@hidden>
+
+       * doc/texinfo.txi (makeinfo Pointer Creation, Writing a Menu):
+       mention that accesskey is used in the HTML output.
+
 2006-07-09  <address@hidden>
 
        * doc/texinfo.txi: Fix some typos.
Index: doc/texinfo.txi
===================================================================
RCS file: /sources/texinfo/texinfo/doc/texinfo.txi,v
retrieving revision 1.168
retrieving revision 1.169
diff -u -r1.168 -r1.169
--- doc/texinfo.txi     9 Jul 2006 22:37:55 -0000       1.168
+++ doc/texinfo.txi     9 Jul 2006 23:34:02 -0000       1.169
@@ -1,5 +1,5 @@
 \input texinfo.tex    @c -*-texinfo-*-
address@hidden $Id: texinfo.txi,v 1.168 2006/07/09 22:37:55 karl Exp $
address@hidden $Id: texinfo.txi,v 1.169 2006/07/09 23:34:02 karl Exp $
 @c Ordinarily, Texinfo files have the extension .texi.  But texinfo.texi
 @c clashes with texinfo.tex on 8.3 filesystems, so we use texinfo.txi.
 
@@ -4882,10 +4882,10 @@
 several nodes, one for each section, subsection, and
 subsubsection.
 
-To create a node, write an @code{@@node} command at the beginning of a
-line, and follow it with up to four arguments, separated by commas, on
-the rest of the same line.  The first argument is required; it is the
-name of this node (for details of node names, @pxref{Node Line
+To specify a node, write an @code{@@node} command at the beginning of
+a line, and follow it with up to four arguments, separated by commas,
+on the rest of the same line.  The first argument is required; it is
+the name of this node (for details of node names, @pxref{Node Line
 Requirements}).  The subsequent arguments are the names of the `Next',
 `Previous', and `Up' pointers, in that order, and may be omitted if
 your Texinfo document is hierarchically organized (@pxref{makeinfo
@@ -4902,12 +4902,6 @@
 @code{@@section} or @code{@@subsection} line.  (@xref{Structuring
 Command Types}.)
 
address@hidden Note
-The GNU Emacs Texinfo mode updating commands work
-only with Texinfo files in which @code{@@node} lines are followed by chapter
-structuring lines.  @xref{Updating Requirements}.
address@hidden quotation
-
 @TeX{} uses @code{@@node} lines to identify the names to use for cross
 references.  For this reason, you must write @code{@@node} lines in a
 Texinfo file that you intend to format for printing, even if you do not
@@ -4953,7 +4947,7 @@
 can write the nodes in the Texinfo source file in an arbitrary order!
 Because @TeX{} processes the file sequentially, irrespective of node
 pointers, you must write the nodes in the order you wish them to appear
-in the printed output.
+in the output.
 
 
 @node Writing a Node
@@ -5239,6 +5233,15 @@
 feature, for that group of nodes.  In those cases, you will need to
 explicitly specify the pointers.
 
address@hidden address@hidden, in HTML output}
+Whether the nodes are specified implicitly or explicitly, the HTML
+output from @command{makeinfo} includes links to the `Next',
+`Previous', and `Up' nodes.  The HTML also uses the @code{accesskey}
+attribute with the values @samp{n}, @samp{p}, and @samp{u}
+respectively.  This allows people using web browsers to follow
+the nagivation using (typically) @address@hidden, e.g.,
address@hidden for the `Next' node, from anywhere within the node.
+
 
 @node anchor
 @section @code{@@anchor}: Defining Arbitrary Cross-reference Targets
@@ -5345,10 +5348,10 @@
 @code{@@ifinfo} conditional instead of the normal sectioning commands
 after a very short node with a menu.  This had the advantage of making
 the printed output look better, because there was no very short text
-between two headings on the page.  But aside from not working with
address@hidden's implicit pointer creation, it also makes the XML
-output incorrect, since it does not reflect the true document
-structure.  So, unfortunately we can no longer recommend this.
+between two headings on the page.  But this also does not work with
address@hidden's implicit pointer creation, and it also makes the
+XML output incorrect, since it does not reflect the true document
+structure.  So, regrettably, we can no longer recommend this.
 
 
 @node Writing a Menu
@@ -5384,6 +5387,13 @@
 entries.  Space characters in a menu are preserved as-is; this allows
 you to format the menu as you wish.
 
address@hidden address@hidden, in HTML output}
+In the HTML output from @command{makeinfo}, the @code{accesskey}
+attribute is used with the values @address@hidden@samp{9} for the
+first nine entries.  This allows people using web browsers to follow
+the first menu entries using (typically) @address@hidden, e.g.,
address@hidden for the first entry.
+
 
 @node Menu Parts
 @section The Parts of a Menu
@@ -18780,7 +18790,7 @@
 (@url{http://www.gnu.org/software/rcs}) version control systems, which
 expand it into a string such as:
 @example
-$Id: texinfo.txi,v 1.168 2006/07/09 22:37:55 karl Exp $
+$Id: texinfo.txi,v 1.169 2006/07/09 23:34:02 karl Exp $
 @end example
 (This is useful in all sources that use version control, not just manuals.)
 You may wish to include the @samp{$Id:} comment in the @code{@@copying}
@@ -18846,7 +18856,7 @@
 
 @verbatim
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: texinfo.txi,v 1.168 2006/07/09 22:37:55 karl Exp $
address@hidden $Id: texinfo.txi,v 1.169 2006/07/09 23:34:02 karl Exp $
 @comment %**start of header
 @setfilename sample.info
 @include version.texi
P ChangeLog
P doc/texinfo.txi