Define the printer type

1. Create a file for the new printer that contains the information required for the "scoadmin printer setup manager" and appended to the system's model.stz(DSP/4dsp) file. An example is shown in the: oklaserit.stz file. A second sample file is shown in the mp2.model.stz file

   The ``key'', ``interface'', and name fields are mandatory; most printers should define all fields.

2. Create a terminfo(4) script that defines the printer's features. See the oklaserit.def file.

   A good generic terminfo entry for a printer is shown in epson_fx-850.def file. Another example is shown in mp2.def file

   • The first line, commonly referred to as the ``header line'', must begin in column one and must contain at least two aliases, separated by vertical bars.

   • The last field in the header line must be the long name of the device and it may contain any string. Alias names must be unique in the terminfo database and they must conform to UNIX system file naming conventions as discussed on the tic manual page. They cannot, for example, contain white space or slashes.

   • The remaining lines must begin with white space and contain a list of comma-separated fields that define the attributes supported by the printer.

   • White space after each comma is ignored.

   • Embedded commas must be escaped with a backslash character.

   Some common attributes that are used in these scribes are:

   
   cols

   number of columns in a line

   
   lines

   number of lines on a page

   
   cpi

   change number of characters per inch

   
   csnm

   list of character set names

   
   ff

   formfeed character

   
   lpi

   change number oflines per inch

   
   scs

   select character set

   
   slines

   set page length to #1 lines

   
   u9

   user string number 9

   Additional attributes that can be defined to utilize the features of more powerful printers are documented on the terminfo(4) manual page. See ``Using the terminfo database'' for additional information.

3. Run the tic utility on the oklaserit.def file to compile the terminfo entry into the terminfo database:

      tic oklaserit.def
   

   One entry is created for each of the aliases generated. By default, these entries are placed in the /usr/share/lib/terminfo directory tree, in the subdirectory that corresponds to the first letter or number of the alias name.

   See ``Printer interface scripts'' for more information.

4. The example printer uses the standard interface script. For printers that provide capabilities beyond the basic ones, create a Printer Interface Script using the routines documented on the curs_terminfo manual page. For example, the PS filter passes postscript output directly to the printer instead of processing a print job as if it were plain text and converting it to postscript. Use the /etc/lp/mode/standard file as a model; all Printer Interface Scripts must support all the basic options defined in the standard file. See ``Printer interface scripts''.