epsonESCP2(1)
epsonESCP2 - Epson Color Stylus printer driver
As shipped in IRIX 6.5.7. Unchanged since IRIX 6.5.
NAME epsonESCP2 - Epson Color Stylus printer driver SYNOPSIS epsonESCP2 -P printername [ options ] [ inputfile ] DESCRIPTION The epsonESCP2 driver is a printer-specific driver for the Epson Color Stylus, Color Stylus Pro and Color Stylus Pro XL printers. epsonESCP2 reads STIFF format image files and writes Epson ESC/P2 commands to standard out (the output is intended to be directed to the printer with an output device specific driver). The driver opens and updates the POD files for the specified printer. For more information on POD files refer to the libpod(3) and pod(4) man pages. INPUT FILE FORMAT epsonESCP2 assumes that its input is coming from standard input unless a filename is specified after any and all command line options. epsonESCP2 accepts the input files in chunky STIFF format and supports 1 bit K and 1 bit CMYK colorspaces. STIFF is a streamable subset of TIFF 6.0. For more information on the STIFF image file format, see the libstiff(3) man pages. USAGE -P printername Specifies the printer epsonESCP2 is driving. printername is the name under which the System V R3 spooler recognizes the printer, as given on the lp command line. This option is required. -s Specifies that the driver should exit after ascertaining printer status and updating the POD status file. -D Turns on debugging information. Five levels of debugging information are supported: None, CoarseDetail, MediumDetail, FineDetail, and EvenFinerDetail. These correspond to 0, 1, 2, 3, and 4 or more -D switches given on the command line. That is, multiple -D options given on the command line result in progressively more detailed debugging information. -X HorizontalResolution Specifies the horizontal resolution of the input STIFF file. 360 and 720 are supported. The default is 360. -Y VerticalResolution Specifies the vertical resolution of the input STIFF file. 360 and 720 are supported. The default is 360. -S PaperSize Specifies the papersize to request from the printer. This may be any papersize recognized by libpod(3), but only those sizes listed in the printer configuration file should be used. This is normally derived from the printer status database, but if given, it overrides and will be written to the printer status database. Four special sizes are supported for the Epson Stylus Pro XL. They are: A3+ (Epson supplied paper. Size is 297 x 483 mm.) B+ (Epson supplied paper. Size is 12.95 x 19.02 inches.) A3A3+ (Do a full bleed A3 on an A3+ paper. Requires A3+ paper.) BB+ (Do a full bleed B on an B+ paper. Requires B+ paper.) -M 0|1 Turn the MicroWeave feature on or off. 0 is off. 1 is on. -b 0|1 Turn the bidirectional printing feature on or off. 0 is off. 1 is on. If off, print head prints ink in one direction (slower but best quality). If on, print head prints ink in both directions. -d 0|1 Turn the MicroDot feature on or off. 0 is off. 1 is on. -B buffer_size Size of buffer to use to read and write data. Specified in bytes. EXIT CODES The driver normally exits with an exit code of zero (0), denoting no error. A number of exit codes are supported to give more information about unsuccessful exits. The error codes 1 through 18 denote the following meanings, in order: unknown error, bad command line or image header arguments, bad POD database access, bad device name, bad device type, bad status update, unsuccessful device access, bad memory reference, failed memory allocation, invalid data format, invalid data header, short or empty input data file, short or empty firmware download code file, bad or short input data file, failed transmission, data buffer invalid, test print failed, firmware download failed. A common error exit is on empty input: the driver will return error code 12, indicating a short or empty input file, whenever the PostScript interpreter (or another upstream filter) dies before a full page of data was written to the driver. This can happen when bad PostScript code is sent to be printed, for instance. In this case, the spooler log file (/var/spool/lp/log) should be consulted to determine which filter failed; an error should have been written to this file by the dying filter or driver. SEE ALSO psrip(1), impressario(1), printstatus(1), printpanel(1), libpod(3), libspool(3), libstiff(3).