texinfo update (Sun Dec 12 16:52:01 EST 2004)

[Karl Berry]

Index: ChangeLog
===================================================================
RCS file: /cvsroot/texinfo/texinfo/ChangeLog,v
retrieving revision 1.427
retrieving revision 1.428
diff -c -r1.427 -r1.428
*** ChangeLog   8 Dec 2004 16:52:47 -0000       1.427
--- ChangeLog   12 Dec 2004 21:37:25 -0000      1.428
***************
*** 1,3 ****
--- 1,9 ----
+ 2004-12-12  Karl Berry  <address@hidden>
+ 
+       * doc/texinfo.txi (makeinfo options): don't be so suggestive about
+       skipping xref validation.
+       emacs-devel mail from: Luc Teirlinck, 12 Dec 2004 13:02:11 -0600.
+ 
  2004-12-08  Karl Berry  <address@hidden>
  
        * pretest version 4.7.91.
Index: doc/texinfo.txi
===================================================================
RCS file: /cvsroot/texinfo/texinfo/doc/texinfo.txi,v
retrieving revision 1.122
retrieving revision 1.123
diff -c -r1.122 -r1.123
*** doc/texinfo.txi     8 Dec 2004 14:34:33 -0000       1.122
--- doc/texinfo.txi     12 Dec 2004 21:37:25 -0000      1.123
***************
*** 1,5 ****
  \input texinfo.tex    @c -*-texinfo-*-
! @c $Id: texinfo.txi,v 1.122 2004/12/08 14:34:33 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.123 2004/12/12 21:37:25 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.
  
***************
*** 15163,15180 ****
  @opindex --no-pointer-validate
  @opindex --no-validate
  @cindex Pointer validation, suppressing
! Suppress the pointer-validation phase of @code{makeinfo}.  This can also
! be done with the @code{@@novalidate} command (@pxref{Use TeX,,Use
! @TeX{}}).  Normally, after a Texinfo file is processed, some consistency
! checks are made to ensure that cross references can be resolved, etc.
! @xref{Pointer Validation}.
  
  @item --no-warn
  @opindex --no-warn
! Suppress warning messages (but @emph{not} error messages).  You might
! want this if the file you are creating has examples of Texinfo cross
! references within it, and the nodes that are referenced do not actually
! exist.
  
  @item --number-sections
  @opindex --number-sections
--- 15163,15177 ----
  @opindex --no-pointer-validate
  @opindex --no-validate
  @cindex Pointer validation, suppressing
! Suppress the pointer-validation phase of @code{makeinfo}---a dangerous
! thing to do.  This can also be done with the @code{@@novalidate}
! command (@pxref{Use TeX,,Use @TeX{}}).  Normally, after a Texinfo file
! is processed, some consistency checks are made to ensure that cross
! references can be resolved, etc.  @xref{Pointer Validation}.
  
  @item --no-warn
  @opindex --no-warn
! Suppress warning messages (but @emph{not} error messages).
  
  @item --number-sections
  @opindex --number-sections
***************
*** 15313,15319 ****
  @cindex @@-commands in @@node, limited support
  Some Texinfo documents might fail during the validation phase because
  they use commands like @code{@@value} and @code{@@definfoenclose} in
! node definitions and cross-references inconsistently.  Consider the
  following example:
  
  @example
--- 15310,15317 ----
  @cindex @@-commands in @@node, limited support
  Some Texinfo documents might fail during the validation phase because
  they use commands like @code{@@value} and @code{@@definfoenclose} in
! node definitions and cross-references inconsistently.  (Your best bet
! is to avoid using @@-commands in node names.)  Consider the
  following example:
  
  @example
***************
*** 18456,18462 ****
  Concurrent Versions System}) or RCS (see rcsintro(1)) version control
  systems, which expand it into a string such as:
  @example
! $Id: texinfo.txi,v 1.122 2004/12/08 14:34:33 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}
--- 18454,18460 ----
  Concurrent Versions System}) or RCS (see rcsintro(1)) version control
  systems, which expand it into a string such as:
  @example
! $Id: texinfo.txi,v 1.123 2004/12/12 21:37:25 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}
***************
*** 18522,18528 ****
  
  @verbatim
  \input texinfo   @c -*-texinfo-*-
! @comment $Id: texinfo.txi,v 1.122 2004/12/08 14:34:33 karl Exp $
  @comment %**start of header
  @setfilename sample.info
  @include version.texi
--- 18520,18526 ----
  
  @verbatim
  \input texinfo   @c -*-texinfo-*-
! @comment $Id: texinfo.txi,v 1.123 2004/12/12 21:37:25 karl Exp $
  @comment %**start of header
  @setfilename sample.info
  @include version.texi
P ChangeLog
P doc/texinfo.txi