Changes between Initial Version and Version 1 of CupsFaq

Timestamp:

Sep 2, 2010, 1:12:27 PM (14 years ago)

Author:

Alex Taylor

Comment:

Initial version

CupsFaq

@@ +1 @@
+{{{
+#!html
+<h1>eCups Frequently Asked Questions</h1>
+
+<p><a href="#1_0">1.  General Information</a>
+<ul style="list-style-type: none;">
+<li><a href="#1_1">1.1.  What is eCups?</a>
+<li><a href="#1_2">1.2.  All right then, what is CUPS?</a>
+<li><a href="#1_3">1.3.  Another spooler?  Doesn't OS/2 already have a print spooler?</a>
+<li><a href="#1_4">1.4.  How does CUPS work?</a>
+<li><a href="#1_5">1.5.  How does CUPS fit into OS/2?</a>
+<li><a href="#1_6">1.6.  What limitations does eCups have?</a>
+<li><a href="#1_7">1.7.  Are there any known problems with eCups?</a>
+</ul></p>
+
+<p><a href="#2_0">2.  Configuration &amp; Use</a>
+<ul style="list-style-type: none;">
+<li><a href="#2_1">2.1.  How do I set up eCups on my system?</a>
+<li><a href="#2_2">2.2.  What printers are supported?</a>
+<li><a href="#2_3">2.3.  How do I install support for a printer which isn't listed?</a>
+<li><a href="#2_4">2.4.  Where can I find PPD files?</a>
+<li><a href="#2_5">2.5.  I can't import my PPD into ECUPS.DRV, what should I do?</a>
+<li><a href="#2_6">2.6.  What's the difference between all these network device types (<em>ipp://</em>, <em>lpd://</em>, <em>socket://</em>, etc.)?</a>
+<li><a href="#2_7">2.7.  What are the "Simplified" printer drivers for?</a>
+<li><a href="#2_8">2.8.  Why do I need to create <em>both</em> a CUPS printer <em>and</em> an OS/2 printer object?</a>
+<li><a href="#2_9">2.9.  Where should I define the printer settings: in the OS/2 printer properties, or in CUPS?</a>
+</ul></p>
+<p><a href="#3_0">3.  Troubleshooting</a>
+<ul style="list-style-type: none;">
+<li><a name="1_0"></a>
+</ul></p>
+
+
+<h2>1.  General Information</h2>
+
+<a name="1_1"></a>
+<h3>1.1.  What is eCups?</h3>
+
+<p>eCups is complete printing framework which is designed to allow the support of
+modern printers which lack &#x2018;native&#x2019; OS/2 print drivers.
+
+<p>eCups includes the following components:
+
+<ul>
+<li>CUPS (ported by Paul Smedley)
+<li>GhostScript (ported by Paul Smedley)
+<li>Print driver packages such as Gutenprint, Splix, & HPLIP (ported by Paul Smedley)
+<li>eCups port driver (various authors; based on LPR32 by Serge Sterck)
+<li>eCups PostScript driver (various authors; based on modified IBM PSCRIPT.DRV)
+<li>foomatic-rip filter (ported by Alex Taylor and Paul Smedley)
+</ul>
+
+<p>Although the terms are sometimes used interchangeably, there is a distinction
+between eCups and CUPS.  eCups is basically a framework of related products and
+tools for integrating the CUPS product into OS/2 and eComStation.
+
+
+<a name="1_2"></a>
+<h3>1.2.  All right then, what is CUPS?</h3>
+
+<p>CUPS stands for <em>Common Unix Printing System</em>.  As the name implies,
+it was originally designed to be a generic framework for printer support under
+various UNIX systems.  Since then, it has been adopted as the main printing
+engine under Linux and MacOS X as well.
+
+<p>It is important to keep in mind that CUPS is not a printer driver.  At its
+most fundamental level, CUPS is essentially a print spooler plus a collection of
+data conversion modules.
+
+<p>The actual printer &#x2018;drivers&#x2019; are located in addon packages like Gutenprint.
+CUPS itself does have a few built-in generic drivers, but generally you need at
+least one driver package installed in addition to CUPS itself.
+
+
+<a name="1_3"></a>
+<h3>1.3.  Another spooler?  Doesn't OS/2 already have a print spooler?</h3>
+
+<p>Yes, it does... but the OS/2 spooler is only capable of receiving print jobs
+sent by various applications, converting them with a native OS/2 printer driver,
+and then sending them straight to the printer port (plus logic for managing the
+job queue, of course).
+
+<p>The CUPS spooler, by contrast, is able to perform a number of vital additional
+tasks during the process of sending a job to the printer.  These tasks are what
+allow CUPS to support such a vast range of printers.
+
+
+<a name="1_4"></a>
+<h3>1.4.  How does CUPS work?</h3>
+
+<p>First of all, CUPS makes extensive use of PostScript, which is an open and
+widely-used standard for data formatting.  A basic understanding of how
+PostScript normally works with regards to printing is needed in order to
+properly explain how CUPS works.  Refer to the box below for a brief summary,
+or just skip past it if you already know this.
+
+<div style="font-size: smaller; background: #e0e0e0; padding-left: 1em; padding-right: 1em; border: thin solid black;">
+<p><b>PostScript and Printing</b></p>
+
+<p>Different printers require the data they receive for printing to be in a
+particular format or printer &#x2018;language&#x2019;.  Naturally, printers from
+any given manufacturer typically use that manufacturer's own proprietary printer
+language.  But even different printers from the same manufacturer often use
+slightly (or occasionally even radically) different variations of these languages.
+This is, of course, why we need specific drivers for our printers in the first
+place.
+
+<p>Some printers, however, (especially higher-end laser printers) are <em>PostScript</em>
+printers, meaning that they use PostScript as their printer language.  (Often,
+it must be said, in addition to the manufacturer's proprietary language.)
+Because PostScript is an open, mature, and fully standardized language, this
+generally means that <em>any</em> printer driver which outputs generic PostScript
+data can print to any PostScript printer.
+
+<p>In this case, the individual capabilities of the printer (such as paper size,
+DPI, number and type of trays, duplexing, etc.) are provided by the manufacturer
+in standardized format via an ASCII file called a PostScript Printer Description
+(PPD).
+
+<p>The standard OS/2 PostScript printer driver includes a utility called PIN which
+allows these PPDs to be imported, thereby adding printer-specific support for
+the model in question without the need for new drivers.
+
+<p>Of course, since PostScript is a standardized language, it should also be
+possible to print to any PostScript printer using only generic settings (the
+PostScript driver includes a definition called "Generic PostScript Printer" for
+this purpose).  As you would expect, however, using a generic printer definition
+does not let you take advantage of printer-specific features.
+
+<p>Given the above, there is rarely a problem with using any model of PostScript
+printer under OS/2, as long as a PPD for that printer is available.  Where we
+need something like CUPS is for non-PostScript printers (of which, regrettably,
+there are many).
+</div>
+
+<p>Basically, what CUPS does is add a PostScript emulation layer on top of all
+printers.  That is to say, from the perspective of the operating system and
+applications, CUPS turns every printer into a PostScript printer.  It
+accomplishes this emulation through a complex system of conversion utilities.
+
+<p>Because CUPS presents all printers as PostScript, it expects to receive
+incoming printer jobs in PostScript format.  Generally, this is the
+responsibility of whatever passes the print job to CUPS in the first place,
+although CUPS is capable of converting a few specific file formats into
+PostScript on its own (such as plain text, PDF, or certain image formats).
+
+<p>CUPS takes each printer job it receives through the following steps:
+
+<ol style="list-style-type: upper-alpha; font-size: smaller;">
+<li>Receives the printer job data as a PostScript file.  If the file CUPS
+    receives is not PostScript, but is in another supported format, it calls
+    one of a number of &#x2018;pre-filter&#x2018; utilities to convert it
+    into PostScript.
+
+    <p>(Some types of image file can be converted directly to CUPS-Raster format
+    (see step C) when printing to a non-PostScript printer; in this case, CUPS
+    skips step B and the first part of step C.)</p>
+
+<li>Uses the configured printer settings (defined via PPD and configured in the
+    CUPS administration GUI and/or the desktop printer object) to add printer-
+    and job-specific options to the PostScript data.
+
+    <p>If printing to a genuine PostScript printer, this data is then sent directly
+    to the backend for printing (step D).  Otherwise, it proceeds to step C.</p>
+
+<li>Passes the data to a program, or series of programs, for final processing.
+    These programs are known as &#x2018;filters&#x2018;, and are responsible for
+    converting the PostScript data into the printer's native language.
+
+    <p>The first filter, in most configurations, is "pstoraster", which uses
+    GhostScript to convert the PostScript data into an intermediate format
+    called  "CUPS-Raster".  (This format is supported by GhostScript as one
+    of its available output formats.)</p>
+
+    <p>The CUPS-Raster data is then passed to another program which knows how to
+    convert it into printer-specific data.  (This latter program can thus, in
+    a sense, be considered the actual printer &#x2018;driver&#x2019;.)  CUPS has a few built-
+    in programs for some common printer languages (generic support only), but
+    more commonly an external driver package will be used.  The largest such
+    driver package is called "Gutenprint" (formerly called "gimp-print", as it
+    was originally developed for The GIMP), which provides support for a large
+    number of (mostly inkjet) printers.  Other packages include HPLIP and Splix.</p>
+
+    <p>As it happens, GhostScript itself includes a number of printer drivers which
+    aren't available in other packages like Gutenprint.  In this case, the
+    PostScript data can be converted directly to printer-specific format, rather
+    than going through the process of CUPS-Raster --> external driver package.
+    In cases like this, an alternative filter called "foomatic-rip" (or simply
+    "Foomatic") gets called instead of pstoraster.  Using instructions in the
+    PPD file, Foomatic calls GhostScript in order to convert the PostScript data
+    &mdash; not into CUPS-Raster format, but directly into the printer's native
+    format instead.  The usual second step of calling an external driver package
+    is thus omitted.  (Note that printers which use Foomatic for their drivers
+    require a special PPD file with the required instructions.)</p>
+
+    <p>Whatever filters are called, at the end of this phase, CUPS should have a
+    printer data file which is now in the printer's own native format, ready for
+    actual printing.</p>
+
+<li>Passes the printer data to the &#x2018;backend&#x2018;.  This is the term used
+    for CUPS's internal equivalent of a port driver: it controls the physical
+    communication with the printer.  Available backends include:
+    <ul>
+     <li>USB, for USB-connected printers.
+     <li>IPP, for network printers on a TCP/IP network.
+     <li>SMB, for network printers being managed by a CIFS server like Samba.
+    </ul><p>
+
+<li>The backend passes the data to the printer, and the job is finally printed.
+</ol>
+
+<p>A flowchart showing the various steps in more detail can be seen
+<a href="http://www.linuxfoundation.org/sites/main/files/static/cups-system-ascii.html">here</a>.
+
+<p>See below for a more simplified flowchart which shows how these steps fit into
+the eCups framework under OS/2.
+
+
+<a name="1_5"></a>
+<h3>1.5.  How does CUPS fit into OS/2?</h3>
+
+<p>All CUPS printers are managed by the CUPS daemon, which is responsible for the
+whole process between receiving the initial job (in PostScript format), through
+all the filters and converters, to the backend whence it is passed off to the
+actual printer.
+
+<p>Once a printer is configured in CUPS, it is possible to print test pages from
+the CUPS administration GUI, as well as send files (or at least those in one of
+the supported formats) directly to the CUPS printer from a command line using
+the cupslpr utility.
+
+<p>To print from OS/2 applications, however, it is necessary to create a normal
+OS/2 printer object.
+
+<p>Wait! you ask.  If we can already print files to the CUPS printer, why is it
+necessary to create an OS/2 printer as well?
+
+<p>Well, we can print using CUPS's own internal tools.  The OS/2 printer object
+will be needed for the more general case.  Basically, normal OS/2 (Presentation
+Manager) applications only know how to print to an OS/2 printer queue.  They
+know nothing about any CUPS printers.  So all our programs will be printing to
+our standard OS/2 printer object, and that gets sent on to CUPS.
+
+<p>How does that work?  Well, we can redirect the jobs that get sent to an OS/2
+printer so they end up going through CUPS.  The OS/2 printing subsystem actually
+provides a mechanism for doing this, via a custom port driver.  Instead of
+configuring the printer for LPTx or COMx, eCups includes a port driver,
+CUPS.PDR, which passes all jobs on to the CUPS daemon.
+
+<p>There's more; remember that CUPS needs the print jobs it receives to be in
+PostScript format before it can process them.  CUPS does know how to convert a
+few specific file types into PostScript on its own, but it's not designed to
+handle the GPI format generated by most OS/2 applications.  Happily, the OS/2
+printer drivers are specifically designed to handle GPI data... and the
+PostScript printer driver in particular generates &mdash; naturally &mdash; a
+PostScript file, which then gets handed off to the printer.  So, we just pass
+that file along to CUPS.
+
+<p>It's certainly possible to use the standard OS/2 PostScript driver for this.
+However, the eCups team has provided an updated PostScript driver called
+ECUPS.DRV; this is actually based on the standard PostScript driver, but with
+various fixes and other improvements to make it work with CUPS more smoothly.
+
+<p>The general flow of operation thus looks something like the following (greatly
+simplified, of course):
+
+<pre>
++-------------+
+| Application |
++-------------+
+       |
+       | (OS/2-GPI printer format)
+       |
+*======|=================== OS/2 PRINTER OBJECT =============================*
+#      |                                                                     #
+#      v                                                                     #
+#   +---------------------------------------+                                #
+#   | PostScript printer driver (ECUPS.DRV) |                                #
+#   +---------------------------------------+                                #
+#                                    |                                       #
+#                                    | (PostScript data)                     #
+#                                    v                                       #
+#                      +-----------------------------+                       #
+#                      | CUPS port driver (CUPS.PDR) |                       #
+#                      +-----------------------------+                       #
+#                                    |                                       #
+*====================================|=======================================*
+                                     |
+*======================= CUPS =======|=======================================*
+#                                    |                                       #
+#                                    | (Incoming PostScript data) (A)        #
+#                                    v                                       #
+#                            +---------------+                               #
+#                            | 'pstops' (B)  |                               #
+#                            +---------------+                               #
+#                                    |                                       #
+#                                    | (Printer-specific PostScript data)    #
+#                                    |                                       #
+#                                    |                                       #
+#      PostScript printer?           |       Built in GhostScript driver?    #
+#          +------------------------< >---------------------+                #
+#          |                         |                      |                #
+#          |       CUPS or 3rd-party | driver module?       |                #
+#          |                         |                      v                #
+#          |                         v                +--------------------+ #
+#          |                +------------------+      | 'foomatic-rip' (C) | #
+#          |                | 'pstoraster' (C) |      +--------------------+ #
+#          |                +------------------+                   |         #
+#          |                         |                             |         #
+#          |                         | (CUPS-Raster format)        |         #
+#          |                         v                             |         #
+#          |           +-----------------------------+             |         #
+#          |           | Printer-specific driver (C) |             |         #
+#          |           +-----------------------------+             |         #
+#          |                         |                             |         #
+#          | (PostScript)            | <-(Printer-native format)-> |         #
+#          |                         |                             |         #
+#          v                         v                             v         #
+#    +------------------------------------------------------------------+    #
+#    | CUPS backend (parallel/serial/USB/IPP/LPD/SMB/AppleTalk/etc. (D) |    #
+#    +------------------------------------------------------------------+    #
+#                                    |                                       #
+*====================================|=======================================*
+                                     |
+                                     V
+                              +-------------+
+                              | PRINTER (E) |
+                              +-------------+
+</pre>
+
+<p>The box labelled "CUPS" indicates components which are part of the cross-
+platform CUPS system.  The whole diagram, with the exception of the application
+at the top and the printer at the bottom, comprises the eCups framework.
+
+
+<a name="1_6"></a>
+<h3>1.6.  What limitations does eCups have?</h3>
+
+<p>CUPS involves a long and exceedingly complex chain of interlocking stages, many
+of which consist of separate programs.  If something goes wrong somewhere along
+the line, it can be very difficult to pinpoint the failing component.
+
+<p>At the moment, installing and configuring eCups is a lengthy and sometimes
+difficult process.
+
+<p>Due to the lack of properly-integrated OS/2 tools, configuring and managing
+CUPS is also awkward.  Simply creating a new printer, for example, is tedious and
+often confusing.
+
+
+<a name="1_7"></a>
+<h3>1.7.  Are there any known problems with eCups?</h3>
+
+<ul>
+<li>Importing certain (mostly Foomatic) PPD files into ECUPS.DRV can cause the
+OS/2 spooler to crash when printing.  Until a fix is found, you should be able
+to use the Generic PostScript Printer driver.<p>
+
+<li>Printing to printers which use Foomatic may result in the job aborting about
+99% of the way through (resulting in the last few words/characters being cut
+off).
+
+<p>This problem is currently under investigation.  In the meantime, it does not
+seem to occur when printing files which are already in either PS or PDF format;
+therefore, one workaround is to print to a PostScript file first (by selecting
+"output to file" on the output port page of the OS/2 printer object's
+properties), and then print the file manually using <em>cupslpr</em> or
+<a href="http://pages.cs.wisc.edu/~ghost/gsview/">gsview</a>.
+
+<p>(Similarly, in programs like OpenOffice, which have the option of exporting
+directly to PDF, you can generate a PDF file which can be printed from
+<em>cupslpr</em> or Lucide.)
+</ul>
+
+
+<a name="2_0"></a>
+<h2>2.  Configuration &amp; Use</h2>
+
+
+<a name="2_1"></a>
+<h3>2.1.  How do I set up eCups on my system?</h3>
+
+<p>Check out the <a href="http://svn.netlabs.org/ecups/wiki/HowTo">eCups HOWTO</a>,
+which provides detailed instructions, including screenshots.
+
+
+<a name="2_2"></a>
+<h3>2.2.  What printers are supported?</h3>
+
+<p>When you go to add a new printer in the CUPS web interface, you will see a list
+of supported printer models, arranged by manufacturer.  CUPS gets this list from
+all the driver packages which you have installed (like Gutenprint), plus the small
+number of generic drivers which CUPS includes natively.
+
+<p>Of course, some printers may be supported by driver packages which you don't
+currently have installed, in which case you won't see it in CUPS (until you install
+the required software).  A good way to check for support for a particular printer
+model is to check the <a href="http://www.openprinting.org/printers?action=search">OpenPrinting
+Database</a>.  Keep in mind, though, that not all of the CUPS driver packages out
+there have been ported to OS/2 (and not all of them are open source in any case.)
+</p>
+
+
+<a name="2_3"></a>
+<h3>2.3.  How do I install support for a printer which isn't listed?</h3>
+
+<p>First, you need to find out if a CUPS driver for your printer (or a compatible
+model) actually exists.  The best place to find out is by looking through the
+printer list on the <a href="http://www.openprinting.org/printers?action=search">OpenPrinting</a>
+web site.
+
+<p>If you've determined that your printer is supported, you will need make sure
+that the driver package required is installed.  Currently, the following driver
+packages are available for eCups:
+<ul>
+<li>Gutenprint
+<li>Splix
+<li>HPLIP
+<li>Foomatic/Ghostscript built-in <em>(only partially working at the moment)</em>
+</ul>
+<p>Go to the <a href="http://svn.netlabs.org/ecups/wiki/CupsPort">CupsPort</a>
+page to download them.
+
+<p>You may also need to download the appropriate CUPS PPD file, if the support
+hasn't been included in the driver package already.  The OpenPrinting site (see
+link above) is your place to go for these.
+
+<p>Finally, you have to install the support for your printer in CUPS and OS/2.  In
+general terms, you need to do the following:
+<ol>
+  <li>Install the driver package; consult its documentation for details.
+  <li>Create a new printer in CUPS.  Either select your printer if it's listed,
+      or import the PPD file if not.
+  <li>If the printer isn't listed in the eCups printer driver, you will also need
+      to import the PPD into ECUPS.DRV using the PIN utility.
+  <li>Create an OS/2 printer object using the newly-added printer driver.
+  <li>Create a new CUPS port which points to the new printer in CUPS, and select
+      it as the output port in the OS/2 printer object.
+</ol>
+<p>The <a href="http://svn.netlabs.org/ecups/wiki/HowTo">eCups HOWTO</a> describes
+these steps in more detail.
+
+
+<a name="2_4"></a>
+<h3>2.4.  Where can I find PPD files?</h3>
+
+<p>Browse the printer list on the <a href="http://www.openprinting.org/printers?action=search">OpenPrinting</a>
+web site.
+
+
+<a name="2_5"></a>
+<h3>2.5.  I can't import my PPD into ECUPS.DRV, what should I do?</h3>
+
+<p>One may occasionally encounter a PPD file which can be imported into CUPS
+without problems, but which the OS/2 printer driver (ECUPS.DRV) chokes on.
+
+<p>If this happens to you, you can simply use the "Generic PostScript Printer"
+driver for the OS/2 printer object.  Since CUPS is designed to operate on
+generic PostScript files, this should work just fine, as long as CUPS itself is
+properly configured to support your printer.
+
+<p>The main disadvantage of doing it this way is that you will be unable to set
+any printer-specific options in the OS/2 printer object or from the standard
+OS/2 job properties dialog.  If you need to change the printer options, you will
+have to do so from the CUPS administration GUI.
+
+
+<a name="2_6"></a>
+<h3>2.6.  What's the difference between all these network device types (<em>ipp://</em>, <em>lpd://</em>, <em>socket://</em>, etc.)?</h3>
+
+<p>CUPS supports several different types of network connection to a printer.
+Basically, you should choose whichever one your printer (or the print server
+it's connected to) supports best.
+
+<dl>
+<dt><tt>ipp://</tt>
+<dd>IPP or Internet Printing Protocol.  This is a modern TCP/IP protocol for
+networking printers which was designed to replace the much older LPD.  It
+supports many features which the LPD and AppSocket do not, including encryption,
+authentication, and job control.  Not all print servers may support it, however.<p>
+<dt><tt>lpd://</tt>
+<dd>This is the venerable TCP/IP Line Printing Daemon protocol.  Virtually all
+TCP/IP network printers and print servers should support it.<p>
+<dt><tt>socket://</tt>
+<dd>AppSocket (or "JetDirect") protocol over TCP/IP.  Originally developed by HP
+but supported by many network printers as well as hardware print servers.<p>
+<dt><tt>smb://</tt>
+<dd>SMB protocol, as used by Windows Networking, OS/2 Peer and LAN Server, and
+Samba.
+</dl>
+
+<p>If your printer is being shared by a Windows, OS/2 Peer, LAN Server, or Samba
+file/print server, then you will probably need to use SMB.  Otherwise, choose
+whichever of the TCP/IP-based protocols your printer (or its print server)
+supports best.
+
+<p>Of course, it's quite likely that more than one of them is supported.  In
+this case, you may want to consult the documentation that came with your
+printer/server (or ask your network administrator) to see if any of them is
+recommended specifically.
+
+<p>In general, IPP supports the most features, AppSocket/JetDirect has the best
+performance, and LPD is the most widely available.
+
+
+<a name="2_7"></a>
+<h3>2.7.  What are the "Simplified" printer drivers for?</h3>
+
+<p>Gutenprint provides many of its printer drivers (through its included PPD
+files) in both normal and "Simplified" versions.
+
+<p>The Gutenprint user's manual explains the difference:
+<blockquote>The "simplified" PPD files offer a basic set of options only, for
+selecting printer options, standard paper sizes, and basic quality settings.
+The PPD files that are not "simplified" offer a much broader set of controls,
+giving the user extensive control over quality and color adjustment.<br>
+&#x2014; Gutenprint 5.<i>x</i> user's manual
+</blockquote>
+
+<p>The Simplified drivers should be adequate for most peoples' needs.
+
+
+<a name="2_8"></a>
+<h3>2.8.  Why do I need to create <em>both</em> a CUPS printer <em>and</em> an OS/2 printer object?</h3>
+
+<p>OS/2 Presentation Manager programs only know how to print to an
+OS/2 printer object (or rather, to an OS/2 print queue, which is what the printer
+object defines).  They know nothing about CUPS printers.
+
+<p>(Obviously, you can print directly to the CUPS printer using CUPS-specific tools
+like <em>cupslpr</em> or the CUPS web interface.  But that doesn't help us with
+the general case.)
+
+<p>Creating an OS/2 printer object gives applications somewhere to send their
+print jobs.  What we do in this case is configure that printer object to redirect
+all its jobs to CUPS.  This is done by setting the printer output port to a CUPS<i>x</i>
+port, which you must configure with the name of the corresponding printer defined
+in CUPS.
+
+<p>To put it more simply: OS/2 printer objects know how to receive print jobs from
+applications.  CUPS knows how to send that data to the actual printer.  So they
+have to work together in tandem in order for printing to work.
+
+<p>In an ideal world, a corresponding OS/2 printer object would be created for you
+automatically whenever you created a new printer in CUPS.  Unfortunately, there is
+no way to do this just at the moment, so you have to create them both separately
+yourself.
+
+
+<a name="2_9"></a>
+<h3>2.9.  Where should I define the printer settings: in the OS/2 printer properties, or in CUPS?</h3>
+
+<p>In principle, you can set your preferred printer settings in either the OS/2
+printer object or in CUPS itself.
+
+<p>When you configure options in the OS/2 printer object, the resulting
+PostScript file which gets sent on to CUPS will have those settings defined.
+In this case, CUPS should respect them.
+
+<p>The settings in CUPS itself (which you can configure through the web
+administration GUI) can be thought of as fall-back defaults.  Any options which
+you set in the OS/2 printer object (or in the job properties dialog which most
+applications will offer you before printing) should take priority.  Options
+which were not set in the printer object (and which are thus not defined in
+the PostScript file which CUPS receives) will fall back to the CUPS-configured
+defaults.
+
+<p>Just to avoid confusion, it's a good idea to keep both the printer object
+defaults and the internal CUPS defaults synchronized with each other.
+
+
+<a name="3_0"></a>
+<h2>3.  Troubleshooting</h2>
+
+<p>TODO
+}}}