DataMuseum.dk

Presents historical artifacts from the history of:

DKUUG/EUUG Conference tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about DKUUG/EUUG Conference tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download
Index: T v

⟦38c90da97⟧ TextFile

    Length: 4650 (0x122a)
    Types: TextFile
    Names: »vmsuser.tex«

Derivation

└─⟦060c9c824⟧ Bits:30007080 DKUUG TeX 2/12/89
    └─⟦this⟧ »./DVIware/lpr-viewers/crudetype/VMS/vmsuser.tex« 
└─⟦52210d11f⟧ Bits:30007239 EUUGD2: TeX 3 1992-12
    └─⟦af5ba6c8e⟧ »unix3.0/DVIWARE.tar.Z« 
        └─⟦ca79c7339⟧ 
            └─⟦this⟧ »DVIware/lpr-viewers/crudetype/VMS/vmsuser.tex« 

TextFile

% VMSUSER.TEX Suggested user document (VMS specific) for Crudetype.
% Formatting could be much improved.


\font\big = cmbx10 at 14.4 truept
\font\bold  = cmb10  scaled \magstephalf
\font\rm  = cmr10  scaled \magstephalf
\font\commandfont = cmtt10 scaled \magstephalf
\def\titlefont{\big}
\rm

\def\title#1{\message{ Title: #1}\centerline {\titlefont#1}}

\def\space#1{{\hglue 0.0 em plus #1 fill}}
\def\author#1{\vskip\parskip\line{\space3 #1\space2}}
\def\sign#1{\author{#1}}

\hsize 170 true mm \vsize 257 true mm


\parindent = 0.0 em
\parskip = 8mm plus 35mm minus 4mm

\def\address{\parskip=0mm\obeylines}




% and here are my own macros


% These macros for verbatim scanning are copied from MANMAC.TEX. But we cant
% use the vertical bar for a temporary escape character as WEAVE catches it.
% So we will use ! instead and hope for the best
\chardef\other=12
\def\ttverbatim{\begingroup
  \catcode`\\=\other  \catcode`\{=\other  \catcode`\}=\other  \catcode`\$=\other
  \catcode`\&=\other  \catcode`\#=\other  \catcode`\%=\other  \catcode`\~=\other
  \catcode`\_=\other  \catcode`\^=\other
  \obeyspaces \obeylines \tt}

\def\begintt{$$\let\par=\endgraf \ttverbatim \parskip=0pt
  \catcode`\!=0 \rightskip-5pc \ttfinish}
{\catcode`\!=0 !catcode`!\=\other   % ! is temporary escape character
  !obeylines !obeyspaces    % end of line is active
  !gdef!ttfinish#1^^M#2\endtt{#1!vbox{#2}!endgroup$$}}

% \font\ninett=cmtt9
% that is the normal WEB practice, but in view of the definition of
% commandfont above, it seemed inadvisable...

\font\ninett = cmtt10 scaled \magstephalf

\let\mc=\ninett 

\def\C{{Crudetype}}
\def\D{{\mc DVI}}


\title{Lineprinter output from \TeX.}

\C\ is a program that takes a standard \TeX\ \D\ file and generates output
suitable for printing on a lineprinter. Of course no lineprinter can possibly
do justice to the power of \TeX, but it does give a fairly good idea of what
your output would look like on a respectable printer.Thus \C\ is very useful
in the early stages of
debugging \TeX\ input, because you do not need any special equipment to run it
and lineprinter output is less expensive than laserprinter output. The output
file can also be
inspected with editors such as EDT or TPU, but for this you need a 132-column-wide
terminal. Also because VDUs cannot show overstruck characters, these appear
incorrectly on the next line.  To use \C, you
must first issue the following commands:\begintt
$USE TEX
$CRT :== $SYS$USERDISK2:[UHAH208.CRUDE]CRUDETYPE \endtt
These commands only need to be given once per login, so you can insert them
into your {\tt LOGIN.COM} file. The first command tells \C\ where to look for
the fonts. The second defines {\tt CRT} as what VMS calls a ``foreign''
command. (Existing users, please note that this command has changed). 
Then you can run the program by this command: \begintt
$CRT (qualifiers) DVI_FILE \endtt
The {\tt DVI\_FILE} must be specified. If you do not specify a directory or an
extension \C\ will look in your current default directory and assume the
default extension {\tt .DVI}.  The qualifiers are all optional; they will
not work unless {\tt CRT} is defined as above. The permitted qualifiers are:

/m (number)  Magnify by (number)/100. Some magnification is needed because
most \TeX\ characters are narrower than lineprinter characters. But I
do not know any plausible algorithm for adjusting the magnification
according to the fonts being used. The least bad alternative seemed to
be to allow the user to specify a magnification; the default is
adjusted
so some files look reasonable on a lineprinter.

/q           (quiet) Suppress information messages.

/r           (run-on) Suppress form feeds; instead \C\ prints a string 
             like {\tt ----- END OF PAGE n -----} .

/s           (squash) Suppress blank lines in the printed output. Normally, 
output is double-spaced to allow space for super- and subscripts.

/f (number)  (first page) Start printing at the first page whose {\tt count0}
             parameter is greater than or equal to the specified number.

/c (number)  (count) Stop after this many pages. The defaults for /c and /f are
$\pm 10^6$, so normally \C\ will print all pages.

/p (printfile)   Send output to the named file instead of the default. The 
             default output file name is:
               (your current default directory)({\tt DVI} file name)({\tt .PRI}).
             But note that when this qualifier is used VMS sometimes alters 
             the name: for example {\tt /p HORSE} generates the output file 
{\tt HORSE.DAT} instead of {\tt HORSE}.


\sign{R.M.Damerell, Mathematics Dept.}


\bye