texi2dvi − convert Texinfo documents to DVI or PDF
texi2pdf [OPTION]... FILE...
pdftexi2dvi [OPTION]... FILE...
Run each Texinfo or (La)TeX FILE through TeX in turn until all cross−references are resolved, building all indices. The directory containing each FILE is searched for included files. The suffix of FILE is used to determine its language ((La)TeX or Texinfo). To process (e)plain TeX files, set the environment variable LATEX=tex.
When invoked as ‘texi2pdf’ or given the option −−pdf generate PDF output. Otherwise, generate DVI.
turn on shell debugging (set −x)
display this help and exit successfully
leave output in OFILE; only one input FILE is allowed
no output unless errors (implies −−batch)
display version information and exit successfully
report on what is done
don’t process files more than N times 
remove auxiliary files or directories from previous runs (but not the output)
output a DVI file [default]
output a PDF file via DVI (using a dvi−to−pdf program)
output an HTML file from LaTeX, using HeVeA
output an Info file from LaTeX, using HeVeA
use pdftex or pdflatex for processing
output a PostScript file via DVI (using dvips)
output a plain text file from LaTeX, using HeVeA
macro expansion using makeinfo
search DIR for Texinfo files
specify LANG for FILE, either latex or texinfo
do not pass −−file−line−error to TeX
pass −−shell−escape to TeX
pass −−src−specials to TeX
use given charset translation file for TeX
insert CMD in copy of input file
Any CMD strings are added after @setfilename for Texinfo input, or in the first line for LaTeX input. Multiple values accumulate.
specify the treatment of auxiliary files [local]
same as −−build=tidy
same as −−build=clean
specify where the tidy compilation is performed; implies −−tidy; defaults to TEXI2DVI_BUILD_DIRECTORY [.]
The MODE specifies where the TeX compilation takes place, and, as a consequence, how auxiliary files are treated. The build mode can also be set using the environment variable TEXI2DVI_BUILD_MODE.
of MODE are:
compile in the current directory, leaving all the auxiliary files around. This is the traditional TeX use.
compile in a local *.t2d directory, where the auxiliary files are left. Output files are copied back to the original file.
same as ‘tidy’, but remove the auxiliary directory afterwards. Every compilation therefore requires the full cycle.
The values of these environment variables are used to run the corresponding commands, if they are set:
BIBER BIBTEX DVIPDF DVIPS EGREP HEVEA LATEX MAKEINDEX MAKEINFO PDFLATEX PDFTEX SED T4HT TEX TEX4HT TEXINDEX TEXINDY THUMBPDF_CMD
Regarding −−dvipdf, if DVIPDF is not set in the environment, the following programs are looked for (in this order): dvipdfmx dvipdfm dvipdf dvi2pdf dvitopdf.
If Texinfo is installed on your site, then the command
should give you access to more documentation.
Report bugs to
bug−email@example.com, general questions and discussion
GNU Texinfo home page: <http://www.gnu.org/software/texinfo/>
General help using GNU software: <http://www.gnu.org/gethelp/>
© 2017 Free Software Foundation, Inc. License GPLv3+:
GNU GPL version 3 or later
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
The full documentation for texi2dvi is maintained as a Texinfo manual. If the info and texi2dvi programs are properly installed at your site, the command
should give you access to the complete manual.