Several TEX DVI translators are available. They all expect the name of the DVI file on the command line, and the extension .dvi can always be omitted. As illustrated below, they issue a one-line identifier message and, if no command line arguments are given, type a -style1usage message. Some of them may have additional help files. On case-sensitive file systems, file names may be expected to be entirely in lower case, so you should should type dvialw instead of DVIALW.
For all except DVIBIT (which is intended for interactive display), the output file will be given the name of the .dvi file, but extension .dvi-xxx, where xxx is the three-character mnemonic for the translator program. If long extensions are not supported, then .xxx is used. For DVIBIT, output is on stdout which defaults to the terminal; it may be redirected in the usual fashion by >filename on the command line (e.g. dvibit foo >foo.out).
As the .dvi file is processed, a list of errors is printed
on the standard error unit stderr; this list is also saved
in a file with extension .dvi-log, or if long extensions
are not supported by the host, then extension .err is used.
This file is not created if there are no errors. As each page is
printed, the physical page number and the TEX page number is
printed without a following character return; after the last
page, the string [OK]
is printed, followed by a carriage
return. This gives a convenient progress report to the terminal.
If it is not wanted, then the error output can be redirected into
a file (possibly the null device) (e.g. dvixxx foo
&foo.err), or the -q option can be given to suppress it.
The order of command options and DVI file names is not significant; all switch values apply to all DVI files. DVI files are processed in order from left to right.
The available translators are as follows: