Software: Apache/2.0.54 (Fedora). PHP/5.0.4 

uname -a: Linux mina-info.me 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 

uid=48(apache) gid=48(apache) groups=48(apache)
context=system_u:system_r:httpd_sys_script_t 

Safe-mode: OFF (not secure)

/usr/share/doc/cups-1.1.23/   drwxr-xr-x
Free 3.78 GB of 27.03 GB (13.99%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     idd.html (49.48 KB)      -rw-r--r--

CUPS Interface Design Description

CUPS-IDD-1.1
Easy Software Products
Copyright 1997-2005, All Rights Reserved

Table of Contents

• 1.1 Identification
• 1.2 System Overview
• 1.3 Document Overview

• 2.1 CUPS Documentation
• 2.2 Other Documents

• 3.1 Character Set Files
  • 3.1.1 8-Bit Character Set Files
  • 3.1.2 Unicode Character Set Files
• 3.2 Language Files
• 3.3 MIME Files
  • 3.3.1 mime.types
  • 3.3.2 mime.convs
• 3.4 Option Files
• 3.5 PostScript Printer Description Files
  • 3.5.1 PPD Specification
  • 3.5.2 CUPS Extensions to PPD Files
• 3.6 Scheduler Configuration Files
  • 3.6.1 classes.conf
  • 3.6.2 cupsd.conf
  • 3.6.3 printers.conf

• 4.1 AppSocket Protocol
• 4.2 CUPS Browsing Protocol
• 4.3 CUPS Form File
  • 4.3.1 CUPS Form DTD
• 4.4 CUPS PostScript File
• 4.5 CUPS Raster File
• 4.6 CUPS Raw Files
• 4.7 Internet Printing Protocol
• 4.8 Line Printer Daemon Protocol
• 4.9 Server Message Block Protocol

• A.1 Terms
• A.2 Acronyms

1 Scope

1.1 Identification

This interface design description document provides detailed file formats, message formats, and program conventions for the Common UNIX Printing System ("CUPS") Version 1.1.

1.2 System Overview

CUPS provides a portable printing layer for UNIX®-based operating systems. It has been developed by Easy Software Products to promote a standard printing solution for all UNIX vendors and users. CUPS provides the System V and Berkeley command-line interfaces.

CUPS uses the Internet Printing Protocol ("IPP") as the basis for managing print jobs and queues. The Line Printer Daemon ("LPD") Server Message Block ("SMB"), and AppSocket (a.k.a. JetDirect) protocols are also supported with reduced functionality. CUPS adds network printer browsing and PostScript Printer Description ("PPD") based printing options to support real-world printing under UNIX.

CUPS includes an image file RIP that supports printing of image files to non-PostScript printers. A customized version of GNU Ghostscript 7.05 for CUPS called ESP Ghostscript is available separately to support printing of PostScript files within the CUPS driver framework. Sample drivers for Dymo, EPSON, HP, and OKIDATA printers are included that use these filters.

Drivers for thousands of printers are provided with our ESP Print Pro software, available at:

    http://www.easysw.com/printpro/

CUPS is licensed under the GNU General Public License and GNU Library General Public License. Please contact Easy Software Products for commercial support and "binary distribution" rights.

1.3 Document Overview

This interface design description document is organized into the following sections:

• 1 - Scope
• 2 - References
• 3 - Internal Interfaces
• 4 - External Interfaces
• 5 - Directories
• A - Glossary

2 References

2.1 CUPS Documentation

The following CUPS documentation is referenced by this document:

• CUPS-CMP-1.1: CUPS Configuration Management Plan
• CUPS-IDD-1.1: CUPS System Interface Design Description
• CUPS-IPP-1.1: CUPS Implementation of IPP
• CUPS-SAM-1.1.x: CUPS Software Administrators Manual
• CUPS-SDD-1.1: CUPS Software Design Description
• CUPS-SPM-1.1.x: CUPS Software Programming Manual
• CUPS-SSR-1.1: CUPS Software Security Report
• CUPS-STP-1.1: CUPS Software Test Plan
• CUPS-SUM-1.1.x: CUPS Software Users Manual
• CUPS-SVD-1.1: CUPS Software Version Description

2.2 Other Documents

The following non-CUPS documents are referenced by this document:

• Adobe PostScript Printer Description File Format Specification, Version 4.3.
• Adobe PostScript Language Reference, Third Edition.
• IPP/1.1: Implementers Guide
• RFC 1179, Line Printer Daemon Protocol
• RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax
• RFC 2567, Design Goals for an Internet Printing Protocol
• RFC 2568, Rationale for the Structure of the Model and Protocol for the Internet Printing Protocol
• RFC 2569, Mapping between LPD and IPP Protocols
• RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1
• RFC 2617, HTTP Authentication: Basic and Digest Access Authentication
• RFC 2910, IPP/1.1: Encoding and Transport
• RFC 2911, IPP/1.1: Model and Semantics
• RFC 3380, IPP: Job and Printer Set Operations

3 Internal Interfaces

3.1 Character Set Files

The character set files define a mapping between 8-bit characters and the Unicode character set, or between Unicode and printer fonts. They are named using the IETF charset names defined in RFCnnnn. These files are ASCII text, the content of which is described below. Comments can be included by using the # character in the first column of a line.

3.1.1 8-Bit Character Set Files

8-bit character set files start with a line reading:

charset 8bit

Following this are lines that define the font information:

first last direction width normal bold italic bold-italic

First and last are the first and last glyphs in the font mapping that correspond to that font; a maximum of 256 characters can be mapped within each group, with a maximum of 256 mappings (this is a PostScript limitation.) The glyph values are hexadecimal.

Direction is the string "ltor", "rtol", or "rtola" indicating left-to-right, right-to-left, or right-to-left Arabic text.

Width is the string "single" or "double"; double means that the glyphs are twice as wide as ASCII characters in the Courier typeface.

Normal, bold, italic, and bold-italic are the typefaces to use for each presentation. If characters are only available in a single style then only one typeface should be listed (e.g. "Symbol".) Each font that is listed will be used (and downloaded if needed) when printing.

The remaining lines define a character to Unicode glyph mapping for the character set. The character and glyph values are hexadecimal:

xx yyyy

3.1.2 Unicode Character Set Files

Unicode character set files start with a line reading:

charset encoding

Encoding is the encoding to use for the text; currently only the string "utf8" is supported.

Following this are lines defining the font information:

first last direction width normal bold italic bold-italic

First and last are the first and last glyphs in the font mapping that correspond to that font; a maximum of 256 characters can be mapped within each group, with a maximum of 256 mappings (this is a PostScript limitation.) The glyph values are hexadecimal.

Direction is the string "ltor", "rtol", or "rtola" indicating left-to-right, right-to-left, or right-to-left Arabic text.

Width is the string "single" or "double"; double means that the glyphs are twice as wide as ASCII characters in the Courier typeface.

Normal, bold, italic, and bold-italic are the typefaces to use for each presentation. If characters are only available in a single style then only one typeface should be listed (e.g. "Symbol".) Each font that is listed will be used (and downloaded if needed) when printing.

3.2 Language Files

The language files define the default character set and a collection of text messages in that language. They are named by prefixing the string "cups_" to the front of the language specifier (e.g. "cups_en", "cups_fr", etc.) Each file consists of two or more lines of ASCII text.

The first line identifies the character set to be used for the messages. The currently recognized values are:

• iso-8859-1
• iso-8859-2
• iso-8859-3
• iso-8859-4
• iso-8859-5
• iso-8859-6
• iso-8859-7
• iso-8859-8
• iso-8859-9
• iso-8859-10
• iso-8859-13
• iso-8859-14
• iso-8859-15
• us-ascii
• utf-8
• windows-874
• windows-1250
• windows-1251
• windows-1252
• windows-1253
• windows-1254
• windows-1255
• windows-1256
• windows-1257
• windows-1258
• koi8-r
• koi8-u

The second and succeeding lines define text messages. If the message text is preceded by a number, then the current message number is updated and the text after the number is used.

3.3 MIME Files

CUPS uses two MIME files in its standard configuration.

3.3.1 mime.types

The mime.types file defines the recognized file types and consists of 1 or more lines of ASCII text. Comment lines start with the pound ("#") character. The backslash ("\") character can be used at the end of a line to continue that line to the next.

Each non-blank line starts with a MIME type identifier ("super/type") as registered with the IANA. All text following the MIME type is treated as a series of type recognition rules:

mime-type := super "/" type { SP rule }*
super := { "a-z" | "A-Z" }*
type := { "a-z" | "A-Z" | "-" | "." | "0-9" }*
rule := { extension | match | operator | "(" rule ")" }*
extension := { "a-z" | "A-Z" | "0-9" }*
match := "match(" regexp ")" |
         "ascii(" offset "," length ")" |
	 "printable(" offset "," length ")" |
	 "string(" offset "," string ")" |
	 "contains(" offset "," length "," string ")" |
	 "char(" offset "," value ")" |
	 "short(" offset "," value ")" |
	 "int(" offset "," value ")" |
	 "locale(" string ")"
operator := "+" |	[ logical AND ]
            "," | SP    [ logical OR ]
	    "!"         [ unary NOT ]

The int and short rules match look for integers in network byte order (a.k.a. big-endian) with the most-significant byte first.

3.3.2 mime.convs

The mime.types file defines the recognized file filters and consists of 1 or more lines of ASCII text. Comment lines start with the pound ("#") character.

Each non-blank line starts with two MIME type identifiers ("super/type") representing the source and destination types. Following the MIME types are a cost value (0 to 100) and the filter program to use. If the filter program is not specified using the full path then it must reside in the CUPS filter directory:

super/type SP super/type2 SP cost SP program

3.4 Option Files

CUPS maintains user-defined printer and option files for each printer and user on the system. The printers and options defined in the system option file (/etc/cups/lpoptions) are loaded first, followed by the user option file ($HOME/.lpoptions). Options in the user file replace those defined in the system file for the same destination. Each line in the files can be one of the following:

Dest name option=value option=value ... option=value
Dest name/instance option=value option=value ... option=value
Default name option=value option=value ... option=value
Default name/instance option=value option=value ... option=value

The line beginning with "Default" indicates the default destination for print jobs; a default line in the user option file overrides the default defined in the system option file.

Name is the name of a printer known to the local server.

Instance can be any string of letters, numbers, and the underscore up to 127 characters in length.

The remainder of the line contains a list of space-separated options and their values.

3.5 PostScript Printer Description Files

PostScript Printer Description ("PPD") files describe the capabilities of each printer and are used by CUPS to support printer-specific features and intelligent filtering.

3.5.1 PPD Specification

The PPD file format is described in Adobe TechNote #5003: PostScript Printer Description File Format Specification Version 4.3.

3.5.2 CUPS Extensions to PPD Files

CUPS adds several new attributes that are described below.

3.5.2.1 cupsFax

This optional boolean attributes specifies whether the printer should be treated as a facsimile device, where failed jobs should be retried according to the FaxRetryInterval and FaxRetryLimit directives in the cupsd.conf file.

3.5.2.2 cupsFilter

This optional string attribute provides a conversion rule of the form:

source/type cost program

The destination type is assumed to the printer's type. If a printer supports the source type directly the special filter program "-" may be specified.

3.5.2.3 cupsFlipDuplex

This optional boolean attribute notifies the RIP filters that the destination printer requires an upside-down image for the back page. The default value is false.

3.5.2.4 cupsManualCopies

This optional boolean attribute notifies the RIP filters that the destination printer does not support copy generation in hardware. The default value is false.

3.5.2.5 cupsModelNumber

This optional integer attribute specifies a printer-specific model number. This number can be used by a filter program to adjust the output for a specific model of printer.

3.5.2.6 cupsProfile

This optional string attribute specifies a color profile of the form:

resolution/type density gamma m00 m01 m02 m10 m11 m12 m20 m21 m22

The resolution and type values may be "-" to act as a wildcard. Otherwise they must match one of the Resolution or MediaType attributes defined in the PPD file.

The density and gamma values define gamma and density adjustment function such that:

f(x) = density * xgamma

The m00 through m22 values define a 3x3 transformation matrix for the CMY color values. The density function is applied after the CMY transformation.

3.5.2.7 cupsProtocol

This optional attribute describes which binary communication protocol to use when printing binary PostScript data. The strings "None", "BCP", and "TBCP" are recognized, corresponding to no encoding, BCP, and TBCP respectively.

3.5.2.8 cupsVersion

This required attribute describes which version of the CUPS IDD was used for the PPD file extensions. Currently it must be the string "1.0" or "1.1".

3.6 Scheduler Configuration Files

The scheduler reads three configuration files that define the available printers, classes, and services:

classes.conf

This file defines all of the printer classes known to the system.

cupsd.conf

This file defines the files, directories, passwords, etc. used by the scheduler.

printers.conf

This file defines all of the printers known to the system.

3.6.1 classes.conf

The classes.conf file consists of 1 or more lines of ASCII text. Comment lines start with the pound ("#") character.

Each non-blank line starts with the name of a configuration directive followed by its value. The following directives are understood:

3.6.2 cupsd.conf

The cupsd.conf file consists of 1 or more lines of ASCII text. Comment lines start with the pound ("#") character.

Each non-blank line starts with the name of a configuration directive followed by its value. The following directives are understood:

3.6.3 printers.conf

The printers.conf file consists of 1 or more lines of ASCII text. Comment lines start with the pound ("#") character.

Each non-blank line starts with the name of a configuration directive followed by its value. The following directives are understood:

4 External Interfaces

4.1 AppSocket Protocol

The AppSocket protocol is an 8-bit clean TCP/IP socket connection. The default IP service port is 9100. The URI method name is "socket".

The AppSocket protocol is used by the Hewlett Packard JetDirect network interfaces and print servers, as well as many other vendors' products. See the CUPS Software Administrators Manual for a list of supported products.

4.2 CUPS Browsing Protocol

The CUPS Browsing Protocol is a UDP/IP-based broadcast service. By default this service operates on IP service port 631.

Each broadcast packet describes the state of a single printer or class and is an ASCII text string of up to 1450 bytes ending with a newline (0x0a). The string is formatted as follows:

type SP state SP uri SP "location" SP "info" SP "make-and-model" NL

State, uri, location, info, and make-and-model, correspond to the IPP printer-state, printer-uri-supported, printer-location, printer-info, and printer-make-and-model attributes.

Type is a hexadecimal number string representing capability/type bits:

4.3 CUPS Form File

CUPS Form files are XML files used by the CUPS formtops filter to produce dynamic banner pages and support preprinted forms.

The MIME type for CUPS Form files is application/vnd.cups-form .

4.3.1 CUPS Form DTD

The following DTD describes the available elements and attributes in a CUPS Form file:

<!ENTITY % Angle "CDATA" -- angle in degrees -->

<!ENTITY % Color "CDATA" -- a color using sRGB: #RRGGBB as Hex values -->

<!ENTITY % Length "CDATA" -- nn for pixels or nn% for percentage length -->

<!ENTITY % Lengths "CDATA" -- comma-separated Length values -->

<!ENTITY % Text "CDATA">

<!ENTITY % heading "H1|H2|H3|H4|H5|H6">

<!ENTITY % preformatted "PRE">

<!ENTITY % i18n
 "lang        %LanguageCode; #IMPLIED  -- language code --
  dir         (ltr|rtl)      #IMPLIED  -- direction for weak/neutral text --"
  >

<!ENTITY % attrs "%i18n;">

<!ENTITY % fontstyle
 "B | FONT | I | TT">

<!ENTITY % graphics
 "BOX | RECT | LINE | POLY | ARC | PIE | TEXT">

<!ENTITY % insert
 "IMG | VAR">

<!-- %inline; covers inline or "text-level" elements -->
<!ENTITY % inline "#PCDATA | %fontstyle; | %graphics; | %insert;">

<!ELEMENT (%fontstyle;) - - (%inline;)*>
<!ATTLIST (%fontstyle;)
  %attrs;                              -- %i18n --
  >

<!ELEMENT BR - O EMPTY                 -- forced line break -->
<!ATTLIST BR
  %attrs;                              -- %i18n --
  >

<!ENTITY % block
     "P | %heading; | %preformatted;">

<!ENTITY % flow "%block; | %inline;">

<!ELEMENT PAGE O O (%flow;)+           -- document body -->
<!ATTLIST PAGE
  %attrs;                              -- %i18n --
  align       (left|center|right) #IMPLIED -- horizontal alignment --
  valign      (top|middle|center|bottom) #IMPLIED -- vertical alignment --
  >

<!ELEMENT P - O (%inline;)*            -- paragraph -->
<!ATTLIST P
  %attrs;                              -- %i18n --
  align       (left|center|right) #IMPLIED -- horizontal alignment --
  >

<!ELEMENT (%heading;)  - - (%inline;)* -- heading -->
<!ATTLIST (%heading;)
  %attrs;                              -- %i18n --
  align       (left|center|right) #IMPLIED -- horizontal alignment --
  >

<!ELEMENT PRE - - (%inline;)*          -- preformatted text -->
<!ATTLIST PRE
  %attrs;                              -- %i18n --
  align       (left|center|right) #IMPLIED -- horizontal alignment --
  >

<!ELEMENT BOX - O EMPTY                -- unfilled box -->
<!ATTLIST BOX
  color       %Color;        #IMPLIED  -- override color --
  height      %Length;       #REQUIRED -- height of box --
  thickness   %Length;       #IMPLIED  -- override line thickness --
  width       %Length;       #REQUIRED -- width of box --
  x           %Length;       #REQUIRED -- horizontal position --
  y           %Length;       #REQUIRED -- vertical position --
  >

<!ELEMENT RECT - O EMPTY               -- filled box -->
<!ATTLIST RECT
  color       %Color;        #IMPLIED  -- override color --
  height      %Length;       #REQUIRED -- height of box --
  width       %Length;       #REQUIRED -- width of box --
  x           %Length;       #REQUIRED -- horizontal position --
  y           %Length;       #REQUIRED -- vertical position --
  >

<!ELEMENT LINE - O EMPTY               -- polyline -->
<!ATTLIST LINE
  color       %Color;        #IMPLIED  -- override color --
  thickness   %Length;       #IMPLIED  -- override line thickness --
  x           %Lengths;      #REQUIRED -- horizontal positions --
  y           %Lengths;      #REQUIRED -- vertical positions --
  >

<!ELEMENT POLY - O EMPTY               -- polygon (filled) -->
<!ATTLIST POLY
  color       %Color;        #IMPLIED  -- override color --
  x           %Lengths;      #REQUIRED -- horizontal positions --
  y           %Lengths;      #REQUIRED -- vertical positions --
  >

<!ELEMENT ARC - O EMPTY                -- unfilled arc -->
<!ATTLIST ARC
  color       %Color;        #IMPLIED  -- override color --
  end         %Angle;        #IMPLIED  -- override end angle --
  height      %Length;       #REQUIRED -- height of arc --
  start       %Angle;        #IMPLIED  -- override start angle --
  thickness   %Length;       #IMPLIED  -- override line thickness --
  width       %Length;       #REQUIRED -- width of arc --
  x           %Length;       #REQUIRED -- horizontal position --
  y           %Length;       #REQUIRED -- vertical position --
  >

<!ELEMENT PIE - O EMPTY                -- filled arc -->
<!ATTLIST PIE
  color       %Color;        #IMPLIED  -- override color --
  end         %Angle;        #IMPLIED  -- override end angle --
  height      %Length;       #REQUIRED -- height of arc --
  start       %Angle;        #IMPLIED  -- override start angle --
  width       %Length;       #REQUIRED -- width of arc --
  x           %Length;       #REQUIRED -- horizontal position --
  y           %Length;       #REQUIRED -- vertical position --
  >

<!ELEMENT TEXT - - (%flow;)*           -- text box -->
<!ATTLIST RECT
  align       (left|center|right) #IMPLIED -- horizontal alignment --
  height      %Length;       #REQUIRED -- height of box --
  valign      (top|middle|center|bottom) #IMPLIED -- vertical alignment --
  width       %Length;       #REQUIRED -- width of box --
  x           %Length;       #REQUIRED -- horizontal position --
  y           %Length;       #REQUIRED -- vertical position --
  >


<!ELEMENT IMG - O EMPTY                -- Embedded image -->
<!ATTLIST IMG
  %attrs;                              -- %coreattrs, %i18n, %events --
  src         %URI;          #REQUIRED -- URI of image to embed --
  height      %Length;       #IMPLIED  -- override height --
  width       %Length;       #IMPLIED  -- override width --
  >

<!ELEMENT HEAD O O (DEFVAR)*           -- document head -->
<!ATTLIST HEAD
  %i18n;                               -- lang, dir --
  >

<!ELEMENT DEFVAR - O EMPTY             -- variable definition -->
<!ATTLIST DEFVAR
  name        CDATA          #REQUIRED -- name
  value       CDATA          #REQUIRED -- value
  >


<!ENTITY % html.content "HEAD, PAGE">

<!ELEMENT CUPSFORM - - (HEAD) (PAGE)+  -- document root element -->
<!ATTLIST CUPSFORM
  %i18n;                               -- lang, dir --
  >

4.4 CUPS PostScript File

CUPS PostScript files are device-dependent Adobe PostScript program files. The PostScript language is described in the Adobe PostScript Language Reference Manual, Third Edition.

The MIME type for CUPS PostScript files is application/vnd.cups-postscript.

4.5 CUPS Raster File

CUPS raster files are device-dependent raster image files that contain a PostScript page device dictionary and device-dependent raster imagery for each page in the document. These files are used to transfer raster data from the PostScript and image file RIPs to device-dependent filters that convert the raster data to a printable format.

A raster file begins with a four byte synchronization word: 0x52615374 ("RaSt") for big-endian architectures and 0x74536152 ("tSaR") for little-endian architectures. The writer of the raster file will use the native word order, and the reader is responsible for detecting a reversed word order file and swapping bytes as needed. The CUPS Image Library raster functions perform this function automatically.

Following the synchronization word are a series of raster pages. Each page starts with a page device dictionary header and is followed immediately by the raster data for that page.

The MIME type for CUPS Raster files is application/vnd.cups-raster.

4.6 CUPS Raw Files

Raw files are printer-dependent print files that are in a format suitable to the destination printer (e.g. HP-PCL, HP-RTL, etc.) The MIME type for CUPS Raw files is application/vnd.cups-raw.

4.7 Internet Printing Protocol

The Internet Printing Protocol and the CUPS extensions to it are described in the CUPS Implementation of IPP document.

4.8 Line Printer Daemon Protocol

The Line Printer Daemon (LPD) protocol is described by RFC 1179: Line Printer Daemon Protocol.

The URI method name for LPD is "lpd".

4.9 Server Message Block Protocol

The Server Message Block (SMB) and related Common Internet File System (CIFS) protocols are described at http://anu.samba.org/cifs.

The URI method name for SMB is "smb". Support for this protocol is provided via the SAMBA smbspool(1) program provided with SAMBA 2.0.6 and higher.

5 Directories

/etc/cups

The scheduler configuration and MIME files reside here.

/etc/cups/certs

The authentication certificates reside here.

/etc/cups/interfaces

System V interface scripts reside here.

/etc/cups/ppd

This directory contains PPD files for each printer.

/usr/bin

The cancel, lp, lpq, lpr, lprm, and lpstat commands reside here.

/usr/lib, /usr/lib32

The shared libraries (DSOs) reside here.

/usr/lib/cups/backend

The backend filters reside here.

/usr/lib/cups/cgi-bin

The CGI programs reside here.

/usr/lib/cups/daemon

The polling and LPD daemons reside here.

/usr/lib/cups/filter

The file filters reside here.

/usr/sbin

The accept, cupsd, lpadmin, lpc, and reject commands reside here.

/usr/share/cups

This is the root directory of the CUPS static data.

/usr/share/cups/charsets

The character set files reside here.

/usr/share/cups/data

The filter data files reside here.

/usr/share/cups/fonts

The pstoraster font files reside here.

/usr/share/cups/model

The sample PPD files reside here.

/usr/share/cups/pstoraster

The pstoraster data files reside here.

/usr/share/doc/cups

The scheduler documentation files reside here.

/var/log/cups

The access_log, error_log, and page_log files reside here.

/var/spool/cups

This directory contains print job files.

A Glossary

A.1 Terms

C

A computer language.

parallel

Sending or receiving data more than 1 bit at a time.

pipe

A one-way communications channel between two programs.

serial

Sending or receiving data 1 bit at a time.

socket

A two-way network communications channel.

A.2 Acronyms

ASCII

American Standard Code for Information Interchange

CUPS

Common UNIX Printing System

ESC/P

EPSON Standard Code for Printers

FTP

File Transfer Protocol

HP-GL

Hewlett-Packard Graphics Language

HP-PCL

Hewlett-Packard Page Control Language

HP-PJL

Hewlett-Packard Printer Job Language

IETF

Internet Engineering Task Force

IPP

Internet Printing Protocol

ISO

International Standards Organization

LPD

Line Printer Daemon

MIME

Multimedia Internet Mail Exchange

PPD

PostScript Printer Description

SMB

Server Message Block

TFTP

Trivial File Transfer Protocol