1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256
|
%
% By: Robert Schneider
%
% LaTeX input file which describes how dvi2tty works under
% VMS with VAXC. When using this file as a source for documentation
% of dvi2tty on your system, look for the string "NOTE ---" to
% see what local variables need to be set.
%
% This file was created by modifying the original Unix man page.
% The majority of the conversion from troff to TeX was done by
% tr2tex.
%
\documentstyle{article}
%
% Set the page margins.
%
\parindent 0pt
\marginparpush 5pt
\headheight 5pt
\headsep 0pt
\footheight 5pt
\footskip 15pt
\columnsep 10pt
\columnseprule 0pt
\marginparwidth 0pt
\oddsidemargin 0pt
\evensidemargin 0pt
\marginparsep 0pt
\topmargin 0pt
\textwidth 6.5in
\textheight 9.0in
%
\newcommand{\bs}{$\backslash$}
%
\title{{\bf DVI2TTY for VAX/VMS}}
\author{}
\date{April 25, 1990}
%
\begin{document}
\maketitle
%
% NOTE --- We like to describe what something is and how to get it
% at the top of our files. You will probably want to
% delete from here to the next \section.
%
This document describes the use of {\bf dvi2tty}\/, a filter for converting
the device independent output files created by \TeX\/ to files which may
be printed on any ASCII terminal or line printer.
This document may be printed on the line printer in CPE-3.102 by entering
the command;
\\[1ex]
{\em DOCPRINT SYS\$DOCUMENT:DVI2TTY.DOC}
\\[1ex]
Copies of this document may be printed on the laser printer in CPE-3.159
by entering the command;
\\[1ex]
{\em PSPRINT SYS\$DOCUMENT:DVI2TTY.PS}
\\[1ex]
You may view copies of this document on workstations or personal computers
which recognize the {\it X}\/ window system protocol by entering the command;
\\[1ex]
{\em XDVI SYS\$DOCUMENT:DVI2TTY.DVI}
\section*{Description}
{\bf dvi2tty}
converts a \TeX\/ DVI-file to a format that is appropriate for terminals
and line printers. The program is intended to be used for
preliminary proofreading of \TeX-ed documents.
By default the output is directed to the terminal.
%
% NOTE --- VMS can't pipe output to a pager. Maybe you are lucky
% and your system can.
%
%,possibly through a pager (depending on how the program was installed),
%but it can be directed to a file or a pipe.
\par\vspace{1.0\baselineskip}
The output leaves much to be desired, but is still
useful if you want to avoid walking to the
laser printer (or whatever) for each iteration of your
document.
\par\vspace{1.0\baselineskip}
Since {\bf dvi2tty}\/ produces output for terminals and line printers the
representation of documents is naturally quite primitive.
Font changes are totally ignored, which implies that
special symbols, such as mathematical symbols, get mapped into the
characters at the corresponding positions in the ``standard'' fonts.
\par\vspace{1.0\baselineskip}
If the width of the output text requires more columns than fits
in one line (c.f. the -w option) it is broken into several lines by
{\bf dvi2tty} although they will be printed as one line on regular \TeX\/ output
devices (e.g. laser printers). To show that a broken line is really
just one logical line an asterisk (``*'') in the last position
means that the logical line is continued on the next physical
line output by {\bf dvi2tty.}
Such a continuation line is started with a space and an asterisk
in the first two columns.
\section*{Format}
{\bf dvi2tty}
[
{\bf -o}
{\it file}
]
[
{\bf -p}
{\it list}
]
[
{\bf -P}
{\it list}
]
[
{\bf -w}
{\it n}
]
[
{\bf -l}
]
[
{\bf -u}
]
[
{\bf -s}
]
{\it file\rm[\it.dvi\rm]}
\par\vspace{1.0\baselineskip}
{\bf dvi2tty}\/ is compiled with VAXC which converts uppercase command line
arguments to lowercase. To pass an uppercase argument to {\bf dvi2tty},
the argument must be enclosed in quotation marks ( i.e. ``-P'' ). Arguments
enclosed in brackets ( [ ] ) are optional.
\section*{Options}
The {\it file}\/ [{\it .dvi}] argument is optional.
Options may be specified in either a symbol or logical which is named
%
% NOTE --- The definition of the following environment variable
% is implementation dependent.
%
DVI\$DVI2TTY or on the command line.
Any option on the command line, conflicting with one in the
environment, will override the one from the environment.
\begin{list}{}{\setlength{\leftmargin}{0.6in}\labelwidth 0.6in}
\item[{{\bf -o} {\it name}}]
Write output to file {\it name}.
\item[{{\bf -p} {\it list}}]
Print the pages chosen by {\it list}.
Numbers refer to \TeX-page numbers (known as \bs count0).
An example of format for {\it list}\/ is ``1,3:6,8''
to choose pages 1, 3 through 6 and 8.
Negative numbers can be used exactly as in \TeX,
e g -1 comes before -4 as in ``-p-1:-4,17''.
\item[{{\bf -P} {\it list}}]
Like -p except that page numbers refer to
the sequential ordering of the pages in the dvi-file.
Negative numbers don't make a lot of sense here...
\item[{{\bf -w} {\it n}}]
Specify terminal width {\it n.}\/ The legal range is 16-132 with a
default of 80. If your terminal has the
ability to display in 132 columns it might
be a good idea to use -w132 and toggle the
terminal into this mode as output will probably look somewhat better.
%
% NOTE --- The ability to pipe to a pager is operating system dependent.
%
%\item[{{\bf -q}}]
%Don't pipe the output through a pager.
%This may be the default on some systems
%(depending on the whims of the SA installing the program).
%\item[{{\bf -f}}]
%Pipe through a pager, \$PAGER if defined, or whatever your SA compiled
%in (often ``more''). This may be the default, but it is still okay
%to redirect output with ``$>$'', the pager will not be used if output
%is not going to a terminal.
%\item[{{\bf -F}}]
%Specify the pager program to be used.
%This overides the \$PAGER and the default pager.
%\item[{{\bf -Fprog}}]
%Use ``prog'' as program to pipe output into. Can be used to choose an
%alternate pager (e g ``-Fless'').
\item[{{\bf -l}}]
Mark page breaks with the two-character sequence ``\^{}L''. The default is
to mark them with a form feed character.
\item[{{\bf -u}}]
Don't make any attempts to find special Scandinavian characters.
If such characters are in the text they will map to ``a'' and ``o''.
This is probably the default outside of Scandinavia. (The SA made
the decision when the program was installed.)
\item[{{\bf -s}}]
Try to find the special Scandinavian characters that on most (?)
terminals in Scandinavia are mapped to ``\{$|$\}[\bs ]''.
This can be the default, and output from files not containing these
special characters will be identical regardless of this option.
\end{list}
%
% NOTE --- No other files are used under VMS.
%
%\section*{FILES}
%/usr/ucb/more \ \ \ \
%probably the default pager.
\section*{Environment}
%
% NOTE --- The PAGER variable isn't used under VMS.
%
%PAGER \ \ \ \ \ \ \ \ \ \ \ \
%the pager to use.
%\nwl
%
% NOTE --- The definition of the following environment variable
% is operating system dependent.
%
Either a symbol or logical which is named DVI\$DVI2TTY can be set to hold
command line options. As an example, if you wish to normally have your
output written to the file {\it dvi2tty.output}\/ and wish to also have
the output be 132 columns in width, you may define the logical name
DVI\$DVI2TTY as in;
\par\vspace{1.0\baselineskip}
\begin{center}
{\bf \$ DEFINE DVI\$DVI2TTY ``{\it o dvi2tty.output w 132}''}
\end{center}
\par\vspace{1.0\baselineskip}
Options set in the environment variable will be overridden by conflicting
options on the command line.
\section*{See Also}
%
% NOTE --- How do you describe where your help files and manuals are?
%
For further information use the DCL command {\bf HELP TeX}\/ to obtain
information on \TeX\/ and how \TeX\/ may be used on our system.
You should also read the \LaTeX\/ {\it Local Guide}\/ which may be found
in SYS\$DOCUMENT:.
This document may be printed on the line printer in CPE-3.102 by entering
the command;
\\[1ex]
{\em DOCPRINT SYS\$DOCUMENT:LOCAL\_GUIDE.DOC}
\\[1ex]
Copies of this document may be printed on the laser printer in CPE-3.159
by entering the command;
\\[1ex]
{\em PSPRINT SYS\$DOCUMENT:LOCAL\_GUIDE.PS}
\\[1ex]
You may view copies of this document on workstations or personal computers
which recognize the {\it X}\/ window system protocol by entering the command;
\\[1ex]
{\em XDVI SYS\$DOCUMENT:LOCAL\_GUIDE.DVI}
\section*{Bugs}
Blanks between words get lost quite easy. This is less
likely if you are using a wider output than the default 80.
\par\vspace{1.0\baselineskip}
Only one file may be specified on the command line.
\section*{Author}
Svante Lindahl, Royal Institute of Technology, Stockholm
\\[1ex]
Improved C version: Marcel Mol
\\[1ex]
\{seismo, mcvax\}!enea!ttds!zap
\\[1ex]
marcel@duteca.tudelft.nl
\end{document}
|