texinfo update (Sat Jul 10 21:22:01 EDT 2004)

[Karl Berry]

Index: NEWS
===================================================================
RCS file: /cvsroot/texinfo/texinfo/NEWS,v
retrieving revision 1.84
retrieving revision 1.85
diff -c -r1.84 -r1.85
*** NEWS        18 May 2004 12:18:31 -0000      1.84
--- NEWS        11 Jul 2004 01:02:35 -0000      1.85
***************
*** 1,4 ****
! $Id: NEWS,v 1.84 2004/05/18 12:18:31 karl Exp $
  This file records noteworthy changes.
  
    Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
--- 1,4 ----
! $Id: NEWS,v 1.85 2004/07/11 01:02:35 karl Exp $
  This file records noteworthy changes.
  
    Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
***************
*** 22,27 ****
--- 22,28 ----
  
  
-------------------------------------------------------------------------------
  * Distribution:
+   . new convenience script texi2pdf, equivalent to texi2dvi --pdf (from 
tetex).
    . automake 1.8.5.
  
  4.7 (9 April 2004)
Index: doc/texinfo.txi
===================================================================
RCS file: /cvsroot/texinfo/texinfo/doc/texinfo.txi,v
retrieving revision 1.99
retrieving revision 1.100
diff -c -r1.99 -r1.100
*** doc/texinfo.txi     24 Jun 2004 12:48:12 -0000      1.99
--- doc/texinfo.txi     11 Jul 2004 01:02:34 -0000      1.100
***************
*** 1,5 ****
  \input texinfo.tex    @c -*-texinfo-*-
! @c $Id: texinfo.txi,v 1.99 2004/06/24 12:48:12 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.100 2004/07/11 01:02:34 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.
  
***************
*** 59,64 ****
--- 59,65 ----
  * Texinfo: (texinfo).           The GNU documentation format.
  * install-info: (texinfo)Invoking install-info. Update info/dir entries.
  * texi2dvi: (texinfo)Format with texi2dvi.      Print Texinfo documents.
+ * texi2pdf: (texinfo)PDF Output.                PDF output for Texinfo.
  * texindex: (texinfo)Format with tex/texindex.  Sort Texinfo index files.
  * makeinfo: (texinfo)Invoking makeinfo.         Translate Texinfo source.
  @end direntry
***************
*** 895,904 ****
  @cindex PDF output
  @cindex Beebe, Nelson
  @pindex pdftex
