diff options
| author | Alexander Gottwald <alexander.gottwald@s1999.tu-chemnitz.de> | 2005-02-11 10:53:13 +0000 |
|---|---|---|
| committer | Alexander Gottwald <alexander.gottwald@s1999.tu-chemnitz.de> | 2005-02-11 10:53:13 +0000 |
| commit | e4677a8b8a672028f0b75b90a66d70dba92a02fe (patch) | |
| tree | 977328dd207b90482f3d9f1301d2fa170b70e214 | |
| parent | c5e0b1719ee1474bc9581d0c6df83e182d1d5705 (diff) | |
Import changes from XORG-6.8.2CYGWIN-6_8_2-MERGECYGWIN
| -rw-r--r-- | hardcopy/XPRINT/Xprint_FAQ.html | 150 | ||||
| -rw-r--r-- | hardcopy/XPRINT/Xprint_FAQ.txt | 12 | ||||
| -rw-r--r-- | hardcopy/XPRINT/Xprint_FAQ.xml | 34 | ||||
| -rw-r--r-- | man/general/Xprint.man | 421 | ||||
| -rw-r--r-- | man/general/Xprint.sgml | 627 | ||||
| -rw-r--r-- | sgml/OpenBSD.sgml | 162 | ||||
| -rw-r--r-- | sgml/README.sgml | 2 | ||||
| -rw-r--r-- | sgml/RELNOTES.sgml | 240 | ||||
| -rw-r--r-- | sgml/Solaris.sgml | 7 |
9 files changed, 1332 insertions, 323 deletions
diff --git a/hardcopy/XPRINT/Xprint_FAQ.html b/hardcopy/XPRINT/Xprint_FAQ.html index 52b24d0..e65756b 100644 --- a/hardcopy/XPRINT/Xprint_FAQ.html +++ b/hardcopy/XPRINT/Xprint_FAQ.html @@ -3,7 +3,7 @@ </p><p> Version: 0.9.1 </p><p> - Last-Modified: 2004/06/14 08:15:16 + Last-Modified: 2004/10/08 01:05:21 </p><p> Maintained-by: <span class="othercredit"><span class="firstname">Roland</span> <span class="surname">Mainz</span></span> @@ -289,48 +289,48 @@ pkgadd: ERROR: no packages were found in </var/tmp/dstreAAA5Jayyz> What is going wrong here ? </a></dt><dt>Q: <a href="#id2882791"> What is XpStartDoc for ? - </a></dt><dt>Q: <a href="#id2882881"> + </a></dt><dt>Q: <a href="#id2882887"> How does the XLFD for printer-builtin fonts look like ? / How can I find/identify printer-builtin fonts ? - </a></dt><dt>Q: <a href="#id2882955"> + </a></dt><dt>Q: <a href="#id2882960"> How can I scale images using the Xprint API ? - </a></dt><dt>Q: <a href="#id2882976"> + </a></dt><dt>Q: <a href="#id2882982"> Can I pass my own PostScript code (fragment) to the print spooler instead of letting Xprt's PostScript DDX generate it ? - </a></dt><dt>Q: <a href="#id2883002"> + </a></dt><dt>Q: <a href="#id2883008"> When I use XpPutDocumentData I get a BadValue X protocol error. Any idea what am I doing wrong ? - </a></dt><dt>Q: <a href="#id2883043"> + </a></dt><dt>Q: <a href="#id2883048"> How do I use the XprintUtil library ? </a></dt><dt>Q: <a href="#why_does_xgetimage_not_work"> Why does the XGetImage not work for Xprt ? - </a></dt><dt>Q: <a href="#id2883200"> + </a></dt><dt>Q: <a href="#id2883206"> How to print with Xt/Athena widgets ? - </a></dt><dt>Q: <a href="#id2883293"> + </a></dt><dt>Q: <a href="#id2883299"> How to print with Xt/Motif widgets ? - </a></dt><dt>Q: <a href="#id2883318"> + </a></dt><dt>Q: <a href="#id2883323"> What are the differences between normal display and Xprint display ? - </a></dt><dt>Q: <a href="#id2883340"> + </a></dt><dt>Q: <a href="#id2883346"> How do I scale images ? - </a></dt><dt>Q: <a href="#id2883361"> + </a></dt><dt>Q: <a href="#id2883367"> libXp Image scaling vs. max. request size ? - </a></dt><dt>Q: <a href="#id2883383"> + </a></dt><dt>Q: <a href="#id2883389"> How can I use XprintUtils ? - </a></dt><dt>Q: <a href="#id2883405"> + </a></dt><dt>Q: <a href="#id2883410"> How do I calculate the DPI values for Xprt DDX screens ? - </a></dt><dt>Q: <a href="#id2883427"> + </a></dt><dt>Q: <a href="#id2883433"> How do I find scaleable fonts ? - </a></dt><dt>Q: <a href="#id2883449"> + </a></dt><dt>Q: <a href="#id2883454"> How do I find printer-builtin fonts ? - </a></dt><dt>Q: <a href="#id2883470"> + </a></dt><dt>Q: <a href="#id2883476"> The XLFD for Printer-builtin fonts look like bitmap fonts - is that bad ? - </a></dt><dt>Q: <a href="#id2883501"> + </a></dt><dt>Q: <a href="#id2883507"> When printing using the XawPrintShell/XmPrintShell print shells my PostScript output is always corrupt. What am I doing wrong ? - </a></dt><dt>Q: <a href="#id2883569"> + </a></dt><dt>Q: <a href="#id2883575"> When printing using the XawPrintShell/XmPrintShell print shells I always get a grey/dithered background on paper. Any idea how to change that to "white" ? - </a></dt><dt>Q: <a href="#id2883605"> + </a></dt><dt>Q: <a href="#id2883611"> Are there any caveats/suggestions when printing via Xt/Motif2 widgets ? </a></dt><dt>Q: <a href="#changing_page_attributes_on_the_fly_when_using_printshells"> Can I change the paper size/resolution/page orientation/etc. when printing using the @@ -810,9 +810,9 @@ pkgadd: ERROR: no packages were found in </var/tmp/dstreAAA5Jayyz> </p><div class="itemizedlist"><ul type="disc"><li><p> Motif/LessTif toolkits (full framework incl. special widgets like <tt class="function">XmPrintShell</tt>) </p></li><li><p> - Athena toolkit (full framework incl. special widgets like <tt class="function">XawPrintShell</tt>, starting with X.org release 6.7.1) + Athena toolkit (full framework incl. special widgets like <tt class="function">XawPrintShell</tt>, starting with X.org release 6.8.0) </p></li><li><p> - Xedit, Xman, Xmore, etc. (starting with X.org release 6.7.1) + Xedit, Xman, Xmore, etc. (starting with X.org release 6.8.0) </p></li><li><p> <a href="http://www.opengroup.org/cde/" target="_top">Common Desktop Environment (CDE) 2.x</a> </p></li><li><p> @@ -820,7 +820,7 @@ pkgadd: ERROR: no packages were found in </var/tmp/dstreAAA5Jayyz> </p></li><li><p> Eclipse </p></li><li><p> - KDE/Qt support is planned for Q3/2004 + KDE/Qt support is planned for Q1/2005 </p></li><li><p> StarOffice 5.x </p></li><li><p> @@ -2621,48 +2621,48 @@ Xp Extension: Can't load driver XP-RASTER What is going wrong here ? </a></dt><dt>Q: <a href="#id2882791"> What is XpStartDoc for ? - </a></dt><dt>Q: <a href="#id2882881"> + </a></dt><dt>Q: <a href="#id2882887"> How does the XLFD for printer-builtin fonts look like ? / How can I find/identify printer-builtin fonts ? - </a></dt><dt>Q: <a href="#id2882955"> + </a></dt><dt>Q: <a href="#id2882960"> How can I scale images using the Xprint API ? - </a></dt><dt>Q: <a href="#id2882976"> + </a></dt><dt>Q: <a href="#id2882982"> Can I pass my own PostScript code (fragment) to the print spooler instead of letting Xprt's PostScript DDX generate it ? - </a></dt><dt>Q: <a href="#id2883002"> + </a></dt><dt>Q: <a href="#id2883008"> When I use XpPutDocumentData I get a BadValue X protocol error. Any idea what am I doing wrong ? - </a></dt><dt>Q: <a href="#id2883043"> + </a></dt><dt>Q: <a href="#id2883048"> How do I use the XprintUtil library ? </a></dt><dt>Q: <a href="#why_does_xgetimage_not_work"> Why does the XGetImage not work for Xprt ? - </a></dt><dt>Q: <a href="#id2883200"> + </a></dt><dt>Q: <a href="#id2883206"> How to print with Xt/Athena widgets ? - </a></dt><dt>Q: <a href="#id2883293"> + </a></dt><dt>Q: <a href="#id2883299"> How to print with Xt/Motif widgets ? - </a></dt><dt>Q: <a href="#id2883318"> + </a></dt><dt>Q: <a href="#id2883323"> What are the differences between normal display and Xprint display ? - </a></dt><dt>Q: <a href="#id2883340"> + </a></dt><dt>Q: <a href="#id2883346"> How do I scale images ? - </a></dt><dt>Q: <a href="#id2883361"> + </a></dt><dt>Q: <a href="#id2883367"> libXp Image scaling vs. max. request size ? - </a></dt><dt>Q: <a href="#id2883383"> + </a></dt><dt>Q: <a href="#id2883389"> How can I use XprintUtils ? - </a></dt><dt>Q: <a href="#id2883405"> + </a></dt><dt>Q: <a href="#id2883410"> How do I calculate the DPI values for Xprt DDX screens ? - </a></dt><dt>Q: <a href="#id2883427"> + </a></dt><dt>Q: <a href="#id2883433"> How do I find scaleable fonts ? - </a></dt><dt>Q: <a href="#id2883449"> + </a></dt><dt>Q: <a href="#id2883454"> How do I find printer-builtin fonts ? - </a></dt><dt>Q: <a href="#id2883470"> + </a></dt><dt>Q: <a href="#id2883476"> The XLFD for Printer-builtin fonts look like bitmap fonts - is that bad ? - </a></dt><dt>Q: <a href="#id2883501"> + </a></dt><dt>Q: <a href="#id2883507"> When printing using the XawPrintShell/XmPrintShell print shells my PostScript output is always corrupt. What am I doing wrong ? - </a></dt><dt>Q: <a href="#id2883569"> + </a></dt><dt>Q: <a href="#id2883575"> When printing using the XawPrintShell/XmPrintShell print shells I always get a grey/dithered background on paper. Any idea how to change that to "white" ? - </a></dt><dt>Q: <a href="#id2883605"> + </a></dt><dt>Q: <a href="#id2883611"> Are there any caveats/suggestions when printing via Xt/Motif2 widgets ? </a></dt><dt>Q: <a href="#changing_page_attributes_on_the_fly_when_using_printshells"> Can I change the paper size/resolution/page orientation/etc. when printing using the @@ -2875,7 +2875,7 @@ Xp Extension: Can't load driver XP-RASTER Because most applications of the day are only printing one document per job, <tt class="function">XpStartPage</tt> was designed that it generates a "synthetic" <tt class="function">XpStartDoc</tt> if it has not been called yet. - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882881"></a><a name="id2882884"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882887"></a><a name="id2882890"></a><b>Q:</b></td><td align="left" valign="top"><p> How does the XLFD for printer-builtin fonts look like ? / How can I find/identify printer-builtin fonts ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> There is no special XLFD scheme for printer-builtin fonts. @@ -2886,26 +2886,26 @@ Xp Extension: Can't load driver XP-RASTER thaht <tt class="function">XListFonts</tt> and co. return both printer-builtin and normal fonts. Removing <tt class="literal">xp-list-internal-printer-fonts</tt> will make printer-builtin fonts disappear, removing <tt class="literal">xp-list-glyph-fonts</tt> will make normal glyph fonts disappear from font lists. - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882955"></a><a name="id2882957"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882960"></a><a name="id2882963"></a><b>Q:</b></td><td align="left" valign="top"><p> How can I scale images using the Xprint API ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882976"></a><a name="id2882979"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882982"></a><a name="id2882985"></a><b>Q:</b></td><td align="left" valign="top"><p> Can I pass my own PostScript code (fragment) to the print spooler instead of letting Xprt's PostScript DDX generate it ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883002"></a><a name="id2883006"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883008"></a><a name="id2883011"></a><b>Q:</b></td><td align="left" valign="top"><p> When I use <tt class="function">XpPutDocumentData</tt> I get a <tt class="literal">BadValue</tt> X protocol error. Any idea what am I doing wrong ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883043"></a><a name="id2883046"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883048"></a><a name="id2883052"></a><b>Q:</b></td><td align="left" valign="top"><p> How do I use the XprintUtil library ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="why_does_xgetimage_not_work"></a><a name="id2883074"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="why_does_xgetimage_not_work"></a><a name="id2883080"></a><b>Q:</b></td><td align="left" valign="top"><p> Why does the <tt class="function">XGetImage</tt> not work for Xprt ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns120="" align="left" valign="top"><p> There are at least three reasons why <tt class="function">XGetImage</tt> does not work for Xprt: @@ -2930,10 +2930,10 @@ Xp Extension: Can't load driver XP-RASTER (which means: A <tt class="function">XGetImage</tt> implementation would return image data but glyphs rendered using the printer-builtin fonts would be missing). </p></li></ol></div><p> - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883200"></a><a name="id2883203"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883206"></a><a name="id2883209"></a><b>Q:</b></td><td align="left" valign="top"><p> How to print with Xt/Athena widgets ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns121="" align="left" valign="top"><p> - There are two examples in the Xprint.org and X11R6.7.1 source trees which demonstrate how to use Xprint using + There are two examples in the Xprint.org and X11R6.8.0 source trees which demonstrate how to use Xprint using Athena widgets: </p><div class="orderedlist"><ol type="1"><li><p> <tt class="filename">xc/programs/xphelloworld/xpawhelloworld/</tt> contains a simple @@ -2945,40 +2945,40 @@ Xp Extension: Can't load driver XP-RASTER <tt class="function">XmPrintShell</tt> should be used since this is the easier way to add print support to an Athena application). </p></li></ol></div><p> - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883293"></a><a name="id2883296"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883299"></a><a name="id2883302"></a><b>Q:</b></td><td align="left" valign="top"><p> How to print with Xt/Motif widgets ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> The Xprint.org source tree contains the xpxmhelloworld (xc/programs/xphelloworld/xpxmhelloworld/) application to demonstrate how to print using the Motif2 toolkit. - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883318"></a><a name="id2883321"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883323"></a><a name="id2883326"></a><b>Q:</b></td><td align="left" valign="top"><p> What are the differences between normal display and Xprint display ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883340"></a><a name="id2883343"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883346"></a><a name="id2883349"></a><b>Q:</b></td><td align="left" valign="top"><p> How do I scale images ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883361"></a><a name="id2883364"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883367"></a><a name="id2883370"></a><b>Q:</b></td><td align="left" valign="top"><p> libXp Image scaling vs. max. request size ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883383"></a><a name="id2883386"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883389"></a><a name="id2883392"></a><b>Q:</b></td><td align="left" valign="top"><p> How can I use XprintUtils ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883405"></a><a name="id2883408"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883410"></a><a name="id2883414"></a><b>Q:</b></td><td align="left" valign="top"><p> How do I calculate the DPI values for Xprt DDX screens ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883427"></a><a name="id2883430"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883433"></a><a name="id2883436"></a><b>Q:</b></td><td align="left" valign="top"><p> How do I find scaleable fonts ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883449"></a><a name="id2883452"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883454"></a><a name="id2883457"></a><b>Q:</b></td><td align="left" valign="top"><p> How do I find printer-builtin fonts ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883470"></a><a name="id2883473"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883476"></a><a name="id2883479"></a><b>Q:</b></td><td align="left" valign="top"><p> The XLFD for Printer-builtin fonts look like bitmap fonts - is that bad ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> No, this is not "bad". The XLFD of a printer-builtin font only looks like a bitmap font since @@ -2986,7 +2986,7 @@ Xp Extension: Can't load driver XP-RASTER AFAIK specifies the resolution which was used for generating the metrics) - however this does not change the fact that the printer-builtin fonts are outline scaleable fonts these fonts reside in the printer's ROM). - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883501"></a><a name="id2883504"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883507"></a><a name="id2883510"></a><b>Q:</b></td><td align="left" valign="top"><p> When printing using the <tt class="function">XawPrintShell</tt>/<tt class="function">XmPrintShell</tt> print shells my PostScript output is always corrupt. What am I doing wrong ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns122="" align="left" valign="top"><p> @@ -2999,13 +2999,13 @@ Xp Extension: Can't load driver XP-RASTER XtSetArg(args[n], XmNcursorPositionVisible, False); ... </pre></div><p> - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883569"></a><a name="id2883572"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883575"></a><a name="id2883578"></a><b>Q:</b></td><td align="left" valign="top"><p> When printing using the <tt class="function">XawPrintShell</tt>/<tt class="function">XmPrintShell</tt> print shells I always get a grey/dithered background on paper. Any idea how to change that to "white" ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> XXX - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883605"></a><a name="id2883608"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883611"></a><a name="id2883614"></a><b>Q:</b></td><td align="left" valign="top"><p> Are there any caveats/suggestions when printing via Xt/Motif2 widgets ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns127="" align="left" valign="top"><p> There are a couple of Xt resources which may likely differ from the normal values (e.g. those values @@ -3054,7 +3054,7 @@ XtSetArg(args[n], XmNcursorPositionVisible, False); a margin either. </p></dd></dl></div><p> </p></dd></dl></div><p> - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="changing_page_attributes_on_the_fly_when_using_printshells"></a><a name="id2884171"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="changing_page_attributes_on_the_fly_when_using_printshells"></a><a name="id2884176"></a><b>Q:</b></td><td align="left" valign="top"><p> Can I change the paper size/resolution/page orientation/etc. when printing using the <tt class="function">XawPrintShell</tt>/<tt class="function">XmPrintShell</tt> print shells ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> @@ -3069,51 +3069,51 @@ XtSetArg(args[n], XmNcursorPositionVisible, False); <tt class="literal">XmNminX</tt>, <tt class="literal">XmNminY</tt>, <tt class="literal">XmNmaxX</tt> and <tt class="literal">XmNmaxX</tt> (<tt class="function">XmPrintShell</tt>) are updated based on events send by the Xp Extension and then the print shell is resized based on the new values (<tt class="function">XawPrintShell</tt> is slightly more flexible since the size mode can be defined using the <tt class="literal">XawNlayoutMode</tt> attribute)). - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="examples_for_using_glx"></a><a name="id2884336"></a><b>Q:</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="examples_for_using_glx"></a><a name="id2884342"></a><b>Q:</b></td><td align="left" valign="top"><p> Where can I find an example how to print with Xprint using the OpenGL/GLX API ? </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> - In Xorg release 6.7.1 Xprint support was added to the GLX demo application "glxgears" + In Xorg release 6.8.0 Xprint support was added to the GLX demo application "glxgears" (<a href="http://xprint.freedesktop.org/cgi-bin/viewcvs.cgi/xorg/xc/programs/glxgears/" target="_top">xc/programs/Xserver/glxgears/</a>). - </p></td></tr></tbody></table></div></div><div class="simplesect" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="knownbugs"></a>Known bugs</h2></div></div><div></div></div><div class="qandaset"><dl><dt></dt><dd><dl><dt>Problem <a href="#id2884394"> + </p></td></tr></tbody></table></div></div><div class="simplesect" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="knownbugs"></a>Known bugs</h2></div></div><div></div></div><div class="qandaset"><dl><dt></dt><dd><dl><dt>Problem <a href="#id2884400"> Xprt build from Xfree86 sources is completely broken and unuseable. - </a></dt><dt>Problem <a href="#id2884449"> + </a></dt><dt>Problem <a href="#id2884455"> The code which matches XLFD names to PS Type1 font names is case-sensitive in Xprts build from X.org X11R6.5.1/X11R6.6 and the current Solaris Xprt. This may cause that the PS DDX refuses to download PS Type1 fonts. - </a></dt><dt>Problem <a href="#id2884485"> + </a></dt><dt>Problem <a href="#id2884491"> Xprt build from X11R6.5.1/X11R6.6 sources and Solaris's version of Xprt can only download PFA (PS ASCII font) fonts which ends of the ending "*.pfa". - </a></dt><dt>Problem <a href="#id2884537"> + </a></dt><dt>Problem <a href="#id2884543"> There is an issue how the Linux and Solaris Xprt handles the "copy-count" of a print job. The result may be that a job with n copies of a document end-up in n jobs with n copies (usually equals to n^2 copies). - </a></dt></dl></dd></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="toc" colspan="2"><td align="left" valign="top" colspan="2"><dl><dt>Problem <a href="#id2884394"> + </a></dt></dl></dd></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="toc" colspan="2"><td align="left" valign="top" colspan="2"><dl><dt>Problem <a href="#id2884400"> Xprt build from Xfree86 sources is completely broken and unuseable. - </a></dt><dt>Problem <a href="#id2884449"> + </a></dt><dt>Problem <a href="#id2884455"> The code which matches XLFD names to PS Type1 font names is case-sensitive in Xprts build from X.org X11R6.5.1/X11R6.6 and the current Solaris Xprt. This may cause that the PS DDX refuses to download PS Type1 fonts. - </a></dt><dt>Problem <a href="#id2884485"> + </a></dt><dt>Problem <a href="#id2884491"> Xprt build from X11R6.5.1/X11R6.6 sources and Solaris's version of Xprt can only download PFA (PS ASCII font) fonts which ends of the ending "*.pfa". - </a></dt><dt>Problem <a href="#id2884537"> + </a></dt><dt>Problem <a href="#id2884543"> There is an issue how the Linux and Solaris Xprt handles the "copy-count" of a print job. The result may be that a job with n copies of a document end-up in n jobs with n copies (usually equals to n^2 copies). - </a></dt></dl></td></tr><tr class="question"><td align="left" valign="top"><a name="id2884394"></a><a name="id2884397"></a><b>Problem</b></td><td align="left" valign="top"><p> + </a></dt></dl></td></tr><tr class="question"><td align="left" valign="top"><a name="id2884400"></a><a name="id2884403"></a><b>Problem</b></td><td align="left" valign="top"><p> Xprt build from Xfree86 sources is completely broken and unuseable. </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Solution</b></td><td align="left" valign="top"><p> Build Xprt from the CVS tree at <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a> or the X.org X11R6.5.1 sources (note that the client side Xprint extension library ("<tt class="filename">libXp.so</tt>") from Xfree86 is not broken and do not need to be replaced). - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2884449"></a><a name="id2884452"></a><b>Problem</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2884455"></a><a name="id2884458"></a><b>Problem</b></td><td align="left" valign="top"><p> The code which matches XLFD names to PS Type1 font names is case-sensitive in Xprts build from X.org X11R6.5.1/X11R6.6 and the current Solaris Xprt. This may cause that the PS DDX refuses to @@ -3121,7 +3121,7 @@ XtSetArg(args[n], XmNcursorPositionVisible, False); </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Solution</b></td><td align="left" valign="top"><p> Patch available, I am looking for a way to get the patch into the X11 and Solaris source trees... - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2884485"></a><a name="id2884488"></a><b>Problem</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2884491"></a><a name="id2884494"></a><b>Problem</b></td><td align="left" valign="top"><p> Xprt build from X11R6.5.1/X11R6.6 sources and Solaris's version of Xprt can only download PFA (PS ASCII font) fonts which ends of the ending "*.pfa". @@ -3131,7 +3131,7 @@ XtSetArg(args[n], XmNcursorPositionVisible, False); I am looking for a way to get the patch into the X11 and Solaris source trees (the fixed version can download both PFA/PFB fonts in PFA format and even handles non-standard file extensions). - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2884537"></a><a name="id2884540"></a><b>Problem</b></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2884543"></a><a name="id2884546"></a><b>Problem</b></td><td align="left" valign="top"><p> There is an issue how the Linux and Solaris Xprt handles the "copy-count" of a print job. The result may be that a job with n copies of a document end-up in n jobs with n copies (usually equals diff --git a/hardcopy/XPRINT/Xprint_FAQ.txt b/hardcopy/XPRINT/Xprint_FAQ.txt index bfe8e2e..b62ec05 100644 --- a/hardcopy/XPRINT/Xprint_FAQ.txt +++ b/hardcopy/XPRINT/Xprint_FAQ.txt @@ -8,7 +8,7 @@ Xprint Frequently Asked Questions Version: 0.9.1 - Last-Modified: 2004/06/14 08:15:16 + Last-Modified: 2004/10/08 01:05:21 Maintained-by: Roland Mainz <[1]roland.mainz@nrubsig.org> @@ -778,12 +778,12 @@ Note * Motif/LessTif toolkits (full framework incl. special widgets like XmPrintShell) * Athena toolkit (full framework incl. special widgets like - XawPrintShell, starting with X.org release 6.7.1) - * Xedit, Xman, Xmore, etc. (starting with X.org release 6.7.1) + XawPrintShell, starting with X.org release 6.8.0) + * Xedit, Xman, Xmore, etc. (starting with X.org release 6.8.0) * [173]Common Desktop Environment (CDE) 2.x * [174]Mozilla, FireFox, ThunderBird, etc. * Eclipse - * KDE/Qt support is planned for Q3/2004 + * KDE/Qt support is planned for Q1/2005 * StarOffice 5.x * etc. @@ -2813,7 +2813,7 @@ Tip How to print with Xt/Athena widgets ? A: - There are two examples in the Xprint.org and X11R6.7.1 source trees + There are two examples in the Xprint.org and X11R6.8.0 source trees which demonstrate how to use Xprint using Athena widgets: 1. xc/programs/xphelloworld/xpawhelloworld/ contains a simple demo application which prints a Athena widget using the XawPrintShell @@ -2998,7 +2998,7 @@ XtSetArg(args[n], XmNcursorPositionVisible, False); OpenGL/GLX API ? A: - In Xorg release 6.7.1 Xprint support was added to the GLX demo + In Xorg release 6.8.0 Xprint support was added to the GLX demo application "glxgears" ([324]xc/programs/Xserver/glxgears/). Known bugs diff --git a/hardcopy/XPRINT/Xprint_FAQ.xml b/hardcopy/XPRINT/Xprint_FAQ.xml index 4396291..eace36f 100644 --- a/hardcopy/XPRINT/Xprint_FAQ.xml +++ b/hardcopy/XPRINT/Xprint_FAQ.xml @@ -44,7 +44,7 @@ Mappings used in this DocBook document: Version: 0.9.1 </para> <para> - Last-Modified: 2004/06/14 08:15:16 + Last-Modified: 2004/10/08 01:05:21 </para> <para> Maintained-by: @@ -756,7 +756,7 @@ Mappings used in this DocBook document: <listitem> <para> You can setup a TTF-aware X font server ("xfs", see - <citerefentry><refentrytitle>xfs</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry>) + <citerefentry><refentrytitle>xfs</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry>) with the matching TrueType fonts and add the font server location to Xprt's font path. </para> </listitem> @@ -901,12 +901,12 @@ Mappings used in this DocBook document: </listitem> <listitem> <para> - Athena toolkit (full framework incl. special widgets like <function>XawPrintShell</function>, starting with X.org release 6.7.1) + Athena toolkit (full framework incl. special widgets like <function>XawPrintShell</function>, starting with X.org release 6.8.0) </para> </listitem> <listitem> <para> - Xedit, Xman, Xmore, etc. (starting with X.org release 6.7.1) + Xedit, Xman, Xmore, etc. (starting with X.org release 6.8.0) </para> </listitem> <listitem> @@ -926,7 +926,7 @@ Mappings used in this DocBook document: </listitem> <listitem> <para> - KDE/Qt support is planned for Q3/2004 + KDE/Qt support is planned for Q1/2005 </para> </listitem> <listitem> @@ -1381,14 +1381,14 @@ printer: david_dj01@jason:5</computeroutput> can be handled in various ways - like per-cookie (using MIT-MAGIC-COOKIE-1 authentification), per-user (using SUN-DES-1 or MIT-KERBEROS-5 auth., see - (see <citerefentry><refentrytitle>xhost</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry>)) - and/or per-machine (using "xhost" (see <citerefentry><refentrytitle>xhost</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry>) and/or + (see <citerefentry><refentrytitle>xhost</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry>)) + and/or per-machine (using "xhost" (see <citerefentry><refentrytitle>xhost</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry>) and/or <filename>/etc/X<dpy>.hosts</filename> (<dpy> == display number, - e.g. <filename>/etc/X0.hosts</filename> for display 0) (see <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry>)) + e.g. <filename>/etc/X0.hosts</filename> for display 0) (see <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry>)) Consult manual pages <citerefentry><refentrytitle>Xsecurity</refentrytitle><manvolnum>__miscmansuffix__</manvolnum></citerefentry>, - <citerefentry><refentrytitle>xhost</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry>, - <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry> + <citerefentry><refentrytitle>xhost</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry>, + <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry> etc. for further details. </para> </answer> @@ -1403,7 +1403,7 @@ printer: david_dj01@jason:5</computeroutput> <answer> <para> Logging access to Xprt can be done using the standard Xserver auditing, - see the <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry> + see the <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry> manual page, option "-audit" </para> </answer> @@ -1447,7 +1447,7 @@ printer: david_dj01@jason:5</computeroutput> </para> <para> See - <citerefentry><refentrytitle>xplsprinters</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry> + <citerefentry><refentrytitle>xplsprinters</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry> for futher usage and a description of the output. </para> </answer> @@ -2972,7 +2972,7 @@ Xlib: Client is not authorized to connect to Server</computeroutput> </title> <para> If you do not want to use access control for Xprt then you can start it - with the option "-ac" (see <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry>) + with the option "-ac" (see <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry>) to disable the access control. Example: <screen> @@ -3002,7 +3002,7 @@ Xlib: Client is not authorized to connect to Server</computeroutput> <para> Host-based access control can be archived using <filename>/etc/X<dpy>.hosts</filename> (<dpy> == display number, e.g. <filename>/etc/X0.hosts</filename> for display 0 (see - <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry> + <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry> manual page for further details)). <blockquote><procedure> <title>Example</title> @@ -3150,7 +3150,7 @@ INET:mars</computeroutput> Xserver must run set-gid "root" to access these directories). Either fix the permission or start Xprt with the option "-pn". Using this option requires to access the server <emphasis>always</emphasis> with - <hostname>:<displaynum> (see <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry> + <hostname>:<displaynum> (see <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__appmansuffix__</manvolnum></citerefentry> manual page for the side-effects of this option). </para> </answer> @@ -4316,7 +4316,7 @@ Xp Extension: Can't load driver XP-RASTER </question> <answer> <para> - There are two examples in the Xprint.org and X11R6.7.1 source trees which demonstrate how to use Xprint using + There are two examples in the Xprint.org and X11R6.8.0 source trees which demonstrate how to use Xprint using Athena widgets: <orderedlist> <listitem> @@ -4662,7 +4662,7 @@ XtSetArg(args[n], XmNcursorPositionVisible, False); </question> <answer> <para> - In Xorg release 6.7.1 Xprint support was added to the GLX demo application "glxgears" + In Xorg release 6.8.0 Xprint support was added to the GLX demo application "glxgears" (<ulink url="http://xprint.freedesktop.org/cgi-bin/viewcvs.cgi/xorg/xc/programs/glxgears/">xc/programs/Xserver/glxgears/</ulink>). </para> </answer> diff --git a/man/general/Xprint.man b/man/general/Xprint.man new file mode 100644 index 0000000..39b0ccc --- /dev/null +++ b/man/general/Xprint.man @@ -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 --git a/man/general/Xprint.sgml b/man/general/Xprint.sgml new file mode 100644 index 0000000..1f7e0a7 --- /dev/null +++ b/man/general/Xprint.sgml @@ -0,0 +1,627 @@ +<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.2//EN" 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd'> + +<!-- Process this file with docbook-to-man to generate an nroff manual + page: 'docbook-to-man manpage.sgml > manpage.1'. You may view + the manual page with: 'docbook-to-man manpage.sgml | nroff -man | less'. + A typical entry in a Makefile or Makefile.am is: + +manpage.1: manpage.sgml + docbook-to-man $< > $@ + +HTML generation can be done like this: +% xsltproc ==docbook /usr/share/sgml/docbook/docbook-xsl-stylesheets-1.60.1/html/docbook.xsl Xprint.sgml >Xprint.html + --> + +<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’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. + <!-- FIXME: IBM/AIX people have integrated Xprt into their main Xserver (currently experimental) ... --> + </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’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 <Xprinters file>] [:dispNum] &</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] &</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 <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>. + </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> + <!-- brain dead <term> does not permit quote marks + (in XPRINTER="hplaser19@littlecat:80"), so omit them --> + <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"> + <!-- specific references --> + <!-- none --> + + <!-- Xprint general references --> +<!-- + <member><citerefentry><refentrytitle>Xprint</refentrytitle><manvolnum>__miscmansuffix__</manvolnum></citerefentry></member> +--> + <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> + <!-- ToDO: Add manual pages for the single Xprint DDX implementations (PostScript/PDF/PCL/PCL-MONO/Raster/etc.) --> + <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 --git a/sgml/OpenBSD.sgml b/sgml/OpenBSD.sgml index 3b2918b..ca96bbf 100644 --- a/sgml/OpenBSD.sgml +++ b/sgml/OpenBSD.sgml @@ -6,8 +6,7 @@ <title>README for X11R&relvers; on OpenBSD <author> Matthieu Herrb -<Date>Last modified on: 9 December 2003; updated 25 March 2004 by Jim Gettys -for X11R&relvers; +<Date>Last modified on: 4 February 2005. <ident> </ident> @@ -18,28 +17,29 @@ for X11R&relvers; <sect>What and Where is X11R&relvers;? <p> -The X.org Foundation X11R&relvers; is an Open Source version of the X Window System that supports +The X.org Foundation X11R&relvers; is an Open Source version of +the X Window System that supports several UNIX(R) and UNIX-like operating systems (such as Linux, the BSDs and Solaris x86) on Intel and other platforms. See the <htmlurl url="COPYRIGHT.html" name="Copyright Notice">. <![ %notsnapshot [ -The sources for X11R&relvers; are available from - +The sources for X11R&relvers; are available from <htmlurl name="http://wiki.x.org" url="http://wiki.x.org">]]> <p> -X11R&relvers; also builds on other OpenBSD architectures. See section +X11R&relvers; builds on most architectures supported by OpenBSD. See section <ref id="otherarch" name="Building on other architectures"> for details. <sect>Bug Reports for This Document <p> -Use the X.org Bugzilla at <url url="http://bugzilla.freedesktop.org"> +Use the X.org Bugzilla at <htmlurl +url="http://bugs.freedesktop.org" name="http://bugs.freedesktop.org"> to submit comments or suggestions about this file, using the xorg product. <sect>New OS dependent features @@ -47,96 +47,17 @@ to submit comments or suggestions about this file, using the xorg product. See the <htmlurl url="RELNOTES.html" name="Release Notes"> for non-OS dependent new features in X11R&relvers;. -<sect1>New OS related features -<p> -<itemize> -<item>The IPv6 support is enabled on OpenBSD, but XDMCP over IPv6 is -not currently enabled since the code uses IPv6 mapped IPv4 addresses -which are not supported on OpenBSD. -<item>The userland part of DRI is enabled and built. Now waiting for -someone to port the kernel modules... -<item>All major revisions of the shared libraries are incremented on -OpenBSD 3.3 and later, to support the API changes introduced by -gcc stack protector. -</itemize> - -<sect1>New OS related features in 4.3 -<p> -<itemize> -<item>Support for some VGA cards on OpenBSD/alpha -</itemize> - -<sect1>New OS dependent features in 4.2 -<p> -<itemize> -<item>Support for OpenBSD/macppc on the ATI Rage128 based -Power Macintoshes. -<item>Support for building clients on OpenBSD/sparc64. -</itemize> - -<sect1>New OS dependent features in 4.0.3 -<p> -<itemize> -<item>Support for the wscons console driver in post 2.8 OpenBSD. -<item>A fix for multi-threaded libraries support. -</itemize> - -<sect1>New OS dependent features in 4.0.2 -<p> -<itemize> -<item>Support for the OpenBSD ports tree, -<item>Preliminary support for the macppc architecture (clients build -and work, the server doesn't work yet), -<item>xdm now writes an utmp entry, -<item>startx now creates an Xauthority magic cookie for the display. -</itemize> - -<sect1>New OS dependent features in 4.0.1 -<p> -<itemize> -<item>Several features from the OpenBSD X11 tree were merged into xdm: -<itemize> -<item> support for Kerberos IV authentication -<item>use the arc4random(4) random number generator -<item>add a new resource "allowRootLogin", which can be used to disable - root logins through xdm -<item>log failed logins to syslogd -<item>verify that the shell is valid using /etc/shell -<item>verify that the account hasn't expired -</itemize> -<item>The Xsun server can be built again on OpenBSD/sparc. -</itemize> - -<sect1>New OS dependent features in 4.0 <p> <itemize> -<item>Multi-thread safe libraries are built by default on OpenBSD 2.6 - and later, -<item>Preliminary APM support. +<item>Switch the the Xinput-aware kbd driver for keyboard input </itemize> -<sect1>New OS dependent features in 3.9.18 -<p> +<sect1>New OS related features in X.Org 6.8 <itemize> -<item>Support for USB mices has been added on OpenBSD. -<item>Soft-booting secondary cards through the int10 BIOS interface is -now possible using the x86emu real mode emulator. +<item>Support for Propolice in modules. +<item>Server support for OpenBSD/amd64. </itemize> -<sect1>New OS dependent features in 3.9.17 -<p> -<itemize> -<item><em>Silken mouse</em> is supported for serial mices, and, under -post 2.6 OpenBSD-current for PS/2 mices. -<item>MTRR Write Combining is enabled under post 2.6 OpenBSD-current. -</itemize> - -<sect>Installing the Binaries - -<p> -Refer to the <htmlurl url="Install.html" name="Installation Document"> -for detailed installation instructions. - <sect>Configuring X for Your Hardware <p> The <tt>/etc/X11/xorg.conf</tt> file tells the X server what kind of @@ -147,7 +68,7 @@ server what specific hardware you have. You'll need info on your hardware: <itemize> <item>Your mouse type, baud rate and its /dev entry. -<item>The video card's chipset (e.g. ET4000, S3, etc). +<item>The video card's chipset (e.g. ATI Radeon, nVidia GeForce 4/MX etc). <item>Your monitor's sync frequencies. </itemize> @@ -168,10 +89,10 @@ modes with the <tt>xvidtune</tt> utility. <p> X11R&relvers; has support for the mouse driver included in -the new <bf/wscons/ console driver introduced by OpenBSD-2.9. +the new <bf/wscons/ console driver. Specify ``<tt/wsmouse/'' as the protocol and -``<tt>/dev/wsmouse0</tt>'' as the device in <tt>/etc/X11/xorg.conf</tt> -if you're using OpenBSD-2.9 or later with a PS/2 or USB mouse. +``<tt>/dev/wsmouse</tt>'' as the device in <tt>/etc/X11/xorg.conf</tt> +with a PS/2 or USB mouse. <p> See <htmlurl url="mouse.html" name="README.mouse"> for general instruction on mouse configuration. @@ -187,15 +108,11 @@ instruction on mouse configuration. To start the display manager, log in as root on the console and type: ``<tt/xdm -nodaemon/''. -You can start xdm automatically on bootup by changing the line -<tscreen><verb> -xdm_flags=NO # for normal use: xdm_flags="" -</verb></tscreen> -to: +You can start xdm automatically on bootup by adding the line: <tscreen><verb> xdm_flags="" # for normal use: xdm_flags="" </verb></tscreen> -in <tt>/etc/rc.conf</tt>. +in <tt>/etc/rc.conf.local</tt>. <sect1>Running X without the display manager <p> @@ -211,21 +128,12 @@ and startx man pages. <sect>Kernel Support for X <p> -To make sure X support is enabled under OpenBSD, the following -line must be in your config file in <tt>/sys/arch/i386/conf</tt>: - -<tscreen> - option APERTURE -</tscreen> +OpenBSD's GENERIC kernels have all support for running X enabled. <sect1>Console drivers <p> The server supports wscons, the standard OpenBSD/i386 console driver. -<p> -The pcvt console driver which was the default up to OpenBSD -2.8, is also supported on those releases. - <sect1>Aperture Driver <p> By default OpenBSD includes the BSD 4.4 kernel security @@ -281,8 +189,12 @@ name="http://www.openbsd.org/anoncvs.html"> for details on anoncvs. <label id="otherarch"> <p> -X11R&relvers; also compiles on other OpenBSD architectures. -<sect1>X11R&relvers; on OpenBSD/alpha +X11R&relvers; compiles on most OpenBSD architectures. The X.Org +X server builds and run on the following systems. On other +architectures supported by OpenBSD, only client side libraries and +applications are supported. + +<sect1>OpenBSD/alpha <p> The X server is known to work on some VGA cards in alpha machines that support BWX I/O, with OpenBSD 3.2 and higher. @@ -300,12 +212,11 @@ Note that this version of doesn't work on TGA cards. The version shipped with OpenBSD 3.1 and higher includes an OS-specific driver <em/wsfb/ that is used to support TGA cards. -<sect1>X11R&relvers; on OpenBSD/macppc +<sect1>OpenBSD/macppc <p> -The X server is currently known to work on the G4 Macs and new -iBooks with ATI Rage 128 cards running OpenBSD 3.0 or later. -Other machines are more or less untested. Earlier OpenBSD versions -lack some kernel support for it. +The X server is currently known to work on most of the G4 Macs and +iBooks with ATI or nVidia cards. +Other machines are more or less untested. <p> Use xorgconfig to build a /etc/X11/xorg.conf file before starting the server for the first time. @@ -326,20 +237,10 @@ OpenBSD instead. <sect1>OpenBSD/sparc64 <p> -This version only has support for X clients on -OpenBSD/sparc64. Note that the version shipped with OpenBSD also has -support for the X server on both SBus and PCI based machines. - +This version only has support PCI based machines using ATI cards on +OpenBSD/sparc64. Note that the version shipped with OpenBSD has +support for the X server on both SBus and UPA (unaccelerated) based cards. -<sect>Building New X Clients - -<p> -The easiest way to build a new client (X application) is to use -<tt/xmkmf/ if an <tt/Imakefile/ is included in the sources. Type -``<tt/xmkmf -a/'' to create the Makefiles, check the configuration if -necessary and type ``<tt/make/''. Whenever you install additional man -pages you should update <tt/whatis.db/ by running ``<tt>makewhatis -/usr/X11R6/man</tt>''. <sect> Thanks <p> @@ -347,6 +248,7 @@ Many thanks to all people who contributed to make X11R&relvers; work on *BSD, in particular: <bf/David Dawes/, <bf/Todd Fries/, +<bf/Miodrag Vallat/, <bf/Rod Grimes/, <bf/Charles Hannum/, <bf/Amancio Hasty/, diff --git a/sgml/README.sgml b/sgml/README.sgml index 0f575e7..94d602d 100644 --- a/sgml/README.sgml +++ b/sgml/README.sgml @@ -95,7 +95,7 @@ Applications for Membership are now being accepted, and active participants in the further development of the X Window Technology are invited to complete a <url url="http://www.x.org/XOrg_Foundation_Membership.html" name="membership application">. -The X11R&relvers; codebase forms the second X window system release since +The X11R&relvers; codebase forms the &whichxorgrel; X window system release since the formation of the X.org foundataion and includes code from the X Consortium, the Open Group and the XFree86™ project. This release is dedicated to the greater X community, developers diff --git a/sgml/RELNOTES.sgml b/sgml/RELNOTES.sgml index a0f0d35..5c03ddf 100644 --- a/sgml/RELNOTES.sgml +++ b/sgml/RELNOTES.sgml @@ -118,12 +118,13 @@ supplied with this distribution, please add: to config/cf/host.def. -<item> The XTT font module and FreeType1 have been retired because FreeType2 subsumes +<item>The XTT font module and FreeType1 have been retired because FreeType2 subsumes their functionality -<item> Retire old PS Type1 font rasterizer (except for CID font usage) since the FreeType2 rasterizer now handles PS Type1 (*.pfa, *.pfb) +<item>Retire old PS Type1 font rasterizer (except for CID font usage) since the FreeType2 rasterizer now handles PS Type1 (*.pfa, *.pfb) <item>Render implementation fixes <item>Updated x86emu and resynced with upstream at Scitech <item>Updated SiS driver +<item>Updated Nvidia driver (opensource version) <item>Render acceleration for ATI's R100 and R200-series cards <item>Substantial speedups in the software implementation of the render extensions when compiled with gcc 3.4 on the i386 architecture. @@ -134,8 +135,9 @@ render extensions when compiled with gcc 3.4 on the i386 architecture. <item>Allow backward compatibility but internally covert to new format </itemize> <item>Software mouse cursor is now based on the Damage extension -<item>A new keyboard driver is enabled by default. The old driver is disabled unless explicitly compiled in by defining the macro USE_DEPRECATED_KEYBOARD_DRIVER -<item>Extensions can be enabled/disabled from the configuration file and from the command line +<item>A new keyboard driver is enabled by default. The old driver is disabled unless explicitly compiled in by defining the macro |USE_DEPRECATED_KEYBOARD_DRIVER|. +<item>All extensions (except Xserver-specific extensions "DMX" and "XpExtension") can now be +enabled/disabled from the configuration file and from the command line. <item>Mac OS X updates: <itemize> <item>Support dynamic screen configuration changes in rootless mode @@ -145,6 +147,7 @@ render extensions when compiled with gcc 3.4 on the i386 architecture. <item>Fixed launch of X clients from Finder with a space in their path <item>Fixed some GLX rendering problems on Mac OS X 10.2 and earlier </itemize> +<item>Updated xterm version </itemize> <sect1>New X extensions @@ -229,89 +232,92 @@ web site" url="http://dmx.sf.net/">, including how to configure and use Xprint updates <p> <itemize> - <item>Integrated various fixes from xprint.mozdev.org (more or less the whole codebase has been merged) + <item>Integrated various fixes from <url name="xprint.mozdev.org" url="http://xprint.mozdev.org"> (more or less the whole codebase has been merged) <item>Integrated various fixes from Sun Microsystems <item>OpenGL is now supported for printing <item>New set of maintenance tools for the Xprint server (xplsprinters, xprehashprinterlist, etc.) - <item>Added new XprintUtils client library to make the usage off Xprint easier + <item>Added new XprintUtils client library to make the usage of Xprint easier <item>Various other features and fixes integrated <item>Athena toolkit now has print support (XawPrintShell) which is included - in a separate version of that library (Xaw8) - <item>Various applications/tools like xman, xedit, xlogo, etc. now have - print support + in a new version of that library (Xaw8) + <item>Various applications/tools like xman, xedit, xlogo, xlsfonts, etc. + now have print support </itemize> <sect1>Updated Mesa and DRI from upstream sources <P> - <itemize> - <item>More OpenGL extensions - <item>MergedFB for Radeon (Dualhead DRI support on these cards) - <item>Many GLX fixes - <item>Working SiS DRI driver - <item>Major Radeon and R200 DRI driver updates - <item>fbconfigs support - <item>Beginnings of pbuffer support (indirect only, and only in specific circumstances). - <item>Merge Mach64 DRI support (Eric Anholt, July 23) - </itemize> + <itemize> + <item>Mesa version has been updated to 6.2.1 (in X11R6.8.2) + <item>More OpenGL extensions + <item>MergedFB for Radeon (Dualhead DRI support on these cards) + <item>Many GLX fixes + <item>Working SiS DRI driver + <item>Major Radeon and R200 DRI driver updates + <item>fbconfigs support + <item>Beginnings of pbuffer support (indirect only, and only in specific circumstances). + <item>Merge Mach64 DRI support (Eric Anholt, July 23) + </itemize> <sect1>Video driver enhancements <p> <itemize> - <item>SiS driver updates include - <itemize> - <item>output device hotplugging - <item>lots of fixes for 661, 741, 760 - <item>extended interface for SiSCtrl? - <item>extended LCD handling (allow more modes) - <item>HDTV support (480p, 480i, 720p. 1080i; 315/330 series) - <item>Added video blitter Xv adapter (315/330 series) - <item>extended RENDER acceleration - </itemize> - <item>Radeon driver updates: - <itemize> - <item>Merged Framebuffer support (dualhead with DRI) - <item>DynamicClocks option (reduced power usage) - <item>Render acceleration (r100, r200 chips only) - <item>Support for new ATI chips (R420/M18, R423, RV370/M22, RV380/M24, RS300) - <item>DRI support for IGP chips - <item>Xv gamma correction - <item>Updated 3D drivers - <item>Many other small fixes - </itemize> - <item>Neomagic driver updates - <itemize> - <item>Support for Xv on pre-nm2160 chips - <item>Pseudocolor overlay mode - <item>Improved support for lowres double scan modes - </itemize> - <item>MGA driver updates - <itemize> - <item>Support for DDC and DPMS on second head on G400 - <item>Updated 3D driver - </itemize> - <item>i810 driver updates - <itemize> - <item>Dualhead support (i830+) - <item>i915 support - <item>New 3D driver (i830+) - </itemize> - <item>Savage driver updates - <itemize> - <item>Pseudocolor overlay mode - </itemize> - <item>S3 driver updates - <itemize> - <item>Support for additional IBM RAMDACS - </itemize> - <item>Chips driver update - <itemize> - <item>Improved BE support - </itemize> - <item>New Voodoo driver (Alan Cox) - <itemize> - <item>Provides native (glide-less) acceleration and mode setup for voodoo/voodoo2 boards - </itemize> - </itemize> + <item>ATI Radeon driver updates: + <itemize> + <item>Merged Framebuffer support (dualhead with DRI) + <item>DynamicClocks option (reduced power usage) + <item>Render acceleration (r100, r200 chips only) + <item>Support for new ATI chips (R420/M18, R423, RV370/M22, RV380/M24, RS300) + <item>DRI support for IGP chips + <item>Xv gamma correction + <item>Updated 3D drivers + <item>Many other small fixes + </itemize> + <item>Chips driver update + <itemize> + <item>Improved BE support + </itemize> + <item>MGA driver updates + <itemize> + <item>Support for DDC and DPMS on second head on G400 + <item>Updated 3D driver + </itemize> + <item>Neomagic driver updates + <itemize> + <item>Support for Xv on pre-nm2160 chips + <item>Pseudocolor overlay mode (=PseudoColor emulation) + <item>Improved support for lowres double scan modes + </itemize> + <item>i810 driver updates + <itemize> + <item>Dualhead support (i830+) + <item>i915 support + <item>New 3D driver (i830+) + <item>i810 driver is now supported for AMD64 + </itemize> + <item>S3 driver updates + <itemize> + <item>Support for additional IBM RAMDACS + </itemize> + <item>Savage driver updates + <itemize> + <item>Pseudocolor overlay mode + </itemize> + <item>SiS driver updates include + <itemize> + <item>output device hotplugging + <item>lots of fixes for 661, 741, 760 + <item>extended interface for SiSCtrl? + <item>extended LCD handling (allow more modes) + <item>HDTV support (480p, 480i, 720p. 1080i; 315/330 series) + <item>Added video blitter Xv adapter (315/330 series) + <item>extended RENDER acceleration + <item>SiS driver now supported on AMD64 + </itemize> + <item>New Voodoo driver (Alan Cox) + <itemize> + <item>Provides native (glide-less) acceleration and mode setup for voodoo/voodoo2 boards + </itemize> +</itemize> <sect>Drivers <P> @@ -418,6 +424,27 @@ Darwin/Mac OS X uses IOKit drivers and does not use the module loader drivers listed above. Further information can be found in <htmlurl name="README.Darwin" url="Darwin.html">. +X11R&relvers; includes the following print drivers: + +<sect1>Print Drivers +<p> + +<table border=1 align="center"> +<tabular ca="|l|l|l|"> + <tabrow>Driver Name<colsep>Description<colsep>Further Information</tabrow> + <hline> + <tabrow><tt>PostScript</tt><colsep>PostScript driver<colsep> </tabrow> + <tabrow><tt>PCL</tt><colsep>PCL color driver<colsep> </tabrow> + <tabrow><tt>PCL-MONO</tt><colsep>PCL monocrome driver<colsep> </tabrow> + <tabrow><tt>RASTER</tt><colsep>Monocrome raster driver (XWD, PS, PCL)<colsep> </tabrow> +<!-- not yet + <tabrow><tt>SVG</tt><colsep>Scaleable Vector Graphics driver<colsep> </tabrow> +--> +</tabular> +</table> + +Drivers marked with (*) are available for Linux only. + X11R&relvers; includes the following input drivers: <sect1>Input Drivers @@ -445,9 +472,9 @@ X11R&relvers; includes the following input drivers: <tabrow><tt>hyperpen</tt><colsep>Aiptek HyperPen 6000<colsep> </tabrow> <tabrow><tt>js_x</tt><colsep>JamStudio pentablet<colsep><htmlurl name="js_x(4)" url="js_x.4.html"></tabrow> - <tabrow><tt>kbd</tt><colsep>generic keyboards (alternate)<colsep><htmlurl + <tabrow><tt>kbd</tt><colsep>generic keyboards (loadable module)<colsep><htmlurl name="kbd(4)" url="kbd.4.html"></tabrow> - <tabrow><tt>keyboard</tt><colsep>generic keyboards<colsep><htmlurl + <tabrow><tt>keyboard</tt><colsep>generic keyboards (builtin driver)<colsep><htmlurl name="keyboard(4)" url="keyboard.4.html"></tabrow> <tabrow><tt>microtouch</tt><colsep>MicroTouch<colsep> </tabrow> <tabrow><tt>mouse</tt><colsep>most mouse devices<colsep><htmlurl @@ -639,8 +666,7 @@ url="http://dri.sf.net/">. The 3D core rendering component is provided by <sect1>XVideo Extension (Xv) <p> - -The XVideo extension is supported in X11R6.7.x. +The XVideo extension is supported in X11R6.7.x and newer releases. An XvQueryPortAttributes function has been added as well as support for XvImages. XvImages are XImages in alternate color spaces such as YUV and can be passed to the server through shared memory @@ -692,7 +718,11 @@ The Xft library uses configuration files, <tt>/etc/fonts/fonts.conf</tt> and <tt>/etc/fonts/local.conf</tt>, which contains information about which directories contain font files and also provides a sophisticated font aliasing mechanism. Documentation for that -file is included in the <htmlurl name="Xft(3)" url="Xft.3.man"> man page. +file is included in the +<htmlurl name="Xft(3)" url="Xft.3.man">, +<htmlurl name="fontconfig(3)" url="fontconfig.3.man"> and +<htmlurl name="fonts.conf(4)" url="fonts.conf.4.man"> +man pages. </sect2> @@ -756,7 +786,7 @@ Xedit has several new features, including: <item>Flexible search/replace interface that allows regex matches. <item>Please refer to <tt><htmlurl name="xedit(1)" url="xedit.1.html"></tt> for more details. - <item>XPrint support. + <item>Support for printing via Xprint. </itemize> <!-- @@ -767,17 +797,18 @@ Xedit has several new features, including: <sect1>Font support <p> -Details about the font support in X11R&relvers;.x can be found +Details about the font support in X11R&lastfullrelvers;.x can be found in the <htmlurl name="README.fonts" url="fonts.html"> document. <sect1>TrueType support <p> X11R6.7 came with two TrueType backends. The functionality from the -`X-TrueType' backend has been integrated into the `FreeType' backend which -is designed to transparently support all of the functionality from the -`X-TrueType' backend with the exception of the font encoding libraries; the -`FreeType' backend uses only the fontenc-based encoding system . +`X-TrueType' (="XTT") backend has been integrated into the `FreeType' +backend which is designed to transparently support all of the functionality +from the `X-TrueType' backend with the exception of the font encoding +libraries; the `FreeType' backend uses only the fontenc-based encoding +system. <sect1>CID font support <p> @@ -904,7 +935,7 @@ These fonts include all of the glyphs needed for ISO 8859 parts 1 9 and 15. The license terms for the Vera fonts are inclued in the file -<tt/COPYRIGHT.Vera/>. +<tt/COPYRIGHT.Vera/. <sect1>Luxi fonts from Bigelow and Holmes <label id="luxi"> <p> @@ -1029,30 +1060,44 @@ send details to <email>xorg@freedesktop.org</email>. <tag>These people contributed in some way to X11R&relvers;</tag> Paul Anderson, Eric Anholt, +Dave Airlie, +Donnie Berkholz, Daniel Berrange, +Thomas Biege, Russ Blaine, Ryan Breen, Alan Coopersmith, +Jay Cotton, Michel Daenzer, David Dawes, +Kevin DeKorte, Alex Deucher, Stefan Dirsch, Egbert Eich, Rik Faith, Jim Gettys, +Giuseppe Ghibò, +Thomas Gilg, Alexander Gottwald, Mike A. Harris, John Harper, John Heasley, +Jeremy Huddleston, Matthieu Herrb, Alan Hourihane, +Jay Hobson, +Matthias Hopf, Kristian Høsberg, Harold L. Hunt II, Adam Jackson, +Daniel Jacobowitz, Deron Johnson, +Masaki Katakai, +Stephen Kennedy, Ivan Kokshaysky, Stuart Kreitman, -Peter Kunzman, +Peter Kunzman, +Julien Lafon, Nolan Leake, Ryan Lortie, Andreas Luik, @@ -1060,18 +1105,27 @@ Torrey T. Lyons, Roland Mainz, Guy Martin, Kevin E. Martin, +Dan McNichol, +Dagfinn Ilmari Mannsaker, +Simon Montagu, Keith Packard, Greg Parker, +Drew Parsons, Aaron Plattner, +Branden Robinson, Søren Sandmann, Ty Sarna, Yu Shao, +Gustavo Noronha Silva, Bryan Stine, Owen Taylor, Travis Tilley, Ryan Underwood, Ronny Vindenes, -Chisato Yamauchi +Chisato Yamauchi, +Mark Vojkovich, +Tim Yamin, +Hui Yu </descrip> <p> @@ -1089,14 +1143,15 @@ Michael Bax, Jehan Bing, Peter Breitenlohner, Alan Coopersmith, +Thomas Dickey, Egbert Eich, John Dennis, Fabrizio Gennari, Jim Gettys, Alexander Gottwald, -Ralf Habacker +Ralf Habacker, Mike Harris, -Mattheiu Herrb +Mattheiu Herrb, Alan Hourihane, Harold L Hunt II, Elliot Lee, @@ -1106,7 +1161,7 @@ Stuart Kreitman, Andreas Luik, Torrey Lyons, Roland Mainz, -Kevin E. Martin, +Kevin E. Martin, Takuma Murakami, Kensuke Matsuzaki, Keith Packard, @@ -1115,8 +1170,7 @@ Earle F. Philhower III, Benjamin Rienfenstahl, Leon Shiman, Toshimitsu Tanaka, -Nicholas Wourms. - +Nicholas Wourms, 2d3d Inc., Aaron Plattner, Adam de Boor, diff --git a/sgml/Solaris.sgml b/sgml/Solaris.sgml index 44e4d07..482d1b8 100644 --- a/sgml/Solaris.sgml +++ b/sgml/Solaris.sgml @@ -9,7 +9,7 @@ <date>2004 August 18 <ident> -$XdotOrg: xc/programs/Xserver/hw/xfree86/doc/sgml/Solaris.sgml,v 1.3 2004/08/19 16:28:42 kem Exp $ +$XdotOrg$ </ident> <!-- Table of contents --> @@ -195,6 +195,11 @@ There is no known work around.<p> The SPARC port is still quite new, so instability is to be expected (and reported!). It might even have broken some aspects of the x86 port.<p> +<item> +The <tt>kbd</tt> driver is not yet supported on Solaris, but the server +still logs a message that it can't find the <tt>Keyboard</tt> driver and +suggests you use <tt>kbd</tt>. That message should be ignored in this +release. </enum> <sect>Bug Notification<p> Bug reports should be reported using the bugzilla.freedesktop.org using the |