DVIOUT is a program that reads in DVI files generated by TeX and other programs and generates output on a particular device. Currently, the Tektronix 4014 and PostScript are supported (also, an untested IMAGEN driver is supplied). The file 'dviout.hlp' contains specific information on the use of DVIOUT. This is a VMS help file which can be inserted into the system help file for general access. This is the only documentation furnished for DVIOUT. The file 'dviout.cld' is the command definition file for DVIOUT. The "image" description will have to be site tailored to point to the proper executable file specification. Other default parameters, such as the pixel source and mark font, can be altered by changing this file. You can use the VMS $ SET COMMAND command to allow DCL to recognize the DVIOUT command; or, the system manager can make it part of DCLTABLES. There are five logical names hard-coded into the software. These are: TEX_FONTS Points to where the TeX TFM files are. TEX_IM_PIXEL Points to where the imagen-style PXL, PK and/or GF files are (write-black, 300dpi). TEX_QMS_PIXEL Points to where the QMS-style PXL, PK and/or GF files are (write-white, 300dpi). DVI_INPUTS Points to where DVIOUT input files are located (all options files). DVI_TEK4014 Defines the terminal port connected to the Tektronix terminal. Can be set to NLA0: if you don't have a Tektronix 4014 terminal. These logical names can be PATCHed to different values, if necessary. (Refer to the link map for the locations to patch.) If you have a C compiler, then you can directly modify the source code to obtain the same effect. If one or more system #include modules are unavailable on your system, the file DVISYSDEF contains all those referenced by the software. You will need to compile using a command similar to: $ CC file+DVISYSDEF/LIBRARY Of course, this only applies if you plan to make modifications to the software. The author has defined the modules fscndef.h and lbrdef.h and put them in the C system text library. You may have to jockey things about a bit to make sure all the right #include modules are properly referenced. DVIOUT uses packed (PK) pixel files. If your installation uses old PXL files instead (or GF files), you will have to modify the command definition file PIXEL_SOURCE default value to either "PXL" or "GF". Additionally, if you have the old Kellerman & Smith TeX distribution, pixel files are located in separate directories, partitioned by magnification size. I felt this was incorrect and instead insist on all pixel files for a particular print engine to be in a single directory. If this is a real problem for you, the file FMTPXLNAM_PENNSTATE contains an alternate mechanism for constructing the pixel file names; you can replace this module in the DVIOUT.OLB library and re-link. For version 1.1 of DVIOUT, the mechanism used to identify native fonts has been completely re-engineered. Native font definitions are now specified in options files, several of which are supplied with DVIOUT. They have a file extension of OPT. You can specify whatever native fonts you wish for the PostScript devices, including pre-downloaded TeX fonts, if they are present in your printer ROM. The help file for DVIOUT explains how to use and modify the options files for your site-specific needs. Version 1.2 of DVIOUT includes the capability to utilize pre-downloaded TeX fonts in PostScript printers. A new command procedure has been supplied (BLDRESFONT.COM) that can build PostScript fonts from the TeX fonts using the new PSFONT utility. You will need to tailor this file and generate only those fonts you think you will need, then modify the options file for your PostScript printer so that DVIOUT can recognize the fonts. A more complete discussion of how to load and use native and/or downloaded fonts is in the file NATIVE_FONTS.TEX. DVIOUT includes a feature to paste PostScript files, Tektronix 4010/14 graphics files and MacPaint bitmap files into the output. This is done with the \special "paste" command, which is described in the help file for DVIOUT. The file 'special.tex' contains an example how to provide an easy-to-use interface to this facility of DVIOUT. There are also a number of graphics extensions which are documented in the help file. DVIOUT uses virtual memory quite liberally. If you have a small working set, DVIOUT may have poor performance. The amount of memory used is dependent upon the complexity of the DVI file being processed, especially, the number of fonts used. Several features of DVIOUT are still being developed. The program is pretty-full-functional, but a few things are still missing (this is endless). Some of these are: a) DVIOUT does not, as yet, handle output devices with aspect ratios other than one-to-one. b) Additional paste capabilities for mixing text and graphics. (Specifically, metafile interpretation is considered quite desirable; and new things are happening all the time now in this field, like X-Windows and DEC's Compound Document Architecture) c) The /PICTURE qualifier to the \special paste command is not yet implemented, and has no effect. d) Support for some graphics extensions are not present in the Tektronix driver. Only the basic TeX functionality is currently supported. e) There is an untested driver for the Imagen laser printer family (imPRESS language, circa 1984) that is accessed using the /DEVICE=IMAGEN qualifier. The author does not have access to an IMAGEN printer, and the driver is supplied in case anyone wants to see if it works. The polygon clipping function of the graphics extensions is not yet complete (will generate errors at the device if any polygon vertex extends outside the page boundaries). Note: this driver does not currently work; but the author is still unable to find the resources to address the problem. f) A preview function is highly desirable (but very, very hard to implement). Version 2.0, if the author ever gets around to it, will contain a preview function.