Your company here — click to reach over 10,000 unique daily visitors

texi2dvi - Man Page

convert Texinfo documents to DVI or PDF


texi2dvi [OPTION]... FILE...
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.

General options

-D,  --debug

turn on shell debugging (set -x)

-h,  --help

display this help and exit successfully

-o,  --output=OFILE

leave output in OFILE; only one input FILE is allowed

-q,  --quiet

no output unless errors

-v,  --version

display version information and exit successfully

-V,  --verbose

report on what is done


don't process files more than N times [7]


remove auxiliary files or directories from previous runs (but not the output)

Output format


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

-p,  --pdf

use pdftex or pdflatex for processing


output a PostScript file via DVI (using dvips)


output a plain text file from LaTeX, using HeVeA

TeX tuning

-E,  --expand

macro expansion using makeinfo


search DIR for Texinfo files

-l,  --language=LANG

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

-t,  --command=CMD

insert CMD in copy of input file

Build modes


specify the treatment of auxiliary files [local]


same as --build=tidy

-c,  --clean

same as --build=clean


specify where the tidy compilation is performed; implies --tidy

The MODE specifies where the TeX compilation takes place, and, as a consequence, how auxiliary files are treated.

Valid values 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 build mode can also be set using the environment variable TEXI2DVI_BUILD_MODE.  The tidy build directory can also be set using the environment variable TEXI2DVI_BUILD_DIRECTORY.

The values of these environment variables are used to run the corresponding commands, if they are set:


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

info texi2dvi

should give you access to more documentation.

Reporting Bugs

Report bugs to bug-texinfo@gnu.org, general questions and discussion to help-texinfo@gnu.org.
GNU Texinfo home page: <http://www.gnu.org/software/texinfo/>
General help using GNU software: <http://www.gnu.org/gethelp/>

See Also

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

info texi2dvi

should give you access to the complete manual.

Referenced By

info(5), texinfo(5).

The man pages pdftexi2dvi(1) and texi2pdf(1) are aliases of texi2dvi(1).

October 2023 texi2dvi (GNU Texinfo 7.1)