texinfo-commits
[Top][All Lists]
Advanced

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

texinfo update (Mon Dec 26 17:22:01 EST 2005)


From: Karl Berry
Subject: texinfo update (Mon Dec 26 17:22:01 EST 2005)
Date: Mon, 26 Dec 2005 17:22:03 -0500

Index: ChangeLog
===================================================================
RCS file: /sources/texinfo/texinfo/ChangeLog,v
retrieving revision 1.552
retrieving revision 1.553
diff -c -r1.552 -r1.553
*** ChangeLog   26 Dec 2005 00:23:11 -0000      1.552
--- ChangeLog   26 Dec 2005 22:05:09 -0000      1.553
***************
*** 1,3 ****
--- 1,8 ----
+ 2005-12-26  Karl Berry  <address@hidden>
+ 
+       * doc/texinfo.txi (node, Node Names): pxref Node Line Requirements,
+       about restrictions on characters in node names.
+ 
  2005-12-25  Karl Berry  <address@hidden>
  
        * doc/texinfo.tex (\pdfurl): make @/ a no-op.
Index: doc/texinfo.txi
===================================================================
RCS file: /sources/texinfo/texinfo/doc/texinfo.txi,v
retrieving revision 1.152
retrieving revision 1.153
diff -c -r1.152 -r1.153
*** doc/texinfo.txi     20 Dec 2005 22:29:11 -0000      1.152
--- doc/texinfo.txi     26 Dec 2005 22:05:10 -0000      1.153
***************
*** 1,5 ****
  \input texinfo.tex    @c -*-texinfo-*-
! @c $Id: texinfo.txi,v 1.152 2005/12/20 22:29:11 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.
  
--- 1,5 ----
  \input texinfo.tex    @c -*-texinfo-*-
! @c $Id: texinfo.txi,v 1.153 2005/12/26 22:05:10 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.
  
***************
*** 4881,4889 ****
  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.  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
  Pointer Creation}).
  
  You may insert spaces before each name if you wish; the spaces are
--- 4881,4890 ----
  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
! 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
  Pointer Creation}).
  
  You may insert spaces before each name if you wish; the spaces are
***************
*** 4924,4931 ****
  @subsection Choosing Node and Pointer Names
  
  @cindex Node names, choosing
! The name of a node identifies the node.  The pointers enable
! you to reach other nodes and consist simply of the names of those nodes.
  
  Normally, a node's `Up' pointer contains the name of the node whose menu
  mentions that node.  The node's `Next' pointer contains the name of the
--- 4925,4933 ----
  @subsection Choosing Node and Pointer Names
  
  @cindex Node names, choosing
! The name of a node identifies the node (for details of node names,
! @pxref{Node Line Requirements}).  The pointers enable you to reach
! other nodes and consist simply of the names of those nodes.
  
  Normally, a node's `Up' pointer contains the name of the node whose menu
  mentions that node.  The node's `Next' pointer contains the name of the
***************
*** 18594,18600 ****
  (@url{http://www.gnu.org/software/rcs}) version control systems, which
  expand it into a string such as:
  @example
! $Id: texinfo.txi,v 1.152 2005/12/20 22:29:11 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}
--- 18596,18602 ----
  (@url{http://www.gnu.org/software/rcs}) version control systems, which
  expand it into a string such as:
  @example
! $Id: texinfo.txi,v 1.153 2005/12/26 22:05:10 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}
***************
*** 18660,18666 ****
  
  @verbatim
  \input texinfo   @c -*-texinfo-*-
! @comment $Id: texinfo.txi,v 1.152 2005/12/20 22:29:11 karl Exp $
  @comment %**start of header
  @setfilename sample.info
  @include version.texi
--- 18662,18668 ----
  
  @verbatim
  \input texinfo   @c -*-texinfo-*-
! @comment $Id: texinfo.txi,v 1.153 2005/12/26 22:05:10 karl Exp $
  @comment %**start of header
  @setfilename sample.info
  @include version.texi
P ChangeLog
P doc/texinfo.txi


reply via email to

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