Attachment 1379 Details for Bug 811 – [FIXED_X11R68x] Patch to fix the "make install.man" bustage

[patch] [FIXED_X11R68x] Patch to fix the "make install.man" bustage

patch.gudiff (text/plain), 143.20 KB, created by Roland Mainz on 2004-11-26 00:55:33 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Roland Mainz

Created: 2004-11-26 00:55:33 UTC

Size: 143.20 KB

patch

obsolete

>Index: xc/ChangeLog
>===================================================================
>RCS file: /cvs/xorg/xc/ChangeLog,v
>retrieving revision 1.547
>diff -u -2 -0 -r1.547 ChangeLog
>--- xc/ChangeLog	25 Nov 2004 22:42:51 -0000	1.547
>+++ xc/ChangeLog	26 Nov 2004 08:48:00 -0000
>@@ -1,21 +1,35 @@
> 2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/doc/man/general/Imakefile        
>+        * xc/doc/man/general/Xprint.html      
>+        * xc/doc/man/general/Xprint.man       
>+        * xc/doc/man/general/Xprint.sgml      
>+        * xc/programs/Xserver/Xprint/Imakefile  
>+        * xc/programs/Xserver/Xprint/Xprint.html
>+        * xc/programs/Xserver/Xprint/Xprint.man 
>+        * xc/programs/Xserver/Xprint/Xprint.sgml
>+        Bugzilla #811 (https://freedesktop.org/bugzilla/show_bug.cgi?id=811):
>+        Fixing "make install.man" build bustage caused by previous checkin
>+        via moving the Xprint(7) manual page it's correct location
>+        (=xc/doc/man/general/)
>+
>+2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>         * xc/programs/Xserver/Xprint/Imakefile
>         * xc/programs/Xserver/Xprint/Xprt.html
>         * xc/programs/Xserver/Xprint/Xprt.man
>         * xc/programs/Xserver/Xprint/Xprt.sgml
>         Bugzilla #811 (https://freedesktop.org/bugzilla/show_bug.cgi?id=811):
>         Add missing manual page for "Xprt" (DocBook master file (Xprt.sgml)
>         and the generated files (Xprt.html, Xprt.man).
> 
> 2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>         * xc/config/cf/xprint_host.def
>         * xc/config/cf/xprint_site.def
>         Bugzilla #1921 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1921):
>         Rename "xc/config/cf/xprint_site.def" to "xc/config/cf/xprint_host.def"
>         to clarify it's purpose.
> 
> 2004-11-25  Matthieu Herrb  <matthieu.herrb@laas.fr>
> 
> 	* extras/Xpm/lib/Attrib.c:
> 	* extras/Xpm/lib/CrBufFrI.c:
> 	* extras/Xpm/lib/CrDatFrI.c:
>Index: xc/doc/man/general/Imakefile
>===================================================================
>RCS file: /cvs/xorg/xc/doc/man/general/Imakefile,v
>retrieving revision 1.2
>diff -u -2 -0 -r1.2 Imakefile
>--- xc/doc/man/general/Imakefile	23 Apr 2004 18:42:14 -0000	1.2
>+++ xc/doc/man/general/Imakefile	26 Nov 2004 08:48:08 -0000
>@@ -1,15 +1,23 @@
> XCOMM $Xorg: Imakefile,v 1.4 2000/08/17 19:42:04 cpqbld Exp $
> 
> 
> 
> XCOMM $XFree86: xc/doc/man/general/Imakefile,v 1.7 2001/01/17 16:57:40 dawes Exp $
> 
> MANDIR = $(MISCMANDIR)
> MANSUFFIX = $(MISCMANSUFFIX)
> 
> InstallManPage(X,$(MANDIR))
>+InstallManPage(Xprint,$(MANDIR))
> InstallManPageLong(Consortium,$(MANDIR),XConsortium)
> InstallManPageLong(Standards,$(MANDIR),XStandards)
> InstallManPageLong(XProjectTeam,$(MANDIR),XProjectTeam)
> InstallManPageAliases(XProjectTeam,$(MANDIR),X.Org)
> InstallManPageLong(security,$(MANDIR),Xsecurity)
>+
>+#ifdef HasDocBookTools
>+all:: Xprint.man Xprint.html
>+
>+ConvertDocBookToManPage(Xprint.sgml, Xprint.man)
>+ConvertDocBookToHTML(Xprint.sgml, Xprint.html)
>+#endif /* HasDocBookTools */
>Index: xc/doc/man/general/Xprint.html
>===================================================================
>RCS file: xc/doc/man/general/Xprint.html
>diff -N xc/doc/man/general/Xprint.html
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ xc/doc/man/general/Xprint.html	26 Nov 2004 08:48:08 -0000
>@@ -0,0 +1,296 @@
>+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Xprint</title><meta name="generator" content="DocBook XSL Stylesheets V1.62.4"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="Xprint"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>Xprint &#8212; The &quot;X print service&quot; - a portable, network-transparent printing system based on the X11 protocol</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p>Xprint is a very flexible, extensible, scaleable, client/server
>+     print system based on ISO 10175 (and some other specs) and the X11        
>+     rendering protocol.                                                       
>+     Using Xprint an application can search, query and use devices like        
>+     printers, FAX machines or create documents in formats like PDF.           
>+     In particular, an application can seek a printer, query supported         
>+     attributes (like paper size, trays, fonts etc.), configure the printer    
>+     device to match it&#8217;s needs and print on it like on any other X device     
>+     reusing parts of the code which is used for the video card Xserver.    
>+    </p></div><div xmlns:ns1="" class="refsect1" lang="en"><a name="id2802144"></a><h2>OVERVIEW</h2><p>
>+      The &quot;X Print Service&quot; technology allows X rendering to devices such as
>+      printers and fax.  Most of the service is available in the X11
>+      technology stack as Xp, with the remainder in single toolkit stacks (e.g. DtPrint for CDE).
>+      Modifications have also been made to the LessTif/Motif/Qt technology
>+      stacks to support Xprint.
>+    </p><p>
>+      The Xp portion consists of:
>+      </p><div class="itemizedlist"><ul type="disc"><li><p>Xp Extension for the X-Server (included in the X-Server Xprt)</p></li><li><p>Xp Extension API for the client side (libXp/libXprintUtils)</p></li><li><p>PCL ddx driver that converts core X to native PCL</p></li><li><p>PDF ddx driver that converts core X to native PDF</p></li><li><p>PostScript ddx driver that converts core X to native PostScript</p></li><li><p>Raster ddx driver that generates xwd rasters which can be converted to PCL, PDF or PostScript rasters</p></li></ul></div><p>
>+      From an X clients perspective, it can attach to one of two nearly
>+      identical X-Servers, a &quot;Video&quot; X-Server, and a &quot;Print&quot; X-Server
>+      which has the additional Xp capability but otherwise looks and
>+      behaves the same.   
>+    </p></div><div xmlns:ns2="" class="refsect1" lang="en"><a name="id2804972"></a><h2>HOW THE X PRINT SERVICE WORKS</h2><p>    
>+      The X Print Service expands on the traditional X-Server and Xlib world
>+      in four ways.
>+
>+      </p><div class="orderedlist"><ol type="1"><li><p>
>+            Most obvious is the use of &quot;print ddx drivers&quot; instead of
>+            &quot;video ddx drivers&quot;.  While a video ddx driver modifies pixels
>+            in a video frame buffer, a print ddx driver generates &quot;page
>+            description language (PDL)&quot; output (such as PCL, PDF or PostScript)
>+            or sends the print rendering instructions to a platform-specific
>+            print API (like Win32/GDI).
>+          </p><p>
>+            Once a print ddx driver generates PDL output, it can be sent to
>+            a spooler such as <span class="citerefentry"><span class="refentrytitle">lp</span>(1)</span>
>+            or retrieved by the client (to implement functionality like &quot;print-to-file&quot;).
>+          </p><p>
>+            Though not currently done, a single X-Server can support both
>+            print and video ddx drivers.
>+            </p></li><li><p>
>+            Since printers support &quot;paged&quot; output, unlike video, a portion
>+            of the Xp Extension supports APIs to delineate printed output.
>+            For example, <tt class="function">XpStartPage</tt> and <tt class="function">XpEndPage</tt> tell the X-Server where
>+            a physical page starts and ends in an otherwise continuous
>+            stream of X rendering primitives.  Likewise, <tt class="function">XpStartJob</tt> and
>+            <tt class="function">XpEndJob</tt> determine when a collection of pages starts and ends.
>+            <tt class="function">XpEndJob</tt> typically causes the generated PDL to be submitted to
>+            a spooler, such as <span class="citerefentry"><span class="refentrytitle">lp</span>(1)</span>.
>+          </p></li><li><p>
>+            Since printers have extensive capabilities, another portion of
>+            the Xp Extension supports APIs to manipulate &quot;print contexts&quot;.
>+          </p><p>
>+            Once a printer is selected using the Xp Extension API, a print
>+            context to represent it can be created.  A print context
>+            embodies the printer selected - it contains the printer's
>+            default capabilities, selectable range of capabilities,
>+            printer state, and generated output.  Some &quot;attributes&quot; within
>+            the print context can be modified by the user, and the
>+            X-Server and print ddx driver will react accordingly.  For
>+            example, the attribute &quot;content-orientation&quot; can be set to
>+            &quot;landscape&quot; or &quot;portrait&quot; (if the printer supports these 
>+            values - which can be queried using the Xprint API as well).
>+          </p></li><li><p>
>+            Since printers can have &quot;built in&quot; fonts, the Xp Extension in
>+            the X-Server works with the print ddx drivers to make
>+            available (for printing only) additional fonts on a per print
>+            context basis.
>+          </p><p>
>+            When a print context is created and set for a given printer,
>+            the X font calls may be able to access additional printer
>+            fonts.  To do this (typically), the X-Server must have access
>+            to &quot;printer metric files&quot; (.pmf) that describe at minimum the
>+            metrics of the built in fonts.
>+          </p></li></ol></div></div><div xmlns:ns3="" class="refsect1" lang="en"><a name="id2804885"></a><h2>USAGE</h2><p>    
>+      There are three tasks to start the X Print Service:
>+      </p><div class="orderedlist"><ol type="1"><li><p>configuring the X Print Server,</p></li><li><p>starting the X Print Service</p></li><li><p>configuring the user session so that clients can find the running X Print Service</p></li></ol></div><p>
>+      The tasks are described in detail below.
>+    </p></div><div xmlns:ns4="" class="refsect1" lang="en"><a name="id2804911"></a><h2>SERVER CONFIGURATION</h2><p>
>+      The X Print Server (Xprt) can read a number of configuration files which
>+      control its behavior and support for printers.  Each vendor platform has
>+      a default location for this information.  Xprt can also read the
>+      environment variable <tt class="envar">XPCONFIGDIR</tt> to locate alternate configuration
>+      directories.  Common settings include:
>+
>+      </p><table class="simplelist" border="0" summary="Simple list"><tr><td>export XPCONFIGDIR=/X11/lib/X11/XpConfig/</td></tr><tr><td>export XPCONFIGDIR=/proj/x11/xc/programs/Xserver/XpConfig/</td></tr></table><p>
>+      Xprt has many built-in defaults, and lacking any configuration files,
>+      will immediately try to support all printers visible via <span class="citerefentry"><span class="refentrytitle">lpstat</span>(1)</span>.
>+    </p><p>
>+      In order of importance for configuration by a system administrator, the
>+      configuration files for a &quot;C&quot; locale are as follows (see <span class="citerefentry"><span class="refentrytitle">Xprt</span>(7)</span> for more
>+      details (including support for non-&quot;C&quot; locales)):
>+      </p><div class="variablelist"><dl><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/Xprinters</tt></span></dt><dd><p>
>+              'Xprinters' is the top most configuration file.  It tells
>+              Xprt which specific printer names (e.g.  mylaser) should
>+              be supported, and whether <span class="citerefentry"><span class="refentrytitle">lpstat</span>(1)</span> or other commands
>+              should be used to automatically supplement the list of
>+              printers.
>+            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/attributes/printer</tt></span></dt><dd><p>
>+              The 'printer' file maps printer names to model
>+              configurations (see 'model-config' below).  For example,
>+              &quot;mylaser&quot; could be mapped to a &quot;HPDJ1600C&quot;, and all other
>+              arbitrary printers could be mapped to a default, such as
>+              &quot;HPLJ4SI&quot;.  When depending on <span class="citerefentry"><span class="refentrytitle">lpstat</span>(1)</span> in the Xprinters
>+              file, setting up defaults in 'printer' becomes all the
>+              more important.
>+            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/attributes/document</tt></span></dt><dd><p>
>+              The 'document' file specifies the initial document values
>+              for any print jobs.  For example, which paper tray to
>+              use, what default resolution, etc.
>+            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/attributes/job</tt></span></dt><dd><p>
>+              The 'job' file specifies the initial job values for any
>+              print jobs.  For example, &quot;notification-profile&quot; can be
>+              set so that when a print job is successfully sent to a
>+              printer, e-mail is sent to the user.
>+            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/model-config</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/fonts/fonts.dir</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00051.pmf</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00093.pmf</tt></span></dt><dd><p>
>+              The 'model-config' file has attributes that describe the
>+              printer model&#8217;s capabilities and default settings.
>+              Printer model fonts may also be present.  The model-config
>+              file also identifies the print ddx driver to be used.
>+
>+              For each printer model supported, a complete hierarchy of
>+              files should exist.  In most cases, these files do not
>+              need to be modified.
>+            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/ddx-config/raster/pcl</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/ddx-config/raster/pdf</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/ddx-config/raster/postscript</tt></span></dt><dd><p>
>+              The print ddx drivers can have highly specific
>+              configuration files to control their behavior.  In most
>+              cases, these files do not need to be modified.
>+            </p></dd></dl></div><p>
>+      
>+      More information in how to configure and customize the X print server can be found in the
>+      <span class="citerefentry"><span class="refentrytitle">Xprt</span>(7)</span>
>+      manual page.
>+    </p></div><div xmlns:ns5="" class="refsect1" lang="en"><a name="id2805166"></a><h2>STARTING UP</h2><p>
>+      The summary checklist for starting the X Print Service is as follows:
>+      
>+      </p><div class="orderedlist"><ol type="1"><li><p>
>+            Choose an execution model for the X Print Service.  The X
>+            Print Service can be run on a per-user session basis, per
>+            machine basis, or can be run on a few machines globally
>+            available to a number of users.
>+          </p></li><li><p>
>+            If print jobs are to be submitted to a spooler (almost always
>+            the case), make sure all needed printers are available to the
>+            spooler subsystem (most often <span class="citerefentry"><span class="refentrytitle">lp</span>(1)</span>)
>+            on the same machine running the X Print Service.
>+          </p></li><li><p>
>+            Configure the X Print Server.  See ``X Print Server
>+            Configuration''.
>+          </p></li><li><p>
>+            Depending on #1, start the X Print Server process &quot;Xprt&quot;, and
>+            then the toolkit-specific Print Dialog Manager Daemon process
>+            (such as CDEnext's &quot;dtpdmd&quot;) at the appropriate times.
>+            Note that libXprintUtils-based applications/toolkits do not need
>+            a Print Dialog Manager Daemon process to use Xprint.
>+          </p></li></ol></div><p>     
>+      The details are described below.
>+    </p><p>
>+      Because the X Print Service is based on X, it can be easily distributed.
>+      The most significant factors in which execution model to choose will be
>+      driven by:
>+      </p><div class="itemizedlist"><ul type="disc"><li><p>
>+            how many printers will be accessable through the printer
>+            subsystem on any given machine.  A system administrator may
>+            choose to cluster printers on a few given machines, or
>+            scatter them across an organization and possibly make
>+            extensive use of remote spoolers to make them globally
>+            available.
>+          </p></li><li><p>
>+            how many machines will need a copy of the X Print Server
>+            configuration files.  The files have been architected so
>+            that one super-set version of them can be maintained and
>+            distributed (e.g.  via NFS), and a per-machine or per-user
>+            version of the `Xprinters' is all that is needed to have the
>+            appropriate information in them utilized or ignored.
>+          </p></li><li><p>
>+            how many users can demand services from a given X Print
>+            Service.
>+          </p></li></ul></div><p>
>+
>+      With the above in mind, some obvious execution models include:
>+      </p><div class="itemizedlist"><ul type="disc"><li><p>
>+            Global - in this model, the system administrator is choosing
>+            to run the X Print Service on a *few* select machines with
>+            appropriate printers configured, and allow clients access to
>+            the global resource.  This can centralize the administration
>+            of printers and configuration files, but may have to be
>+            monitored for performance loading.
>+          </p><p>
>+            Startup would likely be done by boot-up scripts (such as <tt class="filename">/etc/init.d/xprint</tt>).
>+          </p></li><li><p>
>+            Per-machine - every machine with potential X Print Service
>+            users would run the service.  Printer and configuration file
>+            administration is decentralized, and usage would be limited
>+            to the users on the machine.
>+          </p><p>
>+            Startup would likely be done by boot-up scripts (such as <tt class="filename">/etc/init.d/xprint</tt>).
>+          </p></li><li><p>
>+            Per-user session - every user would run an entire X Print
>+            Service for themselves.  In the future, the Video X Server
>+            normally started may contain Print X Server capability, so
>+            this model becomes very natural.
>+          </p><p>
>+            Startup would likely be done at session login or by
>+            launching actions or processes manually once the user
>+            logs in.  Note: Deamons like &quot;dtpdmd&quot; must be started after Xprt.
>+          </p></li></ul></div><p>
>+       Starting of the processes is straight forward.  In strict order (example is for manually starting the X print server for CDEnext usage):
>+       </p><div class="orderedlist"><ol type="1"><li><pre class="programlisting">[machineA] % Xprt [-XpFile Xprinters file] [:dispNum] </pre><p>
>+             Note that Xprt will look for configuration files in either
>+             a default location or where <tt class="envar">XPCONFIGDIR</tt> points.
>+           </p><p><tt class="option">-XpFile</tt> specifies an alternate `Xprinters' file, rather
>+             than the default one or `<tt class="filename">${XPCONFIGDIR}/C/print/Xprinters</tt>'.
>+           </p></li><li><pre class="programlisting">[machineA] % dtpdmd -d machineA[:dispNum] [-l /tmp/dtpdmd.log] </pre><p>
>+            The dtpdmd will maintain an X-Selection on the X-Server,
>+            and will start dtpdm's as required to service requests.
>+           </p></li></ol></div><p>
>+       In all but the per-user session model, the machine running the dtpdmd
>+       (thus dtpdm's) will need display authorization to the users video
>+       display.
>+    </p></div><div xmlns:ns6="" class="refsect1" lang="en"><a name="id2805371"></a><h2>CLIENT CONFIGURATION</h2><p>
>+      Once a X Print Server and dtpdmd have been started -- many of them
>+      in some cases -- clients will need to find and use them.  There are
>+      two mechanisms that allow clients to discover X Print Servers and
>+      printers.
>+
>+      </p><div class="itemizedlist"><ul type="disc"><li><p>
>+            &quot;X Print Specifier&quot; - assuming usage of the DtPrint/XprintUtils-based print
>+            applications, the following notation is understood:
>+          </p><pre class="programlisting">printer_name@machine[:dispNum]</pre><p>
>+            For example:
>+          </p><pre class="programlisting">colorlj7@printhub:2</pre><p>
>+           In the above example, the X Print Server running at `printhub:2'
>+           is assumed to support the printer named `colorlj7'.
>+          </p></li><li><p><tt class="envar">${XPSERVERLIST}</tt> - assuming usage of the DtPrint print dialogs,
>+            the environment variable <tt class="envar">${XPSERVERLIST}</tt> can contain a list
>+            of X Print Servers.  For example:
>+          </p><pre class="programlisting">XPSERVERLIST=&quot;printhub:2 printhub:3 otherdept:0&quot;</pre><p>
>+            Then in the dialogs, only a printer name needs to be entered.
>+            The dialog will then search the X Print Servers in <tt class="envar">${XPSERVERLIST}</tt>
>+            for a server than supports the printer, and then establish
>+            contact.
>+          </p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2806227"></a><h2>END-USER SEQUENCE</h2><p>
>+      From most CDEnext applications, printing is accomplished by bringing
>+      down the File menu and selecting Print....  This will result in
>+      the DtPrintSetupBox dialog, which will request the name of a printer,
>+      and offer limited capability to configure print options (e.g. number
>+      of copies).  If the user wishes, they can select Setup..., which
>+      will start a dtpdm capable of modifying additional print options.
>+      Finally, the user should select Print.
>+    </p></div><div class="refsect1" lang="en"><a name="id2806249"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term"><tt class="envar">${XPCONFIGDIR}</tt></span></dt><dd><p> This environment variable points to the  root
>+	    of  the Xprint server configuration directory hierarchy.
>+	    If the variable is not defined,  the  default
>+	    path  is be assumed.  The default path may be
>+            <tt class="filename">/usr/X11R6/lib/X11/xserver/</tt>, 
>+            <tt class="filename">/usr/lib/X11/xserver/</tt>,
>+            <tt class="filename">/usr/share/Xprint/xserver/</tt> or
>+            <tt class="filename">/usr/openwin/server/etc/XpConfig</tt>, depending on the
>+	    system, and may be configured in <tt class="filename">/etc/init.d/xprint</tt>.</p></dd><dt><span class="term"><tt class="envar">${LANG}</tt></span></dt><dd><p>
>+            This environment variable selects the locale settings used by the Xprint server.
>+            Xprt allows language-specific settings (stored in <tt class="filename">${XPCONFIGDIR}/${LANG}/print/</tt>)
>+            which will override the default settings (stored in <tt class="filename">${XPCONFIGDIR}/C/print/</tt>).
>+            If <tt class="envar">${LANG}</tt> is not set &quot;C&quot; is assumed.
>+          </p></dd><dt><span class="term"><tt class="envar">${XPSERVERLIST}</tt></span></dt><dd xmlns:ns7=""><p>The environment variable <tt class="envar">${XPSERVERLIST}</tt> contains a list
>+	    of display identifiers (separated by whitespace) which tell an
>+	    application where it can find the Xprint servers.  Usually
>+	    <tt class="envar">${XPSERVERLIST}</tt> is set by the profile startup scripts (e.g.
>+	    <tt class="filename">/etc/profile</tt> or <tt class="filename">/etc/profile.d/xprint.sh</tt>) using the output of
>+	    <b class="userinput"><tt>/etc/init.d/xprint get_xpserverlist</tt></b>.</p><p>Example: 
>+	    </p><div class="informalexample"><pre class="programlisting">
>+		export XPSERVERLIST=&quot;`/etc/init.d/xprint get_xpserverlist`&quot;</pre></div><p>Alternatively <tt class="envar">${XPSERVERLIST}</tt> can be set
>+	    manually. Example:</p><div class="informalexample"><pre class="programlisting">
>+		export XPSERVERLIST=&quot;littlecat:80 bitdog:72&quot;</pre></div><p>
>+	    instructs an application to find an Xprint server at display
>+	    80 on the machine &quot;littlecat&quot; and at display 72 on the
>+	    machine bigdog.
>+	  </p></dd><dt><span class="term"><tt class="envar">${XPRINTER}</tt></span></dt><dd xmlns:ns8=""><p>The environment variable <tt class="envar">${XPRINTER}</tt>
>+	    defines the default printer used by print
>+	    applications. The syntax is either
>+	    <i class="replaceable"><tt>printername</tt></i> or
>+	    <i class="replaceable"><tt>printername</tt></i>@<i class="replaceable"><tt>display</tt></i>.</p><p>Examples:
>+	    </p><div class="variablelist"><dl><dt><span class="term"><b class="userinput"><tt>XPRINTER=ps003</tt></b></span></dt><dd><p>
>+		  tells an application to look for the
>+		  first printer named &quot;ps003&quot; on all Xprint
>+		  servers.</p></dd><dt><span class="term"><b class="userinput"><tt>XPRINTER=hplaser19@littlecat:80</tt></b></span></dt><dd><p>
>+		  tells an application to use the printer &quot;hplaser19&quot;
>+		on the Xprint server at display 
>+		  &quot;littlecat:80&quot;.</p></dd></dl></div><p>If <tt class="envar">${XPRINTER}</tt> is not set the applications
>+	    will examine the values of the <tt class="envar">${PDPRINTER}</tt>,
>+	    <tt class="envar">${LPDEST}</tt>, and 
>+	    <tt class="envar">${PRINTER}</tt> environment variables (in that order).  
>+	  </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2806468"></a><h2>SEE ALSO</h2><p><span class="simplelist"><span class="citerefentry"><span class="refentrytitle">X11</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xplsprinters</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xprehashprinterlist</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xphelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xpxmhelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xpawhelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xpxthelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xpsimplehelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">Xserver</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">Xprt</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">libXp</span>(3x)</span>, <span class="citerefentry"><span class="refentrytitle">libXprintUtils</span>(3x)</span>, <span class="citerefentry"><span class="refentrytitle">libXprintAppUtils</span>(3x)</span>, <span class="citerefentry"><span class="refentrytitle">XmPrintShell</span>(3x)</span>, <span class="citerefentry"><span class="refentrytitle">XawPrintShell</span>(3x)</span>, Xprint FAQ (<a href="http://xprint.mozdev.org/docs/Xprint_FAQ.html" target="_top">http://xprint.mozdev.org/docs/Xprint_FAQ.html</a>), Xprint main site (<a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a>)</span></p></div><div class="refsect1" lang="en"><a name="id2806639"></a><h2>AUTHORS</h2><p>
>+      This manual page was written by 
>+      Roland Mainz <tt class="email">&lt;<a href="mailto:roland.mainz@nrubsig.org">roland.mainz@nrubsig.org</a>&gt;</tt> based on the original X11R6.6
>+      <tt class="filename">xc/programs/Xserver/XpConfig/README</tt>.
>+    </p></div></div></body></html>
>Index: xc/doc/man/general/Xprint.man
>===================================================================
>RCS file: xc/doc/man/general/Xprint.man
>diff -N xc/doc/man/general/Xprint.man
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ xc/doc/man/general/Xprint.man	26 Nov 2004 08:48:09 -0000
>@@ -0,0 +1,421 @@
>+.\" -*- coding: us-ascii -*-
>+.TH Xprint __miscmansuffix__ "8 October 2004"  
>+.SH NAME
>+Xprint \- The "X print service" - a portable, network-transparent printing system based on the X11 protocol
>+.SH SYNOPSIS
>+Xprint is a very flexible, extensible, scaleable, client/server
>+print system based on ISO 10175 (and some other specs) and the X11 
>+rendering protocol. 
>+Using Xprint an application can search, query and use devices like 
>+printers, FAX machines or create documents in formats like PDF. 
>+In particular, an application can seek a printer, query supported 
>+attributes (like paper size, trays, fonts etc.), configure the printer 
>+device to match it\(cqs needs and print on it like on any other X device 
>+reusing parts of the code which is used for the video card Xserver. 
>+.SH OVERVIEW
>+The "X Print Service" technology allows X rendering to devices such as
>+printers and fax. Most of the service is available in the X11
>+technology stack as Xp, with the remainder in single toolkit stacks (e.g. DtPrint for CDE).
>+Modifications have also been made to the LessTif/Motif/Qt technology
>+stacks to support Xprint.
>+.PP
>+The Xp portion consists of:
>+.TP 0.2i
>+\(bu
>+Xp Extension for the X-Server (included in the X-Server Xprt)
>+.TP 0.2i
>+\(bu
>+Xp Extension API for the client side (libXp/libXprintUtils)
>+.TP 0.2i
>+\(bu
>+PCL ddx driver that converts core X to native PCL
>+.TP 0.2i
>+\(bu
>+PDF ddx driver that converts core X to native PDF
>+.TP 0.2i
>+\(bu
>+PostScript ddx driver that converts core X to native PostScript
>+.TP 0.2i
>+\(bu
>+Raster ddx driver that generates xwd rasters which can be converted to PCL, PDF or PostScript rasters
>+.PP
>+.PP
>+From an X clients perspective, it can attach to one of two nearly
>+identical X-Servers, a "Video" X-Server, and a "Print" X-Server
>+which has the additional Xp capability but otherwise looks and
>+behaves the same. 
>+.SH "HOW THE X PRINT SERVICE WORKS"
>+The X Print Service expands on the traditional X-Server and Xlib world
>+in four ways.
>+.TP 0.4i
>+1.
>+Most obvious is the use of "print ddx drivers" instead of
>+"video ddx drivers". While a video ddx driver modifies pixels
>+in a video frame buffer, a print ddx driver generates "page
>+description language (PDL)" output (such as PCL, PDF or PostScript)
>+or sends the print rendering instructions to a platform-specific
>+print API (like Win32/GDI).
>+
>+Once a print ddx driver generates PDL output, it can be sent to
>+a spooler such as \fBlp\fR(1)
>+or retrieved by the client (to implement functionality like "print-to-file").
>+
>+Though not currently done, a single X-Server can support both
>+print and video ddx drivers.
>+.TP 0.4i
>+2.
>+Since printers support "paged" output, unlike video, a portion
>+of the Xp Extension supports APIs to delineate printed output.
>+For example, XpStartPage and XpEndPage tell the X-Server where
>+a physical page starts and ends in an otherwise continuous
>+stream of X rendering primitives. Likewise, XpStartJob and
>+XpEndJob determine when a collection of pages starts and ends.
>+XpEndJob typically causes the generated PDL to be submitted to
>+a spooler, such as \fBlp\fR(1).
>+.TP 0.4i
>+3.
>+Since printers have extensive capabilities, another portion of
>+the Xp Extension supports APIs to manipulate "print contexts".
>+
>+Once a printer is selected using the Xp Extension API, a print
>+context to represent it can be created. A print context
>+embodies the printer selected - it contains the printer's
>+default capabilities, selectable range of capabilities,
>+printer state, and generated output. Some "attributes" within
>+the print context can be modified by the user, and the
>+X-Server and print ddx driver will react accordingly. For
>+example, the attribute "content-orientation" can be set to
>+"landscape" or "portrait" (if the printer supports these 
>+values - which can be queried using the Xprint API as well).
>+.TP 0.4i
>+4.
>+Since printers can have "built in" fonts, the Xp Extension in
>+the X-Server works with the print ddx drivers to make
>+available (for printing only) additional fonts on a per print
>+context basis.
>+
>+When a print context is created and set for a given printer,
>+the X font calls may be able to access additional printer
>+fonts. To do this (typically), the X-Server must have access
>+to "printer metric files" (.pmf) that describe at minimum the
>+metrics of the built in fonts.
>+.PP
>+.SH USAGE
>+There are three tasks to start the X Print Service:
>+.TP 0.4i
>+1.
>+configuring the X Print Server,
>+.TP 0.4i
>+2.
>+starting the X Print Service
>+.TP 0.4i
>+3.
>+configuring the user session so that clients can find the running X Print Service
>+.PP
>+.PP
>+The tasks are described in detail below.
>+.SH "SERVER CONFIGURATION"
>+The X Print Server (Xprt) can read a number of configuration files which
>+control its behavior and support for printers. Each vendor platform has
>+a default location for this information. Xprt can also read the
>+environment variable \fBXPCONFIGDIR\fR to locate alternate configuration
>+directories. Common settings include:
>+
>+export XPCONFIGDIR=/X11/lib/X11/XpConfig/
>+.PP
>+export XPCONFIGDIR=/proj/x11/xc/programs/Xserver/XpConfig/
>+
>+.PP
>+Xprt has many built-in defaults, and lacking any configuration files,
>+will immediately try to support all printers visible via \fBlpstat\fR(1).
>+.PP
>+In order of importance for configuration by a system administrator, the
>+configuration files for a "C" locale are as follows (see \fBXprt\fR(__appmansuffix__) for more
>+details (including support for non-"C" locales)):
>+.TP 
>+\fB${XPCONFIGDIR}/C/print/Xprinters\fR
>+\&'Xprinters' is the top most configuration file. It tells
>+Xprt which specific printer names (e.g. mylaser) should
>+be supported, and whether \fBlpstat\fR(1) or other commands
>+should be used to automatically supplement the list of
>+printers.
>+.TP 
>+\fB${XPCONFIGDIR}/C/print/attributes/printer\fR
>+The 'printer' file maps printer names to model
>+configurations (see 'model-config' below). For example,
>+"mylaser" could be mapped to a "HPDJ1600C", and all other
>+arbitrary printers could be mapped to a default, such as
>+"HPLJ4SI". When depending on \fBlpstat\fR(1) in the Xprinters
>+file, setting up defaults in 'printer' becomes all the
>+more important.
>+.TP 
>+\fB${XPCONFIGDIR}/C/print/attributes/document\fR
>+The 'document' file specifies the initial document values
>+for any print jobs. For example, which paper tray to
>+use, what default resolution, etc.
>+.TP 
>+\fB${XPCONFIGDIR}/C/print/attributes/job\fR
>+The 'job' file specifies the initial job values for any
>+print jobs. For example, "notification-profile" can be
>+set so that when a print job is successfully sent to a
>+printer, e-mail is sent to the user.
>+.TP 
>+\fB${XPCONFIGDIR}/C/print/models/PSdefault/model\-config\fR, \fB${XPCONFIGDIR}/C/print/models/PSdefault/fonts/fonts.dir\fR, \fB${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00051.pmf\fR, \fB${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00093.pmf\fR
>+The 'model-config' file has attributes that describe the
>+printer model\(cqs capabilities and default settings.
>+Printer model fonts may also be present. The model-config
>+file also identifies the print ddx driver to be used.
>+For each printer model supported, a complete hierarchy of
>+files should exist. In most cases, these files do not
>+need to be modified.
>+.TP 
>+\fB${XPCONFIGDIR}/C/print/ddx\-config/raster/pcl\fR, \fB${XPCONFIGDIR}/C/print/ddx\-config/raster/pdf\fR, \fB${XPCONFIGDIR}/C/print/ddx\-config/raster/postscript\fR
>+The print ddx drivers can have highly specific
>+configuration files to control their behavior. In most
>+cases, these files do not need to be modified.
>+.PP
>+More information in how to configure and customize the X print server can be found in the
>+\fBXprt\fR(__appmansuffix__)
>+manual page.
>+.SH "STARTING UP"
>+The summary checklist for starting the X Print Service is as follows:
>+.TP 0.4i
>+1.
>+Choose an execution model for the X Print Service. The X
>+Print Service can be run on a per-user session basis, per
>+machine basis, or can be run on a few machines globally
>+available to a number of users.
>+.TP 0.4i
>+2.
>+If print jobs are to be submitted to a spooler (almost always
>+the case), make sure all needed printers are available to the
>+spooler subsystem (most often \fBlp\fR(1))
>+on the same machine running the X Print Service.
>+.TP 0.4i
>+3.
>+Configure the X Print Server. See ``X Print Server
>+Configuration''.
>+.TP 0.4i
>+4.
>+Depending on #1, start the X Print Server process "Xprt", and
>+then the toolkit-specific Print Dialog Manager Daemon process
>+(such as CDEnext's "dtpdmd") at the appropriate times.
>+Note that libXprintUtils-based applications/toolkits do not need
>+a Print Dialog Manager Daemon process to use Xprint.
>+.PP
>+The details are described below.
>+.PP
>+Because the X Print Service is based on X, it can be easily distributed.
>+The most significant factors in which execution model to choose will be
>+driven by:
>+.TP 0.2i
>+\(bu
>+how many printers will be accessable through the printer
>+subsystem on any given machine. A system administrator may
>+choose to cluster printers on a few given machines, or
>+scatter them across an organization and possibly make
>+extensive use of remote spoolers to make them globally
>+available.
>+.TP 0.2i
>+\(bu
>+how many machines will need a copy of the X Print Server
>+configuration files. The files have been architected so
>+that one super-set version of them can be maintained and
>+distributed (e.g. via NFS), and a per-machine or per-user
>+version of the `Xprinters' is all that is needed to have the
>+appropriate information in them utilized or ignored.
>+.TP 0.2i
>+\(bu
>+how many users can demand services from a given X Print
>+Service.
>+.PP
>+With the above in mind, some obvious execution models include:
>+.TP 0.2i
>+\(bu
>+Global - in this model, the system administrator is choosing
>+to run the X Print Service on a *few* select machines with
>+appropriate printers configured, and allow clients access to
>+the global resource. This can centralize the administration
>+of printers and configuration files, but may have to be
>+monitored for performance loading.
>+
>+Startup would likely be done by boot-up scripts (such as \fB/etc/init.d/xprint\fR).
>+.TP 0.2i
>+\(bu
>+Per-machine - every machine with potential X Print Service
>+users would run the service. Printer and configuration file
>+administration is decentralized, and usage would be limited
>+to the users on the machine.
>+
>+Startup would likely be done by boot-up scripts (such as \fB/etc/init.d/xprint\fR).
>+.TP 0.2i
>+\(bu
>+Per-user session - every user would run an entire X Print
>+Service for themselves. In the future, the Video X Server
>+normally started may contain Print X Server capability, so
>+this model becomes very natural.
>+
>+Startup would likely be done at session login or by
>+launching actions or processes manually once the user
>+logs in. Note: Deamons like "dtpdmd" must be started after Xprt.
>+.PP
>+.PP
>+Starting of the processes is straight forward. In strict order (example is for manually starting the X print server for CDEnext usage):
>+.TP 0.4i
>+1.
>+
>+.nf
>+[machineA] % Xprt [\-XpFile <Xprinters file>] [:dispNum] &
>+.fi
>+
>+
>+Note that Xprt will look for configuration files in either
>+a default location or where \fBXPCONFIGDIR\fR points.
>+
>+\fB\-XpFile\fR specifies an alternate `Xprinters' file, rather
>+than the default one or `\fB${XPCONFIGDIR}/C/print/Xprinters\fR'.
>+.TP 0.4i
>+2.
>+
>+.nf
>+[machineA] % dtpdmd \-d machineA[:dispNum] [\-l /tmp/dtpdmd.log] &
>+.fi
>+
>+
>+The dtpdmd will maintain an X-Selection on the X-Server,
>+and will start dtpdm's as required to service requests.
>+.PP
>+.PP
>+In all but the per-user session model, the machine running the dtpdmd
>+(thus dtpdm's) will need display authorization to the users video
>+display.
>+.SH "CLIENT CONFIGURATION"
>+Once a X Print Server and dtpdmd have been started -- many of them
>+in some cases -- clients will need to find and use them. There are
>+two mechanisms that allow clients to discover X Print Servers and
>+printers.
>+.TP 0.2i
>+\(bu
>+"X Print Specifier" - assuming usage of the DtPrint/XprintUtils-based print
>+applications, the following notation is understood:
>+
>+
>+.nf
>+printer_name@machine[:dispNum]
>+.fi
>+
>+
>+For example:
>+
>+
>+.nf
>+colorlj7@printhub:2
>+.fi
>+
>+
>+In the above example, the X Print Server running at `printhub:2'
>+is assumed to support the printer named `colorlj7'.
>+.TP 0.2i
>+\(bu
>+\fB${XPSERVERLIST}\fR - assuming usage of the DtPrint print dialogs,
>+the environment variable \fB${XPSERVERLIST}\fR can contain a list
>+of X Print Servers. For example:
>+
>+
>+.nf
>+XPSERVERLIST="printhub:2 printhub:3 otherdept:0"
>+.fi
>+
>+
>+Then in the dialogs, only a printer name needs to be entered.
>+The dialog will then search the X Print Servers in \fB${XPSERVERLIST}\fR
>+for a server than supports the printer, and then establish
>+contact.
>+.PP
>+.SH "END-USER SEQUENCE"
>+From most CDEnext applications, printing is accomplished by bringing
>+down the <File> menu and selecting <Print...>. This will result in
>+the DtPrintSetupBox dialog, which will request the name of a printer,
>+and offer limited capability to configure print options (e.g. number
>+of copies). If the user wishes, they can select <Setup...>, which
>+will start a dtpdm capable of modifying additional print options.
>+Finally, the user should select <Print>.
>+.SH ENVIRONMENT
>+.TP 
>+\fB${XPCONFIGDIR}\fR
>+This environment variable points to the root
>+of the Xprint server configuration directory hierarchy.
>+If the variable is not defined, the default
>+path is be assumed. The default path may be
>+\fB/usr/X11R6/lib/X11/xserver/\fR, 
>+\fB/usr/lib/X11/xserver/\fR,
>+\fB/usr/share/Xprint/xserver/\fR or
>+\fB/usr/openwin/server/etc/XpConfig\fR, depending on the
>+system, and may be configured in \fB/etc/init.d/xprint\fR.
>+.TP 
>+\fB${LANG}\fR
>+This environment variable selects the locale settings used by the Xprint server.
>+Xprt allows language-specific settings (stored in \fB${XPCONFIGDIR}/${LANG}/print/\fR)
>+which will override the default settings (stored in \fB${XPCONFIGDIR}/C/print/\fR).
>+If \fB${LANG}\fR is not set "C" is assumed.
>+.TP 
>+\fB${XPSERVERLIST}\fR
>+The environment variable \fB${XPSERVERLIST}\fR contains a list
>+of display identifiers (separated by whitespace) which tell an
>+application where it can find the Xprint servers. Usually
>+\fB${XPSERVERLIST}\fR is set by the profile startup scripts (e.g.
>+\fB/etc/profile\fR or \fB/etc/profile.d/xprint.sh\fR) using the output of
>+\fB/etc/init.d/xprint get_xpserverlist\fR.
>+
>+Example: 
>+
>+.nf
>+
>+		export XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`"
>+.fi
>+
>+
>+Alternatively \fB${XPSERVERLIST}\fR can be set
>+manually. Example:
>+
>+.nf
>+
>+		export XPSERVERLIST="littlecat:80 bitdog:72"
>+.fi
>+
>+instructs an application to find an Xprint server at display
>+80 on the machine "littlecat" and at display 72 on the
>+machine bigdog.
>+.TP 
>+\fB${XPRINTER}\fR 
>+The environment variable \fB${XPRINTER}\fR
>+defines the default printer used by print
>+applications. The syntax is either
>+\fIprintername\fR or
>+\fIprintername\fR@\fIdisplay\fR.
>+
>+Examples:
>+.RS 
>+.TP 
>+\fBXPRINTER=ps003\fR
>+tells an application to look for the
>+first printer named "ps003" on all Xprint
>+servers.
>+.TP 
>+\fBXPRINTER=hplaser19@littlecat:80\fR
>+tells an application to use the printer "hplaser19"
>+on the Xprint server at display 
>+"littlecat:80".
>+.RE
>+
>+
>+If \fB${XPRINTER}\fR is not set the applications
>+will examine the values of the \fB${PDPRINTER}\fR,
>+\fB${LPDEST}\fR, and 
>+\fB${PRINTER}\fR environment variables (in that order). 
>+.SH "SEE ALSO"
>+\fBX11\fR(__miscmansuffix__), \fBxplsprinters\fR(__appmansuffix__), \fBxprehashprinterlist\fR(__appmansuffix__), \fBxphelloworld\fR(__appmansuffix__), \fBxpxmhelloworld\fR(__appmansuffix__), \fBxpawhelloworld\fR(__appmansuffix__), \fBxpxthelloworld\fR(__appmansuffix__), \fBxpsimplehelloworld\fR(__appmansuffix__), \fBXserver\fR(__appmansuffix__), \fBXprt\fR(__appmansuffix__), \fBlibXp\fR(__libmansuffix__), \fBlibXprintUtils\fR(__libmansuffix__), \fBlibXprintAppUtils\fR(__libmansuffix__), \fBXmPrintShell\fR(__libmansuffix__), \fBXawPrintShell\fR(__libmansuffix__), Xprint FAQ (http://xprint.mozdev.org/docs/Xprint_FAQ.html), Xprint main site (http://xprint.mozdev.org/)
>+.SH AUTHORS
>+This manual page was written by 
>+Roland Mainz <roland.mainz@nrubsig.org> based on the original X11R6.6
>+\fBxc/programs/Xserver/XpConfig/README\fR.
>Index: xc/doc/man/general/Xprint.sgml
>===================================================================
>RCS file: xc/doc/man/general/Xprint.sgml
>diff -N xc/doc/man/general/Xprint.sgml
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ xc/doc/man/general/Xprint.sgml	26 Nov 2004 08:48:13 -0000
>@@ -0,0 +1,627 @@
>+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.2//EN" 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd'>
>+
>+
>+
>+<refentry id="Xprint">
>+  <refmeta>
>+    <refentrytitle>Xprint</refentrytitle>
>+    <manvolnum>__miscmansuffix__</manvolnum>
>+  </refmeta>
>+  <refnamediv>
>+    <refname>Xprint</refname>
>+
>+    <refpurpose>The "X print service" - a portable, network-transparent printing system based on the X11 protocol</refpurpose>
>+  </refnamediv>
>+  <refsynopsisdiv>
>+    <para>Xprint is a very flexible, extensible, scaleable, client/server
>+     print system based on ISO 10175 (and some other specs) and the X11        
>+     rendering protocol.                                                       
>+     Using Xprint an application can search, query and use devices like        
>+     printers, FAX machines or create documents in formats like PDF.           
>+     In particular, an application can seek a printer, query supported         
>+     attributes (like paper size, trays, fonts etc.), configure the printer    
>+     device to match it&rsquo;s needs and print on it like on any other X device     
>+     reusing parts of the code which is used for the video card Xserver.    
>+    </para>
>+  </refsynopsisdiv>
>+  
>+  <refsect1>
>+    <title>OVERVIEW</title>
>+    <para>
>+      The "X Print Service" technology allows X rendering to devices such as
>+      printers and fax.  Most of the service is available in the X11
>+      technology stack as Xp, with the remainder in single toolkit stacks (e.g. DtPrint for CDE).
>+      Modifications have also been made to the LessTif/Motif/Qt technology
>+      stacks to support Xprint.
>+    </para>
>+    <para>
>+      The Xp portion consists of:
>+      <itemizedlist>
>+        <listitem><para>Xp Extension for the X-Server (included in the X-Server Xprt)</para></listitem>
>+        <listitem><para>Xp Extension API for the client side (libXp/libXprintUtils)</para></listitem>
>+        <listitem><para>PCL ddx driver that converts core X to native PCL</para></listitem>
>+        <listitem><para>PDF ddx driver that converts core X to native PDF</para></listitem>
>+        <listitem><para>PostScript ddx driver that converts core X to native PostScript</para></listitem>
>+        <listitem><para>Raster ddx driver that generates xwd rasters which can be converted to PCL, PDF or PostScript rasters</para></listitem>
>+      </itemizedlist>
>+    </para>
>+    <para>
>+      From an X clients perspective, it can attach to one of two nearly
>+      identical X-Servers, a "Video" X-Server, and a "Print" X-Server
>+      which has the additional Xp capability but otherwise looks and
>+      behaves the same.   
>+    </para>
>+  </refsect1>
>+
>+  <refsect1>
>+    <title>HOW THE X PRINT SERVICE WORKS</title>
>+    <para>    
>+      The X Print Service expands on the traditional X-Server and Xlib world
>+      in four ways.
>+
>+      <orderedlist>
>+        <listitem>
>+          <para>
>+            Most obvious is the use of "print ddx drivers" instead of
>+            "video ddx drivers".  While a video ddx driver modifies pixels
>+            in a video frame buffer, a print ddx driver generates "page
>+            description language (PDL)" output (such as PCL, PDF or PostScript)
>+            or sends the print rendering instructions to a platform-specific
>+            print API (like Win32/GDI).
>+          </para>
>+          <para>
>+            Once a print ddx driver generates PDL output, it can be sent to
>+            a spooler such as <citerefentry><refentrytitle>lp</refentrytitle><manvolnum>1</manvolnum></citerefentry>
>+            or retrieved by the client (to implement functionality like "print-to-file").
>+          </para>
>+          <para>
>+            Though not currently done, a single X-Server can support both
>+            print and video ddx drivers.
>+            
>+          </para>
>+        </listitem>
>+        <listitem>
>+          <para>
>+            Since printers support "paged" output, unlike video, a portion
>+            of the Xp Extension supports APIs to delineate printed output.
>+            For example, <function>XpStartPage</function> and <function>XpEndPage</function> tell the X-Server where
>+            a physical page starts and ends in an otherwise continuous
>+            stream of X rendering primitives.  Likewise, <function>XpStartJob</function> and
>+            <function>XpEndJob</function> determine when a collection of pages starts and ends.
>+            <function>XpEndJob</function> typically causes the generated PDL to be submitted to
>+            a spooler, such as <citerefentry><refentrytitle>lp</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
>+          </para>
>+        </listitem>
>+        <listitem>
>+          <para>
>+            Since printers have extensive capabilities, another portion of
>+            the Xp Extension supports APIs to manipulate "print contexts".
>+          </para>
>+          <para>
>+            Once a printer is selected using the Xp Extension API, a print
>+            context to represent it can be created.  A print context
>+            embodies the printer selected - it contains the printer's
>+            default capabilities, selectable range of capabilities,
>+            printer state, and generated output.  Some "attributes" within
>+            the print context can be modified by the user, and the
>+            X-Server and print ddx driver will react accordingly.  For
>+            example, the attribute "content-orientation" can be set to
>+            "landscape" or "portrait" (if the printer supports these 
>+            values - which can be queried using the Xprint API as well).
>+          </para>
>+        </listitem>
>+        <listitem>
>+          <para>
>+            Since printers can have "built in" fonts, the Xp Extension in
>+            the X-Server works with the print ddx drivers to make
>+            available (for printing only) additional fonts on a per print
>+            context basis.
>+          </para>
>+          <para>
>+            When a print context is created and set for a given printer,
>+            the X font calls may be able to access additional printer
>+            fonts.  To do this (typically), the X-Server must have access
>+            to "printer metric files" (.pmf) that describe at minimum the
>+            metrics of the built in fonts.
>+          </para>
>+        </listitem>
>+      </orderedlist>
>+    </para>
>+  </refsect1>
>+
>+  <refsect1>
>+    <title>USAGE</title>
>+    <para>    
>+      There are three tasks to start the X Print Service:
>+      <orderedlist>
>+        <listitem><para>configuring the X Print Server,</para></listitem>
>+        <listitem><para>starting the X Print Service</para></listitem>
>+        <listitem><para>configuring the user session so that clients can find the running X Print Service</para></listitem>
>+      </orderedlist>
>+    </para>
>+    <para>
>+      The tasks are described in detail below.
>+    </para>
>+  </refsect1>
>+
>+  <refsect1>
>+    <title>SERVER CONFIGURATION</title>
>+    <para>
>+      The X Print Server (Xprt) can read a number of configuration files which
>+      control its behavior and support for printers.  Each vendor platform has
>+      a default location for this information.  Xprt can also read the
>+      environment variable <envar>XPCONFIGDIR</envar> to locate alternate configuration
>+      directories.  Common settings include:
>+
>+      <simplelist type="vert">
>+        <member>export XPCONFIGDIR=/X11/lib/X11/XpConfig/</member>
>+        <member>export XPCONFIGDIR=/proj/x11/xc/programs/Xserver/XpConfig/</member>
>+      </simplelist>
>+    </para>
>+    <para>
>+      Xprt has many built-in defaults, and lacking any configuration files,
>+      will immediately try to support all printers visible via <citerefentry><refentrytitle>lpstat</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
>+    </para>
>+    <para>
>+      In order of importance for configuration by a system administrator, the
>+      configuration files for a "C" locale are as follows (see <citerefentry><refentrytitle>Xprt</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry> for more
>+      details (including support for non-"C" locales)):
>+      <variablelist>
>+        <varlistentry>
>+          <term><filename>${XPCONFIGDIR}/C/print/Xprinters</filename></term>
>+          <listitem>
>+            <para>
>+              'Xprinters' is the top most configuration file.  It tells
>+              Xprt which specific printer names (e.g.  mylaser) should
>+              be supported, and whether <citerefentry><refentrytitle>lpstat</refentrytitle><manvolnum>1</manvolnum></citerefentry> or other commands
>+              should be used to automatically supplement the list of
>+              printers.
>+            </para>
>+          </listitem>
>+        </varlistentry>
>+
>+        <varlistentry>
>+          <term><filename>${XPCONFIGDIR}/C/print/attributes/printer</filename></term>
>+          <listitem>
>+            <para>
>+              The 'printer' file maps printer names to model
>+              configurations (see 'model-config' below).  For example,
>+              "mylaser" could be mapped to a "HPDJ1600C", and all other
>+              arbitrary printers could be mapped to a default, such as
>+              "HPLJ4SI".  When depending on <citerefentry><refentrytitle>lpstat</refentrytitle><manvolnum>1</manvolnum></citerefentry> in the Xprinters
>+              file, setting up defaults in 'printer' becomes all the
>+              more important.
>+            </para>
>+          </listitem>
>+        </varlistentry>
>+
>+        <varlistentry>
>+          <term><filename>${XPCONFIGDIR}/C/print/attributes/document</filename></term>
>+          <listitem>
>+            <para>
>+              The 'document' file specifies the initial document values
>+              for any print jobs.  For example, which paper tray to
>+              use, what default resolution, etc.
>+            </para>
>+          </listitem>
>+        </varlistentry>
>+
>+        <varlistentry>
>+          <term><filename>${XPCONFIGDIR}/C/print/attributes/job</filename></term>
>+          <listitem>
>+            <para>
>+              The 'job' file specifies the initial job values for any
>+              print jobs.  For example, "notification-profile" can be
>+              set so that when a print job is successfully sent to a
>+              printer, e-mail is sent to the user.
>+            </para>
>+          </listitem>
>+        </varlistentry>
>+
>+        <varlistentry>
>+          <term><filename>${XPCONFIGDIR}/C/print/models/PSdefault/model-config</filename></term>
>+          <term><filename>${XPCONFIGDIR}/C/print/models/PSdefault/fonts/fonts.dir</filename></term>
>+          <term><filename>${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00051.pmf</filename></term>
>+          <term><filename>${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00093.pmf</filename></term>
>+
>+          <listitem>
>+            <para>
>+              The 'model-config' file has attributes that describe the
>+              printer model&rsquo;s capabilities and default settings.
>+              Printer model fonts may also be present.  The model-config
>+              file also identifies the print ddx driver to be used.
>+
>+              For each printer model supported, a complete hierarchy of
>+              files should exist.  In most cases, these files do not
>+              need to be modified.
>+            </para>
>+          </listitem>
>+        </varlistentry>
>+
>+        <varlistentry>
>+          <term><filename>${XPCONFIGDIR}/C/print/ddx-config/raster/pcl</filename></term>
>+          <term><filename>${XPCONFIGDIR}/C/print/ddx-config/raster/pdf</filename></term>
>+          <term><filename>${XPCONFIGDIR}/C/print/ddx-config/raster/postscript</filename></term>
>+
>+          <listitem>
>+            <para>
>+              The print ddx drivers can have highly specific
>+              configuration files to control their behavior.  In most
>+              cases, these files do not need to be modified.
>+            </para>
>+          </listitem>
>+        </varlistentry>
>+      </variablelist>
>+      
>+      More information in how to configure and customize the X print server can be found in the
>+      <citerefentry><refentrytitle>Xprt</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry>
>+      manual page.
>+    </para>
>+  </refsect1>
>+
>+  <refsect1>
>+    <title>STARTING UP</title>
>+    <para>
>+      The summary checklist for starting the X Print Service is as follows:
>+      
>+      <orderedlist>
>+        <listitem>
>+          <para>
>+            Choose an execution model for the X Print Service.  The X
>+            Print Service can be run on a per-user session basis, per
>+            machine basis, or can be run on a few machines globally
>+            available to a number of users.
>+          </para>
>+        </listitem>
>+        <listitem>
>+          <para>
>+            If print jobs are to be submitted to a spooler (almost always
>+            the case), make sure all needed printers are available to the
>+            spooler subsystem (most often <citerefentry><refentrytitle>lp</refentrytitle><manvolnum>1</manvolnum></citerefentry>)
>+            on the same machine running the X Print Service.
>+          </para>
>+        </listitem>
>+        <listitem>
>+          <para>
>+            Configure the X Print Server.  See ``X Print Server
>+            Configuration''.
>+          </para>
>+        </listitem>
>+        <listitem>
>+          <para>
>+            Depending on #1, start the X Print Server process "Xprt", and
>+            then the toolkit-specific Print Dialog Manager Daemon process
>+            (such as CDEnext's "dtpdmd") at the appropriate times.
>+            Note that libXprintUtils-based applications/toolkits do not need
>+            a Print Dialog Manager Daemon process to use Xprint.
>+          </para>
>+        </listitem>
>+      </orderedlist>     
>+      The details are described below.
>+    </para>
>+    <para>
>+      Because the X Print Service is based on X, it can be easily distributed.
>+      The most significant factors in which execution model to choose will be
>+      driven by:
>+      <itemizedlist>
>+        <listitem>
>+          <para>
>+            how many printers will be accessable through the printer
>+            subsystem on any given machine.  A system administrator may
>+            choose to cluster printers on a few given machines, or
>+            scatter them across an organization and possibly make
>+            extensive use of remote spoolers to make them globally
>+            available.
>+          </para>
>+        </listitem>
>+        <listitem>
>+          <para>
>+            how many machines will need a copy of the X Print Server
>+            configuration files.  The files have been architected so
>+            that one super-set version of them can be maintained and
>+            distributed (e.g.  via NFS), and a per-machine or per-user
>+            version of the `Xprinters' is all that is needed to have the
>+            appropriate information in them utilized or ignored.
>+          </para>
>+        </listitem>
>+        <listitem>
>+          <para>
>+            how many users can demand services from a given X Print
>+            Service.
>+          </para>
>+        </listitem>
>+      </itemizedlist>
>+
>+      With the above in mind, some obvious execution models include:
>+      <itemizedlist>
>+        <listitem>
>+          <para>
>+            Global - in this model, the system administrator is choosing
>+            to run the X Print Service on a *few* select machines with
>+            appropriate printers configured, and allow clients access to
>+            the global resource.  This can centralize the administration
>+            of printers and configuration files, but may have to be
>+            monitored for performance loading.
>+          </para>
>+          <para>
>+            Startup would likely be done by boot-up scripts (such as <filename>/etc/init.d/xprint</filename>).
>+          </para>
>+        </listitem>
>+
>+        <listitem>
>+          <para>
>+            Per-machine - every machine with potential X Print Service
>+            users would run the service.  Printer and configuration file
>+            administration is decentralized, and usage would be limited
>+            to the users on the machine.
>+          </para>
>+          <para>
>+            Startup would likely be done by boot-up scripts (such as <filename>/etc/init.d/xprint</filename>).
>+          </para>
>+        </listitem>
>+
>+        <listitem>
>+          <para>
>+            Per-user session - every user would run an entire X Print
>+            Service for themselves.  In the future, the Video X Server
>+            normally started may contain Print X Server capability, so
>+            this model becomes very natural.
>+          </para>
>+          <para>
>+            Startup would likely be done at session login or by
>+            launching actions or processes manually once the user
>+            logs in.  Note: Deamons like "dtpdmd" must be started after Xprt.
>+          </para>
>+        </listitem>
>+      </itemizedlist>
>+     </para>
>+     <para>
>+       Starting of the processes is straight forward.  In strict order (example is for manually starting the X print server for CDEnext usage):
>+       <orderedlist>
>+         <listitem>
>+           <para>
>+             <programlisting>[machineA] % Xprt [-XpFile &lt;Xprinters file&gt;] [:dispNum] &amp;</programlisting>
>+           </para>
>+           <para>
>+             Note that Xprt will look for configuration files in either
>+             a default location or where <envar>XPCONFIGDIR</envar> points.
>+           </para>
>+           <para>
>+             <option>-XpFile</option> specifies an alternate `Xprinters' file, rather
>+             than the default one or `<filename>${XPCONFIGDIR}/C/print/Xprinters</filename>'.
>+           </para>
>+         </listitem>
>+         <listitem>
>+           <para>
>+             <programlisting>[machineA] % dtpdmd -d machineA[:dispNum] [-l /tmp/dtpdmd.log] &amp;</programlisting>
>+           </para>
>+           <para>
>+            The dtpdmd will maintain an X-Selection on the X-Server,
>+            and will start dtpdm's as required to service requests.
>+           </para>
>+         </listitem>
>+       </orderedlist>
>+     </para>
>+     <para>
>+       In all but the per-user session model, the machine running the dtpdmd
>+       (thus dtpdm's) will need display authorization to the users video
>+       display.
>+    </para>
>+  </refsect1>
>+
>+  <refsect1>
>+    <title>CLIENT CONFIGURATION</title>
>+    <para>
>+      Once a X Print Server and dtpdmd have been started -- many of them
>+      in some cases -- clients will need to find and use them.  There are
>+      two mechanisms that allow clients to discover X Print Servers and
>+      printers.
>+
>+      <itemizedlist>
>+        <listitem>
>+          <para>
>+            "X Print Specifier" - assuming usage of the DtPrint/XprintUtils-based print
>+            applications, the following notation is understood:
>+          </para>
>+          <para>
>+            <programlisting>printer_name@machine[:dispNum]</programlisting>
>+          </para>
>+          <para>
>+            For example:
>+          </para>
>+          <para>
>+            <programlisting>colorlj7@printhub:2</programlisting>
>+          </para>
>+          <para>
>+           In the above example, the X Print Server running at `printhub:2'
>+           is assumed to support the printer named `colorlj7'.
>+          </para>
>+        </listitem>
>+        <listitem>
>+          <para>
>+            <envar>${XPSERVERLIST}</envar> - assuming usage of the DtPrint print dialogs,
>+            the environment variable <envar>${XPSERVERLIST}</envar> can contain a list
>+            of X Print Servers.  For example:
>+          </para>
>+          <para>
>+            <programlisting>XPSERVERLIST="printhub:2 printhub:3 otherdept:0"</programlisting>
>+          </para>
>+          <para>
>+            Then in the dialogs, only a printer name needs to be entered.
>+            The dialog will then search the X Print Servers in <envar>${XPSERVERLIST}</envar>
>+            for a server than supports the printer, and then establish
>+            contact.
>+          </para>
>+        </listitem>
>+      </itemizedlist>
>+    </para>
>+  </refsect1>
>+
>+  <refsect1>
>+    <title>END-USER SEQUENCE</title>
>+    <para>
>+      From most CDEnext applications, printing is accomplished by bringing
>+      down the &lt;File&gt; menu and selecting &lt;Print...&gt;.  This will result in
>+      the DtPrintSetupBox dialog, which will request the name of a printer,
>+      and offer limited capability to configure print options (e.g. number
>+      of copies).  If the user wishes, they can select &lt;Setup...&gt;, which
>+      will start a dtpdm capable of modifying additional print options.
>+      Finally, the user should select &lt;Print&gt;.
>+    </para>
>+  </refsect1>
>+
>+  <refsect1>
>+    <title>ENVIRONMENT</title>
>+    <variablelist>
>+      <varlistentry>
>+        <term><envar>${XPCONFIGDIR}</envar></term>
>+        <listitem>
>+          <para> This environment variable points to the  root
>+	    of  the Xprint server configuration directory hierarchy.
>+	    If the variable is not defined,  the  default
>+	    path  is be assumed.  The default path may be
>+            <filename>/usr/X11R6/lib/X11/xserver/</filename>, 
>+            <filename>/usr/lib/X11/xserver/</filename>,
>+            <filename>/usr/share/Xprint/xserver/</filename> or
>+            <filename>/usr/openwin/server/etc/XpConfig</filename>, depending on the
>+	    system, and may be configured in <filename>/etc/init.d/xprint</filename>.</para>
>+        </listitem>
>+      </varlistentry>
>+
>+      <varlistentry>
>+        <term><envar>${LANG}</envar></term>
>+        <listitem>
>+          <para>
>+            This environment variable selects the locale settings used by the Xprint server.
>+            Xprt allows language-specific settings (stored in <filename>${XPCONFIGDIR}/${LANG}/print/</filename>)
>+            which will override the default settings (stored in <filename>${XPCONFIGDIR}/C/print/</filename>).
>+            If <envar>${LANG}</envar> is not set "C" is assumed.
>+          </para>
>+        </listitem>
>+      </varlistentry>
>+      
>+      <varlistentry>
>+        <term><envar>${XPSERVERLIST}</envar></term>
>+        <listitem>
>+	    <para>The environment variable <envar>${XPSERVERLIST}</envar> contains a list
>+	    of display identifiers (separated by whitespace) which tell an
>+	    application where it can find the Xprint servers.  Usually
>+	    <envar>${XPSERVERLIST}</envar> is set by the profile startup scripts (e.g.
>+	    <filename>/etc/profile</filename> or <filename>/etc/profile.d/xprint.sh</filename>) using the output of
>+	    <userinput>/etc/init.d/xprint get_xpserverlist</userinput>.</para>
>+	  <para>Example: 
>+	    <informalexample>
>+	      <programlisting>
>+		export XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`"</programlisting>
>+	    </informalexample>
>+	  </para>
>+	  <para>Alternatively <envar>${XPSERVERLIST}</envar> can be set
>+	    manually. Example:</para>
>+	    <informalexample>
>+	      <programlisting>
>+		export XPSERVERLIST="littlecat:80 bitdog:72"</programlisting>
>+	    </informalexample>
>+	  <para>
>+	    instructs an application to find an Xprint server at display
>+	    80 on the machine "littlecat" and at display 72 on the
>+	    machine bigdog.
>+	  </para>
>+	</listitem>
>+      </varlistentry>
>+
>+      <varlistentry>
>+        <term><envar>${XPRINTER}</envar>
>+        </term>
>+        <listitem>
>+          <para>The environment variable <envar>${XPRINTER}</envar>
>+	    defines the default printer used by print
>+	    applications. The syntax is either
>+	    <replaceable>printername</replaceable> or
>+	    <replaceable>printername</replaceable>@<replaceable>display</replaceable>.</para>
>+	    <para>Examples:
>+	    <variablelist>
>+	      <varlistentry>
>+		<term><userinput>XPRINTER=ps003</userinput></term>
>+		<listitem><para>
>+		  tells an application to look for the
>+		  first printer named "ps003" on all Xprint
>+		  servers.</para>
>+		</listitem>
>+	      </varlistentry>
>+	
>+	      <varlistentry>
>+		
>+		<term><userinput>XPRINTER=hplaser19@littlecat:80</userinput></term>
>+		<listitem><para>
>+		  tells an application to use the printer "hplaser19"
>+		on the Xprint server at display 
>+		  "littlecat:80".</para>
>+	      </listitem>
>+	      </varlistentry>
>+
>+	    </variablelist>
>+	  </para>
>+	  <para>If <envar>${XPRINTER}</envar> is not set the applications
>+	    will examine the values of the <envar>${PDPRINTER}</envar>,
>+	    <envar>${LPDEST}</envar>, and 
>+	    <envar>${PRINTER}</envar> environment variables (in that order).  
>+	  </para>
>+        </listitem>
>+      </varlistentry>
>+    </variablelist>
>+  </refsect1>
>+
>+  <refsect1>
>+    <title>SEE ALSO</title>
>+    <para>
>+      <simplelist type="inline">
>+        
>+        
>+        
>+        
>+
>+        <member><citerefentry><refentrytitle>X11</refentrytitle><manvolnum>__miscmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>xplsprinters</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>xprehashprinterlist</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>xphelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>xpxmhelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>xpawhelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>xpxthelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>xpsimplehelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>Xprt</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>+        
>+        <member><citerefentry><refentrytitle>libXp</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>libXprintUtils</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>libXprintAppUtils</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>XmPrintShell</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>+        <member><citerefentry><refentrytitle>XawPrintShell</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>+        <member>Xprint FAQ (<ulink url="http://xprint.mozdev.org/docs/Xprint_FAQ.html">http://xprint.mozdev.org/docs/Xprint_FAQ.html</ulink>)</member>
>+        <member>Xprint main site (<ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink>)</member>
>+      </simplelist>
>+    </para>
>+  </refsect1>
>+
>+  <refsect1>
>+    <title>AUTHORS</title>
>+    <para>
>+      This manual page was written by 
>+      Roland Mainz <email>roland.mainz@nrubsig.org</email> based on the original X11R6.6
>+      <filename>xc/programs/Xserver/XpConfig/README</filename>.
>+    </para>
>+  </refsect1>
>+</refentry>
>+
>Index: xc/programs/Xserver/Xprint/Imakefile
>===================================================================
>RCS file: /cvs/xorg/xc/programs/Xserver/Xprint/Imakefile,v
>retrieving revision 1.4
>diff -u -2 -0 -r1.4 Imakefile
>--- xc/programs/Xserver/Xprint/Imakefile	25 Nov 2004 22:42:51 -0000	1.4
>+++ xc/programs/Xserver/Xprint/Imakefile	26 Nov 2004 08:48:16 -0000
>@@ -111,33 +111,26 @@
> LinkSourceFile(dpmsproc.h,$(SERVERSRC)/Xext)
> SpecialCObjectRule(dpmsstubs,$(ICONFIGFILES),$(PO_DEFINES) $(OS_DEFINES) $(XPEXT_DEFINES) -DXPRINT)
> #endif
> #endif
> 
> #ifdef OS2Architecture
> LinkSourceFile(os2_stubs.c,../hw/xfree86/os-support/os2)
> SpecialCObjectRule(os2_stubs,$(ICONFIGFILES),-DOS2NULLSELECT)
> #endif
> 
> #ifdef IHaveSubdirs
> MakeSubdirs($(SUBDIRS))
> DependSubdirs($(SUBDIRS))
> MakeLintLibSubdirs($(SUBDIRS))
> #endif
> 
> DependTarget()
> 
> InstallManPage(Xprt,$(MANDIR))
> 
>-MANDIR = $(MISCMANDIR)
>-MANSUFFIX = $(MISCMANSUFFIX)
>-InstallManPage(Xprint,$(MANDIR))
>-
> #ifdef HasDocBookTools
>-all:: Xprt.man Xprt.html Xprint.man Xprint.html
>+all:: Xprt.man Xprt.html
> 
> ConvertDocBookToManPage(Xprt.sgml, Xprt.man)
> ConvertDocBookToHTML(Xprt.sgml, Xprt.html)
>-
>-ConvertDocBookToManPage(Xprint.sgml, Xprint.man)
>-ConvertDocBookToHTML(Xprint.sgml, Xprint.html)
> #endif /* HasDocBookTools */
>Index: xc/programs/Xserver/Xprint/Xprint.html
>===================================================================
>RCS file: xc/programs/Xserver/Xprint/Xprint.html
>diff -N xc/programs/Xserver/Xprint/Xprint.html
>--- xc/programs/Xserver/Xprint/Xprint.html	8 Oct 2004 02:39:40 -0000	1.4
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,296 +0,0 @@
>-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Xprint</title><meta name="generator" content="DocBook XSL Stylesheets V1.62.4"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="Xprint"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>Xprint &#8212; The &quot;X print service&quot; - a portable, network-transparent printing system based on the X11 protocol</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p>Xprint is a very flexible, extensible, scaleable, client/server
>-     print system based on ISO 10175 (and some other specs) and the X11        
>-     rendering protocol.                                                       
>-     Using Xprint an application can search, query and use devices like        
>-     printers, FAX machines or create documents in formats like PDF.           
>-     In particular, an application can seek a printer, query supported         
>-     attributes (like paper size, trays, fonts etc.), configure the printer    
>-     device to match it&#8217;s needs and print on it like on any other X device     
>-     reusing parts of the code which is used for the video card Xserver.    
>-    </p></div><div xmlns:ns1="" class="refsect1" lang="en"><a name="id2802144"></a><h2>OVERVIEW</h2><p>
>-      The &quot;X Print Service&quot; technology allows X rendering to devices such as
>-      printers and fax.  Most of the service is available in the X11
>-      technology stack as Xp, with the remainder in single toolkit stacks (e.g. DtPrint for CDE).
>-      Modifications have also been made to the LessTif/Motif/Qt technology
>-      stacks to support Xprint.
>-    </p><p>
>-      The Xp portion consists of:
>-      </p><div class="itemizedlist"><ul type="disc"><li><p>Xp Extension for the X-Server (included in the X-Server Xprt)</p></li><li><p>Xp Extension API for the client side (libXp/libXprintUtils)</p></li><li><p>PCL ddx driver that converts core X to native PCL</p></li><li><p>PDF ddx driver that converts core X to native PDF</p></li><li><p>PostScript ddx driver that converts core X to native PostScript</p></li><li><p>Raster ddx driver that generates xwd rasters which can be converted to PCL, PDF or PostScript rasters</p></li></ul></div><p>
>-      From an X clients perspective, it can attach to one of two nearly
>-      identical X-Servers, a &quot;Video&quot; X-Server, and a &quot;Print&quot; X-Server
>-      which has the additional Xp capability but otherwise looks and
>-      behaves the same.   
>-    </p></div><div xmlns:ns2="" class="refsect1" lang="en"><a name="id2804972"></a><h2>HOW THE X PRINT SERVICE WORKS</h2><p>    
>-      The X Print Service expands on the traditional X-Server and Xlib world
>-      in four ways.
>-
>-      </p><div class="orderedlist"><ol type="1"><li><p>
>-            Most obvious is the use of &quot;print ddx drivers&quot; instead of
>-            &quot;video ddx drivers&quot;.  While a video ddx driver modifies pixels
>-            in a video frame buffer, a print ddx driver generates &quot;page
>-            description language (PDL)&quot; output (such as PCL, PDF or PostScript)
>-            or sends the print rendering instructions to a platform-specific
>-            print API (like Win32/GDI).
>-          </p><p>
>-            Once a print ddx driver generates PDL output, it can be sent to
>-            a spooler such as <span class="citerefentry"><span class="refentrytitle">lp</span>(1)</span>
>-            or retrieved by the client (to implement functionality like &quot;print-to-file&quot;).
>-          </p><p>
>-            Though not currently done, a single X-Server can support both
>-            print and video ddx drivers.
>-            </p></li><li><p>
>-            Since printers support &quot;paged&quot; output, unlike video, a portion
>-            of the Xp Extension supports APIs to delineate printed output.
>-            For example, <tt class="function">XpStartPage</tt> and <tt class="function">XpEndPage</tt> tell the X-Server where
>-            a physical page starts and ends in an otherwise continuous
>-            stream of X rendering primitives.  Likewise, <tt class="function">XpStartJob</tt> and
>-            <tt class="function">XpEndJob</tt> determine when a collection of pages starts and ends.
>-            <tt class="function">XpEndJob</tt> typically causes the generated PDL to be submitted to
>-            a spooler, such as <span class="citerefentry"><span class="refentrytitle">lp</span>(1)</span>.
>-          </p></li><li><p>
>-            Since printers have extensive capabilities, another portion of
>-            the Xp Extension supports APIs to manipulate &quot;print contexts&quot;.
>-          </p><p>
>-            Once a printer is selected using the Xp Extension API, a print
>-            context to represent it can be created.  A print context
>-            embodies the printer selected - it contains the printer's
>-            default capabilities, selectable range of capabilities,
>-            printer state, and generated output.  Some &quot;attributes&quot; within
>-            the print context can be modified by the user, and the
>-            X-Server and print ddx driver will react accordingly.  For
>-            example, the attribute &quot;content-orientation&quot; can be set to
>-            &quot;landscape&quot; or &quot;portrait&quot; (if the printer supports these 
>-            values - which can be queried using the Xprint API as well).
>-          </p></li><li><p>
>-            Since printers can have &quot;built in&quot; fonts, the Xp Extension in
>-            the X-Server works with the print ddx drivers to make
>-            available (for printing only) additional fonts on a per print
>-            context basis.
>-          </p><p>
>-            When a print context is created and set for a given printer,
>-            the X font calls may be able to access additional printer
>-            fonts.  To do this (typically), the X-Server must have access
>-            to &quot;printer metric files&quot; (.pmf) that describe at minimum the
>-            metrics of the built in fonts.
>-          </p></li></ol></div></div><div xmlns:ns3="" class="refsect1" lang="en"><a name="id2804885"></a><h2>USAGE</h2><p>    
>-      There are three tasks to start the X Print Service:
>-      </p><div class="orderedlist"><ol type="1"><li><p>configuring the X Print Server,</p></li><li><p>starting the X Print Service</p></li><li><p>configuring the user session so that clients can find the running X Print Service</p></li></ol></div><p>
>-      The tasks are described in detail below.
>-    </p></div><div xmlns:ns4="" class="refsect1" lang="en"><a name="id2804911"></a><h2>SERVER CONFIGURATION</h2><p>
>-      The X Print Server (Xprt) can read a number of configuration files which
>-      control its behavior and support for printers.  Each vendor platform has
>-      a default location for this information.  Xprt can also read the
>-      environment variable <tt class="envar">XPCONFIGDIR</tt> to locate alternate configuration
>-      directories.  Common settings include:
>-
>-      </p><table class="simplelist" border="0" summary="Simple list"><tr><td>export XPCONFIGDIR=/X11/lib/X11/XpConfig/</td></tr><tr><td>export XPCONFIGDIR=/proj/x11/xc/programs/Xserver/XpConfig/</td></tr></table><p>
>-      Xprt has many built-in defaults, and lacking any configuration files,
>-      will immediately try to support all printers visible via <span class="citerefentry"><span class="refentrytitle">lpstat</span>(1)</span>.
>-    </p><p>
>-      In order of importance for configuration by a system administrator, the
>-      configuration files for a &quot;C&quot; locale are as follows (see <span class="citerefentry"><span class="refentrytitle">Xprt</span>(7)</span> for more
>-      details (including support for non-&quot;C&quot; locales)):
>-      </p><div class="variablelist"><dl><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/Xprinters</tt></span></dt><dd><p>
>-              'Xprinters' is the top most configuration file.  It tells
>-              Xprt which specific printer names (e.g.  mylaser) should
>-              be supported, and whether <span class="citerefentry"><span class="refentrytitle">lpstat</span>(1)</span> or other commands
>-              should be used to automatically supplement the list of
>-              printers.
>-            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/attributes/printer</tt></span></dt><dd><p>
>-              The 'printer' file maps printer names to model
>-              configurations (see 'model-config' below).  For example,
>-              &quot;mylaser&quot; could be mapped to a &quot;HPDJ1600C&quot;, and all other
>-              arbitrary printers could be mapped to a default, such as
>-              &quot;HPLJ4SI&quot;.  When depending on <span class="citerefentry"><span class="refentrytitle">lpstat</span>(1)</span> in the Xprinters
>-              file, setting up defaults in 'printer' becomes all the
>-              more important.
>-            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/attributes/document</tt></span></dt><dd><p>
>-              The 'document' file specifies the initial document values
>-              for any print jobs.  For example, which paper tray to
>-              use, what default resolution, etc.
>-            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/attributes/job</tt></span></dt><dd><p>
>-              The 'job' file specifies the initial job values for any
>-              print jobs.  For example, &quot;notification-profile&quot; can be
>-              set so that when a print job is successfully sent to a
>-              printer, e-mail is sent to the user.
>-            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/model-config</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/fonts/fonts.dir</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00051.pmf</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00093.pmf</tt></span></dt><dd><p>
>-              The 'model-config' file has attributes that describe the
>-              printer model&#8217;s capabilities and default settings.
>-              Printer model fonts may also be present.  The model-config
>-              file also identifies the print ddx driver to be used.
>-
>-              For each printer model supported, a complete hierarchy of
>-              files should exist.  In most cases, these files do not
>-              need to be modified.
>-            </p></dd><dt><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/ddx-config/raster/pcl</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/ddx-config/raster/pdf</tt>, </span><span class="term"><tt class="filename">${XPCONFIGDIR}/C/print/ddx-config/raster/postscript</tt></span></dt><dd><p>
>-              The print ddx drivers can have highly specific
>-              configuration files to control their behavior.  In most
>-              cases, these files do not need to be modified.
>-            </p></dd></dl></div><p>
>-      
>-      More information in how to configure and customize the X print server can be found in the
>-      <span class="citerefentry"><span class="refentrytitle">Xprt</span>(7)</span>
>-      manual page.
>-    </p></div><div xmlns:ns5="" class="refsect1" lang="en"><a name="id2805166"></a><h2>STARTING UP</h2><p>
>-      The summary checklist for starting the X Print Service is as follows:
>-      
>-      </p><div class="orderedlist"><ol type="1"><li><p>
>-            Choose an execution model for the X Print Service.  The X
>-            Print Service can be run on a per-user session basis, per
>-            machine basis, or can be run on a few machines globally
>-            available to a number of users.
>-          </p></li><li><p>
>-            If print jobs are to be submitted to a spooler (almost always
>-            the case), make sure all needed printers are available to the
>-            spooler subsystem (most often <span class="citerefentry"><span class="refentrytitle">lp</span>(1)</span>)
>-            on the same machine running the X Print Service.
>-          </p></li><li><p>
>-            Configure the X Print Server.  See ``X Print Server
>-            Configuration''.
>-          </p></li><li><p>
>-            Depending on #1, start the X Print Server process &quot;Xprt&quot;, and
>-            then the toolkit-specific Print Dialog Manager Daemon process
>-            (such as CDEnext's &quot;dtpdmd&quot;) at the appropriate times.
>-            Note that libXprintUtils-based applications/toolkits do not need
>-            a Print Dialog Manager Daemon process to use Xprint.
>-          </p></li></ol></div><p>     
>-      The details are described below.
>-    </p><p>
>-      Because the X Print Service is based on X, it can be easily distributed.
>-      The most significant factors in which execution model to choose will be
>-      driven by:
>-      </p><div class="itemizedlist"><ul type="disc"><li><p>
>-            how many printers will be accessable through the printer
>-            subsystem on any given machine.  A system administrator may
>-            choose to cluster printers on a few given machines, or
>-            scatter them across an organization and possibly make
>-            extensive use of remote spoolers to make them globally
>-            available.
>-          </p></li><li><p>
>-            how many machines will need a copy of the X Print Server
>-            configuration files.  The files have been architected so
>-            that one super-set version of them can be maintained and
>-            distributed (e.g.  via NFS), and a per-machine or per-user
>-            version of the `Xprinters' is all that is needed to have the
>-            appropriate information in them utilized or ignored.
>-          </p></li><li><p>
>-            how many users can demand services from a given X Print
>-            Service.
>-          </p></li></ul></div><p>
>-
>-      With the above in mind, some obvious execution models include:
>-      </p><div class="itemizedlist"><ul type="disc"><li><p>
>-            Global - in this model, the system administrator is choosing
>-            to run the X Print Service on a *few* select machines with
>-            appropriate printers configured, and allow clients access to
>-            the global resource.  This can centralize the administration
>-            of printers and configuration files, but may have to be
>-            monitored for performance loading.
>-          </p><p>
>-            Startup would likely be done by boot-up scripts (such as <tt class="filename">/etc/init.d/xprint</tt>).
>-          </p></li><li><p>
>-            Per-machine - every machine with potential X Print Service
>-            users would run the service.  Printer and configuration file
>-            administration is decentralized, and usage would be limited
>-            to the users on the machine.
>-          </p><p>
>-            Startup would likely be done by boot-up scripts (such as <tt class="filename">/etc/init.d/xprint</tt>).
>-          </p></li><li><p>
>-            Per-user session - every user would run an entire X Print
>-            Service for themselves.  In the future, the Video X Server
>-            normally started may contain Print X Server capability, so
>-            this model becomes very natural.
>-          </p><p>
>-            Startup would likely be done at session login or by
>-            launching actions or processes manually once the user
>-            logs in.  Note: Deamons like &quot;dtpdmd&quot; must be started after Xprt.
>-          </p></li></ul></div><p>
>-       Starting of the processes is straight forward.  In strict order (example is for manually starting the X print server for CDEnext usage):
>-       </p><div class="orderedlist"><ol type="1"><li><pre class="programlisting">[machineA] % Xprt [-XpFile Xprinters file] [:dispNum] </pre><p>
>-             Note that Xprt will look for configuration files in either
>-             a default location or where <tt class="envar">XPCONFIGDIR</tt> points.
>-           </p><p><tt class="option">-XpFile</tt> specifies an alternate `Xprinters' file, rather
>-             than the default one or `<tt class="filename">${XPCONFIGDIR}/C/print/Xprinters</tt>'.
>-           </p></li><li><pre class="programlisting">[machineA] % dtpdmd -d machineA[:dispNum] [-l /tmp/dtpdmd.log] </pre><p>
>-            The dtpdmd will maintain an X-Selection on the X-Server,
>-            and will start dtpdm's as required to service requests.
>-           </p></li></ol></div><p>
>-       In all but the per-user session model, the machine running the dtpdmd
>-       (thus dtpdm's) will need display authorization to the users video
>-       display.
>-    </p></div><div xmlns:ns6="" class="refsect1" lang="en"><a name="id2805371"></a><h2>CLIENT CONFIGURATION</h2><p>
>-      Once a X Print Server and dtpdmd have been started -- many of them
>-      in some cases -- clients will need to find and use them.  There are
>-      two mechanisms that allow clients to discover X Print Servers and
>-      printers.
>-
>-      </p><div class="itemizedlist"><ul type="disc"><li><p>
>-            &quot;X Print Specifier&quot; - assuming usage of the DtPrint/XprintUtils-based print
>-            applications, the following notation is understood:
>-          </p><pre class="programlisting">printer_name@machine[:dispNum]</pre><p>
>-            For example:
>-          </p><pre class="programlisting">colorlj7@printhub:2</pre><p>
>-           In the above example, the X Print Server running at `printhub:2'
>-           is assumed to support the printer named `colorlj7'.
>-          </p></li><li><p><tt class="envar">${XPSERVERLIST}</tt> - assuming usage of the DtPrint print dialogs,
>-            the environment variable <tt class="envar">${XPSERVERLIST}</tt> can contain a list
>-            of X Print Servers.  For example:
>-          </p><pre class="programlisting">XPSERVERLIST=&quot;printhub:2 printhub:3 otherdept:0&quot;</pre><p>
>-            Then in the dialogs, only a printer name needs to be entered.
>-            The dialog will then search the X Print Servers in <tt class="envar">${XPSERVERLIST}</tt>
>-            for a server than supports the printer, and then establish
>-            contact.
>-          </p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2806227"></a><h2>END-USER SEQUENCE</h2><p>
>-      From most CDEnext applications, printing is accomplished by bringing
>-      down the File menu and selecting Print....  This will result in
>-      the DtPrintSetupBox dialog, which will request the name of a printer,
>-      and offer limited capability to configure print options (e.g. number
>-      of copies).  If the user wishes, they can select Setup..., which
>-      will start a dtpdm capable of modifying additional print options.
>-      Finally, the user should select Print.
>-    </p></div><div class="refsect1" lang="en"><a name="id2806249"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term"><tt class="envar">${XPCONFIGDIR}</tt></span></dt><dd><p> This environment variable points to the  root
>-	    of  the Xprint server configuration directory hierarchy.
>-	    If the variable is not defined,  the  default
>-	    path  is be assumed.  The default path may be
>-            <tt class="filename">/usr/X11R6/lib/X11/xserver/</tt>, 
>-            <tt class="filename">/usr/lib/X11/xserver/</tt>,
>-            <tt class="filename">/usr/share/Xprint/xserver/</tt> or
>-            <tt class="filename">/usr/openwin/server/etc/XpConfig</tt>, depending on the
>-	    system, and may be configured in <tt class="filename">/etc/init.d/xprint</tt>.</p></dd><dt><span class="term"><tt class="envar">${LANG}</tt></span></dt><dd><p>
>-            This environment variable selects the locale settings used by the Xprint server.
>-            Xprt allows language-specific settings (stored in <tt class="filename">${XPCONFIGDIR}/${LANG}/print/</tt>)
>-            which will override the default settings (stored in <tt class="filename">${XPCONFIGDIR}/C/print/</tt>).
>-            If <tt class="envar">${LANG}</tt> is not set &quot;C&quot; is assumed.
>-          </p></dd><dt><span class="term"><tt class="envar">${XPSERVERLIST}</tt></span></dt><dd xmlns:ns7=""><p>The environment variable <tt class="envar">${XPSERVERLIST}</tt> contains a list
>-	    of display identifiers (separated by whitespace) which tell an
>-	    application where it can find the Xprint servers.  Usually
>-	    <tt class="envar">${XPSERVERLIST}</tt> is set by the profile startup scripts (e.g.
>-	    <tt class="filename">/etc/profile</tt> or <tt class="filename">/etc/profile.d/xprint.sh</tt>) using the output of
>-	    <b class="userinput"><tt>/etc/init.d/xprint get_xpserverlist</tt></b>.</p><p>Example: 
>-	    </p><div class="informalexample"><pre class="programlisting">
>-		export XPSERVERLIST=&quot;`/etc/init.d/xprint get_xpserverlist`&quot;</pre></div><p>Alternatively <tt class="envar">${XPSERVERLIST}</tt> can be set
>-	    manually. Example:</p><div class="informalexample"><pre class="programlisting">
>-		export XPSERVERLIST=&quot;littlecat:80 bitdog:72&quot;</pre></div><p>
>-	    instructs an application to find an Xprint server at display
>-	    80 on the machine &quot;littlecat&quot; and at display 72 on the
>-	    machine bigdog.
>-	  </p></dd><dt><span class="term"><tt class="envar">${XPRINTER}</tt></span></dt><dd xmlns:ns8=""><p>The environment variable <tt class="envar">${XPRINTER}</tt>
>-	    defines the default printer used by print
>-	    applications. The syntax is either
>-	    <i class="replaceable"><tt>printername</tt></i> or
>-	    <i class="replaceable"><tt>printername</tt></i>@<i class="replaceable"><tt>display</tt></i>.</p><p>Examples:
>-	    </p><div class="variablelist"><dl><dt><span class="term"><b class="userinput"><tt>XPRINTER=ps003</tt></b></span></dt><dd><p>
>-		  tells an application to look for the
>-		  first printer named &quot;ps003&quot; on all Xprint
>-		  servers.</p></dd><dt><span class="term"><b class="userinput"><tt>XPRINTER=hplaser19@littlecat:80</tt></b></span></dt><dd><p>
>-		  tells an application to use the printer &quot;hplaser19&quot;
>-		on the Xprint server at display 
>-		  &quot;littlecat:80&quot;.</p></dd></dl></div><p>If <tt class="envar">${XPRINTER}</tt> is not set the applications
>-	    will examine the values of the <tt class="envar">${PDPRINTER}</tt>,
>-	    <tt class="envar">${LPDEST}</tt>, and 
>-	    <tt class="envar">${PRINTER}</tt> environment variables (in that order).  
>-	  </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2806468"></a><h2>SEE ALSO</h2><p><span class="simplelist"><span class="citerefentry"><span class="refentrytitle">X11</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xplsprinters</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xprehashprinterlist</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xphelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xpxmhelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xpawhelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xpxthelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">xpsimplehelloworld</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">Xserver</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">Xprt</span>(7)</span>, <span class="citerefentry"><span class="refentrytitle">libXp</span>(3x)</span>, <span class="citerefentry"><span class="refentrytitle">libXprintUtils</span>(3x)</span>, <span class="citerefentry"><span class="refentrytitle">libXprintAppUtils</span>(3x)</span>, <span class="citerefentry"><span class="refentrytitle">XmPrintShell</span>(3x)</span>, <span class="citerefentry"><span class="refentrytitle">XawPrintShell</span>(3x)</span>, Xprint FAQ (<a href="http://xprint.mozdev.org/docs/Xprint_FAQ.html" target="_top">http://xprint.mozdev.org/docs/Xprint_FAQ.html</a>), Xprint main site (<a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a>)</span></p></div><div class="refsect1" lang="en"><a name="id2806639"></a><h2>AUTHORS</h2><p>
>-      This manual page was written by 
>-      Roland Mainz <tt class="email">&lt;<a href="mailto:roland.mainz@nrubsig.org">roland.mainz@nrubsig.org</a>&gt;</tt> based on the original X11R6.6
>-      <tt class="filename">xc/programs/Xserver/XpConfig/README</tt>.
>-    </p></div></div></body></html>
>Index: xc/programs/Xserver/Xprint/Xprint.man
>===================================================================
>RCS file: xc/programs/Xserver/Xprint/Xprint.man
>diff -N xc/programs/Xserver/Xprint/Xprint.man
>--- xc/programs/Xserver/Xprint/Xprint.man	8 Oct 2004 02:39:40 -0000	1.4
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,421 +0,0 @@
>-.\" -*- coding: us-ascii -*-
>-.TH Xprint __miscmansuffix__ "8 October 2004"  
>-.SH NAME
>-Xprint \- The "X print service" - a portable, network-transparent printing system based on the X11 protocol
>-.SH SYNOPSIS
>-Xprint is a very flexible, extensible, scaleable, client/server
>-print system based on ISO 10175 (and some other specs) and the X11 
>-rendering protocol. 
>-Using Xprint an application can search, query and use devices like 
>-printers, FAX machines or create documents in formats like PDF. 
>-In particular, an application can seek a printer, query supported 
>-attributes (like paper size, trays, fonts etc.), configure the printer 
>-device to match it\(cqs needs and print on it like on any other X device 
>-reusing parts of the code which is used for the video card Xserver. 
>-.SH OVERVIEW
>-The "X Print Service" technology allows X rendering to devices such as
>-printers and fax. Most of the service is available in the X11
>-technology stack as Xp, with the remainder in single toolkit stacks (e.g. DtPrint for CDE).
>-Modifications have also been made to the LessTif/Motif/Qt technology
>-stacks to support Xprint.
>-.PP
>-The Xp portion consists of:
>-.TP 0.2i
>-\(bu
>-Xp Extension for the X-Server (included in the X-Server Xprt)
>-.TP 0.2i
>-\(bu
>-Xp Extension API for the client side (libXp/libXprintUtils)
>-.TP 0.2i
>-\(bu
>-PCL ddx driver that converts core X to native PCL
>-.TP 0.2i
>-\(bu
>-PDF ddx driver that converts core X to native PDF
>-.TP 0.2i
>-\(bu
>-PostScript ddx driver that converts core X to native PostScript
>-.TP 0.2i
>-\(bu
>-Raster ddx driver that generates xwd rasters which can be converted to PCL, PDF or PostScript rasters
>-.PP
>-.PP
>-From an X clients perspective, it can attach to one of two nearly
>-identical X-Servers, a "Video" X-Server, and a "Print" X-Server
>-which has the additional Xp capability but otherwise looks and
>-behaves the same. 
>-.SH "HOW THE X PRINT SERVICE WORKS"
>-The X Print Service expands on the traditional X-Server and Xlib world
>-in four ways.
>-.TP 0.4i
>-1.
>-Most obvious is the use of "print ddx drivers" instead of
>-"video ddx drivers". While a video ddx driver modifies pixels
>-in a video frame buffer, a print ddx driver generates "page
>-description language (PDL)" output (such as PCL, PDF or PostScript)
>-or sends the print rendering instructions to a platform-specific
>-print API (like Win32/GDI).
>-
>-Once a print ddx driver generates PDL output, it can be sent to
>-a spooler such as \fBlp\fR(1)
>-or retrieved by the client (to implement functionality like "print-to-file").
>-
>-Though not currently done, a single X-Server can support both
>-print and video ddx drivers.
>-.TP 0.4i
>-2.
>-Since printers support "paged" output, unlike video, a portion
>-of the Xp Extension supports APIs to delineate printed output.
>-For example, XpStartPage and XpEndPage tell the X-Server where
>-a physical page starts and ends in an otherwise continuous
>-stream of X rendering primitives. Likewise, XpStartJob and
>-XpEndJob determine when a collection of pages starts and ends.
>-XpEndJob typically causes the generated PDL to be submitted to
>-a spooler, such as \fBlp\fR(1).
>-.TP 0.4i
>-3.
>-Since printers have extensive capabilities, another portion of
>-the Xp Extension supports APIs to manipulate "print contexts".
>-
>-Once a printer is selected using the Xp Extension API, a print
>-context to represent it can be created. A print context
>-embodies the printer selected - it contains the printer's
>-default capabilities, selectable range of capabilities,
>-printer state, and generated output. Some "attributes" within
>-the print context can be modified by the user, and the
>-X-Server and print ddx driver will react accordingly. For
>-example, the attribute "content-orientation" can be set to
>-"landscape" or "portrait" (if the printer supports these 
>-values - which can be queried using the Xprint API as well).
>-.TP 0.4i
>-4.
>-Since printers can have "built in" fonts, the Xp Extension in
>-the X-Server works with the print ddx drivers to make
>-available (for printing only) additional fonts on a per print
>-context basis.
>-
>-When a print context is created and set for a given printer,
>-the X font calls may be able to access additional printer
>-fonts. To do this (typically), the X-Server must have access
>-to "printer metric files" (.pmf) that describe at minimum the
>-metrics of the built in fonts.
>-.PP
>-.SH USAGE
>-There are three tasks to start the X Print Service:
>-.TP 0.4i
>-1.
>-configuring the X Print Server,
>-.TP 0.4i
>-2.
>-starting the X Print Service
>-.TP 0.4i
>-3.
>-configuring the user session so that clients can find the running X Print Service
>-.PP
>-.PP
>-The tasks are described in detail below.
>-.SH "SERVER CONFIGURATION"
>-The X Print Server (Xprt) can read a number of configuration files which
>-control its behavior and support for printers. Each vendor platform has
>-a default location for this information. Xprt can also read the
>-environment variable \fBXPCONFIGDIR\fR to locate alternate configuration
>-directories. Common settings include:
>-
>-export XPCONFIGDIR=/X11/lib/X11/XpConfig/
>-.PP
>-export XPCONFIGDIR=/proj/x11/xc/programs/Xserver/XpConfig/
>-
>-.PP
>-Xprt has many built-in defaults, and lacking any configuration files,
>-will immediately try to support all printers visible via \fBlpstat\fR(1).
>-.PP
>-In order of importance for configuration by a system administrator, the
>-configuration files for a "C" locale are as follows (see \fBXprt\fR(__appmansuffix__) for more
>-details (including support for non-"C" locales)):
>-.TP 
>-\fB${XPCONFIGDIR}/C/print/Xprinters\fR
>-\&'Xprinters' is the top most configuration file. It tells
>-Xprt which specific printer names (e.g. mylaser) should
>-be supported, and whether \fBlpstat\fR(1) or other commands
>-should be used to automatically supplement the list of
>-printers.
>-.TP 
>-\fB${XPCONFIGDIR}/C/print/attributes/printer\fR
>-The 'printer' file maps printer names to model
>-configurations (see 'model-config' below). For example,
>-"mylaser" could be mapped to a "HPDJ1600C", and all other
>-arbitrary printers could be mapped to a default, such as
>-"HPLJ4SI". When depending on \fBlpstat\fR(1) in the Xprinters
>-file, setting up defaults in 'printer' becomes all the
>-more important.
>-.TP 
>-\fB${XPCONFIGDIR}/C/print/attributes/document\fR
>-The 'document' file specifies the initial document values
>-for any print jobs. For example, which paper tray to
>-use, what default resolution, etc.
>-.TP 
>-\fB${XPCONFIGDIR}/C/print/attributes/job\fR
>-The 'job' file specifies the initial job values for any
>-print jobs. For example, "notification-profile" can be
>-set so that when a print job is successfully sent to a
>-printer, e-mail is sent to the user.
>-.TP 
>-\fB${XPCONFIGDIR}/C/print/models/PSdefault/model\-config\fR, \fB${XPCONFIGDIR}/C/print/models/PSdefault/fonts/fonts.dir\fR, \fB${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00051.pmf\fR, \fB${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00093.pmf\fR
>-The 'model-config' file has attributes that describe the
>-printer model\(cqs capabilities and default settings.
>-Printer model fonts may also be present. The model-config
>-file also identifies the print ddx driver to be used.
>-For each printer model supported, a complete hierarchy of
>-files should exist. In most cases, these files do not
>-need to be modified.
>-.TP 
>-\fB${XPCONFIGDIR}/C/print/ddx\-config/raster/pcl\fR, \fB${XPCONFIGDIR}/C/print/ddx\-config/raster/pdf\fR, \fB${XPCONFIGDIR}/C/print/ddx\-config/raster/postscript\fR
>-The print ddx drivers can have highly specific
>-configuration files to control their behavior. In most
>-cases, these files do not need to be modified.
>-.PP
>-More information in how to configure and customize the X print server can be found in the
>-\fBXprt\fR(__appmansuffix__)
>-manual page.
>-.SH "STARTING UP"
>-The summary checklist for starting the X Print Service is as follows:
>-.TP 0.4i
>-1.
>-Choose an execution model for the X Print Service. The X
>-Print Service can be run on a per-user session basis, per
>-machine basis, or can be run on a few machines globally
>-available to a number of users.
>-.TP 0.4i
>-2.
>-If print jobs are to be submitted to a spooler (almost always
>-the case), make sure all needed printers are available to the
>-spooler subsystem (most often \fBlp\fR(1))
>-on the same machine running the X Print Service.
>-.TP 0.4i
>-3.
>-Configure the X Print Server. See ``X Print Server
>-Configuration''.
>-.TP 0.4i
>-4.
>-Depending on #1, start the X Print Server process "Xprt", and
>-then the toolkit-specific Print Dialog Manager Daemon process
>-(such as CDEnext's "dtpdmd") at the appropriate times.
>-Note that libXprintUtils-based applications/toolkits do not need
>-a Print Dialog Manager Daemon process to use Xprint.
>-.PP
>-The details are described below.
>-.PP
>-Because the X Print Service is based on X, it can be easily distributed.
>-The most significant factors in which execution model to choose will be
>-driven by:
>-.TP 0.2i
>-\(bu
>-how many printers will be accessable through the printer
>-subsystem on any given machine. A system administrator may
>-choose to cluster printers on a few given machines, or
>-scatter them across an organization and possibly make
>-extensive use of remote spoolers to make them globally
>-available.
>-.TP 0.2i
>-\(bu
>-how many machines will need a copy of the X Print Server
>-configuration files. The files have been architected so
>-that one super-set version of them can be maintained and
>-distributed (e.g. via NFS), and a per-machine or per-user
>-version of the `Xprinters' is all that is needed to have the
>-appropriate information in them utilized or ignored.
>-.TP 0.2i
>-\(bu
>-how many users can demand services from a given X Print
>-Service.
>-.PP
>-With the above in mind, some obvious execution models include:
>-.TP 0.2i
>-\(bu
>-Global - in this model, the system administrator is choosing
>-to run the X Print Service on a *few* select machines with
>-appropriate printers configured, and allow clients access to
>-the global resource. This can centralize the administration
>-of printers and configuration files, but may have to be
>-monitored for performance loading.
>-
>-Startup would likely be done by boot-up scripts (such as \fB/etc/init.d/xprint\fR).
>-.TP 0.2i
>-\(bu
>-Per-machine - every machine with potential X Print Service
>-users would run the service. Printer and configuration file
>-administration is decentralized, and usage would be limited
>-to the users on the machine.
>-
>-Startup would likely be done by boot-up scripts (such as \fB/etc/init.d/xprint\fR).
>-.TP 0.2i
>-\(bu
>-Per-user session - every user would run an entire X Print
>-Service for themselves. In the future, the Video X Server
>-normally started may contain Print X Server capability, so
>-this model becomes very natural.
>-
>-Startup would likely be done at session login or by
>-launching actions or processes manually once the user
>-logs in. Note: Deamons like "dtpdmd" must be started after Xprt.
>-.PP
>-.PP
>-Starting of the processes is straight forward. In strict order (example is for manually starting the X print server for CDEnext usage):
>-.TP 0.4i
>-1.
>-
>-.nf
>-[machineA] % Xprt [\-XpFile <Xprinters file>] [:dispNum] &
>-.fi
>-
>-
>-Note that Xprt will look for configuration files in either
>-a default location or where \fBXPCONFIGDIR\fR points.
>-
>-\fB\-XpFile\fR specifies an alternate `Xprinters' file, rather
>-than the default one or `\fB${XPCONFIGDIR}/C/print/Xprinters\fR'.
>-.TP 0.4i
>-2.
>-
>-.nf
>-[machineA] % dtpdmd \-d machineA[:dispNum] [\-l /tmp/dtpdmd.log] &
>-.fi
>-
>-
>-The dtpdmd will maintain an X-Selection on the X-Server,
>-and will start dtpdm's as required to service requests.
>-.PP
>-.PP
>-In all but the per-user session model, the machine running the dtpdmd
>-(thus dtpdm's) will need display authorization to the users video
>-display.
>-.SH "CLIENT CONFIGURATION"
>-Once a X Print Server and dtpdmd have been started -- many of them
>-in some cases -- clients will need to find and use them. There are
>-two mechanisms that allow clients to discover X Print Servers and
>-printers.
>-.TP 0.2i
>-\(bu
>-"X Print Specifier" - assuming usage of the DtPrint/XprintUtils-based print
>-applications, the following notation is understood:
>-
>-
>-.nf
>-printer_name@machine[:dispNum]
>-.fi
>-
>-
>-For example:
>-
>-
>-.nf
>-colorlj7@printhub:2
>-.fi
>-
>-
>-In the above example, the X Print Server running at `printhub:2'
>-is assumed to support the printer named `colorlj7'.
>-.TP 0.2i
>-\(bu
>-\fB${XPSERVERLIST}\fR - assuming usage of the DtPrint print dialogs,
>-the environment variable \fB${XPSERVERLIST}\fR can contain a list
>-of X Print Servers. For example:
>-
>-
>-.nf
>-XPSERVERLIST="printhub:2 printhub:3 otherdept:0"
>-.fi
>-
>-
>-Then in the dialogs, only a printer name needs to be entered.
>-The dialog will then search the X Print Servers in \fB${XPSERVERLIST}\fR
>-for a server than supports the printer, and then establish
>-contact.
>-.PP
>-.SH "END-USER SEQUENCE"
>-From most CDEnext applications, printing is accomplished by bringing
>-down the <File> menu and selecting <Print...>. This will result in
>-the DtPrintSetupBox dialog, which will request the name of a printer,
>-and offer limited capability to configure print options (e.g. number
>-of copies). If the user wishes, they can select <Setup...>, which
>-will start a dtpdm capable of modifying additional print options.
>-Finally, the user should select <Print>.
>-.SH ENVIRONMENT
>-.TP 
>-\fB${XPCONFIGDIR}\fR
>-This environment variable points to the root
>-of the Xprint server configuration directory hierarchy.
>-If the variable is not defined, the default
>-path is be assumed. The default path may be
>-\fB/usr/X11R6/lib/X11/xserver/\fR, 
>-\fB/usr/lib/X11/xserver/\fR,
>-\fB/usr/share/Xprint/xserver/\fR or
>-\fB/usr/openwin/server/etc/XpConfig\fR, depending on the
>-system, and may be configured in \fB/etc/init.d/xprint\fR.
>-.TP 
>-\fB${LANG}\fR
>-This environment variable selects the locale settings used by the Xprint server.
>-Xprt allows language-specific settings (stored in \fB${XPCONFIGDIR}/${LANG}/print/\fR)
>-which will override the default settings (stored in \fB${XPCONFIGDIR}/C/print/\fR).
>-If \fB${LANG}\fR is not set "C" is assumed.
>-.TP 
>-\fB${XPSERVERLIST}\fR
>-The environment variable \fB${XPSERVERLIST}\fR contains a list
>-of display identifiers (separated by whitespace) which tell an
>-application where it can find the Xprint servers. Usually
>-\fB${XPSERVERLIST}\fR is set by the profile startup scripts (e.g.
>-\fB/etc/profile\fR or \fB/etc/profile.d/xprint.sh\fR) using the output of
>-\fB/etc/init.d/xprint get_xpserverlist\fR.
>-
>-Example: 
>-
>-.nf
>-
>-		export XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`"
>-.fi
>-
>-
>-Alternatively \fB${XPSERVERLIST}\fR can be set
>-manually. Example:
>-
>-.nf
>-
>-		export XPSERVERLIST="littlecat:80 bitdog:72"
>-.fi
>-
>-instructs an application to find an Xprint server at display
>-80 on the machine "littlecat" and at display 72 on the
>-machine bigdog.
>-.TP 
>-\fB${XPRINTER}\fR 
>-The environment variable \fB${XPRINTER}\fR
>-defines the default printer used by print
>-applications. The syntax is either
>-\fIprintername\fR or
>-\fIprintername\fR@\fIdisplay\fR.
>-
>-Examples:
>-.RS 
>-.TP 
>-\fBXPRINTER=ps003\fR
>-tells an application to look for the
>-first printer named "ps003" on all Xprint
>-servers.
>-.TP 
>-\fBXPRINTER=hplaser19@littlecat:80\fR
>-tells an application to use the printer "hplaser19"
>-on the Xprint server at display 
>-"littlecat:80".
>-.RE
>-
>-
>-If \fB${XPRINTER}\fR is not set the applications
>-will examine the values of the \fB${PDPRINTER}\fR,
>-\fB${LPDEST}\fR, and 
>-\fB${PRINTER}\fR environment variables (in that order). 
>-.SH "SEE ALSO"
>-\fBX11\fR(__miscmansuffix__), \fBxplsprinters\fR(__appmansuffix__), \fBxprehashprinterlist\fR(__appmansuffix__), \fBxphelloworld\fR(__appmansuffix__), \fBxpxmhelloworld\fR(__appmansuffix__), \fBxpawhelloworld\fR(__appmansuffix__), \fBxpxthelloworld\fR(__appmansuffix__), \fBxpsimplehelloworld\fR(__appmansuffix__), \fBXserver\fR(__appmansuffix__), \fBXprt\fR(__appmansuffix__), \fBlibXp\fR(__libmansuffix__), \fBlibXprintUtils\fR(__libmansuffix__), \fBlibXprintAppUtils\fR(__libmansuffix__), \fBXmPrintShell\fR(__libmansuffix__), \fBXawPrintShell\fR(__libmansuffix__), Xprint FAQ (http://xprint.mozdev.org/docs/Xprint_FAQ.html), Xprint main site (http://xprint.mozdev.org/)
>-.SH AUTHORS
>-This manual page was written by 
>-Roland Mainz <roland.mainz@nrubsig.org> based on the original X11R6.6
>-\fBxc/programs/Xserver/XpConfig/README\fR.
>Index: xc/programs/Xserver/Xprint/Xprint.sgml
>===================================================================
>RCS file: xc/programs/Xserver/Xprint/Xprint.sgml
>diff -N xc/programs/Xserver/Xprint/Xprint.sgml
>--- xc/programs/Xserver/Xprint/Xprint.sgml	8 Oct 2004 02:39:40 -0000	1.4
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,627 +0,0 @@
>-<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.2//EN" 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd'>
>-
>-
>-
>-<refentry id="Xprint">
>-  <refmeta>
>-    <refentrytitle>Xprint</refentrytitle>
>-    <manvolnum>__miscmansuffix__</manvolnum>
>-  </refmeta>
>-  <refnamediv>
>-    <refname>Xprint</refname>
>-
>-    <refpurpose>The "X print service" - a portable, network-transparent printing system based on the X11 protocol</refpurpose>
>-  </refnamediv>
>-  <refsynopsisdiv>
>-    <para>Xprint is a very flexible, extensible, scaleable, client/server
>-     print system based on ISO 10175 (and some other specs) and the X11        
>-     rendering protocol.                                                       
>-     Using Xprint an application can search, query and use devices like        
>-     printers, FAX machines or create documents in formats like PDF.           
>-     In particular, an application can seek a printer, query supported         
>-     attributes (like paper size, trays, fonts etc.), configure the printer    
>-     device to match it&rsquo;s needs and print on it like on any other X device     
>-     reusing parts of the code which is used for the video card Xserver.    
>-    </para>
>-  </refsynopsisdiv>
>-  
>-  <refsect1>
>-    <title>OVERVIEW</title>
>-    <para>
>-      The "X Print Service" technology allows X rendering to devices such as
>-      printers and fax.  Most of the service is available in the X11
>-      technology stack as Xp, with the remainder in single toolkit stacks (e.g. DtPrint for CDE).
>-      Modifications have also been made to the LessTif/Motif/Qt technology
>-      stacks to support Xprint.
>-    </para>
>-    <para>
>-      The Xp portion consists of:
>-      <itemizedlist>
>-        <listitem><para>Xp Extension for the X-Server (included in the X-Server Xprt)</para></listitem>
>-        <listitem><para>Xp Extension API for the client side (libXp/libXprintUtils)</para></listitem>
>-        <listitem><para>PCL ddx driver that converts core X to native PCL</para></listitem>
>-        <listitem><para>PDF ddx driver that converts core X to native PDF</para></listitem>
>-        <listitem><para>PostScript ddx driver that converts core X to native PostScript</para></listitem>
>-        <listitem><para>Raster ddx driver that generates xwd rasters which can be converted to PCL, PDF or PostScript rasters</para></listitem>
>-      </itemizedlist>
>-    </para>
>-    <para>
>-      From an X clients perspective, it can attach to one of two nearly
>-      identical X-Servers, a "Video" X-Server, and a "Print" X-Server
>-      which has the additional Xp capability but otherwise looks and
>-      behaves the same.   
>-    </para>
>-  </refsect1>
>-
>-  <refsect1>
>-    <title>HOW THE X PRINT SERVICE WORKS</title>
>-    <para>    
>-      The X Print Service expands on the traditional X-Server and Xlib world
>-      in four ways.
>-
>-      <orderedlist>
>-        <listitem>
>-          <para>
>-            Most obvious is the use of "print ddx drivers" instead of
>-            "video ddx drivers".  While a video ddx driver modifies pixels
>-            in a video frame buffer, a print ddx driver generates "page
>-            description language (PDL)" output (such as PCL, PDF or PostScript)
>-            or sends the print rendering instructions to a platform-specific
>-            print API (like Win32/GDI).
>-          </para>
>-          <para>
>-            Once a print ddx driver generates PDL output, it can be sent to
>-            a spooler such as <citerefentry><refentrytitle>lp</refentrytitle><manvolnum>1</manvolnum></citerefentry>
>-            or retrieved by the client (to implement functionality like "print-to-file").
>-          </para>
>-          <para>
>-            Though not currently done, a single X-Server can support both
>-            print and video ddx drivers.
>-            
>-          </para>
>-        </listitem>
>-        <listitem>
>-          <para>
>-            Since printers support "paged" output, unlike video, a portion
>-            of the Xp Extension supports APIs to delineate printed output.
>-            For example, <function>XpStartPage</function> and <function>XpEndPage</function> tell the X-Server where
>-            a physical page starts and ends in an otherwise continuous
>-            stream of X rendering primitives.  Likewise, <function>XpStartJob</function> and
>-            <function>XpEndJob</function> determine when a collection of pages starts and ends.
>-            <function>XpEndJob</function> typically causes the generated PDL to be submitted to
>-            a spooler, such as <citerefentry><refentrytitle>lp</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
>-          </para>
>-        </listitem>
>-        <listitem>
>-          <para>
>-            Since printers have extensive capabilities, another portion of
>-            the Xp Extension supports APIs to manipulate "print contexts".
>-          </para>
>-          <para>
>-            Once a printer is selected using the Xp Extension API, a print
>-            context to represent it can be created.  A print context
>-            embodies the printer selected - it contains the printer's
>-            default capabilities, selectable range of capabilities,
>-            printer state, and generated output.  Some "attributes" within
>-            the print context can be modified by the user, and the
>-            X-Server and print ddx driver will react accordingly.  For
>-            example, the attribute "content-orientation" can be set to
>-            "landscape" or "portrait" (if the printer supports these 
>-            values - which can be queried using the Xprint API as well).
>-          </para>
>-        </listitem>
>-        <listitem>
>-          <para>
>-            Since printers can have "built in" fonts, the Xp Extension in
>-            the X-Server works with the print ddx drivers to make
>-            available (for printing only) additional fonts on a per print
>-            context basis.
>-          </para>
>-          <para>
>-            When a print context is created and set for a given printer,
>-            the X font calls may be able to access additional printer
>-            fonts.  To do this (typically), the X-Server must have access
>-            to "printer metric files" (.pmf) that describe at minimum the
>-            metrics of the built in fonts.
>-          </para>
>-        </listitem>
>-      </orderedlist>
>-    </para>
>-  </refsect1>
>-
>-  <refsect1>
>-    <title>USAGE</title>
>-    <para>    
>-      There are three tasks to start the X Print Service:
>-      <orderedlist>
>-        <listitem><para>configuring the X Print Server,</para></listitem>
>-        <listitem><para>starting the X Print Service</para></listitem>
>-        <listitem><para>configuring the user session so that clients can find the running X Print Service</para></listitem>
>-      </orderedlist>
>-    </para>
>-    <para>
>-      The tasks are described in detail below.
>-    </para>
>-  </refsect1>
>-
>-  <refsect1>
>-    <title>SERVER CONFIGURATION</title>
>-    <para>
>-      The X Print Server (Xprt) can read a number of configuration files which
>-      control its behavior and support for printers.  Each vendor platform has
>-      a default location for this information.  Xprt can also read the
>-      environment variable <envar>XPCONFIGDIR</envar> to locate alternate configuration
>-      directories.  Common settings include:
>-
>-      <simplelist type="vert">
>-        <member>export XPCONFIGDIR=/X11/lib/X11/XpConfig/</member>
>-        <member>export XPCONFIGDIR=/proj/x11/xc/programs/Xserver/XpConfig/</member>
>-      </simplelist>
>-    </para>
>-    <para>
>-      Xprt has many built-in defaults, and lacking any configuration files,
>-      will immediately try to support all printers visible via <citerefentry><refentrytitle>lpstat</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
>-    </para>
>-    <para>
>-      In order of importance for configuration by a system administrator, the
>-      configuration files for a "C" locale are as follows (see <citerefentry><refentrytitle>Xprt</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry> for more
>-      details (including support for non-"C" locales)):
>-      <variablelist>
>-        <varlistentry>
>-          <term><filename>${XPCONFIGDIR}/C/print/Xprinters</filename></term>
>-          <listitem>
>-            <para>
>-              'Xprinters' is the top most configuration file.  It tells
>-              Xprt which specific printer names (e.g.  mylaser) should
>-              be supported, and whether <citerefentry><refentrytitle>lpstat</refentrytitle><manvolnum>1</manvolnum></citerefentry> or other commands
>-              should be used to automatically supplement the list of
>-              printers.
>-            </para>
>-          </listitem>
>-        </varlistentry>
>-
>-        <varlistentry>
>-          <term><filename>${XPCONFIGDIR}/C/print/attributes/printer</filename></term>
>-          <listitem>
>-            <para>
>-              The 'printer' file maps printer names to model
>-              configurations (see 'model-config' below).  For example,
>-              "mylaser" could be mapped to a "HPDJ1600C", and all other
>-              arbitrary printers could be mapped to a default, such as
>-              "HPLJ4SI".  When depending on <citerefentry><refentrytitle>lpstat</refentrytitle><manvolnum>1</manvolnum></citerefentry> in the Xprinters
>-              file, setting up defaults in 'printer' becomes all the
>-              more important.
>-            </para>
>-          </listitem>
>-        </varlistentry>
>-
>-        <varlistentry>
>-          <term><filename>${XPCONFIGDIR}/C/print/attributes/document</filename></term>
>-          <listitem>
>-            <para>
>-              The 'document' file specifies the initial document values
>-              for any print jobs.  For example, which paper tray to
>-              use, what default resolution, etc.
>-            </para>
>-          </listitem>
>-        </varlistentry>
>-
>-        <varlistentry>
>-          <term><filename>${XPCONFIGDIR}/C/print/attributes/job</filename></term>
>-          <listitem>
>-            <para>
>-              The 'job' file specifies the initial job values for any
>-              print jobs.  For example, "notification-profile" can be
>-              set so that when a print job is successfully sent to a
>-              printer, e-mail is sent to the user.
>-            </para>
>-          </listitem>
>-        </varlistentry>
>-
>-        <varlistentry>
>-          <term><filename>${XPCONFIGDIR}/C/print/models/PSdefault/model-config</filename></term>
>-          <term><filename>${XPCONFIGDIR}/C/print/models/PSdefault/fonts/fonts.dir</filename></term>
>-          <term><filename>${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00051.pmf</filename></term>
>-          <term><filename>${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00093.pmf</filename></term>
>-
>-          <listitem>
>-            <para>
>-              The 'model-config' file has attributes that describe the
>-              printer model&rsquo;s capabilities and default settings.
>-              Printer model fonts may also be present.  The model-config
>-              file also identifies the print ddx driver to be used.
>-
>-              For each printer model supported, a complete hierarchy of
>-              files should exist.  In most cases, these files do not
>-              need to be modified.
>-            </para>
>-          </listitem>
>-        </varlistentry>
>-
>-        <varlistentry>
>-          <term><filename>${XPCONFIGDIR}/C/print/ddx-config/raster/pcl</filename></term>
>-          <term><filename>${XPCONFIGDIR}/C/print/ddx-config/raster/pdf</filename></term>
>-          <term><filename>${XPCONFIGDIR}/C/print/ddx-config/raster/postscript</filename></term>
>-
>-          <listitem>
>-            <para>
>-              The print ddx drivers can have highly specific
>-              configuration files to control their behavior.  In most
>-              cases, these files do not need to be modified.
>-            </para>
>-          </listitem>
>-        </varlistentry>
>-      </variablelist>
>-      
>-      More information in how to configure and customize the X print server can be found in the
>-      <citerefentry><refentrytitle>Xprt</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry>
>-      manual page.
>-    </para>
>-  </refsect1>
>-
>-  <refsect1>
>-    <title>STARTING UP</title>
>-    <para>
>-      The summary checklist for starting the X Print Service is as follows:
>-      
>-      <orderedlist>
>-        <listitem>
>-          <para>
>-            Choose an execution model for the X Print Service.  The X
>-            Print Service can be run on a per-user session basis, per
>-            machine basis, or can be run on a few machines globally
>-            available to a number of users.
>-          </para>
>-        </listitem>
>-        <listitem>
>-          <para>
>-            If print jobs are to be submitted to a spooler (almost always
>-            the case), make sure all needed printers are available to the
>-            spooler subsystem (most often <citerefentry><refentrytitle>lp</refentrytitle><manvolnum>1</manvolnum></citerefentry>)
>-            on the same machine running the X Print Service.
>-          </para>
>-        </listitem>
>-        <listitem>
>-          <para>
>-            Configure the X Print Server.  See ``X Print Server
>-            Configuration''.
>-          </para>
>-        </listitem>
>-        <listitem>
>-          <para>
>-            Depending on #1, start the X Print Server process "Xprt", and
>-            then the toolkit-specific Print Dialog Manager Daemon process
>-            (such as CDEnext's "dtpdmd") at the appropriate times.
>-            Note that libXprintUtils-based applications/toolkits do not need
>-            a Print Dialog Manager Daemon process to use Xprint.
>-          </para>
>-        </listitem>
>-      </orderedlist>     
>-      The details are described below.
>-    </para>
>-    <para>
>-      Because the X Print Service is based on X, it can be easily distributed.
>-      The most significant factors in which execution model to choose will be
>-      driven by:
>-      <itemizedlist>
>-        <listitem>
>-          <para>
>-            how many printers will be accessable through the printer
>-            subsystem on any given machine.  A system administrator may
>-            choose to cluster printers on a few given machines, or
>-            scatter them across an organization and possibly make
>-            extensive use of remote spoolers to make them globally
>-            available.
>-          </para>
>-        </listitem>
>-        <listitem>
>-          <para>
>-            how many machines will need a copy of the X Print Server
>-            configuration files.  The files have been architected so
>-            that one super-set version of them can be maintained and
>-            distributed (e.g.  via NFS), and a per-machine or per-user
>-            version of the `Xprinters' is all that is needed to have the
>-            appropriate information in them utilized or ignored.
>-          </para>
>-        </listitem>
>-        <listitem>
>-          <para>
>-            how many users can demand services from a given X Print
>-            Service.
>-          </para>
>-        </listitem>
>-      </itemizedlist>
>-
>-      With the above in mind, some obvious execution models include:
>-      <itemizedlist>
>-        <listitem>
>-          <para>
>-            Global - in this model, the system administrator is choosing
>-            to run the X Print Service on a *few* select machines with
>-            appropriate printers configured, and allow clients access to
>-            the global resource.  This can centralize the administration
>-            of printers and configuration files, but may have to be
>-            monitored for performance loading.
>-          </para>
>-          <para>
>-            Startup would likely be done by boot-up scripts (such as <filename>/etc/init.d/xprint</filename>).
>-          </para>
>-        </listitem>
>-
>-        <listitem>
>-          <para>
>-            Per-machine - every machine with potential X Print Service
>-            users would run the service.  Printer and configuration file
>-            administration is decentralized, and usage would be limited
>-            to the users on the machine.
>-          </para>
>-          <para>
>-            Startup would likely be done by boot-up scripts (such as <filename>/etc/init.d/xprint</filename>).
>-          </para>
>-        </listitem>
>-
>-        <listitem>
>-          <para>
>-            Per-user session - every user would run an entire X Print
>-            Service for themselves.  In the future, the Video X Server
>-            normally started may contain Print X Server capability, so
>-            this model becomes very natural.
>-          </para>
>-          <para>
>-            Startup would likely be done at session login or by
>-            launching actions or processes manually once the user
>-            logs in.  Note: Deamons like "dtpdmd" must be started after Xprt.
>-          </para>
>-        </listitem>
>-      </itemizedlist>
>-     </para>
>-     <para>
>-       Starting of the processes is straight forward.  In strict order (example is for manually starting the X print server for CDEnext usage):
>-       <orderedlist>
>-         <listitem>
>-           <para>
>-             <programlisting>[machineA] % Xprt [-XpFile &lt;Xprinters file&gt;] [:dispNum] &amp;</programlisting>
>-           </para>
>-           <para>
>-             Note that Xprt will look for configuration files in either
>-             a default location or where <envar>XPCONFIGDIR</envar> points.
>-           </para>
>-           <para>
>-             <option>-XpFile</option> specifies an alternate `Xprinters' file, rather
>-             than the default one or `<filename>${XPCONFIGDIR}/C/print/Xprinters</filename>'.
>-           </para>
>-         </listitem>
>-         <listitem>
>-           <para>
>-             <programlisting>[machineA] % dtpdmd -d machineA[:dispNum] [-l /tmp/dtpdmd.log] &amp;</programlisting>
>-           </para>
>-           <para>
>-            The dtpdmd will maintain an X-Selection on the X-Server,
>-            and will start dtpdm's as required to service requests.
>-           </para>
>-         </listitem>
>-       </orderedlist>
>-     </para>
>-     <para>
>-       In all but the per-user session model, the machine running the dtpdmd
>-       (thus dtpdm's) will need display authorization to the users video
>-       display.
>-    </para>
>-  </refsect1>
>-
>-  <refsect1>
>-    <title>CLIENT CONFIGURATION</title>
>-    <para>
>-      Once a X Print Server and dtpdmd have been started -- many of them
>-      in some cases -- clients will need to find and use them.  There are
>-      two mechanisms that allow clients to discover X Print Servers and
>-      printers.
>-
>-      <itemizedlist>
>-        <listitem>
>-          <para>
>-            "X Print Specifier" - assuming usage of the DtPrint/XprintUtils-based print
>-            applications, the following notation is understood:
>-          </para>
>-          <para>
>-            <programlisting>printer_name@machine[:dispNum]</programlisting>
>-          </para>
>-          <para>
>-            For example:
>-          </para>
>-          <para>
>-            <programlisting>colorlj7@printhub:2</programlisting>
>-          </para>
>-          <para>
>-           In the above example, the X Print Server running at `printhub:2'
>-           is assumed to support the printer named `colorlj7'.
>-          </para>
>-        </listitem>
>-        <listitem>
>-          <para>
>-            <envar>${XPSERVERLIST}</envar> - assuming usage of the DtPrint print dialogs,
>-            the environment variable <envar>${XPSERVERLIST}</envar> can contain a list
>-            of X Print Servers.  For example:
>-          </para>
>-          <para>
>-            <programlisting>XPSERVERLIST="printhub:2 printhub:3 otherdept:0"</programlisting>
>-          </para>
>-          <para>
>-            Then in the dialogs, only a printer name needs to be entered.
>-            The dialog will then search the X Print Servers in <envar>${XPSERVERLIST}</envar>
>-            for a server than supports the printer, and then establish
>-            contact.
>-          </para>
>-        </listitem>
>-      </itemizedlist>
>-    </para>
>-  </refsect1>
>-
>-  <refsect1>
>-    <title>END-USER SEQUENCE</title>
>-    <para>
>-      From most CDEnext applications, printing is accomplished by bringing
>-      down the &lt;File&gt; menu and selecting &lt;Print...&gt;.  This will result in
>-      the DtPrintSetupBox dialog, which will request the name of a printer,
>-      and offer limited capability to configure print options (e.g. number
>-      of copies).  If the user wishes, they can select &lt;Setup...&gt;, which
>-      will start a dtpdm capable of modifying additional print options.
>-      Finally, the user should select &lt;Print&gt;.
>-    </para>
>-  </refsect1>
>-
>-  <refsect1>
>-    <title>ENVIRONMENT</title>
>-    <variablelist>
>-      <varlistentry>
>-        <term><envar>${XPCONFIGDIR}</envar></term>
>-        <listitem>
>-          <para> This environment variable points to the  root
>-	    of  the Xprint server configuration directory hierarchy.
>-	    If the variable is not defined,  the  default
>-	    path  is be assumed.  The default path may be
>-            <filename>/usr/X11R6/lib/X11/xserver/</filename>, 
>-            <filename>/usr/lib/X11/xserver/</filename>,
>-            <filename>/usr/share/Xprint/xserver/</filename> or
>-            <filename>/usr/openwin/server/etc/XpConfig</filename>, depending on the
>-	    system, and may be configured in <filename>/etc/init.d/xprint</filename>.</para>
>-        </listitem>
>-      </varlistentry>
>-
>-      <varlistentry>
>-        <term><envar>${LANG}</envar></term>
>-        <listitem>
>-          <para>
>-            This environment variable selects the locale settings used by the Xprint server.
>-            Xprt allows language-specific settings (stored in <filename>${XPCONFIGDIR}/${LANG}/print/</filename>)
>-            which will override the default settings (stored in <filename>${XPCONFIGDIR}/C/print/</filename>).
>-            If <envar>${LANG}</envar> is not set "C" is assumed.
>-          </para>
>-        </listitem>
>-      </varlistentry>
>-      
>-      <varlistentry>
>-        <term><envar>${XPSERVERLIST}</envar></term>
>-        <listitem>
>-	    <para>The environment variable <envar>${XPSERVERLIST}</envar> contains a list
>-	    of display identifiers (separated by whitespace) which tell an
>-	    application where it can find the Xprint servers.  Usually
>-	    <envar>${XPSERVERLIST}</envar> is set by the profile startup scripts (e.g.
>-	    <filename>/etc/profile</filename> or <filename>/etc/profile.d/xprint.sh</filename>) using the output of
>-	    <userinput>/etc/init.d/xprint get_xpserverlist</userinput>.</para>
>-	  <para>Example: 
>-	    <informalexample>
>-	      <programlisting>
>-		export XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`"</programlisting>
>-	    </informalexample>
>-	  </para>
>-	  <para>Alternatively <envar>${XPSERVERLIST}</envar> can be set
>-	    manually. Example:</para>
>-	    <informalexample>
>-	      <programlisting>
>-		export XPSERVERLIST="littlecat:80 bitdog:72"</programlisting>
>-	    </informalexample>
>-	  <para>
>-	    instructs an application to find an Xprint server at display
>-	    80 on the machine "littlecat" and at display 72 on the
>-	    machine bigdog.
>-	  </para>
>-	</listitem>
>-      </varlistentry>
>-
>-      <varlistentry>
>-        <term><envar>${XPRINTER}</envar>
>-        </term>
>-        <listitem>
>-          <para>The environment variable <envar>${XPRINTER}</envar>
>-	    defines the default printer used by print
>-	    applications. The syntax is either
>-	    <replaceable>printername</replaceable> or
>-	    <replaceable>printername</replaceable>@<replaceable>display</replaceable>.</para>
>-	    <para>Examples:
>-	    <variablelist>
>-	      <varlistentry>
>-		<term><userinput>XPRINTER=ps003</userinput></term>
>-		<listitem><para>
>-		  tells an application to look for the
>-		  first printer named "ps003" on all Xprint
>-		  servers.</para>
>-		</listitem>
>-	      </varlistentry>
>-	
>-	      <varlistentry>
>-		
>-		<term><userinput>XPRINTER=hplaser19@littlecat:80</userinput></term>
>-		<listitem><para>
>-		  tells an application to use the printer "hplaser19"
>-		on the Xprint server at display 
>-		  "littlecat:80".</para>
>-	      </listitem>
>-	      </varlistentry>
>-
>-	    </variablelist>
>-	  </para>
>-	  <para>If <envar>${XPRINTER}</envar> is not set the applications
>-	    will examine the values of the <envar>${PDPRINTER}</envar>,
>-	    <envar>${LPDEST}</envar>, and 
>-	    <envar>${PRINTER}</envar> environment variables (in that order).  
>-	  </para>
>-        </listitem>
>-      </varlistentry>
>-    </variablelist>
>-  </refsect1>
>-
>-  <refsect1>
>-    <title>SEE ALSO</title>
>-    <para>
>-      <simplelist type="inline">
>-        
>-        
>-        
>-        
>-
>-        <member><citerefentry><refentrytitle>X11</refentrytitle><manvolnum>__miscmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>xplsprinters</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>xprehashprinterlist</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>xphelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>xpxmhelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>xpawhelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>xpxthelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>xpsimplehelloworld</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>Xprt</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry></member>
>-        
>-        <member><citerefentry><refentrytitle>libXp</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>libXprintUtils</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>libXprintAppUtils</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>XmPrintShell</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>-        <member><citerefentry><refentrytitle>XawPrintShell</refentrytitle><manvolnum>__libmansuffix__</manvolnum></citerefentry></member>
>-        <member>Xprint FAQ (<ulink url="http://xprint.mozdev.org/docs/Xprint_FAQ.html">http://xprint.mozdev.org/docs/Xprint_FAQ.html</ulink>)</member>
>-        <member>Xprint main site (<ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink>)</member>
>-      </simplelist>
>-    </para>
>-  </refsect1>
>-
>-  <refsect1>
>-    <title>AUTHORS</title>
>-    <para>
>-      This manual page was written by 
>-      Roland Mainz <email>roland.mainz@nrubsig.org</email> based on the original X11R6.6
>-      <filename>xc/programs/Xserver/XpConfig/README</filename>.
>-    </para>
>-  </refsect1>
>-</refentry>
>-

Flags:

roland.mainz: 6.8-branch+

Actions: View | Splinter Review

Attachments on bug 811: 1374 | 1379 | 1431

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.