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       -e, -E, --expand
63              force macro expansion using makeinfo
64
65       -I DIR search DIR for Texinfo files
66
67       -l, --language=LANG
68              specify the LANG of FILE (LaTeX or Texinfo)
69
70       --no-line-error
71              do not pass --file-line-error to TeX
72
73       -p, --pdf
74              use pdftex or pdflatex for processing
75
76       -r, --recode
77              call recode before TeX to translate input
78
79       --recode-from=ENC
80              recode from ENC to the @documentencoding
81
82       --src-specials
83              pass --src-specials to TeX
84
85       -t, --command=CMD
86              insert CMD in copy of input file
87
88       or --texinfo=CMD
89              multiple values accumulate
90
91       --translate-file=FILE
92              use given charset translation file for TeX
93
94   Build modes:
95       --build=MODE
96              specify the treatment of auxiliary files [local]
97
98       --tidy same as --build=tidy
99
100       -c, --clean
101              same as --build=clean
102
103       --build-dir=DIR
104              specify where the tidy compilation is performed; implies --tidy;
105              defaults to TEXI2DVI_BUILD_DIRECTORY [.]
106
107       --mostly-clean
108              remove the auxiliary files and directories but not the output
109
110       The MODE specifies where the TeX compilation takes  place,  and,  as  a
111       consequence,  how auxiliary files are treated.  The build mode can also
112       be set using the environment variable TEXI2DVI_BUILD_MODE.
113
114   Valid MODEs are:
115       `local'
116              compile in the current directory, leaving all the auxiliary
117
118       files around.
119              This is the traditional TeX use.
120
121       `tidy' compile in a local *.t2d directory, where the auxiliary files
122
123       are left.
124              Output files are copied back to the original file.
125
126       `clean'
127              same as `tidy', but remove the auxiliary directory afterwards.
128
129              Every compilation therefore requires the full cycle.
130
131   Using the `tidy' mode brings several advantages:
132              - the current directory is not cluttered with plethora of tempo‐
133              rary   files.    -   clutter   can   be   even   reduced   using
134              --build-dir=dir: all the *.t2d
135
136              directories are stored there.
137
138              -    clutter    can     be     reduced     to     zero     using
139              --build-dir=/tmp/$USER.t2d or
140
141       --build-dir=/u/karl/.t2d.
142
143              - the output file is updated after every succesful TeX run, for
144
145       sake of concurrent visualization of the output.
146              In a `local' build
147
148              the viewer stops during the whole TeX run.
149
150              -  if  the  compilation  fails, the previous state of the output
151              file
152
153              is preserved.
154
155              - PDF and DVI compilation are kept in separate subdirectories
156
157              preventing any possibility of auxiliary file incompatibility.
158
159       On the other hand, because `tidy' compilation takes  place  in  another
160       directory,  occasionally  TeX  won't  be able to find some files (e.g.,
161       when using \graphicspath): in that case use -I  to  specify  the  addi‐
162       tional directories to consider.
163
164       The values of the BIBTEX, LATEX (or PDFLATEX), MAKEINDEX, MAKEINFO, TEX
165       (or PDFTEX), TEXINDEX, and THUMBPDF environment variables are  used  to
166       run  those  commands, if they are set.  Any CMD strings are added after
167       @setfilename for Texinfo input, in the first line for LaTeX input.
168

REPORTING BUGS

170       Email bug reports to <bug-texinfo@gnu.org>, general questions and  dis‐
171       cussion     to     <help-texinfo@gnu.org>.     Texinfo    home    page:
172       http://www.gnu.org/software/texinfo/
173

COPYRIGHT

175       Copyright © 2007 Free Software Foundation, Inc.   License  GPLv3+:  GNU
176       GPL version 3 or later <http://gnu.org/licenses/gpl.html>
177       This  is  free  software:  you  are free to change and redistribute it.
178       There is NO WARRANTY, to the extent permitted by law.
179

NAME

SYNOPSIS

DESCRIPTION

REPORTING BUGS

COPYRIGHT

SEE ALSO