texi2dvi(1)

1TEXI2DVI(1)                      User Commands                     TEXI2DVI(1)
2
3
4

NAME

6       texi2dvi - convert Texinfo documents to DVI
7

SYNOPSIS

9       texi2dvi [OPTION]... FILE...
10

DESCRIPTION

12       Run  each  Texinfo  or  (La)TeX  FILE  through  TeX  in  turn until all
13       cross-references are resolved, building  all  indices.   The  directory
14       containing  each  FILE  is  searched for included files.  The suffix of
15       FILE is used to  determine  its  language  ((La)TeX  or  Texinfo).   To
16       process (e)plain TeX files, set the environment variable LATEX=tex.
17
18       In  order  to  make  texi2dvi  a  drop-in  replacement  of TeX/LaTeX in
19       AUC-TeX, the FILE may also be composed of the following simple TeX com‐
20       mands.
21
22       `\input{FILE}'
23              the actual file to compile
24
25       `\nonstopmode'
26              same as --batch
27
28       Makeinfo  is used to perform Texinfo macro expansion before running TeX
29       when needed.
30
31   General options:
32       -b, --batch
33              no interaction
34
35       -D, --debug
36              turn on shell debugging (set -x)
37
38       -h, --help
39              display this help and exit successfully
40
41       -o, --output=OFILE
42              leave output in OFILE (implies --clean); only one input FILE may
43              be specified in this case
44
45       -q, --quiet
46              no output unless errors (implies --batch)
47
48       -s, --silent
49              same as --quiet
50
51       -v, --version
52              display version information and exit successfully
53
54       -V, --verbose
55              report on what is done
56
57   TeX tuning:
58       -@     use @input instead of \input for preloaded Texinfo
59
60       --dvi  output a DVI file [default]
61
62       --dvipdf
63              output a PDF file via DVI (using dvipdf)
64
65       -e, -E, --expand
66              force macro expansion using makeinfo
67
68       -I DIR search DIR for Texinfo files
69
70       -l, --language=LANG
71              specify LANG for FILE, either latex or texinfo
72
73       --no-line-error
74              do not pass --file-line-error to TeX
75
76       -p, --pdf
77              use pdftex or pdflatex for processing
78
79       -r, --recode
80              call recode before TeX to translate input
81
82       --recode-from=ENC
83              recode from ENC to the @documentencoding
84
85       --src-specials
86              pass --src-specials to TeX
87
88       -t, --command=CMD
89              insert CMD in copy of input file
90
91       or --texinfo=CMD
92              multiple values accumulate
93
94       --translate-file=FILE
95              use given charset translation file for TeX
96
97   Build modes:
98       --build=MODE
99              specify the treatment of auxiliary files [local]
100
101       --tidy same as --build=tidy
102
103       -c, --clean
104              same as --build=clean
105
106       --build-dir=DIR
107              specify where the tidy compilation is performed; implies --tidy;
108              defaults to TEXI2DVI_BUILD_DIRECTORY [.]
109
110       --mostly-clean
111              remove the auxiliary files and directories but not the output
112
113       The MODE specifies where the TeX compilation takes  place,  and,  as  a
114       consequence,  how auxiliary files are treated.  The build mode can also
115       be set using the environment variable TEXI2DVI_BUILD_MODE.
116
117   Valid MODEs are:
118       `local'
119              compile in the current  directory,  leaving  all  the  auxiliary
120              files around.  This is the traditional TeX use.
121
122       `tidy' compile  in  a  local *.t2d directory, where the auxiliary files
123              are left.  Output files are copied back to the original file.
124
125       `clean'
126              same as `tidy', but remove the auxiliary  directory  afterwards.
127              Every compilation therefore requires the full cycle.
128
129   Using the `tidy' mode brings several advantages:
130       -      the  current  directory is not cluttered with plethora of tempo‐
131              rary files.
132
133       -      clutter can be even reduced using --build-dir=dir: all the *.t2d
134              directories are stored there.
135
136       -      clutter    can    be    reduced    to    zero    using,    e.g.,
137              --build-dir=/tmp/$USER.t2d or --build-dir=$HOME/.t2d.
138
139       -      the output file is updated after every succesful  TeX  run,  for
140              sake  of  concurrent  visualization of the output.  In a `local'
141              build the viewer stops during the whole TeX run.
142
143       -      if the compilation fails, the previous state of the output  file
144              is preserved.
145
146       -      PDF and DVI compilation are kept in separate subdirectories pre‐
147              venting any possibility of auxiliary file incompatibility.
148
149       On the other hand, because `tidy' compilation takes  place  in  another
150       directory,  occasionally  TeX  won't  be able to find some files (e.g.,
151       when using \graphicspath): in that case use -I  to  specify  the  addi‐
152       tional directories to consider.
153
154       The values of the BIBTEX, LATEX (or PDFLATEX), MAKEINDEX, MAKEINFO, TEX
155       (or PDFTEX), TEXINDEX, and THUMBPDF environment variables are  used  to
156       run  those  commands, if they are set.  Any CMD strings are added after
157       @setfilename for Texinfo input, in the first line for LaTeX input.
158

REPORTING BUGS

160       Email bug reports to <bug-texinfo@gnu.org>, general questions and  dis‐
161       cussion     to     <help-texinfo@gnu.org>.     Texinfo    home    page:
162       http://www.gnu.org/software/texinfo/
163

COPYRIGHT

165       Copyright © 2008 Free Software Foundation, Inc.   License  GPLv3+:  GNU
166       GPL version 3 or later <http://gnu.org/licenses/gpl.html>
167       This  is  free  software:  you  are free to change and redistribute it.
168       There is NO WARRANTY, to the extent permitted by law.
169

NAME

SYNOPSIS

DESCRIPTION

REPORTING BUGS

COPYRIGHT

SEE ALSO