Attachment 1558 Details for Bug 1923 – All patches combined (diff between xprint_packagertest_20041125_base and xprint_packagertest_20041125)

[patch] All patches combined (diff between xprint_packagertest_20041125_base and xprint_packagertest_20041125)

xprint_package_branch1.gudiff (text/plain), 250.28 KB, created by Roland Mainz on 2004-12-16 22:12:34 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Roland Mainz

Created: 2004-12-16 22:12:34 UTC

Size: 250.28 KB

patch

obsolete

>diff -N -x '*CVS*' -r -u base/xc/ChangeLog branch/xc/ChangeLog
>--- base/xc/ChangeLog	2004-11-25 23:42:51.000000000 +0100
>+++ branch/xc/ChangeLog	2004-12-05 21:25:55.000000000 +0100
>@@ -1,3 +1,161 @@
>+2004-12-05 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/config/cf/X11.tmpl
>+        * xc/config/cf/xprint_host.def
>+        * xc/lib/X11/Imakefile
>+        Bugzilla #1923 (https://bugs.freedesktop.org/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 12:
>+        FreeBSD build fixes.
>+
>+2004-12-04 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/list_files_not_used_by_xp.ksh
>+        * xc/lib/Imakefile
>+        * xc/lib/X11/Imakefile
>+        Bugzilla #1923 (https://bugs.freedesktop.org/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 11:
>+        Re-add minimum set of libX11 includes required to build the tree
>+        when the build system doesn't have them installed.
>+
>+2004-12-04 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/programs/Xserver/Xprint/ps/PsInit.c
>+        Bugzilla #1800 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1800):
>+        Fix Postscript DDX's 1bit StaticGray visual to report only 1bit
>+        of significant bits in color specification (instead of 8bits).
>+        Patch by Julien Lafon <julien.lafon@gmail.com>
>+
>+2004-12-04 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/packager/rpm/xprint.spec
>+        Bugzilla #1923 (https://bugs.freedesktop.org/show_bug.cgi?id=1923):
>+        Remove old hack for Redhat Linux (platform no longer supported).
>+
>+2004-12-03 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/config/cf/host.def
>+        Bugzilla #1923 (https://bugs.freedesktop.org/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 10:
>+        Removing accidental change to host.def.
>+
>+2004-12-03 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/config/cf/host.def
>+        * xc/config/cf/xprint_host.def
>+        * xc/packager/tarball/Imakefile
>+        Bugzilla #1923 (https://bugs.freedesktop.org/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 10:
>+        Solaris package fixes to find the encoding mapping files
>+        in the correct location (basically a fallout from bug 2002).
>+
>+2004-12-03 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/config/cf/xprint_host.def
>+        * xc/packager/solaris/GISWxprint/README
>+        * xc/packager/solaris/GISWxprint/pkginfo
>+        * xc/packager/solaris/GISWxprintglue/README
>+        * xc/packager/solaris/GISWxprintglue/pkginfo       
>+        Bugzilla #1923 (https://bugs.freedesktop.org/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 9:
>+        Solaris packaging adjustments and README updates.
>+
>+2004-12-02 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/config/cf/X11.tmpl
>+        * xc/lib/font/fontfile/Imakefile 
>+        Bugzilla #2002 (https://freedesktop.org/bugzilla/show_bug.cgi?id=2002):
>+        Make location of the encodings/ files configurable in the build
>+        system via adding a new |FontEncDir|-symbol to xc/config/cf/X11.tmpl
>+        (default value is |$(LIBDIR)/fonts/encodings|).
>+
>+2004-12-02 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/config/cf/xprint_host.def
>+        * xc/packager/tarball/startxprint.sh
>+        Bugzilla #1923 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 8:
>+        Fixing problems with XDMCP code on Solaris and pre-Solaris 10 Motif
>+        bits.
>+
>+2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/packager/rpm/xprint.spec
>+        Bugzilla #1923 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 7:
>+        (Hopefully) final round of RPM build fixes.
>+
>+2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/config/cf/xprint_host.def
>+        * xc/programs/Xserver/miext/damage/damagestr.h
>+        Bugzilla #1923 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1923):
>+        Build fixes for Solaris 8.
>+
>+2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/list_files_not_used_by_xp.ksh
>+        * xc/doc/Imakefile
>+        * xc/doc/man/Imakefile
>+        * 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 #1923 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1923)
>+        and Bugzilla #811 (https://freedesktop.org/bugzilla/show_bug.cgi?id=811):
>+        Fixing build bustage caused by first patch of bug 811.
>+
>+2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/packager/rpm/xprint.spec
>+        Bugzilla #1923 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 4:
>+        Fixing RPM build bustage.
>+
>+2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/list_files_not_used_by_xp.ksh
>+        * xc/packager/rpm/xprint.spec
>+        * xc/packager/rpm/xprint_rpmpackage.patch
>+        Bugzilla #1923 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 3:
>+        Misc fixes (more file stripping and RPM adjustments)
>+
>+2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/list_files_not_used_by_xp.ksh
>+        Bugzilla #1923 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server, part 2:
>+        Adding file stripper script to create a stripped source tarball on
>+        demand.
>+
>+2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>+        * xc/Imakefile
>+        * xc/config/cf/host.def 
>+        * xc/config/cf/xprint_host.def 
>+        * xc/doc/Imakefile
>+        * xc/doc/hardcopy/Imakefile
>+        * xc/fonts/Imakefile
>+        * xc/lib/Imakefile
>+        * xc/packager/Imakefile
>+        * xc/packager/mozilla_xpi/Imakefile
>+        * xc/packager/mozilla_xpi/K98xprint_xpi.sh
>+        * xc/packager/mozilla_xpi/S98xprint_xpi.sh
>+        * xc/packager/mozilla_xpi/install.js
>+        * xc/packager/mozilla_xpi/make_mozilla_xpi.sh
>+        * xc/packager/rpm/Imakefile   
>+        * xc/packager/rpm/xprint.spec 
>+        * xc/packager/rpm/xprint_rpmpackage.patch     
>+        * xc/packager/solaris/Imakefile               
>+        * xc/packager/solaris/GISWxprint/Imakefile    
>+        * xc/packager/solaris/GISWxprint/README       
>+        * xc/packager/solaris/GISWxprint/depend       
>+        * xc/packager/solaris/GISWxprint/pkginfo      
>+        * xc/packager/solaris/GISWxprint/postinstall  
>+        * xc/packager/solaris/GISWxprint/preinstall   
>+        * xc/packager/solaris/GISWxprintglue/Imakefile
>+        * xc/packager/solaris/GISWxprintglue/README   
>+        * xc/packager/solaris/GISWxprintglue/depend   
>+        * xc/packager/solaris/GISWxprintglue/make_solaris_pkg.sh
>+        * xc/packager/solaris/GISWxprintglue/pkginfo    
>+        * xc/packager/solaris/GISWxprintglue/postinstall
>+        * xc/packager/solaris/GISWxprintglue/preinstall
>+        * xc/packager/tarball/Imakefile
>+        * xc/packager/tarball/README_tarball
>+        * xc/packager/tarball/make_xprint_binary_tarball.sh
>+        * xc/packager/tarball/startxprint.sh
>+        * xc/programs/Imakefile
>+        Bugzilla #1923 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1923):
>+        Testing standalone package system for Xprint server.
>+
> 2004-11-25 Roland Mainz <roland.mainz@nrubsig.org>
>         * xc/programs/Xserver/Xprint/Imakefile
>         * xc/programs/Xserver/Xprint/Xprt.html
>@@ -10267,4 +10425,4 @@
>        so i18n libs from build tree get used instead of installed ones
>        (Egbert Eich).
> 
>-$XdotOrg: xc/ChangeLog,v 1.547 2004/11/25 22:42:51 gisburn Exp $
>+$XdotOrg: xc/ChangeLog,v 1.547.2.16 2004/12/05 20:25:55 gisburn Exp $
>diff -N -x '*CVS*' -r -u base/xc/Imakefile branch/xc/Imakefile
>--- base/xc/Imakefile	2004-11-15 16:06:43.000000000 +0100
>+++ branch/xc/Imakefile	2004-11-26 04:29:50.000000000 +0100
>@@ -27,7 +27,7 @@
> #endif
> 
>         SUBDIRS = include config lib $(NLSSUBDIR) \
>-                  programs $(FONTSDIR) $(DOCSDIR)
>+                  programs $(FONTSDIR) $(DOCSDIR) packager
>   LNINSTALLDIRS = lib
> 
> #if HasParallelMake
>diff -N -x '*CVS*' -r -u base/xc/config/cf/X11.tmpl branch/xc/config/cf/X11.tmpl
>--- base/xc/config/cf/X11.tmpl	2004-10-30 03:41:46.000000000 +0200
>+++ branch/xc/config/cf/X11.tmpl	2004-12-05 21:25:56.000000000 +0100
>@@ -1,6 +1,6 @@
> XCOMM ----------------------------------------------------------------------
> XCOMM X Window System Build Parameters and Rules
>-XCOMM $XdotOrg: xc/config/cf/X11.tmpl,v 1.37 2004/10/30 01:41:46 torrey Exp $
>+XCOMM $XdotOrg: xc/config/cf/X11.tmpl,v 1.37.2.2 2004/12/05 20:25:56 gisburn Exp $
> XCOMM $Xorg: X11.tmpl,v 1.6 2000/08/17 19:41:46 cpqbld Exp $
> XCOMM
> XCOMM
>@@ -1513,6 +1513,9 @@
> #ifndef FontDir
> #define FontDir $(LIBDIR)/fonts
> #endif
>+#ifndef FontEncDir
>+#define FontEncDir $(LIBDIR)/fonts/encodings
>+#endif
> #ifndef AdmDir
> #define AdmDir /usr/adm
> #endif
>@@ -1680,7 +1683,7 @@
>          DOCPSDIR = DocPsDir
>         DOCPDFDIR = DocPdfDir
>           FONTDIR = FontDir		/* font directories */
>-     ENCODINGSDIR = $(FONTDIR)/encodings /* font encodings directory */
>+     ENCODINGSDIR = FontEncDir          /* font encodings directory */
>          XINITDIR = XinitDir		/* xinit config files */
>            XDMDIR = XdmDir		/* xdm config files */
>         XDMVARDIR = XdmVarDir		/* xdm config files */
>@@ -4768,7 +4771,7 @@
> 	@$(RM) __tmp1__ __tmp2__
> #endif
> 
>-#if !HasFreetype2
>+#if !HasFreetype2 && SharedLibFreetype2
>       FT2PRELOADPATTERN = libfreetype.so.?
> #endif
> #if !HasFontconfig
>diff -N -x '*CVS*' -r -u base/xc/config/cf/host.def branch/xc/config/cf/host.def
>--- base/xc/config/cf/host.def	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/config/cf/host.def	2004-12-04 03:24:03.000000000 +0100
>@@ -0,0 +1,4 @@
>+
>+/* lame hack, in theory the build script should symlink the file :-) */
>+#include "xprint_host.def"
>+
>diff -N -x '*CVS*' -r -u base/xc/config/cf/xprint_host.def branch/xc/config/cf/xprint_host.def
>--- base/xc/config/cf/xprint_host.def	2004-11-25 22:46:11.000000000 +0100
>+++ branch/xc/config/cf/xprint_host.def	2004-12-05 21:25:56.000000000 +0100
>@@ -110,6 +110,8 @@
> /* LBX is needed for compatibility to the XWeb stuff */
> #define BuildLBX	               YES
> 
>+#define HasXdmAuth                     NO
>+
> /* Xprt's non-bitmap based DDX (PS, PCL, PDF, SVGprint etc.) cannot support MIT-SHM */
> #undef HasShm
> #define HasShm NO
>@@ -144,6 +146,7 @@
> #define BuildXcursorgen                NO
> #define SharedLibFontEnc               NO
> #define SharedLibFont                  NO
>+#define SharedLibXdmcp                 NO
> #define XserverStaticFontLib           YES
> 
> /* Build only Xprint applications */
>@@ -156,11 +159,12 @@
> #define XVendorString "xprint.mozdev.org"
> #define XVendorRelease 100000
> 
>-#define UseHackLinkAgainstInstalledX11Libs NO
>+#define UseHackLinkAgainstInstalledX11Libs YES
> #if UseHackLinkAgainstInstalledX11Libs
> /* "Hack" to reuse an already installed X11 distribution when linking our
>  * programs (this assumes that the installed X version is at least X11R6.4) */
> # ifndef IBMArchitecture
>+#  define X11ProjectDefines -I/usr/X11R6/include
> #  define LdPreLib -L$(USRLIBDIR) -R$(USRLIBDIR) -L$(BUILDLIBDIR)
> # endif /* !IBMArchitecture */
> #endif /* UseHackLinkAgainstInstalledX11Libs */
>@@ -211,9 +215,7 @@
>    /* Make sure we install our own encoding files since Solaris uses a format we
>     * (currently) do not support (yet).
>     */
>-#  define InstallXF86EncodingFiles YES
>-#  undef XF86EncodingsPath
>-#  define XF86EncodingsPath /opt/GISWxprint/lib/X11/fonts/encodings
>+#  define FontEncDir /opt/GISWxprint/lib/X11/fonts/encodings
> #endif /* GISWxprint */
> 
> /* Install XF86 encoding files since that's the only format we currently support */
>@@ -222,8 +224,11 @@
> #endif /* InstallXF86EncodingFiles */
> 
> #define HasVarDirectory NO
>+
>+#undef HasMotif
> #undef HasMotif2
>-#define HasMotif2 YES
>+#define HasMotif NO
>+#define HasMotif2 NO
> 
> #if 1 /* Switch for 32bit binaries or 64bit binaries */
>    /* 32bit SPARC */
>@@ -273,7 +278,9 @@
> #undef XF86SVGAServer
> #define XF86SVGAServer NO
> #define HasVarDirectory NO
>+#if 0
> #define HasMotif2 YES
>+#endif
> #define HasGhostScript YES
> #define InstallXF86EncodingFiles NO
> /* Debian Xprint package puts the Xprt config files elsewhere */
>@@ -295,10 +302,6 @@
> 
> INSTALLXF86ENCODINGFILES = InstallXF86EncodingFiles
> 
>-#ifndef XF86EncodingsPath
>-#define XF86EncodingsPath $(FONTDIR)/encodings
>-#endif /* XF86EncodingsPath *
>-
> /* #########################################################################
>  * ################      xprint.mozdev.org defaults end     ################
>  * #########################################################################
>diff -N -x '*CVS*' -r -u base/xc/doc/Imakefile branch/xc/doc/Imakefile
>--- base/xc/doc/Imakefile	2004-04-23 20:42:01.000000000 +0200
>+++ branch/xc/doc/Imakefile	2004-11-26 10:45:46.000000000 +0100
>@@ -20,7 +20,11 @@
> HARDCOPYDIR = hardcopy
> #endif
> 
>+#if 0
> SUBDIRS = man $(MISCDIR) $(SPECSDIR) $(HARDCOPYDIR)
>+#else
>+SUBDIRS = man $(HARDCOPYDIR)
>+#endif
> 
> all::
> 
>diff -N -x '*CVS*' -r -u base/xc/doc/hardcopy/Imakefile branch/xc/doc/hardcopy/Imakefile
>--- base/xc/doc/hardcopy/Imakefile	2004-07-19 23:07:32.000000000 +0200
>+++ branch/xc/doc/hardcopy/Imakefile	2004-11-26 04:29:50.000000000 +0100
>@@ -3,11 +3,15 @@
> #define IHaveSubdirs
> #define PassCDebugFlags
> 
>+#if 0
> #if defined(HardcopyDocDirs) && !BuildAllHardcopyDocs
> SUBDIRS = HardcopyDocDirs
> #else
> SUBDIRS = RX XKB XPRINT
> #endif /* defined(HardcopyDocDirs) && !BuildAllHardcopyDocs */
>+#else
>+SUBDIRS = XPRINT
>+#endif
> 
> all::
> 
>diff -N -x '*CVS*' -r -u base/xc/doc/man/Imakefile branch/xc/doc/man/Imakefile
>--- base/xc/doc/man/Imakefile	2004-06-30 22:06:51.000000000 +0200
>+++ branch/xc/doc/man/Imakefile	2004-11-26 10:45:46.000000000 +0100
>@@ -1,5 +1,5 @@
> XCOMM $Xorg: Imakefile,v 1.3 2000/08/17 19:41:54 cpqbld Exp $
>-XCOMM $XdotOrg: xc/doc/man/Imakefile,v 1.4 2004/06/30 20:06:51 kem Exp $
>+XCOMM $XdotOrg: xc/doc/man/Imakefile,v 1.4.12.1 2004/11/26 09:45:46 gisburn Exp $
> 
> 
> 
>@@ -33,7 +33,11 @@
> LIBMANDIRS = X11 Xt Xext Xi Xau $(XVDIR) $(GLXDIRS) $(GLUDIRS) $(DMXDIR) $(XPRINTLIBDIRS)
> #endif
> 
>+#if 0
> SUBDIRS = general $(LIBMANDIRS) $(MISCDIR)
>+#else
>+SUBDIRS = general
>+#endif
> 
> all::
> 
>diff -N -x '*CVS*' -r -u base/xc/doc/man/general/Imakefile branch/xc/doc/man/general/Imakefile
>--- base/xc/doc/man/general/Imakefile	2004-04-23 20:42:14.000000000 +0200
>+++ branch/xc/doc/man/general/Imakefile	2004-11-26 10:45:46.000000000 +0100
>@@ -8,8 +8,16 @@
> 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 */
>diff -N -x '*CVS*' -r -u base/xc/doc/man/general/Xprint.html branch/xc/doc/man/general/Xprint.html
>--- base/xc/doc/man/general/Xprint.html	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/doc/man/general/Xprint.html	2004-11-26 10:45:46.000000000 +0100
>@@ -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>
>diff -N -x '*CVS*' -r -u base/xc/doc/man/general/Xprint.man branch/xc/doc/man/general/Xprint.man
>--- base/xc/doc/man/general/Xprint.man	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/doc/man/general/Xprint.man	2004-11-26 10:45:46.000000000 +0100
>@@ -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.
>diff -N -x '*CVS*' -r -u base/xc/doc/man/general/Xprint.sgml branch/xc/doc/man/general/Xprint.sgml
>--- base/xc/doc/man/general/Xprint.sgml	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/doc/man/general/Xprint.sgml	2004-11-26 10:45:46.000000000 +0100
>@@ -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>
>+
>diff -N -x '*CVS*' -r -u base/xc/fonts/Imakefile branch/xc/fonts/Imakefile
>--- base/xc/fonts/Imakefile	2004-04-23 20:43:00.000000000 +0200
>+++ branch/xc/fonts/Imakefile	2004-11-26 04:29:50.000000000 +0100
>@@ -15,7 +15,11 @@
> 
> FONTDIRS = bdf $(SCALEDDIR)
> 
>+#if 0
> SUBDIRS = $(ENCODINGDIR) util bdf $(SCALEDDIR)
>+#else
>+SUBDIRS = $(ENCODINGDIR) util
>+#endif
> 
> #if MakeLocalFontDir
> MakeDirectories(install,$(FONTDIR)/local)
>diff -N -x '*CVS*' -r -u base/xc/lib/Imakefile branch/xc/lib/Imakefile
>--- base/xc/lib/Imakefile	2004-09-29 14:40:28.000000000 +0200
>+++ branch/xc/lib/Imakefile	2004-12-05 14:16:21.000000000 +0100
>@@ -222,7 +222,7 @@
> FSLIBDIR = FS
> #endif
> 
>-
>+#if 0
> LINTSUBDIRS = $(XAULIBDIR) $(XDMCPLIBDIR) $(X11LIBDIR) \
>              $(OLDXLIBDIR) $(ICELIBDIR) $(SMLIBDIR) $(XEXTLIBDIR) $(XTLIBDIR) \
>              $(SSLIBDIR) $(XF86MISCLIBDIR) $(XF86VMLIBDIR) $(XF86DGALIBDIR) \
>@@ -237,9 +237,13 @@
> 	     $(XFTLIBDIR) $(XVMCLIBDIR) $(RANDRLIBDIR) $(XTRAPLIBDIR) \
> 	     $(XRESLIBDIR) $(XCURSORLIBDIR) $(APPLELIBDIR) $(DMXLIBDIR) \
> 	     $(WINDOWSLIBDIR) $(XEVIELIBDIR) $(XFIXESLIBDIR) $(DAMAGELIBDIR) $(COMPOSITELIBDIR)
>+#else
>+LINTSUBDIRS = $(XAULIBDIR) $(XDMCPLIBDIR) $(X11LIBDIR) \
>+             $(XPRINTLIBDIRS) $(LBXUTILDIR) \
>+             $(ZLIBDIR) $(REGEXDIR) $(FREETYPE2BUILDDIR)
>+#endif
> 
>-SUBDIRS = $(BERKDIR) xtrans $(LINTSUBDIRS) $(FONTSUBDIR) $(FONTENCSUBDIR) \
>-          $(FONTCACHELIBDIR)
>+SUBDIRS = $(BERKDIR) xtrans $(LINTSUBDIRS) $(FONTSUBDIR) $(FONTENCSUBDIR)
> 
> MakeSubdirs($(SUBDIRS))
> DependSubdirs($(SUBDIRS))
>diff -N -x '*CVS*' -r -u base/xc/lib/X11/Imakefile branch/xc/lib/X11/Imakefile
>--- base/xc/lib/X11/Imakefile	2004-09-01 03:04:33.000000000 +0200
>+++ branch/xc/lib/X11/Imakefile	2004-12-05 21:25:56.000000000 +0100
>@@ -10,1098 +10,5 @@
>         HEADERS = Xlib.h Xresource.h Xutil.h cursorfont.h Xlibint.h \
> 			Xcms.h Xlocale.h XKBlib.h
> 
>-#if BuildServersOnly && !XWinServer && !XnestServer && !BuildGLXLibrary && !BuildClients && !XdmxServer
>-all::
>-
>-BuildIncludes($(HEADERS),IncSubdir,..)
>-
>-#else
>-
>-#if BuildLoadableXlibI18n
>-#define IHaveSubdirs
>-#define PassCDebugFlags CDEBUGFLAGS="$(CDEBUGFLAGS)"
>-#define NoLibSubdirs
>-#endif
>-
>-#define DoNormalLib NormalLibX11
>-#define DoSharedLib SharedLibX11
>-#define DoExtraLib SharedLibX11
>-#define DoDebugLib DebugLibX11
>-#define DoProfileLib ProfileLibX11
>-#define LibName X11
>-#define SoRev SOXLIBREV
>-#define HugeLibrary YES
>-#define IncSubdir X11
>-
>-#if BuildLoadableXlibI18n
>-SUBDIRS = xlibi18n
>-#endif
>-
>-#include <Threads.tmpl>
>-
>-#ifndef MotifBC
>-#define MotifBC NO
>-#endif
>-
>-#ifdef SharedX11Reqs
>-REQUIREDX11LIBS = SharedX11Reqs
>-#endif
>-#if BuildLoadableXlibI18n
>-REQUIREDI18NLIBS = DlLibrary
>-#endif
>-#ifdef cygwinArchitecture
>-EXCLUDE_SYMBOL = -Wl,--exclude-symbol,XdmcpWrap:_XdmcpWrapperToOddParity
>-#endif
>-
>-REQUIREDLIBS=$(REQUIREDX11LIBS) $(REQUIREDI18NLIBS) $(EXCLUDE_SYMBOL)
>-
>-#if defined(MacIIArchitecture) || defined(SequentArchitecture) || defined(i386ScoArchitecture)
>-XBSDLIB = /**/
>-#endif
>-#if defined(LunaArchitecture) && defined(Mc88000Architecture)
>-EXTRA_LIBRARIES = /**/
>-#endif
>-#if Malloc0ReturnsNull
>-     MALLOC_DEFINES = XMalloc0ReturnsNullDefines
>-#endif
>-#if HasXdmAuth
>-        XDMAUTHDEFS = -DHASXDMAUTH
>-        XDMAUTHOBJS = Wrap.o Wraphelp.o
>-        XDMAUTHSRCS = Wrap.c Wraphelp.c
>-#endif
>-#if BuildXKBlib
>-    XKB_DEFINES = -DXKB 
>-        XKBSRCS = XKB.c XKBBind.c XKBCompat.c XKBCtrls.c XKBCvt.c XKBGetMap.c \
>-	          XKBGetByName.c XKBNames.c XKBRdBuf.c XKBSetMap.c XKBUse.c \
>-		  XKBleds.c XKBBell.c XKBGeom.c XKBSetGeom.c XKBExtDev.c \
>-		  XKBList.c XKBMisc.c \
>-		  XKBMAlloc.c XKBGAlloc.c XKBAlloc.c
>-        XKBOBJS = XKB.o XKBBind.o XKBCompat.o XKBCtrls.o XKBCvt.o XKBGetMap.o \
>-		  XKBGetByName.o XKBNames.o XKBRdBuf.o XKBSetMap.o XKBUse.o \
>-		  XKBleds.o XKBBell.o XKBGeom.o XKBSetGeom.o XKBExtDev.o \
>-		  XKBList.o XKBMisc.o \
>-		  XKBMAlloc.o XKBGAlloc.o XKBAlloc.o
>-#endif
>-#if HasSecureRPC
>-        RPCDEFS = -DSECURE_RPC
>-#endif
>-#if HasPoll
>-   POLL_DEFINES = -DUSE_POLL
>-#endif
>-   CONN_DEFINES = $(CONNECTION_FLAGS)
>-   XTRANS_X_DEFINES = -DX11_t -DTRANS_CLIENT $(XTRANS_FAILDEFINES)
>-   XTRANS_XIM_DEFINES = -DXIM_t -DTRANS_CLIENT $(XTRANS_FAILDEFINES)
>-#if HasBSD44Sockets
>-   SOCK_DEFINES = -DBSD44SOCKETS
>-#endif
>-#if HasShm
>-    SHM_DEFINES = -DHAS_SHM
>-#endif
>-
>-    XF86BIGFONT_DEFINES = XF86BigfontExtensionDefines
>-
>-     EDB_DEFINES = -DERRORDB=\"$(LIBDIR)/XErrorDB\"
>-     KDB_DEFINES = -DKEYSYMDB=\"$(LIBDIR)/XKeysymDB\"
>-     CMS_DEFINES = -DXCMSDB=\"$(LIBDIR)/Xcms.txt\"
>-#if HasSnprintf
>-    MISC_DEFINES = -DHAS_SNPRINTF -DLIBX11
>-#endif
>-#if MotifBC
>-      BC_DEFINES = -DMOTIFBC
>-#endif
>-#if NoRConst
>- RCONST_DEFINES = -DNORCONST
>-#endif
>-#if DisableXLocaleDirEnv
>-  SETID_DEFINES = -DNO_XLOCALEDIR
>-#elif HasIssetugid
>-  SETID_DEFINES = -DHASSETUGID
>-#elif HasGetresuid
>-  SETID_DEFINES = -DHASGETRESUID
>-#endif
>-    XLC_DEFINES = -DXLOCALEDIR=\"$(XLOCALEDIR)\"
>-#if HasKrb5
>-         K5OBJS = k5encode.o
>-         K5SRCS = k5encode.c
>-         K5INCL = Krb5Includes
>-         K5DEFS = Krb5Defines
>-#endif
>-#if (defined(FreeBSDArchitecture) && OSRelVersion < 500016) || \
>-	defined(OpenBSDArchitecture)
>-THRSTUBSRCS = UIThrStubs.c
>-THRSTUBOBJS = UIThrStubs.o
>-#endif
>-#if BuildLoadableXlibXcursor
>-XCURSOR_DEFINES = -DUSE_DYNAMIC_XCURSOR -DLIBXCURSOR=\"libXcursor.so.$(SOXCURSORREV)\"
>-#endif
>-#if NeedLibInsideFlag
>-    LIB_DEFINES = -D_XLIBINT_
>-#endif
>-#if defined(LibDirName)
>-        POSTLOCALELIBDIR = LibDirName
>-        POSTLOCALELIBDEFINES = -DPOSTLOCALELIBDIR=\"$(POSTLOCALELIBDIR)\"
>-#endif
>-        DEFINES = $(MALLOC_DEFINES) $(LIB_DEFINES) $(MISC_DEFINES)\
>-			$(POSTLOCALELIBDEFINES)
>-   OPEN_DEFINES = -I$(EXTINCSRC) $(K5INCL) $(K5DEFS)
>- DEPEND_DEFINES = $(OPEN_DEFINES) $(TRANS_INCLUDES) $(CONN_DEFINES) $(THREADS_DEFINES) DependDefines
>-       AUTHOBJS = AuDispose.o AuGetBest.o AuFileName.o AuRead.o
>-       AUTHSRCS = AuDispose.c AuGetBest.c AuFileName.c AuRead.c
>-           SRCS = $(SRCS1) $(SRCS2) $(SRCS3) $(EXTRASRCS) /* try *.c if you have trouble */
>-       LINTLIBS =
>-
>-#if BuildLoadableXlibI18n && DoSharedLib
>-EXTRASHAREDSRC = $(SHAREDLCSRCS)
>-#endif
>-#if !BuildLoadableXlibI18n || DoNormalLib
>-EXTRASTATICSRC = $(STATICLCSRCS)
>-#endif
>-
>-EXTRASRCS = $(EXTRASHAREDSRC) $(EXTRASTATICSRC)
>-
>-SRCS1 = \
>-	Context.c \
>-	Depths.c \
>-	ParseCmd.c \
>-	Quarks.c \
>-	AllCells.c \
>-	AllPlanes.c \
>-	AllowEv.c \
>-	AutoRep.c \
>-	Backgnd.c \
>-	BdrWidth.c \
>-	Bell.c \
>-	Border.c \
>-	ChAccCon.c \
>-	ChClMode.c \
>-	ChActPGb.c \
>-	ChCmap.c \
>-	ChGC.c \
>-	ChKeyCon.c \
>-	ChPntCon.c \
>-	ChProp.c \
>-	ChSaveSet.c \
>-	ChWAttrs.c \
>-	ChWindow.c \
>-	ChkIfEv.c \
>-	ChkMaskEv.c \
>-	ChkWinEv.c \
>-	ChkTypEv.c \
>-	ChkTypWEv.c \
>-	CirWin.c \
>-	CirWinDn.c \
>-	CirWinUp.c \
>-	ClDisplay.c \
>-	Clear.c \
>-	ClearArea.c \
>-	ConfWind.c \
>-	ConnDis.c \
>-	ConvSel.c \
>-	CopyArea.c \
>-	CopyCmap.c \
>-	CopyGC.c \
>-	CopyPlane.c \
>-	CrBFData.c \
>-	CrCmap.c \
>-	CrCursor.c \
>-	CrGC.c \
>-	CrGlCur.c \
>-	CrPFBData.c \
>-	CrPixmap.c \
>-	CrWindow.c \
>-	Cursor.c \
>-	DefCursor.c \
>-	DelProp.c \
>-	DestSubs.c \
>-	DestWind.c \
>-	DisName.c \
>-	DrArc.c \
>-	DrArcs.c \
>-	DrLine.c \
>-	DrLines.c \
>-	DrPoint.c \
>-	DrPoints.c \
>-	DrRect.c \
>-	DrRects.c \
>-	DrSegs.c \
>-	ErrDes.c \
>-	ErrHndlr.c \
>-	EvToWire.c \
>-	FetchName.c \
>-	FillArc.c \
>-	FillArcs.c \
>-	FillPoly.c \
>-	FillRct.c \
>-	FillRcts.c \
>-	Flush.c \
>-	Font.c \
>-	FontNames.c \
>-	FontInfo.c \
>-	FreeCmap.c \
>-	FreeCols.c \
>-	FreeCurs.c \
>-	FreeEData.c \
>-	FreeGC.c \
>-	FreePix.c \
>-	FSSaver.c \
>-	GCMisc.c \
>-	Geom.c \
>-	GetAtomNm.c \
>-	GetColor.c \
>-	GetDflt.c \
>-	GetFPath.c \
>-	GetFProp.c \
>-	GetGeom.c \
>-	GetHColor.c \
>-	GetHints.c \
>-	GetIFocus.c \
>-	GetImage.c \
>-	GetKCnt.c \
>-	GetMoEv.c \
>-	GetPCnt.c \
>-	GetPntMap.c \
>-	GetProp.c \
>-	GetSOwner.c \
>-	GetSSaver.c \
>-	GetStCmap.c \
>-	GetWAttrs.c \
>-	GrButton.c \
>-	GrKey.c \
>-	GrKeybd.c \
>-	GrPointer.c \
>-	GrServer.c \
>-	Host.c \
>-	IfEvent.c \
>-	ImUtil.c \
>-	ImText.c \
>-	ImText16.c \
>-	InitExt.c \
>-	InsCmap.c \
>-	IntAtom.c \
>-	KeyBind.c \
>-	KeysymStr.c \
>-	KillCl.c \
>-	LiHosts.c \
>-	LiICmaps.c \
>-	LiProps.c \
>-	ListExt.c \
>-	LoadFont.c \
>-	LookupCol.c \
>-	LowerWin.c 
>-
>-OBJS1 = \
>-	Context.o \
>-	Depths.o \
>-	ParseCmd.o \
>-	Quarks.o \
>-	AllCells.o \
>-	AllPlanes.o \
>-	AllowEv.o \
>-	AutoRep.o \
>-	Backgnd.o \
>-	BdrWidth.o \
>-	Bell.o \
>-	Border.o \
>-	ChAccCon.o \
>-	ChClMode.o \
>-	ChActPGb.o \
>-	ChCmap.o \
>-	ChGC.o \
>-	ChKeyCon.o \
>-	ChPntCon.o \
>-	ChProp.o \
>-	ChSaveSet.o \
>-	ChWAttrs.o \
>-	ChWindow.o \
>-	ChkIfEv.o \
>-	ChkMaskEv.o \
>-	ChkWinEv.o \
>-	ChkTypEv.o \
>-	ChkTypWEv.o \
>-	CirWin.o \
>-	CirWinDn.o \
>-	CirWinUp.o \
>-	ClDisplay.o \
>-	Clear.o \
>-	ClearArea.o \
>-	ConfWind.o \
>-	ConnDis.o \
>-	ConvSel.o \
>-	CopyArea.o \
>-	CopyCmap.o \
>-	CopyGC.o \
>-	CopyPlane.o \
>-	CrBFData.o \
>-	CrCmap.o \
>-	CrCursor.o \
>-	CrGC.o \
>-	CrGlCur.o \
>-	CrPFBData.o \
>-	CrPixmap.o \
>-	CrWindow.o \
>-	Cursor.o \
>-	DefCursor.o \
>-	DelProp.o \
>-	DestSubs.o \
>-	DestWind.o \
>-	DisName.o \
>-	DrArc.o \
>-	DrArcs.o \
>-	DrLine.o \
>-	DrLines.o \
>-	DrPoint.o \
>-	DrPoints.o \
>-	DrRect.o \
>-	DrRects.o \
>-	DrSegs.o \
>-	ErrDes.o \
>-	ErrHndlr.o \
>-	EvToWire.o \
>-	FetchName.o \
>-	FillArc.o \
>-	FillArcs.o \
>-	FillPoly.o \
>-	FillRct.o \
>-	FillRcts.o \
>-	Flush.o \
>-	Font.o \
>-	FontNames.o \
>-	FontInfo.o \
>-	FreeCmap.o \
>-	FreeCols.o \
>-	FreeCurs.o \
>-	FreeEData.o \
>-	FreeGC.o \
>-	FreePix.o \
>-	FSSaver.o \
>-	GCMisc.o \
>-	Geom.o \
>-	GetAtomNm.o \
>-	GetColor.o \
>-	GetDflt.o \
>-	GetFPath.o \
>-	GetFProp.o \
>-	GetGeom.o \
>-	GetHColor.o \
>-	GetHints.o \
>-	GetIFocus.o \
>-	GetImage.o \
>-	GetKCnt.o \
>-	GetMoEv.o \
>-	GetPCnt.o \
>-	GetPntMap.o \
>-	GetProp.o \
>-	GetSOwner.o \
>-	GetSSaver.o \
>-	GetStCmap.o \
>-	GetWAttrs.o \
>-	GrButton.o \
>-	GrKey.o \
>-	GrKeybd.o \
>-	GrPointer.o \
>-	GrServer.o \
>-	Host.o \
>-	IfEvent.o \
>-	ImUtil.o \
>-	ImText.o \
>-	ImText16.o \
>-	InitExt.o \
>-	InsCmap.o \
>-	IntAtom.o \
>-	KeyBind.o \
>-	KeysymStr.o \
>-	KillCl.o \
>-	LiHosts.o \
>-	LiICmaps.o \
>-	LiProps.o \
>-	ListExt.o \
>-	LoadFont.o \
>-	LookupCol.o \
>-	LowerWin.o 
>-
>-SRCS2 = \
>-	Macros.c \
>-	MapRaised.c \
>-	MapSubs.c \
>-	MapWindow.c \
>-	MaskEvent.c \
>-	Misc.c \
>-	ModMap.c \
>-	MoveWin.c \
>-	NextEvent.c \
>-	OpenDis.c \
>-	ParseCol.c \
>-	ParseGeom.c \
>-	PeekEvent.c \
>-	PeekIfEv.c \
>-	Pending.c \
>-	PmapBgnd.c \
>-	PmapBord.c \
>-	PolyReg.c \
>-	PolyTxt.c \
>-	PolyTxt16.c \
>-	PutBEvent.c \
>-	PutImage.c \
>-	QuBest.c \
>-	QuColor.c \
>-	QuColors.c \
>-	QuCurShp.c \
>-	QuExt.c \
>-	QuKeybd.c \
>-	QuPntr.c \
>-	QuStipShp.c \
>-	QuTextE16.c \
>-	QuTextExt.c \
>-	QuTileShp.c \
>-	QuTree.c \
>-	RaiseWin.c \
>-	RdBitF.c \
>-	RecolorC.c \
>-	ReconfWin.c \
>-	Region.c \
>-	RepWindow.c \
>-	RestackWs.c \
>-	RotProp.c \
>-	ScrResStr.c \
>-	SelInput.c \
>-	SendEvent.c \
>-	SetBack.c \
>-	SetCRects.c \
>-	SetClMask.c \
>-	SetClOrig.c \
>-	SetDashes.c \
>-	SetFPath.c \
>-	SetFont.c \
>-	SetFore.c \
>-	SetFunc.c \
>-	SetHints.c \
>-	SetIFocus.c \
>-	SetLStyle.c \
>-	SetPMask.c \
>-	SetPntMap.c \
>-	SetSOwner.c \
>-	SetSSaver.c \
>-	SetState.c \
>-	SetStip.c \
>-	SetStCmap.c \
>-	SetTile.c \
>-	SetTSOrig.c \
>-	StBytes.c \
>-	StColor.c \
>-	StColors.c \
>-	StNColor.c \
>-	StName.c \
>-	StrKeysym.c \
>-	Sync.c \
>-	Synchro.c \
>-	Text.c \
>-	Text16.c \
>-	TextExt.c \
>-	TextExt16.c \
>-	TrCoords.c \
>-	UndefCurs.c \
>-	UngrabBut.c \
>-	UngrabKbd.c \
>-	UngrabKey.c \
>-	UngrabPtr.c \
>-	UngrabSvr.c \
>-	UninsCmap.c \
>-	UnldFont.c \
>-	UnmapSubs.c \
>-	UnmapWin.c \
>-	VisUtil.c \
>-	WarpPtr.c \
>-	WinEvent.c \
>-	Window.c \
>-	WrBitF.c \
>-	XlibAsync.c \
>-	XlibInt.c \
>-	Xrm.c \
>-	evtomask.c \
>-	globals.c \
>-	GetGCVals.c \
>-	GetNrmHint.c \
>-	GetRGBCMap.c \
>-	GetTxtProp.c \
>-	GetWMCMapW.c \
>-	GetWMProto.c \
>-	Iconify.c \
>-	PixFormats.c \
>-	PropAlloc.c \
>-	ReconfWM.c \
>-	SetNrmHint.c \
>-	SetRGBCMap.c \
>-	SetTxtProp.c \
>-	SetWMCMapW.c \
>-	SetWMProto.c \
>-	StrToText.c \
>-	TextToStr.c \
>-	Withdraw.c \
>-	WMGeom.c \
>-	WMProps.c \
>-	$(AUTHSRCS) $(XDMAUTHSRCS) $(K5SRCS) $(THRSTUBSRCS)
>-
>-OBJS2 = \
>-	Macros.o \
>-	MapRaised.o \
>-	MapSubs.o \
>-	MapWindow.o \
>-	MaskEvent.o \
>-	Misc.o \
>-	ModMap.o \
>-	MoveWin.o \
>-	NextEvent.o \
>-	OpenDis.o \
>-	ParseCol.o \
>-	ParseGeom.o \
>-	PeekEvent.o \
>-	PeekIfEv.o \
>-	Pending.o \
>-	PmapBgnd.o \
>-	PmapBord.o \
>-	PolyReg.o \
>-	PolyTxt.o \
>-	PolyTxt16.o \
>-	PutBEvent.o \
>-	PutImage.o \
>-	QuBest.o \
>-	QuColor.o \
>-	QuColors.o \
>-	QuCurShp.o \
>-	QuExt.o \
>-	QuKeybd.o \
>-	QuPntr.o \
>-	QuStipShp.o \
>-	QuTextE16.o \
>-	QuTextExt.o \
>-	QuTileShp.o \
>-	QuTree.o \
>-	RaiseWin.o \
>-	RdBitF.o \
>-	RecolorC.o \
>-	ReconfWin.o \
>-	Region.o \
>-	RepWindow.o \
>-	RestackWs.o \
>-	RotProp.o \
>-	ScrResStr.o \
>-	SelInput.o \
>-	SendEvent.o \
>-	SetBack.o \
>-	SetCRects.o \
>-	SetClMask.o \
>-	SetClOrig.o \
>-	SetDashes.o \
>-	SetFPath.o \
>-	SetFont.o \
>-	SetFore.o \
>-	SetFunc.o \
>-	SetHints.o \
>-	SetIFocus.o \
>-	SetLStyle.o \
>-	SetPMask.o \
>-	SetPntMap.o \
>-	SetSOwner.o \
>-	SetSSaver.o \
>-	SetState.o \
>-	SetStip.o \
>-	SetStCmap.o \
>-	SetTile.o \
>-	SetTSOrig.o \
>-	StBytes.o \
>-	StColor.o \
>-	StColors.o \
>-	StNColor.o \
>-	StName.o \
>-	StrKeysym.o \
>-	Sync.o \
>-	Synchro.o \
>-	Text.o \
>-	Text16.o \
>-	TextExt.o \
>-	TextExt16.o \
>-	TrCoords.o \
>-	UndefCurs.o \
>-	UngrabBut.o \
>-	UngrabKbd.o \
>-	UngrabKey.o \
>-	UngrabPtr.o \
>-	UngrabSvr.o \
>-	UninsCmap.o \
>-	UnldFont.o \
>-	UnmapSubs.o \
>-	UnmapWin.o \
>-	VisUtil.o \
>-	WarpPtr.o \
>-	WinEvent.o \
>-	Window.o \
>-	WrBitF.o \
>-	XlibAsync.o \
>-	XlibInt.o \
>-	Xrm.o \
>-	evtomask.o \
>-	globals.o \
>-	GetGCVals.o \
>-	GetNrmHint.o \
>-	GetRGBCMap.o \
>-	GetTxtProp.o \
>-	GetWMCMapW.o \
>-	GetWMProto.o \
>-	Iconify.o \
>-	PixFormats.o \
>-	PropAlloc.o \
>-	ReconfWM.o \
>-	SetNrmHint.o \
>-	SetRGBCMap.o \
>-	SetTxtProp.o \
>-	SetWMCMapW.o \
>-	SetWMProto.o \
>-	StrToText.o \
>-	TextToStr.o \
>-	Withdraw.o \
>-	WMGeom.o \
>-	WMProps.o \
>-	$(AUTHOBJS) \
>-	$(XDMAUTHOBJS) \
>-	$(K5OBJS) \
>-	$(THRSTUBOBJS)
>-
>-SRCS3 = \
>-	Lab.c \
>-	LabGcC.c \
>-	LabGcL.c \
>-	LabGcLC.c \
>-	LabMnL.c \
>-	LabMxC.c \
>-	LabMxL.c \
>-	LabMxLC.c \
>-	LabWpAj.c \
>-	Luv.c \
>-	LuvGcC.c \
>-	LuvGcL.c \
>-	LuvGcLC.c \
>-	LuvMnL.c \
>-	LuvMxC.c \
>-	LuvMxL.c \
>-	LuvMxLC.c \
>-	LuvWpAj.c \
>-	XYZ.c \
>-	uvY.c \
>-	xyY.c \
>-	HVC.c \
>-	HVCGcC.c \
>-	HVCGcV.c \
>-	HVCGcVC.c \
>-	HVCMnV.c \
>-	HVCMxC.c \
>-	HVCMxV.c \
>-	HVCMxVC.c \
>-	HVCMxVs.c \
>-	HVCWpAj.c \
>-	UNDEFINED.c \
>-	AddDIC.c \
>-	AddSF.c \
>-	cmsAllNCol.c \
>-	cmsAllCol.c \
>-	CCC.c \
>-	cmsCmap.c \
>-	cmsColNm.c \
>-	CvColW.c \
>-	CvCols.c \
>-	cmsGlobls.c \
>-	IdOfPr.c \
>-	cmsInt.c \
>-	LRGB.c \
>-	cmsLkCol.c \
>-	cmsMath.c \
>-	OfCCC.c \
>-	PrOfId.c \
>-	cmsProp.c \
>-	QBlack.c \
>-	QBlue.c \
>-	QGreen.c \
>-	QRed.c \
>-	QWhite.c \
>-	QuCol.c \
>-	QuCols.c \
>-	SetCCC.c \
>-	SetGetCols.c \
>-	StCol.c \
>-	StCols.c \
>-	cmsTrig.c \
>-	XRGB.c \
>-	FSWrap.c \
>-	ICWrap.c \
>-	IMWrap.c \
>-	OCWrap.c \
>-	OMWrap.c \
>-	lcWrap.c \
>-	mbWMProps.c \
>-	utf8WMProps.c \
>-	mbWrap.c \
>-	wcWrap.c \
>-	utf8Wrap.c \
>-	FilterEv.c \
>-	RegstFlt.c \
>-	locking.c \
>-	LockDis.c \
>-	x11trans.c \
>-	ximtrans.c \
>-	$(XKBSRCS) $(LCSRCS) $(MISCSRCS)
>-
>-OBJS3 = \
>-	Lab.o \
>-	LabGcC.o \
>-	LabGcL.o \
>-	LabGcLC.o \
>-	LabMnL.o \
>-	LabMxC.o \
>-	LabMxL.o \
>-	LabMxLC.o \
>-	LabWpAj.o \
>-	Luv.o \
>-	LuvGcC.o \
>-	LuvGcL.o \
>-	LuvGcLC.o \
>-	LuvMnL.o \
>-	LuvMxC.o \
>-	LuvMxL.o \
>-	LuvMxLC.o \
>-	LuvWpAj.o \
>-	XYZ.o \
>-	uvY.o \
>-	xyY.o \
>-	HVC.o \
>-	HVCGcC.o \
>-	HVCGcV.o \
>-	HVCGcVC.o \
>-	HVCMnV.o \
>-	HVCMxC.o \
>-	HVCMxV.o \
>-	HVCMxVC.o \
>-	HVCMxVs.o \
>-	HVCWpAj.o \
>-	UNDEFINED.o \
>-	AddDIC.o \
>-	AddSF.o \
>-	cmsAllNCol.o \
>-	cmsAllCol.o \
>-	CCC.o \
>-	cmsCmap.o \
>-	cmsColNm.o \
>-	CvColW.o \
>-	CvCols.o \
>-	cmsGlobls.o \
>-	IdOfPr.o \
>-	cmsInt.o \
>-	LRGB.o \
>-	cmsLkCol.o \
>-	cmsMath.o \
>-	OfCCC.o \
>-	PrOfId.o \
>-	cmsProp.o \
>-	QBlack.o \
>-	QBlue.o \
>-	QGreen.o \
>-	QRed.o \
>-	QWhite.o \
>-	QuCol.o \
>-	QuCols.o \
>-	SetCCC.o \
>-	SetGetCols.o \
>-	StCol.o \
>-	StCols.o \
>-	cmsTrig.o \
>-	XRGB.o \
>-	FSWrap.o \
>-	ICWrap.o \
>-	IMWrap.o \
>-	OCWrap.o \
>-	OMWrap.o \
>-	lcWrap.o \
>-	mbWMProps.o \
>-	utf8WMProps.o \
>-	mbWrap.o \
>-	wcWrap.o \
>-	utf8Wrap.o \
>-	FilterEv.o \
>-	RegstFlt.o \
>-	locking.o \
>-	LockDis.o \
>-	x11trans.o \
>-	ximtrans.o \
>-	$(XKBOBJS) $(LCOBJS) $(MISCOBJS)
>-
>-#if BuildLoadableXlibI18n
>-LC_DYNDEFINES = -DUSE_DYNAMIC_LC
>-#endif
>-
>-SHAREDLCDEPSYMSRCS = XlcDL.c XlcSL.c
>-
>-SHAREDI18NSTATICSRCS = \
>-        XDefaultIMIF.c XDefaultOMIF.c
>-
>-STATICLCDEPSYMSRCS =
>-
>-STATICI18NSTATICSRCS = \
>-	imCallbk.c \
>-	imDefFlt.c \
>-	imDefIc.c \
>-	imDefIm.c \
>-	imDefLkup.c \
>-	imDispch.c \
>-	imEvToWire.c \
>-	imExten.c \
>-	imImSw.c \
>-	imInsClbk.c \
>-	imInt.c \
>-	imLcFlt.c \
>-	imLcGIc.c \
>-	imLcIc.c \
>-	imLcIm.c \
>-	imLcLkup.c \
>-	imLcPrs.c \
>-	imLcSIc.c \
>-	imRm.c \
>-	imRmAttr.c \
>-	imThaiFlt.c \
>-	imThaiIc.c \
>-	imThaiIm.c \
>-	imTrX.c \
>-	imTransR.c \
>-	imTrans.c \
>-	lcEuc.c \
>-	lcGenConv.c \
>-	lcJis.c \
>-	lcSjis.c \
>-	lcUTF8Load.c \
>-	omDefault.c \
>-	omGeneric.c \
>-	omImText.c \
>-	omText.c \
>-	omTextEsc.c \
>-	omTextExt.c \
>-	omTextPer.c \
>-	omXChar.c
>-
>-LCSRCS = \
>-	SetLocale.c \
>-	imConv.c \
>-	imKStoUCS.c \
>-	lcCT.c \
>-	lcCharSet.c \
>-	lcConv.c \
>-	lcDB.c \
>-	lcDefConv.c \
>-	lcFile.c \
>-	lcGeneric.c \
>-	lcInit.c \
>-	lcPrTxt.c \
>-	lcPubWrap.c \
>-	lcPublic.c \
>-	lcRM.c \
>-	lcStd.c \
>-	lcTxtPr.c \
>-	lcUtil.c \
>-	lcUTF8.c
>-
>-STATICLCSRCS = \
>-	$(STATICLCDEPSYMSRCS) \
>-	$(STATICI18NSTATICSRCS)
>-
>-SHAREDLCSRCS = \
>-	$(SHAREDLCDEPSYMSRCS) \
>-	$(SHAREDI18NSTATICSRCS)
>-
>-SHAREDLCDEPOBJS = XlcDL.o XlcSL.o
>-SHAREDI18NSTATICOBJS = \
>-	XDefaultIMIF.o XDefaultOMIF.o
>-STATICLCDEPOBJS = 
>-STATICI18NSTATICOBJS = \
>-	imCallbk.o \
>-	imDefFlt.o \
>-	imDefIc.o \
>-	imDefIm.o \
>-	imDefLkup.o \
>-	imDispch.o \
>-	imEvToWire.o \
>-	imExten.o \
>-	imImSw.o \
>-	imInsClbk.o \
>-	imInt.o \
>-	imLcFlt.o \
>-	imLcGIc.o \
>-	imLcIc.o \
>-	imLcIm.o \
>-	imLcLkup.o \
>-	imLcPrs.o \
>-	imLcSIc.o \
>-	imRm.o \
>-	imRmAttr.o \
>-	imThaiFlt.o \
>-	imThaiIc.o \
>-	imThaiIm.o \
>-	imTrX.o \
>-	imTransR.o \
>-	imTrans.o \
>-	lcEuc.o \
>-	lcGenConv.o \
>-	lcJis.o \
>-	lcSjis.o \
>-	lcUTF8Load.o \
>-	omDefault.o \
>-	omGeneric.o \
>-	omImText.o \
>-	omText.o \
>-	omTextEsc.o \
>-	omTextExt.o \
>-	omTextPer.o \
>-	omXChar.o
>-
>-LCOBJS = \
>-	SetLocale.o \
>-	imConv.o \
>-	imKStoUCS.o \
>-	lcCT.o \
>-	lcCharSet.o \
>-	lcConv.o \
>-	lcDB.o \
>-	lcDefConv.o \
>-	lcFile.o \
>-	lcGeneric.o \
>-	lcInit.o \
>-	lcPrTxt.o \
>-	lcPubWrap.o \
>-	lcPublic.o \
>-	lcRM.o \
>-	lcStd.o \
>-	lcTxtPr.o \
>-	lcUtil.o \
>-	lcUTF8.o
>-
>-STATICLCOBJS = \
>-	$(STATICLCDEPOBJS) \
>-	$(STATICI18NSTATICOBJS) 
>-
>-SHAREDLCOBJS = \
>-	$(SHAREDLCDEPOBJS) \
>-	$(SHAREDI18NSTATICOBJS) 
>-
>-#ifdef OS2Architecture
>-MISCSRCS = os2Stubs.c
>-#endif
>-
>-#ifdef OS2Architecture
>-MISCOBJS = os2Stubs.o
>-#endif
>-
>-OBJS = $(OBJS1) $(OBJS2) $(OBJS3)
>-
>-EXTRAUNSHAREDOBJS = $(STATICLCOBJS)
>-
>-#if BuildLoadableXlibI18n
>-EXTRASHAREDOBJS = $(SHAREDLCOBJS)
>-# else
>-EXTRASHAREDOBJS = $(STATICLCOBJS)
>-#endif
>-
>-#include <Library.tmpl>
>-
>-SpecialCLibObjectRule(ErrDes,$(ICONFIGFILES),$(EDB_DEFINES))
>-SpecialCLibObjectRule(StrKeysym,$(ICONFIGFILES),$(KDB_DEFINES))
>-SpecialCLibObjectRule(ConnDis,$(ICONFIGFILES),$(XDMAUTHDEFS) $(RPCDEFS) $(CONN_DEFINES) $(SOCK_DEFINES) $(POLL_DEFINES) $(XTRANS_X_DEFINES) $(K5INCL) $(K5DEFS))
>-SpecialCLibObjectRule(x11trans,$(ICONFIGFILES),$(TRANS_INCLUDES) $(CONN_DEFINES) $(SOCK_DEFINES) $(XTRANS_X_DEFINES) $(POLL_DEFINES))
>-LinkFile(x11trans.c,$(TRANSCOMMSRC)/transport.c)
>-SpecialCLibObjectRule(ximtrans,$(ICONFIGFILES),$(TRANS_INCLUDES) $(CONN_DEFINES) $(SOCK_DEFINES) $(XTRANS_XIM_DEFINES) $(POLL_DEFINES))
>-LinkFile(ximtrans.c,$(TRANSCOMMSRC)/transport.c)
>-SpecialCLibObjectRule(OpenDis,$(ICONFIGFILES),$(BC_DEFINES) $(OPEN_DEFINES) $(XTRANS_X_DEFINES) $(XKB_DEFINES))
>-SpecialCLibObjectRule(Wrap,$(ICONFIGFILES),$(XDMAUTHDEFS))
>-SpecialCLibObjectRule(XlibInt,$(ICONFIGFILES),$(CONN_DEFINES) $(POLL_DEFINES) $(XTRANS_X_DEFINES))
>-SpecialCLibObjectRule(Font,$(ICONFIGFILES),$(SHM_DEFINES) $(XF86BIGFONT_DEFINES))
>-SpecialCLibObjectRule(FontInfo,$(ICONFIGFILES),$(SHM_DEFINES) $(XF86BIGFONT_DEFINES))
>-SpecialCLibObjectRule(cmsColNm,$(ICONFIGFILES),$(CMS_DEFINES))
>-SpecialCLibObjectRule(globals,$(ICONFIGFILES),$(CONN_DEFINES))
>-SpecialCLibObjectRule(Context,$(ICONFIGFILES),$(BC_DEFINES))
>-SpecialCLibObjectRule(Xrm,$(_NOOP_),$(RCONST_DEFINES))
>-SpecialCLibObjectRule(imTransR,$(ICONFIGFILES),$(CONN_DEFINES) $(XTRANS_XIM_DEFINES))
>-SpecialCLibObjectRule(imTrans,$(ICONFIGFILES),$(CONN_DEFINES) $(XTRANS_XIM_DEFINES))
>-SpecialCLibObjectRule(lcFile,$(ICONFIGFILES),$(XLC_DEFINES) $(SETID_DEFINES))
>-#if BuildXKBlib
>-SpecialCLibObjectRule(XKBCvt,$(_NOOP_),$(RCONST_DEFINES))
>-SpecialCLibObjectRule(KeyBind,$(ICONFIGFILES),$(XKB_DEFINES))
>-SpecialCLibObjectRule(XKBBind,$(ICONFIGFILES),$(XKB_DEFINES))
>-SpecialCLibObjectRule(imConv,$(ICONFIGFILES),$(XKB_DEFINES))
>-#endif
>-#if HasKrb5
>-SpecialCLibObjectRule(k5encode,$(_NOOP_),$(K5INCL))
>-#endif
>-#if BuildLoadableXlibI18n
>-SpecialCLibObjectRuleSeparateOpts(lcInit,$(ICONFIGFILES),$(_NOOP_),$(LC_DYNDEFINES))
>-SpecialCLibObjectRuleSeparateOpts(lcGeneric,$(ICONFIGFILES),$(_NOOP_),$(LC_DYNDEFINES))
>-SpecialCLibObjectRuleSeparateOpts(lcPublic,$(ICONFIGFILES),$(_NOOP_),$(LC_DYNDEFINES))
>-#endif
>-#if BuildLoadableXlibXcursor
>-SpecialCLibObjectRuleSeparateOpts(CrCursor,$(ICONFIGFILES),$(_NOOP_),$(XCURSOR_DEFINES))
>-SpecialCLibObjectRuleSeparateOpts(CrGlCur,$(ICONFIGFILES),$(_NOOP_),$(XCURSOR_DEFINES))
>-SpecialCLibObjectRuleSeparateOpts(CrPixmap,$(ICONFIGFILES),$(_NOOP_),$(XCURSOR_DEFINES))
>-SpecialCLibObjectRuleSeparateOpts(PutImage,$(ICONFIGFILES),$(_NOOP_),$(XCURSOR_DEFINES))
>-#endif
>-
>-#if InstallXcmsTxt
>-InstallNonExecFile(Xcms.txt,$(LIBDIR))
>-#endif
>-InstallNonExecFile(XErrorDB,$(LIBDIR))
>-InstallNonExecFile(XKeysymDB,$(LIBDIR))
>-InstallLintLibrary(X11,$(LINTLIBDIR))
>-
>-
>-LinkSourceFile(AuDispose.c,$(XAUTHSRC))
>-LinkSourceFile(AuGetBest.c,$(XAUTHSRC))
>-LinkSourceFile(AuFileName.c,$(XAUTHSRC))
>-LinkSourceFile(AuRead.c,$(XAUTHSRC))
>-#if HasKrb5
>-LinkSourceFile(k5encode.c,$(XAUTHSRC))
>-#endif
>-#if HasXdmAuth
>-LinkSourceFile(Wrap.h,$(XDMCPLIBSRC))
>-LinkSourceFile(Wrap.c,$(XDMCPLIBSRC))
>-LinkSourceFile(Wraphelp.c,$(XDMCPLIBSRC))
>-#endif
>-
>-#ifdef QNX4Architecture
>-LOCAL_LDFLAGS=-F
>-#endif
>-
>-MAKEKEYS = ./makekeys
>-
>-#if CrossCompiling
>-HOST_LDLIBS=
>-#else
>-HOST_LDLIBS=$(LDLIBS)
>-#endif
>-
>-ks_tables.h: $(XINCLUDESRC)/keysymdef.h util/makekeys.c
>-	RemoveFiles($@ HostProgramTargetName(makekeys) makekeys.Osuf)
>-	-HostLinkRule(HostProgramTargetName(makekeys),$(CFLAGS) $(LOCAL_LDFLAGS),util/makekeys.c,$(HOST_LDLIBS))
>-	RunProgram(MAKEKEYS,< $(XINCLUDESRC)/keysymdef.h > ks_tables_h)
>-	$(MV) ks_tables_h $@
>-	RemoveFiles(HostProgramTargetName(makekeys) makekeys.Osuf ks_tables_h)
>-
>-includes:: ks_tables.h
>-
>-depend:: ks_tables.h
>-
>-clean::
>-	RemoveFiles(ks_tables_h ks_tables.h HostProgramTargetName(makekeys))
>-
>-
>-DependTarget3($(SRCS1),$(SRCS2),$(SRCS3) $(EXTRASRCS))
>-
>-#if BuildLoadableXlibI18n
>-MakeSubdirs($(SUBDIRS))
>-DependSubdirs($(SUBDIRS))
>-MakeLintLibSubdirs($(LINTSUBDIRS))
>-MakeLintSubdirs($(LINTSUBDIRS),install.ln,install.ln)
>-#endif
>-#endif
>+BuildIncludes($(HEADERS),X11,..)
> 
>diff -N -x '*CVS*' -r -u base/xc/lib/font/fontfile/Imakefile branch/xc/lib/font/fontfile/Imakefile
>--- base/xc/lib/font/fontfile/Imakefile	2004-05-05 00:59:15.000000000 +0200
>+++ branch/xc/lib/font/fontfile/Imakefile	2004-12-03 04:39:10.000000000 +0100
>@@ -45,7 +45,7 @@
> #endif
> 
>  ATTRIBDEFS = -DFONTDIRATTRIB
>-FONTENCDEFS = -DFONT_ENCODINGS_DIRECTORY=\"$(FONTDIR)/encodings/encodings.dir\"
>+FONTENCDEFS = -DFONT_ENCODINGS_DIRECTORY=\"$(ENCODINGSDIR)/encodings.dir\"
> 
>     DEFINES = StrcasecmpDefines $(ATTRIBDEFS) \
> 	      $(SPEEDO_DEFINES) $(TYPE1_DEFINES) $(CID_DEFINES) \
>diff -N -x '*CVS*' -r -u base/xc/list_files_not_used_by_xp.ksh branch/xc/list_files_not_used_by_xp.ksh
>--- base/xc/list_files_not_used_by_xp.ksh	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/list_files_not_used_by_xp.ksh	2004-12-05 14:16:20.000000000 +0100
>@@ -0,0 +1,253 @@
>+#!/bin/ksh
>+# List files not used by the Xprint standalone config
>+
>+list_files()
>+{
>+(
>+  # extras
>+  find \
>+    xc/extras/fontconfig \
>+    xc/extras/drm \
>+    xc/extras/fonts \
>+    -type f
>+
>+  # libs
>+  find \
>+    xc/lib/FS \
>+    xc/lib/GLU \
>+    xc/lib/GLw \
>+    xc/lib/ICE \
>+    xc/lib/SM \
>+    xc/lib/XTrap \
>+    xc/lib/Xaw \
>+    xc/lib/Xaw6 \
>+    xc/lib/Xaw7 \
>+    xc/lib/Xcomposite \
>+    xc/lib/Xcursor \
>+    xc/lib/Xfontcache \
>+    xc/lib/Xft \
>+    xc/lib/Xft1 \
>+    xc/lib/Xi \
>+    xc/lib/Xinerama \
>+    xc/lib/Xmu \
>+    xc/lib/Xmuu \
>+    xc/lib/Xrandr \
>+    xc/lib/Xrender \
>+    xc/lib/Xss \
>+    xc/lib/Xt \
>+    xc/lib/Xtst \
>+    xc/lib/Xv \
>+    xc/lib/XvMC \
>+    xc/lib/Xxf86dga \
>+    xc/lib/Xxf86misc \
>+    xc/lib/Xxf86rush \
>+    xc/lib/Xxf86vm \
>+    xc/lib/apple \
>+    xc/lib/dmx \
>+    xc/lib/dps \
>+    xc/lib/dpstk \
>+    xc/lib/fontconfig \
>+    xc/lib/oldX \
>+    xc/lib/psres \
>+    xc/lib/xkbfile \
>+    xc/lib/xkbui \
>+    -type f
>+
>+  find \
>+    xc/lib/X11 \
>+      -type f |
>+    egrep -v "/Xlib.h|/Xresource.h|/Xutil.h|/cursorfont.h|/Xlibint.h|/Xresinternal.h" |
>+    egrep -v "/Xcms.h|/Xlocale.h|/XKBlib.h|/XrmI.h|/Xlcint.h|/Xrm.c|/Quarks.c" |
>+    egrep -v "/Imakefile"
>+
>+  # programs
>+  find \
>+    xc/programs/appres \
>+    xc/programs/bdftopcf \
>+    xc/programs/beforelight \
>+    xc/programs/bitmap \
>+    xc/programs/cxpm \
>+    xc/programs/dpsexec \
>+    xc/programs/dpsinfo \
>+    xc/programs/editres \
>+    xc/programs/fc-cache \
>+    xc/programs/fc-lang \
>+    xc/programs/fc-list \
>+    xc/programs/fonttosfnt \
>+    xc/programs/fslsfonts \
>+    xc/programs/fstobdf \
>+    xc/programs/glxinfo \
>+    xc/programs/iceauth \
>+    xc/programs/ico \
>+    xc/programs/lbxproxy \
>+    xc/programs/listres \
>+    xc/programs/luit \
>+    xc/programs/makepsres \
>+    xc/programs/mkcfm \
>+    xc/programs/oclock \
>+    xc/programs/proxymngr \
>+    xc/programs/rstart \
>+    xc/programs/setxkbmap \
>+    xc/programs/showfont \
>+    xc/programs/smproxy \
>+    xc/programs/sxpm \
>+    xc/programs/texteroids \
>+    xc/programs/twm \
>+    xc/programs/viewres \
>+    xc/programs/x11perf \
>+    xc/programs/xauth \
>+    xc/programs/xbiff \
>+    xc/programs/xcalc \
>+    xc/programs/xclipboard \
>+    xc/programs/xclock \
>+    xc/programs/xcmsdb \
>+    xc/programs/xconsole \
>+    xc/programs/xcursorgen \
>+    xc/programs/xditview \
>+    xc/programs/xdm \
>+    xc/programs/xdpyinfo \
>+    xc/programs/xdriinfo \
>+    xc/programs/xedit \
>+    xc/programs/xev \
>+    xc/programs/xeyes \
>+    xc/programs/xf86dga \
>+    xc/programs/xfd \
>+    xc/programs/xfindproxy \
>+    xc/programs/xfontsel \
>+    xc/programs/xfs \
>+    xc/programs/xfsinfo \
>+    xc/programs/xfwp \
>+    xc/programs/xgamma \
>+    xc/programs/xgc \
>+    xc/programs/xhost \
>+    xc/programs/xinit \
>+    xc/programs/xkbcomp \
>+    xc/programs/xkbevd \
>+    xc/programs/xkbprint \
>+    xc/programs/xkbutils \
>+    xc/programs/xkill \
>+    xc/programs/xload \
>+    xc/programs/xlogo \
>+    xc/programs/xlsatoms \
>+    xc/programs/xlsclients \
>+    xc/programs/xlsfonts \
>+    xc/programs/xmag \
>+    xc/programs/xman \
>+    xc/programs/xmessage \
>+    xc/programs/xmh \
>+    xc/programs/xmodmap \
>+    xc/programs/xmore \
>+    xc/programs/xprop \
>+    xc/programs/xrandr \
>+    xc/programs/xrdb \
>+    xc/programs/xrefresh \
>+    xc/programs/xrx \
>+    xc/programs/xset \
>+    xc/programs/xsetmode \
>+    xc/programs/xsetpointer \
>+    xc/programs/xsetroot \
>+    xc/programs/xsm \
>+    xc/programs/xstdcmap \
>+    xc/programs/xterm \
>+    xc/programs/xtrap \
>+    xc/programs/xvidtune \
>+    xc/programs/xvinfo \
>+    xc/programs/xwininfo  \
>+        -type f
>+
>+  # Xserver
>+  find \
>+    xc/programs/Xserver/hw/darwin \
>+    xc/programs/Xserver/hw/dmx \
>+    xc/programs/Xserver/hw/kdrive \
>+    xc/programs/Xserver/hw/sun \
>+    xc/programs/Xserver/hw/sunLynx \
>+    xc/programs/Xserver/hw/vfb \
>+    xc/programs/Xserver/hw/xfree86 \
>+    xc/programs/Xserver/hw/xnest \
>+    xc/programs/Xserver/hw/xwin \
>+        -type f | 
>+        egrep -v "/xf86_ansic.h|common/compiler.h" |
>+        egrep -v "/xf86_libc.h|/xf86Version.h|/xf86Date.h"
>+
>+  # fonts
>+  find \
>+    xc/fonts/bdf \
>+    xc/fonts/scaled -type f
>+
>+  # doc
>+  find \
>+    xc/doc/misc \
>+    xc/doc/specs \
>+    xc/doc/man/DMX \
>+    xc/doc/man/GL \
>+    xc/doc/man/GLU \
>+    xc/doc/man/GLw \
>+    xc/doc/man/X11 \
>+    xc/doc/man/Xau \
>+    xc/doc/man/Xext \
>+    xc/doc/man/Xi \
>+    xc/doc/man/Xp \
>+    xc/doc/man/Xt \
>+    xc/doc/man/Xv \
>+    xc/doc/man/misc \
>+    xc/doc/hardcopy/BDF \
>+    xc/doc/hardcopy/CTEXT \
>+    xc/doc/hardcopy/FSProtocol \
>+    xc/doc/hardcopy/ICCCM \
>+    xc/doc/hardcopy/ICE \
>+    xc/doc/hardcopy/RX \
>+    xc/doc/hardcopy/SM \
>+    xc/doc/hardcopy/X11 \
>+    xc/doc/hardcopy/XDMCP \
>+    xc/doc/hardcopy/XIM \
>+    xc/doc/hardcopy/XKB \
>+    xc/doc/hardcopy/XLFD \
>+    xc/doc/hardcopy/XProtocol \
>+    xc/doc/hardcopy/Xaw \
>+    xc/doc/hardcopy/Xext \
>+    xc/doc/hardcopy/Xi \
>+    xc/doc/hardcopy/Xmu \
>+    xc/doc/hardcopy/Xserver \
>+    xc/doc/hardcopy/Xt \
>+    xc/doc/hardcopy/Xv \
>+    xc/doc/hardcopy/i18n \
>+    xc/doc/hardcopy/man \
>+    xc/doc/hardcopy/rstart \
>+    xc/doc/hardcopy/saver \
>+    xc/doc/hardcopy/xfs \
>+    xc/doc/hardcopy/xterm \
>+    xc/doc/hardcopy/xtrans -type f
>+
>+  # misc
>+  echo "xc/README"
>+  echo "xc/README.crypto"
>+  echo "xc/BUILD"
>+  echo "xc/LABEL"
>+  echo "xc/RELNOTES"
>+) | egrep -v "/CVS/|_xp_disabled$" 
>+}
>+
>+case "$1" in
>+    'list')
>+        list_files
>+        ;;
>+    'rename')
>+        list_files | 
>+          while read i ; do 
>+              echo "# $i" ; 
>+              mv "$i" "${i}_xp_disabled" ;
>+          done
>+        ;;
>+    'delete')
>+        list_files | 
>+          while read i ; do 
>+              echo "# $i" ; 
>+              rm "$i"
>+          done
>+        ;;
>+    *)
>+        echo "${0}: Usage: ${0} [list] [rename] [delete]"
>+        ;;
>+esac
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/Imakefile branch/xc/packager/Imakefile
>--- base/xc/packager/Imakefile	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/Imakefile	2004-11-26 04:29:50.000000000 +0100
>@@ -0,0 +1,16 @@
>+XCOMM $Xorg: Imakefile,v 1.2 2003/01/20 15:05:12 gisburn Exp $
>+#define IHaveSubdirs 
>+#define PassCDebugFlags CDEBUGFLAGS="$(CDEBUGFLAGS)"
>+
>+# Compatibility for 007 and early 008 releases
>+make_xprint_tarball::
>+	cd tarball ; make make_xprint_tarball
>+
>+SUBDIRS = \
>+	tarball \
>+	rpm \
>+	solaris \
>+	mozilla_xpi
>+
>+MakeSubdirs($(SUBDIRS))
>+DependSubdirs($(SUBDIRS))
>diff -N -x '*CVS*' -r -u base/xc/packager/mozilla_xpi/Imakefile branch/xc/packager/mozilla_xpi/Imakefile
>--- base/xc/packager/mozilla_xpi/Imakefile	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/mozilla_xpi/Imakefile	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,11 @@
>+XCOMM $Xorg: Imakefile,v 1.1 2003/01/20 19:54:53 gisburn Exp $
>+
>+#if BuildMozillaXprintXPIPackage
>+make_mozilla_xpi::
>+	XPRINTDIR=$(XPRINTDIR) XBINDIR=$(BINDIR) XTOP=$(TOP) ; \
>+	export XPRINTDIR XBINDIR XTOP ; \
>+	/bin/ksh -e ./make_mozilla_xpi.sh
>+        
>+clean::
>+	$(RM) mozilla_xprint_xpi.xpi
>+#endif /* BuildMozillaXprintXPIPackage */
>diff -N -x '*CVS*' -r -u base/xc/packager/mozilla_xpi/K98xprint_xpi.sh branch/xc/packager/mozilla_xpi/K98xprint_xpi.sh
>--- base/xc/packager/mozilla_xpi/K98xprint_xpi.sh	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/mozilla_xpi/K98xprint_xpi.sh	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,22 @@
>+echo "# Stopping Xprint server"
>+
>+if [ -z "${MOZ_USER_DIR}" ] ; then
>+    echo "Internal error: MOZ_USER_DIR not set."
>+    exit 1
>+fi
>+
>+# Make sure we pick the right binary - users may share one profile
>+# between different architectures
>+uname_os="`uname -s`"
>+uname_cpu="`uname -p 2>/dev/null`" # uname -p may fail on old Debian
>+if [ "${uname_cpu}" = "unknown" -o "${uname_cpu}" = "" ] ; then
>+    uname_cpu="`uname -m`"
>+fi
>+
>+MOZXPSTARTSCRIPT="${HOME}/${MOZ_USER_DIR}/xprint_xpi/${uname_os}_${uname_cpu}/run_xprint_from_tarball.sh"
>+
>+if [ -f "${MOZXPSTARTSCRIPT}" ] ; then
>+    /bin/sh "${MOZXPSTARTSCRIPT}" stop
>+fi
>+
>+echo "# Done."
>diff -N -x '*CVS*' -r -u base/xc/packager/mozilla_xpi/S98xprint_xpi.sh branch/xc/packager/mozilla_xpi/S98xprint_xpi.sh
>--- base/xc/packager/mozilla_xpi/S98xprint_xpi.sh	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/mozilla_xpi/S98xprint_xpi.sh	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,39 @@
>+echo "# Starting Xprint server"
>+
>+if [ -z "${MOZ_USER_DIR}" ] ; then
>+    echo "Internal error: MOZ_USER_DIR not set."
>+    moz_startstop_addon_scripts stop
>+    exit 1
>+fi
>+
>+# Make sure we pick the right binary - users may share one profile
>+# between different architectures
>+uname_os="`uname -s`"
>+uname_cpu="`uname -p 2>/dev/null`" # uname -p may fail on old Debian
>+if [ "${uname_cpu}" = "unknown" -o "${uname_cpu}" = "" ] ; then
>+    uname_cpu="`uname -m`"
>+fi
>+
>+MOZXPSTARTSCRIPT="${HOME}/${MOZ_USER_DIR}/xprint_xpi/${uname_os}_${uname_cpu}/run_xprint_from_tarball.sh"
>+
>+if [ -f "${MOZXPSTARTSCRIPT}" ] ; then
>+    echo "# Starting Xprint server"
>+    /bin/sh "${MOZXPSTARTSCRIPT}" start
>+
>+    echo "# Populating XPSERVERLIST"
>+
>+    XPSERVERLIST="`/bin/sh "${MOZXPSTARTSCRIPT}" get_xpserverlist`"
>+    export XPSERVERLIST
>+
>+    echo "XPSERVERLIST=${XPSERVERLIST}"
>+
>+    if [ -z "${XPSERVERLIST}" ] ; then
>+        echo "Fatal error: XPSERVERLIST empty."
>+        moz_startstop_addon_scripts stop
>+        exit 1
>+    fi
>+else
>+    echo "# Warning: No Xprint XPI start script found for \"${uname_os}_${uname_cpu}\"."
>+fi
>+
>+echo "# Done."
>diff -N -x '*CVS*' -r -u base/xc/packager/mozilla_xpi/install.js branch/xc/packager/mozilla_xpi/install.js
>--- base/xc/packager/mozilla_xpi/install.js	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/mozilla_xpi/install.js	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,151 @@
>+// Install script for Xprint XPI
>+
>+var err;
>+
>+var regname="xprint";
>+var version="20040214";
>+  
>+err = initInstall("XprintXPI v0.0.2", // name for install UI
>+                  regname,            // registered name
>+                  version);           // package version
>+
>+logComment("initInstall: " + err);
>+
>+logComment("# Main start.");
>+doXpXPIInstall();
>+logComment("# Main done.");
>+
>+function doXpXPIInstall()
>+{
>+  var srDest = 16384; // Disk space required for installation (KB)
>+
>+  var fProgram           = getFolder("Program");
>+  var fComponents        = getFolder("Components");
>+  var userProfileBaseDir = getUserProfileBaseDir();
>+
>+  logComment("# fProgram:           '" + fProgram           + "'.");
>+  logComment("# fComponents:        '" + fComponents        + "'.");
>+  logComment("# userProfileBaseDir: '" + userProfileBaseDir + "'.");
>+
>+  /* Test whether Xprint's client side module was compiled-in (this is the
>+   * default for Mozilla builds, but Red Hat has turned it off... ;-( ) */
>+  var libgfxxprintPath = getFolder(fComponents, "libgfxxprint.so");
>+  logComment("# Checking whether '" + libgfxxprintPath + "' exists.");
>+  if (!File.exists(libgfxxprintPath)) {
>+    logComment("# libgfxxprint.so missing");
>+    alert("It seems that your version of Mozilla was build with --disable-xprint\n" +
>+          "which means the Xprint client support was EXPLICITLY TURNED OFF at build time.\n" + 
>+          "Please contact the creator of the Mozilla package to provide a build where this flag was not set.");
>+    cancelInstall(ACCESS_DENIED);
>+    return;
>+  }
>+
>+  /* Test whether we're running mozilla or something else */
>+  logComment("# Checking application type exists.");
>+  var is_mozilla     = File.exists(getFolder(fProgram, "mozilla-bin"));
>+  var is_firefox     = File.exists(getFolder(fProgram, "firefox-bin")) || File.exists(getFolder(fProgram, "firebird-bin"));
>+  var is_thunderbird = File.exists(getFolder(fProgram, "thunderbird-bin"));
>+  if ( (!is_mozilla) && (!is_firefox) && (!is_thunderbird)) {
>+    logComment("# unknown application type");
>+    alert("This XPI currently only supports Mozilla, FirdBird and ThunderBird.\n" +
>+          "Please contact file a bug at http://xprint.mozdev.org if you see this error.");
>+    cancelInstall(ACCESS_DENIED);
>+    return;
>+  }
>+
>+  /* Test whether this mozilla supports pluggable shell scripts */
>+  var init_d_readme_path = getFolder(fProgram, "init.d/README");
>+  logComment("# Checking whether '" + init_d_readme_path + "' exists.");
>+  if (!File.exists(init_d_readme_path)) {
>+    logComment("# init_d_readme_path missing");
>+    if (is_firefox) {
>+      alert("Your version of FireFox does not support pluggable shell scripts.\n" + 
>+            "You need at least FireFox 0.9 (or later).");
>+    }
>+    else if (is_thunderbird) {
>+      alert("Your version of ThunderBird does not support pluggable shell scripts.\n" + 
>+            "You need at least ThunderBird 0.6 (or later).");
>+    }
>+    else
>+    {
>+      alert("Your version of Mozilla does not support pluggable shell scripts.\n" + 
>+            "You need at least Mozilla 1.7a (or later).");
>+    }
>+    cancelInstall(ACCESS_DENIED);
>+    return;
>+  }
>+    
>+  /* Verify available disk space */
>+  if (!verifyDiskSpace(fProgram, srDest)) {
>+    logComment("# verifyDiskSpace failure.");
>+    cancelInstall(INSUFFICIENT_DISK_SPACE);
>+    return;
>+  }
>+  
>+  /* Add the files which should be installed */
>+  logComment("# addDirectory sequence begin.");       
>+  addDirectory(regname, version, "xprint_xpi", userProfileBaseDir, "xprint_xpi", true);
>+  addDirectory(regname, version, "init.d",     userProfileBaseDir, "init.d",     true);
>+  logComment("# addDirectory sequence end.");       
>+
>+  err = getLastError();
>+
>+  if (err == ACCESS_DENIED) {
>+    logComment("# ACCESS_DENIED");
>+    alert("Unable to write to directory " + userProfileBaseDir + ".\n" +
>+          "You will need to restart the browser with administrator/root " + 
>+          "privileges to install this software." +
>+          "After installing as root (or administrator), " + 
>+          "you will need to restart the browser one more time to " + 
>+          "register the installed software.\n After the second restart, " +
>+          "you can go back to running the browser without privileges!");
>+
>+    logComment("# cancelInstall(), ACCESS_DENIED");
>+    cancelInstall(ACCESS_DENIED);
>+    return;
>+  }
>+  else if (err != SUCCESS) {
>+    logComment("# cancelInstall(), err=" + err);
>+    cancelInstall(err);
>+    return;
>+  }
>+
>+  logComment("# performInstall()");
>+  performInstall();
>+}
>+
>+// this function verifies disk space in kilobytes
>+function verifyDiskSpace(dirPath, spaceRequired) {
>+  var spaceAvailable;
>+
>+  // Get the available disk space on the given path
>+  spaceAvailable = fileGetDiskSpaceAvailable(dirPath);
>+
>+  // Convert the available disk space into kilobytes
>+  spaceAvailable = parseInt(spaceAvailable / 1024);
>+
>+  // do the verification
>+  if(spaceAvailable < spaceRequired) {
>+    logComment("Insufficient disk space: " + dirPath);
>+    logComment("  required : " + spaceRequired  + " K");
>+    logComment("  available: " + spaceAvailable + " K");
>+    return false;
>+  }
>+
>+  return true;
>+}
>+
>+function getUserProfileBaseDir()
>+{
>+    var userPofileBaseDir;
>+    
>+    logComment("# getUserProfileBaseDir");
>+    
>+    userPofileBaseDir = getFolder("Profile", "../..");
>+
>+    logComment("# getUserProfileBaseDir='" + userPofileBaseDir + "'");
>+
>+    return userPofileBaseDir;
>+}
>+
>+/* EOF. */
>diff -N -x '*CVS*' -r -u base/xc/packager/mozilla_xpi/make_mozilla_xpi.sh branch/xc/packager/mozilla_xpi/make_mozilla_xpi.sh
>--- base/xc/packager/mozilla_xpi/make_mozilla_xpi.sh	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/mozilla_xpi/make_mozilla_xpi.sh	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,127 @@
>+#!/bin/ksh
>+
>+# Set search path for commands
>+export PATH=/usr/xpg4/bin:/usr/sbin:/usr/bin:/bin:/sbin
>+
>+set -x
>+set -e
>+
>+#XPRINTDIR=/usr/openwin/server/etc/XpConfig/
>+#XBINDIR=/usr/openwin/bin
>+
>+PKG_NAME="mozilla_xprint_xpi"
>+
>+PKG_FILES="/tmp/tmp_${PKG_NAME}"
>+
>+
>+if [ "${XPRINTDIR}" = "" ] ; then
>+    echo "$0: Error: XPRINTDIR not set"
>+    exit 1
>+fi
>+
>+if [ "${XBINDIR}" = "" ] ; then
>+    echo "$0: Error: XBINDIR not set"
>+    exit 1
>+fi
>+ 
>+
>+# Do not edit
>+# REL_* vars are paths relative to '/'
>+# Thanks to the "wonders" of some /bin/sh I cannot use ...
>+# REL_XPRINTDIR=${XPRINTDIR#*/}
>+# REL_XBINDIR=${XBINDIR#*/}
>+# ... ;-(
>+REL_XPRINTDIR="`echo ${XPRINTDIR} | sed 's/\///'`"
>+REL_XBINDIR="`echo ${XBINDIR} | sed 's/\///'`"
>+
>+
>+#### Main
>+
>+# Create and test tarball of files which should be in the final RPM...
>+if true ; then
>+echo "###### Fetching files from build dir..."
>+(
>+  # Go to xc/packager/tarball
>+  cd ../tarball
>+  # ${XPDESTTARFILE} is used by "make make_xprint_tarball"
>+  export XPDESTTARFILE="/tmp/xprint_pkg_`date +%y%m%d%H%M%S`.tar.gz"
>+  make make_xprint_tarball
>+
>+  # Check if the temp. tarball was being build
>+  if [ ! -f "${XPDESTTARFILE}" ] ; then
>+      echo "# temp. tarball missing."
>+      exit 1
>+  fi
>+
>+  # ... and then unpack the temp. tarball in the ${PKG_FILES} dir
>+  [ -d "${PKG_FILES}" ] && rm -Rf "${PKG_FILES}"
>+  mkdir "${PKG_FILES}"
>+  cd "${PKG_FILES}"
>+  gunzip -c ${XPDESTTARFILE} | tar -xf -
>+  rm -f ${XPDESTTARFILE}
>+  
>+  cd xprint/install
>+   
>+  # Remove old ReadMe
>+  rm -f ${REL_XPRINTDIR}/README
>+  # Remove docs we do not need in the XPI
>+  rm -Rf usr/X11R6/man
>+)
>+fi
>+
>+echo "###### Building pkgproto file..."
>+
>+
>+# Make sure we pick the right binary - users may share one profile
>+# between different architectures
>+uname_os="`uname -s`"
>+uname_cpu="`uname -p 2>/dev/null`" # uname -p may fail on old Debian
>+if [ "${uname_cpu}" = "unknown" -o "${uname_cpu}" = "" ] ; then
>+    uname_cpu="`uname -m`"
>+fi
>+
>+XPIDIR="${PKG_FILES}/xpi"
>+echo "XPIDIR=${XPIDIR}."
>+
>+mkdir -p "${XPIDIR}/xprint_xpi"
>+mkdir -p "${XPIDIR}/xprint_xpi/${uname_os}_${uname_cpu}"
>+(
>+  cd "${XPIDIR}/xprint_xpi"
>+  # FixME: Need softlinks for all compatible |uname_cpu| types
>+  case "${uname_cpu}" in
>+      "i386" | "i486" | "i586" | "i686" | "x86_64" | "athlon" | "Athlon")
>+          [ ! -d "${uname_os}_i386"   ] && ln -s "${uname_os}_${uname_cpu}" "${uname_os}_i386"
>+          [ ! -d "${uname_os}_i486"   ] && ln -s "${uname_os}_${uname_cpu}" "${uname_os}_i486"
>+          [ ! -d "${uname_os}_i586"   ] && ln -s "${uname_os}_${uname_cpu}" "${uname_os}_i586"
>+          [ ! -d "${uname_os}_i686"   ] && ln -s "${uname_os}_${uname_cpu}" "${uname_os}_i686"
>+          [ ! -d "${uname_os}_x86_64" ] && ln -s "${uname_os}_${uname_cpu}" "${uname_os}_x86_64"
>+          [ ! -d "${uname_os}_athlon" ] && ln -s "${uname_os}_${uname_cpu}" "${uname_os}_athlon"
>+          [ ! -d "${uname_os}_Athlon" ] && ln -s "${uname_os}_${uname_cpu}" "${uname_os}_Athlon"
>+          ;;
>+  esac    
>+)
>+mkdir -p "${XPIDIR}/init.d"
>+mv "${PKG_FILES}/xprint"/* "${XPIDIR}/xprint_xpi/${uname_os}_${uname_cpu}/."
>+cp "K98xprint_xpi.sh" "${XPIDIR}/init.d/."
>+cp "S98xprint_xpi.sh" "${XPIDIR}/init.d/."
>+chmod a+rx "${XPIDIR}/init.d"/*.sh
>+cp "install.js" "${XPIDIR}/."
>+
>+echo "###### Making package..."
>+
>+echo "#### zip..."
>+(
>+  OLDPWD="${PWD}"
>+  cd "${XPIDIR}"
>+  zip -r -y -9 "${OLDPWD}/${PKG_NAME}.xpi" .
>+)
>+
>+#echo "###### Cleaning up..."
>+rm -rf "${PKG_FILES}"
>+
>+echo "###### Package done:"
>+ls -lad "${PKG_NAME}.xpi"
>+
>+echo "###### Done."
>+exit 0
>+#
>diff -N -x '*CVS*' -r -u base/xc/packager/rpm/Imakefile branch/xc/packager/rpm/Imakefile
>--- base/xc/packager/rpm/Imakefile	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/rpm/Imakefile	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,3 @@
>+XCOMM $Xorg: Imakefile,v 1.1 2003/02/10 19:54:53 gisburn Exp $
>+       
>+XCOMM dummy for now
>diff -N -x '*CVS*' -r -u base/xc/packager/rpm/xprint.spec branch/xc/packager/rpm/xprint.spec
>--- base/xc/packager/rpm/xprint.spec	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/rpm/xprint.spec	2004-12-05 06:11:14.000000000 +0100
>@@ -0,0 +1,203 @@
>+%define name		xprint
>+%define version		20041204trunk
>+%define release		1.0.000
>+
>+Summary:	Xprint
>+Name:		%{name}
>+Version: 	%{version}
>+Release: 	%{release}
>+Copyright: 	MIT
>+Group: 		X11/Applications
>+URL: 		http://xprint.mozdev.org/
>+Source: 	xprint-%{version}.tar.gz
>+#BuildPrereq:    XFree86-devel
>+BuildRoot:	%{_tmppath}/%{name}-%{version}
>+Prefix:		%{_prefix}
>+Packager:       Roland Mainz <roland.mainz@nrubsig.org>
>+
>+%description
>+Xprint provides an advanched print API for X11-based
>+(incl. CDE, Xt/Motif-, Xt/LessTif-, Xt/Athena-, Qt- and
>+Mozilla-based) applications.
>+
>+%prep
>+
>+%setup -q -n xc
>+
>+%build
>+rm -f config/cf/host.def
>+echo '#define BuildXprintRPMPackage YES' >config/cf/host.def
>+echo '#include "xprint_host.def"'        >>config/cf/host.def
>+
>+make World
>+
>+%install
>+if [ -d ${RPM_BUILD_ROOT} ] ; then
>+    rm -rf ${RPM_BUILD_ROOT}
>+fi
>+mkdir -p ${RPM_BUILD_ROOT}
>+
>+# Create and test tarball of files which should be in the final RPM...
>+cd packager/
>+# ${XPDESTTARFILE} is used by "make make_xprint_tarball"
>+XPDESTTARFILE="/tmp/xprint_rpm_`date +%y%m%d%H%M%S`.tar.gz"
>+export XPDESTTARFILE
>+make make_xprint_tarball
>+
>+# Check if the temp. tarball was being build
>+if [ ! -f "${XPDESTTARFILE}" ] ; then
>+    echo "# temp. tarball missing."
>+    exit 1
>+fi
>+
>+# ... and then unpack the temp. tarball in the ${RPM_BUILD_ROOT} dir
>+cd ${RPM_BUILD_ROOT}
>+gunzip -c ${XPDESTTARFILE} | tar -xvf -
>+rm -f ${XPDESTTARFILE}
>+
>+# the tarball generation script puts the files which should be installed
>+# in the "install/" subdir. we strip the tarball README and the
>+# tarball-specific "run_xprint_from_tarball.sh" and then move all stuff
>+# in install/* to $PWD
>+rm -f xprint/run_xprint_from_tarball.sh
>+rm -f xprint/README
>+mv xprint/install/* .
>+rmdir xprint/install
>+rmdir xprint
>+
>+# remove obsolete README and SECURITY extension config "SecurityPolicy"
>+rm -f ${RPM_BUILD_ROOT}/etc/X11/xserver/xserver/README
>+rm -f ${RPM_BUILD_ROOT}/etc/X11/xserver/xserver/SecurityPolicy
>+
>+if [ ! -f ${RPM_BUILD_ROOT}/etc/X11/xserver/C/print/models/PSdefault/model-config ] ; then
>+    echo "# ERROR: ${RPM_BUILD_ROOT}/etc/X11/xserver/C/print/models/PSdefault/model-config missing."
>+    exit 1
>+fi
>+
>+%clean
>+rm -rf ${RPM_BUILD_ROOT}
>+
>+%post
>+if [ -x /usr/lib/lsb/install_initd ] ; then
>+    # (hopefully) LSB-compliant distribution
>+    /usr/lib/lsb/install_initd /etc/init.d/xprint
>+else
>+    if [ -f /etc/redhat-release ] ; then
>+        if [ $1 = 1 ]; then
>+            /sbin/chkconfig --add xprint
>+        fi
>+    else
>+        # SuSE(-like) ?
>+        if [ -d /etc/rc.d/rc2.d/ ] ; then
>+            echo "# Detected SuSE(-like) distribution"
>+            echo "# Creating links..."
>+            ln -sf ../xprint /etc/rc.d/rc2.d/K21xprint
>+            ln -sf ../xprint /etc/rc.d/rc2.d/S21xprint
>+            ln -sf ../xprint /etc/rc.d/rc3.d/K21xprint
>+            ln -sf ../xprint /etc/rc.d/rc3.d/S21xprint
>+
>+            # Older SuSE versions (like SuSE 6.4) do not have /etc/init.d/
>+            if [ ! -f /etc/rc.d/xprint ] ; then
>+                echo "# Creating old SuSE compatibility link..."
>+                ln -s /etc/init.d/xprint /etc/rc.d/xprint
>+            fi
>+        else
>+            # RedHat(-like) ?
>+            if [ -d "/etc/rc1.d" -a -d "/etc/init.d/" ] ; then
>+                echo "# Detected RedHat(-like) distribution"
>+                echo "# Creating links..."             
>+                ln -sf /etc/init.d/xprint /etc/rc.d/rc0.d/K61xprint
>+                ln -sf /etc/init.d/xprint /etc/rc.d/rc1.d/K61xprint
>+                ln -sf /etc/init.d/xprint /etc/rc.d/rc2.d/S61xprint
>+                ln -sf /etc/init.d/xprint /etc/rc.d/rc3.d/S61xprint
>+                ln -sf /etc/init.d/xprint /etc/rc.d/rc4.d/S61xprint
>+                ln -sf /etc/init.d/xprint /etc/rc.d/rc5.d/S61xprint
>+                ln -sf /etc/init.d/xprint /etc/rc.d/rc6.d/K61xprint
>+            else
>+                echo "# Unsupported version of Linux, cannot create links for /etc/init.d/."
>+                exit 1
>+            fi
>+        fi
>+    fi
>+fi
>+
>+echo "#"
>+echo "# Notes:"
>+echo "# 1. You have to start the Xprint servers using % /etc/init.d/xprint start #"
>+echo "#    and relogin (to populate the XPSERVERLIST env variable using"
>+echo "#    /etc/profile.d/xprint) before using any Xprint-based applications."
>+echo "# 2. Please consult the FAQ (/usr/doc/packages/xprint/Xprint_FAQ.txt)"
>+echo "#    or http://xprint.mozdev.org/ if there are any problems."
>+
>+%preun
>+if [ -x /usr/lib/lsb/remove_initd ] ; then
>+    # (hopefully) LSB-compliant distribution
>+    /usr/lib/lsb/remove_initd /etc/init.d/xprint
>+else
>+    if [ -f /etc/redhat-release ] ; then
>+        if [ $1 = 0 ]; then
>+            /sbin/service xprint stop >/dev/null 2>&1
>+            /sbin/chkconfig --del xprint
>+        fi
>+    else
>+        # SuSE(-like) ?
>+        if [ -d /etc/rc.d/rc2.d/ ] ; then
>+            echo "# Detected SuSE(-like) distribution"
>+            echo "# Removing links..."
>+            rm -f /etc/rc.d/rc2.d/K21xprint
>+            rm -f /etc/rc.d/rc2.d/S21xprint
>+            rm -f /etc/rc.d/rc3.d/K21xprint
>+            rm -f /etc/rc.d/rc3.d/S21xprint
>+
>+            # See comment above about old SuSE versions
>+            if [ -L /etc/rc.d/xprint ] ; then
>+                echo "# Removing old SuSE compatibility link..."
>+                rm -f /etc/rc.d/xprint
>+            fi
>+        else
>+            # RedHat(-like) ?
>+            if [ -d "/etc/rc1.d" -a -d "/etc/init.d/" ] ; then
>+                echo "# Detected RedHat(-like) distribution"
>+                echo "# Removing links..."             
>+                rm -f /etc/rc.d/rc0.d/K61xprint
>+                rm -f /etc/rc.d/rc1.d/K61xprint
>+                rm -f /etc/rc.d/rc2.d/S61xprint
>+                rm -f /etc/rc.d/rc3.d/S61xprint
>+                rm -f /etc/rc.d/rc4.d/S61xprint
>+                rm -f /etc/rc.d/rc5.d/S61xprint
>+                rm -f /etc/rc.d/rc6.d/K61xprint
>+            else
>+                echo "# Unsupported version of Linux, cannot remove links for /etc/init.d/."
>+                exit 1
>+            fi
>+        fi
>+    fi
>+fi
>+
>+%postun
>+if [ $1 -ge 1 ]; then
>+    /sbin/service xprint condrestart >/dev/null 2>&1
>+fi
>+
>+%files 
>+%defattr(-,root,root) 
>+%doc doc/hardcopy/XPRINT/Xprint_FAQ.html
>+%doc doc/hardcopy/XPRINT/Xprint_FAQ.txt
>+%doc doc/hardcopy/XPRINT/dtprint_fspec.ps
>+/etc/init.d/*
>+/etc/profile.d/*
>+/etc/X11/Xsession.d/92xprint-xpserverlist.sh
>+/etc/X11/xinit/xinitrc.d/92xprint-xpserverlist.sh
>+/usr/X11R6/bin/Xprt
>+/usr/X11R6/bin/xplsprinters
>+/usr/X11R6/bin/xprehashprinterlist
>+/usr/X11R6/bin/xphelloworld
>+/usr/X11R6/bin/xpxthelloworld
>+/usr/X11R6/bin/xpsimplehelloworld
>+/usr/X11R6/bin/pclcomp
>+/usr/X11R6/bin/xdpr
>+/usr/X11R6/bin/xpr
>+/etc/X11/xserver/*
>+/usr/X11R6/man/man1/*
>+/usr/X11R6/man/man7/*
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprint/Imakefile branch/xc/packager/solaris/GISWxprint/Imakefile
>--- base/xc/packager/solaris/GISWxprint/Imakefile	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprint/Imakefile	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,11 @@
>+XCOMM $Xorg: Imakefile,v 1.1 2003/01/20 19:54:53 gisburn Exp $
>+
>+#if BuildGISWxprint
>+make_GISWxprint::
>+	XPRINTDIR=$(XPRINTDIR) XBINDIR=$(BINDIR) XTOP=$(TOP) ; \
>+	export XPRINTDIR XBINDIR XTOP ; \
>+	/bin/ksh -e ../GISWxprintglue/make_solaris_pkg.sh "GISWxprint"
>+        
>+clean::
>+	$(RM) GISWxprint.tar.gz pkgproto.tmp
>+#endif /* BuildGISWxprint */
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprint/README branch/xc/packager/solaris/GISWxprint/README
>--- base/xc/packager/solaris/GISWxprint/README	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprint/README	2004-12-03 14:36:21.000000000 +0100
>@@ -0,0 +1,83 @@
>+README for GISWxprint (=Xprint server for Solaris) package
>+
>+This package contains the Xprint server side (e.g. server, startup and
>+configuration files) which are required to use Xprint-based applications
>+(like Mozilla, Firefox, Thunderbird, Eclipse, Motif2, Qt etc.)
>+
>+For futher information please consult the Xprint FAQ (available under
>+/opt/GISWxprint/docs/Xprint_FAQ.txt after installation - or see
>+http://xprint.mozdev.org/ for the newest version) and/or
>+http://xprint.mozdev.org/
>+
>+Installation requirements:
>+==========================
>+The following Solaris patches are REQUIRED to gurantee correct behaviour of
>+this package:
>+* Solaris 2.7/SPARC:
>+  106541-27   SunOS 5.7: Kernel Update Patch
>+  107443-17   SunOS 5.7: packaging utilities patch
>+  107650-08   OpenWindows 3.6.1 X11R6.4 Xprint Extension Patch
>+  107654-10   OpenWindows 3.6.1: X11R6.4 LBX & XRX Extensions Patch
>+  107656-11   OpenWindows 3.6.1 libXt Patch
>+  108376-44   OpenWindows 3.6.1: Xsun Patch
>+  115228-01   CDE 1.3: dtksh patch
>+* Solaris 2.7/x86:
>+  106542-27  SunOS 5.7_x86: Kernel Update Patch
>+  107444-17  SunOS 5.7_x86: packaging utilities patch
>+  107651-08  OpenWindows 3.6.1_x86: X11R6.4 Xprint Extension Patch
>+  107655-10  OpenWindows 3.6.1_x86: X11R6.4 LBX & XRX Extensions Patch
>+  107657-09  OpenWindows 3.6.1_x86: ERC X11R6.4 Extension Patch
>+  108377-39  OpenWindows 3.6.1_x86: Xsun Patch
>+
>+* Solaris 2.8/SPARC:
>+  108652-74   X11 6.4.1: Xsun patch
>+  108897-01   X11 6.4.1 Xprint patch
>+  110934-14   SunOS 5.8: pkgtrans, pkgadd, pkgchk, pkgmk and libpkg.a patch
>+  114956-02   CDE 1.4: dtksh patch
>+* Solaris 2.8/x86:
>+  108653-63   X11 6.4.1_x86: Xsun patch
>+  110934-14   SunOS 5.8: pkgtrans, pkgadd, pkgchk, pkgmk and libpkg.a patch
>+
>+* Solaris 2.9/SPARC:
>+  112785-26   X11 6.6.1: Xsun patch
>+  113713-03   SunOS 5.9: pkginstall Patch
>+* Solaris 2.9/x86:
>+  112786-15   X11 6.6.1_x86: Xsun patch
>+  114568-02   SunOS 5.9_x86: usr/sadm/install/bin/pkginstall Patch
>+
>+
>+Installation:
>+============
>+1. Install the package:
>+  % /usr/sbin/pkgadd -d GISWxprint.pkg
>+
>+2. Start Xprint server side:
>+  a) reboot
>+    or
>+  b) start the Xprint servers manually using
>+     % /etc/init.d/xprint start
>+     % sleep 30
>+     and restart your user CDE sessions (e.g. re-login.)
>+
>+3. Verification:
>+  After (re-)login into CDE the env variable ${XPSERVERLIST} should be
>+  set and
>+  % /opt/GISWxprint/bin/xplsprinters
>+  should list all available printer queues.
>+
>+
>+Deinstallation:
>+===============
>+1. Stop Xprint servers:
>+  % /etc/init.d/xprint stop
>+
>+2. Remove the package
>+  % /usr/sbin/pkgrm GISWxprint
>+
>+
>+Reporting bugs:
>+===============
>+Please send bug reports/comments/questions to 
>+mailto:roland.mainz@nrubsig.org or
>+mailto:xprint@mozdev.org
>+
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprint/depend branch/xc/packager/solaris/GISWxprint/depend
>--- base/xc/packager/solaris/GISWxprint/depend	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprint/depend	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,41 @@
>+# Copyright 2003-2004 Roland Mainz <roland.mainz@nrubsig.org>
>+# All Rights Reserved.
>+# Use is subject to license terms.
>+#
>+#	$Id: depend,v 1.3 2004/02/13 04:43:47 gisburn Exp $
>+#
>+# This package information file defines software dependencies associated
>+# with the pkg.  You can define three types of pkg dependencies with this file:
>+#	 P indicates a prerequisite for installation
>+#	 I indicates an incompatible package
>+#	 R indicates a reverse dependency
>+# <pkg.abbr> see pkginfo(4), PKG parameter
>+# <name> see pkginfo(4), NAME parameter
>+# <version> see pkginfo(4), VERSION parameter
>+# <arch> see pkginfo(4), ARCH parameter
>+# <type> <pkg.abbr> <name>
>+# 	(<arch>)<version>
>+# 	(<arch>)<version>
>+# 	...
>+# <type> <pkg.abbr> <name>
>+# ...
>+
>+P SUNWcsr	Core Solaris, (Root)
>+P SUNWxwplt	X Window System platform software
>+P SUNWpcu	SunSoft Print - Client, (usr)
>+P SUNWxcu4      XCU4 Utilities
>+P SUNWxwfnt     X Window System platform required fonts
>+P SUNWdtbas     CDE application basic runtime environment
>+
>+# "GISWxprint" is the full version (incl. Xprt binary; "GISWxprintglue"
>+# uses Solaris's own /usr/openwin/bin/Xprt instead) of the package
>+# (which installs it's own /etc/init.d/xprint)
>+I GISWxprintglue	Xprint server glue
>+# "GISWxprintcommon" may be used in the future for /etc/init.d/xprint and co.
>+I GISWxprintcommon
>+
>+# make sure we don't collide with the blastwave.org versions of these packages
>+I CSWxprint
>+I CSWxprintglue
>+I CSWxprintcommon
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprint/pkginfo branch/xc/packager/solaris/GISWxprint/pkginfo
>--- base/xc/packager/solaris/GISWxprint/pkginfo	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprint/pkginfo	2004-12-03 14:36:21.000000000 +0100
>@@ -0,0 +1,23 @@
>+#
>+# Copyright 2003-2004 Roland Mainz <roland.mainz@nrubsig.org>
>+# All Rights Reserved.
>+# Use is subject to license terms.
>+#
>+#ident	"$Id: pkginfo,v 1.4 2004/12/02 04:43:47 gisburn Exp $"
>+#
>+# This required package information file describes characteristics of the
>+# package, such as package abbreviation, full package name, package version,
>+# and package architecture.
>+#
>+PKG="GISWxprint"
>+NAME="Xprint server (full version)"
>+ARCH="sparc"
>+VERSION="1.0"
>+CATEGORY="system"
>+DESC="Xprint server"
>+VENDOR="xprint.mozdev.org"
>+HOTLINE="Please contact your local service provider"
>+EMAIL="xprint@mozdev.org"
>+CLASSES="none"
>+BASEDIR=/
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprint/postinstall branch/xc/packager/solaris/GISWxprint/postinstall
>--- base/xc/packager/solaris/GISWxprint/postinstall	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprint/postinstall	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,33 @@
>+#!/bin/sh
>+#
>+# Copyright 2003-2004 Roland Mainz <roland.mainz@nrubsig.org>
>+# All Rights Reserved.
>+# Use is subject to license terms.
>+#
>+#ident	"$Id: postinstall,v 1.2 2004/02/13 04:43:47 gisburn Exp $"
>+#
>+# postinstall for GISWxprint package
>+
>+print_package_usage()
>+{
>+cat <<'@EOF'
>+# To finish the installation please
>+#   a) reboot
>+#     or
>+#   b) start the Xprint servers manually using
>+#      % /etc/init.d/xprint start
>+#      % sleep 30
>+#      and restart your user CDE sessions (e.g. re-login.)
>+#
>+# Verification:
>+#   After login the env variable ${XPSERVERLIST} should be set and
>+#   % /opt/GISWxprint/bin/xplsprinters
>+#   should list all available printer queues.
>+@EOF
>+}
>+
>+# Print postinstall notice about the steps todo after installation
>+print_package_usage
>+
>+exit 0
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprint/preinstall branch/xc/packager/solaris/GISWxprint/preinstall
>--- base/xc/packager/solaris/GISWxprint/preinstall	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprint/preinstall	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,14 @@
>+#!/bin/sh
>+#
>+# Copyright 2003-2004 Roland Mainz <roland.mainz@nrubsig.org>
>+# All Rights Reserved.
>+# Use is subject to license terms.
>+#
>+#ident	"$Id: preinstall,v 1.2 2004/02/13 04:43:47 gisburn Exp $"
>+#
>+# preinstall for GISWxprint package
>+
>+# NO-OP for now
>+
>+exit 0
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprintglue/Imakefile branch/xc/packager/solaris/GISWxprintglue/Imakefile
>--- base/xc/packager/solaris/GISWxprintglue/Imakefile	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprintglue/Imakefile	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,11 @@
>+XCOMM $Xorg: Imakefile,v 1.1 2003/01/20 19:54:53 gisburn Exp $
>+
>+#if BuildGISWxprintglue
>+make_GISWxprintglue::
>+	XPRINTDIR=$(XPRINTDIR) XBINDIR=$(BINDIR) XTOP=$(TOP) ; \
>+	export XPRINTDIR XBINDIR XTOP ; \
>+	/bin/ksh -e ./make_solaris_pkg.sh "GISWxprintglue"
>+        
>+clean::
>+	$(RM) GISWxprintglue.tar.gz pkgproto.tmp
>+#endif /* BuildGISWxprintglue */
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprintglue/README branch/xc/packager/solaris/GISWxprintglue/README
>--- base/xc/packager/solaris/GISWxprintglue/README	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprintglue/README	2004-12-03 14:36:21.000000000 +0100
>@@ -0,0 +1,121 @@
>+README for GISWxprintglue (=Xprint glue for Solaris) package
>+
>+This package contains the Xprint glue (startup and configuration files)
>+which are currently missing in Solaris to use Xprint-based applications
>+(like Mozilla, Firefox, Thunderbird, Eclipse, Motif2, Qt etc.)
>+
>+For futher information please consult the Xprint FAQ (available under
>+/opt/GISWxprintglue/docs/Xprint_FAQ.txt after installation - or see
>+http://xprint.mozdev.org/ for the newest version) and/or
>+http://xprint.mozdev.org/
>+
>+Installation requirements:
>+==========================
>+The following Solaris patches are REQUIRED to gurantee correct behaviour of
>+this package:
>+* Solaris 2.7/SPARC:
>+  106541-27   SunOS 5.7: Kernel Update Patch
>+  107443-17   SunOS 5.7: packaging utilities patch
>+  107650-08   OpenWindows 3.6.1 X11R6.4 Xprint Extension Patch
>+  107654-10   OpenWindows 3.6.1: X11R6.4 LBX & XRX Extensions Patch
>+  107656-11   OpenWindows 3.6.1 libXt Patch
>+  108376-44   OpenWindows 3.6.1: Xsun Patch
>+  115228-01   CDE 1.3: dtksh patch
>+* Solaris 2.7/x86:
>+  106542-27  SunOS 5.7_x86: Kernel Update Patch
>+  107444-17  SunOS 5.7_x86: packaging utilities patch
>+  107651-08  OpenWindows 3.6.1_x86: X11R6.4 Xprint Extension Patch
>+  107655-10  OpenWindows 3.6.1_x86: X11R6.4 LBX & XRX Extensions Patch
>+  107657-09  OpenWindows 3.6.1_x86: ERC X11R6.4 Extension Patch
>+  108377-39  OpenWindows 3.6.1_x86: Xsun Patch
>+
>+* Solaris 2.8/SPARC:
>+  108652-74   X11 6.4.1: Xsun patch
>+  108897-01   X11 6.4.1 Xprint patch
>+  110934-14   SunOS 5.8: pkgtrans, pkgadd, pkgchk, pkgmk and libpkg.a patch
>+  114956-02   CDE 1.4: dtksh patch
>+* Solaris 2.8/x86:
>+  108653-63   X11 6.4.1_x86: Xsun patch
>+  110934-14   SunOS 5.8: pkgtrans, pkgadd, pkgchk, pkgmk and libpkg.a patch
>+
>+* Solaris 2.9/SPARC:
>+  112785-26   X11 6.6.1: Xsun patch
>+  113713-03   SunOS 5.9: pkginstall Patch
>+* Solaris 2.9/x86:
>+  112786-15   X11 6.6.1_x86: Xsun patch
>+  114568-02   SunOS 5.9_x86: usr/sadm/install/bin/pkginstall Patch
>+
>+
>+Installation:
>+============
>+1. Install the package:
>+  % /usr/sbin/pkgadd -d GISWxprintglue.pkg
>+
>+2. Start Xprint server side:
>+  a) reboot
>+    or
>+  b) start the Xprint servers manually using
>+     % /etc/init.d/xprint start
>+     % sleep 30
>+     and restart your user CDE sessions (e.g. re-login.)
>+
>+3. Verification:
>+  After (re-)login into CDE the env variable ${XPSERVERLIST} should be
>+  set and
>+  % /opt/GISWxprintglue/bin/xplsprinters
>+  should list all available printer queues.
>+
>+
>+Deinstallation:
>+===============
>+1. Stop Xprint servers:
>+  % /etc/init.d/xprint stop
>+
>+2. Remove the package
>+  % /usr/sbin/pkgrm GISWxprintglue
>+
>+
>+Known bugs/issues:
>+==================
>+- Printing may remove spaces when monotype fonts (like "-monotype-arial-*")
>+  are being used by the PostScript driver.
>+  This is a bug in the Solaris Xprint server binary (/usr/openwin/bin/Xprt).
>+
>+  Various bug reports have been filed, see
>+  - SunSolve bugid 4843234 
>+  - http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353 ("Solaris Xprt looses
>+    space when rendering with '-monotype-arial-*'-fonts")
>+  - http://bugzilla.mozilla.org/show_bug.cgi?id=199957 ("Solaris 8 Mozilla
>+    removes spaces for text within <font face="Arial">...</font>")
>+
>+  Solution:
>+    Please apply the patches listed in the section "Installation requirements"
>+    of this document.
>+  
>+  Known workarounds:
>+  - Remove the '-monotype-arial-*' fonts from the font path
>+  - Use an alternate Xprint server like available in the "GISWxprint" package
>+    (this package is identical to the "GISWxprintglue" package except that it
>+    uses a Xprint server build from xprint.mozdev.org sources and not the
>+    /usr/openwin/bin/Xprt binary from Solaris)
>+  - Mozilla-only: Adding
>+    -- snip --
>+    user_pref("print.xprint.font.rejectfontpattern",
>+    "fname=-dt-.*;scalable=.*;outline_scaled=false;xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*|" + 
>+    "fname=-monotype-arial.*;scalable=.*;outline_scaled=.*;xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*");
>+    -- snip --
>+    to prefs.js works around the problem (see
>+    http://bugzilla.mozilla.org/show_bug.cgi?id=199957#c6 , too).
>+
>+- Not all paper sizes defined in the "PSdefault" printer models may be
>+  available since the Xprint drivers(including the PostScript DDX) within
>+  Xprt will validate those lists against a buildin list and this list may
>+  not have been updated yet in Solaris's version of Xprt.
>+
>+
>+Reporting bugs:
>+===============
>+Please send bug reports/comments/questions to 
>+mailto:roland.mainz@nrubsig.org or
>+mailto:xprint@mozdev.org
>+
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprintglue/depend branch/xc/packager/solaris/GISWxprintglue/depend
>--- base/xc/packager/solaris/GISWxprintglue/depend	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprintglue/depend	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,41 @@
>+# Copyright 2003-2004 Roland Mainz <roland.mainz@nrubsig.org>
>+# All Rights Reserved.
>+# Use is subject to license terms.
>+#
>+#	$Id: depend,v 1.3 2004/02/13 04:43:47 gisburn Exp $
>+#
>+# This package information file defines software dependencies associated
>+# with the pkg.  You can define three types of pkg dependencies with this file:
>+#	 P indicates a prerequisite for installation
>+#	 I indicates an incompatible package
>+#	 R indicates a reverse dependency
>+# <pkg.abbr> see pkginfo(4), PKG parameter
>+# <name> see pkginfo(4), NAME parameter
>+# <version> see pkginfo(4), VERSION parameter
>+# <arch> see pkginfo(4), ARCH parameter
>+# <type> <pkg.abbr> <name>
>+# 	(<arch>)<version>
>+# 	(<arch>)<version>
>+# 	...
>+# <type> <pkg.abbr> <name>
>+# ...
>+
>+P SUNWcsr	Core Solaris, (Root)
>+P SUNWxwplt	X Window System platform software
>+P SUNWpcu	SunSoft Print - Client, (usr)
>+P SUNWxcu4      XCU4 Utilities
>+P SUNWxwfnt     X Window System platform required fonts
>+P SUNWdtbas     CDE application basic runtime environment
>+
>+# "GISWxprint" is the full version (incl. Xprt binary; "GISWxprintglue"
>+# uses Solaris's own /usr/openwin/bin/Xprt instead) of the package
>+# (which installs it's own /etc/init.d/xprint)
>+I GISWxprint	Xprint server (full version)
>+# "GISWxprintcommon" may be used in the future for /etc/init.d/xprint and co.
>+I GISWxprintcommon
>+
>+# make sure we don't collide with the blastwave.org versions of these packages
>+I CSWxprint
>+I CSWxprintglue
>+I CSWxprintcommon
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprintglue/make_solaris_pkg.sh branch/xc/packager/solaris/GISWxprintglue/make_solaris_pkg.sh
>--- base/xc/packager/solaris/GISWxprintglue/make_solaris_pkg.sh	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprintglue/make_solaris_pkg.sh	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,184 @@
>+#!/bin/ksh
>+
>+# Set search path for commands
>+export PATH=/usr/xpg4/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/dt/bin:/usr/openwin/bin
>+
>+#XPRINTDIR=/usr/openwin/server/etc/XpConfig/
>+#XBINDIR=/usr/openwin/bin
>+
>+case "$1" in
>+    'GISWxprintglue')
>+        PKG_NAME="GISWxprintglue"
>+        ;;
>+    'GISWxprint')
>+        PKG_NAME="GISWxprint"
>+        ;;
>+    *)
>+        echo "## Error illegal target"
>+        exit 1
>+        ;;
>+esac
>+
>+
>+PKG_FILES=/tmp/tmp_${PKG_NAME}
>+
>+
>+if [ "${XPRINTDIR}" = "" ] ; then
>+    echo "$0: Error: XPRINTDIR not set"
>+    exit 1
>+fi
>+
>+if [ "${XBINDIR}" = "" ] ; then
>+    echo "$0: Error: XBINDIR not set"
>+    exit 1
>+fi
>+ 
>+
>+# Do not edit
>+# REL_* vars are paths relative to '/'
>+# Thanks to the "wonders" of some /bin/sh I cannot use ...
>+# REL_XPRINTDIR=${XPRINTDIR#*/}
>+# REL_XBINDIR=${XBINDIR#*/}
>+# ... ;-(
>+REL_XPRINTDIR="`echo ${XPRINTDIR} | sed 's/\///'`"
>+REL_XBINDIR="`echo ${XBINDIR} | sed 's/\///'`"
>+
>+createpkgproto()
>+{
>+    pkgproto | 
>+    while read i1 i2 i3 i4 i5 ; do       
>+        if [ "${i1}" = "f" ] ; then
>+            if [ ! -r "${i3}" ] ; then
>+                echo "${0}: \"${i3}\" not found." >&2
>+                exit 1
>+            fi
>+        fi
>+    
>+        if [ "${i1}" = "d" -o -x "${i3}" ] ; then
>+            echo "$i1 $i2 $i3 0755"
>+        else
>+            echo "$i1 $i2 $i3"
>+        fi  
>+    done
>+}
>+
>+#### Main
>+
>+# Create and test tarball of files which should be in the final RPM...
>+if true ; then
>+echo "###### Fetching files from build dir..."
>+(
>+  # Go to xc/packager/tarball
>+  cd ../../tarball
>+  # ${XPDESTTARFILE} is used by "make make_xprint_tarball"
>+  export XPDESTTARFILE="/tmp/xprint_pkg_`date +%y%m%d%H%M%S`.tar.gz"
>+  make make_xprint_tarball
>+
>+  # Check if the temp. tarball was being build
>+  if [ ! -f "${XPDESTTARFILE}" ] ; then
>+      echo "# temp. tarball missing."
>+      exit 1
>+  fi
>+
>+  # ... and then unpack the temp. tarball in the ${PKG_FILES} dir
>+  [ -d "${PKG_FILES}" ] && rm -Rf "${PKG_FILES}"
>+  mkdir "${PKG_FILES}"
>+  cd "${PKG_FILES}"
>+  gunzip -c ${XPDESTTARFILE} | tar -xf -
>+  rm -f ${XPDESTTARFILE}
>+  
>+  cd xprint/install
>+   
>+  # Remove old ReadMe
>+  rm -f ${REL_XPRINTDIR}/README
>+  
>+  if [ "${PKG_NAME}" = "GISWxprintglue" ] ; then
>+    # Remove our own Xprt binary, Solaris has it's own working version
>+    # under /usr/openwin/bin/Xprt and the GISWxprintglue will use that
>+    # (only the "GISWxprint" package will ship it's own version of Xprt)
>+    rm -f ${REL_XBINDIR}/Xprt
>+  fi
>+)
>+fi
>+
>+echo "###### Building pkgproto file..."
>+
>+rm -f pkgproto.tmp
>+(
>+  OLD_PWD="${PWD}"
>+  cd "${PKG_FILES}/xprint/install"
>+
>+  # Add files in /etc but skip any dirs (they are part of SUNWcsr)
>+  # (and treat them all as executable)
>+  echo '!default 755 root bin'
>+  find etc '!' -type d -print | createpkgproto
>+
>+  # Add entry for package base dir ("/opt/GISWxprintglue" or "/opt/GISWxprint")
>+  echo "opt/${PKG_NAME}" | createpkgproto
>+
>+  # Add files in opt/${PKG_NAME}/bin (executables)
>+  echo '!default 755 root bin'
>+  find opt/${PKG_NAME}/bin -print | createpkgproto
>+
>+  # Add CDE/1.x glue
>+  find usr/dt/config/Xsession.d '!' -type d -print | createpkgproto
>+
>+  # Add config files in opt/${PKG_NAME}/server (all non-executable)
>+  echo '!default 644 root bin'
>+  find opt/${PKG_NAME}/server -print | createpkgproto
>+
>+  # Add Xfree86 encoding files for GISWxprint
>+  # (GISWxprintglue uses Solaris Xprt which uses the Solaris encoding/ttmap files)
>+  if [ "${PKG_NAME}" = "GISWxprint" ] ; then
>+    find opt/${PKG_NAME}/lib/X11/fonts/encodings -print | createpkgproto
>+  fi
>+
>+  # Add files in opt/${PKG_NAME}/man (manual pages)
>+  if [ -d opt/${PKG_NAME}/man ] ; then 
>+    echo '!default 644 root bin'
>+    find opt/${PKG_NAME}/man -print | createpkgproto
>+  fi
>+
>+  # Add FAQ, README etc.
>+  echo '!default 644 root bin'
>+  [ ! -d "opt/${PKG_NAME}/docs" ] && mkdirhier "opt/${PKG_NAME}/docs"
>+  cp "${OLD_PWD}/../../../doc/hardcopy/XPRINT/Xprint_FAQ.txt" opt/${PKG_NAME}/docs/.
>+  cp "${OLD_PWD}/README" opt/${PKG_NAME}/docs/.
>+  find opt/${PKG_NAME}/docs -print | createpkgproto
>+  
>+  # List package info files
>+  echo "# packaging files"
>+  echo "i pkginfo"
>+  echo "i depend"
>+  echo "i preinstall=./preinstall"
>+  echo "i postinstall=./postinstall"
>+) >pkgproto.tmp
>+ls -l pkgproto.tmp
>+
>+echo "###### Making package..."
>+[ -d "/tmp/${PKG_NAME}" ] && rm -R "/tmp/${PKG_NAME}"
>+
>+echo "#### pkgmk..."
>+pkgmk -f pkgproto.tmp -d /tmp -o -r "${PKG_FILES}/xprint/install" ${PKG_NAME}
>+
>+echo "#### pkgtrans..."
>+pwd
>+rm -f "./${PKG_NAME}.pkg"
>+pkgtrans /tmp "${PWD}/${PKG_NAME}.pkg" ${PKG_NAME}
>+
>+echo "#### compressing..."
>+rm -f "${PKG_NAME}.tar.gz"
>+tar -cvf - "${PKG_NAME}.pkg" README | gzip --best --stdout >"${PKG_NAME}.tar.gz"
>+rm -f "${PKG_NAME}.pkg"
>+
>+echo "###### Cleaning up..."
>+rm -rf "${PKG_FILES}"
>+rm -R "/tmp/${PKG_NAME}"
>+#rm -f pkgproto.tmp
>+
>+echo "###### Package done:"
>+ls -lad "${PKG_NAME}.tar.gz"
>+
>+echo "###### Done."
>+exit 0
>+#
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprintglue/pkginfo branch/xc/packager/solaris/GISWxprintglue/pkginfo
>--- base/xc/packager/solaris/GISWxprintglue/pkginfo	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprintglue/pkginfo	2004-12-03 14:36:21.000000000 +0100
>@@ -0,0 +1,23 @@
>+#
>+# Copyright 2003-2004 Roland Mainz <roland.mainz@nrubsig.org>
>+# All Rights Reserved.
>+# Use is subject to license terms.
>+#
>+#ident	"$Id: pkginfo,v 1.4 2004/12/02 04:43:47 gisburn Exp $"
>+#
>+# This required package information file describes characteristics of the
>+# package, such as package abbreviation, full package name, package version,
>+# and package architecture.
>+#
>+PKG="GISWxprintglue"
>+NAME="Xprint server glue"
>+ARCH="sparc"
>+VERSION="1.0"
>+CATEGORY="system"
>+DESC="Runtime glue for Solaris Xprint server"
>+VENDOR="xprint.mozdev.org"
>+HOTLINE="Please contact your local service provider"
>+EMAIL="xprint@mozdev.org"
>+CLASSES="none"
>+BASEDIR=/
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprintglue/postinstall branch/xc/packager/solaris/GISWxprintglue/postinstall
>--- base/xc/packager/solaris/GISWxprintglue/postinstall	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprintglue/postinstall	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,33 @@
>+#!/bin/sh
>+#
>+# Copyright 2003-2004 Roland Mainz <roland.mainz@nrubsig.org>
>+# All Rights Reserved.
>+# Use is subject to license terms.
>+#
>+#ident	"$Id: postinstall,v 1.2 2004/02/13 04:43:47 gisburn Exp $"
>+#
>+# postinstall for GISWxprintglue package
>+
>+print_package_usage()
>+{
>+cat <<'@EOF'
>+# To finish the installation please
>+#   a) reboot
>+#     or
>+#   b) start the Xprint servers manually using
>+#      % /etc/init.d/xprint start
>+#      % sleep 30
>+#      and restart your user CDE sessions (e.g. re-login.)
>+#
>+# Verification:
>+#   After login the env variable ${XPSERVERLIST} should be set and
>+#   % /opt/GISWxprintglue/bin/xplsprinters
>+#   should list all available printer queues.
>+@EOF
>+}
>+
>+# Print postinstall notice about the steps todo after installation
>+print_package_usage
>+
>+exit 0
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/GISWxprintglue/preinstall branch/xc/packager/solaris/GISWxprintglue/preinstall
>--- base/xc/packager/solaris/GISWxprintglue/preinstall	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/GISWxprintglue/preinstall	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,14 @@
>+#!/bin/sh
>+#
>+# Copyright 2003-2004 Roland Mainz <roland.mainz@nrubsig.org>
>+# All Rights Reserved.
>+# Use is subject to license terms.
>+#
>+#ident	"$Id: preinstall,v 1.4 2004/02/13 04:43:47 gisburn Exp $"
>+#
>+# preinstall for GISWxprintglue package
>+
>+# nothing here 
>+
>+exit 0
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/solaris/Imakefile branch/xc/packager/solaris/Imakefile
>--- base/xc/packager/solaris/Imakefile	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/solaris/Imakefile	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,10 @@
>+XCOMM $Xorg: Imakefile,v 1.1 2003/01/20 19:54:53 gisburn Exp $
>+#define IHaveSubdirs 
>+#define PassCDebugFlags CDEBUGFLAGS="$(CDEBUGFLAGS)"
>+
>+SUBDIRS = \
>+        GISWxprintglue \
>+        GISWxprint
>+
>+MakeSubdirs($(SUBDIRS))
>+DependSubdirs($(SUBDIRS))
>diff -N -x '*CVS*' -r -u base/xc/packager/tarball/Imakefile branch/xc/packager/tarball/Imakefile
>--- base/xc/packager/tarball/Imakefile	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/tarball/Imakefile	2004-12-04 00:13:15.000000000 +0100
>@@ -0,0 +1,12 @@
>+XCOMM $Xorg: Imakefile,v 1.1 2003/02/10 19:54:53 gisburn Exp $
>+
>+#if InstallXF86EncodingFiles
>+INSTALLXF86ENCODINGFILES=1
>+#else
>+INSTALLXF86ENCODINGFILES=0
>+#endif /* InstallXF86EncodingFiles */
>+
>+make_xprint_tarball::
>+	XPRINTDIR=$(XPRINTDIR) XBINDIR=$(BINDIR) XTOP=$(TOP) XMANPATH=$(MANPATH) XFONTENCPATH=$(ENCODINGSDIR) XINSTALLXF86ENCODINGFILES=$(INSTALLXF86ENCODINGFILES) ; \
>+	export XPRINTDIR XBINDIR XTOP XMANPATH XFONTENCPATH XINSTALLXF86ENCODINGFILES ; \
>+	$(SHELL) make_xprint_binary_tarball.sh
>diff -N -x '*CVS*' -r -u base/xc/packager/tarball/README_tarball branch/xc/packager/tarball/README_tarball
>--- base/xc/packager/tarball/README_tarball	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/tarball/README_tarball	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,121 @@
>+
>+Xprint server for Linux/AIX/IRIX README
>+
>+8th release of the Xprt (X11 print server) build from xprint.mozdev.org sources
>+
>+Disclaimer:
>+We do not guarantee that any source code or executable code available from the 
>+in this package is Year 2000 compliant, works in any way or may not eat your
>+harddisk alive.
>+
>+Please read the the Xprint_FAQ.txt how to configure Xprint.
>+
>+* Installation and usage 
>+  (short version, reading the Xprint_FAQ.txt first is better):
>+a) For the impatient, the hurry or if you do not have the "root"-password or if 
>+   you do not want to try this as "root":
>+     1. Unpack the tarball to your favourite dir:
>+       % mkdir /tmp/test_xprint
>+       % cd /tmp/test_xprint
>+       % gunzip -c xprint_linux_tarball.tar.gz | tar -xvf -
>+
>+     2. Start the Xprint server
>+        ("./run_xprint_from_tarball.sh" is a wrapper script
>+        for the "/etc/init.d/xprint" script which tells that script where the
>+        Xprint server files are currently be located.)
>+       % cd xprint
>+       % ./run_xprint_from_tarball.sh start
>+  
>+     3. Set the ${XPSERVERLIST} env var (and/or put this into your shell profile,
>+        do not forget to specify the _full_ path to the "run_xprint_from_tarball.sh"
>+        script):
>+       # sh
>+       % XPSERVERLIST="`./run_xprint_from_tarball.sh get_xpserverlist`"
>+       % export XPSERVERLIST
>+       
>+       # ksh/bash syntax
>+       % export XPSERVERLIST="$(./run_xprint_from_tarball.sh get_xpserverlist)"
>+
>+     4. Verifying that Xprint is running and working 
>+       (this is usually "done" by /usr/X11R6/bin/xplsprinters - but the
>+        "./run_xprint_from_tarball.sh" / "/etc/init.d/xprint" scripts provide
>+        a wrapper for that tool, too):
>+       % ./run_xprint_from_tarball.sh lsprinters
>+
>+     5. Run the application you want to use
>+       % /usr/local/bin/bin/mozilla
>+
>+     * Alternatively you can replace step [3] and [5] with:
>+       % ./run_xprint_from_tarball.sh wrapper /usr/local/bin/bin/mozilla
>+  
>+a) If you have adminstrator priviledges ("root") on your machine:
>+  # There are binary and source RPMs for Linux, *.deb packages for Debian and
>+  # *.pkg packages for Solaris available at http://xprint.mozdev.org,
>+  # the tarball installation is only for those platforms which are not coverd
>+  # by the list above or for those people who only want to run Xprint per-user
>+  # without installing it permanently <--
>+
>+  1. Make sure that you eliminate any existing Xfree86-based Xprt servers.
>+     All Xprt binares build from Xfree86 sources up to today are broken and
>+     will not work.
>+     Example:
>+     % which Xprt
>+     /usr/X11R6/bin/Xprt
>+     % mv /usr/X11R6/bin/Xprt /usr/X11R6/bin/Xprt_xf86_disabled
>+
>+  2. Copy the files in dist/usr into the matching dirs on your hard disk:
>+     Example:
>+     % (cd install; chmod -R og=u,og-w . ; tar -cf - usr etc) | (cd / ; tar -xf -)
>+
>+  3. Start X print server:
>+     % /etc/init.d/xprint start
>+
>+  4. Make the info available where the applications can find Xprint server(s):
>+     For all users (maybe in /etc/profile):
>+     % XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`"
>+     % export XPSERVERLIST
>+     (this step is optional for systems which support /etc/profile.d/ ; the tarball
>+     comes with /etc/profile.d/xprint.sh and /etc/profile.d/xprint.csh which will
>+     set the XPSERVERLIST env var for all users if the Xprint servers are running)
>+
>+    # Do not set $DISPLAY to the Xprt server. You still need your normal
>+    # Xserver for your video card(=framebuffer) - Xprt is only for your
>+    # printer(s).
>+
>+  5. Verifying that Xprint is running and working 
>+    % /usr/X11R6/bin/xplsprinters
>+      OR
>+    % ./run_xprint_from_tarball.sh lsprinters
>+
>+* Top two of the issues on Linux (all items from the FAQ):
>+  ("P"=problem, "B"=background, "S"=solution", "W"=Workaround)
>+  1. P: "Printing works but the printout is covers only 1/4 of the page"
>+     B: This is usually an indicator for a wrong DPI setting. The default
>+        "PSdefault" model config uses 300DPI but some printers use 600DPI.
>+     W: Edit ${XPCONFIGDIR}/C/print/attributes/document and replace the line
>+        "*default-printer-resolution: 300" with
>+        "*default-printer-resolution: 600"
>+     S: Create a model-config for your printer which only contains attributes
>+        supported by your printer (read the docs... :)
>+   
>+  2. P: "Printing works but I get large borders..."
>+     B: Same issue as issue [2] - wrong DPI
>+     S: Check the DPI value and adjust it as described in [2]. Common DPI
>+        values are 240, 300, 360, 400 and 600 DPI.
>+
>+More info will follow when I have time, take a look at the Xprint pages at
>+http://xprint.mozdev.org/ in the meantime...
>+
>+----
>+
>+Bye,
>+Roland
>+
>+-- 
>+  __ .  . __
>+ (o.\ \/ /.o) roland.mainz@nrubsig.org
>+  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
>+  /O /==\ O\  TEL +49 2426 901568 FAX +49 2426 901569
>+ (;O/ \/ \O;) 
>+
>+
>diff -N -x '*CVS*' -r -u base/xc/packager/tarball/make_xprint_binary_tarball.sh branch/xc/packager/tarball/make_xprint_binary_tarball.sh
>--- base/xc/packager/tarball/make_xprint_binary_tarball.sh	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/tarball/make_xprint_binary_tarball.sh	2004-11-26 04:29:51.000000000 +0100
>@@ -0,0 +1,356 @@
>+#!/bin/sh
>+#
>+# make_xprint_binary_tarball.sh - packager script for Xprint stuff
>+#
>+# $Xorg: make_xprint_binary_tarball.sh,v 1.2 2003/02/09 04:41:52 gisburn Exp $
>+#
>+# This script creates a binary tarball for Xprint stuff (Xprt, Xprt config
>+# files and Xprint helper applications.
>+#
>+# Written by Roland Mainz <roland.mainz@nrubsig.org>
>+#
>+
>+# These should be provided by Imakefile
>+#XTOP=..
>+#XPRINTDIR=/usr/openwin/lib/X11/xserver
>+#XBINDIR=/usr/openwin/bin
>+#
>+# XPDESTTARFILE may be optionally set as a command line argument to give the 
>+# destination filepath for the tarball, otherwise it will be found in /tmp.
>+# Note that the tarball is automatically compressed (to .gz, if gzip is
>+# available, otherwise to .Z); your name for XPDESTTARFILE should reflect this.
>+
>+PATH=/usr/bin:/bin:/usr/sbin:/sbin
>+if [ "`uname -s`" = "SunOS" ] ; then
>+    PATH=/usr/xpg4/bin:/usr/ccs/bin:${PATH}
>+fi
>+export PATH
>+
>+fatal_error()
>+{
>+    echo "${this_script}: ## FATAL ERROR: ${1}" 1>&2
>+    exit 1
>+}
>+
>+# Check if mandatory env vars have been set
>+[ "${XTOP}"                       = "" ] && fatal_error "XTOP env var not set."
>+[ "${XPRINTDIR}"                  = "" ] && fatal_error "XPRINTDIR env var not set."
>+[ "${XBINDIR}"                    = "" ] && fatal_error "XBINDIR env var not set."
>+[ "${XMANPATH}"                   = "" ] && fatal_error "XMANPATH env var not set."
>+[ "${XFONTENCPATH}"               = "" ] && fatal_error "XFONTENCPATH env var not set."
>+[ "${XINSTALLXF86ENCODINGFILES}"  = "" ] && fatal_error "XINSTALLXF86ENCODINGFILES env var not set."
>+
>+
>+# Do not edit
>+# REL_* vars are paths relative to '/'
>+# Thanks to the "wonders" of some /bin/sh I cannot use ...
>+# REL_XPRINTDIR=${XPRINTDIR#*/}
>+# REL_XBINDIR=${XBINDIR#*/}
>+# ... ;-(
>+REL_XPRINTDIR="`echo ${XPRINTDIR} | sed 's/\///'`"
>+REL_XBINDIR="`echo ${XBINDIR} | sed 's/\///'`"
>+REL_XMANPATH="`echo ${XMANPATH} | sed 's/\///'`"
>+REL_XFONTENCPATH="`echo ${XFONTENCPATH} | sed 's/\///'`"
>+
>+XPINSTALL_SESSION="`date +%y%m%d%H%M%S`"
>+XPINSTALLDIR_BASE=/tmp/xpinstall_${XPINSTALL_SESSION}
>+XPINSTALLDIR=${XPINSTALLDIR_BASE}/xprint
>+XPINSTALLDIR_X11=${XPINSTALLDIR}/install
>+XPLOGFILE=/tmp/xpinstall_${XPINSTALL_SESSION}.log
>+XPTARFILE=/tmp/xprint_server_${XPINSTALL_SESSION}.tar
>+
>+CURR_DIR="`pwd`"
>+
>+DO_BUILD=false
>+
>+# List of files/dirs which should be put into the tarball
>+if [ "`uname -s`" = "FreeBSD" ] ; then
>+  REL_XETCDIR="`echo ${XBINDIR} | sed 's/\///' | sed 's/bin/etc/'`"
>+else
>+  REL_XETCDIR="etc"
>+fi
>+BINFILELIST=" \
>+  xprint/install/${REL_XBINDIR}/Xprt \
>+  xprint/install/${REL_XBINDIR}/xplsprinters \
>+  xprint/install/${REL_XBINDIR}/xprehashprinterlist \
>+  xprint/install/${REL_XBINDIR}/xphelloworld \
>+  xprint/install/${REL_XBINDIR}/xpxthelloworld \
>+  xprint/install/${REL_XBINDIR}/xpsimplehelloworld \
>+  xprint/install/${REL_XBINDIR}/pclcomp \
>+  xprint/install/${REL_XBINDIR}/xdpr \
>+  xprint/install/${REL_XBINDIR}/xpr \
>+  xprint/install/${REL_XETCDIR} \
>+  xprint/install/${REL_XPRINTDIR} \
>+  xprint/install/${REL_XPRINTDIR}/C/print/models/PSdefault/fonts/fonts.dir \
>+  xprint/install/${REL_XPRINTDIR}/C/print/models/PSdefault/fonts/Courier.pmf \
>+  xprint/install/${REL_XPRINTDIR}/C/print/attributes/document \
>+  xprint/install/${REL_XPRINTDIR}/en_US/print/attributes/document \
>+  xprint/install/${REL_XMANPATH} \
>+  xprint/run_xprint_from_tarball.sh \
>+  xprint/README"
>+
>+# Solaris/CDE1.x || AIX/CDE extra files
>+if [ "`uname -s`" = "SunOS" -o "`uname -s`" = "AIX" ] ; then
>+  BINFILELIST="${BINFILELIST} \
>+    xprint/install/usr/dt/config/Xsession.d"
>+fi
>+
>+# Should we install our own copies of the XF86 encoding files ?
>+if [ ${XINSTALLXF86ENCODINGFILES} -eq 1 ] ; then
>+  BINFILELIST="${BINFILELIST} \
>+    xprint/install/${REL_XFONTENCPATH}"
>+fi
>+
>+# List of manual page names (suffix is omitted here since it differs
>+# from platform to platform)
>+MANPAGELIST=" \
>+  Xprint. \
>+  Xprt. \
>+  xplsprinters. \
>+  xprehashprinterlist. \
>+  xphelloworld \
>+  xpxthelloworld. \
>+  xpawhelloworld. \
>+  xpxmhelloworld. \
>+  xpsimplehelloworld. \
>+  pclcomp. \
>+  xdpr. \
>+  xpr."
>+
>+step=0
>+
>+umask 022
>+
>+inc_step_counter()
>+{
>+  step=`expr ${step} + 1`
>+}
>+
>+has_gzip()
>+{
>+  for i in `echo ${PATH} | tr ":" " "` 
>+  do
>+    if [ -x "${i}/gzip" ] ; then
>+      return 0
>+    fi
>+  done
>+
>+  return 1
>+}
>+
>+# Step 1:
>+# Build xc/ tree...
>+if ${DO_BUILD} ; then
>+  inc_step_counter
>+  echo "## Step ${step}: Building..."
>+  (
>+    (
>+      cd ${XTOP}
>+      if make World 2>&1 | tee -a buildlog.log >&${XPLOGFILE} ; then
>+        echo "Build OK."
>+      else
>+        echo "Build failed:"
>+        echo "-- snip --"
>+        tail ${XPLOGFILE}
>+        echo "-- snip --"
>+        exit 1
>+      fi
>+    )
>+  )
>+  echo "##         Build completed DONE."
>+fi # ${DO_BUILD}
>+
>+# Step 2:
>+# Verification...
>+inc_step_counter
>+echo "## Step ${step}: Verifying..."
>+(
>+  status=true
>+
>+  if [ ! -x ${XTOP}/programs/Xserver/Xprt ] ; then
>+    echo "error: X print server (${XTOP}/programs/Xserver/Xprt) binary missing."
>+    status=false
>+  fi
>+
>+  if [ ! -x ${XTOP}/programs/xplsprinters/xplsprinters ] ; then
>+    echo "error: ${XTOP}/programs/xplsprinters/xplsprinters binary missing."
>+    status=false
>+  fi
>+
>+  if [ ! -x ${XTOP}/programs/xprehashprinterlist/xprehashprinterlist ] ; then
>+    echo "error: ${XTOP}/programs/xprehashprinterlist/xprehashprinterlist binary missing."
>+    status=false
>+  fi
>+
>+  if [ ! -x ${XTOP}/programs/xphelloworld/xpxthelloworld/xpxthelloworld ] ; then
>+    echo "error: ${XTOP}/programs/xphelloworld/xpxthelloworld/xpxthelloworld binary missing."
>+    status=false
>+  fi
>+
>+  if [ ! -x ${XTOP}/programs/xphelloworld/xphelloworld/xphelloworld ] ; then
>+    echo "error: ${XTOP}/programs/xphelloworld/xphelloworld/xphelloworld binary missing."
>+    status=false
>+  fi
>+
>+  if [ ! -x ${XTOP}/programs/xphelloworld/xpsimplehelloworld/xpsimplehelloworld  ] ; then
>+    echo "error: ${XTOP}/programs/xphelloworld/xpsimplehelloworld/xpsimplehelloworld binary missing."
>+    status=false
>+  fi
>+
>+  if ${status} ; then
>+    echo "No errors found."
>+  else
>+    fatal_error "Verification failed."
>+  fi
>+)
>+[ $? != 0 ] && exit 1;
>+echo "##         Verification DONE."
>+
>+# Step 3:
>+# Install into temp. location
>+inc_step_counter
>+echo "## Step ${step}: Install into temporary location..."
>+(
>+  [ -d ${XPINSTALLDIR} ] && fatal_error "Temp. installation dir ${XPINSTALLDIR} already exists."
>+  mkdir -p ${XPINSTALLDIR}
>+  [ ! -d ${XPINSTALLDIR} ] && fatal_error "Could not create temp. installation dir ${XPINSTALLDIR}."
>+
>+  mkdir ${XPINSTALLDIR_X11}
>+  [ ! -d ${XPINSTALLDIR_X11} ] && fatal_error "Could not create temp. installation dir ${XPINSTALLDIR_X11}."
>+  
>+  (
>+    cd ${XTOP}
>+    
>+    # Install binaries, config files etc.
>+    if make install DESTDIR=${XPINSTALLDIR_X11} >>${XPLOGFILE} 2>&1 ; then
>+      echo "Installation (1/3) OK."
>+    else
>+      echo "Installation (1/3) failed:"
>+      echo "-- snip --"
>+      tail ${XPLOGFILE}
>+      echo "-- snip --"
>+      exit 1
>+    fi
>+    
>+    # Install manual pages...
>+    if make install.man DESTDIR=${XPINSTALLDIR_X11} >>${XPLOGFILE} 2>&1 ; then
>+      echo "Installation (2/3) OK."
>+    else
>+      echo "Installation (2/3) failed:"
>+      echo "-- snip --"
>+      tail ${XPLOGFILE}
>+      echo "-- snip --"
>+      exit 1
>+    fi
>+    
>+    # Copy tarball startxprint.sh and README_tarball
>+    cp "${CURR_DIR}/README_tarball" "${XPINSTALLDIR}/README"
>+    cp "${CURR_DIR}/startxprint.sh" "${XPINSTALLDIR}/run_xprint_from_tarball.sh"
>+    chmod a+rx "${XPINSTALLDIR}/run_xprint_from_tarball.sh"
>+    echo "Installation (3/3) OK."
>+    
>+    # Search the ${XPINSTALLDIR_X11}/${REL_XMANPATH} dir for manual pages which
>+    # do not occur in the ${MANPAGELIST} list and remove those files
>+    cd ${XPINSTALLDIR_X11}/${REL_XMANPATH}
>+    for i in */*.* ; do
>+      NO_MATCH="true"
>+      
>+      for j in ${MANPAGELIST} ; do
>+        [ "`echo "${i}" | fgrep "${j}"`" != "" ] && NO_MATCH="false"
>+      done
>+      
>+      if ${NO_MATCH} ; then 
>+        rm -f "${i}"
>+      fi
>+    done
>+  )
>+)
>+[ $? != 0 ] && exit 1;
>+echo "##         Temp. installation DONE."
>+
>+# Step 4:
>+# Verify installation
>+inc_step_counter
>+echo "## Step ${step}: Verifying installation..."
>+(
>+  # Part 1: Test for missing files
>+  cd ${XPINSTALLDIR_BASE}
>+  status=true
>+  for i in ${BINFILELIST} ; do
>+    if [ ! -r ${i} ] ; then
>+      echo "File ${i} missing."
>+      status=false
>+    fi
>+  done
>+  
>+  # Part 2: Test "PSdefault" printer model
>+  cd ${XPINSTALLDIR_BASE}
>+  x=`cat "xprint/install/${REL_XPRINTDIR}/C/print/models/PSdefault/fonts/fonts.dir" | wc -l`
>+  if [ "$x" -ne 31 ] ; then
>+    echo "PSdefault model fonts.dir misses font entries."
>+    status=false
>+  fi
>+  
>+  if ${status} ; then
>+    echo "No errors found."
>+  else
>+    fatal_error "Verification failed."
>+  fi
>+)
>+[ $? != 0 ] && exit 1;
>+echo "##        Verification of installation DONE."
>+
>+# Step 5.a:
>+# Create binary tarball
>+inc_step_counter
>+echo "## Step ${step}: Create binary tarball..."
>+(
>+  cd ${XPINSTALLDIR_BASE}
>+  if has_gzip ; then
>+    tar -cf - ${BINFILELIST} | gzip --best --stdout >${XPTARFILE}.gz
>+  else
>+    tar -cf - ${BINFILELIST} | compress >${XPTARFILE}.Z
>+  fi
>+)
>+[ $? != 0 ] && exit 1;
>+echo "##        Binary tarball creation DONE."
>+
>+# Step 5.b:
>+# Copy binary tarball to destination, if required.
>+if [ "${XPDESTTARFILE}" != "" ] ; then
>+    inc_step_counter
>+    echo "## Step ${step}: Copying binary tarball to destination..."
>+    (
>+    if has_gzip ; then
>+	mv ${XPTARFILE}.gz ${XPDESTTARFILE}
>+    else
>+	mv ${XPTARFILE}.Z ${XPDESTTARFILE}
>+    fi
>+    )
>+    echo "##        Copying tarball to destination DONE."
>+fi
>+
>+# Step 6:
>+# Cleaning up
>+inc_step_counter
>+echo "## Step ${step}: Cleaning up..."
>+(
>+  # Be carefull... =:-)
>+  if [ "${XPINSTALLDIR_BASE}" != "/" ] ; then
>+    rm -Rf ${XPINSTALLDIR_BASE}
>+  fi
>+)
>+echo "##        Cleanup done."
>+
>+
>+# Done.
>+echo "#### Binary tarball is now available at "
>+if [ "${XPDESTTARFILE}" != "" ] ; then
>+    ls -l ${XPDESTTARFILE}*
>+else
>+    ls -l ${XPTARFILE}*
>+fi
>+echo "#### All done."
>+
>+exit 0
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/packager/tarball/startxprint.sh branch/xc/packager/tarball/startxprint.sh
>--- base/xc/packager/tarball/startxprint.sh	1970-01-01 01:00:00.000000000 +0100
>+++ branch/xc/packager/tarball/startxprint.sh	2004-12-03 03:58:30.000000000 +0100
>@@ -0,0 +1,85 @@
>+#!/bin/sh
>+#
>+# Copyright (c) 2003-2004 by Roland Mainz <roland.mainz@nrubsig.org>
>+# All rights reserved.
>+#
>+#ident  "@(#)startxprint.sh   0.1    2003/02/08 gisburn"
>+#
>+# (Hack-like) wrapper script to use /etc/init.d/xprint directly from a
>+# tarball without the need to be "root" nor to do any special installation
>+# steps
>+#
>+############################################################################
>+
>+# Force use of a POSIX conformant sh 
>+# (Solaris /sbin/sh is plain Bourne shell)
>+[ "$1" != "posix_sh_forced" -a -x /usr/dt/bin/dtksh  ]   && exec /usr/dt/bin/dtksh  "$0" posix_sh_forced "$@"
>+[ "$1" != "posix_sh_forced" -a -x /bin/ksh93  ]          && exec /bin/ksh93  "$0" posix_sh_forced "$@"
>+[ "$1" != "posix_sh_forced" -a -x /bin/ksh  ]            && exec /bin/ksh  "$0" posix_sh_forced "$@"
>+[ "$1" != "posix_sh_forced" -a -x /bin/bash ]            && exec /bin/bash "$0" posix_sh_forced "$@"
>+[ "$1" != "posix_sh_forced" -a -x /usr/local/bin/ksh93 ] && exec /usr/local/bin/ksh93 "$0" posix_sh_forced "$@"
>+[ "$1" != "posix_sh_forced" -a -x /usr/local/bin/ksh ]   && exec /usr/local/bin/ksh "$0" posix_sh_forced "$@"
>+[ "$1" != "posix_sh_forced" -a -x /usr/local/bin/bash ]  && exec /usr/local/bin/bash "$0" posix_sh_forced "$@"
>+if [ "$1" != "posix_sh_forced" ] ; then
>+    echo "${0}: ## FATAL ERROR: No POSIX-shell found."  1>&2
>+    exit 1
>+fi
>+
>+
>+shift # Drop "posix_sh_forced"
>+
>+PATH=/usr/sbin:/usr/bin:/sbin:/bin
>+export PATH
>+
>+fatal_error()
>+{
>+    echo "${this_script}: ## FATAL ERROR: ${1}" 1>&2
>+    exit 1
>+}
>+
>+relpath2abspath()
>+{
>+    (
>+      dirpart="`dirname "${1}"`"
>+      basepart="`basename "${1}"`"
>+    
>+      echo "`cd "${dirpart}" ; pwd`/${basepart}"
>+    )
>+    return 0
>+}
>+
>+##### main
>+this_script="$(relpath2abspath "${0}")"
>+unpackdir="$(dirname "${this_script}")/install"
>+if [ -d ${unpackdir}/usr/X11R6/etc/rc.d ]; then
>+xinitdir="usr/X11R6/etc/rc.d"
>+else
>+xinitdir="etc/init.d"
>+fi
>+
>+## prechecks
>+[ ! -d "${unpackdir}/usr"               ] && fatal_error "${unpackdir}/usr not found"
>+[ ! -r "${unpackdir}/${xinitdir}/xprint" ] && fatal_error "${unpackdir}/${xinitdir}/xprint not found"
>+
>+xprt_path="$(find "${unpackdir}" -name Xprt -print)"
>+xplsprinters_path="$(find "${unpackdir}" -name xplsprinters -print)"
>+psdefault_path="$(find "${unpackdir}" -name PSdefault -print)"
>+xf86encodingsdir_path="$(find "${unpackdir}" -name encodings.dir -print | fgrep -v /large)"
>+
>+[ "${psdefault_path}"         = "" ] && fatal_error "no PSdefault model found in ${unpackdir}"
>+[ "${xprt_path}"              = "" ] && fatal_error "no Xprt binary found in ${unpackdir}"
>+[ "${xplsprinters_path}"      = "" ] && fatal_error "no xplsprinters binary found in ${unpackdir}"
>+[ ! -r "${psdefault_path}"         ] && fatal_error "PSdefault model \"${psdefault_path}\" found in ${unpackdir} not accessible"
>+[ ! -x "${xprt_path}"              ] && fatal_error "Xprt binary \"${xprt_path}\" found in ${unpackdir} not accessible/executable"
>+
>+xpconfig_dir="${psdefault_path%*/C/print/models/PSdefault}"
>+
>+# run the "/etc/init.d/xprint start" using the binaries/config files/scripts in the tarball
>+ETC_INITD_XPRINT_XPRT_PATH="${xprt_path}"
>+ETC_INITD_XPRINT_XPLSPRINTERS_PATH="${xplsprinters_path}"
>+ETC_INITD_XPRINT_XPCONFIGDIR="${xpconfig_dir}"
>+ETC_INITD_XPRINT_XF86ENCODINGSDIR="${xf86encodingsdir_path}"
>+export ETC_INITD_XPRINT_XPRT_PATH ETC_INITD_XPRINT_XPCONFIGDIR ETC_INITD_XPRINT_XPLSPRINTERS_PATH ETC_INITD_XPRINT_XF86ENCODINGSDIR
>+/bin/sh "${unpackdir}/${xinitdir}/xprint" "$@"
>+
>+# EOF.
>diff -N -x '*CVS*' -r -u base/xc/programs/Imakefile branch/xc/programs/Imakefile
>--- base/xc/programs/Imakefile	2004-10-31 03:14:05.000000000 +0100
>+++ branch/xc/programs/Imakefile	2004-11-26 04:29:51.000000000 +0100
>@@ -133,26 +133,8 @@
> SUBDIRS = $(XSSRCDIR)
> #else
> SUBDIRS = \
>-	appres bdftopcf bitmap \
>-	$(SCREENSAVESRCDIR) editres $(FCDIRS) $(FCLANGDIR) fslsfonts fstobdf \
>-	iceauth ico listres luit \
>-	$(MAKEPSRESDIR) $(DPSCLIENTDIRS) $(DBECLIENTDIRS) \
>-	$(MKCFMSRCDIR) \
>-	mkfontdir $(MKFONTSCALEDIR) oclock $(PROXYMGRSRCDIR) \
>-	$(RGBSRCDIR) $(RSTARTSRCDIR) showfont \
>-	$(SMPROXYSRCDIR) $(TWMSRCDIR) viewres x11perf xauth xbiff xcalc \
>-	xclipboard xclock \
>-	xcmsdb $(XCONSOLESRCDIR) xditview $(XDMSRCDIR) xdpyinfo \
>-	$(XF86DGASRCDIR) xedit xev xeyes xfd xfontsel $(XFSSRCDIR) xfsinfo \
>-	$(XFINDPROXYSRCDIR) $(XFWPSRCDIR) $(XGAMMASRCDIR) xgc $(XHOSTSRCDIR) \
>-	$(XINITSRCDIR) $(XKBSRCDIRS) xkill $(XLOADDIR) xlogo xlsatoms \
>-	xlsclients xlsfonts xmag xman xmessage xmh xmodmap $(XMORE) xprop \
>-	xrdb xrefresh $(XRXSRCDIR) xset \
>-	xsetroot $(XSMSRCDIR) xstdcmap $(XINPUTCLIENTDIRS) \
>-	$(XTERMSRCDIR) $(XTRAPCLIENTDIRS) $(XVIDTUNESRCDIR) xwd xwininfo xwud \
>-	$(XPMCLIENTDIRS) $(XVINFOSRCDIR) $(XPRASTERFILTERDIRS) \
>-	$(XSSRCDIR) $(XASSRCDIR) $(LBXPROXYSRCDIR) $(XPSRCDIRS) $(SCRIPTSDIR) \
>-	$(GLXCLIENTDIRS) $(XRANDRDIR) $(XCURSORGENDIR) $(XDRIINFO)
>+	mkfontdir $(MKFONTSCALEDIR) $(XPRASTERFILTERDIRS) \
>+	$(XSSRCDIR) $(XPSRCDIRS) $(SCRIPTSDIR)
> #endif
> 
> MakeSubdirs($(SUBDIRS))
>diff -N -x '*CVS*' -r -u base/xc/programs/Xserver/Xprint/Imakefile branch/xc/programs/Xserver/Xprint/Imakefile
>--- base/xc/programs/Xserver/Xprint/Imakefile	2004-11-25 23:42:51.000000000 +0100
>+++ branch/xc/programs/Xserver/Xprint/Imakefile	2004-11-26 10:45:46.000000000 +0100
>@@ -128,16 +128,9 @@
> 
> 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 */
>diff -N -x '*CVS*' -r -u base/xc/programs/Xserver/Xprint/Xprint.html branch/xc/programs/Xserver/Xprint/Xprint.html
>--- base/xc/programs/Xserver/Xprint/Xprint.html	2004-10-08 04:39:40.000000000 +0200
>+++ branch/xc/programs/Xserver/Xprint/Xprint.html	1970-01-01 01:00:00.000000000 +0100
>@@ -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>
>diff -N -x '*CVS*' -r -u base/xc/programs/Xserver/Xprint/Xprint.man branch/xc/programs/Xserver/Xprint/Xprint.man
>--- base/xc/programs/Xserver/Xprint/Xprint.man	2004-10-08 04:39:40.000000000 +0200
>+++ branch/xc/programs/Xserver/Xprint/Xprint.man	1970-01-01 01:00:00.000000000 +0100
>@@ -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.
>diff -N -x '*CVS*' -r -u base/xc/programs/Xserver/Xprint/Xprint.sgml branch/xc/programs/Xserver/Xprint/Xprint.sgml
>--- base/xc/programs/Xserver/Xprint/Xprint.sgml	2004-10-08 04:39:40.000000000 +0200
>+++ branch/xc/programs/Xserver/Xprint/Xprint.sgml	1970-01-01 01:00:00.000000000 +0100
>@@ -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>
>-
>diff -N -x '*CVS*' -r -u base/xc/programs/Xserver/Xprint/ps/PsInit.c branch/xc/programs/Xserver/Xprint/ps/PsInit.c
>--- base/xc/programs/Xserver/Xprint/ps/PsInit.c	2004-10-14 04:20:52.000000000 +0200
>+++ branch/xc/programs/Xserver/Xprint/ps/PsInit.c	2004-12-05 06:16:09.000000000 +0100
>@@ -262,7 +262,7 @@
>   /* StaticGray, 1bit */
>   visuals[nv].vid             = FakeClientID(0);
>   visuals[nv].class           = StaticGray;
>-  visuals[nv].bitsPerRGBValue = 8;
>+  visuals[nv].bitsPerRGBValue = 1;
>   visuals[nv].ColormapEntries = 2;
>   visuals[nv].nplanes         = 1;
>   visuals[nv].redMask         = 0x0;
>diff -N -x '*CVS*' -r -u base/xc/programs/Xserver/miext/damage/damagestr.h branch/xc/programs/Xserver/miext/damage/damagestr.h
>--- base/xc/programs/Xserver/miext/damage/damagestr.h	2004-08-12 00:40:14.000000000 +0200
>+++ branch/xc/programs/Xserver/miext/damage/damagestr.h	2004-11-26 11:02:41.000000000 +0100
>@@ -26,7 +26,9 @@
> #define _DAMAGESTR_H_
> 
> #include "damage.h"
>-#include "picturestr.h"
>+#ifdef RENDER
>+# include "picturestr.h"
>+#endif
> 
> typedef struct _damage {
>     DamagePtr		pNext;

Actions: View | Splinter Review

Attachments on bug 1923: 1375 | 1376 | 1377 | 1378 | 1380 | 1381 | 1382 | 1449 | 1455 | 1460 | 1475 | 1479 | 1558

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.