! (Generated via @command{texi2dvi --pdf}.)  This format, based on
! PostScript, was developed by Adobe Systems for document interchange.
! It is intended to be platform-independent and easily viewable, among
! other design goals; for a discussion, see
  @uref{http://tug.org/tugboat/Articles/tb22-3/tb72beebeI.pdf}.  Texinfo
  uses the @command{pdftex} program, a variant of @TeX{}, to output pdf;
  see @uref{http://tug.org/applications/pdftex}.  @xref{PDF Output}.
--- 896,905 ----
  @cindex PDF output
  @cindex Beebe, Nelson
  @pindex pdftex
! (Generated via @command{texi2dvi --pdf} or @command{texi2pdf}.)  This
! format, based on PostScript, was developed by Adobe Systems for
! document interchange.  It is intended to be platform-independent and
! easily viewable, among other design goals; for a discussion, see
  @uref{http://tug.org/tugboat/Articles/tb22-3/tb72beebeI.pdf}.  Texinfo
  uses the @command{pdftex} program, a variant of @TeX{}, to output pdf;
  see @uref{http://tug.org/applications/pdftex}.  @xref{PDF Output}.
***************
*** 13757,13769 ****
  
  @pindex texindex
  The @code{tex} formatting command itself does not sort the indices; it
! writes an output file of unsorted index data.  (The @code{texi2dvi}
! command automatically generates indices; @pxref{Format with texi2dvi,,
! Format with @code{texi2dvi}}.)  To generate a printed index after
! running the @code{tex} command, you first need a sorted index to work
! from.  The @code{texindex} command sorts indices.  (The source file
! @file{texindex.c} comes as part of the standard Texinfo distribution,
! among other places.)@refill
  
  @cindex Names of index files
  @cindex Index file names
--- 13758,13769 ----
  
  @pindex texindex
  The @code{tex} formatting command itself does not sort the indices; it
! writes an output file of unsorted index data.  To generate a printed
! index after running the @command{tex} command, you first need a sorted
! index to work from.  The @command{texindex} command sorts indices.
! (The source file @file{texindex.c} comes as part of the standard
! Texinfo distribution, among other places.)  (@command{texi2dvi} runs
! @command{tex} and @command{texindex} as necessary.)
  
  @cindex Names of index files
  @cindex Index file names
***************
*** 13901,13910 ****
--- 13901,13921 ----
  (You can also do this on a site-wide basis with @file{texinfo.cnf};
  @pxref{Preparing for TeX,,Preparing for @TeX{}}).
  
+ With the @option{--pdf} option, @command{texi2dvi} produces PDF output
+ instead of DVI (@pxref{PDF Output}), by running @command{pdftex}
+ instead of @command{tex}.  Alternatively, the command
+ @command{texi2pdf} is an abbreviation for running @samp{texi2dvi --pdf}.
+ 
  @cindex @LaTeX{}, processing with @command{texi2dvi}
  @command{texi2dvi} can also be used to process @LaTeX{} files; simply
  run @samp{texi2dvi filename.ext}.
  
+ @command{texi2dvi} will use @command{etex} (or @command{pdfetex}) if
+ they are available; these extended versions of @TeX{} are not
+ required, and the DVI (or PDF) output is identical, but they simplify
+ the @TeX{} programming in some cases, and provide additional tracing
+ information when debugging @file{texinfo.tex}.
+ 
  For a list of other options, run @samp{texi2dvi --help}.
  
  
***************
*** 14569,14578 ****
  @cindex PDF output
  
  @pindex pdftex
! You can generate a PDF output file from Texinfo source by using the
! @command{pdftex} program to process your file instead of plain
! @command{tex}.  That is, run @samp{pdftex foo.texi} instead of @samp{tex
! foo.texi}, or give the @samp{--pdf} option to @command{texi2dvi}.
  
  @dfn{PDF} stands for `Portable Document Format'. It was invented by
  Adobe Systems some years ago for document interchange, based on their
--- 14580,14592 ----
  @cindex PDF output
  
  @pindex pdftex
! The simplest way to generate PDF output from Texinfo source is to run
! the convenience script @command{texi2pdf}; this simply executes the
! @command{texi2dvi} script with the @option{--pdf} option
! (@pxref{Format with texi2dvi}).  If for some reason you want to
! process by hand, simply run the @command{pdftex} program instead of
! plain @command{tex}.  That is, run @samp{pdftex foo.texi} instead of
! @samp{tex foo.texi}.
  
  @dfn{PDF} stands for `Portable Document Format'. It was invented by
  Adobe Systems some years ago for document interchange, based on their
***************
*** 14585,14593 ****
  PDF files require special software to be displayed, unlike the plain
  ASCII formats (Info, HTML) that Texinfo supports.  They also tend to
  be much larger than the DVI files output by @TeX{} by default.
! Nevertheless, a PDF file does preserve, in a self-contained way, an
! actual printed document on a screen as faithfully as possible, so it
! has its place.
  
  
  @node Obtaining TeX
--- 14599,14606 ----
  PDF files require special software to be displayed, unlike the plain
  ASCII formats (Info, HTML) that Texinfo supports.  They also tend to
  be much larger than the DVI files output by @TeX{} by default.
! Nevertheless, a PDF file does define an actual typeset document in a
! self-contained file, so it has its place.
  
  
  @node Obtaining TeX
***************
*** 18173,18179 ****
  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.99 2004/06/24 12:48:12 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}
--- 18186,18192 ----
  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.100 2004/07/11 01:02:34 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}
***************
*** 18239,18245 ****
  
  @verbatim
  \input texinfo   @c -*-texinfo-*-
! @comment $Id: texinfo.txi,v 1.99 2004/06/24 12:48:12 karl Exp $
  @comment %**start of header
  @setfilename sample.info
  @include version.texi
--- 18252,18258 ----
  
  @verbatim
  \input texinfo   @c -*-texinfo-*-
! @comment $Id: texinfo.txi,v 1.100 2004/07/11 01:02:34 karl Exp $
  @comment %**start of header
  @setfilename sample.info
  @include version.texi
Index: util/Makefile.am
===================================================================
RCS file: /cvsroot/texinfo/texinfo/util/Makefile.am,v
retrieving revision 1.12
retrieving revision 1.13
diff -c -r1.12 -r1.13
*** util/Makefile.am    13 Apr 2004 00:07:51 -0000      1.12
--- util/Makefile.am    11 Jul 2004 01:02:35 -0000      1.13
***************
*** 1,4 ****
! # $Id: Makefile.am,v 1.12 2004/04/13 00:07:51 karl Exp $
  # Makefile.am for texinfo/util.
  # Run automake in .. to produce Makefile.in from this.
  #
--- 1,4 ----
! # $Id: Makefile.am,v 1.13 2004/07/11 01:02:35 karl Exp $
  # Makefile.am for texinfo/util.
  # Run automake in .. to produce Makefile.in from this.
  #
***************
*** 11,17 ****
  # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
  
  bin_PROGRAMS = ginstall-info texindex
! bin_SCRIPTS = texi2dvi
  
  # Use `ginstall-info' in the definition of PROGRAMS and in dependencies
  # because automake generates an install-info target in every Makefile (a
--- 11,17 ----
  # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
  
  bin_PROGRAMS = ginstall-info texindex
! bin_SCRIPTS = texi2dvi texi2pdf
  
  # Use `ginstall-info' in the definition of PROGRAMS and in dependencies
  # because automake generates an install-info target in every Makefile (a
***************
*** 34,44 ****
  texinfo.cat: texinfo-cat.in $(top_srcdir)/doc/version.texi
        sed 's/__VERSION__/@VERSION@/g' texinfo-cat.in >$@
  
! # Most of these are for fun.  The only one that's really supported is 
texi2dvi.
  # 
  EXTRA_DIST = README deref.c dir-example fix-info-dir fixfonts \
    fixref.gawk gdoc gen-dir-node gendocs.sh gendocs_template infosrch \
    install-info-html outline.gawk \
!   prepinfo.awk tex3patch texi-docstring-magic.el texi2dvi txitextest \
    $(dist_pkgdata_DATA) texinfo-cat.in
  CLEANFILES = $(pkgdata_DATA)
--- 34,45 ----
  texinfo.cat: texinfo-cat.in $(top_srcdir)/doc/version.texi
        sed 's/__VERSION__/@VERSION@/g' texinfo-cat.in >$@
  
! # Most of these are for fun.  The only official/installed ones are the
! # texi2* scripts.
  # 
  EXTRA_DIST = README deref.c dir-example fix-info-dir fixfonts \
    fixref.gawk gdoc gen-dir-node gendocs.sh gendocs_template infosrch \
    install-info-html outline.gawk \
!   prepinfo.awk tex3patch texi-docstring-magic.el texi2dvi texi2pdf txitextest 
\
    $(dist_pkgdata_DATA) texinfo-cat.in
  CLEANFILES = $(pkgdata_DATA)
P NEWS
P doc/texinfo.txi
P util/Makefile.am
U util/texi2pdf