VPR(1)

NAME
vpr - Versatec printer/plotter spooler

SYNOPSIS
vpr [ -v ] [ -t [ -1234 font ] ] [ -w ] [ -wwidth ] [ -m ] [ name ... ]

DESCRIPTION
Vpr causes the named files to be queued for printing or typeset simulation on the Versatec printer/plotter. If no files are named, the standard input is read. By default the input is assumed to be line printer like text and is run through the filter /usr/lib/sidebyside giving it an argument of -w106 which arranges it four pages adjacent with 90 column lines (the rest is for the left margin). Since there are 8 lines per inch in the default printer font, vpr thus produces 86 lines per page (the top and bottom lines are left blank).

The following options are available:

-1234
    Specifies a font to be mounted on font position i. The daemon will construct a .railmag file referencing /usr/lib/vfont/name.size.

-m  Report by mail(1) when printing is complete.

-w  Do not run the input through sidebyside. Such processing has been done already, or full (440 character) printer width is desired.

-wwidth
    Use width width rather than 90 for sidebyside.

-v  Use the filter /usr/lib/vrast to convert the vectors to raster. The named files must be a parameter and vector file (in that order) created by versaplot(3x) routines.

-t  Use the filter vcat(1) to typeset the input on the Versatec. The input must have been generated by troff(1) run with the -t option. This is not normally run directly! Since the Versatec is 36'' wide, it is wasteful to run only one page across. The program vtroff(1) is normally used and arranges, using vsort(1) for printing to occur four pages across, conserving paper.

FILES
/usr/spool/vpd/*    spool area
/usr/lib/vpd    Versatec daemon
/usr/lib/vpf    Filter for printer simulation
/usr/lib/vcat    Filter for typeset simulation
/usr/lib/vrast    Filter for versaplot
/usr/lib/sidebyside

SEE ALSO
troff(1), vfont(5), vp(4), pti(1), vpq(1), vprint(1), vprm(1), vtroff(1), versaplot(3x)

BUGS
You can't run bit maps in a queued fashion to the Versatec. This is because the volume of the data (more than 1 Megabyte per vertical foot) is unwieldy. Instead you must follow the instructions in vp(4) and run your program when the Versatec is idle, or run it in the background and have it wait for the Versatec to become idle.

Queued jobs print in directory (seemingly random) order. The Versatec is fast enough that this is not a real problem.