diff options
| author | Egbert Eich <eich@suse.de> | 2004-04-23 19:23:59 +0000 |
|---|---|---|
| committer | Egbert Eich <eich@suse.de> | 2004-04-23 19:23:59 +0000 |
| commit | 250f6d2ae21283f98a052d0a86fb4b10c0beb0ae (patch) | |
| tree | b7e075e0c8b4d289ff2e0f76e814dab2431bda07 | |
| parent | 625cc4967802a36e9b0e7306928d293f12747fc4 (diff) | |
Merging XORG-CURRENT into trunkXACE-SELINUX-MERGE
128 files changed, 15051 insertions, 2490 deletions
diff --git a/hardcopy/BDF/bdf.PS.gz b/hardcopy/BDF/bdf.PS.gz Binary files differindex d6f78a6..79385ad 100644 --- a/hardcopy/BDF/bdf.PS.gz +++ b/hardcopy/BDF/bdf.PS.gz diff --git a/hardcopy/CTEXT/ctext.PS.gz b/hardcopy/CTEXT/ctext.PS.gz Binary files differindex 227044c..b973eea 100644 --- a/hardcopy/CTEXT/ctext.PS.gz +++ b/hardcopy/CTEXT/ctext.PS.gz diff --git a/hardcopy/ICCCM/icccm.PS.gz b/hardcopy/ICCCM/icccm.PS.gz Binary files differindex e0d9454..5855d7a 100644 --- a/hardcopy/ICCCM/icccm.PS.gz +++ b/hardcopy/ICCCM/icccm.PS.gz diff --git a/hardcopy/ICCCM/icccm.idx.PS.gz b/hardcopy/ICCCM/icccm.idx.PS.gz Binary files differindex 9745373..37dd983 100644 --- a/hardcopy/ICCCM/icccm.idx.PS.gz +++ b/hardcopy/ICCCM/icccm.idx.PS.gz diff --git a/hardcopy/ICE/ICElib.PS.gz b/hardcopy/ICE/ICElib.PS.gz Binary files differindex 64d544e..538f19e 100644 --- a/hardcopy/ICE/ICElib.PS.gz +++ b/hardcopy/ICE/ICElib.PS.gz diff --git a/hardcopy/ICE/ice.PS.gz b/hardcopy/ICE/ice.PS.gz Binary files differindex 4b5f8d5..287f40b 100644 --- a/hardcopy/ICE/ice.PS.gz +++ b/hardcopy/ICE/ice.PS.gz diff --git a/hardcopy/SM/SMlib.PS.gz b/hardcopy/SM/SMlib.PS.gz Binary files differindex 06858ff..a81cfe2 100644 --- a/hardcopy/SM/SMlib.PS.gz +++ b/hardcopy/SM/SMlib.PS.gz diff --git a/hardcopy/SM/xsmp.PS.gz b/hardcopy/SM/xsmp.PS.gz Binary files differindex 3c6d0b6..167b4c2 100644 --- a/hardcopy/SM/xsmp.PS.gz +++ b/hardcopy/SM/xsmp.PS.gz diff --git a/hardcopy/X11/xlib.PS.gz b/hardcopy/X11/xlib.PS.gz Binary files differindex 04357e2..80da2ed 100644 --- a/hardcopy/X11/xlib.PS.gz +++ b/hardcopy/X11/xlib.PS.gz diff --git a/hardcopy/X11/xlib.idx.PS.gz b/hardcopy/X11/xlib.idx.PS.gz Binary files differindex 1b92eae..9f754ae 100644 --- a/hardcopy/X11/xlib.idx.PS.gz +++ b/hardcopy/X11/xlib.idx.PS.gz diff --git a/hardcopy/XDMCP/xdmcp.PS.gz b/hardcopy/XDMCP/xdmcp.PS.gz Binary files differindex 837ba0a..a536897 100644 --- a/hardcopy/XDMCP/xdmcp.PS.gz +++ b/hardcopy/XDMCP/xdmcp.PS.gz diff --git a/hardcopy/XIM/xim.PS.gz b/hardcopy/XIM/xim.PS.gz Binary files differindex 9e4c38a..fbc493a 100644 --- a/hardcopy/XIM/xim.PS.gz +++ b/hardcopy/XIM/xim.PS.gz diff --git a/hardcopy/XLFD/xlfd.PS.gz b/hardcopy/XLFD/xlfd.PS.gz Binary files differindex e814c9b..c978f0f 100644 --- a/hardcopy/XLFD/xlfd.PS.gz +++ b/hardcopy/XLFD/xlfd.PS.gz diff --git a/hardcopy/XPRINT/Xprint_FAQ.html b/hardcopy/XPRINT/Xprint_FAQ.html new file mode 100644 index 0000000..cfeaa57 --- /dev/null +++ b/hardcopy/XPRINT/Xprint_FAQ.html @@ -0,0 +1,3080 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Xprint Frequently Asked Questions</title><meta name="generator" content="DocBook XSL Stylesheets V1.62.4"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2873366"></a>Xprint Frequently Asked Questions</h1></div></div><div></div><hr></div><div xmlns:ns1="" class="abstract"><a name="about"></a><p class="title"><b>About this FAQ</b></p><p> + Archive-name: Xprint/FAQ + </p><p> + Version: 0.9 + </p><p> + Last-Modified: 2004/02/16 04:15:16 + </p><p> + Maintained-by: + <span class="othercredit"><span class="firstname">Roland</span> <span class="surname">Mainz</span></span> + <tt class="email"><<a href="mailto:roland.mainz@nrubsig.org">roland.mainz@nrubsig.org</a>></tt> + </p><p> + The following is a list of questions that are frequently asked about + Xprint. + </p><p> + You can help make it an even better-quality FAQ by writing a short + contribution or update and sending it BY EMAIL ONLY to me. + A contribution should consist of a question and an answer, and increasing + number of people sends me contributions of the form "I don't know the + answer to this, but it must be a FAQ, please answer it for me". Please + read the FAQ first (including the item "<a href="#getting_help">Getting Help</a>") + and then feel free to ask me if it is not in the FAQ. + </p><p> + Thanks! + </p><p> + The latest Xprint FAQ and some other goodies can be obtained through http from + <a href="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.html" target="_top"> + http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.html + </a> + or + <a href="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.txt" target="_top"> + http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.txt + </a> + (the DocBook/XML master source file is + <a href="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.xml" target="_top"> + http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.xml + </a>). + </p><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + Note that the FAQ has not been finished yet (nor is it half-finished...), + many items marked with "XXX" as the answer have still to be written (or have + to be copy&pasted from my item collection... <tt class="literal">:)</tt> + </p></div><p> + </p></div><div class="simplesect" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="faq"></a>Frequently Asked Questions with Answers</h2></div></div><div></div></div><div class="qandaset"><dl><dt>1. <a href="#faq_general">General</a></dt><dd><dl><dt>Q: <a href="#what_is_xprint"> + What is "Xprint" ? + </a></dt><dt>Q: <a href="#where_can_i_get_xprint_from"> + Where can I get Xprint/Xprt from ? + </a></dt><dt>Q: <a href="#what_is_xprt"> + What is "Xprt" ? + </a></dt><dt>Q: <a href="#getting_help"> + Where can I get help for problems with Xprint ? + </a></dt><dt>Q: <a href="#advantages_of_xprint"> + "Why do some people like Xprint ?" / "What are the advantages of Xprint ?" + </a></dt><dt>Q: <a href="#contra_xprint"> + Why do some people dislike Xprint ? + </a></dt><dt>Q: <a href="#does_xprint_support_anti_aliased_fonts"> + Does Xprint support anti-aliased fonts ? + </a></dt><dt>Q: <a href="#id2808353"> + How can I check if Xprint is working and should be used ? + </a></dt><dt>Q: <a href="#how_can_i_view_postscript_files"> + How can I view PS(=PostScript) files ? + </a></dt><dt>Q: <a href="#how_can_i_view_pcl_files"> + How can I view PCL files ? + </a></dt><dt>Q: <a href="#id2808532"> + How does Xprt find fonts ? + </a></dt><dt>Q: <a href="#id2808607"> + How can I print TrueType fonts with Xprint ? + </a></dt><dt>Q: <a href="#what_does_ddx_mean"> + What does "DDX" mean ? + </a></dt><dt>Q: <a href="#what_does_dix_mean"> + What does "DIX" mean ? + </a></dt><dt>Q: <a href="#what_does_pdl_mean"> + What does "PDL" mean ? + </a></dt><dt>Q: <a href="#id2808848"> + I have twenty printers installed on my system - but Xprt only shows two + screens. Where are all the other printers ? + </a></dt><dt>Q: <a href="#platforms_supported_by_xprint"> + Which platforms support Xprint ? + </a></dt><dt>Q: <a href="#id2808945"> + I have the broken Xfree86 Xprt binary on my system. Do I need a new + version of libXp.so (the client side X11 extension library for Xprint), + too ? + </a></dt><dt>Q: <a href="#who_do_i_spell_xprint"> + Which spelling is correct - "Xprint", "XPrint", "Xprinter" or Xprt" ? + </a></dt><dt>Q: <a href="#id2809018"> + Which applications support Xprint ? + </a></dt><dt>Q: <a href="#is_xprint_only_for_mozilla"> + Is "Xprint" "mozilla"-only (I saw that it's hosted by mozdev.org) ? + </a></dt><dt>Q: <a href="#id2809195"> + Under which license is the source code from xprint.mozdev.org distributed under ? + </a></dt></dl></dd><dt>2. <a href="#faq_usage">Usage</a></dt><dd><dl><dt>Q: <a href="#id2809283"> + How do I configure Xprint on the client side ? + </a></dt><dt>Q: <a href="#how_do_i_start_xprt"> + How do I start Xprt ? + </a></dt><dt>Q: <a href="#id2874114"> + How can I get a list of printers managed by Xprint ? + </a></dt><dt>Q: <a href="#id2874216"> + How can I start Xprt at boot time ? + </a></dt><dt>Q: <a href="#id2874249"> + How can I start Xprt per-user ? + </a></dt><dt>Q: <a href="#id2874282"> + How can I start Xprt only for one application ? + </a></dt><dt>Q: <a href="#id2874315"> + How can I filter the font path which should be passed to Xprt for + certain fonts ? + </a></dt><dt>Q: <a href="#id2874337"> + How can I manage access control to the Xprt server ? + </a></dt><dt>Q: <a href="#id2874435"> + How can I log access to the Xprt server ? + </a></dt><dt>Q: <a href="#id2874468"> + Does it require "root" permissions to use Xprt/Xprint ? + </a></dt><dt>Q: <a href="#id2874511"> + How can I see the attributes of a printer managed by Xprint ? + </a></dt><dt>Q: <a href="#how_can_i_list_the_font_path_used_by_xprint"> + How can I list the font path used by a Xprt server ? + </a></dt><dt>Q: <a href="#id2874641"> + "xset q" lists all model-specific font dirs (like + PRINTER:/myxpcfg/C/print/models/SPSPARC2/fonts/") - is that a bug ? + </a></dt><dt>Q: <a href="#id2874690"> + My application lists a printer called "xp_ps_spooldir_tmp_Xprintjobs" / + "xp_pdf_spooldir_tmp_Xprintjobs" / "spooldir_tmp_Xprintjobs" / in the + print dialog but I do not have such a print queue installed anywhere. + What is that for a thing ?! + </a></dt><dt>Q: <a href="#manual_xprint_forwarding_via_ssh"> + How can I forward Xprint services when logging-in via ssh to another machine ? + </a></dt></dl></dd><dt>3. <a href="#faq_configuration">Configuration</a></dt><dd><dl><dt>Q: <a href="#id2875040"> + How do I change the defaults for double-sided/single-sided/etc. + printing ? + </a></dt><dt>Q: <a href="#id2875227"> + I am in America and I don't have any ISO A4 paper. How do I change the + default paper size to 8.5 inch x 11 inch (US-Letter) ? + </a></dt><dt>Q: <a href="#id2875790"> + How do I change the default printer resolution ? + </a></dt><dt>Q: <a href="#id2876121"> + How do I change the default settings for "portrait"/"landscape"/"seascape" (=page orientation) ? + </a></dt><dt>Q: <a href="#id2876311"> + How can I prevent Xprt from using any bitmap(=gfx) fonts ? + </a></dt><dt>Q: <a href="#configure_manual_list_of_printers"> + I want only my manually added printers managed by Xprint. How can I + prevent Xprt from looking-up the printer names automatically ? + </a></dt><dt>Q: <a href="#configure_custom_script_to_enumerate_system_printers"> + How can I specify an own program/script to enumerate the printers on my system ? + </a></dt><dt>Q: <a href="#id2876663"> + Which program is used by default by Xprt to enumerate the printers on my system ? + </a></dt><dt>Q: <a href="#id2876920"> + Where can I get more PostScript Type1 fonts from ? + </a></dt><dt>Q: <a href="#id2877269"> + What are PMF fonts (e.g. the *.pmf fonts in + ${XPCONFIGDIR}/C/print/models/%model_name%/fonts/ (or + ${XPCONFIGDIR}/${LANG}/print/models/%model_name%/fonts/)) ? + </a></dt><dt>Q: <a href="#id2877348"> + Can I use the fontserver ("xfs") with Xprt ? + </a></dt><dt>Q: <a href="#id2877411"> + What is a "model-config" ? + </a></dt><dt>Q: <a href="#id2877522"> + Where can I store the default values for printers ? + </a></dt><dt>Q: <a href="#id2877544"> + How can I create my own model-config ? + </a></dt><dt>Q: <a href="#id2877566"> + How can I create my own PMF "fonts" ? + </a></dt><dt>Q: <a href="#id2877607"> + Where can I get more model-configs from ? + </a></dt><dt>Q: <a href="#id2877668"> + If I install Xprt &co. as "root" in the default location and don't need + to set ${XPCONFIGDIR} - where are my configuration files located then ? + </a></dt><dt>Q: <a href="#id2877813"> + Are config files and/or the PMF fonts architecture dependent ? + </a></dt><dt>Q: <a href="#id2877882"> + Can I localise my Xprint/Xprt configuration (l10n) ? + </a></dt><dt>Q: <a href="#id2878167"> + Can I execute my own scripts to process the PostScript files generated + by Xprt ? + </a></dt><dt>Q: <a href="#id2878373"> + How can I disable "xp_ps_spooldir_tmp_Xprintjobs" / "xp_pdf_spooldir_tmp_Xprintjobs" printer targets ? + </a></dt></dl></dd><dt>4. <a href="#faq_troubleshooting">Troubleshooting</a></dt><dd><dl><dt>Q: <a href="#id2878443"> + Xprt refuses to start with the message "sh: lpc: command not found" on + my Linux machine. What does that mean ? + </a></dt><dt>Q: <a href="#id2878532"> + When the application (=client side) tries to connect to the Xprt + (Xserver) side it fails with a + +Xlib: connection to "meridian:52.0" refused by server +Xlib: Client is not authorized to connect to Server + + What does that mean ? + </a></dt><dt>Q: <a href="#id2878802"> + Xprt refuses to start with the message "failed to set default font path + '...' Fatal server error: could not open default font 'fixed'". + What does that mean ? + </a></dt><dt>Q: <a href="#id2878900"> + Just copying my fonts into a directory and adding the path to my Xprt + command line didn't work - I always get "Fatal server error: could not + open default font 'fixed'". What am I doing wrong ? + </a></dt><dt>Q: <a href="#id2879012"> + Xprt refuses to start with the message "Fatal server error: Cannot + establish any listening sockets - Make sure an X server isn't already + running". What does that mean ? + </a></dt><dt>Q: <a href="#id2879040"> + Xprt refuses to start with the message "Fatal server error: Failed to + establish all listening sockets". What does that mean ? + </a></dt><dt>Q: <a href="#id2879085"> + Xprt refuses to start with the message "Fatal server error: could not + open default font 'fixed'" or "Fatal server error: could not open default + cursor font 'cursor'". + </a></dt><dt>Q: <a href="#id2879112"> + Xprt refuses to start with the message "Fatal server error: no screens + found". What does that mean ? + </a></dt><dt>Q: <a href="#printout_only_covers_1_4_of_the_paper"> + "Printing itself works but the printout covers only 1/4 of the paper - what am I doing wrong ?" + </a></dt><dt>Q: <a href="#id2879502"> + "Printing works but I get large borders/margins..." / "[Top] margin is too small" / + "Margins are wrong" / etc. + </a></dt><dt>Q: <a href="#id2879587"> + Xprt prints a warning like "Xp Extension: could not find config dir + /usr/X11R6/lib/X11/C/print" - what does that mean ? + </a></dt><dt>Q: <a href="#id2879661"> + Xprt crashes with "Fatal server error: Beziers this big not yet supported" + What does that mean ? + </a></dt><dt>Q: <a href="#id2879688"> + "My PS Type1 font does not work with my Xserver - how can I fix this ?" + </a></dt><dt>Q: <a href="#id2879800"> + I can't get it working. I have set ${DISPLAY} correctly to point to the + Xprt display and... ... What is going wrong ? + </a></dt><dt>Q: <a href="#id2879847"> + When I try to print via Xprint I get the message "Fatal server error: + unable to exec '/usr/bin/lp'". What is going wrong here ? + </a></dt><dt>Q: <a href="#id2879888"> + The Solaris Xprt prints some error messages about PostScript fonts like + "FOOBAR not found, using Courier. CMEX0123 not found, using Courier." + etc. and uses "Courier" instead of these fonts... + </a></dt><dt>Q: <a href="#id2880176"> + "Xprt refused to start, complaining about a missing dir + (/etc/X11/xserver/C/print/ directory)... I created it by hand (empty) and + started Xprt but it still does not work properly..." + </a></dt><dt>Q: <a href="#id2880231"> + My Linux system already shipps with a '/usr/X11R6/bin/Xprt'-binary. + Do I need the binary distribution from http://xprint.mozdev.org/ ? + </a></dt><dt>Q: <a href="#id2880316"> + I am getting the error message "error opening security policy file + /usr/X11R6/lib/X11/xserver/SecurityPolicy". What does that mean ? + </a></dt><dt>Q: <a href="#id2880368"> + I have modified the "HPLJ4family" [or "HPDJ1600C" etc.] printer model to + work with my PostScript printer, but when I print I get empty places + where some text should be - what am I doing wrong here ? + </a></dt><dt>Q: <a href="#id2880421"> + Xprt outputs warning messages like: + + +Xp Extension: Can't load driver XP-PCL-MONO + init function missing +Xp Extension: Can't load driver XP-RASTER + init function missing + + + What does that mean ? + </a></dt><dt>Q: <a href="#bug_solaris_xprt_removes_spaces_between_words"> + Printing on Solaris with Mozilla/Eclipse [or any other Xprint client] + removes spaces between words. What is going wrong ? + </a></dt><dt>Q: <a href="#id2881185"> + Installation of the "GISWxprint" / "GISWxprintglue" packages fails like this: +# pkgadd -d /space/staging/xprint/GISWxprint.pkg +pkgadd: ERROR: no packages were found in </var/tmp/dstreAAA5Jayyz> + Any idea what I am doing wrong ? + </a></dt><dt>Q: <a href="#multiple_leading_blank_pages"> + Printing page results in [two/three/.../16] leading blank pages, followed by a correct (but offset) page. + Any idea what is going wrong ? + </a></dt></dl></dd><dt>5. <a href="#faq_development">Software development</a></dt><dd><dl><dt>Q: <a href="#id2881454"> + How does the X print server (Xprt) and the Xlib client side differ + from the "normal" video Xserver/video client side ? + </a></dt><dt>Q: <a href="#id2881903"> + How can I get the printable area (e.g. the portion of the page on which + the printer is physically capable of placing ink) of the paper after I + have chosen a paper ? + </a></dt><dt>Q: <a href="#id2881952"> + Do "offscreen" pixmaps work on Xprt ? + </a></dt><dt>Q: <a href="#id2881974"> + How can I get the DPI value for the current Xprt server ? Can I use the + values from "xdpyinfo" ? + </a></dt><dt>Q: <a href="#id2882044"> + Why does Xprt not offer the MIT-SHM protocol extension ? + </a></dt><dt>Q: <a href="#id2882142"> + Does Xprint/Xprt support font rotation ? + </a></dt><dt>Q: <a href="#id2882261"> + When I render something on my window and call XpStartPage all the + rendered stuff is gone, I only get a white, empty paper. + What is going wrong here ? + </a></dt><dt>Q: <a href="#id2882357"> + What is XpStartDoc for ? + </a></dt><dt>Q: <a href="#id2882447"> + How does the XLFD for printer-builtin fonts look like ? / How can I find/identify printer-builtin fonts ? + </a></dt><dt>Q: <a href="#id2882520"> + How can I scale images using the Xprint API ? + </a></dt><dt>Q: <a href="#id2882542"> + 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="#id2882568"> + When I use XpPutDocumentData I get a + BadValue X protocol error. Any idea what am I doing wrong ? + </a></dt><dt>Q: <a href="#id2882608"> + 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="#id2882766"> + How to print with Xt/Athena widgets ? + </a></dt><dt>Q: <a href="#id2882858"> + How to print with Xt/Motif widgets ? + </a></dt><dt>Q: <a href="#id2882883"> + What are the differences between normal display and Xprint display ? + </a></dt><dt>Q: <a href="#id2882905"> + How do I scale images ? + </a></dt><dt>Q: <a href="#id2882926"> + libXp Image scaling vs. max. request size ? + </a></dt><dt>Q: <a href="#id2882948"> + How can I use XprintUtils ? + </a></dt><dt>Q: <a href="#id2882970"> + How do I calculate the DPI values for Xprt DDX screens ? + </a></dt><dt>Q: <a href="#id2882992"> + How do I find scaleable fonts ? + </a></dt><dt>Q: <a href="#id2883014"> + How do I find printer-builtin fonts ? + </a></dt><dt>Q: <a href="#id2883035"> + The XLFD for Printer-builtin fonts look like bitmap fonts - is that bad ? + </a></dt><dt>Q: <a href="#id2883066"> + 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="#id2883134"> + 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="#id2883170"> + Are there any caveats/suggestions when printing via Xt/Motif2 widgets ? + </a></dt><dt>Q: <a href="#id2883723"> + Can I change the paper size/resolution/page orientation/etc. when printing using the + XawPrintShell/XmPrintShell print shells ? + </a></dt></dl></dd></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="qandadiv"><td align="left" valign="top" colspan="2"><a name="faq_general"></a><h4 class="title"><a name="faq_general"></a>1. General</h4></td></tr><tr class="toc" colspan="2"><td align="left" valign="top" colspan="2"><dl><dt>Q: <a href="#what_is_xprint"> + What is "Xprint" ? + </a></dt><dt>Q: <a href="#where_can_i_get_xprint_from"> + Where can I get Xprint/Xprt from ? + </a></dt><dt>Q: <a href="#what_is_xprt"> + What is "Xprt" ? + </a></dt><dt>Q: <a href="#getting_help"> + Where can I get help for problems with Xprint ? + </a></dt><dt>Q: <a href="#advantages_of_xprint"> + "Why do some people like Xprint ?" / "What are the advantages of Xprint ?" + </a></dt><dt>Q: <a href="#contra_xprint"> + Why do some people dislike Xprint ? + </a></dt><dt>Q: <a href="#does_xprint_support_anti_aliased_fonts"> + Does Xprint support anti-aliased fonts ? + </a></dt><dt>Q: <a href="#id2808353"> + How can I check if Xprint is working and should be used ? + </a></dt><dt>Q: <a href="#how_can_i_view_postscript_files"> + How can I view PS(=PostScript) files ? + </a></dt><dt>Q: <a href="#how_can_i_view_pcl_files"> + How can I view PCL files ? + </a></dt><dt>Q: <a href="#id2808532"> + How does Xprt find fonts ? + </a></dt><dt>Q: <a href="#id2808607"> + How can I print TrueType fonts with Xprint ? + </a></dt><dt>Q: <a href="#what_does_ddx_mean"> + What does "DDX" mean ? + </a></dt><dt>Q: <a href="#what_does_dix_mean"> + What does "DIX" mean ? + </a></dt><dt>Q: <a href="#what_does_pdl_mean"> + What does "PDL" mean ? + </a></dt><dt>Q: <a href="#id2808848"> + I have twenty printers installed on my system - but Xprt only shows two + screens. Where are all the other printers ? + </a></dt><dt>Q: <a href="#platforms_supported_by_xprint"> + Which platforms support Xprint ? + </a></dt><dt>Q: <a href="#id2808945"> + I have the broken Xfree86 Xprt binary on my system. Do I need a new + version of libXp.so (the client side X11 extension library for Xprint), + too ? + </a></dt><dt>Q: <a href="#who_do_i_spell_xprint"> + Which spelling is correct - "Xprint", "XPrint", "Xprinter" or Xprt" ? + </a></dt><dt>Q: <a href="#id2809018"> + Which applications support Xprint ? + </a></dt><dt>Q: <a href="#is_xprint_only_for_mozilla"> + Is "Xprint" "mozilla"-only (I saw that it's hosted by mozdev.org) ? + </a></dt><dt>Q: <a href="#id2809195"> + Under which license is the source code from xprint.mozdev.org distributed under ? + </a></dt></dl></td></tr><tr class="question"><td align="left" valign="top"><a name="what_is_xprint"></a><a name="id2807302"></a><b>Q:</b></td><td align="left" valign="top"><p> + What is "Xprint" ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + In short, "Xprint" is an advanced printing system which enables X11 + applications to use devices like printers, FAX or create documents in + formats like PostScript, PDF or SVGprint. + </p><p> + In long, "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 or SVGprint. + 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... + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="where_can_i_get_xprint_from"></a><a name="id2807345"></a><b>Q:</b></td><td align="left" valign="top"><p> + Where can I get Xprint/Xprt from ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns3="" align="left" valign="top"><p> + Xprint is client-server based, therefore two answers: + </p><div class="itemizedlist"><ul type="disc"><li xmlns:ns2=""><p> + The server side is available by default on Solaris (see + <a href="#where_can_i_get_xprint_from_giswxprint_package_note">Note</a> + below) and HP-UX (Xfree86 ships a "Xprt" binary, but that is broken and the server config files + are missing, too). + For those platforms who do not have a (working) Xprt server the you + can get source, binary tarballs and Linux RPMs from + <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a>, + Debian Linux has a package based on the + same sources (see + <a href="http://packages.qa.debian.org/x/xprint-xprintorg.html" target="_top">http://packages.qa.debian.org/x/xprint-xprintorg.html</a>). + + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title"><a name="where_can_i_get_xprint_from_giswxprint_package_note"></a>Note</h3><p> + For Solaris >= 2.7 <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a> + provides the "GISWxprintglue" + and "GISWxprint" packages (available from + <a href="http://xprint.mozdev.org/download.html" target="_top">http://xprint.mozdev.org/download.html</a>) + which provides a single-step + drop-in way to configure and start Xprint at system startup and/or + per-user for all applications and users (the package provides only + startup scripts and some config data and uses the Xprt binary provided + with Solaris (<tt class="filename">/usr/openwin/bin/Xprt</tt>)). + </p></div><p> + </p></li><li><p> + The client-side Xprint support library (<tt class="filename">libXp.so</tt>) is available on all + X11 platforms >=R6.4, including Linux, Solaris, HP-UX, AIX, FreeBSD, NetBSD, etc. + </p><p> + If you do not have it you can build it from the sources available at + <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a>. + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="what_is_xprt"></a><a name="id2807546"></a><b>Q:</b></td><td align="left" valign="top"><p> + What is "Xprt" ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Xprt is the server-side of Xprint. It's just like any other Xserver - it + uses only an other kind of output device (printer instead of framebuffer) + and implements an extra X11 extension ("XpExtension") to handle the + special features/requirements of a "paged device"(=printer etc.). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="getting_help"></a><a name="id2807577"></a><b>Q:</b></td><td align="left" valign="top"><p> + Where can I get help for problems with Xprint ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + The current main site for the Xprint development is <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a> + which hosts various resources including a <a href="http://xprint.mozdev.org/list.html" target="_top">mailinglist</a> + (please subscribe before posting) for end-users, admin and developers. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="advantages_of_xprint"></a><a name="id2807636"></a><b>Q:</b></td><td align="left" valign="top"><p> + "Why do some people like Xprint ?" / "What are the advantages of Xprint ?" + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns4="" align="left" valign="top"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> + Xprint allows an application to query what features (paper size, trays, + orientation, resolutions, plexes, fonts and much more) a printer supports. + For example it is avoidable that a user accidently prints DIN-A4 on a + DIN-A0 poster printer (the print dialog would only offer DIN-A0 as paper + size, e.g. offers only choices which are valid for this printer). + </p></li><li><p> + Server-side, localizeable configuration - changes to the server + config apply to all users without the need to change/updating anything + on the user side (the user may still start his/her own Xprt instance + using his/her preferred configuration). + </p></li><li><p> + Small footprint - ideal for for mobile devices (client side does not + need to process any fonts - that's the job of the server side). + </p></li><li><p> + API not restriced to PostScript (X11R6.5.1 comes with PCL and Raster + implementations - and PDF/G3-FAX/SVG would be possible without problems). + </p></li><li><p> + Scaleable - Xprint can use as many Xprt servers as the user/admin wants. + </p></li><li><p> + "Xprint is designed for the enterprise", e.g. Xprint was designed to + match the needs of large company networks. + </p></li><li><p> + Automatic font handling - font download or the existence of + printer-builtin fonts is automagically handled by Xprt - the application + does not need to know/handle any details (but the application can + optionally get information and control the usage of printer builtin + fonts). + </p></li><li><p> + You can print anything what you can render on the framebuffer(=video + card) Xserver. + </p></li><li><p> + Existing code can be reused 1:1 for printing - which means reduced + development costs. + </p></li><li><p> + Easy support for I18N (internationalization) - you simply render any + fonts in any language with Xprint. + </p></li><li><p> + Network-transparent design - Client can use local or remote Xprt servers + like any other Xserver. + </p></li><li><p> + Uses the X11 protocol - easy adoption of existing code to implement + printer support. And all the network goodies like firewall proxies, + compressors etc. can be used for Xprint without modifications. + </p></li><li><p> + Security: Xprint can use all authentification schemes available in X11 + (like Kerberos5, SecureRPC, MIT-MAGIC-COOKIE or host-based + authentification). + </p></li><li><p> + Enhachements on the server side (Xprt) to not require the change of + client-side code. + </p></li><li><p> + Optimized job output (like the PostScript created by the PostScript DDX) + is usually a lot smaller than the PS code created by other PostScript + engines. + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="contra_xprint"></a><a name="id2807847"></a><b>Q:</b></td><td align="left" valign="top"><p> + Why do some people dislike Xprint ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + There are a few common misconceptions about Xprint. + Let's take a look some of these "myths", some background - and the facts: + </p><div class="blockquote"><blockquote class="blockquote"><div class="qandaset"><dl><dt>Myth: <a href="#id2807878"> + + Xprint prints just a XWD dump of the Xserver bitmap + + </a></dt><dt>Myth: <a href="#id2808002"> + + Xprint cannot handle non-'ISO Latin 1' chars + + </a></dt><dt>Myth: <a href="#id2808043"> + + Xprint uses a 1024x768 screen resolution to render the stuff on + the paper - therefore it will never be able to do high-resolution + stuff + + </a></dt><dt>Myth: <a href="#id2808091"> + + Xprint prints only graphics(=bitmap/gfx) fonts + + </a></dt><dt>Myth: <a href="#id2808170"> + + Xprint does not support pages sizes larger than DIN-A4 + + </a></dt><dt>Myth: <a href="#id2808217"> + + Xprint does not support rotated text + + </a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2807878"></a><a name="id2807881"></a><b>Myth:</b></td><td align="left" valign="top"><p> + “<span class="quote"> + Xprint prints just a XWD dump of the Xserver bitmap + </span>” + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Fact:</b></td><td xmlns:ns5="" align="left" valign="top"><p> + Whoever says Xprint simply does an "xwd"-like dump is wrong. + </p><p> + + In short, Xprint <span class="emphasis"><em>currently</em></span> (X11R6.5.1) supports *four* drivers: + </p><div class="orderedlist"><ol type="1"><li><p> + X to native Postscript + </p></li><li><p> + X to native PCL5 + </p></li><li><p> + X to native PCL3 + </p></li><li><p> + X to a raster which is then feed to something like xpr to + create PS or PCL5 wrapped rasters. + </p></li></ol></div><p> + </p><p> + In long, the original X Print Service ("XPS") was attempted + during CDE 1.0, and they only got so far as the "raster" driver. + </p><p> + As CDE 2.0 came around, Bob Schiefler and others at the X + Consortium agreed that the X Consortium would work on a X to + native PS Level 2 driver and HP would work on a X to native + PCL5 driver. + </p><p> + It was probably the CDE 1.0 effect that left many people with + the impression that Xprint is all about xwd-like window dumps. + NO! Xprint has native PostScript and PCL5 printing and more + drivers (like PDF and SVGprint DDXs etc.) are in the development. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808002"></a><a name="id2808005"></a><b>Myth:</b></td><td align="left" valign="top"><p> + “<span class="quote"> + Xprint cannot handle non-'ISO Latin 1' chars + </span>” + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Fact:</b></td><td align="left" valign="top"><p> + Xprint can print any chars incl. those required for MathML, + Hebrew, Arabic, Japanese etc. etc. + For example - the Xprint module for Mozilla5 is the only print + module which can proprtly print MathML. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808043"></a><a name="id2808046"></a><b>Myth:</b></td><td align="left" valign="top"><p> + “<span class="quote"> + Xprint uses a 1024x768 screen resolution to render the stuff on + the paper - therefore it will never be able to do high-resolution + stuff + </span>” + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Fact:</b></td><td align="left" valign="top"><p> + Xprt uses the screen resolution requested by the application or + the printers default resolution. + For example a 300 DPI printer which supports paper sizes up to + DIN-A4 will get a screen with 3300x3300 pixels (screen width and + height are usually equal to support per-page changes in the + orientation (potrait/landscape etc.), the window size would be + 2400x3149 for "portrait" orientation) - and larger resolutions + will result in larger screens. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808091"></a><a name="id2808094"></a><b>Myth:</b></td><td align="left" valign="top"><p> + “<span class="quote"> + Xprint prints only graphics(=bitmap/gfx) fonts + </span>” + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Fact:</b></td><td align="left" valign="top"><p> + In short, Xprt supports printer-builtin fonts and can + download fonts to the printer if they do not exist on the printer. + </p><p> + In long, this myth seems to have it's root in a <span class="emphasis"><em>feature</em></span> of + Xprt which can - if Xprt gets misconfigured - disable the use of + printer-builtin fonts and the ability to download fonts. + </p><p> + Xprt's PostScript and PCL DDX have the <span class="emphasis"><em>unique</em></span> feature to create + font glyphs from bitmap fonts if they are not available as + printer-builtin fonts nor as PostScipt Type1 fonts. However this + is the fallback - the <span class="emphasis"><em>last</em></span> option used by Xprt. Used if + everything else fails. + But when someone does not pass any PS Type1 fonts with the font + path nor configures a printer model-config (which contains a + description of the features&fonts supported by the printer) Xprt + will never have a chance to use them. And if everything else + fails it has no other option than using what has been left - the + bitmap fonts... + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808170"></a><a name="id2808173"></a><b>Myth:</b></td><td align="left" valign="top"><p> + “<span class="quote"> + Xprint does not support pages sizes larger than DIN-A4 + </span>” + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Fact:</b></td><td align="left" valign="top"><p> + There is no such limitation. + The only limit is the 16bit coordinate system of the X11 + protocol - which is large enougth that Xprint can support paper + sizes <span class="emphasis"><em>larger</em></span> than DIN-A0 oversize papers. There is no problem + with creating your own monster-size DIN-A0 posters using + Xprint-based applications. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808217"></a><a name="id2808220"></a><b>Myth:</b></td><td align="left" valign="top"><p> + “<span class="quote"> + Xprint does not support rotated text + </span>” + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Fact:</b></td><td align="left" valign="top"><p> + Xprint and all it's drivers support the X11 matrix XLFD + enhancement introduced in X11R6 (and future versions of Xprint will + support the <a href="http://stsf.sourceforge.net/" target="_top">STSF</a> font API which supports + matrix transformations as well). + Fonts can be rotated at any angle. Take a look at the + <a href="#faq_development">SOFTWARE DEVELOPMENT</a> section in + this FAQ for examples... + </p></td></tr></tbody></table></div></blockquote></div></td></tr><tr class="question"><td align="left" valign="top"><a name="does_xprint_support_anti_aliased_fonts"></a><a name="id2808312"></a><b>Q:</b></td><td align="left" valign="top"><p> + Does Xprint support anti-aliased fonts ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Question back: When do we need anti-aliased fonts ? + Anti-aliasing is a "hack" to work around the limitations caused by the + low resolution of monitors - they usually operate between 72 DPI and + 150 DPI. + </p><p> + But Xprint operates on printers where the usual <span class="emphasis"><em>minimum</em></span> resolution is + 300 DPI (today's normal office printers support resolutions ranging from + 300 DPI up to 2400 DPI depending on the model; most common is 600 DPI). + Anti-aliasing at those resolutions is not required anymore. + Additionally many printers support their own font anti-aliasing at lower + resolutions which is far better and faster than it could be "done" on the + client side. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808353"></a><a name="id2808356"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I check if Xprint is working and should be used ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Check whether the <tt class="envar">${XPSERVERLIST}</tt> env var is set or not. + If <tt class="envar">${XPSERVERLIST}</tt> is set then Xprint is available and should be used. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="how_can_i_view_postscript_files"></a><a name="id2808392"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I view PS(=PostScript) files ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns8="" align="left" valign="top"><p> + </p><div class="itemizedlist"><ul type="disc"><li xmlns:ns6=""><p> + On Unix/Linux (general): + </p><div class="itemizedlist"><ul type="circle"><li><p> + GhostScript ("gs") and GhostView ("gv" and it's KDE- and Gnome-specific versions "kghostview" and "ggv") + </p></li></ul></div><p> + </p></li></ul></div><p> + </p><div class="itemizedlist"><ul type="disc"><li xmlns:ns7=""><p> + Solaris: + </p><div class="itemizedlist"><ul type="circle"><li><p> + <tt class="filename">/usr/dt/bin/sdtimage</tt> (DPS-based image viewer for CDE) + </p></li><li><p> + <tt class="filename">/usr/openwin/bin/pageview</tt> (DPS-based image viewer for OpenWindows) + </p></li></ul></div><p> + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="how_can_i_view_pcl_files"></a><a name="id2808499"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I view PCL files ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + XXX - <a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=2261" target="_top">xprint.mozdev.org bug 2261</a> + has been filed for that issue. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808532"></a><a name="id2808535"></a><b>Q:</b></td><td align="left" valign="top"><p> + How does Xprt find fonts ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns9="" align="left" valign="top"><p> + + Lookup-rule for Xprt's PostScript DDX to find fonts: + </p><div class="orderedlist"><ol type="1"><li><p> + Printer-builtin fonts (defined by the fonts/-dir in the model-config) + </p></li><li><p> + PostScript fonts (will be downloaded via generated print job) + </p></li><li><p> + GFX-fonts build from X11 scaleable fonts + </p></li><li><p> + GFX-fonts build from X11 bitmap fonts + </p></li></ol></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808607"></a><a name="id2808610"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I print TrueType fonts with Xprint ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns10="" align="left" valign="top"><p> + </p><div class="orderedlist"><ol type="1"><li><p> + Linux Xprt build from <a href="http://xprint.mozdev.org" target="_top">http://xprint.mozdev.org/</a>'s source supports + TrueType fonts out-of-the-box (starting with the 008 development tree; + xprint.mozdev.org's releases <= 007 do not support TrueType fonts) and + and does not require any special actions. + </p></li><li><p> + Sun's Xprt on Solaris (<tt class="filename">/usr/openwin/bin/Xprt</tt>) has TrueType font + support out-of-the-box and does not require any special actions. + </p></li><li><p> + You can setup a TTF-aware X font server ("xfs", see + <span class="citerefentry"><span class="refentrytitle">xfs</span>(1x)</span>) + with the matching TrueType fonts and add the font server location to Xprt's font path. + </p></li><li><p> + Sourceforge has a TrueType to PostScript Type 1 converter project, + see <a href="http://ttf2pt1.sourceforge.net/download.html" target="_top">http://ttf2pt1.sourceforge.net/download.html</a>. + You may convert the TTF files into PT1 files that Xprt can download them + to the printer on demand... + </p></li></ol></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="what_does_ddx_mean"></a><a name="id2808742"></a><b>Q:</b></td><td align="left" valign="top"><p> + What does "DDX" mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + "DDX" is a short term for "Device Dependent X" - the device-specific layer + of a Xserver (<a href="#what_does_dix_mean">"DIX"</a>(="Device Independent X") is the counterpart). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="what_does_dix_mean"></a><a name="id2808785"></a><b>Q:</b></td><td align="left" valign="top"><p> + What does "DIX" mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + "DIX" is a short term for "Device Independent X" - the non-device specific + code of a Xserver (<a href="#what_does_ddx_mean">"DDX"</a>(="Device Dependent X") is the counterpart). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="what_does_pdl_mean"></a><a name="id2808828"></a><b>Q:</b></td><td align="left" valign="top"><p> + What does "PDL" mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + "PDL" is a short term for "Page Description Language". Examples for PDLs are + PostScript, PCL, PDF and SVGprint. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808848"></a><a name="id2808851"></a><b>Q:</b></td><td align="left" valign="top"><p> + I have twenty printers installed on my system - but Xprt only shows two + screens. Where are all the other printers ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + A Xprt screen does not represent a single printer. A Xprt screen + represents a single DDX (currently supported are PostScript, PCL3/5 color, + PCL mono and "raster" output(=1bit deep bitmap). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="platforms_supported_by_xprint"></a><a name="id2808884"></a><b>Q:</b></td><td align="left" valign="top"><p> + Which platforms support Xprint ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + All platforms which support X11 >= R6.4 can use Xprint. The client side + (<tt class="filename">libXp.so</tt>) is available on Linux/FreeBSD(=Xfree86), Solaris, HP-UX and AIX + and the Xprt server side is available by default on Solaris and HP-UX + (Xfree86 shipps with a Xprt binary - but that is broken and unuseable). + The client-side extension library (<tt class="filename">libXp.so</tt>) can be compiled on any + platform, the Xprt server needs minor adjustments for the specific + platforms... + If your platform does not have Xprint (client-side and/or server-side) + you can get the sources from <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a>. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2808945"></a><a name="id2808948"></a><b>Q:</b></td><td align="left" valign="top"><p> + I have the broken Xfree86 Xprt binary on my system. Do I need a new + version of <tt class="filename">libXp.so</tt> (the client side X11 extension library for Xprint), + too ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + No, the <tt class="filename">libXp.so</tt> shared library shipped with Xfree86 or build from + Xfree86 sources is not broken, only the server side ("Xprt") is buggy. + There is no need to replace the library. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="who_do_i_spell_xprint"></a><a name="id2808995"></a><b>Q:</b></td><td align="left" valign="top"><p> + Which spelling is correct - "Xprint", "XPrint", "Xprinter" or Xprt" ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + "Xprint" is the correct one - "XPrint" is just a typo, "Xprinter" is a + complety different product not related to X11/Xprint and "Xprt" is only + the "X11 print server"(=the server side of Xprint). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2809018"></a><a name="id2809021"></a><b>Q:</b></td><td align="left" valign="top"><p> + Which applications support Xprint ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns11="" align="left" valign="top"><p> + There are various applications which support Xprint: + </p><div class="itemizedlist"><ul type="disc"><li><p> + Motif/LessTif (full framework incl. special widgets like <tt class="function">XmPrintShell</tt>) + </p></li><li><p> + <a href="http://www.opengroup.org/cde/" target="_top">Common Desktop Environment (CDE) 2.x</a> + </p></li><li><p> + <a href="http://www.mozilla.org/projects/xprint/" target="_top">Mozilla</a> + </p></li><li><p> + Eclipse + </p></li><li><p> + KDE/Qt support is comming is planned for the end of Dec/2003 + </p></li><li><p> + StarOffice 5.x + </p></li><li><p> + etc. + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="is_xprint_only_for_mozilla"></a><a name="id2809152"></a><b>Q:</b></td><td align="left" valign="top"><p> + Is "Xprint" "mozilla"-only (I saw that it's hosted by mozdev.org) ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + No, Xprint is a general-purpose print API based on the X11 API used by + many applications (<a href="http://www.mozdev.org/" target="_top">mozdev.org</a> is just + hosting the development area, but this does not mean the project is limited to mozilla... + <tt class="literal">:)</tt>). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2809195"></a><a name="id2809198"></a><b>Q:</b></td><td align="left" valign="top"><p> + Under which license is the source code from xprint.mozdev.org distributed under ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns12="" align="left" valign="top"><p> + That's the plain "MIT" license, the same as used by Xfree86.org and X.org: +</p><pre class="programlisting"> +Copyright (c) <year> <copyright holders> + +Permission is hereby granted, free of charge, to any person obtaining a copy of this software +and associated documentation files (the "Software"), to deal in the Software without +restriction, including without limitation the rights to use, copy, modify, merge, publish, +distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the +Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all copies or +substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING +BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND +NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, +DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. +</pre><p> + </p></td></tr><tr class="qandadiv"><td align="left" valign="top" colspan="2"><a name="faq_usage"></a><h4 class="title"><a name="faq_usage"></a>2. Usage</h4></td></tr><tr class="toc" colspan="2"><td align="left" valign="top" colspan="2"><dl><dt>Q: <a href="#id2809283"> + How do I configure Xprint on the client side ? + </a></dt><dt>Q: <a href="#how_do_i_start_xprt"> + How do I start Xprt ? + </a></dt><dt>Q: <a href="#id2874114"> + How can I get a list of printers managed by Xprint ? + </a></dt><dt>Q: <a href="#id2874216"> + How can I start Xprt at boot time ? + </a></dt><dt>Q: <a href="#id2874249"> + How can I start Xprt per-user ? + </a></dt><dt>Q: <a href="#id2874282"> + How can I start Xprt only for one application ? + </a></dt><dt>Q: <a href="#id2874315"> + How can I filter the font path which should be passed to Xprt for + certain fonts ? + </a></dt><dt>Q: <a href="#id2874337"> + How can I manage access control to the Xprt server ? + </a></dt><dt>Q: <a href="#id2874435"> + How can I log access to the Xprt server ? + </a></dt><dt>Q: <a href="#id2874468"> + Does it require "root" permissions to use Xprt/Xprint ? + </a></dt><dt>Q: <a href="#id2874511"> + How can I see the attributes of a printer managed by Xprint ? + </a></dt><dt>Q: <a href="#how_can_i_list_the_font_path_used_by_xprint"> + How can I list the font path used by a Xprt server ? + </a></dt><dt>Q: <a href="#id2874641"> + "xset q" lists all model-specific font dirs (like + PRINTER:/myxpcfg/C/print/models/SPSPARC2/fonts/") - is that a bug ? + </a></dt><dt>Q: <a href="#id2874690"> + My application lists a printer called "xp_ps_spooldir_tmp_Xprintjobs" / + "xp_pdf_spooldir_tmp_Xprintjobs" / "spooldir_tmp_Xprintjobs" / in the + print dialog but I do not have such a print queue installed anywhere. + What is that for a thing ?! + </a></dt><dt>Q: <a href="#manual_xprint_forwarding_via_ssh"> + How can I forward Xprint services when logging-in via ssh to another machine ? + </a></dt></dl></td></tr><tr class="question"><td align="left" valign="top"><a name="id2809283"></a><a name="id2809286"></a><b>Q:</b></td><td align="left" valign="top"><p> + How do I configure Xprint on the client side ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns17="" align="left" valign="top"><p> + There are two env vars which control Xprint on the client side: + </p><div class="orderedlist"><ol type="1"><li xmlns:ns13=""><p> + The env variable <tt class="envar">${XPSERVERLIST}</tt> contains a list of display identifiers + (seperated by whitespace) to tell the application where it can find + the Xprt servers. + Usually <tt class="envar">${XPSERVERLIST}</tt> is set by the profile startup scripts (e.g. + <tt class="filename">/etc/profile</tt> or <tt class="filename">/etc/profile.d/xprint.sh</tt>) using the output of + "/etc/init.d/xprint get_xpserverlist". + Example: +</p><pre class="screen"> + % <b class="userinput"><tt>export XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`"</tt></b> +</pre><p> + Alternativly <tt class="envar">${XPSERVERLIST}</tt> can be set manually: + </p><p> + Example: +</p><pre class="screen"> + % <b class="userinput"><tt>export XPSERVERLIST="littlecat:80 bitdog:72"</tt></b> +</pre><p> + instructs an application to look at the displays 80 on the machine + "littlecat" and display 72 on the machine bigdog to look for Xprt + servers. + </p></li><li xmlns:ns16=""><p> + The env variable <tt class="envar">${XPRINTER}</tt> defines the default printer used by print + applications. The syntax is either <printername> or + <printername>@<display> + + </p><div class="orderedlist"><p class="title"><b>Examples:</b></p><ol type="a"><li xmlns:ns14=""><p> +</p><pre class="screen"> + % <b class="userinput"><tt>export XPRINTER=ps003</tt></b> +</pre><p> + tells an application to look for the first printer named "ps003" on + all Xprt servers. + </p></li><li xmlns:ns15=""><p> +</p><pre class="screen"> + % <b class="userinput"><tt>export XPRINTER="hplaser19@littlecat:80"</tt></b> +</pre><p> + tells an application to look for the printer "hplaser19" on the Xprt + display "littlecat:80". + </p></li></ol></div><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note:</h3><p> + If <tt class="envar">${XPRINTER}</tt> is not set the applications will examine the values of + the <tt class="envar">${PDPRINTER}</tt>, <tt class="envar">${LPDEST}</tt>, and + <tt class="envar">${PRINTER}</tt> env vars (in that order). + </p></div><p> + </p></li></ol></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="how_do_i_start_xprt"></a><a name="id2809516"></a><b>Q:</b></td><td align="left" valign="top"><p> + How do I start Xprt ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns25="" align="left" valign="top"><p> + </p><div class="orderedlist"><ol type="1"><li><p><a name="starting_xprt_on_linux_rpm"></a> + Linux RPM installations on Mandrake/RedHat/SuSE Linux: + Binary RPM packages provided by xprint.mozdev.org (or based on the same + source :) will install <tt class="filename">/etc/init.d/xprint</tt> and related glue + (see <a href="#starting_xprt_general">[4]</a>) + automatically; after a reboot a Xprt instance will be started at system + startup and <tt class="envar">${XPSERVERLIST}</tt> should be populated for all users. + Note that you can start/stop per-user instances using <tt class="filename">/etc/init.d/xprint</tt> + (see <a href="#starting_xprt_general">[4]</a>), too... + </p></li><li xmlns:ns18=""><p><a name="starting_xprt_on_debian_linux"></a> + Debian Linux: + Same as <a href="#starting_xprt_on_linux_rpm">[1]</a>, however Debian does not support + <tt class="filename">/etc/profile.d/</tt> - you have to add the following line to <tt class="filename">/etc/profile</tt> + (for sh/ksh/bash) to populate <tt class="envar">${XPSERVERLIST}</tt>: +</p><pre class="screen"> + <b class="userinput"><tt>export XPSERVERLIST="`/bin/sh /etc/init.d/xprint get_xpserverlist`"</tt></b> +</pre><p> + See <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=171174" target="_top">bugs.debian.org bug 171174</a> + ('"xprint-xprintorg" should automatically populate <tt class="envar">$XPSERVERLIST</tt>') for + further details on this issue... + </p></li><li><a name="starting_xprt_on_solaris"></a><div class="orderedlist"><ol type="a"><li><p><a name="starting_xprt_on_solaris_using_giswxprintglue"></a> + Solaris using the "GISWxprintglue" package: + <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a> + provides a Solaris package called "GISWxprintglue" + which contains all the neccesary configuration files and startup scripts + to use Xprint; after a reboot a Xprt instance will be started at system + startup and <tt class="envar">${XPSERVERLIST}</tt> should be populated for all users. + Note that you can start/stop per-user instances using <tt class="filename">/etc/init.d/xprint</tt> + (see <a href="#starting_xprt_general">[4]</a>), too... + </p></li><li><p><a name="starting_xprt_on_solaris_using_giswxprint"></a> + Solaris using the "GISWxprint" package: + <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a> + provides a Solaris package called "GISWxprint" + which is technically identical to the "GISWxprintglue" + (see <a href="#starting_xprt_on_solaris_using_giswxprintglue">[3a]</a>) but + provides a Xprt binary build from the xprint.mozdve.org sources + ("GISWxprintglue" uses the <tt class="filename">/usr/openwin/bin/Xprt</tt> binary provided by Solaris). + </p></li></ol></div></li><li xmlns:ns19=""><p><a name="starting_xprt_general"></a> + General: Using <tt class="filename">/etc/init.d/xprint</tt> and related glue: + There are startup/shutdown scripts in <tt class="filename">xc/programs/Xserver/Xprint/etc/</tt> + to start/stop/restart Xprt per-machine and/or per-user and to populate the + <tt class="envar">${XPSERVERLIST}</tt> env var: + </p><div class="itemizedlist"><ul type="disc"><li><p> + "<tt class="filename">xc/programs/Xserver/Xprint/etc/init.d/xprint</tt>" is a script for SystemV + and Linux to start/stop/restart Xprt. The script includes installation + and usage details and can be used by both "root" (to start Xprt for all + users) or by a single (non-priviledged, plain) user (to start Xprt + instances only for his/her own use) + </p></li><li><p> + "<tt class="filename">xc/programs/Xserver/Xprint/etc/profile.d/xprint.csh</tt>" and + "<tt class="filename">xc/programs/Xserver/Xprint/etc/profile.d/xprint.sh</tt>" are scripts for + Linux (which support <tt class="filename">/etc/profile.d/</tt> ; note that this does not include + Debian) to populate the <tt class="envar">${XPSERVERLIST}</tt> env var for each user. + </p></li></ul></div><p> + </p></li><li xmlns:ns20=""><p><a name="starting_xprt_manually"></a> + Starting Xprt "manually" (without using <tt class="filename">/etc/init.d/xprint</tt>): + Set the <tt class="envar">${XPCONFIGDIR}</tt> env variable to the directory where Xprt can find + it's configuration data. + </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">WARNING</h3><p> + If Xprt cannot find it's configuration data it will not be + able to use printer-builtin fonts (which are defined by the + model-config in the configuration dir). Without printer-builtin fonts + Xprt <span class="emphasis"><em>may</em></span> fall back to generate font glyphs from bitmap fonts (this + resulted in the MYTH that "Xprt can only print gfx fonts". This is not + <span class="emphasis"><em>TRUE</em></span> - this only happens if Xprt is either misconfigured or no + matching builtin or PS Type1 font is available). + </p><p> + You may want to make a copy of the default configuration directory and + modify it to match your needs. + </p></div><p> + </p></li><li xmlns:ns21=""><p> + Starting Xprt is just as easy as starting any other Xserver: +</p><pre class="screen"> + % <b class="userinput"><tt>Xprt :12</tt></b> +</pre><p> + will start Xprt on display 12 (e.g. set <tt class="envar">${XPSERVERLIST}</tt> to ":12" or + "myhostname:12". + </p><p> + You may want to copy your framebuffer Xserver's font path to be able to + print all fonts which can be displayed on that Xserver. +</p><pre class="screen"> + % <b class="userinput"><tt>Xprt -fp $(xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }") :12</tt></b> +</pre><p> + </p></li></ol></div><p> + </p><div xmlns:ns24="" class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Notes:</h3><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> + The <tt class="filename">/etc/init.d/xprint</tt> has a more advanched filtering scheme based on + regex patters to "accept" and/or "reject" font paths + </p></li><li xmlns:ns22=""><p> + 'xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }"' + may be too simple-minded if your Xserver does not support TrueType + fonts. The following statemement is better in this case since it + filters the font path and removes all path elements which have TrueType + fonts (*.ttf, *.TTF) or TrueType font collections (*.ttc, *.TTC) in + <tt class="filename">fonts.dir</tt>: +</p><pre class="screen"> + % <b class="userinput"><tt>xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }" | + tr "," "\n" | while read i ; do \ + if [ "$(cat ${i}/fonts.dir | egrep -i "ttf|ttc" 2>/dev/null)" == "" ] \ + ; then echo $i ; fi ; done | (fontpath="" ; fpdelim=""; while read i ; \ + do fontpath=${fontpath}${fpdelim}${i} ; fpdelim="," ; done ; echo \ + $fontpath)</tt></b> +</pre><p> + </p></li><li xmlns:ns23=""><p> + It may be easier to just feed all available font paths to Xprt + (BTW: mozilla 1.0 had a bug in that case which resulted in the problem + that it used many many bitmap fonts in that case - this has been fixed + for 1.0.1 and Netscape 7 (that's the reason why the quickguides for + hebrew/cyrillic use the "Xp_dummyfonts" fonts instead of + <tt class="filename">/usr/openwin/lib/X11/fonts/misc/</tt> - to avoid that Mozilla finds bitmap + fonts for the same locale). + The following "small" one-liner finds all fonts (except printer builtin + fonts): +</p><pre class="screen"> + % <b class="userinput"><tt>find /usr/openwin -name fonts.dir | while read i ; do echo + ${i%/fonts.dir} ; done | fgrep -v "models/"</tt></b> +</pre><p> + Plug it into the filter above to remove the Truetype fonts and you are + "done"... :) + </p></li></ul></div><p> + See <a href="#faq_troubleshooting">TROUBLESHOOTING</a> if you run into problems... + </p></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874114"></a><a name="id2874117"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I get a list of printers managed by Xprint ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns28="" align="left" valign="top"><p> + The tool "xplsprinters" is designed for that purpose. It can deliver both + list of printers and attributes supported for a specific list of printers. + Use % xplsprinters -h # to obtain usage information. + Example: + </p><div class="itemizedlist"><ul type="disc"><li xmlns:ns26=""><p> + Get list of available printers: +</p><pre class="screen"> +% <b class="userinput"><tt>xplsprinters</tt></b> +<tt class="computeroutput">printer: hplaserjet001@castor:19 +printer: hpcolor001@castor:19 +printer: laser1@jason:5 +printer: david_dj01@jason:5</tt> +</pre><p> + </p></li><li xmlns:ns27=""><p> + Get information about the supported attrbites of printer "ps002": +</p><pre class="screen"> +% <b class="userinput"><tt>xplsprinters -printer ps002 -l</tt></b> +<tt class="computeroutput">printer: ps002@castor:18 + comment= + model-identifier=HPDJ1600C + default-medium=iso-a4 + default-input-tray= + medium-source-sizes-supported=iso-a4 false 6.35 203.65 6.35 290.65 + medium-source-sizes-supported=na-letter false 6.35 209.55 6.35 273.05 + default-printer-resolution=300 + resolution=300 + default_orientation= + orientation=portrait + orientation=landscape + default_plex= + plex=simplex</tt> +</pre><p> + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874216"></a><a name="id2874219"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I start Xprt at boot time ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + "<tt class="filename">xc/programs/Xserver/Xprint/etc/init.d/xprint</tt>" is a script for SystemV + and Linux to start/stop/restart Xprt at system startup (e.g. per-machine) + or for a single user (e.g. per-user). + The script includes installation and usage details. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874249"></a><a name="id2874252"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I start Xprt per-user ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + "<tt class="filename">xc/programs/Xserver/Xprint/etc/init.d/xprint</tt>" is a script for SystemV + and Linux to start/stop/restart Xprt at system startup (e.g. per-machine) + or for a single user (e.g. per-user). + The script includes installation and usage details. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874282"></a><a name="id2874285"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I start Xprt only for one application ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Create your own version/copy of <tt class="filename">/etc/init.d/xprint</tt> and modify it to fit + your requirements and then make sure that you issue a + "my_xprint_startscript start" before starting the application and a + "my_xprint_startscript stop" after leaving the application. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874315"></a><a name="id2874318"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I filter the font path which should be passed to Xprt for + certain 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="id2874337"></a><a name="id2874340"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I manage access control to the Xprt server ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Access control to Xprt is not differently as to any other Xserver and + 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 <span class="citerefentry"><span class="refentrytitle">xhost</span>(1x)</span>)) + and/or per-machine (using "xhost" (see <span class="citerefentry"><span class="refentrytitle">xhost</span>(1x)</span>) and/or + <tt class="filename">/etc/X<dpy>.hosts</tt> (<dpy> == display number, + e.g. <tt class="filename">/etc/X0.hosts</tt> for display 0) (see <span class="citerefentry"><span class="refentrytitle">Xserver</span>(1x)</span>)) + Consult manual pages + <span class="citerefentry"><span class="refentrytitle">Xsecurity</span>(7)</span>, + <span class="citerefentry"><span class="refentrytitle">xhost</span>(1x)</span>, + <span class="citerefentry"><span class="refentrytitle">Xserver</span>(1x)</span> + etc. for further details. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874435"></a><a name="id2874438"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I log access to the Xprt server ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Logging access to Xprt can be done using the standard Xserver auditing, + see the <span class="citerefentry"><span class="refentrytitle">Xserver</span>(1x)</span> + manual page, option "-audit" + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874468"></a><a name="id2874471"></a><b>Q:</b></td><td align="left" valign="top"><p> + Does it require "root" permissions to use Xprt/Xprint ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + No, both Xprint clients and Xprint server(s) do not require root rights + to work. + </p><p> + Xprint clients are handled like any other X11 application and the Xprt + servers can run without any special requirements. + Solaris is an exception here since it requires to start any Xserver + (incl. Xprt) setgid "root" (set-group-id "root", this is <span class="emphasis"><em>not</em></span> + set-user-id "root") since the sockets/pipe files in /tmp/.X11-pipe/ and + /tmp/.X11-unix/ are only accessible for the group "root". + The workaround is to start Xprt with the option "-pn"; therefore even + Xprt server binaries which are not setgid "root" can run without + problems). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874511"></a><a name="id2874514"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I see the attributes of a printer managed by Xprint ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + "xplsprinters -printer myprinter004 -l" will do the job for printer + "myprinter004". + </p><p> + See + <span class="citerefentry"><span class="refentrytitle">xplsprinters</span>(1x)</span> + for futher usage and a description of the output. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="how_can_i_list_the_font_path_used_by_xprint"></a><a name="id2874560"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I list the font path used by a Xprt server ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns29="" align="left" valign="top"><p> + Figure out the display id of the server which should be queried (we are + using "foobar:98" in this example) and then try this: +</p><pre class="screen"> +% <b class="userinput"><tt>(DISPLAY=foobar:98 xset q | \ +awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }" | \ +tr "," "[\n]")</tt></b> +# Output may look like: +<tt class="computeroutput">PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/HPDJ1600C/fonts/ +PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/SPSPARC2/fonts/ +PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/HPLJ3Si-PS/fonts/ +/usr/openwin/lib/X11/fonts/F3/ +/usr/openwin/lib/X11/fonts/F3bitmaps/ +/usr/openwin/lib/X11/fonts/Type1/ +/usr/openwin/lib/X11/fonts/Speedo/ +/usr/openwin/lib/X11/fonts/misc/ +/usr/openwin/lib/X11/fonts/75dpi/ +/usr/openwin/lib/X11/fonts/100dpi/</tt> +</pre><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note:</h3><p> + Note that the font path items which start with "PRINTER:" are <span class="emphasis"><em>only</em></span> be + sourced <span class="emphasis"><em>after</em></span> the matching printer has been selected and configured + (for developers: After <tt class="function">XpSetContext</tt> has been called). + </p></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874641"></a><a name="id2874644"></a><b>Q:</b></td><td align="left" valign="top"><p> + "xset q" lists all model-specific font dirs (like + PRINTER:/myxpcfg/C/print/models/SPSPARC2/fonts/") - is that a bug ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + No, this is normal. Xprt will add all fonts of all printer models to the + font path - but font path items starting with "PRINTER:" are <span class="emphasis"><em>only</em></span> + available for an application <span class="emphasis"><em>after</em></span> the matching printer has been + selected and configured (for developers: After <tt class="function">XpSetContext</tt> has been + called), <span class="emphasis"><em>before</em></span> that point fonts in these dirs are not available for + an application. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2874690"></a><a name="id2874693"></a><b>Q:</b></td><td align="left" valign="top"><p> + My application lists a printer called "xp_ps_spooldir_tmp_Xprintjobs" / + "xp_pdf_spooldir_tmp_Xprintjobs" / "spooldir_tmp_Xprintjobs" / in the + print dialog but I do not have such a print queue installed anywhere. + What is that for a thing ?! + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns30="" align="left" valign="top"><p> + "xp_ps_spooldir_tmp_Xprintjobs" and "xp_pdf_spooldir_tmp_Xprintjobs" + ("spooldir_tmp_Xprintjobs" was the old, pre-009 name for "xp_ps_spooldir_tmp_Xprintjobs") + are special Xprint printer targets which uses the "PSspooldir" / "PS2PDFspooldir-GS" + printer models. These model config sends PostScript or PDF jobs + to the <tt class="filename">/tmp/Xprintjobs/</tt> directory instead to a physical printer + (quite usefull for people who want to get the PostScript or PDF files as output instead + of printed pages). + </p><p><b>References: </b> + </p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=5092" target="_top">xprint.mozdev.org bug 5092 ("[PS2PDFspooldir-GS] RFE: Add printer model which sends PDF jobs to /tmp/Xprintjobs/")</a></p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="manual_xprint_forwarding_via_ssh"></a><a name="id2874780"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I forward Xprint services when logging-in via ssh to another machine ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns33="" align="left" valign="top"><p> + You have to forward the X11 connection for the Xprint server(s) to the remote system + and set the <tt class="envar">XPSERVERLIST</tt> variable to direct the Xprint clients to the forwarded ports. + + </p><div xmlns:ns31="" class="example"><a name="id2874804"></a><p class="title"><b>Example 1. Login to a remote host using slogin (assuming there is only one + Xprint server listed in <tt class="envar">XPSERVERLIST</tt>)</b></p><pre class="screen">% <b class="userinput"><tt>echo $XPSERVERLIST</tt></b></pre><pre class="screen"><tt class="computeroutput">west:33</tt></pre><p>Add 6000 to the display number ("33" in this example) to get the port number + (X11 port numbers start at port 6000. 6000 is display number "0", 6001 is display number 6001 and so on) + and then ask slogin to forward the port: + </p><pre class="screen">% <b class="userinput"><tt>slogin -R6033:west:6033 -l nrubsig puzzle</tt></b></pre><p> + </p><pre class="screen"><tt class="computeroutput">nrubsig's password: +Last login: Fri Jan 23 04:05:06 2004 from west.informatik.med.uni-giessen.de +Have a lot of fun... +</tt></pre><p> + </p><p> + Then set the <tt class="envar">XPSERVERLIST</tt> env var on the remote host to the forwarded + ports and you are done: + </p><pre class="screen">% <b class="userinput"><tt>export XPSERVERLIST="localhost:33 ${XPSERVERLIST}"</tt></b></pre></div><p> + + </p><div xmlns:ns32="" class="example"><a name="id2874908"></a><p class="title"><b>Example 2. Login to a remote host using slogin (assuming there are multiple + Xprint servers listed in <tt class="envar">XPSERVERLIST</tt>)</b></p><p> + The following small shell script will process the <tt class="envar">XPSERVERLIST</tt> env var and output the + parameters for calling slogin/ssh with all Xprint server ports forwarded: +</p><pre class="programlisting"> +#!/bin/ksh +# xp_print_slogin_args.ksh +# Small example which parses $XPSERVERLIST and prints out how slogin/ssh +# should be used to forward all local Xprint servers + +PORTARGS="" +REMOTE_XPSERVERLIST="" +spacer="" # seperator +remoteport=6100 +remotedisplaynum=100 + +echo "${XPSERVERLIST}" | tr " " "\n" | + while read i ; do + [ "$i" = "" ] && continue + displaynum="${i##*:}" + port="$(( ${displaynum} + 6000 ))" + hostname="${i%:*}" + PORTARGS="${PORTARGS}${spacer}-R${remoteport}:${hostname}:${port}" + REMOTE_XPSERVERLIST="${REMOTE_XPSERVERLIST}${spacer}localhost:${remotedisplaynum}" + + spacer=" " + remoteport=$((${remoteport} + 1)) + remotedisplaynum=$((${remotedisplaynum} + 1)) + done +echo "Log in with: % slogin ${PORTARGS} -l myloginname myremotehost" +echo "Set remote XPSERVERLIST with % export XPSERVERLIST=\"${REMOTE_XPSERVERLIST} \${XPSERVERLIST}\"" +# EOF. +</pre><p> + </p><p>Example usage: + </p><pre class="screen">% <b class="userinput"><tt>xp_print_slogin_args.ksh</tt></b></pre><p> + will print + </p><pre class="screen"><tt class="computeroutput">Log in with: % slogin -R6100:west:6033 -R6101:north:6033 -l myloginname myremotehost +Set remote XPSERVERLIST with % export XPSERVERLIST="localhost:100 localhost:101 ${XPSERVERLIST}"</tt></pre><p> + </p></div><p> + </p></td></tr><tr class="qandadiv"><td align="left" valign="top" colspan="2"><a name="faq_configuration"></a><h4 class="title"><a name="faq_configuration"></a>3. Configuration</h4></td></tr><tr class="toc" colspan="2"><td align="left" valign="top" colspan="2"><dl><dt>Q: <a href="#id2875040"> + How do I change the defaults for double-sided/single-sided/etc. + printing ? + </a></dt><dt>Q: <a href="#id2875227"> + I am in America and I don't have any ISO A4 paper. How do I change the + default paper size to 8.5 inch x 11 inch (US-Letter) ? + </a></dt><dt>Q: <a href="#id2875790"> + How do I change the default printer resolution ? + </a></dt><dt>Q: <a href="#id2876121"> + How do I change the default settings for "portrait"/"landscape"/"seascape" (=page orientation) ? + </a></dt><dt>Q: <a href="#id2876311"> + How can I prevent Xprt from using any bitmap(=gfx) fonts ? + </a></dt><dt>Q: <a href="#configure_manual_list_of_printers"> + I want only my manually added printers managed by Xprint. How can I + prevent Xprt from looking-up the printer names automatically ? + </a></dt><dt>Q: <a href="#configure_custom_script_to_enumerate_system_printers"> + How can I specify an own program/script to enumerate the printers on my system ? + </a></dt><dt>Q: <a href="#id2876663"> + Which program is used by default by Xprt to enumerate the printers on my system ? + </a></dt><dt>Q: <a href="#id2876920"> + Where can I get more PostScript Type1 fonts from ? + </a></dt><dt>Q: <a href="#id2877269"> + What are PMF fonts (e.g. the *.pmf fonts in + ${XPCONFIGDIR}/C/print/models/%model_name%/fonts/ (or + ${XPCONFIGDIR}/${LANG}/print/models/%model_name%/fonts/)) ? + </a></dt><dt>Q: <a href="#id2877348"> + Can I use the fontserver ("xfs") with Xprt ? + </a></dt><dt>Q: <a href="#id2877411"> + What is a "model-config" ? + </a></dt><dt>Q: <a href="#id2877522"> + Where can I store the default values for printers ? + </a></dt><dt>Q: <a href="#id2877544"> + How can I create my own model-config ? + </a></dt><dt>Q: <a href="#id2877566"> + How can I create my own PMF "fonts" ? + </a></dt><dt>Q: <a href="#id2877607"> + Where can I get more model-configs from ? + </a></dt><dt>Q: <a href="#id2877668"> + If I install Xprt &co. as "root" in the default location and don't need + to set ${XPCONFIGDIR} - where are my configuration files located then ? + </a></dt><dt>Q: <a href="#id2877813"> + Are config files and/or the PMF fonts architecture dependent ? + </a></dt><dt>Q: <a href="#id2877882"> + Can I localise my Xprint/Xprt configuration (l10n) ? + </a></dt><dt>Q: <a href="#id2878167"> + Can I execute my own scripts to process the PostScript files generated + by Xprt ? + </a></dt><dt>Q: <a href="#id2878373"> + How can I disable "xp_ps_spooldir_tmp_Xprintjobs" / "xp_pdf_spooldir_tmp_Xprintjobs" printer targets ? + </a></dt></dl></td></tr><tr class="question"><td align="left" valign="top"><a name="id2875040"></a><a name="id2875043"></a><b>Q:</b></td><td align="left" valign="top"><p> + How do I change the defaults for double-sided/single-sided/etc. + printing ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns38="" align="left" valign="top"><p> + This is controlled via the "plex" attribute in the document attribute + pool <tt class="filename">(<tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/attributes/document</tt> and/or + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt>). + Examples: + </p><div class="orderedlist"><ol type="1"><li xmlns:ns34=""><p> + Adding/modifying the following line to/in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt> sets the default plex for + all printers to "duplex": +</p><pre class="screen"> + *plex: duplex +</pre><p> + </p></li><li xmlns:ns35=""><p> + Adding/modifying the following two lines to/in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt> sets the default plex for + all printers to "duplex" except for printer "ps003" which should + default to "simplex": +</p><pre class="screen"> + *plex: duplex + ps003.plex: simplex +</pre><p> + </p></li></ol></div><p> + + </p><div xmlns:ns37="" class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Notes:</h3><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> + Not all printers support all plex modes. The model-config may restrict + the available plex modes. + </p></li><li><p> + Setting a plex mode which is not supported by either the DDX(=driver) + or not specified in the model-config will cause Xprt to not set a + default plex. + </p></li><li><p> + The PostScript DDX supports plex modes "simplex", "duplex" and "tumble". + </p></li><li xmlns:ns36=""><p> + Verification: + Use +</p><pre class="programlisting"> + xplsprinters -l | egrep "^printer:|default_plex=|plex=" +</pre><p> + to view the plex settings for all printers. + </p></li></ul></div><p> + </p></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2875227"></a><a name="id2875230"></a><b>Q:</b></td><td align="left" valign="top"><p> + I am in America and I don't have any ISO A4 paper. How do I change the + default paper size to 8.5 inch x 11 inch (US-Letter) ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns44="" align="left" valign="top"><p> + This is controlled via the "default-medium" attribute in the document + attribute pool (<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/attributes/document</tt> and/or + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt>). + Examples: + </p><div class="orderedlist"><ol type="1"><li xmlns:ns39=""><p> + Adding/modifying the following line to/in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt> sets the default paper size + for all printers to "na-letter": +</p><pre class="screen"> + *default-medium: na-letter +</pre><p> + </p></li><li xmlns:ns40=""><p> + Adding/modifying the following two lines to/in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt> sets the default paper size + for all printers to "na-letter" except for printer "ps003" which should + default to "iso-a4": +</p><pre class="screen"> + *default-medium: na-letter + ps003.default-medium: iso-a4 +</pre><p> + </p></li></ol></div><p> + + </p><div xmlns:ns43="" class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Notes:</h3><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> + xprint.mozdev.org releases >= 007 provides a seperate "document" + attribute pool for en_US(-like) locales (see + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/en_US/print/attributes/document</tt>) which will override the + default ISO-A4 with US-Letter (this feature assumes that <tt class="envar">${LANG}</tt> is set + to "en_US" (or a locale which has similar defaults as "en_US", those + are currently linked to "en_US" in <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/</tt>)) + </p></li><li><p> + Not all printers support all paper sizes. The model-config may restrict + the available paper sizes. + </p></li><li><p> + Setting a paper size which is not supported by either the DDX(=driver) + or not specified in the model-config will cause Xprt to not set a + default paper size. + </p></li><li xmlns:ns41=""><p> + The PostScript DDX supports the following paper sizes: + </p><div class="itemizedlist"><ul type="circle"><li><p> + X.org release 6.6 (X116.6): + <span class="simplelist">"iso-a4", "na-letter", "na-legal", "executive", "iso-designated-long", "na-number-10-envelope"</span> + </p></li><li><p> + xprint.mozdev.org release >= 006: + <span class="simplelist">"na-letter", "na-legal", "executive", "folio", "invoice", "ledger", "quarto", "a", "b", "c", "d", "e", "na-6x9-envelope", "na-10x15-envelope", "monarch-envelope", "na-10x13-envelope", "na-9x12-envelope", "na-number-10-envelope", "na-7x9-envelope", "na-9x11-envelope", "na-10x14-envelope", "na-number-9-envelope", "iso-a0", "iso-a1", "iso-a2", "iso-a3", "iso-a4", "iso-a5", "iso-a6", "iso-a7", "iso-a8", "iso-a9", "iso-a10", "iso-b1", "iso-b2", "iso-b3", "iso-b4", "iso-b5", "iso-b6", "iso-b7", "iso-b8", "iso-b9", "iso-b10", "jis-b1", "jis-b2", "jis-b3", "jis-b4", "jis-b5", "jis-b6", "jis-b7", "jis-b8", "jis-b9", "jis-b10", "iso-c3", "iso-c4", "iso-c5", "iso-c6", "iso-designated-long"</span> + </p></li></ul></div><p> + </p></li><li xmlns:ns42=""><p> + Verification: + Use +</p><pre class="programlisting"> + xplsprinters -l | egrep "^printer:|default-medium=|medium-source-sizes-supported=" +</pre><p> + to view the medium settings for all printers. + The 'medium-source-sizes-supported='-lines have the format XXX. + </p></li></ul></div><p> + </p></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2875790"></a><a name="id2875793"></a><b>Q:</b></td><td align="left" valign="top"><p> + How do I change the default printer resolution ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns50="" align="left" valign="top"><p> + This is controlled via the "default-printer-resolution" attribute in the + document attribute pool (<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/attributes/document</tt> + and/or <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt>). + Examples: + </p><div class="orderedlist"><ol type="1"><li xmlns:ns45=""><p> + Adding/modifying the following line to/in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt> sets the default + resolution for all printers to 600 DPI: +</p><pre class="screen"> + *default-printer-resolution: 600 +</pre><p> + </p></li><li xmlns:ns46=""><p> + Adding/modifying the following two lines to/in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt> sets the default resolution + for all printers to 300 DPI except for printer "tekcolor_ps" which + should default to 1200 DPI: +</p><pre class="screen"> + *default-printer-resolution: 300 + tekcolor_ps.default-printer-resolution: 1200 +</pre><p> + </p></li></ol></div><p> + + </p><div xmlns:ns49="" class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Notes:</h3><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> + Not all printers support all resolutions. The model-config may restrict + the available resolutions. + </p></li><li><p> + Setting a resolution which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt to + not set a default resolution. + </p></li><li xmlns:ns47=""><p> + The PostScript DDX supports the following default resolutions + </p><div class="itemizedlist"><ul type="circle"><li><p> + X.org release 6.6 (X116.6): + <span class="simplelist">300, 600, 720, 940, 1200, 1440, 2400</span> + </p></li><li><p> + xprint.mozdev.org release >= 006: + <span class="simplelist">75, 100, 120, 150, 180, 200, 240, 300, 360, 400, 600, 720, 940, 1200, 1440, 2400</span> + </p></li></ul></div><p> + + </p></li><li xmlns:ns48=""><p> + Verification: + Use +</p><pre class="programlisting"> + xplsprinters -l | egrep "^printer:|default-printer-resolution=|resolution=" +</pre><p> + to view the resolution settings for all printers. + </p></li></ul></div><p> + </p></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2876121"></a><a name="id2876124"></a><b>Q:</b></td><td align="left" valign="top"><p> + How do I change the default settings for "portrait"/"landscape"/"seascape" (=page orientation) ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns55="" align="left" valign="top"><p> + This is controlled via the "content-orientation" attribute in the + document attribute pool (<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/attributes/document</tt> + and/or <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt>). + Examples: + </p><div class="orderedlist"><ol type="1"><li xmlns:ns51=""><p> + Adding/modifying the following line to/in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt> sets the default + orientation for all printers to "portrait": +</p><pre class="screen"> + *content-orientation: portrait +</pre><p> + </p></li><li xmlns:ns52=""><p> + Adding/modifying the following two lines to/in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt> sets the default orientation + for all printers to "portrait" except for printer "ps003" which should + default to "landscape": +</p><pre class="screen"> + *content-orientation: portrait + ps003.content-orientation: landscape +</pre><p> + </p></li></ol></div><p> + + </p><div xmlns:ns54="" class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Notes:</h3><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> + Not all printers support all orientations. The model-config may + restrict the available orientations. + </p></li><li><p> + Setting an orientation which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt to + not set a default orientation. + </p></li><li><p> + The PostScript DDX supports the following orientations: + "portrait", "landscape", "reverse-portrait" and "reverse-landscape". + </p></li><li xmlns:ns53=""><p> + Verification: + Use +</p><pre class="programlisting"> + xplsprinters -l | egrep "^printer:|default_orientation=|orientation=" +</pre><p> + to view the orientation settings for all printers. + </p></li></ul></div><p> + </p></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2876311"></a><a name="id2876314"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I prevent Xprt from using any bitmap(=gfx) fonts ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns61="" align="left" valign="top"><p> + Do not pass any bitmap fonts with the "-fp" (=font path) argument. + However you have to provide a 'fixed' and a 'cursor' font, a Xserver + can't start without having these fonts. + </p><div class="blockquote"><blockquote class="blockquote"><div class="procedure"><p class="title"><b>Procedure 1. Task list:</b></p><ol type="1"><li xmlns:ns56=""><p> + Create a new directory: +</p><pre class="screen"> +% <b class="userinput"><tt>mkdir Xp_dummyfonts</tt></b> +% <b class="userinput"><tt>cd Xp_dummyfonts</tt></b> +</pre><p> + </p></li><li xmlns:ns57=""><p> + Create a <tt class="filename">fonts.alias</tt> file with the following content: +</p><pre class="programlisting"> +! alias for "fixed" font +! original from /usr/openwin/lib/X11/fonts/misc/fonts.alias looks like this: +! fixed "-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1" +fixed -*-r-*--*-*-*-*-*-*-iso8859-1 +! EOF. +</pre><p> + </p></li><li xmlns:ns58=""><p> + Copy or link "<tt class="filename">6x13.pcf.Z</tt>" and "<tt class="filename">cursor.pcf.Z</tt>" and create <tt class="filename">fonts.dir</tt> +</p><pre class="screen"> +% <b class="userinput"><tt>ln -s /usr/openwin/lib/X11/fonts/misc/6x13.pcf.Z .</tt></b> +% <b class="userinput"><tt>ln -s /usr/openwin/lib/X11/fonts/misc/cursor.pcf.Z .</tt></b> +% <b class="userinput"><tt>mkfontdir $PWD</tt></b> +</pre><p> + </p></li><li xmlns:ns59=""><p> + Verify: The directory should now look like this: +</p><pre class="screen"> +% <b class="userinput"><tt>ls -1</tt></b> +<tt class="computeroutput">6x13.pcf.Z +cursor.pcf.Z +fonts.alias +fonts.dir</tt> +</pre><p> + </p></li><li xmlns:ns60=""><p> + Add the full path (e.g. /home/xp/Xp_dummyfonts) as last element + of the font path when starting Xprt: +</p><pre class="screen"> + % <b class="userinput"><tt>Xprt -fp /usr/openwin/lib/X11/fonts/Type1/,/home/xp/Xp_dummyfonts :12</tt></b> +</pre><p> + </p></li></ol></div></blockquote></div><p> + + + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="configure_manual_list_of_printers"></a><a name="id2876542"></a><b>Q:</b></td><td align="left" valign="top"><p> + I want only my manually added printers managed by Xprint. How can I + prevent Xprt from looking-up the printer names automatically ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns62="" align="left" valign="top"><p> + Add a line with "Augment_Printer_List %none%" to + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/Xprinters</tt> (or + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/Xprinters</tt>) and add lines with + "Printer <name>" for each printer <name>. + Example: +</p><pre class="screen"> +Augment_Printer_List %none% +Printer ps001 +Printer ps003 +Printer hplaser6 +</pre><p> + will add only the printers "ps001", ps003" and "hplaser6". + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="configure_custom_script_to_enumerate_system_printers"></a><a name="id2876621"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I specify an own program/script to enumerate the printers on my system ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Add "Augment_Printer_List my_script" to <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/Xprinters</tt> (or + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG</tt>}/print/Xprinters</tt>). + The script must return the printer names - one per line, ASCII-only - to stdout. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2876663"></a><a name="id2876666"></a><b>Q:</b></td><td align="left" valign="top"><p> + Which program is used by default by Xprt to enumerate the printers on my system ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns69="" align="left" valign="top"><p> + This depends on the OS: + </p><div class="itemizedlist"><ul type="disc"><li xmlns:ns63=""><p> + On Solaris (and most other OSes exclusing AIX and Linux): +</p><pre class="screen"> +% <b class="userinput"><tt>lpstat -a | cut -d " " -f 1</tt></b> +</pre><p> + </p></li><li xmlns:ns66=""><p> + On Linux: + </p><div class="itemizedlist"><ul type="circle"><li xmlns:ns64=""><p> + For Xprt build from X11R6.x X.org sources: +</p><pre class="screen"> +% <b class="userinput"><tt>lpc status | grep -v '^\t' | sed -e /:/s///</tt></b> # '\t' means TAB +</pre><p> + </p></li><li xmlns:ns65=""><p> + For Xprt build from xprint.mozdev.org <= release 008 sources (both lines are executed + to support both LPRng and CUPS (using the CUPS *BSD compatibility tools)): +</p><pre class="screen"> +% <b class="userinput"><tt>lpc status | awk '/:$/ && !/@/ { print $1 }' | sed -e /:/s/// ; \ + lpc -a status | awk '/@/ && !/:/ { split( $1, name, \"@\" ); print name[1]; }'</tt></b> +</pre><p> + </p></li><li><p> + Xprt build from xprint.mozdev.org >= release 009 sources uses a more flexible scheme + which tries to enumerate the print spoolers in the order "CUPS" (using the normal CUPS + (SYSV-like) commands), "LPRng" and finally "*BSD", the first working (=print queues are + found) print spooler is chosen. + The spooler(s) being used (and the query order) can be changed by the "-XpSpoolerType" + command line option. + The list of commands used to enumerate the queues for a specific spooler type + can be found in <tt class="filename">xc/programs/Xserver/Xprint/spooler.c</tt> + </p></li></ul></div><p> + </p></li><li xmlns:ns67=""><p> + On AIX v4: +</p><pre class="screen"> +% <b class="userinput"><tt>lsallq | grep -v '^bsh$'</tt></b> +</pre><p> + </p></li></ul></div><p> + </p><div xmlns:ns68="" class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Notes:</h3><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> + See <tt class="filename">xc/programs/Xserver/Xprint/Init.c</tt> (xprint.mozdev.org >= release 009 uses + <tt class="filename">xc/programs/Xserver/Xprint/spooler.c</tt>) for a complete list of commands + used on the specific platforms to enumerate the printers. + </p></li><li><p> + Note that the output is always piped through "sort" to get an + alphabetical order (the "default" printer is not chosen/defined + here(=server side), the client side is responsible to choose a default + printer. + See FAQ item about the <tt class="envar">${XPRINTER}</tt> env var how to set your default + printer). + </p></li></ul></div><p> + </p></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2876920"></a><a name="id2876923"></a><b>Q:</b></td><td align="left" valign="top"><p> + Where can I get more PostScript Type1 fonts from ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns73="" align="left" valign="top"><p> + Some sources: + </p><div class="itemizedlist"><ul type="disc"><li xmlns:ns71=""><p> + Adobe: + + </p><div class="itemizedlist"><ul type="circle"><li><p> + Commercial fonts: + <a href="http://www.adobe.com/type/main.html" target="_top">http://www.adobe.com/type/main.html</a> + </p></li><li xmlns:ns70=""><p> + Free Euro font: + </p><div class="itemizedlist"><ul type="disc"><li><p> + Single-glyph (e.g. it contains <span class="emphasis"><em>only</em></span> the euro char) euro font: + <a href="http://www.adobe.com/type/eurofont.html" target="_top">http://www.adobe.com/type/eurofont.html</a> or + <a href="ftp://ftp.adobe.com/pub/adobe/type/win/all/" target="_top">ftp://ftp.adobe.com/pub/adobe/type/win/all/</a> + ("eurofont.exe" can be unzipped using "unzip") + </p></li><li><p> + ISO8859-15: + XXX - WANTED!! + </p></li></ul></div><p> + </p></li></ul></div><p> + </p></li><li xmlns:ns72=""><p> + Solaris shipps with various PS Type 1 fonts: + </p><div class="itemizedlist"><ul type="circle"><li><p> + Arabic: + <tt class="filename">/usr/openwin/lib/locale/ar/X11/fonts/Type1/</tt> + (<tt class="filename">fonts.dir</tt> and <tt class="filename">fonts.scale</tt> missing, maybe they miss the + presentation forms a&b, too [unconfirmed]) + </p></li><li><p> + ISO-8859-13 (Latin 8): + <tt class="filename">/usr/openwin/lib/locale/iso_8859_13/X11/fonts/Type1/</tt> + </p></li><li><p> + ISO-8859-5 (Latin 5): + <tt class="filename">/usr/openwin/lib/locale/iso_8859_9/X11/fonts/Type1/</tt> + </p></li><li><p> + ISO-8859-8/Hebrew: + <tt class="filename">/usr/openwin/lib/locale/iso_8859_8/X11/fonts/Type1</tt> + (BROKEN, even "type1fix" cannot fix them. Use the hebrew fonts from + + <a href="broken-link/PS_Type1_iso8859-8.tar.gz" target="_top"> + broken-link-/PS_Type1_iso8859-8.tar.gz</a>) + </p></li><li><p> + ISO-8859-7/Modern greek: + <tt class="filename">/usr/openwin/lib/locale/iso_8859_7/X11/fonts/Type1/</tt> + </p></li><li><p> + ISO-8859-5/Cryrillic: + <tt class="filename">/usr/openwin/lib/locale/iso_8859_5/X11/fonts/Type1/</tt> + </p></li><li><p> + ISO-8859-4 (Latin 4): + <tt class="filename">/usr/openwin/lib/locale/iso_8859_4/X11/fonts/Type1/</tt> + </p></li><li><p> + ISO-8859-2 (Latin 2): + <tt class="filename">/usr/openwin/lib/locale/iso_8859_2/X11/fonts/Type1/</tt> + </p></li><li><p> + ISO-8859-1 (Latin 1) and Symbol fonts: + <tt class="filename">/usr/openwin/lib/X11/fonts/Type1/</tt> + </p></li></ul></div><p> + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2877269"></a><a name="id2877272"></a><b>Q:</b></td><td align="left" valign="top"><p> + What are PMF fonts (e.g. the *.pmf fonts in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/models/%model_name%/fonts/</tt> (or + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/models/%model_name%/fonts/</tt>)) ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + PMF "fonts" are "printer metric files" (.pmf) that describe the metrics + of the fonts (which means they do not contain any data to render the + fonts - they contain only the plain metrics of a font) which are built + into the printer (ROM or via font catridge etc.). + The file format is identical to the PCF ("Portable Compiled Format") font + format except that the bitmap data is not provided. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2877348"></a><a name="id2877351"></a><b>Q:</b></td><td align="left" valign="top"><p> + Can I use the fontserver ("xfs") with Xprt ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + You can use Xprt with the font server ("xfs") like with any other + Xserver - but it is not recommded since the font server protocol does + not allow access to the native font format and therefore disables font + download, e.g. both PS Type1 and TrueType fonts cannot be downloaded + anymore and Xprt will fall-back to embed them as bitmap glyphs in the + print job (e.g. the fonts will still appear correctly in the printout, + but the quality may be reduced since downloaded fonts are always better + than bitmap glyphs). + (users of xprint.mozdev.org-release <= 006 may see + <a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=2092" target="_top">xprint.mozdev.org bug 2092</a> + if they use "xfs"; this has been fixed in the 007 release!) + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2877411"></a><a name="id2877414"></a><b>Q:</b></td><td align="left" valign="top"><p> + What is a "model-config" ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns74="" align="left" valign="top"><p> + The term "model-config" refers to the subdirs in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/models/</tt>. + There subdirs contain information + about the attributes for a specific printer model or family/class of + printer models. In particular there are two kinds of information: + + </p><div class="itemizedlist"><ul type="disc"><li><p> + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/models/${NAME_OF_MODEL}/model-config</tt>" + this file defines a set of attributes supported by this specific printer + (-family/-class/etc.) + and + </p></li><li><p> + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/models/${NAME_OF_MODEL}/fonts/</tt>" - a + directory which contains a set of PMF (printer metrics file) fonts + builtin into the printer itself (actually the PMF "font" format + contains only metrics information and no glyphs). + These fonts are only available to the application <span class="emphasis"><em>after</em></span> the + application has selected a printer and configured it (for developers: + After <tt class="function">XpSetContext</tt> has been called). + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2877522"></a><a name="id2877525"></a><b>Q:</b></td><td align="left" valign="top"><p> + Where can I store the default values for printers ? + </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="id2877544"></a><a name="id2877547"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I create my own model-config ? + </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="id2877566"></a><a name="id2877569"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I create my own PMF "fonts" ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + XXX - no solution yet, but + <a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=2430" target="_top">xprint.mozdev.org bug 2430 + ("RFE: Need tool to create PMF (printer metrics file) fonts")</a> + has been filed to create a freeware tool to create such fonts. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2877607"></a><a name="id2877610"></a><b>Q:</b></td><td align="left" valign="top"><p> + Where can I get more model-configs from ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + If you miss a model-config for your printer please open a bug/RFE at + <a href="http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi?product=xprint&component=Server%3A%2BConfig%3A%2Bmodel-configs" target="_top"> + http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi?product=xprint&component=Server%3A+Config%3A+model-configs</a> + (e.g. <a href="http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi" target="_top">http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi</a>, product "Xprint", component + "Server Config: model-configs"). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2877668"></a><a name="id2877672"></a><b>Q:</b></td><td align="left" valign="top"><p> + If I install Xprt &co. as "root" in the default location and don't need + to set <tt class="envar">${XPCONFIGDIR}</tt> - where are my configuration files located then ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns76="" align="left" valign="top"><p> + This is platform-specific, based on the "XPrintDir" Imake variable set + at build time. Default location for plain X11R6.x is + "<tt class="filename">${XProjectRoot}/lib/X11/xserver</tt>" (set at build time), but some + platforms modify "XPrintDir" to alternate locations: + </p><div class="itemizedlist"><ul type="disc"><li><p> + Solaris sets <tt class="envar">${XPCONFIGDIR}</tt> to <tt class="filename">/usr/openwin/server/etc/XpConfig/</tt> + </p></li><li><p> + Linux (non-Debian) sets <tt class="envar">${XPCONFIGDIR}</tt> to <tt class="filename">/usr/X11R6/lib/X11/xserver/</tt> + or <tt class="filename">/etc/X11/xserver/</tt> + </p></li><li><p> + Debian Linux sets <tt class="envar">${XPCONFIGDIR}</tt> to <tt class="filename">/usr/share/Xprint/xserver/</tt> + </p></li></ul></div><p> + </p><div xmlns:ns75="" class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> + If you don't know where the default location for <tt class="envar">${XPCONFIGDIR}</tt> is + located try +</p><pre class="programlisting"> + strings -a /usr/openwin/bin/Xprt | grep XPRINTDIR +</pre><p> - it <span class="emphasis"><em>may</em></span> + return some debug info from the binary containing the builtin XpConfig + path. + </p></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2877813"></a><a name="id2877816"></a><b>Q:</b></td><td align="left" valign="top"><p> + Are config files and/or the PMF fonts architecture dependent ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + The PMF fonts are a variant of the PCF font format, they are + (like the PCF format) architecture-independent. + These fonts must be kept together with the other model config data since + they depend on the printer model (de facto + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/models/</tt> (and/or + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/models/</tt>) should be supplied by the printer + vendors (but most people will create their own models on demand since + I doubt that any vendor except HP, Sun and xprint.mozdev.org staff ever + looked at that stuff)). + Per definition they are read-only data supplied by the vendor, but + modifying them may be usefull, too. + I would say it is recommended to put treat all Xprint files in + <tt class="envar">${XPCONFIGDIR}</tt> as read-only vendor data; admins should create copies of + this tree on demand (and/or (soft-)link some files) and set + <tt class="envar">${XPCONFIGDIR}</tt> to the modified config data. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2877882"></a><a name="id2877885"></a><b>Q:</b></td><td align="left" valign="top"><p> + Can I localise my Xprint/Xprt configuration (l10n) ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns78="" align="left" valign="top"><p> + Yes, Xprt supports localisation ("l10n") by default. Default values for + all locales are stored in <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/</tt>, locale-specific + settings can be set in <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/</tt> + Rules: + </p><div class="itemizedlist"><ul type="disc"><li><p> + Attribute pools + ("<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/*/print/attributes/document</tt>", + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/*/print/attributes/job</tt>", + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/*/print/attributes/printer</tt>" and + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/*/print/models/*/model-config</tt>"): + "document", "job" and "printer" attribute pools and printer + model-configs are sourced first from the + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/</tt>"-directory, then they are overridden by any + attributes from the locale-specific pools (in + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/</tt>"), e.g. any values set in + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/*</tt>" and + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/models/*/model-config</tt>" will automatically + apply to all other locales unless they are overridden by + locale-specific versions of these files + ("<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/attributes/*</tt>", + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/models/*/model-config</tt>") + </p></li><li><p> + "Xprinters" (list of printers): + If there is a locale-specific <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/Xprinters</tt> present + it will be used instead of <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/Xprinters</tt> (e.g. values set + in <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/Xprinters</tt> will be ignored and the values from + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/Xprinters</tt> will be used instead). + </p></li><li xmlns:ns77=""><p> + Xprt will determinate the locale which should be used based on the + <tt class="envar">${LANG}</tt>-environment vaiable at startup time. If there is no such + variable set at that time LANG="C" is assumed. + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note:</h3><p> + Attribute values for paper names and orientation names refer to + builtin strings in the DDX code (which are itself based on + international standards), these cannot be changed to your own + "inventions" (it does it make sense to try to "localize" paper names - + "ISO-A4" is "ISO-A4" even in japanese/hebrew/german etc.). + Locale-spefific attribute pools can set their own, different values - + but only within the allowed range of values supported by the DDX and + printers's model-config. + </p></div><p> + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2878167"></a><a name="id2878170"></a><b>Q:</b></td><td align="left" valign="top"><p> + Can I execute my own scripts to process the PostScript files generated + by Xprt ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns82="" align="left" valign="top"><p> + Yes, there are at least two possible solutions: + </p><div class="orderedlist"><ol type="1"><li><p> + Create your own model-config which uses a custom "xp-spooler-command" + value - the xprint.mozdev.org's + "PSspooldir" model config (see + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/models/PSspooldir/</tt>" and + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/printer</tt>" and + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/Xprinters</tt>") + and + "PS2PDFspooldir-GS" model config (see + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/models/PS2PDFspooldir-GS/</tt>" and + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/printer</tt>" and + "<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/Xprinters</tt>") + are good examples for that. + </p></li><li xmlns:ns81=""><p> + Use an existing "model-config" (which would normally send it's data to + a printer using the default print spooler command) and provide a + custom "xp-spooler-command". + </p><div class="blockquote"><blockquote class="blockquote"><div class="procedure"><p class="title"><b>Procedure 2. + Example (using "SPSPARC2" as printer model, <tt class="filename">/w/xp_conv</tt> + as the script to execute and "myscriptprinter" as name of the printer): + </b></p><ol type="1"><li xmlns:ns79=""><p> + Edit <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/printer</tt> and add these lines + (Xprt will replace "%printer-name%" with the printer's name, + "%copy-count%" with the number of job copies, "%job-name%" with the + job's title and "%options%" with any custom spooler options): +</p><pre class="screen"> +myscriptprinter.xp-model-identifier: SPSPARC2 +myscriptprinter.xp-spooler-command: /w/xp_conv -p %printer-name% -c %copy-count% -t %job-name% -o "%options%" +</pre><p> + </p></li><li xmlns:ns80=""><p> + Edit <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/Xprinters</tt> and append this line: +</p><pre class="screen"> +Printer myscriptprinter +</pre><p> + </p></li></ol></div></blockquote></div><p> + + </p></li></ol></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2878373"></a><a name="id2878376"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I disable "xp_ps_spooldir_tmp_Xprintjobs" / "xp_pdf_spooldir_tmp_Xprintjobs" printer targets ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns83="" align="left" valign="top"><p> + Edit <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/Xprinters</tt> and + remove or comment-out (using '#') the lines "Printer xp_ps_spooldir_tmp_Xprintjobs" + and "Printer xp_pdf_spooldir_tmp_Xprintjobs". + + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note:</h3><p> + Note that Xprt will <span class="emphasis"><em>NOT</em></span> start if this printer has been removed/disabled + and no other print queue is available (e.g. if "xp_ps_spooldir_tmp_Xprintjobs" + and "Printer xp_pdf_spooldir_tmp_Xprintjobs" are the only printer target available). + </p></div><p> + </p></td></tr><tr class="qandadiv"><td align="left" valign="top" colspan="2"><a name="faq_troubleshooting"></a><h4 class="title"><a name="faq_troubleshooting"></a>4. Troubleshooting</h4></td></tr><tr class="toc" colspan="2"><td align="left" valign="top" colspan="2"><dl><dt>Q: <a href="#id2878443"> + Xprt refuses to start with the message "sh: lpc: command not found" on + my Linux machine. What does that mean ? + </a></dt><dt>Q: <a href="#id2878532"> + When the application (=client side) tries to connect to the Xprt + (Xserver) side it fails with a + +Xlib: connection to "meridian:52.0" refused by server +Xlib: Client is not authorized to connect to Server + + What does that mean ? + </a></dt><dt>Q: <a href="#id2878802"> + Xprt refuses to start with the message "failed to set default font path + '...' Fatal server error: could not open default font 'fixed'". + What does that mean ? + </a></dt><dt>Q: <a href="#id2878900"> + Just copying my fonts into a directory and adding the path to my Xprt + command line didn't work - I always get "Fatal server error: could not + open default font 'fixed'". What am I doing wrong ? + </a></dt><dt>Q: <a href="#id2879012"> + Xprt refuses to start with the message "Fatal server error: Cannot + establish any listening sockets - Make sure an X server isn't already + running". What does that mean ? + </a></dt><dt>Q: <a href="#id2879040"> + Xprt refuses to start with the message "Fatal server error: Failed to + establish all listening sockets". What does that mean ? + </a></dt><dt>Q: <a href="#id2879085"> + Xprt refuses to start with the message "Fatal server error: could not + open default font 'fixed'" or "Fatal server error: could not open default + cursor font 'cursor'". + </a></dt><dt>Q: <a href="#id2879112"> + Xprt refuses to start with the message "Fatal server error: no screens + found". What does that mean ? + </a></dt><dt>Q: <a href="#printout_only_covers_1_4_of_the_paper"> + "Printing itself works but the printout covers only 1/4 of the paper - what am I doing wrong ?" + </a></dt><dt>Q: <a href="#id2879502"> + "Printing works but I get large borders/margins..." / "[Top] margin is too small" / + "Margins are wrong" / etc. + </a></dt><dt>Q: <a href="#id2879587"> + Xprt prints a warning like "Xp Extension: could not find config dir + /usr/X11R6/lib/X11/C/print" - what does that mean ? + </a></dt><dt>Q: <a href="#id2879661"> + Xprt crashes with "Fatal server error: Beziers this big not yet supported" + What does that mean ? + </a></dt><dt>Q: <a href="#id2879688"> + "My PS Type1 font does not work with my Xserver - how can I fix this ?" + </a></dt><dt>Q: <a href="#id2879800"> + I can't get it working. I have set ${DISPLAY} correctly to point to the + Xprt display and... ... What is going wrong ? + </a></dt><dt>Q: <a href="#id2879847"> + When I try to print via Xprint I get the message "Fatal server error: + unable to exec '/usr/bin/lp'". What is going wrong here ? + </a></dt><dt>Q: <a href="#id2879888"> + The Solaris Xprt prints some error messages about PostScript fonts like + "FOOBAR not found, using Courier. CMEX0123 not found, using Courier." + etc. and uses "Courier" instead of these fonts... + </a></dt><dt>Q: <a href="#id2880176"> + "Xprt refused to start, complaining about a missing dir + (/etc/X11/xserver/C/print/ directory)... I created it by hand (empty) and + started Xprt but it still does not work properly..." + </a></dt><dt>Q: <a href="#id2880231"> + My Linux system already shipps with a '/usr/X11R6/bin/Xprt'-binary. + Do I need the binary distribution from http://xprint.mozdev.org/ ? + </a></dt><dt>Q: <a href="#id2880316"> + I am getting the error message "error opening security policy file + /usr/X11R6/lib/X11/xserver/SecurityPolicy". What does that mean ? + </a></dt><dt>Q: <a href="#id2880368"> + I have modified the "HPLJ4family" [or "HPDJ1600C" etc.] printer model to + work with my PostScript printer, but when I print I get empty places + where some text should be - what am I doing wrong here ? + </a></dt><dt>Q: <a href="#id2880421"> + Xprt outputs warning messages like: + + +Xp Extension: Can't load driver XP-PCL-MONO + init function missing +Xp Extension: Can't load driver XP-RASTER + init function missing + + + What does that mean ? + </a></dt><dt>Q: <a href="#bug_solaris_xprt_removes_spaces_between_words"> + Printing on Solaris with Mozilla/Eclipse [or any other Xprint client] + removes spaces between words. What is going wrong ? + </a></dt><dt>Q: <a href="#id2881185"> + Installation of the "GISWxprint" / "GISWxprintglue" packages fails like this: +# pkgadd -d /space/staging/xprint/GISWxprint.pkg +pkgadd: ERROR: no packages were found in </var/tmp/dstreAAA5Jayyz> + Any idea what I am doing wrong ? + </a></dt><dt>Q: <a href="#multiple_leading_blank_pages"> + Printing page results in [two/three/.../16] leading blank pages, followed by a correct (but offset) page. + Any idea what is going wrong ? + </a></dt></dl></td></tr><tr class="question"><td align="left" valign="top"><a name="id2878443"></a><a name="id2878446"></a><b>Q:</b></td><td align="left" valign="top"><p> + Xprt refuses to start with the message "sh: lpc: command not found" on + my Linux machine. What does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns84="" align="left" valign="top"><p> + Some versions of Xprt look up printer queues using "lpc" on Linux. + In this case "lpc" cannot be found for some reason. + Solution: + Find the place where "lpc" is installed on your machine (some + distributions put it into <tt class="filename">/usr/sbin</tt>, some into <tt class="filename">/usr/bin/</tt>) and check + whether your <tt class="envar">PATH</tt> env var includes this directory. + Example (if "lpc" is located in <tt class="filename">/usr/sbin/</tt>): +</p><pre class="screen"> + % <b class="userinput"><tt>which lpc</tt></b> + <tt class="computeroutput">/usr/sbin/lpc</tt> + % <b class="userinput"><tt>export PATH=$PATH:/usr/sbin</tt></b> + # Start Xprt ... + % <b class="userinput"><tt>Xprt <your-options-come-here></tt></b> +</pre><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2878532"></a><a name="id2878536"></a><b>Q:</b></td><td xmlns:ns85="" align="left" valign="top"><p> + When the application (=client side) tries to connect to the Xprt + (Xserver) side it fails with a +</p><pre class="screen"> +<tt class="computeroutput">Xlib: connection to "meridian:52.0" refused by server +Xlib: Client is not authorized to connect to Server</tt> +</pre><p> + What does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns90="" align="left" valign="top"><p> + X11 implements access control. You can have host-based, cookie-based (a + "cookie" is used like a passport) or user-based (SecureRPC or Kerberos5) + authentification. <span class="citerefentry"><span class="refentrytitle">Xsecurity</span>(7)</span> + has most of the details. + </p><div class="orderedlist"><ol type="1"><li xmlns:ns86=""><p><b> + No access control: + . </b> + If you do not want to use access control for Xprt then you can start it + with the option "-ac" (see <span class="citerefentry"><span class="refentrytitle">Xserver</span>(1x)</span>) + to disable the access control. + Example: +</p><pre class="screen"> + % <b class="userinput"><tt>Xprt -ac -audit 4 :12</tt></b> +</pre><p> + will start Xprt with access control disabled and with auditing enabled + (e.g. the "-audit 4" option). + </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title"> + WARNING + </h3><p> + Disabling the access control will enable <span class="emphasis"><em>everyone</em></span> who can + access Xprt to print on your printers (that's why the above example + shows how to use auditing, too - that you can see who does something + with Xprt...) !! + </p></div><p> + </p></li><li xmlns:ns89=""><p><b> + Host-based access control: + . </b> + Host-based access control can be archived using <tt class="filename">/etc/X<dpy>.hosts</tt> + (<dpy> == display number, e.g. <tt class="filename">/etc/X0.hosts</tt> for display 0 (see + <span class="citerefentry"><span class="refentrytitle">Xserver</span>(1x)</span> + manual page for further details)). + </p><div class="blockquote"><blockquote class="blockquote"><div class="procedure"><p class="title"><b>Procedure 3. Example</b></p><ol type="1"><li xmlns:ns87=""><p> + Add the following line to `<tt class="filename">/etc/X12.hosts</tt>' (assuming you want that + the hosts 'merkur' and 'mars' should be able to access the Xprt + server running as display 12 on your host 'neptun'): +</p><pre class="screen"> +INET:merkur +INET:mars +</pre><p> + </p></li><li><p> + Start Xprt + </p></li><li xmlns:ns88=""><p> + Verify that Xprt is correctly configured: +</p><pre class="screen"> +% <b class="userinput"><tt>export DISPLAY=neptun:12</tt></b> +% <b class="userinput"><tt>xhost</tt></b> +<tt class="computeroutput">access control enabled, only authorized clients can connect +INET:localhost +LOCAL: +INET:merkur +INET:mars</tt> +</pre><p> + </p></li></ol></div></blockquote></div><p> + </p></li></ol></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2878802"></a><a name="id2878804"></a><b>Q:</b></td><td align="left" valign="top"><p> + Xprt refuses to start with the message "failed to set default font path + '...' Fatal server error: could not open default font 'fixed'". + What does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns91="" align="left" valign="top"><p> + This means one or more components in the font path (set via the option + "-fp") are either... + </p><div class="itemizedlist"><ul type="disc"><li><p> + ... not valid + </p></li><li><p> + ... contain fonts not supported by this Xserver (e.g. support has not + be compiled "in" (usually happens for TrueType (which are only support for Solaris version + of Xprt and xprint.mozdev.org releases ≥ 008), OpenType (which are only supported by + xprint.mozdev.org releases 009 or higher) or F3 fonts (Sunsoft/F3 fonts are Solaris-specific + and <span class="emphasis"><em>not</em></span> supported by other vendors (AFAIK)) + when support for these fonts was not enabled at build time)) + </p></li><li><p> + ... no font or font alias in the font path matches the name "fixed" + </p></li><li><p> + ... an entry in <tt class="filename">fonts.dir</tt> or <tt class="filename">fonts.alias</tt> + with the name "fixed" which references a non-existing or non-readable file + </p></li></ul></div><p> + + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2878900"></a><a name="id2878903"></a><b>Q:</b></td><td align="left" valign="top"><p> + Just copying my fonts into a directory and adding the path to my Xprt + command line didn't work - I always get "Fatal server error: could not + open default font 'fixed'". 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> + Every Xserver needs an index file called <tt class="filename">fonts.dir</tt> to tell it which + fonts are available in this directory and which properties these fonts + have. + </p><p> + If you are lucky there may be already a <tt class="filename">fonts.scale</tt> file which can be + used by "mkfontdir" to create the <tt class="filename">fonts.dir</tt> file. + If there is no <tt class="filename">fonts.scale</tt> then you have to create your own + <tt class="filename">fonts.dir</tt>/<tt class="filename">fonts.scale</tt> either by hand or + via tools like "mkfontscale" (works for all types of scaleable fonts), + "type1inst" (for PS Type1 fonts; see + <a href="http://packages.debian.org/stable/utils/type1inst.html" target="_top">http://packages.debian.org/stable/utils/type1inst.html</a>) + or "ttmkfdir" (for TrueType fonts; see + <a href="http://packages.debian.org/stable/x11/ttmkfdir.html" target="_top">http://packages.debian.org/stable/x11/ttmkfdir.html</a>). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879012"></a><a name="id2879015"></a><b>Q:</b></td><td align="left" valign="top"><p> + Xprt refuses to start with the message "Fatal server error: Cannot + establish any listening sockets - Make sure an X server isn't already + running". What does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + There is already a Xserver running at the display ID you have specified + to start Xprt (for example your framebuffer Xserver runs at ":0" then + Xprt can't run at the same display display). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879040"></a><a name="id2879043"></a><b>Q:</b></td><td align="left" valign="top"><p> + Xprt refuses to start with the message "Fatal server error: Failed to + establish all listening sockets". What does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + This means that the Xserver could not open one of it's sockets. Check + the permission of /tmp/.X11-pipe and /tmp/.X11-unix (on Solaris a + 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 <span class="emphasis"><em>always</em></span> with + <hostname>:<displaynum> (see <span class="citerefentry"><span class="refentrytitle">Xserver</span>(1x)</span> + manual page for the side-effects of this option). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879085"></a><a name="id2879088"></a><b>Q:</b></td><td align="left" valign="top"><p> + Xprt refuses to start with the message "Fatal server error: could not + open default font 'fixed'" or "Fatal server error: could not open default + cursor font 'cursor'". + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + All Xservers at least two fonts as the minimum: One fixed-width font + ("fixed") and one font for the cursor ("cursor"). Be sure that the font + path contains these fonts. + + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879112"></a><a name="id2879123"></a><b>Q:</b></td><td align="left" valign="top"><p> + Xprt refuses to start with the message "Fatal server error: no screens + found". What does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns97="" align="left" valign="top"><p><b>Cause: </b> + This means that Xprt could not find any printers. Either there are no + printers installed, "lpstat"/"lpc" could not find any printers or the + configuration does not contain any manual printer configurations + (see Q/A item "Which program is used by default by Xprt to enumerate the + printers on my system" for further details...). + </p><p><b>Solution: </b> + Two solutions: + </p><div class="orderedlist"><ol type="1"><li xmlns:ns92=""><p><b> + Using "PSspooldir" model: + . </b> + Xprt releases from <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a> provide the "PSspooldir" + model config for such cases. Just edit the "<tt class="filename">Xprinters</tt>" file and add + this line: +</p><pre class="screen"> +Printer xp_ps_spooldir_tmp_Xprintjobs +</pre><p> + this will add the pre-configured (see + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/printer</tt>) "xp_ps_spooldir_tmp_Xprintjobs" + printer which will send jobs to the directory "/tmp/Xprintjobs/" + instead to a printer queue. + (This feature was added in the xprint.mozdev.org release 007, see + <a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=2475" target="_top">xprint.mozdev.org bug 2475 ("RFE: Need + model-config which spools print jobs in a predefined directory")</a>.) + </p></li><li xmlns:ns96=""><p><b> + Manual setup (task list): + . </b> + </p><div class="blockquote"><blockquote class="blockquote"><div class="procedure"><ol type="1"><li xmlns:ns93=""><p> + Provide a simple "Xprinters" spec file which contains a dummy + queue. + Example: +</p><pre class="screen"> +# Create "Xprinters_onlydummy" file which turns autolookup of printers +# OFF (using "Augment_Printer_List %none%") and provides one dummy +# queue called "ps_myscript" instead (using "Printer ps_myscript") +% <b class="userinput"><tt>echo "Augment_Printer_List %none%" >Xprinters_onlydummy</tt></b> +% <b class="userinput"><tt>echo "Printer ps_myscript" >>Xprinters_onlydummy</tt></b> +</pre><p> + </p></li><li xmlns:ns94=""><p> + Edit <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/printer</tt> and add these + two lines: +</p><pre class="screen"> +ps_myscript.xp-model-identifier: PSdefault +ps_myscript.xp-spooler-command: /home/sanja/xprint_test/my_xprt_cat_script.sh +</pre><p> + This means that the printer "ps_myscript" now uses the "PSdefault" + printer model and it will feed the jobs to the script + "/home/sanja/xprint_test/my_xprt_cat_script.sh" (via stdin). + Note that the absolute path is required for "*xp-spooler-command". + </p></li><li xmlns:ns95=""><p> + Start Xprt on display 18, passing the "Xprinters_onlydummy" + using the "-XpFile" option: +</p><pre class="screen"> +% <b class="userinput"><tt>Xprt -XpFile ./Xprinters_onlydummy -pn -ac -audit 4 :18</tt></b> +</pre><p> + </p></li></ol></div></blockquote></div><p> + </p></li></ol></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="printout_only_covers_1_4_of_the_paper"></a><a name="id2879414"></a><b>Q:</b></td><td align="left" valign="top"><p> + "Printing itself works but the printout covers only 1/4 of the paper - 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> + This is usually an indicator for a wrong DPI setting. The default + "PSdefault" model config uses 300 DPI but some printers only support + 600 DPI. + </p><p><b>Workaround: </b> + Edit <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt> and replace the line + "*default-printer-resolution: 300" with + "*default-printer-resolution: 600" + (Note that locale-specific settings in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/<tt class="envar">${LANG}</tt>/print/attributes/document</tt> always override values + set in <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/attributes/document</tt>.) + </p><p><b>Solution: </b> + Create a model-config for your printer which only contains attributes + supported by your printer ("printer-resolutions-supported" is the + attribute in the "model-config" which holds the space-seperated list + of DPI values which are supported by the printer). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879502"></a><a name="id2879505"></a><b>Q:</b></td><td align="left" valign="top"><p> + "Printing works but I get large borders/margins..." / "[Top] margin is too small" / + "Margins are wrong" / etc. + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns98="" align="left" valign="top"><p> + Two possible causes: + </p><div class="itemizedlist"><ul type="disc"><li><p> + Usually same issue as "Printing itself works but the printout covers + only 1/4 of the page"-issue: Wrong DPI. + Solution: Check the DPI value and adjust it as described in the FAQ item + above. Common DPI values for the PostScript DDX are 240, 300, 360, 400 + and 600 DPI. + </p></li><li><p> + You are trying to print "US-letter" on a "DIN-A4" paper or "DIN-A4" on + "US-letter". + </p><p> + Solution: Check your paper settings + </p><p> + Note that the default papersize for Xprt depends on the locale + (e.g. on the env var <tt class="envar">${LANG}</tt>) Xprt is running in - "en_US"&co. get + US-letter, all others use DIN-A4 (incl. german/austrian etc. locales)). + Exception from this rule: If the selected printer does not support the + default paper size it will set no default paper size for this printer + (then the application side has to make an explicit choice). + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879587"></a><a name="id2879590"></a><b>Q:</b></td><td align="left" valign="top"><p> + Xprt prints a warning like "Xp Extension: could not find config dir + /usr/X11R6/lib/X11/C/print" - what does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns99="" align="left" valign="top"><p> + This is actually the worst case what can happen. + The message indicates that Xprt was unable to find it's configuration + data. + </p><p><b>Solution: </b> + Two solutions are possible: + </p><div class="itemizedlist"><ul type="disc"><li><p> + Install the configuration data at the requested location + (<tt class="filename">/usr/X11R6/lib/X11/C/print/</tt> in this example) + </p></li><li><p> + Set the <tt class="envar">${XPCONFIGDIR}</tt> env var to the location of the Xprt + configuration directory. + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879661"></a><a name="id2879664"></a><b>Q:</b></td><td align="left" valign="top"><p> + Xprt crashes with "Fatal server error: Beziers this big not yet supported" + What does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + This is a known issue in the X11R6.5.1 code. In rare cases some PostScript + Type1 fonts can trigger this. + See "My PS Type1 font does not work with my Xserver" ... + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879688"></a><a name="id2879691"></a><b>Q:</b></td><td align="left" valign="top"><p> + "My PS Type1 font does not work with my Xserver - how can I fix this ?" + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns100="" align="left" valign="top"><p> + Some PS Type1 do not work out-of-the-box with all PS Type1 font engines - + some will work with the Adobe font engine (used in Solaris Xsun) but not + with the X.org font engine (or the other way round) or the fonts are + simply broken. + + The following procedure will try to fix this problem: + Get the "type1fix" perl script the TeXTrace package + (<a href="http://www.inf.bme.hu/~pts/textrace-latest.tar.gz" target="_top">http://www.inf.bme.hu/~pts/textrace-latest.tar.gz</a>) + and run it over the fonts. + + Example 1 (filter fonts): +</p><pre class="screen"> +# Broken PFA fonts are in broken_fonts/ +% <b class="userinput"><tt>mkdir fixed_fonts ; cd fixed_fonts</tt></b> +% <b class="userinput"><tt>for i in ../broken_fonts/*.pfa ; do + echo " ------- $i" ; + type1fix.pl --ofmt=pfa --infile=$i --outfile=$(basename ${i}) ; + done</tt></b> +</pre><p> + + Example 2 (filter fonts and convert them to PFB on-the-fly; do not forget + to update <tt class="filename">fonts.scale</tt> and run "mkfontdir" (to update <tt class="filename">fonts.dir</tt>) ; + systems which use the Adobe font engine (like Solaris/Xsun) may require + to run "makepsres", too): +</p><pre class="screen"> +# Broken PFA fonts are in broken_fonts/ +% <b class="userinput"><tt>mkdir fixed_fonts ; cd fixed_fonts</tt></b> +% <b class="userinput"><tt>for i in ../broken_fonts/*.pfa ; do + echo " ------- $i" ; + type1fix.pl --ofmt=pfb --infile=$i --outfile=$(basename ${i%.pfa}.pfb) ; + done</tt></b> +</pre><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879800"></a><a name="id2879803"></a><b>Q:</b></td><td align="left" valign="top"><p> + I can't get it working. I have set <tt class="envar">${DISPLAY}</tt> correctly to point to the + Xprt display and... ... What is going wrong ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Do not set <tt class="envar">${DISPLAY}</tt> to the Xprt server. You still need your normal + Xserver for your video card - Xprt is only for your printer(s). + Applications look up Xprt servers via the <tt class="envar">${XPSERVERLIST}</tt> env var, <span class="emphasis"><em>NOT</em></span> + via the <tt class="envar">${DISPLAY}</tt> env var. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879847"></a><a name="id2879850"></a><b>Q:</b></td><td align="left" valign="top"><p> + When I try to print via Xprint I get the message "Fatal server error: + unable to exec '/usr/bin/lp'". What is going wrong here ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + This usually means that the spooler application "<tt class="filename">/usr/bin/lp</tt>" + could not be launched. This is usually the result when + <tt class="filename">/usr/bin/lp</tt> does not exist or + cannot be executed (for example, shell scripts without the +x (executable) flag etc.). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2879888"></a><a name="id2879892"></a><b>Q:</b></td><td align="left" valign="top"><p> + The Solaris Xprt prints some error messages about PostScript fonts like + "FOOBAR not found, using Courier. CMEX0123 not found, using Courier." + etc. and uses "Courier" instead of these fonts... + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns105="" align="left" valign="top"><p><b>Cause: </b> + The Solaris (Adobe-based) PostScript font engine requires a "PostScript + resource database" file named "<tt class="filename">PSres.upr</tt>" to use the PostScript fonts + correctly. + </p><p><b>Solution: </b> + Create the missing <tt class="filename">PSres.upr</tt> database. + </p><div class="blockquote"><blockquote class="blockquote"><div class="procedure"><p class="title"><b>Procedure 5. Steps to create the missing "<tt class="filename">PSres.upr</tt>" file (task list):</b></p><ol type="1"><li xmlns:ns101=""><p> + Go to the location where the matching fonts are installed (we're using + <tt class="filename">/home/sanja/mathml_fonts/tex_cmps/Type1/</tt> in this example): +</p><pre class="screen"> +% <b class="userinput"><tt>cd /home/sanja/mathml_fonts/tex_cmps/Type1//</tt></b> +</pre><p> + </p></li><li xmlns:ns102=""><p> + Create "<tt class="filename">PSres.upr</tt>" using the "makepsres" command. +</p><pre class="screen"> +% <b class="userinput"><tt>makepsres</tt></b> +</pre><p> + </p></li><li xmlns:ns103=""><p> + Validation: + Make sure the file has been created: +</p><pre class="screen"> +% <b class="userinput"><tt>ls -l PSres.upr</tt></b> +</pre><p> + </p></li><li xmlns:ns104=""><p> + Restart Xprt server(s): +</p><pre class="screen"> +% <b class="userinput"><tt>/etc/init.d/xprint restart</tt></b> +</pre><p> + </p></li><li><p> + Restart application which uses these fonts + </p></li></ol></div></blockquote></div><p> + </p><p><b>References: </b> + </p><div class="itemizedlist"><ul type="disc"><li><p><span class="citerefentry"><span class="refentrytitle">makepsres</span>(1)</span> manual page</p></li><li><p><a href="http://bugzilla.mozilla.org/show_bug.cgi?id=120560" target="_top">bugzilla.mozilla.org 120560 ("Solaris Xsun does not like CMEX10/CMSY10 Type1 fonts")</a></p></li><li><p><a href="http://bugzilla.mozilla.org/show_bug.cgi?id=142718" target="_top">bugzilla.mozilla.org 142718 ("Document how to get the MathML fonts to work on Solaris")</a></p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2880176"></a><a name="id2880179"></a><b>Q:</b></td><td align="left" valign="top"><p> + "Xprt refused to start, complaining about a missing dir + (<tt class="filename">/etc/X11/xserver/C/print/</tt> directory)... I created it by hand (empty) and + started Xprt but it still does not work properly..." + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Xprt expects some config data in this directory. Just making it an + existing but empty dir will work around the error message but will not + result in a properly working Xprt since it has no (usefull) builtins + which would make it possible to run the binary without the config data. + Your X11 binary distribution should always come with the config data + (for example <tt class="filename">/usr/openwin/server/etc/XpConfig/</tt> on Solaris) or you will not + be able to use Xprint (however it is possible to copy the config data + from another system :) + BTW: Source for the configs can be found under <tt class="filename">xc/programs/Xserver/XpConfig/</tt> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2880231"></a><a name="id2880234"></a><b>Q:</b></td><td align="left" valign="top"><p> + My Linux system already shipps with a '<tt class="filename">/usr/X11R6/bin/Xprt</tt>'-binary. + Do I need the binary distribution from <a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a> ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns106="" align="left" valign="top"><p> + This depends on what is shipped with your Linux distribution. + Please check the "vendor" string of the Xprt server: +</p><pre class="screen"> +% <b class="userinput"><tt>Xprt :10 &</tt></b> +% <b class="userinput"><tt>xdpyinfo -display :10 | grep -i "vendor string"</tt></b> +</pre><p> + If this outputs a line like "vendor string: The XFree86 Project, Inc" + then you have the Xprt binary build from Xfree86 sources - which are + broken - even the newest version [I'll update this as soon as Xfree86 + shipps with a working version]. + Xprt from Solaris, HP-UX and my own builds (which identifies itself as + "vendor string: xprint.mozdev.org" for releases >= 007, older releases + (e.g. <= 006) identify itself as as "vendor string: The X.Org Group") + are known to work proprtly. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2880316"></a><a name="id2880318"></a><b>Q:</b></td><td align="left" valign="top"><p> + I am getting the error message "error opening security policy file + /usr/X11R6/lib/X11/xserver/SecurityPolicy". What does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + The policy file for the SECURITY extension cannot be found. + This is not serious unless you want to make use of features of the + SECURITY extensions (like treating clients as "untrusted", e.g. restrict + their access to certain Xserver resources). + Normally the missing policy file is a problem with your Unix/Linux X11 + distribution; consult your vendor where to get the missing file from. + Alternatively you can get the plain X11R6.6 security policy file from + <a href="ftp://ftp.x.org/pub/R6.6/xc/programs/Xserver/Xext/SecurityPolicy" target="_top">ftp://ftp.x.org/pub/R6.6/xc/programs/Xserver/Xext/SecurityPolicy</a> + (copy it to the matching location - but be sure that you do not overwrite any + existing security policy file). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2880368"></a><a name="id2880372"></a><b>Q:</b></td><td align="left" valign="top"><p> + I have modified the "HPLJ4family" [or "HPDJ1600C" etc.] printer model to + work with my PostScript printer, but when I print I get empty places + where some text should be - what am I doing wrong here ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + The "HPLJ4family" and "HPDJ1600C" models are PCL-only, check + the model-config spec + (<tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/C/print/models/${MODEL_NAME}/model-config</tt>) - if the + "xp-ddx-identifier" attribute says something with "PCL" (like + "XP-PCL-MONO" etc.) in the value string then this model-config is for + the PCL-DDX <span class="emphasis"><em>only</em></span> (e.g. their PMF fonts do not supply the neccesary + information (e.g. the "_ADOBE_POSTSCRIPT_FONTNAME" chunk is missing; + they only provide the "PCL_FONT_NAME" chunk) nor are these fonts + accessible via the PostScript-support in these printers. + A solution is to use the "PSdefault" model instead (and/or create your + customized own version of this model) - or look if there is a + model-config beginning with the same name and ending with "PS" (e.g. + "HPLJ4family-PS"). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2880421"></a><a name="id2880424"></a><b>Q:</b></td><td xmlns:ns107="" align="left" valign="top"><p> + Xprt outputs warning messages like: +</p><pre class="screen"> +<tt class="computeroutput"> +Xp Extension: Can't load driver XP-PCL-MONO + init function missing +Xp Extension: Can't load driver XP-RASTER + init function missing +</tt> +</pre><p> + What does that mean ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns109="" align="left" valign="top"><p> + Two possible problems: + </p><div class="orderedlist"><ol type="1"><li xmlns:ns108=""><p> + The requested driver is not supported by that version of Xprt. + For example Solaris 2.7 Xprt does not support XP-PCL-MONO nor the + XP-RASTER driver. + Valid values for the "xp-ddx-identifier" attribute in + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/*/print/attributes/printers</tt> and/or + <tt class="filename"><tt class="envar">${XPCONFIGDIR}</tt>/*/print/models/*/model-config</tt> are + </p><div class="itemizedlist"><ul type="disc"><li><p> + Solaris 2.7: XP-POSTSCRIPT and XP-PCL-COLOR + </p></li><li><p> + Solaris >=2.8: XP-POSTSCRIPT, XP-PCL-COLOR, XP-PCL-MONO and XP-RASTER + </p></li><li><p> + HP-UX: XP-POSTSCRIPT, XP-PCL-COLOR, XP-PCL-MONO, XP-PCL-LJ3, + XP-PCL-DJ1200 and XP-RASTER + </p></li><li><p> + xprint.mozdev.org release 007: XP-POSTSCRIPT and XP-RASTER + </p></li><li><p> + xprint.mozdev.org release 008: XP-POSTSCRIPT, XP-PCL-COLOR, + XP-PCL-MONO, XP-PCL-LJ3 and XP-RASTER + </p></li><li><p> + xprint.mozdev.org release >=2.0 (planned): XP-POSTSCRIPT, XP-PCL-COLOR, + XP-PCL-MONO, XP-PCL-LJ3, XP-RASTER, XP-PDF and XP-SVGPRINT. + </p></li></ul></div><p> + </p></li><li><p> + There may be too many drivers loaded into one Xprt instance. + By default a single Xserver instance can only handle three screens - and + since one Xprint DDX maps to one Xserver screen this limit applies to + the number of loaded Xprt drivers, too. + Starting with xprint.mozdev.org release 008 the per-Xserver screen limit + was increased from "3" to "8" to avoid this issue... + Workaround: Start a 2nd instance of Xprt which handles the other + drivers which do not fit into the first instance. + </p></li></ol></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="bug_solaris_xprt_removes_spaces_between_words"></a><a name="id2880607"></a><b>Q:</b></td><td align="left" valign="top"><p> + Printing on Solaris with Mozilla/Eclipse [or any other Xprint client] + removes spaces between words. What is going wrong ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns110="" align="left" valign="top"><p><b>Cause: </b> + This is a bug in the Solaris Xprint server binary (<tt class="filename">/usr/openwin/bin/Xprt</tt>). + Various bug reports have been filed, see + </p><div class="itemizedlist"><ul type="disc"><li><p> + <a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353" target="_top">xprint.mozdev.org bug 3353 + ("Solaris Xprt looses space when rendering with '-monotype-arial-*'-fonts")</a> + </p></li><li><p> + <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=199957" target="_top">bugzilla.mozilla.org bug 199957 ("Solaris 8 Mozilla + removes spaces for text within <font face="Arial">...</font>"</a>) + </p></li></ul></div><p> + </p><p><b>Solution: </b> + Solution: + Please apply the following OS patches from <a href="http://sunsolve.sun.com/" target="_top">http://sunsolve.sun.com/</a>: + </p><div class="table"><a name="id2880736"></a><p class="title"><b>Table 1. + Solaris patches to fix <a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353" target="_top">xprint.mozdev.org bug 3353 + ("Solaris Xprt looses space when rendering with '-monotype-arial-*'-fonts")</a> + </b></p><table summary=" + Solaris patches to fix xprint.mozdev.org bug 3353 + ("Solaris Xprt looses space when rendering with '-monotype-arial-*'-fonts") + " border="1"><colgroup><col><col><col><col><col><col></colgroup><thead><tr><th colspan="2" align="center">Solaris 2.7</th><th colspan="2" align="center">Solaris 2.8</th><th colspan="2" align="center">Solaris 2.9</th></tr><tr><th>SPARC</th><th>x86</th><th>SPARC</th><th>x86</th><th>SPARC</th><th>x86</th></tr></thead><tbody><tr><td><a href="#bug_solaris_xprt_removes_spaces_between_words_s27_no_patches_yet">n/a</a></td><td><a href="#bug_solaris_xprt_removes_spaces_between_words_s27_no_patches_yet">n/a</a></td><td><a href="http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=108652&collection=fpatches" target="_top">108652-73</a></td><td><a href="http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=108653&collection=fpatches" target="_top">108653-62</a></td><td><a href="http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=112785&collection=fpatches" target="_top">112785-21</a></td><td><a href="http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=112786&collection=fpatches" target="_top">112786-11</a></td></tr></tbody></table></div><p> + + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title"><a name="bug_solaris_xprt_removes_spaces_between_words_s27_no_patches_yet"></a>Note</h3><p> + For Solaris 2.7 (both SPARC and x86 platforms) there are currently + <a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353#c24" target="_top">no patches available</a>... + <tt class="literal">;-(</tt> + </p></div><p> + </p><p><b>Known workarounds: </b> + </p><div class="itemizedlist"><ul type="disc"><li><p> + Remove the '-monotype-arial-*' fonts from the font path + </p></li><li><p> + Use an alternate Xprint server like available in the "GISWxprint" package + (this package is identical to the "GISWxprintglue" package except that it + uses a Xprint server build from xprint.mozdev.org sources and not the + <tt class="filename">/usr/openwin/bin/Xprt</tt> binary from Solaris) + </p></li><li xmlns:ns111=""><p> + Mozilla-only: Adding +</p><pre class="programlisting"> + user_pref("print.xprint.font.rejectfontpattern", + "fname=-dt-.*;scalable=.*;outline_scaled=false;xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*|" + + "fname=-monotype-arial.*;scalable=.*;outline_scaled=.*;xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*"); +</pre><p> + to <tt class="filename">prefs.js</tt> works around the problem (see + <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=199957#c6" target="_top">bugzilla.mozilla.org bug 199957 comment #6</a>, + too). + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + Note that this workaround may render various locales completly + inaccessible for printing since many of them only employ MonoType fonts. + </p></div><p> + </p></li></ul></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2881185"></a><a name="id2881188"></a><b>Q:</b></td><td xmlns:ns112="" align="left" valign="top"><p> + Installation of the "GISWxprint" / "GISWxprintglue" packages fails like this: +</p><pre class="screen"># <b class="userinput"><tt>pkgadd -d /space/staging/xprint/GISWxprint.pkg</tt></b> +<tt class="computeroutput">pkgadd: ERROR: no packages were found in </var/tmp/dstreAAA5Jayyz></tt></pre><p> + Any idea what I am doing wrong ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + The target machine misses a patch to cure SunSolve bug 4025718 ("pkginfo: allow greater than nine characters for PKG parameter value"). + Please apply the patches listed in the "Installation Requirements" section in the README + for the <a href="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/packager/solaris/GISWxprint/README" target="_top">GISWxprint</a> / + <a href="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/packager/solaris/GISWxprintglue/README" target="_top">GISWxprintglue</a> package. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="multiple_leading_blank_pages"></a><a name="id2881276"></a><b>Q:</b></td><td align="left" valign="top"><p> + Printing page results in [two/three/.../16] leading blank pages, followed by a correct (but offset) page. + Any idea what is going wrong ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns113="" align="left" valign="top"><p> + This symptom depends on the CUPS GhostScript driver used, however the exact cause is currently unknown + (see comments in <a href="http://sdb.suse.de/en/sdb/html/jsmeix_print-81-cups-formfeed.html" target="_top">SuSE + support database entry SDB-2002/11/jsmeix_print-81-cups-formfeed ("Blank Pages When Printing with + CUPS")</a>). + </p><p><b>Solution: </b> + Disable the CUPS accounting functionality in the cupsomatic filter by changing the line +</p><pre class="programlisting"> + my $ps_accounting = 1; +</pre><p> + to +</p><pre class="programlisting"> + my $ps_accounting = 0; +</pre><p> + in the filter script <tt class="filename">/usr/lib/cups/filter/cupsomatic</tt> as the user root. + If you use <tt class="filename">/etc/foomatic/filter.conf</tt>, disable ps_accounting there. + </p><p><b>References: </b> + </p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://sdb.suse.de/en/sdb/html/jsmeix_print-81-cups-formfeed.html" target="_top">SuSE support database entry SDB-2002/11/jsmeix_print-81-cups-formfeed ("Blank Pages When Printing with CUPS")</a></p></li><li><p><a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=4181" target="_top">xprint.mozdev.org bug 4181 ("Two empty pages printed first")</a></p></li><li><p><a href="http://bugzilla.mozilla.org/show_bug.cgi?id=180602#c7" target="_top">bugzilla.mozilla.org bug 180602 comment #7 ("Printing page results in 16 leading blank pages, followed by a correct, but offset, page")</a></p></li></ul></div><p> + </p></td></tr><tr class="qandadiv"><td align="left" valign="top" colspan="2"><a name="faq_development"></a><h4 class="title"><a name="faq_development"></a>5. Software development</h4></td></tr><tr class="toc" colspan="2"><td align="left" valign="top" colspan="2"><dl><dt>Q: <a href="#id2881454"> + How does the X print server (Xprt) and the Xlib client side differ + from the "normal" video Xserver/video client side ? + </a></dt><dt>Q: <a href="#id2881903"> + How can I get the printable area (e.g. the portion of the page on which + the printer is physically capable of placing ink) of the paper after I + have chosen a paper ? + </a></dt><dt>Q: <a href="#id2881952"> + Do "offscreen" pixmaps work on Xprt ? + </a></dt><dt>Q: <a href="#id2881974"> + How can I get the DPI value for the current Xprt server ? Can I use the + values from "xdpyinfo" ? + </a></dt><dt>Q: <a href="#id2882044"> + Why does Xprt not offer the MIT-SHM protocol extension ? + </a></dt><dt>Q: <a href="#id2882142"> + Does Xprint/Xprt support font rotation ? + </a></dt><dt>Q: <a href="#id2882261"> + When I render something on my window and call XpStartPage all the + rendered stuff is gone, I only get a white, empty paper. + What is going wrong here ? + </a></dt><dt>Q: <a href="#id2882357"> + What is XpStartDoc for ? + </a></dt><dt>Q: <a href="#id2882447"> + How does the XLFD for printer-builtin fonts look like ? / How can I find/identify printer-builtin fonts ? + </a></dt><dt>Q: <a href="#id2882520"> + How can I scale images using the Xprint API ? + </a></dt><dt>Q: <a href="#id2882542"> + 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="#id2882568"> + When I use XpPutDocumentData I get a + BadValue X protocol error. Any idea what am I doing wrong ? + </a></dt><dt>Q: <a href="#id2882608"> + 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="#id2882766"> + How to print with Xt/Athena widgets ? + </a></dt><dt>Q: <a href="#id2882858"> + How to print with Xt/Motif widgets ? + </a></dt><dt>Q: <a href="#id2882883"> + What are the differences between normal display and Xprint display ? + </a></dt><dt>Q: <a href="#id2882905"> + How do I scale images ? + </a></dt><dt>Q: <a href="#id2882926"> + libXp Image scaling vs. max. request size ? + </a></dt><dt>Q: <a href="#id2882948"> + How can I use XprintUtils ? + </a></dt><dt>Q: <a href="#id2882970"> + How do I calculate the DPI values for Xprt DDX screens ? + </a></dt><dt>Q: <a href="#id2882992"> + How do I find scaleable fonts ? + </a></dt><dt>Q: <a href="#id2883014"> + How do I find printer-builtin fonts ? + </a></dt><dt>Q: <a href="#id2883035"> + The XLFD for Printer-builtin fonts look like bitmap fonts - is that bad ? + </a></dt><dt>Q: <a href="#id2883066"> + 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="#id2883134"> + 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="#id2883170"> + Are there any caveats/suggestions when printing via Xt/Motif2 widgets ? + </a></dt><dt>Q: <a href="#id2883723"> + Can I change the paper size/resolution/page orientation/etc. when printing using the + XawPrintShell/XmPrintShell print shells ? + </a></dt></dl></td></tr><tr class="question"><td align="left" valign="top"><a name="id2881454"></a><a name="id2881416"></a><b>Q:</b></td><td align="left" valign="top"><p> + How does the X print server (Xprt) and the Xlib client side differ + from the "normal" video Xserver/video client side ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns114="" align="left" valign="top"><p> + The X Print Service expands on the traditional X-Server and Xlib world + in the following ways: + + </p><div class="orderedlist"><ol type="1"><li><p> + 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 (<a href="#what_does_pdl_mean">PDL</a>)" output (such as PCL, PDF, PostScript, SVGprint, etc.) + or sends the print rendering instructions to a platform-specific + print API (like Win32/GDI). + </p><p> + Once a print ddx driver generates <a href="#what_does_pdl_mean">PDL</a> output, it can be sent to + a spooler + (using <tt class="function">XpuStartJobToSpooler</tt>) + or retrieved by the client (to implement functionality like "print-to-file" + with functions such as <tt class="function">XpuStartJobToFile</tt>). + </p></li><li><p> + Since printers support "paged" output, unlike video, a portion + of the Xp Extension supports APIs to delineate printed output + into a print job. + </p><p> + A "print job" in Xprint consists of one or more "documents" which itself + consists of one or more "pages". + </p><p> + A client starts a job sequence with <tt class="function">XpStartJob</tt> and + ends it with <tt class="function">XpEndJob</tt> or <tt class="function">XpCancelJob</tt> to cancel the + generation of the current print job. + Any document-specific print attributes MUST be changed before <tt class="function">XpStartJob</tt>. + </p><p> + A client starts a document sequence with <tt class="function">XpStartDoc</tt> and + ends it with <tt class="function">XpEndDoc</tt> or <tt class="function">XpCancelDoc</tt> to cancel the + generation of the current document. + Any document-specific print attributes MUST be changed before <tt class="function">XpStartDoc</tt> + or after <tt class="function">XpEndDoc</tt> (to affect the following document). + </p><p> + A client starts a page sequence with <tt class="function">XpStartPage</tt> and + ends it with <tt class="function">XpEndPage</tt> or <tt class="function">XpCancelPage</tt> to cancel the + generation of the current page. + Any page-specific print attributes MUST be changed before <tt class="function">XpStartDoc</tt> + or after <tt class="function">XpEndDoc</tt> (to affect the following document). + </p></li><li><p> + Since printers have extensive capabilities, another portion of + the Xp Extension supports APIs to manipulate "print contexts". + </p><p> + Once a printer is selected using the Xp Extension API, a print + context to represent it can be created. A print context + embodies the printer selected - it contains the printer's + default capabilities, selectable range of capabilities, + printer state, and generated output. Some "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). + </p></li><li><p> + 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. + </p><p> + When a print context is created and set for a given printer, + the X font calls may be able to access additional printer + fonts. To do this (typically), the X-Server must have access + to "printer metric files" (.pmf) that describe at minimum the + metrics of the built in fonts. + </p></li><li><p> + 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. + </p><p> + When a print context is created and set for a given printer, + the X rendering calls use the resolution of the current page + (or if not given, the resolution of the current document or + the current resolution for this print job). + The screen's resolution is INVALID in this case. + XprintUtils has the functions <tt class="function">XpuGetResolution</tt> + (to get the current print resolution (searching page, document and + job level attributes (in that order)), <tt class="function">XpuSetPageResolution</tt> + (to set the current page resolution), <tt class="function">XpuSetDocResolution</tt> + (to set the current document resolution), <tt class="function">XpuGetResolutionList</tt> (to + get the list of all resolutions supported by this printer) and <tt class="function">XpuFindResolution</tt> + (to find a resolution in the list returned by <tt class="function">XpuGetResolutionList</tt>) + to support getting/setting/queries of resolutions. + </p><p> + When a print context is created and set for a given printer, + the X image rendering calls (such as <tt class="function">XPutImage</tt> support + scaling of images. + The Xp Extension API provides the functions <tt class="function">XpSetImageResolution</tt> + and <tt class="function">XpSetImageResolution</tt> to set and get an image resolution. + The scaling factor for an image printed on the paper can simply calculated via + + <tt class="literal">scaling_factor = curr_print_resolution_resolution / image_resolution</tt> + where <tt class="varname">curr_print_resolution_resolution</tt> is the value returned by a function such as + <tt class="function">XpuGetResolution</tt>, <tt class="varname">image_resolution</tt> the resolution passed to + <tt class="function">XpSetImageResolution</tt> and <tt class="varname">scaling_factor</tt> the resulting scaling factor. + Note that <tt class="function">XpSetImageResolution</tt> will failure (=FALSE) when the print DDX + (for example the RASTER DDX) does not support scaling. + In that case the application has to scale the image manually. + </p></li></ol></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2881903"></a><a name="id2881906"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I get the printable area (e.g. the portion of the page on which + the printer is physically capable of placing ink) of the paper after I + have chosen a paper ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + The <tt class="function">XpGetPageDimensions</tt> function returns the printable area and other information + about the current page geometry. + Note that the page geometry changes when the page attributes such as <tt class="literal">content-orientation</tt> + or <tt class="literal">default-medium</tt> are changed by the application. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2881952"></a><a name="id2881955"></a><b>Q:</b></td><td align="left" valign="top"><p> + Do "offscreen" pixmaps work on Xprt ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + Yes, "offscreen" pixmaps are working on Xprt. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2881974"></a><a name="id2881978"></a><b>Q:</b></td><td align="left" valign="top"><p> + How can I get the DPI value for the current Xprt server ? Can I use the + values from "xdpyinfo" ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + The Xprt screen resolution defines only the maximum resolution configured + for the matching DDX, the printers real DPI is obtained via an another + API (XprintUtil has a bunch of functions to get/set the document/page + resolution, see <tt class="function">XpuGetResolutionList</tt>, <tt class="function">XpuFreeResolutionList</tt>, + <tt class="function">XpuGetResolution</tt>, <tt class="function">XpuSetPageResolution</tt>, + <tt class="function">XpuSetDocResolution</tt> and <tt class="function">XpuFindResolution</tt>). + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882044"></a><a name="id2882047"></a><b>Q:</b></td><td align="left" valign="top"><p> + Why does Xprt not offer the MIT-SHM protocol extension ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + The MIT-SHM protocol extension is partially (<tt class="function">XShmPutImage</tt> would work, + but others like <tt class="function">XShmGetImage</tt> and esp. <tt class="function">XShmCreatePixmap</tt> + cannot be implemented properly) incompatible to the way how some of the Xprint DDX are implemented. + For example the PostScript, PDF, PCL and SVGprint DDX do not rasterize any images on their side - instead they convert the + stream of X11 rendering instructions into the matching <a href="#what_does_pdl_mean">PDL</a> instruction stream. + Only the printer side will (finally) do the rasterisation of the output image. This is the basically the same reason why + <a href="#why_does_xgetimage_not_work"><tt class="function">XGetImage</tt> does not work for those DDXs</a> - and + functions such as <tt class="function">XShmCreatePixmap</tt> would be useless since drawing operations on the shared + pixmap would not be applied to the application (e.g. Xprint client) as well. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882142"></a><a name="id2882145"></a><b>Q:</b></td><td align="left" valign="top"><p> + Does Xprint/Xprt support font rotation ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns117="" align="left" valign="top"><p> + Yes - Xprint/Xprt supports font rotation at any angle via the matrix XLFD + enhancement (this even works for printer-builtin fonts !!). For details + see the paper "New Font Technology for X11R6" by Nathan Meyers (a copy can be found in the + Xprint.org source tree under <tt class="filename">xc/doc/hardcopy/XLFD/x11r6_fonts_94_paper.PS.gz</tt>) + </p><p> + Short: + The transformation-matrix for rotation can be calculated like this: +</p><pre class="programlisting"> ++-- --+ +| cos(angle) sin(angle)| +| | +|-sin(angle) cos(angle)| ++-- --+ +</pre><p> + Examples: + </p><div class="orderedlist"><ol type="1"><li xmlns:ns115=""><p> + the following code fragment obtains a 180 degree rotated font (matrix [-1 0 0 -1]): +</p><pre class="programlisting"> + ... = XLoadQueryFont(..., "-adobe-courier-bold-r-normal--*-[~24 0 0 ~24]-0-0-m-*-iso8859-1"); +</pre><p> + </p></li><li xmlns:ns116=""><p> + the following code fragment obtains a 90 degree rotated font (matrix [0 1 -1 0]): +</p><pre class="programlisting"> + ... = XLoadQueryFont(..., "-adobe-courier-bold-r-normal--*-[0 24 ~24 0]-0-0-m-*-iso8859-1"); +</pre><p> + </p></li></ol></div><p> + </p><p> + Future versions of Xprint will support the <a href="http://stsf.sourceforge.net/" target="_top">STSF</a> + font API which supports matrix transformations as well. + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882261"></a><a name="id2882264"></a><b>Q:</b></td><td align="left" valign="top"><p> + When I render something on my window and call <tt class="function">XpStartPage</tt> all the + rendered stuff is gone, I only get a white, empty paper. + What is going wrong here ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td xmlns:ns118="" align="left" valign="top"><p> + Remember the rule that "only those drawings are printed on the paper which + were rendered between <tt class="function">XpStartPage</tt> and <tt class="function">XpEndPage</tt>". + <tt class="function">XpStartPage</tt> clears the window you passed as argument, e.g. it creates + a new, blank sheet of paper where you can do your rendering stuff on. + <tt class="function">XpEndpage</tt> then pushes the "paper sheet" to the stash of papers from the + document in process. + + </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> + If you want to render something once for multiple or all pages: + Render on a offscreen pixmap and copy (with <tt class="function">XCopyArea</tt>) the content to + the "paper" drawable (after calling <tt class="function">XpStartPage</tt>) - <tt class="function">XpStartpage</tt> only + affects the window passed as parameter. + </p></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2882357"></a><a name="id2882360"></a><b>Q:</b></td><td align="left" valign="top"><p> + What is <tt class="function">XpStartDoc</tt> for ? + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>A:</b></td><td align="left" valign="top"><p> + ISO 10175 and some advanced printing systems by IBM and HP had set forth + the standard that a "Job" is made up of one or more "Documents", and + each document is made up of one or more "Pages". Xprint was designed that + in a true ISO 10175 environment/implementation (<span class="citerefentry"><span class="refentrytitle">lp</span>(1)</span> on steroids, and + with an API), Xprt can actually learn about all printers and their + capabilities though API's into the printer subsystem (vs. using config + files), map Job/Doc/Page directly into ISO 10175 equivalents, and use + APIs to view job status and kill jobs (vs. + <span class="citerefentry"><span class="refentrytitle">cancel</span>(1)</span>, + <span class="citerefentry"><span class="refentrytitle">lpcancel</span>(1)</span>, + <span class="citerefentry"><span class="refentrytitle">lpstatus</span>(1)</span>). + 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="id2882447"></a><a name="id2882450"></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. + Instead the <tt class="literal">xp-listfonts-modes-supported</tt> is used to define + whether <tt class="function">XListFonts</tt> and co. return printer-builtin fonts or not. + By default the attribute looks is set to + <tt class="literal">*xp-listfonts-modes-supported: xp-list-internal-printer-fonts xp-list-glyph-fonts</tt> which defines + 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="id2882520"></a><a name="id2882523"></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="id2882542"></a><a name="id2882545"></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="id2882568"></a><a name="id2882571"></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="id2882608"></a><a name="id2882611"></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="id2882638"></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:ns119="" align="left" valign="top"><p> + There are at least three reasons why <tt class="function">XGetImage</tt> does not work for Xprt: + </p><div class="orderedlist"><ol type="1"><li><p> + Most of the Xprt DDX implementations do not render itself on any + bitmaps like the framebuffer(=video) DDX do, they translate the + rendering commands into the matching commands of the printer language + (it is technically possible to implement such support for <tt class="function">XGetImage</tt> + even for those drivers - but there are more reasons:) + </p></li><li><p> + Xprt usually operates at high resolutions which results in very large + dimensions. If a client would request the 24bit TrueColor <span class="emphasis"><em>bitmap</em></span> + data for a <span class="emphasis"><em>whole</em></span> DIN-A4 page at 2400 DPI a data chunk of ~173 + megabytes would be the response. This would be more or less a + DOS(=Denial of Service) for either the client, the network and/or the + server. + </p></li><li><p> + The printer-builtin fonts only provide metrics information - there is no real "outline" + information at that time (these fonts reside only in the printer's ROM and are only + available at the time the printer rasterizes the incoming <a href="#what_does_pdl_mean">PDL</a> + (e.g. PCL/PostScript) data stream) which could be used to rasterize the matching glyphs + (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="id2882766"></a><a name="id2882769"></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:ns120="" align="left" valign="top"><p> + There are two examples in the Xprint.org source tree 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 + demo application which prints a Athena widget using the <tt class="function">XawPrintShell</tt> widget class. + </p></li><li><p> + <tt class="filename">xc/programs/xphelloworld/xpxthelloworld/</tt> contains a simple + demo application which prints a Athena widget without using a special print + widget class (however, if possible a print shell such as <tt class="function">XawPrintShell</tt> or + <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="id2882858"></a><a name="id2882861"></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="id2882883"></a><a name="id2882886"></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="id2882905"></a><a name="id2882908"></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="id2882926"></a><a name="id2882930"></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="id2882948"></a><a name="id2882951"></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="id2882970"></a><a name="id2882973"></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="id2882992"></a><a name="id2882995"></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="id2883014"></a><a name="id2883017"></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="id2883035"></a><a name="id2883038"></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 + the *.pmf (Printer metrics file) format is a PCF file format variant (the DPI values in the XLFD + 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="id2883066"></a><a name="id2883069"></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:ns121="" align="left" valign="top"><p> + Make sure the widgets (such as text input widgets) have the (blinking) cursor turned-off. + Setting the <tt class="literal">XmNcursorPositionVisible,</tt> to <tt class="literal">False</tt> usually + solves the problem (for Motif2 widgets). + Example: + </p><div class="informalexample"><pre class="programlisting"> +... +XtSetArg(args[n], XmNcursorPositionVisible, False); +... +</pre></div><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2883134"></a><a name="id2883137"></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="id2883170"></a><a name="id2883173"></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:ns126="" align="left" valign="top"><p> + There are a couple of Xt resources which may likely differ from the normal values (e.g. those values + used for a video Xserver): + </p><div class="variablelist"><dl><dt><span class="term"><tt class="literal">Core</tt> class level</span></dt><dd xmlns:ns122=""><p> + </p><div class="variablelist"><dl><dt><span class="term"><tt class="literal">XmNbackground</tt> resource</span></dt><dd><p> + The application will probably want to set the <tt class="literal">XmNbackground</tt> resource + to "white" to match the default paper color. + </p></dd><dt><span class="term"><tt class="literal">XmNborderWidth</tt> resource</span></dt><dd><p> + The application will probably want to set the <tt class="literal">XmNborderWidth</tt> resource + to "0" (usually the default value) to avoid that a black border appears around the widget. + </p></dd></dl></div><p> + </p></dd><dt><span class="term"><tt class="function">XmPrimitive</tt> class</span></dt><dd xmlns:ns123=""><p> + </p><div class="variablelist"><dl><dt><span class="term"><tt class="literal">XmNshadowThickness</tt> and <tt class="literal">XmNhightlightThickness</tt> resources</span></dt><dd><p> + The application will probably want to set <tt class="literal">XmNshadowThickness</tt> and + <tt class="literal">XmNhightlightThickness</tt> to "0" (usually the default value) to avoid + 3D border effects on the printout (depends on application and author's preference... + <tt class="literal">:-)</tt>). + </p></dd></dl></div><p> + </p></dd><dt><span class="term"><tt class="function">XmText</tt> and <tt class="literal">XmTextField</tt> classes</span></dt><dd xmlns:ns124=""><p> + </p><div class="variablelist"><dl><dt><span class="term"><tt class="literal">XmNcursorPositionVisible</tt> resource</span></dt><dd><p> + The application will probably want to set <tt class="literal">XmNcursorPositionVisible</tt> + to <tt class="literal">False</tt> to avoid that the cursor is visible on printouts (and to avoid + problems with some nasty implementation details which may cause corrupted PostScript output). + </p></dd><dt><span class="term"><tt class="literal">XmNscrollHorizontal</tt> and <tt class="literal">XmNscrollVertical</tt> resources</span></dt><dd><p> + The application will probably want to set the <tt class="literal">XmNscrollHorizontal</tt> and + <tt class="literal">XmNscrollVertical</tt> resources to <tt class="literal">False</tt> to suppress printing + of scrollbars (on paper "scrolling" is replaced with "pagination" except for rare exceptions + (like 1:1 WYSIWYG-printing)). + </p></dd><dt><span class="term"><tt class="literal">XmNmarginWidth</tt> and <tt class="literal">XmNmarginHeight</tt> resources</span></dt><dd><p> + The application will probably want to recalculate the <tt class="literal">XmNmarginWidth</tt> and + <tt class="literal">XmNmarginHeight</tt> resources based on the (far) higher print resolution + (or reverse: set them to "0" - depending on what style matches + the application needs better...). + </p></dd></dl></div><p> + </p></dd><dt><span class="term"><tt class="function">XmLabel</tt> class</span></dt><dd xmlns:ns125=""><p> + </p><div class="variablelist"><dl><dt><span class="term"><tt class="literal">XmNmarginTop</tt>, <tt class="literal">XmNmarginBottom</tt>, + <tt class="literal">XmNmarginRight</tt>, <tt class="literal">XmNmarginLeft</tt>, + <tt class="literal">XmNmarginWidth</tt>, <tt class="literal">XmNmarginHeight</tt> and + <tt class="literal">XmNalignment</tt> resources</span></dt><dd><p> + The application will probably want to use different value for <tt class="literal">XmLabel</tt> class's + <tt class="literal">XmNmarginTop</tt>, <tt class="literal">XmNmarginBottom</tt>, <tt class="literal">XmNmarginRight</tt>, + <tt class="literal">XmNmarginLeft</tt>, <tt class="literal">XmNmarginWidth</tt>, <tt class="literal">XmNmarginHeight</tt> and + <tt class="literal">XmNalignment</tt> resources. These resources are mainly usefull when the widget holds a + border, highlight or shadow of some kind. If borders are not to be transferred there is no real need to transfer + 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="id2883723"></a><a name="id2883726"></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> + Yes, it is allowed to change the page attributes in the page setup callback + (e.g. <tt class="literal">XawNpageSetupCallback</tt> or <tt class="literal">XmNpageSetupCallback</tt>) + since this callback is always called before <tt class="function">XpStartPage</tt> + (for the 2nd and following pages: between <tt class="function">XpEndPage</tt> and + <tt class="function">XpStartPage</tt>). + Note that changing page attributes will automagically update the print shell widget size + (e.g. attributes <tt class="literal">XawNminX</tt>, <tt class="literal">XawNminY</tt>, <tt class="literal">XawNmaxX</tt> and <tt class="literal">XawNmaxX</tt> (<tt class="function">XawPrintShell</tt>) + or + <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></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="#id2883905"> + Xprt build from Xfree86 sources is completely broken and unuseable. + </a></dt><dt>Problem <a href="#id2883961"> + 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="#id2883997"> + 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="#id2884049"> + 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="#id2883905"> + Xprt build from Xfree86 sources is completely broken and unuseable. + </a></dt><dt>Problem <a href="#id2883961"> + 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="#id2883997"> + 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="#id2884049"> + 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="id2883905"></a><a name="id2883908"></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="id2883961"></a><a name="id2883964"></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 + download PS Type1 fonts. + </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="id2883997"></a><a name="id2884000"></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". + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Solution</b></td><td align="left" valign="top"><p> + Either convert PFB (PS Type 1 binary font) to PFA format and adjust + the <tt class="filename">fonts.dir</tt> and <tt class="filename">fonts.scale</tt> file or get a patch for the sources. + 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="id2884049"></a><a name="id2884052"></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 + to n^2 copies). + </p></td></tr><tr class="answer"><td align="left" valign="top"><b>Solution</b></td><td align="left" valign="top"><p> + Xprt build from xprint.mozdev.org sources has been fixed in release + 007, see <a href="http://xprint.mozdev.org/bugs/show_bug.cgi?id=1378" target="_top">xprint.mozdev.org bug 1378 + ("PS DDX creates n^2 copies of a job instead of n copies")</a> and + <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=140030" target="_top">bugzilla.mozilla.org 140030 + ("Setting number of copies causes too many copies to print")</a> for details. + Solaris 2.7 Xprt still suffers from this issue... <tt class="literal">;-(</tt> + </p></td></tr></tbody></table></div></div><div xmlns:ns127="" class="simplesect" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="unanswered_questions"></a>Unanswered questions</h2></div></div><div></div></div><p> + (My small ToDo list what I will write soon; 379 items missing... <tt class="literal">=:-)</tt> + Email me if you want one of these answered "now" and/or to contribute + an answer... :) + </p><table class="simplelist" border="0" summary="Simple list"><tr><td>How do I create a model-config for my printer ?</td></tr><tr><td>How can I customize a model-config for my site/machine ?</td></tr><tr><td>Which attributes/values can be set in a model-config ?</td></tr><tr><td>Why can't I set default values (for my {paper size, resolution, ...}) in the model-config ?</td></tr><tr><td>Should I add the fonts in the model-config dir to the Xserver's font path ?</td></tr><tr><td>What are the fonts in the model-config dir for ?</td></tr><tr><td>Can I use a font server for all fonts instead of passing then directly to the Xprint server ?</td></tr><tr><td>Does the Xprint PostScript driver do full rasterisation of the print job ?</td></tr><tr><td>Is it possible to prepare a printer config entry so that the PS + output is piped to "ps2pdf" and will produce directly a PDF file? + It would be nice to have mozilla directly producing PDF files when + printing. + </td></tr><tr><td>Problem: I have changed the Xprt config - but "xplsprinters -l"</td></tr><tr><td>(or any other Xprint application) does not show the change.</td></tr><tr><td>Any idea what I am doing wrong ?</td></tr><tr><td>How can I add a font path to Xprt ?</td></tr><tr><td>Why does "xset +fp path_to_font" not work in some cases ?</td></tr><tr><td>How can I get a "core"-dump when Xprt crashes ?</td></tr><tr><td>How can I debug Xprt (hint: use "-audit 4") ?</td></tr><tr><td>How can I debug Xprt with Sun Workshop (hint: "check -access") ?</td></tr><tr><td>How can I check whether Xprint is "active" ? / How can I verify that a Xprint is working ?</td></tr></table><p> + </p></div><div xmlns:ns128="" class="simplesect" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="acknowledgements"></a>Acknowledgements</h2></div></div><div></div></div><p> + We'd like like to express their gratitude to the whole community for + providing insightful answers to innumerable questions. In particular, + the following people (listed alphabetically) have contributed to this + FAQ (apologies, in advance, if anyone has been forgotten): + </p><p> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><span class="othercredit"><span class="firstname">Alan</span> <span class="surname">Coopersmith</span></span> <tt class="email"><<a href="mailto:alan.coopersmith@sun.com">alan.coopersmith@sun.com</a>></tt></td></tr><tr><td><span class="othercredit"><span class="firstname">Giuseppe</span> <span class="surname">Ghibò</span></span> <tt class="email"><<a href="mailto:ghibo@mandrakesoft.com">ghibo@mandrakesoft.com</a>></tt></td></tr><tr><td><span class="othercredit"><span class="firstname">Thomas</span> <span class="surname">Gilg</span></span> <tt class="email"><<a href="mailto:thomas_gilg@hp.com">thomas_gilg@hp.com</a>></tt></td></tr><tr><td><span class="othercredit"><span class="firstname">Jay</span> <span class="surname">Hobson</span></span> <tt class="email"><<a href="mailto:jay.hobson@sun.com">jay.hobson@sun.com</a>></tt></td></tr><tr><td><span class="othercredit"><span class="firstname">Masaki</span> <span class="surname">Katakai</span></span> <tt class="email"><<a href="mailto:katakai@japan.sun.com">katakai@japan.sun.com</a>></tt></td></tr><tr><td><span class="othercredit"><span class="firstname">Simon</span> <span class="surname">Montagu</span></span> <tt class="email"><<a href="mailto:smontagu@smontagu.org">smontagu@smontagu.org</a>></tt></td></tr><tr><td><span class="othercredit"><span class="firstname">Drew</span> <span class="surname">Parsons</span></span> <tt class="email"><<a href="mailto:dparsons@debian.org">dparsons@debian.org</a>></tt></td></tr><tr><td>(and many many others)</td></tr></table><p> + </p></div></div></body></html> diff --git a/hardcopy/XPRINT/Xprint_FAQ.txt b/hardcopy/XPRINT/Xprint_FAQ.txt new file mode 100644 index 0000000..1fc06eb --- /dev/null +++ b/hardcopy/XPRINT/Xprint_FAQ.txt @@ -0,0 +1,3113 @@ + +Xprint Frequently Asked Questions + _________________________________________________________________ + + About this FAQ + + Archive-name: Xprint/FAQ + + Version: 0.9 + + Last-Modified: 2004/02/16 04:15:16 + + Maintained-by: Roland Mainz <[1]roland.mainz@nrubsig.org> + + The following is a list of questions that are frequently asked about + Xprint. + + You can help make it an even better-quality FAQ by writing a short + contribution or update and sending it BY EMAIL ONLY to me. A + contribution should consist of a question and an answer, and + increasing number of people sends me contributions of the form "I + don't know the answer to this, but it must be a FAQ, please answer it + for me". Please read the FAQ first (including the item "[2]Getting + Help") and then feel free to ask me if it is not in the FAQ. + + Thanks! + + The latest Xprint FAQ and some other goodies can be obtained through + http from + [3]http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/ + doc/hardcopy/XPRINT/Xprint_FAQ.html or + [4]http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/ + doc/hardcopy/XPRINT/Xprint_FAQ.txt (the DocBook/XML master source file + is + [5]http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/ + doc/hardcopy/XPRINT/Xprint_FAQ.xml ). + +Note + + Note that the FAQ has not been finished yet (nor is it + half-finished...), many items marked with "XXX" as the answer have + still to be written (or have to be copy&pasted from my item + collection... :) + +Frequently Asked Questions with Answers + + 1. [6]General + + Q: [7]What is "Xprint" ? + Q: [8]Where can I get Xprint/Xprt from ? + Q: [9]What is "Xprt" ? + Q: [10]Where can I get help for problems with Xprint ? + Q: [11]"Why do some people like Xprint ?" / "What are the + advantages of Xprint ?" + + Q: [12]Why do some people dislike Xprint ? + Q: [13]Does Xprint support anti-aliased fonts ? + Q: [14]How can I check if Xprint is working and should be used ? + Q: [15]How can I view PS(=PostScript) files ? + Q: [16]How can I view PCL files ? + Q: [17]How does Xprt find fonts ? + Q: [18]How can I print TrueType fonts with Xprint ? + Q: [19]What does "DDX" mean ? + Q: [20]What does "DIX" mean ? + Q: [21]What does "PDL" mean ? + Q: [22]I have twenty printers installed on my system - but Xprt + only shows two screens. Where are all the other printers + ? + + Q: [23]Which platforms support Xprint ? + Q: [24]I have the broken Xfree86 Xprt binary on my system. Do I + need a new version of libXp.so (the client side X11 + extension library for Xprint), too ? + + Q: [25]Which spelling is correct - "Xprint", "XPrint", "Xprinter" + or Xprt" ? + + Q: [26]Which applications support Xprint ? + Q: [27]Is "Xprint" "mozilla"-only (I saw that it's hosted by + mozdev.org) ? + + Q: [28]Under which license is the source code from + xprint.mozdev.org distributed under ? + + 2. [29]Usage + + Q: [30]How do I configure Xprint on the client side ? + Q: [31]How do I start Xprt ? + Q: [32]How can I get a list of printers managed by Xprint ? + Q: [33]How can I start Xprt at boot time ? + Q: [34]How can I start Xprt per-user ? + Q: [35]How can I start Xprt only for one application ? + Q: [36]How can I filter the font path which should be passed to + Xprt for certain fonts ? + + Q: [37]How can I manage access control to the Xprt server ? + Q: [38]How can I log access to the Xprt server ? + Q: [39]Does it require "root" permissions to use Xprt/Xprint ? + Q: [40]How can I see the attributes of a printer managed by + Xprint ? + + Q: [41]How can I list the font path used by a Xprt server ? + Q: [42]"xset q" lists all model-specific font dirs (like + PRINTER:/myxpcfg/C/print/models/SPSPARC2/fonts/") - is + that a bug ? + + Q: [43]My application lists a printer called + "xp_ps_spooldir_tmp_Xprintjobs" / + "xp_pdf_spooldir_tmp_Xprintjobs" / + "spooldir_tmp_Xprintjobs" / in the print dialog but I do + not have such a print queue installed anywhere. What is + that for a thing ?! + + Q: [44]How can I forward Xprint services when logging-in via ssh + to another machine ? + + 3. [45]Configuration + + Q: [46]How do I change the defaults for + double-sided/single-sided/etc. printing ? + + Q: [47]I am in America and I don't have any ISO A4 paper. How do + I change the default paper size to 8.5 inch x 11 inch + (US-Letter) ? + + Q: [48]How do I change the default printer resolution ? + Q: [49]How do I change the default settings for + "portrait"/"landscape"/"seascape" (=page orientation) ? + + Q: [50]How can I prevent Xprt from using any bitmap(=gfx) fonts ? + + Q: [51]I want only my manually added printers managed by Xprint. + How can I prevent Xprt from looking-up the printer names + automatically ? + + Q: [52]How can I specify an own program/script to enumerate the + printers on my system ? + + Q: [53]Which program is used by default by Xprt to enumerate the + printers on my system ? + + Q: [54]Where can I get more PostScript Type1 fonts from ? + Q: [55]What are PMF fonts (e.g. the *.pmf fonts in + ${XPCONFIGDIR}/C/print/models/%model_name%/fonts/ (or + ${XPCONFIGDIR}/${LANG}/print/models/%model_name%/fonts/)) + ? + + Q: [56]Can I use the fontserver ("xfs") with Xprt ? + Q: [57]What is a "model-config" ? + Q: [58]Where can I store the default values for printers ? + Q: [59]How can I create my own model-config ? + Q: [60]How can I create my own PMF "fonts" ? + Q: [61]Where can I get more model-configs from ? + Q: [62]If I install Xprt &co. as "root" in the default location + and don't need to set ${XPCONFIGDIR} - where are my + configuration files located then ? + + Q: [63]Are config files and/or the PMF fonts architecture + dependent ? + + Q: [64]Can I localise my Xprint/Xprt configuration (l10n) ? + Q: [65]Can I execute my own scripts to process the PostScript + files generated by Xprt ? + + Q: [66]How can I disable "xp_ps_spooldir_tmp_Xprintjobs" / + "xp_pdf_spooldir_tmp_Xprintjobs" printer targets ? + + 4. [67]Troubleshooting + + Q: [68]Xprt refuses to start with the message "sh: lpc: command + not found" on my Linux machine. What does that mean ? + + Q: [69]When the application (=client side) tries to connect to + the Xprt (Xserver) side it fails with a Xlib: connection + to "meridian:52.0" refused by server Xlib: Client is not + authorized to connect to Server What does that mean ? + + Q: [70]Xprt refuses to start with the message "failed to set + default font path '...' Fatal server error: could not + open default font 'fixed'". What does that mean ? + + Q: [71]Just copying my fonts into a directory and adding the path + to my Xprt command line didn't work - I always get "Fatal + server error: could not open default font 'fixed'". What + am I doing wrong ? + + Q: [72]Xprt refuses to start with the message "Fatal server + error: Cannot establish any listening sockets - Make sure + an X server isn't already running". What does that mean ? + + Q: [73]Xprt refuses to start with the message "Fatal server + error: Failed to establish all listening sockets". What + does that mean ? + + Q: [74]Xprt refuses to start with the message "Fatal server + error: could not open default font 'fixed'" or "Fatal + server error: could not open default cursor font + 'cursor'". + + Q: [75]Xprt refuses to start with the message "Fatal server + error: no screens found". What does that mean ? + + Q: [76]"Printing itself works but the printout covers only 1/4 of + the paper - what am I doing wrong ?" + + Q: [77]"Printing works but I get large borders/margins..." / + "[Top] margin is too small" / "Margins are wrong" / etc. + + Q: [78]Xprt prints a warning like "Xp Extension: could not find + config dir /usr/X11R6/lib/X11/C/print" - what does that + mean ? + + Q: [79]Xprt crashes with "Fatal server error: Beziers this big + not yet supported" What does that mean ? + + Q: [80]"My PS Type1 font does not work with my Xserver - how can + I fix this ?" + + Q: [81]I can't get it working. I have set ${DISPLAY} correctly to + point to the Xprt display and... ... What is going wrong + ? + + Q: [82]When I try to print via Xprint I get the message "Fatal + server error: unable to exec '/usr/bin/lp'". What is + going wrong here ? + + Q: [83]The Solaris Xprt prints some error messages about + PostScript fonts like "FOOBAR not found, using Courier. + CMEX0123 not found, using Courier." etc. and uses + "Courier" instead of these fonts... + + Q: [84]"Xprt refused to start, complaining about a missing dir + (/etc/X11/xserver/C/print/ directory)... I created it by + hand (empty) and started Xprt but it still does not work + properly..." + + Q: [85]My Linux system already shipps with a + '/usr/X11R6/bin/Xprt'-binary. Do I need the binary + distribution from http://xprint.mozdev.org/ ? + + Q: [86]I am getting the error message "error opening security + policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy". + What does that mean ? + + Q: [87]I have modified the "HPLJ4family" [or "HPDJ1600C" etc.] + printer model to work with my PostScript printer, but + when I print I get empty places where some text should be + - what am I doing wrong here ? + + Q: [88]Xprt outputs warning messages like: Xp Extension: Can't + load driver XP-PCL-MONO init function missing Xp + Extension: Can't load driver XP-RASTER init function + missing What does that mean ? + + Q: [89]Printing on Solaris with Mozilla/Eclipse [or any other + Xprint client] removes spaces between words. What is + going wrong ? + + Q: [90]Installation of the "GISWxprint" / "GISWxprintglue" + packages fails like this: # pkgadd -d + /space/staging/xprint/GISWxprint.pkg pkgadd: ERROR: no + packages were found in </var/tmp/dstreAAA5Jayyz> Any idea + what I am doing wrong ? + + Q: [91]Printing page results in [two/three/.../16] leading blank + pages, followed by a correct (but offset) page. Any idea + what is going wrong ? + + 5. [92]Software development + + Q: [93]How does the X print server (Xprt) and the Xlib client + side differ from the "normal" video Xserver/video client + side ? + + Q: [94]How can I get the printable area (e.g. the portion of the + page on which the printer is physically capable of + placing ink) of the paper after I have chosen a paper ? + + Q: [95]Do "offscreen" pixmaps work on Xprt ? + Q: [96]How can I get the DPI value for the current Xprt server ? + Can I use the values from "xdpyinfo" ? + + Q: [97]Why does Xprt not offer the MIT-SHM protocol extension ? + Q: [98]Does Xprint/Xprt support font rotation ? + Q: [99]When I render something on my window and call XpStartPage + all the rendered stuff is gone, I only get a white, empty + paper. What is going wrong here ? + + Q: [100]What is XpStartDoc for ? + Q: [101]How does the XLFD for printer-builtin fonts look like ? / + How can I find/identify printer-builtin fonts ? + + Q: [102]How can I scale images using the Xprint API ? + Q: [103]Can I pass my own PostScript code (fragment) to the print + spooler instead of letting Xprt's PostScript DDX generate + it ? + + Q: [104]When I use XpPutDocumentData I get a BadValue X protocol + error. Any idea what am I doing wrong ? + + Q: [105]How do I use the XprintUtil library ? + Q: [106]Why does the XGetImage not work for Xprt ? + Q: [107]How to print with Xt/Athena widgets ? + Q: [108]How to print with Xt/Motif widgets ? + Q: [109]What are the differences between normal display and + Xprint display ? + + Q: [110]How do I scale images ? + Q: [111]libXp Image scaling vs. max. request size ? + Q: [112]How can I use XprintUtils ? + Q: [113]How do I calculate the DPI values for Xprt DDX screens ? + Q: [114]How do I find scaleable fonts ? + Q: [115]How do I find printer-builtin fonts ? + Q: [116]The XLFD for Printer-builtin fonts look like bitmap fonts + - is that bad ? + + Q: [117]When printing using the XawPrintShell/XmPrintShell print + shells my PostScript output is always corrupt. What am I + doing wrong ? + + Q: [118]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" ? + + Q: [119]Are there any caveats/suggestions when printing via + Xt/Motif2 widgets ? + + Q: [120]Can I change the paper size/resolution/page + orientation/etc. when printing using the + XawPrintShell/XmPrintShell print shells ? + +1. General + + Q: [121]What is "Xprint" ? + Q: [122]Where can I get Xprint/Xprt from ? + Q: [123]What is "Xprt" ? + Q: [124]Where can I get help for problems with Xprint ? + Q: [125]"Why do some people like Xprint ?" / "What are the advantages + of Xprint ?" + + Q: [126]Why do some people dislike Xprint ? + Q: [127]Does Xprint support anti-aliased fonts ? + Q: [128]How can I check if Xprint is working and should be used ? + Q: [129]How can I view PS(=PostScript) files ? + Q: [130]How can I view PCL files ? + Q: [131]How does Xprt find fonts ? + Q: [132]How can I print TrueType fonts with Xprint ? + Q: [133]What does "DDX" mean ? + Q: [134]What does "DIX" mean ? + Q: [135]What does "PDL" mean ? + Q: [136]I have twenty printers installed on my system - but Xprt only + shows two screens. Where are all the other printers ? + + Q: [137]Which platforms support Xprint ? + Q: [138]I have the broken Xfree86 Xprt binary on my system. Do I need + a new version of libXp.so (the client side X11 extension + library for Xprint), too ? + + Q: [139]Which spelling is correct - "Xprint", "XPrint", "Xprinter" or + Xprt" ? + + Q: [140]Which applications support Xprint ? + Q: [141]Is "Xprint" "mozilla"-only (I saw that it's hosted by + mozdev.org) ? + + Q: [142]Under which license is the source code from xprint.mozdev.org + distributed under ? + + Q: + + What is "Xprint" ? + A: + + In short, "Xprint" is an advanced printing system which enables X11 + applications to use devices like printers, FAX or create documents in + formats like PostScript, PDF or SVGprint. + + In long, "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 or SVGprint. 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... + Q: + + Where can I get Xprint/Xprt from ? + A: + + Xprint is client-server based, therefore two answers: + * The server side is available by default on Solaris (see [143]Note + below) and HP-UX (Xfree86 ships a "Xprt" binary, but that is + broken and the server config files are missing, too). For those + platforms who do not have a (working) Xprt server the you can get + source, binary tarballs and Linux RPMs from + [144]http://xprint.mozdev.org/, Debian Linux has a package based + on the same sources (see + [145]http://packages.qa.debian.org/x/xprint-xprintorg.html). + +Note + For Solaris >= 2.7 [146]http://xprint.mozdev.org/ provides the + "GISWxprintglue" and "GISWxprint" packages (available from + [147]http://xprint.mozdev.org/download.html) which provides a + single-step drop-in way to configure and start Xprint at system + startup and/or per-user for all applications and users (the + package provides only startup scripts and some config data and + uses the Xprt binary provided with Solaris + (/usr/openwin/bin/Xprt)). + * The client-side Xprint support library (libXp.so) is available on + all X11 platforms >=R6.4, including Linux, Solaris, HP-UX, AIX, + FreeBSD, NetBSD, etc. + If you do not have it you can build it from the sources available + at [148]http://xprint.mozdev.org/. + + Q: + + What is "Xprt" ? + A: + + Xprt is the server-side of Xprint. It's just like any other Xserver - + it uses only an other kind of output device (printer instead of + framebuffer) and implements an extra X11 extension ("XpExtension") to + handle the special features/requirements of a "paged device"(=printer + etc.). + Q: + + Where can I get help for problems with Xprint ? + A: + + The current main site for the Xprint development is + [149]http://xprint.mozdev.org/ which hosts various resources including + a [150]mailinglist (please subscribe before posting) for end-users, + admin and developers. + Q: + + "Why do some people like Xprint ?" / "What are the advantages of + Xprint ?" + A: + + * Xprint allows an application to query what features (paper size, + trays, orientation, resolutions, plexes, fonts and much more) a + printer supports. For example it is avoidable that a user + accidently prints DIN-A4 on a DIN-A0 poster printer (the print + dialog would only offer DIN-A0 as paper size, e.g. offers only + choices which are valid for this printer). + * Server-side, localizeable configuration - changes to the server + config apply to all users without the need to change/updating + anything on the user side (the user may still start his/her own + Xprt instance using his/her preferred configuration). + * Small footprint - ideal for for mobile devices (client side does + not need to process any fonts - that's the job of the server + side). + * API not restriced to PostScript (X11R6.5.1 comes with PCL and + Raster implementations - and PDF/G3-FAX/SVG would be possible + without problems). + * Scaleable - Xprint can use as many Xprt servers as the user/admin + wants. + * "Xprint is designed for the enterprise", e.g. Xprint was designed + to match the needs of large company networks. + * Automatic font handling - font download or the existence of + printer-builtin fonts is automagically handled by Xprt - the + application does not need to know/handle any details (but the + application can optionally get information and control the usage + of printer builtin fonts). + * You can print anything what you can render on the + framebuffer(=video card) Xserver. + * Existing code can be reused 1:1 for printing - which means reduced + development costs. + * Easy support for I18N (internationalization) - you simply render + any fonts in any language with Xprint. + * Network-transparent design - Client can use local or remote Xprt + servers like any other Xserver. + * Uses the X11 protocol - easy adoption of existing code to + implement printer support. And all the network goodies like + firewall proxies, compressors etc. can be used for Xprint without + modifications. + * Security: Xprint can use all authentification schemes available in + X11 (like Kerberos5, SecureRPC, MIT-MAGIC-COOKIE or host-based + authentification). + * Enhachements on the server side (Xprt) to not require the change + of client-side code. + * Optimized job output (like the PostScript created by the + PostScript DDX) is usually a lot smaller than the PS code created + by other PostScript engines. + + Q: + + Why do some people dislike Xprint ? + A: + + There are a few common misconceptions about Xprint. Let's take a look + some of these "myths", some background - and the facts: + + Myth: [151]Xprint prints just a XWD dump of the Xserver bitmap + Myth: [152]Xprint cannot handle non-'ISO Latin 1' chars + Myth: [153]Xprint uses a 1024x768 screen resolution to render the + stuff on the paper - therefore it will never be able to do + high-resolution stuff + + Myth: [154]Xprint prints only graphics(=bitmap/gfx) fonts + Myth: [155]Xprint does not support pages sizes larger than DIN-A4 + Myth: [156]Xprint does not support rotated text + + Myth: + + " Xprint prints just a XWD dump of the Xserver bitmap " + Fact: + + Whoever says Xprint simply does an "xwd"-like dump is wrong. + + In short, Xprint currently (X11R6.5.1) supports *four* drivers: + 1. X to native Postscript + 2. X to native PCL5 + 3. X to native PCL3 + 4. X to a raster which is then feed to something like xpr to create + PS or PCL5 wrapped rasters. + + In long, the original X Print Service ("XPS") was attempted during CDE + 1.0, and they only got so far as the "raster" driver. + + As CDE 2.0 came around, Bob Schiefler and others at the X Consortium + agreed that the X Consortium would work on a X to native PS Level 2 + driver and HP would work on a X to native PCL5 driver. + + It was probably the CDE 1.0 effect that left many people with the + impression that Xprint is all about xwd-like window dumps. NO! Xprint + has native PostScript and PCL5 printing and more drivers (like PDF and + SVGprint DDXs etc.) are in the development. + Myth: + + " Xprint cannot handle non-'ISO Latin 1' chars " + Fact: + + Xprint can print any chars incl. those required for MathML, Hebrew, + Arabic, Japanese etc. etc. For example - the Xprint module for + Mozilla5 is the only print module which can proprtly print MathML. + Myth: + + " Xprint uses a 1024x768 screen resolution to render the stuff on the + paper - therefore it will never be able to do high-resolution stuff " + Fact: + + Xprt uses the screen resolution requested by the application or the + printers default resolution. For example a 300 DPI printer which + supports paper sizes up to DIN-A4 will get a screen with 3300x3300 + pixels (screen width and height are usually equal to support per-page + changes in the orientation (potrait/landscape etc.), the window size + would be 2400x3149 for "portrait" orientation) - and larger + resolutions will result in larger screens. + Myth: + + " Xprint prints only graphics(=bitmap/gfx) fonts " + Fact: + + In short, Xprt supports printer-builtin fonts and can download fonts + to the printer if they do not exist on the printer. + + In long, this myth seems to have it's root in a feature of Xprt which + can - if Xprt gets misconfigured - disable the use of printer-builtin + fonts and the ability to download fonts. + + Xprt's PostScript and PCL DDX have the unique feature to create font + glyphs from bitmap fonts if they are not available as printer-builtin + fonts nor as PostScipt Type1 fonts. However this is the fallback - the + last option used by Xprt. Used if everything else fails. But when + someone does not pass any PS Type1 fonts with the font path nor + configures a printer model-config (which contains a description of the + features&fonts supported by the printer) Xprt will never have a chance + to use them. And if everything else fails it has no other option than + using what has been left - the bitmap fonts... + Myth: + + " Xprint does not support pages sizes larger than DIN-A4 " + Fact: + + There is no such limitation. The only limit is the 16bit coordinate + system of the X11 protocol - which is large enougth that Xprint can + support paper sizes larger than DIN-A0 oversize papers. There is no + problem with creating your own monster-size DIN-A0 posters using + Xprint-based applications. + Myth: + + " Xprint does not support rotated text " + Fact: + + Xprint and all it's drivers support the X11 matrix XLFD enhancement + introduced in X11R6 (and future versions of Xprint will support the + [157]STSF font API which supports matrix transformations as well). + Fonts can be rotated at any angle. Take a look at the [158]SOFTWARE + DEVELOPMENT section in this FAQ for examples... + + Q: + + Does Xprint support anti-aliased fonts ? + A: + + Question back: When do we need anti-aliased fonts ? Anti-aliasing is a + "hack" to work around the limitations caused by the low resolution of + monitors - they usually operate between 72 DPI and 150 DPI. + + But Xprint operates on printers where the usual minimum resolution is + 300 DPI (today's normal office printers support resolutions ranging + from 300 DPI up to 2400 DPI depending on the model; most common is 600 + DPI). Anti-aliasing at those resolutions is not required anymore. + Additionally many printers support their own font anti-aliasing at + lower resolutions which is far better and faster than it could be + "done" on the client side. + Q: + + How can I check if Xprint is working and should be used ? + A: + + Check whether the ${XPSERVERLIST} env var is set or not. If + ${XPSERVERLIST} is set then Xprint is available and should be used. + Q: + + How can I view PS(=PostScript) files ? + A: + + * On Unix/Linux (general): + + GhostScript ("gs") and GhostView ("gv" and it's KDE- and + Gnome-specific versions "kghostview" and "ggv") + + * Solaris: + + /usr/dt/bin/sdtimage (DPS-based image viewer for CDE) + + /usr/openwin/bin/pageview (DPS-based image viewer for + OpenWindows) + + Q: + + How can I view PCL files ? + A: + + XXX - [159]xprint.mozdev.org bug 2261 has been filed for that issue. + Q: + + How does Xprt find fonts ? + A: + + Lookup-rule for Xprt's PostScript DDX to find fonts: + 1. Printer-builtin fonts (defined by the fonts/-dir in the + model-config) + 2. PostScript fonts (will be downloaded via generated print job) + 3. GFX-fonts build from X11 scaleable fonts + 4. GFX-fonts build from X11 bitmap fonts + + Q: + + How can I print TrueType fonts with Xprint ? + A: + + 1. Linux Xprt build from [160]http://xprint.mozdev.org/'s source + supports TrueType fonts out-of-the-box (starting with the 008 + development tree; xprint.mozdev.org's releases <= 007 do not + support TrueType fonts) and and does not require any special + actions. + 2. Sun's Xprt on Solaris (/usr/openwin/bin/Xprt) has TrueType font + support out-of-the-box and does not require any special actions. + 3. You can setup a TTF-aware X font server ("xfs", see xfs(1x)) with + the matching TrueType fonts and add the font server location to + Xprt's font path. + 4. Sourceforge has a TrueType to PostScript Type 1 converter project, + see [161]http://ttf2pt1.sourceforge.net/download.html. You may + convert the TTF files into PT1 files that Xprt can download them + to the printer on demand... + + Q: + + What does "DDX" mean ? + A: + + "DDX" is a short term for "Device Dependent X" - the device-specific + layer of a Xserver ([162]"DIX"(="Device Independent X") is the + counterpart). + Q: + + What does "DIX" mean ? + A: + + "DIX" is a short term for "Device Independent X" - the non-device + specific code of a Xserver ([163]"DDX"(="Device Dependent X") is the + counterpart). + Q: + + What does "PDL" mean ? + A: + + "PDL" is a short term for "Page Description Language". Examples for + PDLs are PostScript, PCL, PDF and SVGprint. + Q: + + I have twenty printers installed on my system - but Xprt only shows + two screens. Where are all the other printers ? + A: + + A Xprt screen does not represent a single printer. A Xprt screen + represents a single DDX (currently supported are PostScript, PCL3/5 + color, PCL mono and "raster" output(=1bit deep bitmap). + Q: + + Which platforms support Xprint ? + A: + + All platforms which support X11 >= R6.4 can use Xprint. The client + side (libXp.so) is available on Linux/FreeBSD(=Xfree86), Solaris, + HP-UX and AIX and the Xprt server side is available by default on + Solaris and HP-UX (Xfree86 shipps with a Xprt binary - but that is + broken and unuseable). The client-side extension library (libXp.so) + can be compiled on any platform, the Xprt server needs minor + adjustments for the specific platforms... If your platform does not + have Xprint (client-side and/or server-side) you can get the sources + from [164]http://xprint.mozdev.org/. + Q: + + I have the broken Xfree86 Xprt binary on my system. Do I need a new + version of libXp.so (the client side X11 extension library for + Xprint), too ? + A: + + No, the libXp.so shared library shipped with Xfree86 or build from + Xfree86 sources is not broken, only the server side ("Xprt") is buggy. + There is no need to replace the library. + Q: + + Which spelling is correct - "Xprint", "XPrint", "Xprinter" or Xprt" ? + A: + + "Xprint" is the correct one - "XPrint" is just a typo, "Xprinter" is a + complety different product not related to X11/Xprint and "Xprt" is + only the "X11 print server"(=the server side of Xprint). + Q: + + Which applications support Xprint ? + A: + + There are various applications which support Xprint: + * Motif/LessTif (full framework incl. special widgets like + XmPrintShell) + * [165]Common Desktop Environment (CDE) 2.x + * [166]Mozilla + * Eclipse + * KDE/Qt support is comming is planned for the end of Dec/2003 + * StarOffice 5.x + * etc. + + Q: + + Is "Xprint" "mozilla"-only (I saw that it's hosted by mozdev.org) ? + A: + + No, Xprint is a general-purpose print API based on the X11 API used by + many applications ([167]mozdev.org is just hosting the development + area, but this does not mean the project is limited to mozilla... :)). + Q: + + Under which license is the source code from xprint.mozdev.org + distributed under ? + A: + + That's the plain "MIT" license, the same as used by Xfree86.org and + X.org: +Copyright (c) <year> <copyright holders> + +Permission is hereby granted, free of charge, to any person obtaining a copy of + this software +and associated documentation files (the "Software"), to deal in the Software wi +thout +restriction, including without limitation the rights to use, copy, modify, merg +e, publish, +distribute, sublicense, and/or sell copies of the Software, and to permit perso +ns to whom the +Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or +substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPL +IED, INCLUDING +BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR +PURPOSE AND +NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE F +OR ANY CLAIM, +DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE +, ARISING +FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN + THE SOFTWARE. + +2. Usage + + Q: [168]How do I configure Xprint on the client side ? + Q: [169]How do I start Xprt ? + Q: [170]How can I get a list of printers managed by Xprint ? + Q: [171]How can I start Xprt at boot time ? + Q: [172]How can I start Xprt per-user ? + Q: [173]How can I start Xprt only for one application ? + Q: [174]How can I filter the font path which should be passed to Xprt + for certain fonts ? + + Q: [175]How can I manage access control to the Xprt server ? + Q: [176]How can I log access to the Xprt server ? + Q: [177]Does it require "root" permissions to use Xprt/Xprint ? + Q: [178]How can I see the attributes of a printer managed by Xprint ? + Q: [179]How can I list the font path used by a Xprt server ? + Q: [180]"xset q" lists all model-specific font dirs (like + PRINTER:/myxpcfg/C/print/models/SPSPARC2/fonts/") - is that a + bug ? + + Q: [181]My application lists a printer called + "xp_ps_spooldir_tmp_Xprintjobs" / + "xp_pdf_spooldir_tmp_Xprintjobs" / "spooldir_tmp_Xprintjobs" / + in the print dialog but I do not have such a print queue + installed anywhere. What is that for a thing ?! + + Q: [182]How can I forward Xprint services when logging-in via ssh to + another machine ? + + Q: + + How do I configure Xprint on the client side ? + A: + + There are two env vars which control Xprint on the client side: + 1. The env variable ${XPSERVERLIST} contains a list of display + identifiers (seperated by whitespace) to tell the application + where it can find the Xprt servers. Usually ${XPSERVERLIST} is set + by the profile startup scripts (e.g. /etc/profile or + /etc/profile.d/xprint.sh) using the output of "/etc/init.d/xprint + get_xpserverlist". Example: + % export XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`" + Alternativly ${XPSERVERLIST} can be set manually: + Example: + % export XPSERVERLIST="littlecat:80 bitdog:72" + instructs an application to look at the displays 80 on the machine + "littlecat" and display 72 on the machine bigdog to look for Xprt + servers. + 2. The env variable ${XPRINTER} defines the default printer used by + print applications. The syntax is either <printername> or + <printername>@<display> + Examples: + a. + % export XPRINTER=ps003 + tells an application to look for the first printer named + "ps003" on all Xprt servers. + b. + % export XPRINTER="hplaser19@littlecat:80" + tells an application to look for the printer "hplaser19" on + the Xprt display "littlecat:80". + +Note: + If ${XPRINTER} is not set the applications will examine the values + of the ${PDPRINTER}, ${LPDEST}, and ${PRINTER} env vars (in that + order). + + Q: + + How do I start Xprt ? + A: + + 1. Linux RPM installations on Mandrake/RedHat/SuSE Linux: Binary RPM + packages provided by xprint.mozdev.org (or based on the same + source :) will install /etc/init.d/xprint and related glue (see + [183][4]) automatically; after a reboot a Xprt instance will be + started at system startup and ${XPSERVERLIST} should be populated + for all users. Note that you can start/stop per-user instances + using /etc/init.d/xprint (see [184][4]), too... + 2. Debian Linux: Same as [185][1], however Debian does not support + /etc/profile.d/ - you have to add the following line to + /etc/profile (for sh/ksh/bash) to populate ${XPSERVERLIST}: + export XPSERVERLIST="`/bin/sh /etc/init.d/xprint get_xpserverlist`" + See [186]bugs.debian.org bug 171174 ('"xprint-xprintorg" should + automatically populate $XPSERVERLIST') for further details on this + issue... + 3. + a. Solaris using the "GISWxprintglue" package: + [187]http://xprint.mozdev.org/ provides a Solaris package + called "GISWxprintglue" which contains all the neccesary + configuration files and startup scripts to use Xprint; after + a reboot a Xprt instance will be started at system startup + and ${XPSERVERLIST} should be populated for all users. Note + that you can start/stop per-user instances using + /etc/init.d/xprint (see [188][4]), too... + b. Solaris using the "GISWxprint" package: + [189]http://xprint.mozdev.org/ provides a Solaris package + called "GISWxprint" which is technically identical to the + "GISWxprintglue" (see [190][3a]) but provides a Xprt binary + build from the xprint.mozdve.org sources ("GISWxprintglue" + uses the /usr/openwin/bin/Xprt binary provided by Solaris). + 4. General: Using /etc/init.d/xprint and related glue: There are + startup/shutdown scripts in xc/programs/Xserver/Xprint/etc/ to + start/stop/restart Xprt per-machine and/or per-user and to + populate the ${XPSERVERLIST} env var: + + "xc/programs/Xserver/Xprint/etc/init.d/xprint" is a script + for SystemV and Linux to start/stop/restart Xprt. The script + includes installation and usage details and can be used by + both "root" (to start Xprt for all users) or by a single + (non-priviledged, plain) user (to start Xprt instances only + for his/her own use) + + "xc/programs/Xserver/Xprint/etc/profile.d/xprint.csh" and + "xc/programs/Xserver/Xprint/etc/profile.d/xprint.sh" are + scripts for Linux (which support /etc/profile.d/ ; note that + this does not include Debian) to populate the ${XPSERVERLIST} + env var for each user. + 5. Starting Xprt "manually" (without using /etc/init.d/xprint): Set + the ${XPCONFIGDIR} env variable to the directory where Xprt can + find it's configuration data. + +WARNING + If Xprt cannot find it's configuration data it will not be able to + use printer-builtin fonts (which are defined by the model-config + in the configuration dir). Without printer-builtin fonts Xprt may + fall back to generate font glyphs from bitmap fonts (this resulted + in the MYTH that "Xprt can only print gfx fonts". This is not TRUE + - this only happens if Xprt is either misconfigured or no matching + builtin or PS Type1 font is available). + You may want to make a copy of the default configuration directory + and modify it to match your needs. + 6. Starting Xprt is just as easy as starting any other Xserver: + % Xprt :12 + will start Xprt on display 12 (e.g. set ${XPSERVERLIST} to ":12" + or "myhostname:12". + You may want to copy your framebuffer Xserver's font path to be + able to print all fonts which can be displayed on that Xserver. + % Xprt -fp $(xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 + }") :12 + +Notes: + + * The /etc/init.d/xprint has a more advanched filtering scheme based + on regex patters to "accept" and/or "reject" font paths + * 'xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 + }"' may be too simple-minded if your Xserver does not support + TrueType fonts. The following statemement is better in this case + since it filters the font path and removes all path elements which + have TrueType fonts (*.ttf, *.TTF) or TrueType font collections + (*.ttc, *.TTC) in fonts.dir: + % xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }" | + tr "," "\n" | while read i ; do \ + if [ "$(cat ${i}/fonts.dir | egrep -i "ttf|ttc" 2>/dev/null)" == "" ] \ + ; then echo $i ; fi ; done | (fontpath="" ; fpdelim=""; while read i ; \ + do fontpath=${fontpath}${fpdelim}${i} ; fpdelim="," ; done ; echo \ + $fontpath) + * It may be easier to just feed all available font paths to Xprt + (BTW: mozilla 1.0 had a bug in that case which resulted in the + problem that it used many many bitmap fonts in that case - this + has been fixed for 1.0.1 and Netscape 7 (that's the reason why the + quickguides for hebrew/cyrillic use the "Xp_dummyfonts" fonts + instead of /usr/openwin/lib/X11/fonts/misc/ - to avoid that + Mozilla finds bitmap fonts for the same locale). The following + "small" one-liner finds all fonts (except printer builtin fonts): + % find /usr/openwin -name fonts.dir | while read i ; do echo + ${i%/fonts.dir} ; done | fgrep -v "models/" + Plug it into the filter above to remove the Truetype fonts and you + are "done"... :) + + See [191]TROUBLESHOOTING if you run into problems... + + Q: + + How can I get a list of printers managed by Xprint ? + A: + + The tool "xplsprinters" is designed for that purpose. It can deliver + both list of printers and attributes supported for a specific list of + printers. Use % xplsprinters -h # to obtain usage information. + Example: + * Get list of available printers: +% xplsprinters +printer: hplaserjet001@castor:19 +printer: hpcolor001@castor:19 +printer: laser1@jason:5 +printer: david_dj01@jason:5 + * Get information about the supported attrbites of printer "ps002": +% xplsprinters -printer ps002 -l +printer: ps002@castor:18 + comment= + model-identifier=HPDJ1600C + default-medium=iso-a4 + default-input-tray= + medium-source-sizes-supported=iso-a4 false 6.35 203.65 6.35 290.65 + medium-source-sizes-supported=na-letter false 6.35 209.55 6.35 273.05 + default-printer-resolution=300 + resolution=300 + default_orientation= + orientation=portrait + orientation=landscape + default_plex= + plex=simplex + + Q: + + How can I start Xprt at boot time ? + A: + + "xc/programs/Xserver/Xprint/etc/init.d/xprint" is a script for SystemV + and Linux to start/stop/restart Xprt at system startup (e.g. + per-machine) or for a single user (e.g. per-user). The script includes + installation and usage details. + Q: + + How can I start Xprt per-user ? + A: + + "xc/programs/Xserver/Xprint/etc/init.d/xprint" is a script for SystemV + and Linux to start/stop/restart Xprt at system startup (e.g. + per-machine) or for a single user (e.g. per-user). The script includes + installation and usage details. + Q: + + How can I start Xprt only for one application ? + A: + + Create your own version/copy of /etc/init.d/xprint and modify it to + fit your requirements and then make sure that you issue a + "my_xprint_startscript start" before starting the application and a + "my_xprint_startscript stop" after leaving the application. + Q: + + How can I filter the font path which should be passed to Xprt for + certain fonts ? + A: + + XXX + Q: + + How can I manage access control to the Xprt server ? + A: + + Access control to Xprt is not differently as to any other Xserver and + 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 xhost(1x))) and/or per-machine (using + "xhost" (see xhost(1x)) and/or /etc/X<dpy>.hosts (<dpy> == display + number, e.g. /etc/X0.hosts for display 0) (see Xserver(1x))) Consult + manual pages Xsecurity(7), xhost(1x), Xserver(1x) etc. for further + details. + Q: + + How can I log access to the Xprt server ? + A: + + Logging access to Xprt can be done using the standard Xserver + auditing, see the Xserver(1x) manual page, option "-audit" + Q: + + Does it require "root" permissions to use Xprt/Xprint ? + A: + + No, both Xprint clients and Xprint server(s) do not require root + rights to work. + + Xprint clients are handled like any other X11 application and the Xprt + servers can run without any special requirements. Solaris is an + exception here since it requires to start any Xserver (incl. Xprt) + setgid "root" (set-group-id "root", this is not set-user-id "root") + since the sockets/pipe files in /tmp/.X11-pipe/ and /tmp/.X11-unix/ + are only accessible for the group "root". The workaround is to start + Xprt with the option "-pn"; therefore even Xprt server binaries which + are not setgid "root" can run without problems). + Q: + + How can I see the attributes of a printer managed by Xprint ? + A: + + "xplsprinters -printer myprinter004 -l" will do the job for printer + "myprinter004". + + See xplsprinters(1x) for futher usage and a description of the output. + Q: + + How can I list the font path used by a Xprt server ? + A: + + Figure out the display id of the server which should be queried (we + are using "foobar:98" in this example) and then try this: +% (DISPLAY=foobar:98 xset q | \ +awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }" | \ +tr "," "[\n]") +# Output may look like: +PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/HPDJ1600C/fonts/ +PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/SPSPARC2/fonts/ +PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/HPLJ3Si-PS/fonts/ +/usr/openwin/lib/X11/fonts/F3/ +/usr/openwin/lib/X11/fonts/F3bitmaps/ +/usr/openwin/lib/X11/fonts/Type1/ +/usr/openwin/lib/X11/fonts/Speedo/ +/usr/openwin/lib/X11/fonts/misc/ +/usr/openwin/lib/X11/fonts/75dpi/ +/usr/openwin/lib/X11/fonts/100dpi/ + +Note: + + Note that the font path items which start with "PRINTER:" are only be + sourced after the matching printer has been selected and configured + (for developers: After XpSetContext has been called). + + Q: + + "xset q" lists all model-specific font dirs (like + PRINTER:/myxpcfg/C/print/models/SPSPARC2/fonts/") - is that a bug ? + A: + + No, this is normal. Xprt will add all fonts of all printer models to + the font path - but font path items starting with "PRINTER:" are only + available for an application after the matching printer has been + selected and configured (for developers: After XpSetContext has been + called), before that point fonts in these dirs are not available for + an application. + Q: + + My application lists a printer called "xp_ps_spooldir_tmp_Xprintjobs" + / "xp_pdf_spooldir_tmp_Xprintjobs" / "spooldir_tmp_Xprintjobs" / in + the print dialog but I do not have such a print queue installed + anywhere. What is that for a thing ?! + A: + + "xp_ps_spooldir_tmp_Xprintjobs" and "xp_pdf_spooldir_tmp_Xprintjobs" + ("spooldir_tmp_Xprintjobs" was the old, pre-009 name for + "xp_ps_spooldir_tmp_Xprintjobs") are special Xprint printer targets + which uses the "PSspooldir" / "PS2PDFspooldir-GS" printer models. + These model config sends PostScript or PDF jobs to the + /tmp/Xprintjobs/ directory instead to a physical printer (quite + usefull for people who want to get the PostScript or PDF files as + output instead of printed pages). + + References: + * [192]xprint.mozdev.org bug 5092 ("[PS2PDFspooldir-GS] RFE: Add + printer model which sends PDF jobs to /tmp/Xprintjobs/") + + Q: + + How can I forward Xprint services when logging-in via ssh to another + machine ? + A: + + You have to forward the X11 connection for the Xprint server(s) to the + remote system and set the XPSERVERLIST variable to direct the Xprint + clients to the forwarded ports. + + Example 1. Login to a remote host using slogin (assuming there is only + one Xprint server listed in XPSERVERLIST) +% echo $XPSERVERLIST +west:33 + + Add 6000 to the display number ("33" in this example) to get the port + number (X11 port numbers start at port 6000. 6000 is display number + "0", 6001 is display number 6001 and so on) and then ask slogin to + forward the port: +% slogin -R6033:west:6033 -l nrubsig puzzle + +nrubsig's password: +Last login: Fri Jan 23 04:05:06 2004 from west.informatik.med.uni-giessen.de +Have a lot of fun... + + Then set the XPSERVERLIST env var on the remote host to the forwarded + ports and you are done: +% export XPSERVERLIST="localhost:33 ${XPSERVERLIST}" + + Example 2. Login to a remote host using slogin (assuming there are + multiple Xprint servers listed in XPSERVERLIST) + + The following small shell script will process the XPSERVERLIST env var + and output the parameters for calling slogin/ssh with all Xprint + server ports forwarded: +#!/bin/ksh +# xp_print_slogin_args.ksh +# Small example which parses $XPSERVERLIST and prints out how slogin/ssh +# should be used to forward all local Xprint servers + +PORTARGS="" +REMOTE_XPSERVERLIST="" +spacer="" # seperator +remoteport=6100 +remotedisplaynum=100 + +echo "${XPSERVERLIST}" | tr " " "\n" | + while read i ; do + [ "$i" = "" ] && continue + displaynum="${i##*:}" + port="$(( ${displaynum} + 6000 ))" + hostname="${i%:*}" + PORTARGS="${PORTARGS}${spacer}-R${remoteport}:${hostname}:${port}" + REMOTE_XPSERVERLIST="${REMOTE_XPSERVERLIST}${spacer}localhost:${remoted +isplaynum}" + + spacer=" " + remoteport=$((${remoteport} + 1)) + remotedisplaynum=$((${remotedisplaynum} + 1)) + done +echo "Log in with: % slogin ${PORTARGS} -l myloginname myremotehost" +echo "Set remote XPSERVERLIST with % export XPSERVERLIST=\"${REMOTE_XPSERVERLIS +T} \${XPSERVERLIST}\"" +# EOF. + + Example usage: +% xp_print_slogin_args.ksh + + will print +Log in with: % slogin -R6100:west:6033 -R6101:north:6033 -l myloginname myremot +ehost +Set remote XPSERVERLIST with % export XPSERVERLIST="localhost:100 localhost:101 + ${XPSERVERLIST}" + +3. Configuration + + Q: [193]How do I change the defaults for + double-sided/single-sided/etc. printing ? + + Q: [194]I am in America and I don't have any ISO A4 paper. How do I + change the default paper size to 8.5 inch x 11 inch (US-Letter) + ? + + Q: [195]How do I change the default printer resolution ? + Q: [196]How do I change the default settings for + "portrait"/"landscape"/"seascape" (=page orientation) ? + + Q: [197]How can I prevent Xprt from using any bitmap(=gfx) fonts ? + Q: [198]I want only my manually added printers managed by Xprint. How + can I prevent Xprt from looking-up the printer names + automatically ? + + Q: [199]How can I specify an own program/script to enumerate the + printers on my system ? + + Q: [200]Which program is used by default by Xprt to enumerate the + printers on my system ? + + Q: [201]Where can I get more PostScript Type1 fonts from ? + Q: [202]What are PMF fonts (e.g. the *.pmf fonts in + ${XPCONFIGDIR}/C/print/models/%model_name%/fonts/ (or + ${XPCONFIGDIR}/${LANG}/print/models/%model_name%/fonts/)) ? + + Q: [203]Can I use the fontserver ("xfs") with Xprt ? + Q: [204]What is a "model-config" ? + Q: [205]Where can I store the default values for printers ? + Q: [206]How can I create my own model-config ? + Q: [207]How can I create my own PMF "fonts" ? + Q: [208]Where can I get more model-configs from ? + Q: [209]If I install Xprt &co. as "root" in the default location and + don't need to set ${XPCONFIGDIR} - where are my configuration + files located then ? + + Q: [210]Are config files and/or the PMF fonts architecture dependent ? + + Q: [211]Can I localise my Xprint/Xprt configuration (l10n) ? + Q: [212]Can I execute my own scripts to process the PostScript files + generated by Xprt ? + + Q: [213]How can I disable "xp_ps_spooldir_tmp_Xprintjobs" / + "xp_pdf_spooldir_tmp_Xprintjobs" printer targets ? + + Q: + + How do I change the defaults for double-sided/single-sided/etc. + printing ? + A: + + This is controlled via the "plex" attribute in the document attribute + pool (${XPCONFIGDIR}/${LANG}/print/attributes/document and/or + ${XPCONFIGDIR}/C/print/attributes/document). Examples: + 1. Adding/modifying the following line to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default plex + for all printers to "duplex": + *plex: duplex + 2. Adding/modifying the following two lines to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default plex + for all printers to "duplex" except for printer "ps003" which + should default to "simplex": + *plex: duplex + ps003.plex: simplex + +Notes: + + * Not all printers support all plex modes. The model-config may + restrict the available plex modes. + * Setting a plex mode which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt + to not set a default plex. + * The PostScript DDX supports plex modes "simplex", "duplex" and + "tumble". + * Verification: Use + xplsprinters -l | egrep "^printer:|default_plex=|plex=" + to view the plex settings for all printers. + + Q: + + I am in America and I don't have any ISO A4 paper. How do I change the + default paper size to 8.5 inch x 11 inch (US-Letter) ? + A: + + This is controlled via the "default-medium" attribute in the document + attribute pool (${XPCONFIGDIR}/${LANG}/print/attributes/document + and/or ${XPCONFIGDIR}/C/print/attributes/document). Examples: + 1. Adding/modifying the following line to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default paper + size for all printers to "na-letter": + *default-medium: na-letter + 2. Adding/modifying the following two lines to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default paper + size for all printers to "na-letter" except for printer "ps003" + which should default to "iso-a4": + *default-medium: na-letter + ps003.default-medium: iso-a4 + +Notes: + + * xprint.mozdev.org releases >= 007 provides a seperate "document" + attribute pool for en_US(-like) locales (see + ${XPCONFIGDIR}/en_US/print/attributes/document) which will + override the default ISO-A4 with US-Letter (this feature assumes + that ${LANG} is set to "en_US" (or a locale which has similar + defaults as "en_US", those are currently linked to "en_US" in + ${XPCONFIGDIR}/)) + * Not all printers support all paper sizes. The model-config may + restrict the available paper sizes. + * Setting a paper size which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt + to not set a default paper size. + * The PostScript DDX supports the following paper sizes: + + X.org release 6.6 (X116.6): "iso-a4", "na-letter", + "na-legal", "executive", "iso-designated-long", + "na-number-10-envelope" + + xprint.mozdev.org release >= 006: "na-letter", "na-legal", + "executive", "folio", "invoice", "ledger", "quarto", "a", + "b", "c", "d", "e", "na-6x9-envelope", "na-10x15-envelope", + "monarch-envelope", "na-10x13-envelope", "na-9x12-envelope", + "na-number-10-envelope", "na-7x9-envelope", + "na-9x11-envelope", "na-10x14-envelope", + "na-number-9-envelope", "iso-a0", "iso-a1", "iso-a2", + "iso-a3", "iso-a4", "iso-a5", "iso-a6", "iso-a7", "iso-a8", + "iso-a9", "iso-a10", "iso-b1", "iso-b2", "iso-b3", "iso-b4", + "iso-b5", "iso-b6", "iso-b7", "iso-b8", "iso-b9", "iso-b10", + "jis-b1", "jis-b2", "jis-b3", "jis-b4", "jis-b5", "jis-b6", + "jis-b7", "jis-b8", "jis-b9", "jis-b10", "iso-c3", "iso-c4", + "iso-c5", "iso-c6", "iso-designated-long" + * Verification: Use + xplsprinters -l | egrep "^printer:|default-medium=|medium-source-sizes-suppor +ted=" + to view the medium settings for all printers. The + 'medium-source-sizes-supported='-lines have the format XXX. + + Q: + + How do I change the default printer resolution ? + A: + + This is controlled via the "default-printer-resolution" attribute in + the document attribute pool + (${XPCONFIGDIR}/${LANG}/print/attributes/document and/or + ${XPCONFIGDIR}/C/print/attributes/document). Examples: + 1. Adding/modifying the following line to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default + resolution for all printers to 600 DPI: + *default-printer-resolution: 600 + 2. Adding/modifying the following two lines to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default + resolution for all printers to 300 DPI except for printer + "tekcolor_ps" which should default to 1200 DPI: + *default-printer-resolution: 300 + tekcolor_ps.default-printer-resolution: 1200 + +Notes: + + * Not all printers support all resolutions. The model-config may + restrict the available resolutions. + * Setting a resolution which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt + to not set a default resolution. + * The PostScript DDX supports the following default resolutions + + X.org release 6.6 (X116.6): 300, 600, 720, 940, 1200, 1440, + 2400 + + xprint.mozdev.org release >= 006: 75, 100, 120, 150, 180, + 200, 240, 300, 360, 400, 600, 720, 940, 1200, 1440, 2400 + * Verification: Use + xplsprinters -l | egrep "^printer:|default-printer-resolution=|resolution=" + to view the resolution settings for all printers. + + Q: + + How do I change the default settings for + "portrait"/"landscape"/"seascape" (=page orientation) ? + A: + + This is controlled via the "content-orientation" attribute in the + document attribute pool + (${XPCONFIGDIR}/${LANG}/print/attributes/document and/or + ${XPCONFIGDIR}/C/print/attributes/document). Examples: + 1. Adding/modifying the following line to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default + orientation for all printers to "portrait": + *content-orientation: portrait + 2. Adding/modifying the following two lines to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default + orientation for all printers to "portrait" except for printer + "ps003" which should default to "landscape": + *content-orientation: portrait + ps003.content-orientation: landscape + +Notes: + + * Not all printers support all orientations. The model-config may + restrict the available orientations. + * Setting an orientation which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt + to not set a default orientation. + * The PostScript DDX supports the following orientations: + "portrait", "landscape", "reverse-portrait" and + "reverse-landscape". + * Verification: Use + xplsprinters -l | egrep "^printer:|default_orientation=|orientation=" + to view the orientation settings for all printers. + + Q: + + How can I prevent Xprt from using any bitmap(=gfx) fonts ? + A: + + Do not pass any bitmap fonts with the "-fp" (=font path) argument. + However you have to provide a 'fixed' and a 'cursor' font, a Xserver + can't start without having these fonts. + + Procedure 1. Task list: + 1. Create a new directory: +% mkdir Xp_dummyfonts +% cd Xp_dummyfonts + 2. Create a fonts.alias file with the following content: +! alias for "fixed" font +! original from /usr/openwin/lib/X11/fonts/misc/fonts.alias looks like this: +! fixed "-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1" +fixed -*-r-*--*-*-*-*-*-*-iso8859-1 +! EOF. + 3. Copy or link "6x13.pcf.Z" and "cursor.pcf.Z" and create fonts.dir +% ln -s /usr/openwin/lib/X11/fonts/misc/6x13.pcf.Z . +% ln -s /usr/openwin/lib/X11/fonts/misc/cursor.pcf.Z . +% mkfontdir $PWD + 4. Verify: The directory should now look like this: +% ls -1 +6x13.pcf.Z +cursor.pcf.Z +fonts.alias +fonts.dir + 5. Add the full path (e.g. /home/xp/Xp_dummyfonts) as last element of + the font path when starting Xprt: + % Xprt -fp /usr/openwin/lib/X11/fonts/Type1/,/home/xp/Xp_dummyfonts :12 + + Q: + + I want only my manually added printers managed by Xprint. How can I + prevent Xprt from looking-up the printer names automatically ? + A: + + Add a line with "Augment_Printer_List %none%" to + ${XPCONFIGDIR}/C/print/Xprinters (or + ${XPCONFIGDIR}/${LANG}/print/Xprinters) and add lines with "Printer + <name>" for each printer <name>. Example: +Augment_Printer_List %none% +Printer ps001 +Printer ps003 +Printer hplaser6 + + will add only the printers "ps001", ps003" and "hplaser6". + Q: + + How can I specify an own program/script to enumerate the printers on + my system ? + A: + + Add "Augment_Printer_List my_script" to + ${XPCONFIGDIR}/C/print/Xprinters (or + ${XPCONFIGDIR}/${LANG}/print/Xprinters). The script must return the + printer names - one per line, ASCII-only - to stdout. + Q: + + Which program is used by default by Xprt to enumerate the printers on + my system ? + A: + + This depends on the OS: + * On Solaris (and most other OSes exclusing AIX and Linux): +% lpstat -a | cut -d " " -f 1 + * On Linux: + + For Xprt build from X11R6.x X.org sources: +% lpc status | grep -v '^\t' | sed -e /:/s/// # '\t' means TAB + + For Xprt build from xprint.mozdev.org <= release 008 sources + (both lines are executed to support both LPRng and CUPS + (using the CUPS *BSD compatibility tools)): +% lpc status | awk '/:$/ && !/@/ { print $1 }' | sed -e /:/s/// ; \ + lpc -a status | awk '/@/ && !/:/ { split( $1, name, \"@\" ); print name[1]; } +' + + Xprt build from xprint.mozdev.org >= release 009 sources uses + a more flexible scheme which tries to enumerate the print + spoolers in the order "CUPS" (using the normal CUPS + (SYSV-like) commands), "LPRng" and finally "*BSD", the first + working (=print queues are found) print spooler is chosen. + The spooler(s) being used (and the query order) can be + changed by the "-XpSpoolerType" command line option. The list + of commands used to enumerate the queues for a specific + spooler type can be found in + xc/programs/Xserver/Xprint/spooler.c + * On AIX v4: +% lsallq | grep -v '^bsh$' + +Notes: + + * See xc/programs/Xserver/Xprint/Init.c (xprint.mozdev.org >= + release 009 uses xc/programs/Xserver/Xprint/spooler.c) for a + complete list of commands used on the specific platforms to + enumerate the printers. + * Note that the output is always piped through "sort" to get an + alphabetical order (the "default" printer is not chosen/defined + here(=server side), the client side is responsible to choose a + default printer. See FAQ item about the ${XPRINTER} env var how to + set your default printer). + + Q: + + Where can I get more PostScript Type1 fonts from ? + A: + + Some sources: + * Adobe: + + Commercial fonts: [214]http://www.adobe.com/type/main.html + + Free Euro font: + o Single-glyph (e.g. it contains only the euro char) euro + font: [215]http://www.adobe.com/type/eurofont.html or + [216]ftp://ftp.adobe.com/pub/adobe/type/win/all/ + ("eurofont.exe" can be unzipped using "unzip") + o ISO8859-15: XXX - WANTED!! + * Solaris shipps with various PS Type 1 fonts: + + Arabic: /usr/openwin/lib/locale/ar/X11/fonts/Type1/ + (fonts.dir and fonts.scale missing, maybe they miss the + presentation forms a&b, too [unconfirmed]) + + ISO-8859-13 (Latin 8): + /usr/openwin/lib/locale/iso_8859_13/X11/fonts/Type1/ + + ISO-8859-5 (Latin 5): + /usr/openwin/lib/locale/iso_8859_9/X11/fonts/Type1/ + + ISO-8859-8/Hebrew: + /usr/openwin/lib/locale/iso_8859_8/X11/fonts/Type1 (BROKEN, + even "type1fix" cannot fix them. Use the hebrew fonts from + [217]broken-link-/PS_Type1_iso8859-8.tar.gz) + + ISO-8859-7/Modern greek: + /usr/openwin/lib/locale/iso_8859_7/X11/fonts/Type1/ + + ISO-8859-5/Cryrillic: + /usr/openwin/lib/locale/iso_8859_5/X11/fonts/Type1/ + + ISO-8859-4 (Latin 4): + /usr/openwin/lib/locale/iso_8859_4/X11/fonts/Type1/ + + ISO-8859-2 (Latin 2): + /usr/openwin/lib/locale/iso_8859_2/X11/fonts/Type1/ + + ISO-8859-1 (Latin 1) and Symbol fonts: + /usr/openwin/lib/X11/fonts/Type1/ + + Q: + + What are PMF fonts (e.g. the *.pmf fonts in + ${XPCONFIGDIR}/C/print/models/%model_name%/fonts/ (or + ${XPCONFIGDIR}/${LANG}/print/models/%model_name%/fonts/)) ? + A: + + PMF "fonts" are "printer metric files" (.pmf) that describe the + metrics of the fonts (which means they do not contain any data to + render the fonts - they contain only the plain metrics of a font) + which are built into the printer (ROM or via font catridge etc.). The + file format is identical to the PCF ("Portable Compiled Format") font + format except that the bitmap data is not provided. + Q: + + Can I use the fontserver ("xfs") with Xprt ? + A: + + You can use Xprt with the font server ("xfs") like with any other + Xserver - but it is not recommded since the font server protocol does + not allow access to the native font format and therefore disables font + download, e.g. both PS Type1 and TrueType fonts cannot be downloaded + anymore and Xprt will fall-back to embed them as bitmap glyphs in the + print job (e.g. the fonts will still appear correctly in the printout, + but the quality may be reduced since downloaded fonts are always + better than bitmap glyphs). (users of xprint.mozdev.org-release <= 006 + may see [218]xprint.mozdev.org bug 2092 if they use "xfs"; this has + been fixed in the 007 release!) + Q: + + What is a "model-config" ? + A: + + The term "model-config" refers to the subdirs in + ${XPCONFIGDIR}/${LANG}/print/models/. There subdirs contain + information about the attributes for a specific printer model or + family/class of printer models. In particular there are two kinds of + information: + * "${XPCONFIGDIR}/${LANG}/print/models/${NAME_OF_MODEL}/model-config + " this file defines a set of attributes supported by this specific + printer (-family/-class/etc.) and + * "${XPCONFIGDIR}/${LANG}/print/models/${NAME_OF_MODEL}/fonts/" - a + directory which contains a set of PMF (printer metrics file) fonts + builtin into the printer itself (actually the PMF "font" format + contains only metrics information and no glyphs). These fonts are + only available to the application after the application has + selected a printer and configured it (for developers: After + XpSetContext has been called). + + Q: + + Where can I store the default values for printers ? + A: + + XXX + Q: + + How can I create my own model-config ? + A: + + XXX + Q: + + How can I create my own PMF "fonts" ? + A: + + XXX - no solution yet, but [219]xprint.mozdev.org bug 2430 ("RFE: Need + tool to create PMF (printer metrics file) fonts") has been filed to + create a freeware tool to create such fonts. + Q: + + Where can I get more model-configs from ? + A: + + If you miss a model-config for your printer please open a bug/RFE at + [220]http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi?prod + uct=xprint&component=Server%3A+Config%3A+model-configs (e.g. + [221]http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi, + product "Xprint", component "Server Config: model-configs"). + Q: + + If I install Xprt &co. as "root" in the default location and don't + need to set ${XPCONFIGDIR} - where are my configuration files located + then ? + A: + + This is platform-specific, based on the "XPrintDir" Imake variable set + at build time. Default location for plain X11R6.x is + "${XProjectRoot}/lib/X11/xserver" (set at build time), but some + platforms modify "XPrintDir" to alternate locations: + * Solaris sets ${XPCONFIGDIR} to /usr/openwin/server/etc/XpConfig/ + * Linux (non-Debian) sets ${XPCONFIGDIR} to + /usr/X11R6/lib/X11/xserver/ or /etc/X11/xserver/ + * Debian Linux sets ${XPCONFIGDIR} to /usr/share/Xprint/xserver/ + +Tip + + If you don't know where the default location for ${XPCONFIGDIR} is + located try + strings -a /usr/openwin/bin/Xprt | grep XPRINTDIR + + - it may return some debug info from the binary containing the builtin + XpConfig path. + + Q: + + Are config files and/or the PMF fonts architecture dependent ? + A: + + The PMF fonts are a variant of the PCF font format, they are (like the + PCF format) architecture-independent. These fonts must be kept + together with the other model config data since they depend on the + printer model (de facto ${XPCONFIGDIR}/C/print/models/ (and/or + ${XPCONFIGDIR}/${LANG}/print/models/) should be supplied by the + printer vendors (but most people will create their own models on + demand since I doubt that any vendor except HP, Sun and + xprint.mozdev.org staff ever looked at that stuff)). Per definition + they are read-only data supplied by the vendor, but modifying them may + be usefull, too. I would say it is recommended to put treat all Xprint + files in ${XPCONFIGDIR} as read-only vendor data; admins should create + copies of this tree on demand (and/or (soft-)link some files) and set + ${XPCONFIGDIR} to the modified config data. + Q: + + Can I localise my Xprint/Xprt configuration (l10n) ? + A: + + Yes, Xprt supports localisation ("l10n") by default. Default values + for all locales are stored in ${XPCONFIGDIR}/C/print/, locale-specific + settings can be set in ${XPCONFIGDIR}/${LANG}/print/ Rules: + * Attribute pools ("${XPCONFIGDIR}/*/print/attributes/document", + "${XPCONFIGDIR}/*/print/attributes/job", + "${XPCONFIGDIR}/*/print/attributes/printer" and + "${XPCONFIGDIR}/*/print/models/*/model-config"): "document", "job" + and "printer" attribute pools and printer model-configs are + sourced first from the "${XPCONFIGDIR}/C/print/"-directory, then + they are overridden by any attributes from the locale-specific + pools (in "${XPCONFIGDIR}/${LANG}/print/"), e.g. any values set in + "${XPCONFIGDIR}/C/print/attributes/*" and + "${XPCONFIGDIR}/C/print/models/*/model-config" will automatically + apply to all other locales unless they are overridden by + locale-specific versions of these files + ("${XPCONFIGDIR}/${LANG}/print/attributes/*", + "${XPCONFIGDIR}/${LANG}/print/models/*/model-config") + * "Xprinters" (list of printers): If there is a locale-specific + ${XPCONFIGDIR}/${LANG}/Xprinters present it will be used instead + of ${XPCONFIGDIR}/C/Xprinters (e.g. values set in + ${XPCONFIGDIR}/C/Xprinters will be ignored and the values from + ${XPCONFIGDIR}/${LANG}/Xprinters will be used instead). + * Xprt will determinate the locale which should be used based on the + ${LANG}-environment vaiable at startup time. If there is no such + variable set at that time LANG="C" is assumed. + +Note: + Attribute values for paper names and orientation names refer to + builtin strings in the DDX code (which are itself based on + international standards), these cannot be changed to your own + "inventions" (it does it make sense to try to "localize" paper + names - "ISO-A4" is "ISO-A4" even in japanese/hebrew/german etc.). + Locale-spefific attribute pools can set their own, different + values - but only within the allowed range of values supported by + the DDX and printers's model-config. + + Q: + + Can I execute my own scripts to process the PostScript files generated + by Xprt ? + A: + + Yes, there are at least two possible solutions: + 1. Create your own model-config which uses a custom + "xp-spooler-command" value - the xprint.mozdev.org's "PSspooldir" + model config (see "${XPCONFIGDIR}/C/print/models/PSspooldir/" and + "${XPCONFIGDIR}/C/print/attributes/printer" and + "${XPCONFIGDIR}/C/print/Xprinters") and "PS2PDFspooldir-GS" model + config (see "${XPCONFIGDIR}/C/print/models/PS2PDFspooldir-GS/" and + "${XPCONFIGDIR}/C/print/attributes/printer" and + "${XPCONFIGDIR}/C/print/Xprinters") are good examples for that. + 2. Use an existing "model-config" (which would normally send it's + data to a printer using the default print spooler command) and + provide a custom "xp-spooler-command". + + Procedure 2. Example (using "SPSPARC2" as printer model, + /w/xp_conv as the script to execute and "myscriptprinter" as name + of the printer): + 1. Edit ${XPCONFIGDIR}/C/print/attributes/printer and add these + lines (Xprt will replace "%printer-name%" with the printer's + name, "%copy-count%" with the number of job copies, + "%job-name%" with the job's title and "%options%" with any + custom spooler options): +myscriptprinter.xp-model-identifier: SPSPARC2 +myscriptprinter.xp-spooler-command: /w/xp_conv -p %printer-name% -c %copy-count +% -t %job-name% -o "%options%" + 2. Edit ${XPCONFIGDIR}/C/print/Xprinters and append this line: +Printer myscriptprinter + + Q: + + How can I disable "xp_ps_spooldir_tmp_Xprintjobs" / + "xp_pdf_spooldir_tmp_Xprintjobs" printer targets ? + A: + + Edit ${XPCONFIGDIR}/C/print/Xprinters and remove or comment-out (using + '#') the lines "Printer xp_ps_spooldir_tmp_Xprintjobs" and "Printer + xp_pdf_spooldir_tmp_Xprintjobs". + +Note: + + Note that Xprt will NOT start if this printer has been + removed/disabled and no other print queue is available (e.g. if + "xp_ps_spooldir_tmp_Xprintjobs" and "Printer + xp_pdf_spooldir_tmp_Xprintjobs" are the only printer target + available). + +4. Troubleshooting + + Q: [222]Xprt refuses to start with the message "sh: lpc: command not + found" on my Linux machine. What does that mean ? + + Q: [223]When the application (=client side) tries to connect to the + Xprt (Xserver) side it fails with a Xlib: connection to + "meridian:52.0" refused by server Xlib: Client is not + authorized to connect to Server What does that mean ? + + Q: [224]Xprt refuses to start with the message "failed to set default + font path '...' Fatal server error: could not open default font + 'fixed'". What does that mean ? + + Q: [225]Just copying my fonts into a directory and adding the path to + my Xprt command line didn't work - I always get "Fatal server + error: could not open default font 'fixed'". What am I doing + wrong ? + + Q: [226]Xprt refuses to start with the message "Fatal server error: + Cannot establish any listening sockets - Make sure an X server + isn't already running". What does that mean ? + + Q: [227]Xprt refuses to start with the message "Fatal server error: + Failed to establish all listening sockets". What does that mean + ? + + Q: [228]Xprt refuses to start with the message "Fatal server error: + could not open default font 'fixed'" or "Fatal server error: + could not open default cursor font 'cursor'". + + Q: [229]Xprt refuses to start with the message "Fatal server error: no + screens found". What does that mean ? + + Q: [230]"Printing itself works but the printout covers only 1/4 of the + paper - what am I doing wrong ?" + + Q: [231]"Printing works but I get large borders/margins..." / "[Top] + margin is too small" / "Margins are wrong" / etc. + + Q: [232]Xprt prints a warning like "Xp Extension: could not find + config dir /usr/X11R6/lib/X11/C/print" - what does that mean ? + + Q: [233]Xprt crashes with "Fatal server error: Beziers this big not + yet supported" What does that mean ? + + Q: [234]"My PS Type1 font does not work with my Xserver - how can I + fix this ?" + + Q: [235]I can't get it working. I have set ${DISPLAY} correctly to + point to the Xprt display and... ... What is going wrong ? + + Q: [236]When I try to print via Xprint I get the message "Fatal server + error: unable to exec '/usr/bin/lp'". What is going wrong here + ? + + Q: [237]The Solaris Xprt prints some error messages about PostScript + fonts like "FOOBAR not found, using Courier. CMEX0123 not + found, using Courier." etc. and uses "Courier" instead of these + fonts... + + Q: [238]"Xprt refused to start, complaining about a missing dir + (/etc/X11/xserver/C/print/ directory)... I created it by hand + (empty) and started Xprt but it still does not work + properly..." + + Q: [239]My Linux system already shipps with a + '/usr/X11R6/bin/Xprt'-binary. Do I need the binary distribution + from http://xprint.mozdev.org/ ? + + Q: [240]I am getting the error message "error opening security policy + file /usr/X11R6/lib/X11/xserver/SecurityPolicy". What does that + mean ? + + Q: [241]I have modified the "HPLJ4family" [or "HPDJ1600C" etc.] + printer model to work with my PostScript printer, but when I + print I get empty places where some text should be - what am I + doing wrong here ? + + Q: [242]Xprt outputs warning messages like: Xp Extension: Can't load + driver XP-PCL-MONO init function missing Xp Extension: Can't + load driver XP-RASTER init function missing What does that mean + ? + + Q: [243]Printing on Solaris with Mozilla/Eclipse [or any other Xprint + client] removes spaces between words. What is going wrong ? + + Q: [244]Installation of the "GISWxprint" / "GISWxprintglue" packages + fails like this: # pkgadd -d + /space/staging/xprint/GISWxprint.pkg pkgadd: ERROR: no packages + were found in </var/tmp/dstreAAA5Jayyz> Any idea what I am + doing wrong ? + + Q: [245]Printing page results in [two/three/.../16] leading blank + pages, followed by a correct (but offset) page. Any idea what + is going wrong ? + + Q: + + Xprt refuses to start with the message "sh: lpc: command not found" on + my Linux machine. What does that mean ? + A: + + Some versions of Xprt look up printer queues using "lpc" on Linux. In + this case "lpc" cannot be found for some reason. Solution: Find the + place where "lpc" is installed on your machine (some distributions put + it into /usr/sbin, some into /usr/bin/) and check whether your PATH + env var includes this directory. Example (if "lpc" is located in + /usr/sbin/): + % which lpc + /usr/sbin/lpc + % export PATH=$PATH:/usr/sbin + # Start Xprt ... + % Xprt <your-options-come-here> + + Q: + + When the application (=client side) tries to connect to the Xprt + (Xserver) side it fails with a +Xlib: connection to "meridian:52.0" refused by server +Xlib: Client is not authorized to connect to Server + + What does that mean ? + A: + + X11 implements access control. You can have host-based, cookie-based + (a "cookie" is used like a passport) or user-based (SecureRPC or + Kerberos5) authentification. Xsecurity(7) has most of the details. + 1. No access control: . If you do not want to use access control for + Xprt then you can start it with the option "-ac" (see Xserver(1x)) + to disable the access control. Example: + % Xprt -ac -audit 4 :12 + will start Xprt with access control disabled and with auditing + enabled (e.g. the "-audit 4" option). + +WARNING + Disabling the access control will enable everyone who can access + Xprt to print on your printers (that's why the above example shows + how to use auditing, too - that you can see who does something + with Xprt...) !! + 2. Host-based access control: . Host-based access control can be + archived using /etc/X<dpy>.hosts (<dpy> == display number, e.g. + /etc/X0.hosts for display 0 (see Xserver(1x) manual page for + further details)). + + Procedure 3. Example + 1. Add the following line to `/etc/X12.hosts' (assuming you want + that the hosts 'merkur' and 'mars' should be able to access + the Xprt server running as display 12 on your host 'neptun'): +INET:merkur +INET:mars + 2. Start Xprt + 3. Verify that Xprt is correctly configured: +% export DISPLAY=neptun:12 +% xhost +access control enabled, only authorized clients can connect +INET:localhost +LOCAL: +INET:merkur +INET:mars + + Q: + + Xprt refuses to start with the message "failed to set default font + path '...' Fatal server error: could not open default font 'fixed'". + What does that mean ? + A: + + This means one or more components in the font path (set via the option + "-fp") are either... + * ... not valid + * ... contain fonts not supported by this Xserver (e.g. support has + not be compiled "in" (usually happens for TrueType (which are only + support for Solaris version of Xprt and xprint.mozdev.org releases + >= 008), OpenType (which are only supported by xprint.mozdev.org + releases 009 or higher) or F3 fonts (Sunsoft/F3 fonts are + Solaris-specific and not supported by other vendors (AFAIK)) when + support for these fonts was not enabled at build time)) + * ... no font or font alias in the font path matches the name + "fixed" + * ... an entry in fonts.dir or fonts.alias with the name "fixed" + which references a non-existing or non-readable file + + Q: + + Just copying my fonts into a directory and adding the path to my Xprt + command line didn't work - I always get "Fatal server error: could not + open default font 'fixed'". What am I doing wrong ? + A: + + Every Xserver needs an index file called fonts.dir to tell it which + fonts are available in this directory and which properties these fonts + have. + + If you are lucky there may be already a fonts.scale file which can be + used by "mkfontdir" to create the fonts.dir file. If there is no + fonts.scale then you have to create your own fonts.dir/fonts.scale + either by hand or via tools like "mkfontscale" (works for all types of + scaleable fonts), "type1inst" (for PS Type1 fonts; see + [246]http://packages.debian.org/stable/utils/type1inst.html) or + "ttmkfdir" (for TrueType fonts; see + [247]http://packages.debian.org/stable/x11/ttmkfdir.html). + Q: + + Xprt refuses to start with the message "Fatal server error: Cannot + establish any listening sockets - Make sure an X server isn't already + running". What does that mean ? + A: + + There is already a Xserver running at the display ID you have + specified to start Xprt (for example your framebuffer Xserver runs at + ":0" then Xprt can't run at the same display display). + Q: + + Xprt refuses to start with the message "Fatal server error: Failed to + establish all listening sockets". What does that mean ? + A: + + This means that the Xserver could not open one of it's sockets. Check + the permission of /tmp/.X11-pipe and /tmp/.X11-unix (on Solaris a + 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 always with + <hostname>:<displaynum> (see Xserver(1x) manual page for the + side-effects of this option). + Q: + + Xprt refuses to start with the message "Fatal server error: could not + open default font 'fixed'" or "Fatal server error: could not open + default cursor font 'cursor'". + A: + + All Xservers at least two fonts as the minimum: One fixed-width font + ("fixed") and one font for the cursor ("cursor"). Be sure that the + font path contains these fonts. + Q: + + Xprt refuses to start with the message "Fatal server error: no screens + found". What does that mean ? + A: + + Cause: This means that Xprt could not find any printers. Either there + are no printers installed, "lpstat"/"lpc" could not find any printers + or the configuration does not contain any manual printer + configurations (see Q/A item "Which program is used by default by Xprt + to enumerate the printers on my system" for further details...). + + Solution: Two solutions: + 1. Using "PSspooldir" model: . Xprt releases from + [248]http://xprint.mozdev.org/ provide the "PSspooldir" model + config for such cases. Just edit the "Xprinters" file and add this + line: +Printer xp_ps_spooldir_tmp_Xprintjobs + this will add the pre-configured (see + ${XPCONFIGDIR}/C/print/attributes/printer) + "xp_ps_spooldir_tmp_Xprintjobs" printer which will send jobs to + the directory "/tmp/Xprintjobs/" instead to a printer queue. (This + feature was added in the xprint.mozdev.org release 007, see + [249]xprint.mozdev.org bug 2475 ("RFE: Need model-config which + spools print jobs in a predefined directory").) + 2. Manual setup (task list): . + + 1. Provide a simple "Xprinters" spec file which contains a dummy + queue. Example: +# Create "Xprinters_onlydummy" file which turns autolookup of printers +# OFF (using "Augment_Printer_List %none%") and provides one dummy +# queue called "ps_myscript" instead (using "Printer ps_myscript") +% echo "Augment_Printer_List %none%" >Xprinters_onlydummy +% echo "Printer ps_myscript" >>Xprinters_onlydummy + 2. Edit ${XPCONFIGDIR}/C/print/attributes/printer and add these + two lines: +ps_myscript.xp-model-identifier: PSdefault +ps_myscript.xp-spooler-command: /home/sanja/xprint_test/my_xprt_cat_script.sh + This means that the printer "ps_myscript" now uses the + "PSdefault" printer model and it will feed the jobs to the + script "/home/sanja/xprint_test/my_xprt_cat_script.sh" (via + stdin). Note that the absolute path is required for + "*xp-spooler-command". + 3. Start Xprt on display 18, passing the "Xprinters_onlydummy" + using the "-XpFile" option: +% Xprt -XpFile ./Xprinters_onlydummy -pn -ac -audit 4 :18 + + Q: + + "Printing itself works but the printout covers only 1/4 of the paper - + what am I doing wrong ?" + A: + + This is usually an indicator for a wrong DPI setting. The default + "PSdefault" model config uses 300 DPI but some printers only support + 600 DPI. + + Workaround: Edit ${XPCONFIGDIR}/C/print/attributes/document and + replace the line "*default-printer-resolution: 300" with + "*default-printer-resolution: 600" (Note that locale-specific settings + in ${XPCONFIGDIR}/${LANG}/print/attributes/document always override + values set in ${XPCONFIGDIR}/C/print/attributes/document.) + + Solution: Create a model-config for your printer which only contains + attributes supported by your printer ("printer-resolutions-supported" + is the attribute in the "model-config" which holds the space-seperated + list of DPI values which are supported by the printer). + Q: + + "Printing works but I get large borders/margins..." / "[Top] margin is + too small" / "Margins are wrong" / etc. + A: + + Two possible causes: + * Usually same issue as "Printing itself works but the printout + covers only 1/4 of the page"-issue: Wrong DPI. Solution: Check the + DPI value and adjust it as described in the FAQ item above. Common + DPI values for the PostScript DDX are 240, 300, 360, 400 and 600 + DPI. + * You are trying to print "US-letter" on a "DIN-A4" paper or + "DIN-A4" on "US-letter". + Solution: Check your paper settings + Note that the default papersize for Xprt depends on the locale + (e.g. on the env var ${LANG}) Xprt is running in - "en_US"&co. get + US-letter, all others use DIN-A4 (incl. german/austrian etc. + locales)). Exception from this rule: If the selected printer does + not support the default paper size it will set no default paper + size for this printer (then the application side has to make an + explicit choice). + + Q: + + Xprt prints a warning like "Xp Extension: could not find config dir + /usr/X11R6/lib/X11/C/print" - what does that mean ? + A: + + This is actually the worst case what can happen. The message indicates + that Xprt was unable to find it's configuration data. + + Solution: Two solutions are possible: + * Install the configuration data at the requested location + (/usr/X11R6/lib/X11/C/print/ in this example) + * Set the ${XPCONFIGDIR} env var to the location of the Xprt + configuration directory. + + Q: + + Xprt crashes with "Fatal server error: Beziers this big not yet + supported" What does that mean ? + A: + + This is a known issue in the X11R6.5.1 code. In rare cases some + PostScript Type1 fonts can trigger this. See "My PS Type1 font does + not work with my Xserver" ... + Q: + + "My PS Type1 font does not work with my Xserver - how can I fix this + ?" + A: + + Some PS Type1 do not work out-of-the-box with all PS Type1 font + engines - some will work with the Adobe font engine (used in Solaris + Xsun) but not with the X.org font engine (or the other way round) or + the fonts are simply broken. The following procedure will try to fix + this problem: Get the "type1fix" perl script the TeXTrace package + ([250]http://www.inf.bme.hu/~pts/textrace-latest.tar.gz) and run it + over the fonts. Example 1 (filter fonts): +# Broken PFA fonts are in broken_fonts/ +% mkdir fixed_fonts ; cd fixed_fonts +% for i in ../broken_fonts/*.pfa ; do + echo " ------- $i" ; + type1fix.pl --ofmt=pfa --infile=$i --outfile=$(basename ${i}) ; + done + + Example 2 (filter fonts and convert them to PFB on-the-fly; do not + forget to update fonts.scale and run "mkfontdir" (to update fonts.dir) + ; systems which use the Adobe font engine (like Solaris/Xsun) may + require to run "makepsres", too): +# Broken PFA fonts are in broken_fonts/ +% mkdir fixed_fonts ; cd fixed_fonts +% for i in ../broken_fonts/*.pfa ; do + echo " ------- $i" ; + type1fix.pl --ofmt=pfb --infile=$i --outfile=$(basename ${i%.pfa}.pfb) ; + done + + Q: + + I can't get it working. I have set ${DISPLAY} correctly to point to + the Xprt display and... ... What is going wrong ? + A: + + Do not set ${DISPLAY} to the Xprt server. You still need your normal + Xserver for your video card - Xprt is only for your printer(s). + Applications look up Xprt servers via the ${XPSERVERLIST} env var, NOT + via the ${DISPLAY} env var. + Q: + + When I try to print via Xprint I get the message "Fatal server error: + unable to exec '/usr/bin/lp'". What is going wrong here ? + A: + + This usually means that the spooler application "/usr/bin/lp" could + not be launched. This is usually the result when /usr/bin/lp does not + exist or cannot be executed (for example, shell scripts without the +x + (executable) flag etc.). + Q: + + The Solaris Xprt prints some error messages about PostScript fonts + like "FOOBAR not found, using Courier. CMEX0123 not found, using + Courier." etc. and uses "Courier" instead of these fonts... + A: + + Cause: The Solaris (Adobe-based) PostScript font engine requires a + "PostScript resource database" file named "PSres.upr" to use the + PostScript fonts correctly. + + Solution: Create the missing PSres.upr database. + + Procedure 5. Steps to create the missing "PSres.upr" file (task list): + 1. Go to the location where the matching fonts are installed (we're + using /home/sanja/mathml_fonts/tex_cmps/Type1/ in this example): +% cd /home/sanja/mathml_fonts/tex_cmps/Type1// + 2. Create "PSres.upr" using the "makepsres" command. +% makepsres + 3. Validation: Make sure the file has been created: +% ls -l PSres.upr + 4. Restart Xprt server(s): +% /etc/init.d/xprint restart + 5. Restart application which uses these fonts + + References: + * makepsres(1) manual page + * [251]bugzilla.mozilla.org 120560 ("Solaris Xsun does not like + CMEX10/CMSY10 Type1 fonts") + * [252]bugzilla.mozilla.org 142718 ("Document how to get the MathML + fonts to work on Solaris") + + Q: + + "Xprt refused to start, complaining about a missing dir + (/etc/X11/xserver/C/print/ directory)... I created it by hand (empty) + and started Xprt but it still does not work properly..." + A: + + Xprt expects some config data in this directory. Just making it an + existing but empty dir will work around the error message but will not + result in a properly working Xprt since it has no (usefull) builtins + which would make it possible to run the binary without the config + data. Your X11 binary distribution should always come with the config + data (for example /usr/openwin/server/etc/XpConfig/ on Solaris) or you + will not be able to use Xprint (however it is possible to copy the + config data from another system :) BTW: Source for the configs can be + found under xc/programs/Xserver/XpConfig/ + Q: + + My Linux system already shipps with a '/usr/X11R6/bin/Xprt'-binary. Do + I need the binary distribution from [253]http://xprint.mozdev.org/ ? + A: + + This depends on what is shipped with your Linux distribution. Please + check the "vendor" string of the Xprt server: +% Xprt :10 & +% xdpyinfo -display :10 | grep -i "vendor string" + + If this outputs a line like "vendor string: The XFree86 Project, Inc" + then you have the Xprt binary build from Xfree86 sources - which are + broken - even the newest version [I'll update this as soon as Xfree86 + shipps with a working version]. Xprt from Solaris, HP-UX and my own + builds (which identifies itself as "vendor string: xprint.mozdev.org" + for releases >= 007, older releases (e.g. <= 006) identify itself as + as "vendor string: The X.Org Group") are known to work proprtly. + Q: + + I am getting the error message "error opening security policy file + /usr/X11R6/lib/X11/xserver/SecurityPolicy". What does that mean ? + A: + + The policy file for the SECURITY extension cannot be found. This is + not serious unless you want to make use of features of the SECURITY + extensions (like treating clients as "untrusted", e.g. restrict their + access to certain Xserver resources). Normally the missing policy file + is a problem with your Unix/Linux X11 distribution; consult your + vendor where to get the missing file from. Alternatively you can get + the plain X11R6.6 security policy file from + [254]ftp://ftp.x.org/pub/R6.6/xc/programs/Xserver/Xext/SecurityPolicy + (copy it to the matching location - but be sure that you do not + overwrite any existing security policy file). + Q: + + I have modified the "HPLJ4family" [or "HPDJ1600C" etc.] printer model + to work with my PostScript printer, but when I print I get empty + places where some text should be - what am I doing wrong here ? + A: + + The "HPLJ4family" and "HPDJ1600C" models are PCL-only, check the + model-config spec + (${XPCONFIGDIR}/C/print/models/${MODEL_NAME}/model-config) - if the + "xp-ddx-identifier" attribute says something with "PCL" (like + "XP-PCL-MONO" etc.) in the value string then this model-config is for + the PCL-DDX only (e.g. their PMF fonts do not supply the neccesary + information (e.g. the "_ADOBE_POSTSCRIPT_FONTNAME" chunk is missing; + they only provide the "PCL_FONT_NAME" chunk) nor are these fonts + accessible via the PostScript-support in these printers. A solution is + to use the "PSdefault" model instead (and/or create your customized + own version of this model) - or look if there is a model-config + beginning with the same name and ending with "PS" (e.g. + "HPLJ4family-PS"). + Q: + + Xprt outputs warning messages like: + +Xp Extension: Can't load driver XP-PCL-MONO + init function missing +Xp Extension: Can't load driver XP-RASTER + init function missing + + What does that mean ? + A: + + Two possible problems: + 1. The requested driver is not supported by that version of Xprt. For + example Solaris 2.7 Xprt does not support XP-PCL-MONO nor the + XP-RASTER driver. Valid values for the "xp-ddx-identifier" + attribute in ${XPCONFIGDIR}/*/print/attributes/printers and/or + ${XPCONFIGDIR}/*/print/models/*/model-config are + + Solaris 2.7: XP-POSTSCRIPT and XP-PCL-COLOR + + Solaris >=2.8: XP-POSTSCRIPT, XP-PCL-COLOR, XP-PCL-MONO and + XP-RASTER + + HP-UX: XP-POSTSCRIPT, XP-PCL-COLOR, XP-PCL-MONO, XP-PCL-LJ3, + XP-PCL-DJ1200 and XP-RASTER + + xprint.mozdev.org release 007: XP-POSTSCRIPT and XP-RASTER + + xprint.mozdev.org release 008: XP-POSTSCRIPT, XP-PCL-COLOR, + XP-PCL-MONO, XP-PCL-LJ3 and XP-RASTER + + xprint.mozdev.org release >=2.0 (planned): XP-POSTSCRIPT, + XP-PCL-COLOR, XP-PCL-MONO, XP-PCL-LJ3, XP-RASTER, XP-PDF and + XP-SVGPRINT. + 2. There may be too many drivers loaded into one Xprt instance. By + default a single Xserver instance can only handle three screens - + and since one Xprint DDX maps to one Xserver screen this limit + applies to the number of loaded Xprt drivers, too. Starting with + xprint.mozdev.org release 008 the per-Xserver screen limit was + increased from "3" to "8" to avoid this issue... Workaround: Start + a 2nd instance of Xprt which handles the other drivers which do + not fit into the first instance. + + Q: + + Printing on Solaris with Mozilla/Eclipse [or any other Xprint client] + removes spaces between words. What is going wrong ? + A: + + Cause: This is a bug in the Solaris Xprint server binary + (/usr/openwin/bin/Xprt). Various bug reports have been filed, see + * [255]xprint.mozdev.org bug 3353 ("Solaris Xprt looses space when + rendering with '-monotype-arial-*'-fonts") + * [256]bugzilla.mozilla.org bug 199957 ("Solaris 8 Mozilla removes + spaces for text within <font face="Arial">...</font>") + + Solution: Solution: Please apply the following OS patches from + [257]http://sunsolve.sun.com/: + + Table 1. Solaris patches to fix [258]xprint.mozdev.org bug 3353 + ("Solaris Xprt looses space when rendering with + '-monotype-arial-*'-fonts") + Solaris 2.7 Solaris 2.8 Solaris 2.9 + SPARC x86 SPARC x86 SPARC x86 + [259]n/a [260]n/a [261]108652-73 [262]108653-62 [263]112785-21 + [264]112786-11 + +Note + + For Solaris 2.7 (both SPARC and x86 platforms) there are currently + [265]no patches available... ;-( + + Known workarounds: + * Remove the '-monotype-arial-*' fonts from the font path + * Use an alternate Xprint server like available in the "GISWxprint" + package (this package is identical to the "GISWxprintglue" package + except that it uses a Xprint server build from xprint.mozdev.org + sources and not the /usr/openwin/bin/Xprt binary from Solaris) + * Mozilla-only: Adding + user_pref("print.xprint.font.rejectfontpattern", + "fname=-dt-.*;scalable=.*;outline_scaled=false;xdisplay=.*;xdpy=.*;ydpy=.*;xd +evice=.*|" + + "fname=-monotype-arial.*;scalable=.*;outline_scaled=.*;xdisplay=.*;xdpy=.*;yd +py=.*;xdevice=.*"); + to prefs.js works around the problem (see + [266]bugzilla.mozilla.org bug 199957 comment #6, too). + +Note + Note that this workaround may render various locales completly + inaccessible for printing since many of them only employ MonoType + fonts. + + Q: + + Installation of the "GISWxprint" / "GISWxprintglue" packages fails + like this: +# pkgadd -d /space/staging/xprint/GISWxprint.pkg +pkgadd: ERROR: no packages were found in </var/tmp/dstreAAA5Jayyz> + + Any idea what I am doing wrong ? + A: + + The target machine misses a patch to cure SunSolve bug 4025718 + ("pkginfo: allow greater than nine characters for PKG parameter + value"). Please apply the patches listed in the "Installation + Requirements" section in the README for the [267]GISWxprint / + [268]GISWxprintglue package. + Q: + + Printing page results in [two/three/.../16] leading blank pages, + followed by a correct (but offset) page. Any idea what is going wrong + ? + A: + + This symptom depends on the CUPS GhostScript driver used, however the + exact cause is currently unknown (see comments in [269]SuSE support + database entry SDB-2002/11/jsmeix_print-81-cups-formfeed ("Blank Pages + When Printing with CUPS")). + + Solution: Disable the CUPS accounting functionality in the cupsomatic + filter by changing the line + my $ps_accounting = 1; + + to + my $ps_accounting = 0; + + in the filter script /usr/lib/cups/filter/cupsomatic as the user root. + If you use /etc/foomatic/filter.conf, disable ps_accounting there. + + References: + * [270]SuSE support database entry + SDB-2002/11/jsmeix_print-81-cups-formfeed ("Blank Pages When + Printing with CUPS") + * [271]xprint.mozdev.org bug 4181 ("Two empty pages printed first") + * [272]bugzilla.mozilla.org bug 180602 comment #7 ("Printing page + results in 16 leading blank pages, followed by a correct, but + offset, page") + +5. Software development + + Q: [273]How does the X print server (Xprt) and the Xlib client side + differ from the "normal" video Xserver/video client side ? + + Q: [274]How can I get the printable area (e.g. the portion of the page + on which the printer is physically capable of placing ink) of + the paper after I have chosen a paper ? + + Q: [275]Do "offscreen" pixmaps work on Xprt ? + Q: [276]How can I get the DPI value for the current Xprt server ? Can + I use the values from "xdpyinfo" ? + + Q: [277]Why does Xprt not offer the MIT-SHM protocol extension ? + Q: [278]Does Xprint/Xprt support font rotation ? + Q: [279]When I render something on my window and call XpStartPage all + the rendered stuff is gone, I only get a white, empty paper. + What is going wrong here ? + + Q: [280]What is XpStartDoc for ? + Q: [281]How does the XLFD for printer-builtin fonts look like ? / How + can I find/identify printer-builtin fonts ? + + Q: [282]How can I scale images using the Xprint API ? + Q: [283]Can I pass my own PostScript code (fragment) to the print + spooler instead of letting Xprt's PostScript DDX generate it ? + + Q: [284]When I use XpPutDocumentData I get a BadValue X protocol + error. Any idea what am I doing wrong ? + + Q: [285]How do I use the XprintUtil library ? + Q: [286]Why does the XGetImage not work for Xprt ? + Q: [287]How to print with Xt/Athena widgets ? + Q: [288]How to print with Xt/Motif widgets ? + Q: [289]What are the differences between normal display and Xprint + display ? + + Q: [290]How do I scale images ? + Q: [291]libXp Image scaling vs. max. request size ? + Q: [292]How can I use XprintUtils ? + Q: [293]How do I calculate the DPI values for Xprt DDX screens ? + Q: [294]How do I find scaleable fonts ? + Q: [295]How do I find printer-builtin fonts ? + Q: [296]The XLFD for Printer-builtin fonts look like bitmap fonts - is + that bad ? + + Q: [297]When printing using the XawPrintShell/XmPrintShell print + shells my PostScript output is always corrupt. What am I doing + wrong ? + + Q: [298]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" ? + + Q: [299]Are there any caveats/suggestions when printing via Xt/Motif2 + widgets ? + + Q: [300]Can I change the paper size/resolution/page orientation/etc. + when printing using the XawPrintShell/XmPrintShell print shells + ? + + Q: + + How does the X print server (Xprt) and the Xlib client side differ + from the "normal" video Xserver/video client side ? + A: + + The X Print Service expands on the traditional X-Server and Xlib world + in the following ways: + 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 ([301]PDL)" output (such as PCL, PDF, PostScript, + SVGprint, etc.) or sends the print rendering instructions to a + platform-specific print API (like Win32/GDI). + Once a print ddx driver generates [302]PDL output, it can be sent + to a spooler (using XpuStartJobToSpooler) or retrieved by the + client (to implement functionality like "print-to-file" with + functions such as XpuStartJobToFile). + 2. Since printers support "paged" output, unlike video, a portion of + the Xp Extension supports APIs to delineate printed output into a + print job. + A "print job" in Xprint consists of one or more "documents" which + itself consists of one or more "pages". + A client starts a job sequence with XpStartJob and ends it with + XpEndJob or XpCancelJob to cancel the generation of the current + print job. Any document-specific print attributes MUST be changed + before XpStartJob. + A client starts a document sequence with XpStartDoc and ends it + with XpEndDoc or XpCancelDoc to cancel the generation of the + current document. Any document-specific print attributes MUST be + changed before XpStartDoc or after XpEndDoc (to affect the + following document). + A client starts a page sequence with XpStartPage and ends it with + XpEndPage or XpCancelPage to cancel the generation of the current + page. Any page-specific print attributes MUST be changed before + XpStartDoc or after XpEndDoc (to affect the following document). + 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). + 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. + 5. 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 + rendering calls use the resolution of the current page (or if not + given, the resolution of the current document or the current + resolution for this print job). The screen's resolution is INVALID + in this case. XprintUtils has the functions XpuGetResolution (to + get the current print resolution (searching page, document and job + level attributes (in that order)), XpuSetPageResolution (to set + the current page resolution), XpuSetDocResolution (to set the + current document resolution), XpuGetResolutionList (to get the + list of all resolutions supported by this printer) and + XpuFindResolution (to find a resolution in the list returned by + XpuGetResolutionList) to support getting/setting/queries of + resolutions. + When a print context is created and set for a given printer, the X + image rendering calls (such as XPutImage support scaling of + images. The Xp Extension API provides the functions + XpSetImageResolution and XpSetImageResolution to set and get an + image resolution. The scaling factor for an image printed on the + paper can simply calculated via scaling_factor = + curr_print_resolution_resolution / image_resolution where + curr_print_resolution_resolution is the value returned by a + function such as XpuGetResolution, image_resolution the resolution + passed to XpSetImageResolution and scaling_factor the resulting + scaling factor. Note that XpSetImageResolution will failure + (=FALSE) when the print DDX (for example the RASTER DDX) does not + support scaling. In that case the application has to scale the + image manually. + + Q: + + How can I get the printable area (e.g. the portion of the page on + which the printer is physically capable of placing ink) of the paper + after I have chosen a paper ? + A: + + The XpGetPageDimensions function returns the printable area and other + information about the current page geometry. Note that the page + geometry changes when the page attributes such as content-orientation + or default-medium are changed by the application. + Q: + + Do "offscreen" pixmaps work on Xprt ? + A: + + Yes, "offscreen" pixmaps are working on Xprt. + Q: + + How can I get the DPI value for the current Xprt server ? Can I use + the values from "xdpyinfo" ? + A: + + The Xprt screen resolution defines only the maximum resolution + configured for the matching DDX, the printers real DPI is obtained via + an another API (XprintUtil has a bunch of functions to get/set the + document/page resolution, see XpuGetResolutionList, + XpuFreeResolutionList, XpuGetResolution, XpuSetPageResolution, + XpuSetDocResolution and XpuFindResolution). + Q: + + Why does Xprt not offer the MIT-SHM protocol extension ? + A: + + The MIT-SHM protocol extension is partially (XShmPutImage would work, + but others like XShmGetImage and esp. XShmCreatePixmap cannot be + implemented properly) incompatible to the way how some of the Xprint + DDX are implemented. For example the PostScript, PDF, PCL and SVGprint + DDX do not rasterize any images on their side - instead they convert + the stream of X11 rendering instructions into the matching [303]PDL + instruction stream. Only the printer side will (finally) do the + rasterisation of the output image. This is the basically the same + reason why [304]XGetImage does not work for those DDXs - and functions + such as XShmCreatePixmap would be useless since drawing operations on + the shared pixmap would not be applied to the application (e.g. Xprint + client) as well. + Q: + + Does Xprint/Xprt support font rotation ? + A: + + Yes - Xprint/Xprt supports font rotation at any angle via the matrix + XLFD enhancement (this even works for printer-builtin fonts !!). For + details see the paper "New Font Technology for X11R6" by Nathan Meyers + (a copy can be found in the Xprint.org source tree under + xc/doc/hardcopy/XLFD/x11r6_fonts_94_paper.PS.gz) + + Short: The transformation-matrix for rotation can be calculated like + this: ++-- --+ +| cos(angle) sin(angle)| +| | +|-sin(angle) cos(angle)| ++-- --+ + + Examples: + 1. the following code fragment obtains a 180 degree rotated font + (matrix [-1 0 0 -1]): + ... = XLoadQueryFont(..., "-adobe-courier-bold-r-normal--*-[~24 0 0 ~24]-0-0- +m-*-iso8859-1"); + 2. the following code fragment obtains a 90 degree rotated font + (matrix [0 1 -1 0]): + ... = XLoadQueryFont(..., "-adobe-courier-bold-r-normal--*-[0 24 ~24 0]-0-0-m +-*-iso8859-1"); + + Future versions of Xprint will support the [305]STSF font API which + supports matrix transformations as well. + Q: + + When I render something on my window and call XpStartPage all the + rendered stuff is gone, I only get a white, empty paper. What is going + wrong here ? + A: + + Remember the rule that "only those drawings are printed on the paper + which were rendered between XpStartPage and XpEndPage". XpStartPage + clears the window you passed as argument, e.g. it creates a new, blank + sheet of paper where you can do your rendering stuff on. XpEndpage + then pushes the "paper sheet" to the stash of papers from the document + in process. + +Tip + + If you want to render something once for multiple or all pages: Render + on a offscreen pixmap and copy (with XCopyArea) the content to the + "paper" drawable (after calling XpStartPage) - XpStartpage only + affects the window passed as parameter. + + Q: + + What is XpStartDoc for ? + A: + + ISO 10175 and some advanced printing systems by IBM and HP had set + forth the standard that a "Job" is made up of one or more "Documents", + and each document is made up of one or more "Pages". Xprint was + designed that in a true ISO 10175 environment/implementation (lp(1) on + steroids, and with an API), Xprt can actually learn about all printers + and their capabilities though API's into the printer subsystem (vs. + using config files), map Job/Doc/Page directly into ISO 10175 + equivalents, and use APIs to view job status and kill jobs (vs. + cancel(1), lpcancel(1), lpstatus(1)). Because most applications of the + day are only printing one document per job, XpStartPage was designed + that it generates a "synthetic" XpStartDoc if it has not been called + yet. + Q: + + How does the XLFD for printer-builtin fonts look like ? / How can I + find/identify printer-builtin fonts ? + A: + + There is no special XLFD scheme for printer-builtin fonts. Instead the + xp-listfonts-modes-supported is used to define whether XListFonts and + co. return printer-builtin fonts or not. By default the attribute + looks is set to *xp-listfonts-modes-supported: + xp-list-internal-printer-fonts xp-list-glyph-fonts which defines thaht + XListFonts and co. return both printer-builtin and normal fonts. + Removing xp-list-internal-printer-fonts will make printer-builtin + fonts disappear, removing xp-list-glyph-fonts will make normal glyph + fonts disappear from font lists. + Q: + + How can I scale images using the Xprint API ? + A: + + XXX + Q: + + Can I pass my own PostScript code (fragment) to the print spooler + instead of letting Xprt's PostScript DDX generate it ? + A: + + XXX + Q: + + When I use XpPutDocumentData I get a BadValue X protocol error. Any + idea what am I doing wrong ? + A: + + XXX + Q: + + How do I use the XprintUtil library ? + A: + + XXX + Q: + + Why does the XGetImage not work for Xprt ? + A: + + There are at least three reasons why XGetImage does not work for Xprt: + 1. Most of the Xprt DDX implementations do not render itself on any + bitmaps like the framebuffer(=video) DDX do, they translate the + rendering commands into the matching commands of the printer + language (it is technically possible to implement such support for + XGetImage even for those drivers - but there are more reasons:) + 2. Xprt usually operates at high resolutions which results in very + large dimensions. If a client would request the 24bit TrueColor + bitmap data for a whole DIN-A4 page at 2400 DPI a data chunk of + ~173 megabytes would be the response. This would be more or less a + DOS(=Denial of Service) for either the client, the network and/or + the server. + 3. The printer-builtin fonts only provide metrics information - there + is no real "outline" information at that time (these fonts reside + only in the printer's ROM and are only available at the time the + printer rasterizes the incoming [306]PDL (e.g. PCL/PostScript) + data stream) which could be used to rasterize the matching glyphs + (which means: A XGetImage implementation would return image data + but glyphs rendered using the printer-builtin fonts would be + missing). + + Q: + + How to print with Xt/Athena widgets ? + A: + + There are two examples in the Xprint.org source tree 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 + widget class. + 2. xc/programs/xphelloworld/xpxthelloworld/ contains a simple demo + application which prints a Athena widget without using a special + print widget class (however, if possible a print shell such as + XawPrintShell or XmPrintShell should be used since this is the + easier way to add print support to an Athena application). + + Q: + + How to print with Xt/Motif widgets ? + A: + + The Xprint.org source tree contains the xpxmhelloworld + (xc/programs/xphelloworld/xpxmhelloworld/) application to demonstrate + how to print using the Motif2 toolkit. + Q: + + What are the differences between normal display and Xprint display ? + A: + + XXX + Q: + + How do I scale images ? + A: + + XXX + Q: + + libXp Image scaling vs. max. request size ? + A: + + XXX + Q: + + How can I use XprintUtils ? + A: + + XXX + Q: + + How do I calculate the DPI values for Xprt DDX screens ? + A: + + XXX + Q: + + How do I find scaleable fonts ? + A: + + XXX + Q: + + How do I find printer-builtin fonts ? + A: + + XXX + Q: + + The XLFD for Printer-builtin fonts look like bitmap fonts - is that + bad ? + A: + + No, this is not "bad". The XLFD of a printer-builtin font only looks + like a bitmap font since the *.pmf (Printer metrics file) format is a + PCF file format variant (the DPI values in the XLFD 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). + Q: + + When printing using the XawPrintShell/XmPrintShell print shells my + PostScript output is always corrupt. What am I doing wrong ? + A: + + Make sure the widgets (such as text input widgets) have the (blinking) + cursor turned-off. Setting the XmNcursorPositionVisible, to False + usually solves the problem (for Motif2 widgets). Example: +... +XtSetArg(args[n], XmNcursorPositionVisible, False); +... + + Q: + + 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: + + XXX + Q: + + Are there any caveats/suggestions when printing via Xt/Motif2 widgets + ? + A: + + There are a couple of Xt resources which may likely differ from the + normal values (e.g. those values used for a video Xserver): + + Core class level + + XmNbackground resource + The application will probably want to set the + XmNbackground resource to "white" to match the default + paper color. + + XmNborderWidth resource + The application will probably want to set the + XmNborderWidth resource to "0" (usually the default + value) to avoid that a black border appears around the + widget. + + XmPrimitive class + + XmNshadowThickness and XmNhightlightThickness resources + The application will probably want to set + XmNshadowThickness and XmNhightlightThickness to "0" + (usually the default value) to avoid 3D border effects on + the printout (depends on application and author's + preference... :-)). + + XmText and XmTextField classes + + XmNcursorPositionVisible resource + The application will probably want to set + XmNcursorPositionVisible to False to avoid that the + cursor is visible on printouts (and to avoid problems + with some nasty implementation details which may cause + corrupted PostScript output). + + XmNscrollHorizontal and XmNscrollVertical resources + The application will probably want to set the + XmNscrollHorizontal and XmNscrollVertical resources to + False to suppress printing of scrollbars (on paper + "scrolling" is replaced with "pagination" except for rare + exceptions (like 1:1 WYSIWYG-printing)). + + XmNmarginWidth and XmNmarginHeight resources + The application will probably want to recalculate the + XmNmarginWidth and XmNmarginHeight resources based on the + (far) higher print resolution (or reverse: set them to + "0" - depending on what style matches the application + needs better...). + + XmLabel class + + XmNmarginTop, XmNmarginBottom, XmNmarginRight, XmNmarginLeft, + XmNmarginWidth, XmNmarginHeight and XmNalignment + resources + The application will probably want to use different value + for XmLabel class's XmNmarginTop, XmNmarginBottom, + XmNmarginRight, XmNmarginLeft, XmNmarginWidth, + XmNmarginHeight and XmNalignment resources. These + resources are mainly usefull when the widget holds a + border, highlight or shadow of some kind. If borders are + not to be transferred there is no real need to transfer a + margin either. + + Q: + + Can I change the paper size/resolution/page orientation/etc. when + printing using the XawPrintShell/XmPrintShell print shells ? + A: + + Yes, it is allowed to change the page attributes in the page setup + callback (e.g. XawNpageSetupCallback or XmNpageSetupCallback) since + this callback is always called before XpStartPage (for the 2nd and + following pages: between XpEndPage and XpStartPage). Note that + changing page attributes will automagically update the print shell + widget size (e.g. attributes XawNminX, XawNminY, XawNmaxX and XawNmaxX + (XawPrintShell) or XmNminX, XmNminY, XmNmaxX and XmNmaxX + (XmPrintShell) are updated based on events send by the Xp Extension + and then the print shell is resized based on the new values + (XawPrintShell is slightly more flexible since the size mode can be + defined using the XawNlayoutMode attribute)). + +Known bugs + + Problem [307]Xprt build from Xfree86 sources is completely broken + and unuseable. + + Problem [308]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. + + Problem [309]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". + + Problem [310]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). + + Problem [311]Xprt build from Xfree86 sources is completely broken and + unuseable. + + Problem [312]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. + + Problem [313]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". + + Problem [314]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). + + Problem + + Xprt build from Xfree86 sources is completely broken and unuseable. + Solution + + Build Xprt from the CVS tree at [315]http://xprint.mozdev.org/ or the + X.org X11R6.5.1 sources (note that the client side Xprint extension + library ("libXp.so") from Xfree86 is not broken and do not need to be + replaced). + Problem + + 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. + Solution + + Patch available, I am looking for a way to get the patch into the X11 + and Solaris source trees... + Problem + + 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". + Solution + + Either convert PFB (PS Type 1 binary font) to PFA format and adjust + the fonts.dir and fonts.scale file or get a patch for the sources. 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). + Problem + + 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). + Solution + + Xprt build from xprint.mozdev.org sources has been fixed in release + 007, see [316]xprint.mozdev.org bug 1378 ("PS DDX creates n^2 copies + of a job instead of n copies") and [317]bugzilla.mozilla.org 140030 + ("Setting number of copies causes too many copies to print") for + details. Solaris 2.7 Xprt still suffers from this issue... ;-( + +Unanswered questions + + (My small ToDo list what I will write soon; 379 items missing... =:-) + Email me if you want one of these answered "now" and/or to contribute + an answer... :) + How do I create a model-config for my printer ? + How can I customize a model-config for my site/machine ? + Which attributes/values can be set in a model-config ? + Why can't I set default values (for my {paper size, resolution, ...}) + in the model-config ? + Should I add the fonts in the model-config dir to the Xserver's font + path ? + What are the fonts in the model-config dir for ? + Can I use a font server for all fonts instead of passing then directly + to the Xprint server ? + Does the Xprint PostScript driver do full rasterisation of the print + job ? + Is it possible to prepare a printer config entry so that the PS output + is piped to "ps2pdf" and will produce directly a PDF file? It would be + nice to have mozilla directly producing PDF files when printing. + Problem: I have changed the Xprt config - but "xplsprinters -l" + (or any other Xprint application) does not show the change. + Any idea what I am doing wrong ? + How can I add a font path to Xprt ? + Why does "xset +fp path_to_font" not work in some cases ? + How can I get a "core"-dump when Xprt crashes ? + How can I debug Xprt (hint: use "-audit 4") ? + How can I debug Xprt with Sun Workshop (hint: "check -access") ? + How can I check whether Xprint is "active" ? / How can I verify that a + Xprint is working ? + +Acknowledgements + + We'd like like to express their gratitude to the whole community for + providing insightful answers to innumerable questions. In particular, + the following people (listed alphabetically) have contributed to this + FAQ (apologies, in advance, if anyone has been forgotten): + + Alan Coopersmith <[318]alan.coopersmith@sun.com> + Giuseppe Ghibò <[319]ghibo@mandrakesoft.com> + Thomas Gilg <[320]thomas_gilg@hp.com> + Jay Hobson <[321]jay.hobson@sun.com> + Masaki Katakai <[322]katakai@japan.sun.com> + Simon Montagu <[323]smontagu@smontagu.org> + Drew Parsons <[324]dparsons@debian.org> + (and many many others) + +References + + 1. mailto:roland.mainz@nrubsig.org + 3. http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.html + 4. http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.txt + 5. http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.xml + 144. http://xprint.mozdev.org/ + 145. http://packages.qa.debian.org/x/xprint-xprintorg.html + 146. http://xprint.mozdev.org/ + 147. http://xprint.mozdev.org/download.html + 148. http://xprint.mozdev.org/ + 149. http://xprint.mozdev.org/ + 150. http://xprint.mozdev.org/list.html + 157. http://stsf.sourceforge.net/ + 159. http://xprint.mozdev.org/bugs/show_bug.cgi?id=2261 + 160. http://xprint.mozdev.org/ + 161. http://ttf2pt1.sourceforge.net/download.html + 164. http://xprint.mozdev.org/ + 165. http://www.opengroup.org/cde/ + 166. http://www.mozilla.org/projects/xprint/ + 167. http://www.mozdev.org/ + 186. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=171174 + 187. http://xprint.mozdev.org/ + 189. http://xprint.mozdev.org/ + 192. http://xprint.mozdev.org/bugs/show_bug.cgi?id=5092 + 214. http://www.adobe.com/type/main.html + 215. http://www.adobe.com/type/eurofont.html + 216. ftp://ftp.adobe.com/pub/adobe/type/win/all/ + 218. http://xprint.mozdev.org/bugs/show_bug.cgi?id=2092 + 219. http://xprint.mozdev.org/bugs/show_bug.cgi?id=2430 + 220. http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi?product=xprint&component=Server%3A%2BConfig%3A%2Bmodel-configs + 221. http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi + 246. http://packages.debian.org/stable/utils/type1inst.html + 247. http://packages.debian.org/stable/x11/ttmkfdir.html + 248. http://xprint.mozdev.org/ + 249. http://xprint.mozdev.org/bugs/show_bug.cgi?id=2475 + 250. http://www.inf.bme.hu/~pts/textrace-latest.tar.gz + 251. http://bugzilla.mozilla.org/show_bug.cgi?id=120560 + 252. http://bugzilla.mozilla.org/show_bug.cgi?id=142718 + 253. http://xprint.mozdev.org/ + 254. ftp://ftp.x.org/pub/R6.6/xc/programs/Xserver/Xext/SecurityPolicy + 255. http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353 + 256. http://bugzilla.mozilla.org/show_bug.cgi?id=199957 + 257. http://sunsolve.sun.com/ + 258. http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353 + 261. http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=108652&collection=fpatches + 262. http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=108653&collection=fpatches + 263. http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=112785&collection=fpatches + 264. http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=112786&collection=fpatches + 265. http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353#c24 + 266. http://bugzilla.mozilla.org/show_bug.cgi?id=199957#c6 + 267. http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/packager/solaris/GISWxprint/README + 268. http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/packager/solaris/GISWxprintglue/README + 269. http://sdb.suse.de/en/sdb/html/jsmeix_print-81-cups-formfeed.html + 270. http://sdb.suse.de/en/sdb/html/jsmeix_print-81-cups-formfeed.html + 271. http://xprint.mozdev.org/bugs/show_bug.cgi?id=4181 + 272. http://bugzilla.mozilla.org/show_bug.cgi?id=180602#c7 + 305. http://stsf.sourceforge.net/ + 315. http://xprint.mozdev.org/ + 316. http://xprint.mozdev.org/bugs/show_bug.cgi?id=1378 + 317. http://bugzilla.mozilla.org/show_bug.cgi?id=140030 + 318. mailto:alan.coopersmith@sun.com + 319. mailto:ghibo@mandrakesoft.com + 320. mailto:thomas_gilg@hp.com + 321. mailto:jay.hobson@sun.com + 322. mailto:katakai@japan.sun.com + 323. mailto:smontagu@smontagu.org + 324. mailto:dparsons@debian.org diff --git a/hardcopy/XPRINT/Xprint_FAQ.xml b/hardcopy/XPRINT/Xprint_FAQ.xml new file mode 100644 index 0000000..3a66d8f --- /dev/null +++ b/hardcopy/XPRINT/Xprint_FAQ.xml @@ -0,0 +1,4698 @@ +<?xml version="1.0" encoding="iso-8859-1"?> + +<!-- DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" '/usr/share/sgml/docbook_4.2/docbookx.dtd' --> +<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd' [ + <!NOTATION URL PUBLIC "-//IETF//NOTATION Uniform Resource Locator//EN"> + <!ENTITY % local.ulink.attrib ' + HyTime CDATA #FIXED "clink" + HyNames CDATA #FIXED "linkend URL" + loctype CDATA #FIXED "URL queryloc URL"' + > + <!ENTITY % local.link.attrib ' + HyTime CDATA #FIXED "clink" + HyNames CDATA #FIXED "linkend linkend"' + > +] > +<?xml-stylesheet href="docbook.css" type="text/css"?> + +<!-- + +Convert this document to HTML using: +% xsltproc /usr/share/sgml/docbook/docbook-xsl-stylesheets-1.60.1/html/docbook.xsl Xprint_FAQ.xml >Xprint_FAQ.html + +Check for errors: +% xmllint ‐‐valid Xprint_FAQ.xml > /dev/null 2>errorlog.txt + +Mappings used in this DocBook document: +- shell environment variable (like "foobar"): <envar>foobar</envar> +- Xprint printer name (like "ps003"): + +--> + + +<article class="faq"> +<articleinfo> + <title>Xprint Frequently Asked Questions</title> +</articleinfo> + +<abstract id="about"> + <title>About this FAQ</title> + <para> + Archive-name: Xprint/FAQ + </para> + <para> + Version: 0.9 + </para> + <para> + Last-Modified: 2004/02/16 04:15:16 + </para> + <para> + Maintained-by: + <othercredit><firstname>Roland</firstname> <surname>Mainz</surname></othercredit> + <email>roland.mainz@nrubsig.org</email> + </para> + + <para> + The following is a list of questions that are frequently asked about + Xprint. + </para> + <para> + You can help make it an even better-quality FAQ by writing a short + contribution or update and sending it BY EMAIL ONLY to me. + A contribution should consist of a question and an answer, and increasing + number of people sends me contributions of the form "I don't know the + answer to this, but it must be a FAQ, please answer it for me". Please + read the FAQ first (including the item "<link linkend="getting_help">Getting Help</link>") + and then feel free to ask me if it is not in the FAQ. + </para> + <para> + Thanks! + </para> + + <para> + The latest Xprint FAQ and some other goodies can be obtained through http from + <ulink url="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.html"> + http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.html + </ulink> + or + <ulink url="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.txt"> + http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.txt + </ulink> + (the DocBook/XML master source file is + <ulink url="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.xml"> + http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.xml + </ulink>). + </para> + <para> + <note> + <para> + Note that the FAQ has not been finished yet (nor is it half-finished...), + many items marked with "XXX" as the answer have still to be written (or have + to be copy&pasted from my item collection... <literal>:)</literal> + </para> + </note> + </para> +</abstract> + +<simplesect id="faq"> + <title>Frequently Asked Questions with Answers</title> + <qandaset defaultlabel="qanda"> + <qandadiv id="faq_general"> + <title>General</title> + +<qandaentry id="what_is_xprint"> + <question> + <para> + What is "Xprint" ? + </para> + </question> + <answer> + <para> + In short, "Xprint" is an advanced printing system which enables X11 + applications to use devices like printers, FAX or create documents in + formats like PostScript, PDF or SVGprint. + </para> + <para> + In long, "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 or SVGprint. + 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> + </answer> +</qandaentry> + +<qandaentry id="where_can_i_get_xprint_from"> + <question> + <para> + Where can I get Xprint/Xprt from ? + </para> + </question> + <answer> + <para> + Xprint is client-server based, therefore two answers: + <itemizedlist> + <listitem> + <para> + The server side is available by default on Solaris (see + <link linkend="where_can_i_get_xprint_from_giswxprint_package_note">Note</link> + below) and HP-UX (Xfree86 ships a "Xprt" binary, but that is broken and the server config files + are missing, too). + For those platforms who do not have a (working) Xprt server the you + can get source, binary tarballs and Linux RPMs from + <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink>, + Debian Linux has a package based on the + same sources (see + <ulink url="http://packages.qa.debian.org/x/xprint-xprintorg.html">http://packages.qa.debian.org/x/xprint-xprintorg.html</ulink>). + + <note id="where_can_i_get_xprint_from_giswxprint_package_note"> + <para> + For Solaris >= 2.7 <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink> + provides the "GISWxprintglue" + and "GISWxprint" packages (available from + <ulink url="http://xprint.mozdev.org/download.html">http://xprint.mozdev.org/download.html</ulink>) + which provides a single-step + drop-in way to configure and start Xprint at system startup and/or + per-user for all applications and users (the package provides only + startup scripts and some config data and uses the Xprt binary provided + with Solaris (<filename>/usr/openwin/bin/Xprt</filename>)). + </para> + </note> + </para> + </listitem> + <listitem> + <para> + The client-side Xprint support library (<filename>libXp.so</filename>) is available on all + X11 platforms >=R6.4, including Linux, Solaris, HP-UX, AIX, FreeBSD, NetBSD, etc. + </para> + <para> + If you do not have it you can build it from the sources available at + <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink>. + </para> + </listitem> + </itemizedlist> + </para> + </answer> +</qandaentry> + +<qandaentry id="what_is_xprt"> + <question> + <para> + What is "Xprt" ? + </para> + </question> + <answer> + <para> + Xprt is the server-side of Xprint. It's just like any other Xserver - it + uses only an other kind of output device (printer instead of framebuffer) + and implements an extra X11 extension ("XpExtension") to handle the + special features/requirements of a "paged device"(=printer etc.). + </para> + </answer> +</qandaentry> + +<qandaentry id="getting_help"> + <question> + <para> + Where can I get help for problems with Xprint ? + </para> + </question> + <answer> + <para> + The current main site for the Xprint development is <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink> + which hosts various resources including a <ulink url="http://xprint.mozdev.org/list.html">mailinglist</ulink> + (please subscribe before posting) for end-users, admin and developers. + </para> + </answer> +</qandaentry> + +<qandaentry id="advantages_of_xprint"> + <question> + <para> + "Why do some people like Xprint ?" / "What are the advantages of Xprint ?" + </para> + </question> + <answer> + <para> + <itemizedlist> + <listitem> + <para> + Xprint allows an application to query what features (paper size, trays, + orientation, resolutions, plexes, fonts and much more) a printer supports. + For example it is avoidable that a user accidently prints DIN-A4 on a + DIN-A0 poster printer (the print dialog would only offer DIN-A0 as paper + size, e.g. offers only choices which are valid for this printer). + </para> + </listitem> + <listitem> + <para> + Server-side, localizeable configuration - changes to the server + config apply to all users without the need to change/updating anything + on the user side (the user may still start his/her own Xprt instance + using his/her preferred configuration). + </para> + </listitem> + <listitem> + <para> + Small footprint - ideal for for mobile devices (client side does not + need to process any fonts - that's the job of the server side). + </para> + </listitem> + <listitem> + <para> + API not restriced to PostScript (X11R6.5.1 comes with PCL and Raster + implementations - and PDF/G3-FAX/SVG would be possible without problems). + </para> + </listitem> + <listitem> + <para> + Scaleable - Xprint can use as many Xprt servers as the user/admin wants. + </para> + </listitem> + <listitem> + <para> + "Xprint is designed for the enterprise", e.g. Xprint was designed to + match the needs of large company networks. + </para> + </listitem> + <listitem> + <para> + Automatic font handling - font download or the existence of + printer-builtin fonts is automagically handled by Xprt - the application + does not need to know/handle any details (but the application can + optionally get information and control the usage of printer builtin + fonts). + </para> + </listitem> + <listitem> + <para> + You can print anything what you can render on the framebuffer(=video + card) Xserver. + </para> + </listitem> + <listitem> + <para> + Existing code can be reused 1:1 for printing - which means reduced + development costs. + </para> + </listitem> + <listitem> + <para> + Easy support for I18N (internationalization) - you simply render any + fonts in any language with Xprint. + </para> + </listitem> + <listitem> + <para> + Network-transparent design - Client can use local or remote Xprt servers + like any other Xserver. + </para> + </listitem> + <listitem> + <para> + Uses the X11 protocol - easy adoption of existing code to implement + printer support. And all the network goodies like firewall proxies, + compressors etc. can be used for Xprint without modifications. + </para> + </listitem> + <listitem> + <para> + Security: Xprint can use all authentification schemes available in X11 + (like Kerberos5, SecureRPC, MIT-MAGIC-COOKIE or host-based + authentification). + </para> + </listitem> + <listitem> + <para> + Enhachements on the server side (Xprt) to not require the change of + client-side code. + </para> + </listitem> + <listitem> + <para> + Optimized job output (like the PostScript created by the PostScript DDX) + is usually a lot smaller than the PS code created by other PostScript + engines. + </para> + </listitem> + </itemizedlist> + </para> + </answer> +</qandaentry> + +<qandaentry id="contra_xprint"> + <question> + <para> + Why do some people dislike Xprint ? + </para> + </question> + <answer> + <para> + There are a few common misconceptions about Xprint. + Let's take a look some of these "myths", some background - and the facts: + </para> + <blockquote> + <!-- myth-fact list begin --> + <qandaset id="myths_about_xprint"> + <qandaentry> + <question> + <label>Myth:</label> + <para> + <quote> + Xprint prints just a XWD dump of the Xserver bitmap + </quote> + </para> + </question> + <answer> + <label>Fact:</label> + <para> + Whoever says Xprint simply does an "xwd"-like dump is wrong. + </para> + + <para> + <!-- XXX: outdated information --> + In short, Xprint <emphasis>currently</emphasis> (X11R6.5.1) supports *four* drivers: + <orderedlist> + <listitem> + <para> + X to native Postscript + </para> + </listitem> + <listitem> + <para> + X to native PCL5 + </para> + </listitem> + <listitem> + <para> + X to native PCL3 + </para> + </listitem> + <listitem> + <para> + X to a raster which is then feed to something like xpr to + create PS or PCL5 wrapped rasters. + </para> + </listitem> + </orderedlist> + </para> + <para> + In long, the original X Print Service ("XPS") was attempted + during CDE 1.0, and they only got so far as the "raster" driver. + </para> + <para> + As CDE 2.0 came around, Bob Schiefler and others at the X + Consortium agreed that the X Consortium would work on a X to + native PS Level 2 driver and HP would work on a X to native + PCL5 driver. + </para> + <para> + It was probably the CDE 1.0 effect that left many people with + the impression that Xprint is all about xwd-like window dumps. + NO! Xprint has native PostScript and PCL5 printing and more + drivers (like PDF and SVGprint DDXs etc.) are in the development. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <label>Myth:</label> + <para> + <quote> + Xprint cannot handle non-'ISO Latin 1' chars + </quote> + </para> + </question> + <answer> + <label>Fact:</label> + <para> + Xprint can print any chars incl. those required for MathML, + Hebrew, Arabic, Japanese etc. etc. + For example - the Xprint module for Mozilla5 is the only print + module which can proprtly print MathML. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <label>Myth:</label> + <para> + <quote> + Xprint uses a 1024x768 screen resolution to render the stuff on + the paper - therefore it will never be able to do high-resolution + stuff + </quote> + </para> + </question> + <answer> + <label>Fact:</label> + <para> + Xprt uses the screen resolution requested by the application or + the printers default resolution. + For example a 300 DPI printer which supports paper sizes up to + DIN-A4 will get a screen with 3300x3300 pixels (screen width and + height are usually equal to support per-page changes in the + orientation (potrait/landscape etc.), the window size would be + 2400x3149 for "portrait" orientation) - and larger resolutions + will result in larger screens. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <label>Myth:</label> + <para> + <quote> + Xprint prints only graphics(=bitmap/gfx) fonts + </quote> + </para> + </question> + <answer> + <label>Fact:</label> + <para> + In short, Xprt supports printer-builtin fonts and can + download fonts to the printer if they do not exist on the printer. + </para> + <para> + In long, this myth seems to have it's root in a <emphasis>feature</emphasis> of + Xprt which can - if Xprt gets misconfigured - disable the use of + printer-builtin fonts and the ability to download fonts. + </para> + <para> + Xprt's PostScript and PCL DDX have the <emphasis>unique</emphasis> feature to create + font glyphs from bitmap fonts if they are not available as + printer-builtin fonts nor as PostScipt Type1 fonts. However this + is the fallback - the <emphasis>last</emphasis> option used by Xprt. Used if + everything else fails. + But when someone does not pass any PS Type1 fonts with the font + path nor configures a printer model-config (which contains a + description of the features&fonts supported by the printer) Xprt + will never have a chance to use them. And if everything else + fails it has no other option than using what has been left - the + bitmap fonts... + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <label>Myth:</label> + <para> + <quote> + Xprint does not support pages sizes larger than DIN-A4 + </quote> + </para> + </question> + <answer> + <label>Fact:</label> + <para> + There is no such limitation. + The only limit is the 16bit coordinate system of the X11 + protocol - which is large enougth that Xprint can support paper + sizes <emphasis>larger</emphasis> than DIN-A0 oversize papers. There is no problem + with creating your own monster-size DIN-A0 posters using + Xprint-based applications. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <label>Myth:</label> + <para> + <quote> + Xprint does not support rotated text + </quote> + </para> + </question> + <answer> + <label>Fact:</label> + <para> + Xprint and all it's drivers support the X11 matrix XLFD + enhancement introduced in X11R6 (and future versions of Xprint will + support the <ulink url="http://stsf.sourceforge.net/">STSF</ulink> font API which supports + matrix transformations as well). + Fonts can be rotated at any angle. Take a look at the + <link linkend="faq_development">SOFTWARE DEVELOPMENT</link> section in + this FAQ for examples... + </para> + </answer> + </qandaentry> + + <!-- myth: Xprint rendering model is not good for printers --> + + </qandaset> + <!-- myth-fact list end --> + + + </blockquote> + </answer> +</qandaentry> + +<qandaentry id="does_xprint_support_anti_aliased_fonts"> + <question> + <para> + Does Xprint support anti-aliased fonts ? + </para> + </question> + <answer> + <para> + Question back: When do we need anti-aliased fonts ? + Anti-aliasing is a "hack" to work around the limitations caused by the + low resolution of monitors - they usually operate between 72 DPI and + 150 DPI. + </para> + <para> + But Xprint operates on printers where the usual <emphasis>minimum</emphasis> resolution is + 300 DPI (today's normal office printers support resolutions ranging from + 300 DPI up to 2400 DPI depending on the model; most common is 600 DPI). + Anti-aliasing at those resolutions is not required anymore. + Additionally many printers support their own font anti-aliasing at lower + resolutions which is far better and faster than it could be "done" on the + client side. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I check if Xprint is working and should be used ? + </para> + </question> + <answer> + <para> + Check whether the <envar>${XPSERVERLIST}</envar> env var is set or not. + If <envar>${XPSERVERLIST}</envar> is set then Xprint is available and should be used. + </para> + </answer> +</qandaentry> + +<qandaentry id="how_can_i_view_postscript_files"> + <question> + <para> + How can I view PS(=PostScript) files ? + </para> + </question> + <answer> + <para> + <itemizedlist> + <listitem> + <para> + On Unix/Linux (general): + <itemizedlist> + <listitem> + <para> + GhostScript ("gs") and GhostView ("gv" and it's KDE- and Gnome-specific versions "kghostview" and "ggv") + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + </itemizedlist> + <itemizedlist> + <listitem> + <para> + Solaris: + <itemizedlist> + <listitem> + <para> + <filename>/usr/dt/bin/sdtimage</filename> (DPS-based image viewer for CDE) + </para> + </listitem> + <listitem> + <para> + <filename>/usr/openwin/bin/pageview</filename> (DPS-based image viewer for OpenWindows) + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + </itemizedlist> + </para> + </answer> +</qandaentry> + +<qandaentry id="how_can_i_view_pcl_files"> + <question> + <para> + How can I view PCL files ? + </para> + </question> + <answer> + <para> + XXX - <ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=2261">xprint.mozdev.org bug 2261</ulink> + has been filed for that issue. + </para> + </answer> +</qandaentry> + + +<qandaentry> + <question> + <para> + How does Xprt find fonts ? + </para> + </question> + <answer> + <para> + <!-- Uhm... this is actually how *Mozilla* does the job... not Xprt... ;-/ (FIXME!) --> + Lookup-rule for Xprt's PostScript DDX to find fonts: + <orderedlist> + <listitem> + <para> + Printer-builtin fonts (defined by the fonts/-dir in the model-config) + </para> + </listitem> + <listitem> + <para> + PostScript fonts (will be downloaded via generated print job) + </para> + </listitem> + <listitem> + <para> + GFX-fonts build from X11 scaleable fonts + </para> + </listitem> + <listitem> + <para> + GFX-fonts build from X11 bitmap fonts + </para> + </listitem> + </orderedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I print TrueType fonts with Xprint ? + </para> + </question> + <answer> + <para> + <orderedlist> + <listitem> + <para> + Linux Xprt build from <ulink url="http://xprint.mozdev.org">http://xprint.mozdev.org/</ulink>'s source supports + TrueType fonts out-of-the-box (starting with the 008 development tree; + xprint.mozdev.org's releases <= 007 do not support TrueType fonts) and + and does not require any special actions. + </para> + </listitem> + <listitem> + <para> + Sun's Xprt on Solaris (<filename>/usr/openwin/bin/Xprt</filename>) has TrueType font + support out-of-the-box and does not require any special actions. + </para> + </listitem> + <listitem> + <para> + You can setup a TTF-aware X font server ("xfs", see + <citerefentry><refentrytitle>xfs</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry>) + with the matching TrueType fonts and add the font server location to Xprt's font path. + </para> + </listitem> + <listitem> + <para> + Sourceforge has a TrueType to PostScript Type 1 converter project, + see <ulink url="http://ttf2pt1.sourceforge.net/download.html">http://ttf2pt1.sourceforge.net/download.html</ulink>. + You may convert the TTF files into PT1 files that Xprt can download them + to the printer on demand... + </para> + </listitem> + </orderedlist> + </para> + </answer> +</qandaentry> + +<qandaentry id="what_does_ddx_mean"> + <question> + <para> + What does "DDX" mean ? + </para> + </question> + <answer> + <para> + "DDX" is a short term for "Device Dependent X" - the device-specific layer + of a Xserver (<link linkend="what_does_dix_mean">"DIX"</link>(="Device Independent X") is the counterpart). + </para> + </answer> +</qandaentry> + +<qandaentry id="what_does_dix_mean"> + <question> + <para> + What does "DIX" mean ? + </para> + </question> + <answer> + <para> + "DIX" is a short term for "Device Independent X" - the non-device specific + code of a Xserver (<link linkend="what_does_ddx_mean">"DDX"</link>(="Device Dependent X") is the counterpart). + </para> + </answer> +</qandaentry> + +<qandaentry id="what_does_pdl_mean"> + <question> + <para> + What does "PDL" mean ? + </para> + </question> + <answer> + <para> + "PDL" is a short term for "Page Description Language". Examples for PDLs are + PostScript, PCL, PDF and SVGprint. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + I have twenty printers installed on my system - but Xprt only shows two + screens. Where are all the other printers ? + </para> + </question> + <answer> + <para> + A Xprt screen does not represent a single printer. A Xprt screen + represents a single DDX (currently supported are PostScript, PCL3/5 color, + PCL mono and "raster" output(=1bit deep bitmap). + </para> + </answer> +</qandaentry> + +<qandaentry id="platforms_supported_by_xprint"> + <question> + <para> + Which platforms support Xprint ? + </para> + </question> + <answer> + <para> + All platforms which support X11 >= R6.4 can use Xprint. The client side + (<filename>libXp.so</filename>) is available on Linux/FreeBSD(=Xfree86), Solaris, HP-UX and AIX + and the Xprt server side is available by default on Solaris and HP-UX + (Xfree86 shipps with a Xprt binary - but that is broken and unuseable). + The client-side extension library (<filename>libXp.so</filename>) can be compiled on any + platform, the Xprt server needs minor adjustments for the specific + platforms... + If your platform does not have Xprint (client-side and/or server-side) + you can get the sources from <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink>. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + I have the broken Xfree86 Xprt binary on my system. Do I need a new + version of <filename>libXp.so</filename> (the client side X11 extension library for Xprint), + too ? + </para> + </question> + <answer> + <para> + No, the <filename>libXp.so</filename> shared library shipped with Xfree86 or build from + Xfree86 sources is not broken, only the server side ("Xprt") is buggy. + There is no need to replace the library. + </para> + </answer> +</qandaentry> + +<qandaentry id="who_do_i_spell_xprint"> + <question> + <para> + Which spelling is correct - "Xprint", "XPrint", "Xprinter" or Xprt" ? + </para> + </question> + <answer> + <para> + "Xprint" is the correct one - "XPrint" is just a typo, "Xprinter" is a + complety different product not related to X11/Xprint and "Xprt" is only + the "X11 print server"(=the server side of Xprint). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Which applications support Xprint ? + </para> + </question> + <answer> + <para> + There are various applications which support Xprint: + <itemizedlist> + <listitem> + <para> + Motif/LessTif (full framework incl. special widgets like <function>XmPrintShell</function>) + </para> + </listitem> + <listitem> + <para> + <ulink url="http://www.opengroup.org/cde/">Common Desktop Environment (CDE) 2.x</ulink> + </para> + </listitem> + <listitem> + <para> + <ulink url="http://www.mozilla.org/projects/xprint/">Mozilla</ulink> + </para> + </listitem> + <listitem> + <para> + Eclipse + </para> + </listitem> + <listitem> + <para> + KDE/Qt support is comming is planned for the end of Dec/2003 + </para> + </listitem> + <listitem> + <para> + StarOffice 5.x + </para> + </listitem> + <listitem> + <para> + etc. + </para> + </listitem> + </itemizedlist> + </para> + </answer> +</qandaentry> + +<qandaentry id="is_xprint_only_for_mozilla"> + <question> + <para> + Is "Xprint" "mozilla"-only (I saw that it's hosted by mozdev.org) ? + </para> + </question> + <answer> + <para> + No, Xprint is a general-purpose print API based on the X11 API used by + many applications (<ulink url="http://www.mozdev.org/">mozdev.org</ulink> is just + hosting the development area, but this does not mean the project is limited to mozilla... + <literal>:)</literal>). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Under which license is the source code from xprint.mozdev.org distributed under ? + </para> + </question> + <answer> + <para> + That's the plain "MIT" license, the same as used by Xfree86.org and X.org: +<programlisting> +Copyright (c) <year> <copyright holders> + +Permission is hereby granted, free of charge, to any person obtaining a copy of this software +and associated documentation files (the "Software"), to deal in the Software without +restriction, including without limitation the rights to use, copy, modify, merge, publish, +distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the +Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all copies or +substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING +BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND +NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, +DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. +</programlisting> + </para> + </answer> + </qandaentry> +</qandadiv> + + <qandadiv id="faq_usage"> +<title>Usage</title> + +<qandaentry> + <question> + <para> + How do I configure Xprint on the client side ? + </para> + </question> + <answer> + <para> + There are two env vars which control Xprint on the client side: + <orderedlist> + <listitem> + <para> + The env variable <envar>${XPSERVERLIST}</envar> contains a list of display identifiers + (seperated by whitespace) to tell the application where it can find + the Xprt 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 + "/etc/init.d/xprint get_xpserverlist". + Example: +<screen> + % <userinput>export XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`"</userinput> +</screen> + Alternativly <envar>${XPSERVERLIST}</envar> can be set manually: + </para> + <para> + Example: +<screen> + % <userinput>export XPSERVERLIST="littlecat:80 bitdog:72"</userinput> +</screen> + instructs an application to look at the displays 80 on the machine + "littlecat" and display 72 on the machine bigdog to look for Xprt + servers. + </para> + </listitem> + <listitem> + <para> + The env variable <envar>${XPRINTER}</envar> defines the default printer used by print + applications. The syntax is either <printername> or + <printername>@<display> + + <orderedlist> + <title>Examples:</title> + <listitem> + <para> +<screen> + % <userinput>export XPRINTER=ps003</userinput> +</screen> + tells an application to look for the first printer named "ps003" on + all Xprt servers. + </para> + </listitem> + <listitem> + <para> +<screen> + % <userinput>export XPRINTER="hplaser19@littlecat:80"</userinput> +</screen> + tells an application to look for the printer "hplaser19" on the Xprt + display "littlecat:80". + </para> + </listitem> + </orderedlist> + <note> + <title>Note:</title> + <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> env vars (in that order). + </para> + </note> + </para> + </listitem> + </orderedlist> + </para> + </answer> +</qandaentry> + +<qandaentry id="how_do_i_start_xprt"> + <question> + <para> + How do I start Xprt ? + </para> + </question> + <answer> + <para> + <orderedlist> + <listitem id="starting_xprt_on_linux_rpm"> + <para> + Linux RPM installations on Mandrake/RedHat/SuSE Linux: + Binary RPM packages provided by xprint.mozdev.org (or based on the same + source :) will install <filename>/etc/init.d/xprint</filename> and related glue + (see <link linkend="starting_xprt_general">[4]</link>) + automatically; after a reboot a Xprt instance will be started at system + startup and <envar>${XPSERVERLIST}</envar> should be populated for all users. + Note that you can start/stop per-user instances using <filename>/etc/init.d/xprint</filename> + (see <link linkend="starting_xprt_general">[4]</link>), too... + </para> + </listitem> + <listitem id="starting_xprt_on_debian_linux"> + <para> + Debian Linux: + Same as <link linkend="starting_xprt_on_linux_rpm">[1]</link>, however Debian does not support + <filename>/etc/profile.d/</filename> - you have to add the following line to <filename>/etc/profile</filename> + (for sh/ksh/bash) to populate <envar>${XPSERVERLIST}</envar>: +<screen> + <userinput>export XPSERVERLIST="`/bin/sh /etc/init.d/xprint get_xpserverlist`"</userinput> +</screen> + See <ulink url="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=171174">bugs.debian.org bug 171174</ulink> + ('"xprint-xprintorg" should automatically populate <envar>$XPSERVERLIST</envar>') for + further details on this issue... + </para> + </listitem> + <listitem id="starting_xprt_on_solaris"> + <orderedlist> + <listitem id="starting_xprt_on_solaris_using_giswxprintglue"> + <para> + Solaris using the "GISWxprintglue" package: + <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink> + provides a Solaris package called "GISWxprintglue" + which contains all the neccesary configuration files and startup scripts + to use Xprint; after a reboot a Xprt instance will be started at system + startup and <envar>${XPSERVERLIST}</envar> should be populated for all users. + Note that you can start/stop per-user instances using <filename>/etc/init.d/xprint</filename> + (see <link linkend="starting_xprt_general">[4]</link>), too... + </para> + </listitem> + <listitem id="starting_xprt_on_solaris_using_giswxprint"> + <para> + Solaris using the "GISWxprint" package: + <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink> + provides a Solaris package called "GISWxprint" + which is technically identical to the "GISWxprintglue" + (see <link linkend="starting_xprt_on_solaris_using_giswxprintglue">[3a]</link>) but + provides a Xprt binary build from the xprint.mozdve.org sources + ("GISWxprintglue" uses the <filename>/usr/openwin/bin/Xprt</filename> binary provided by Solaris). + </para> + </listitem> + </orderedlist> + </listitem> + <listitem id="starting_xprt_general"> + <para> + General: Using <filename>/etc/init.d/xprint</filename> and related glue: + There are startup/shutdown scripts in <filename>xc/programs/Xserver/Xprint/etc/</filename> + to start/stop/restart Xprt per-machine and/or per-user and to populate the + <envar>${XPSERVERLIST}</envar> env var: + <itemizedlist> + <listitem> + <para> + "<filename>xc/programs/Xserver/Xprint/etc/init.d/xprint</filename>" is a script for SystemV + and Linux to start/stop/restart Xprt. The script includes installation + and usage details and can be used by both "root" (to start Xprt for all + users) or by a single (non-priviledged, plain) user (to start Xprt + instances only for his/her own use) + </para> + </listitem> + <listitem> + <para> + "<filename>xc/programs/Xserver/Xprint/etc/profile.d/xprint.csh</filename>" and + "<filename>xc/programs/Xserver/Xprint/etc/profile.d/xprint.sh</filename>" are scripts for + Linux (which support <filename>/etc/profile.d/</filename> ; note that this does not include + Debian) to populate the <envar>${XPSERVERLIST}</envar> env var for each user. + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + <listitem id="starting_xprt_manually"> + <para> + Starting Xprt "manually" (without using <filename>/etc/init.d/xprint</filename>): + Set the <envar>${XPCONFIGDIR}</envar> env variable to the directory where Xprt can find + it's configuration data. + <warning> + <title>WARNING</title> + <para> + If Xprt cannot find it's configuration data it will not be + able to use printer-builtin fonts (which are defined by the + model-config in the configuration dir). Without printer-builtin fonts + Xprt <emphasis>may</emphasis> fall back to generate font glyphs from bitmap fonts (this + resulted in the MYTH that "Xprt can only print gfx fonts". This is not + <emphasis>TRUE</emphasis> - this only happens if Xprt is either misconfigured or no + matching builtin or PS Type1 font is available). + </para> + <para> + You may want to make a copy of the default configuration directory and + modify it to match your needs. + </para> + </warning> + </para> + </listitem> + <listitem> + <para> + Starting Xprt is just as easy as starting any other Xserver: +<screen> + % <userinput>Xprt :12</userinput> +</screen> + will start Xprt on display 12 (e.g. set <envar>${XPSERVERLIST}</envar> to ":12" or + "myhostname:12". + </para> + <para> + You may want to copy your framebuffer Xserver's font path to be able to + print all fonts which can be displayed on that Xserver. +<screen> + % <userinput>Xprt -fp $(xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }") :12</userinput> +</screen> + </para> + </listitem> + </orderedlist> + <note> + <title>Notes:</title> + <para> + <itemizedlist> + <listitem> + <para> + The <filename>/etc/init.d/xprint</filename> has a more advanched filtering scheme based on + regex patters to "accept" and/or "reject" font paths + </para> + </listitem> + <listitem> + <para> + 'xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }"' + may be too simple-minded if your Xserver does not support TrueType + fonts. The following statemement is better in this case since it + filters the font path and removes all path elements which have TrueType + fonts (*.ttf, *.TTF) or TrueType font collections (*.ttc, *.TTC) in + <filename>fonts.dir</filename>: +<screen> + % <userinput>xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }" | + tr "," "\n" | while read i ; do \ + if [ "$(cat ${i}/fonts.dir | egrep -i "ttf|ttc" 2>/dev/null)" == "" ] \ + ; then echo $i ; fi ; done | (fontpath="" ; fpdelim=""; while read i ; \ + do fontpath=${fontpath}${fpdelim}${i} ; fpdelim="," ; done ; echo \ + $fontpath)</userinput> +</screen> + </para> + </listitem> + <listitem> + <para> + It may be easier to just feed all available font paths to Xprt + (BTW: mozilla 1.0 had a bug in that case which resulted in the problem + that it used many many bitmap fonts in that case - this has been fixed + for 1.0.1 and Netscape 7 (that's the reason why the quickguides for + hebrew/cyrillic use the "Xp_dummyfonts" fonts instead of + <filename class="directory">/usr/openwin/lib/X11/fonts/misc/</filename> - to avoid that Mozilla finds bitmap + fonts for the same locale). + The following "small" one-liner finds all fonts (except printer builtin + fonts): +<screen> + % <userinput>find /usr/openwin -name fonts.dir | while read i ; do echo + ${i%/fonts.dir} ; done | fgrep -v "models/"</userinput> +</screen> + Plug it into the filter above to remove the Truetype fonts and you are + "done"... :) + </para> + </listitem> + </itemizedlist> + See <link linkend="faq_troubleshooting">TROUBLESHOOTING</link> if you run into problems... + </para> + </note> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I get a list of printers managed by Xprint ? + </para> + </question> + <answer> + <para> + The tool "xplsprinters" is designed for that purpose. It can deliver both + list of printers and attributes supported for a specific list of printers. + Use % xplsprinters -h # to obtain usage information. + Example: + <itemizedlist> + <listitem> + <para> + Get list of available printers: +<screen> +% <userinput>xplsprinters</userinput> +<computeroutput>printer: hplaserjet001@castor:19 +printer: hpcolor001@castor:19 +printer: laser1@jason:5 +printer: david_dj01@jason:5</computeroutput> +</screen> + </para> + </listitem> + <listitem> + <para> + Get information about the supported attrbites of printer "ps002": +<screen> +% <userinput>xplsprinters -printer ps002 -l</userinput> +<computeroutput>printer: ps002@castor:18 + comment= + model-identifier=HPDJ1600C + default-medium=iso-a4 + default-input-tray= + medium-source-sizes-supported=iso-a4 false 6.35 203.65 6.35 290.65 + medium-source-sizes-supported=na-letter false 6.35 209.55 6.35 273.05 + default-printer-resolution=300 + resolution=300 + default_orientation= + orientation=portrait + orientation=landscape + default_plex= + plex=simplex</computeroutput> +</screen> + </para> + </listitem> + </itemizedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I start Xprt at boot time ? + </para> + </question> + <answer> + <para> + "<filename>xc/programs/Xserver/Xprint/etc/init.d/xprint</filename>" is a script for SystemV + and Linux to start/stop/restart Xprt at system startup (e.g. per-machine) + or for a single user (e.g. per-user). + The script includes installation and usage details. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I start Xprt per-user ? + </para> + </question> + <answer> + <para> + "<filename>xc/programs/Xserver/Xprint/etc/init.d/xprint</filename>" is a script for SystemV + and Linux to start/stop/restart Xprt at system startup (e.g. per-machine) + or for a single user (e.g. per-user). + The script includes installation and usage details. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I start Xprt only for one application ? + </para> + </question> + <answer> + <para> + Create your own version/copy of <filename>/etc/init.d/xprint</filename> and modify it to fit + your requirements and then make sure that you issue a + "my_xprint_startscript start" before starting the application and a + "my_xprint_startscript stop" after leaving the application. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I filter the font path which should be passed to Xprt for + certain fonts ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I manage access control to the Xprt server ? + </para> + </question> + <answer> + <para> + Access control to Xprt is not differently as to any other Xserver and + 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 + <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>)) + 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> + etc. for further details. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I log access to the Xprt server ? + </para> + </question> + <answer> + <para> + Logging access to Xprt can be done using the standard Xserver auditing, + see the <citerefentry><refentrytitle>Xserver</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry> + manual page, option "-audit" + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Does it require "root" permissions to use Xprt/Xprint ? + </para> + </question> + <answer> + <para> + No, both Xprint clients and Xprint server(s) do not require root rights + to work. + </para> + <para> + Xprint clients are handled like any other X11 application and the Xprt + servers can run without any special requirements. + Solaris is an exception here since it requires to start any Xserver + (incl. Xprt) setgid "root" (set-group-id "root", this is <emphasis>not</emphasis> + set-user-id "root") since the sockets/pipe files in /tmp/.X11-pipe/ and + /tmp/.X11-unix/ are only accessible for the group "root". + The workaround is to start Xprt with the option "-pn"; therefore even + Xprt server binaries which are not setgid "root" can run without + problems). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I see the attributes of a printer managed by Xprint ? + </para> + </question> + <answer> + <para> + "xplsprinters -printer myprinter004 -l" will do the job for printer + "myprinter004". + </para> + <para> + See + <citerefentry><refentrytitle>xplsprinters</refentrytitle><manvolnum>__mansuffix__</manvolnum></citerefentry> + for futher usage and a description of the output. + </para> + </answer> +</qandaentry> + +<qandaentry id="how_can_i_list_the_font_path_used_by_xprint"> + <question> + <para> + How can I list the font path used by a Xprt server ? + </para> + </question> + <answer> + <para> + Figure out the display id of the server which should be queried (we are + using "foobar:98" in this example) and then try this: +<screen> +% <userinput>(DISPLAY=foobar:98 xset q | \ +awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }" | \ +tr "," "[\n]")</userinput> +# Output may look like: +<computeroutput>PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/HPDJ1600C/fonts/ +PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/SPSPARC2/fonts/ +PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/HPLJ3Si-PS/fonts/ +/usr/openwin/lib/X11/fonts/F3/ +/usr/openwin/lib/X11/fonts/F3bitmaps/ +/usr/openwin/lib/X11/fonts/Type1/ +/usr/openwin/lib/X11/fonts/Speedo/ +/usr/openwin/lib/X11/fonts/misc/ +/usr/openwin/lib/X11/fonts/75dpi/ +/usr/openwin/lib/X11/fonts/100dpi/</computeroutput> +</screen> + <note> + <title>Note:</title> + <para> + Note that the font path items which start with "PRINTER:" are <emphasis>only</emphasis> be + sourced <emphasis>after</emphasis> the matching printer has been selected and configured + (for developers: After <function>XpSetContext</function> has been called). + </para> + </note> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + "xset q" lists all model-specific font dirs (like + PRINTER:/myxpcfg/C/print/models/SPSPARC2/fonts/") - is that a bug ? + </para> + </question> + <answer> + <para> + No, this is normal. Xprt will add all fonts of all printer models to the + font path - but font path items starting with "PRINTER:" are <emphasis>only</emphasis> + available for an application <emphasis>after</emphasis> the matching printer has been + selected and configured (for developers: After <function>XpSetContext</function> has been + called), <emphasis>before</emphasis> that point fonts in these dirs are not available for + an application. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + My application lists a printer called "xp_ps_spooldir_tmp_Xprintjobs" / + "xp_pdf_spooldir_tmp_Xprintjobs" / "spooldir_tmp_Xprintjobs" / in the + print dialog but I do not have such a print queue installed anywhere. + What is that for a thing ?! + </para> + </question> + <answer> + <para> + "xp_ps_spooldir_tmp_Xprintjobs" and "xp_pdf_spooldir_tmp_Xprintjobs" + ("spooldir_tmp_Xprintjobs" was the old, pre-009 name for "xp_ps_spooldir_tmp_Xprintjobs") + are special Xprint printer targets which uses the "PSspooldir" / "PS2PDFspooldir-GS" + printer models. These model config sends PostScript or PDF jobs + to the <filename>/tmp/Xprintjobs/</filename> directory instead to a physical printer + (quite usefull for people who want to get the PostScript or PDF files as output instead + of printed pages). + </para> + <formalpara> + <title>References:</title> + <para> + <itemizedlist> + <listitem><para><ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=5092">xprint.mozdev.org bug 5092 ("[PS2PDFspooldir-GS] RFE: Add printer model which sends PDF jobs to /tmp/Xprintjobs/")</ulink></para></listitem> + </itemizedlist> + </para> + </formalpara> + </answer> +</qandaentry> + +<qandaentry id="manual_xprint_forwarding_via_ssh"> + <question> + <para> + How can I forward Xprint services when logging-in via ssh to another machine ? + </para> + </question> + <answer> + <para> + You have to forward the X11 connection for the Xprint server(s) to the remote system + and set the <envar>XPSERVERLIST</envar> variable to direct the Xprint clients to the forwarded ports. + + <example role="example"> + <title>Login to a remote host using slogin (assuming there is only one + Xprint server listed in <envar>XPSERVERLIST</envar>)</title> + + <para><screen>% <userinput>echo $XPSERVERLIST</userinput></screen></para> + <screen><computeroutput>west:33</computeroutput></screen> + <para>Add 6000 to the display number ("33" in this example) to get the port number + (X11 port numbers start at port 6000. 6000 is display number "0", 6001 is display number 6001 and so on) + and then ask slogin to forward the port: + </para> + <para><screen>% <userinput>slogin -R6033:west:6033 -l nrubsig puzzle</userinput></screen> + <screen><computeroutput>nrubsig's password: +Last login: Fri Jan 23 04:05:06 2004 from west.informatik.med.uni-giessen.de +Have a lot of fun... +</computeroutput></screen> + </para> + <para> + Then set the <envar>XPSERVERLIST</envar> env var on the remote host to the forwarded + ports and you are done: + </para> + <para><screen>% <userinput>export XPSERVERLIST="localhost:33 ${XPSERVERLIST}"</userinput></screen></para> + </example> + + <example role="example"> + <title>Login to a remote host using slogin (assuming there are multiple + Xprint servers listed in <envar>XPSERVERLIST</envar>)</title> + <para> + The following small shell script will process the <envar>XPSERVERLIST</envar> env var and output the + parameters for calling slogin/ssh with all Xprint server ports forwarded: +<programlisting> +#!/bin/ksh +# xp_print_slogin_args.ksh +# Small example which parses $XPSERVERLIST and prints out how slogin/ssh +# should be used to forward all local Xprint servers + +PORTARGS="" +REMOTE_XPSERVERLIST="" +spacer="" # seperator +remoteport=6100 +remotedisplaynum=100 + +echo "${XPSERVERLIST}" | tr " " "\n" | + while read i ; do + [ "$i" = "" ] && continue + displaynum="${i##*:}" + port="$(( ${displaynum} + 6000 ))" + hostname="${i%:*}" + PORTARGS="${PORTARGS}${spacer}-R${remoteport}:${hostname}:${port}" + REMOTE_XPSERVERLIST="${REMOTE_XPSERVERLIST}${spacer}localhost:${remotedisplaynum}" + + spacer=" " + remoteport=$((${remoteport} + 1)) + remotedisplaynum=$((${remotedisplaynum} + 1)) + done +echo "Log in with: % slogin ${PORTARGS} -l myloginname myremotehost" +echo "Set remote XPSERVERLIST with % export XPSERVERLIST=\"${REMOTE_XPSERVERLIST} \${XPSERVERLIST}\"" +# EOF. +</programlisting> + </para> + <para>Example usage: + <screen>% <userinput>xp_print_slogin_args.ksh</userinput></screen> + will print + <screen><computeroutput>Log in with: % slogin -R6100:west:6033 -R6101:north:6033 -l myloginname myremotehost +Set remote XPSERVERLIST with % export XPSERVERLIST="localhost:100 localhost:101 ${XPSERVERLIST}"</computeroutput></screen> + </para> + </example> + </para> + </answer> +</qandaentry> + + +</qandadiv> + +<qandadiv id="faq_configuration"> +<title>Configuration</title> + +<qandaentry> + <question> + <para> + How do I change the defaults for double-sided/single-sided/etc. + printing ? + </para> + </question> + <answer> + <para> + This is controlled via the "plex" attribute in the document attribute + pool <filename>(<envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/attributes/document</filename> and/or + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename>). + Examples: + <orderedlist> + <listitem> + <para> + Adding/modifying the following line to/in + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename> sets the default plex for + all printers to "duplex": +<screen> + *plex: duplex +</screen> + </para> + </listitem> + <listitem> + <para> + Adding/modifying the following two lines to/in + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename> sets the default plex for + all printers to "duplex" except for printer "ps003" which should + default to "simplex": +<screen> + *plex: duplex + ps003.plex: simplex +</screen> + </para> + </listitem> + </orderedlist> + + <note> + <title>Notes:</title> + <para> + <itemizedlist> + <listitem> + <para> + Not all printers support all plex modes. The model-config may restrict + the available plex modes. + </para> + </listitem> + <listitem> + <para> + Setting a plex mode which is not supported by either the DDX(=driver) + or not specified in the model-config will cause Xprt to not set a + default plex. + </para> + </listitem> + <listitem> + <para> + The PostScript DDX supports plex modes "simplex", "duplex" and "tumble". + </para> + </listitem> + <listitem> + <para> + Verification: + Use +<programlisting> + xplsprinters -l | egrep "^printer:|default_plex=|plex=" +</programlisting> + to view the plex settings for all printers. + </para> + </listitem> + </itemizedlist> + </para> + </note> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + I am in America and I don't have any ISO A4 paper. How do I change the + default paper size to 8.5 inch x 11 inch (US-Letter) ? + </para> + </question> + <answer> + <para> + This is controlled via the "default-medium" attribute in the document + attribute pool (<filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/attributes/document</filename> and/or + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename>). + Examples: + <orderedlist> + <listitem> + <para> + Adding/modifying the following line to/in + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename> sets the default paper size + for all printers to "na-letter": +<screen> + *default-medium: na-letter +</screen> + </para> + </listitem> + <listitem> + <para> + Adding/modifying the following two lines to/in + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename> sets the default paper size + for all printers to "na-letter" except for printer "ps003" which should + default to "iso-a4": +<screen> + *default-medium: na-letter + ps003.default-medium: iso-a4 +</screen> + </para> + </listitem> + </orderedlist> + + <note> + <title>Notes:</title> + <para> + <itemizedlist> + <listitem> + <para> + xprint.mozdev.org releases >= 007 provides a seperate "document" + attribute pool for en_US(-like) locales (see + <filename><envar>${XPCONFIGDIR}</envar>/en_US/print/attributes/document</filename>) which will override the + default ISO-A4 with US-Letter (this feature assumes that <envar>${LANG}</envar> is set + to "en_US" (or a locale which has similar defaults as "en_US", those + are currently linked to "en_US" in <filename><envar>${XPCONFIGDIR}</envar>/</filename>)) + </para> + </listitem> + <listitem> + <para> + Not all printers support all paper sizes. The model-config may restrict + the available paper sizes. + </para> + </listitem> + <listitem> + <para> + Setting a paper size which is not supported by either the DDX(=driver) + or not specified in the model-config will cause Xprt to not set a + default paper size. + </para> + </listitem> + <listitem> + <para> + The PostScript DDX supports the following paper sizes: + <itemizedlist> + <listitem> + <para> + X.org release 6.6 (X116.6): + <simplelist type="inline"> + <member>"iso-a4"</member> + <member>"na-letter"</member> + <member>"na-legal"</member> + <member>"executive"</member> + <member>"iso-designated-long"</member> + <member>"na-number-10-envelope"</member> + </simplelist> + </para> + </listitem> + <listitem> + <para> + xprint.mozdev.org release >= 006: + <simplelist type="inline"> + <member>"na-letter"</member> + <member>"na-legal"</member> + <member>"executive"</member> + <member>"folio"</member> + <member>"invoice"</member> + <member>"ledger"</member> + <member>"quarto"</member> + <member>"a"</member> + <member>"b"</member> + <member>"c"</member> + <member>"d"</member> + <member>"e"</member> + <member>"na-6x9-envelope"</member> + <member>"na-10x15-envelope"</member> + <member>"monarch-envelope"</member> + <member>"na-10x13-envelope"</member> + <member>"na-9x12-envelope"</member> + <member>"na-number-10-envelope"</member> + <member>"na-7x9-envelope"</member> + <member>"na-9x11-envelope"</member> + <member>"na-10x14-envelope"</member> + <member>"na-number-9-envelope"</member> + <member>"iso-a0"</member> + <member>"iso-a1"</member> + <member>"iso-a2"</member> + <member>"iso-a3"</member> + <member>"iso-a4"</member> + <member>"iso-a5"</member> + <member>"iso-a6"</member> + <member>"iso-a7"</member> + <member>"iso-a8"</member> + <member>"iso-a9"</member> + <member>"iso-a10"</member> + <member>"iso-b1"</member> + <member>"iso-b2"</member> + <member>"iso-b3"</member> + <member>"iso-b4"</member> + <member>"iso-b5"</member> + <member>"iso-b6"</member> + <member>"iso-b7"</member> + <member>"iso-b8"</member> + <member>"iso-b9"</member> + <member>"iso-b10"</member> + <member>"jis-b1"</member> + <member>"jis-b2"</member> + <member>"jis-b3"</member> + <member>"jis-b4"</member> + <member>"jis-b5"</member> + <member>"jis-b6"</member> + <member>"jis-b7"</member> + <member>"jis-b8"</member> + <member>"jis-b9"</member> + <member>"jis-b10"</member> + <member>"iso-c3"</member> + <member>"iso-c4"</member> + <member>"iso-c5"</member> + <member>"iso-c6"</member> + <member>"iso-designated-long"</member> + </simplelist> + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + <listitem> + <para> + Verification: + Use +<programlisting> + xplsprinters -l | egrep "^printer:|default-medium=|medium-source-sizes-supported=" +</programlisting> + to view the medium settings for all printers. + The 'medium-source-sizes-supported='-lines have the format XXX. + </para> + </listitem> + </itemizedlist> + </para> + </note> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How do I change the default printer resolution ? + </para> + </question> + <answer> + <para> + This is controlled via the "default-printer-resolution" attribute in the + document attribute pool (<filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/attributes/document</filename> + and/or <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename>). + Examples: + <orderedlist> + <listitem> + <para> + Adding/modifying the following line to/in + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename> sets the default + resolution for all printers to 600 DPI: +<screen> + *default-printer-resolution: 600 +</screen> + </para> + </listitem> + <listitem> + <para> + Adding/modifying the following two lines to/in + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename> sets the default resolution + for all printers to 300 DPI except for printer "tekcolor_ps" which + should default to 1200 DPI: +<screen> + *default-printer-resolution: 300 + tekcolor_ps.default-printer-resolution: 1200 +</screen> + </para> + </listitem> + </orderedlist> + + <note> + <title>Notes:</title> + <para> + <itemizedlist> + <listitem> + <para> + Not all printers support all resolutions. The model-config may restrict + the available resolutions. + </para> + </listitem> + <listitem> + <para> + Setting a resolution which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt to + not set a default resolution. + </para> + </listitem> + <listitem> + <para> + The PostScript DDX supports the following default resolutions + <itemizedlist> + <listitem> + <para> + X.org release 6.6 (X116.6): + <simplelist type="inline"> + <member>300</member> + <member>600</member> + <member>720</member> + <member>940</member> + <member>1200</member> + <member>1440</member> + <member>2400</member> + </simplelist> + </para> + </listitem> + <listitem> + <para> + xprint.mozdev.org release >= 006: + <simplelist type="inline"> + <member>75</member> + <member>100</member> + <member>120</member> + <member>150</member> + <member>180</member> + <member>200</member> + <member>240</member> + <member>300</member> + <member>360</member> + <member>400</member> + <member>600</member> + <member>720</member> + <member>940</member> + <member>1200</member> + <member>1440</member> + <member>2400</member> + </simplelist> + </para> + </listitem> + </itemizedlist> + + </para> + </listitem> + <listitem> + <para> + Verification: + Use +<programlisting> + xplsprinters -l | egrep "^printer:|default-printer-resolution=|resolution=" +</programlisting> + to view the resolution settings for all printers. + </para> + </listitem> + </itemizedlist> + </para> + </note> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How do I change the default settings for "portrait"/"landscape"/"seascape" (=page orientation) ? + </para> + </question> + <answer> + <para> + This is controlled via the "content-orientation" attribute in the + document attribute pool (<filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/attributes/document</filename> + and/or <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename>). + Examples: + <orderedlist> + <listitem> + <para> + Adding/modifying the following line to/in + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename> sets the default + orientation for all printers to "portrait": +<screen> + *content-orientation: portrait +</screen> + </para> + </listitem> + <listitem> + <para> + Adding/modifying the following two lines to/in + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename> sets the default orientation + for all printers to "portrait" except for printer "ps003" which should + default to "landscape": +<screen> + *content-orientation: portrait + ps003.content-orientation: landscape +</screen> + </para> + </listitem> + </orderedlist> + + <note> + <title>Notes:</title> + <para> + <itemizedlist> + <listitem> + <para> + Not all printers support all orientations. The model-config may + restrict the available orientations. + </para> + </listitem> + <listitem> + <para> + Setting an orientation which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt to + not set a default orientation. + </para> + </listitem> + <listitem> + <para> + The PostScript DDX supports the following orientations: + "portrait", "landscape", "reverse-portrait" and "reverse-landscape". + </para> + </listitem> + <listitem> + <para> + Verification: + Use +<programlisting> + xplsprinters -l | egrep "^printer:|default_orientation=|orientation=" +</programlisting> + to view the orientation settings for all printers. + </para> + </listitem> + </itemizedlist> + </para> + </note> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I prevent Xprt from using any bitmap(=gfx) fonts ? + </para> + </question> + <answer> + <para> + Do not pass any bitmap fonts with the "-fp" (=font path) argument. + However you have to provide a 'fixed' and a 'cursor' font, a Xserver + can't start without having these fonts. + <blockquote><procedure> + <title>Task list:</title> + <step> + <para> + Create a new directory: +<screen> +% <userinput>mkdir Xp_dummyfonts</userinput> +% <userinput>cd Xp_dummyfonts</userinput> +</screen> + </para> + </step> + <step> + <para> + Create a <filename>fonts.alias</filename> file with the following content: +<programlisting> +! alias for "fixed" font +! original from /usr/openwin/lib/X11/fonts/misc/fonts.alias looks like this: +! fixed "-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1" +fixed -*-r-*--*-*-*-*-*-*-iso8859-1 +! EOF. +</programlisting> + </para> + </step> + <step> + <para> + Copy or link "<filename>6x13.pcf.Z</filename>" and "<filename>cursor.pcf.Z</filename>" and create <filename>fonts.dir</filename> +<screen> +% <userinput>ln -s /usr/openwin/lib/X11/fonts/misc/6x13.pcf.Z .</userinput> +% <userinput>ln -s /usr/openwin/lib/X11/fonts/misc/cursor.pcf.Z .</userinput> +% <userinput>mkfontdir $PWD</userinput> +</screen> + </para> + </step> + <step> + <para> + Verify: The directory should now look like this: +<screen> +% <userinput>ls -1</userinput> +<computeroutput>6x13.pcf.Z +cursor.pcf.Z +fonts.alias +fonts.dir</computeroutput> +</screen> + </para> + </step> + <step> + <para> + Add the full path (e.g. /home/xp/Xp_dummyfonts) as last element + of the font path when starting Xprt: +<screen> + % <userinput>Xprt -fp /usr/openwin/lib/X11/fonts/Type1/,/home/xp/Xp_dummyfonts :12</userinput> +</screen> + </para> + </step> + </procedure></blockquote> + +<!-- fixme: puck is dead, need replacement + <note> + <para> + I created a tarball from these instructions, get it from + <ulink url="http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/Xp_dummyfonts.tar.gz">http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/Xp_dummyfonts.tar.gz</ulink> + Unpack it and add the new dir to your fontpath) + </para> + </note> +--> + </para> + </answer> +</qandaentry> + +<qandaentry id="configure_manual_list_of_printers"> + <question> + <para> + I want only my manually added printers managed by Xprint. How can I + prevent Xprt from looking-up the printer names automatically ? + </para> + </question> + <answer> + <para> + Add a line with "Augment_Printer_List %none%" to + <filename><envar>${XPCONFIGDIR}</envar>/C/print/Xprinters</filename> (or + <filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/Xprinters</filename>) and add lines with + "Printer <name>" for each printer <name>. + Example: +<screen> +Augment_Printer_List %none% +Printer ps001 +Printer ps003 +Printer hplaser6 +</screen> + will add only the printers "ps001", ps003" and "hplaser6". + </para> + </answer> +</qandaentry> + +<qandaentry id="configure_custom_script_to_enumerate_system_printers"> + <question> + <para> + How can I specify an own program/script to enumerate the printers on my system ? + </para> + </question> + <answer> + <para> + Add "Augment_Printer_List my_script" to <filename><envar>${XPCONFIGDIR}</envar>/C/print/Xprinters</filename> (or + <filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG</envar>}/print/Xprinters</filename>). + The script must return the printer names - one per line, ASCII-only - to stdout. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Which program is used by default by Xprt to enumerate the printers on my system ? + </para> + </question> + <answer> + <para> + This depends on the OS: + <itemizedlist> + <listitem> + <para> + On Solaris (and most other OSes exclusing AIX and Linux): +<screen> +% <userinput>lpstat -a | cut -d " " -f 1</userinput> +</screen> + </para> + </listitem> + <listitem> + <para> + On Linux: + <itemizedlist> + <listitem> + <para> + For Xprt build from X11R6.x X.org sources: +<screen> +% <userinput>lpc status | grep -v '^\t' | sed -e /:/s///</userinput> # '\t' means TAB +</screen> + </para> + </listitem> + <listitem> + <para> + For Xprt build from xprint.mozdev.org <= release 008 sources (both lines are executed + to support both LPRng and CUPS (using the CUPS *BSD compatibility tools)): +<screen> +% <userinput>lpc status | awk '/:$/ && !/@/ { print $1 }' | sed -e /:/s/// ; \ + lpc -a status | awk '/@/ && !/:/ { split( $1, name, \"@\" ); print name[1]; }'</userinput> +</screen> + </para> + </listitem> + <listitem> + <para> + Xprt build from xprint.mozdev.org >= release 009 sources uses a more flexible scheme + which tries to enumerate the print spoolers in the order "CUPS" (using the normal CUPS + (SYSV-like) commands), "LPRng" and finally "*BSD", the first working (=print queues are + found) print spooler is chosen. + The spooler(s) being used (and the query order) can be changed by the "-XpSpoolerType" + command line option. + The list of commands used to enumerate the queues for a specific spooler type + can be found in <filename>xc/programs/Xserver/Xprint/spooler.c</filename> + </para> + </listitem> + + </itemizedlist> + </para> + </listitem> + <listitem> + <para> + On AIX v4: +<screen> +% <userinput>lsallq | grep -v '^bsh$'</userinput> +</screen> + </para> + </listitem> + </itemizedlist> + <note> + <title>Notes:</title> + <para> + <itemizedlist> + <listitem> + <para> + See <filename>xc/programs/Xserver/Xprint/Init.c</filename> (xprint.mozdev.org >= release 009 uses + <filename>xc/programs/Xserver/Xprint/spooler.c</filename>) for a complete list of commands + used on the specific platforms to enumerate the printers. + </para> + </listitem> + <listitem> + <para> + Note that the output is always piped through "sort" to get an + alphabetical order (the "default" printer is not chosen/defined + here(=server side), the client side is responsible to choose a default + printer. + See FAQ item about the <envar>${XPRINTER}</envar> env var how to set your default + printer). + </para> + </listitem> + </itemizedlist> + </para> + </note> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Where can I get more PostScript Type1 fonts from ? + </para> + </question> + <answer> + <para> + Some sources: + <itemizedlist> + <listitem> + <para> + Adobe: + + <itemizedlist> + <listitem> + <para> + Commercial fonts: + <ulink url="http://www.adobe.com/type/main.html">http://www.adobe.com/type/main.html</ulink> + </para> + </listitem> + <listitem> + <para> + Free Euro font: + <itemizedlist> + <listitem> + <para> + Single-glyph (e.g. it contains <emphasis>only</emphasis> the euro char) euro font: + <ulink url="http://www.adobe.com/type/eurofont.html">http://www.adobe.com/type/eurofont.html</ulink> or + <ulink url="ftp://ftp.adobe.com/pub/adobe/type/win/all/">ftp://ftp.adobe.com/pub/adobe/type/win/all/</ulink> + ("eurofont.exe" can be unzipped using "unzip") + </para> + </listitem> + <listitem> + <para> + ISO8859-15: + XXX - WANTED!! + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + <listitem> + <para> + Solaris shipps with various PS Type 1 fonts: + <itemizedlist> + <listitem> + <para> + Arabic: + <filename>/usr/openwin/lib/locale/ar/X11/fonts/Type1/</filename> + (<filename>fonts.dir</filename> and <filename>fonts.scale</filename> missing, maybe they miss the + presentation forms a&b, too [unconfirmed]) + </para> + </listitem> + <listitem> + <para> + ISO-8859-13 (Latin 8): + <filename>/usr/openwin/lib/locale/iso_8859_13/X11/fonts/Type1/</filename> + </para> + </listitem> + <listitem> + <para> + ISO-8859-5 (Latin 5): + <filename>/usr/openwin/lib/locale/iso_8859_9/X11/fonts/Type1/</filename> + </para> + </listitem> + <listitem> + <para> + ISO-8859-8/Hebrew: + <filename>/usr/openwin/lib/locale/iso_8859_8/X11/fonts/Type1</filename> + (BROKEN, even "type1fix" cannot fix them. Use the hebrew fonts from + <!-- XXX: FixMe!! --> + <ulink url="broken-link/PS_Type1_iso8859-8.tar.gz"> + broken-link-/PS_Type1_iso8859-8.tar.gz</ulink>) + </para> + </listitem> + <listitem> + <para> + ISO-8859-7/Modern greek: + <filename>/usr/openwin/lib/locale/iso_8859_7/X11/fonts/Type1/</filename> + </para> + </listitem> + <listitem> + <para> + ISO-8859-5/Cryrillic: + <filename>/usr/openwin/lib/locale/iso_8859_5/X11/fonts/Type1/</filename> + </para> + </listitem> + <listitem> + <para> + ISO-8859-4 (Latin 4): + <filename>/usr/openwin/lib/locale/iso_8859_4/X11/fonts/Type1/</filename> + </para> + </listitem> + <listitem> + <para> + ISO-8859-2 (Latin 2): + <filename>/usr/openwin/lib/locale/iso_8859_2/X11/fonts/Type1/</filename> + </para> + </listitem> + <listitem> + <para> + ISO-8859-1 (Latin 1) and Symbol fonts: + <filename>/usr/openwin/lib/X11/fonts/Type1/</filename> + </para> + </listitem> + </itemizedlist> + </para> + </listitem> +<!-- XXX/FixMe: puck is dead, need replacement... ;-( + <listitem> + <para> + Some of my own collections: + (see <ulink url="http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/"> + http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/</ulink>): + <itemizedlist> + <listitem> + <para> + KOI8-R: + <ulink url="http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/PS_Type1_koi8-r.tar.gz"> + http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/PS_Type1_koi8-r.tar.gz</ulink> + </para> + </listitem> + <listitem> + <para> + ISO-8859-8/Hebrew: + <ulink url="http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/PS_Type1_iso8859-8.tar.gz"> + http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/PS_Type1_iso8859-8.tar.gz</ulink> + </para> + </listitem> + </itemizedlist> + </para> + </listitem> +--> + </itemizedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + What are PMF fonts (e.g. the *.pmf fonts in + <filename><envar>${XPCONFIGDIR}</envar>/C/print/models/%model_name%/fonts/</filename> (or + <filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/models/%model_name%/fonts/</filename>)) ? + </para> + </question> + <answer> + <para> + PMF "fonts" are "printer metric files" (.pmf) that describe the metrics + of the fonts (which means they do not contain any data to render the + fonts - they contain only the plain metrics of a font) which are built + into the printer (ROM or via font catridge etc.). + The file format is identical to the PCF ("Portable Compiled Format") font + format except that the bitmap data is not provided. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Can I use the fontserver ("xfs") with Xprt ? + </para> + </question> + <answer> + <para> + You can use Xprt with the font server ("xfs") like with any other + Xserver - but it is not recommded since the font server protocol does + not allow access to the native font format and therefore disables font + download, e.g. both PS Type1 and TrueType fonts cannot be downloaded + anymore and Xprt will fall-back to embed them as bitmap glyphs in the + print job (e.g. the fonts will still appear correctly in the printout, + but the quality may be reduced since downloaded fonts are always better + than bitmap glyphs). + (users of xprint.mozdev.org-release <= 006 may see + <ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=2092">xprint.mozdev.org bug 2092</ulink> + if they use "xfs"; this has been fixed in the 007 release!) + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + What is a "model-config" ? + </para> + </question> + <answer> + <para> + The term "model-config" refers to the subdirs in + <filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/models/</filename>. + There subdirs contain information + about the attributes for a specific printer model or family/class of + printer models. In particular there are two kinds of information: + + <itemizedlist> + <listitem> + <para> + "<filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/models/${NAME_OF_MODEL}/model-config</filename>" + this file defines a set of attributes supported by this specific printer + (-family/-class/etc.) + and + </para> + </listitem> + <listitem> + <para> + "<filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/models/${NAME_OF_MODEL}/fonts/</filename>" - a + directory which contains a set of PMF (printer metrics file) fonts + builtin into the printer itself (actually the PMF "font" format + contains only metrics information and no glyphs). + These fonts are only available to the application <emphasis>after</emphasis> the + application has selected a printer and configured it (for developers: + After <function>XpSetContext</function> has been called). + </para> + </listitem> + </itemizedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Where can I store the default values for printers ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I create my own model-config ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I create my own PMF "fonts" ? + </para> + </question> + <answer> + <para> + XXX - no solution yet, but + <ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=2430">xprint.mozdev.org bug 2430 + ("RFE: Need tool to create PMF (printer metrics file) fonts")</ulink> + has been filed to create a freeware tool to create such fonts. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Where can I get more model-configs from ? + </para> + </question> + <answer> + <para> + If you miss a model-config for your printer please open a bug/RFE at + <ulink url="http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi?product=xprint&component=Server%3A+Config%3A+model-configs"> + http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi?product=xprint&component=Server%3A+Config%3A+model-configs</ulink> + (e.g. <ulink url="http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi">http://xprint.freedesktop.org/cgi-bin/bugzilla/enter_bug.cgi</ulink>, product "Xprint", component + "Server Config: model-configs"). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + If I install Xprt &co. as "root" in the default location and don't need + to set <envar>${XPCONFIGDIR}</envar> - where are my configuration files located then ? + </para> + </question> + <answer> + <para> + This is platform-specific, based on the "XPrintDir" Imake variable set + at build time. Default location for plain X11R6.x is + "<filename>${XProjectRoot}/lib/X11/xserver</filename>" (set at build time), but some + platforms modify "XPrintDir" to alternate locations: + <itemizedlist> + <listitem> + <para> + Solaris sets <envar>${XPCONFIGDIR}</envar> to <filename class="directory">/usr/openwin/server/etc/XpConfig/</filename> + </para> + </listitem> + <listitem> + <para> + Linux (non-Debian) sets <envar>${XPCONFIGDIR}</envar> to <filename>/usr/X11R6/lib/X11/xserver/</filename> + or <filename>/etc/X11/xserver/</filename> + </para> + </listitem> + <listitem> + <para> + Debian Linux sets <envar>${XPCONFIGDIR}</envar> to <filename>/usr/share/Xprint/xserver/</filename> + </para> + </listitem> + </itemizedlist> + <tip> + <para> + If you don't know where the default location for <envar>${XPCONFIGDIR}</envar> is + located try +<programlisting> + strings -a /usr/openwin/bin/Xprt | grep XPRINTDIR +</programlisting> - it <emphasis>may</emphasis> + return some debug info from the binary containing the builtin XpConfig + path. + </para> + </tip> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Are config files and/or the PMF fonts architecture dependent ? + </para> + </question> + <answer> + <para> + The PMF fonts are a variant of the PCF font format, they are + (like the PCF format) architecture-independent. + These fonts must be kept together with the other model config data since + they depend on the printer model (de facto + <filename><envar>${XPCONFIGDIR}</envar>/C/print/models/</filename> (and/or + <filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/models/</filename>) should be supplied by the printer + vendors (but most people will create their own models on demand since + I doubt that any vendor except HP, Sun and xprint.mozdev.org staff ever + looked at that stuff)). + Per definition they are read-only data supplied by the vendor, but + modifying them may be usefull, too. + I would say it is recommended to put treat all Xprint files in + <envar>${XPCONFIGDIR}</envar> as read-only vendor data; admins should create copies of + this tree on demand (and/or (soft-)link some files) and set + <envar>${XPCONFIGDIR}</envar> to the modified config data. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Can I localise my Xprint/Xprt configuration (l10n) ? + </para> + </question> + <answer> + <para> + Yes, Xprt supports localisation ("l10n") by default. Default values for + all locales are stored in <filename><envar>${XPCONFIGDIR}</envar>/C/print/</filename>, locale-specific + settings can be set in <filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/</filename> + Rules: + <itemizedlist> + <listitem> + <para> + Attribute pools + ("<filename><envar>${XPCONFIGDIR}</envar>/*/print/attributes/document</filename>", + "<filename><envar>${XPCONFIGDIR}</envar>/*/print/attributes/job</filename>", + "<filename><envar>${XPCONFIGDIR}</envar>/*/print/attributes/printer</filename>" and + "<filename><envar>${XPCONFIGDIR}</envar>/*/print/models/*/model-config</filename>"): + "document", "job" and "printer" attribute pools and printer + model-configs are sourced first from the + "<filename><envar>${XPCONFIGDIR}</envar>/C/print/</filename>"-directory, then they are overridden by any + attributes from the locale-specific pools (in + "<filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/</filename>"), e.g. any values set in + "<filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/*</filename>" and + "<filename><envar>${XPCONFIGDIR}</envar>/C/print/models/*/model-config</filename>" will automatically + apply to all other locales unless they are overridden by + locale-specific versions of these files + ("<filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/attributes/*</filename>", + "<filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/models/*/model-config</filename>") + </para> + </listitem> + <listitem> + <para> + "Xprinters" (list of printers): + If there is a locale-specific <filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/Xprinters</filename> present + it will be used instead of <filename><envar>${XPCONFIGDIR}</envar>/C/Xprinters</filename> (e.g. values set + in <filename><envar>${XPCONFIGDIR}</envar>/C/Xprinters</filename> will be ignored and the values from + <filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/Xprinters</filename> will be used instead). + </para> + </listitem> + <listitem> + <para> + Xprt will determinate the locale which should be used based on the + <envar>${LANG}</envar>-environment vaiable at startup time. If there is no such + variable set at that time LANG="C" is assumed. + <note> + <title>Note:</title> + <para> + Attribute values for paper names and orientation names refer to + builtin strings in the DDX code (which are itself based on + international standards), these cannot be changed to your own + "inventions" (it does it make sense to try to "localize" paper names - + "ISO-A4" is "ISO-A4" even in japanese/hebrew/german etc.). + Locale-spefific attribute pools can set their own, different values - + but only within the allowed range of values supported by the DDX and + printers's model-config. + </para> + </note> + </para> + </listitem> + </itemizedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Can I execute my own scripts to process the PostScript files generated + by Xprt ? + </para> + </question> + <answer> + <para> + Yes, there are at least two possible solutions: + <orderedlist> + <listitem> + <para> + Create your own model-config which uses a custom "xp-spooler-command" + value - the xprint.mozdev.org's + "PSspooldir" model config (see + "<filename><envar>${XPCONFIGDIR}</envar>/C/print/models/PSspooldir/</filename>" and + "<filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/printer</filename>" and + "<filename><envar>${XPCONFIGDIR}</envar>/C/print/Xprinters</filename>") + and + "PS2PDFspooldir-GS" model config (see + "<filename><envar>${XPCONFIGDIR}</envar>/C/print/models/PS2PDFspooldir-GS/</filename>" and + "<filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/printer</filename>" and + "<filename><envar>${XPCONFIGDIR}</envar>/C/print/Xprinters</filename>") + are good examples for that. + </para> + </listitem> + <listitem> + <para> + Use an existing "model-config" (which would normally send it's data to + a printer using the default print spooler command) and provide a + custom "xp-spooler-command". + <blockquote><procedure> + <title> + Example (using "SPSPARC2" as printer model, <filename>/w/xp_conv</filename> + as the script to execute and "myscriptprinter" as name of the printer): + </title> + <step> + <para> + Edit <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/printer</filename> and add these lines + (Xprt will replace "%printer-name%" with the printer's name, + "%copy-count%" with the number of job copies, "%job-name%" with the + job's title and "%options%" with any custom spooler options): +<screen> +myscriptprinter.xp-model-identifier: SPSPARC2 +myscriptprinter.xp-spooler-command: /w/xp_conv -p %printer-name% -c %copy-count% -t %job-name% -o "%options%" +</screen> + </para> + </step> + <step> + <para> + Edit <filename><envar>${XPCONFIGDIR}</envar>/C/print/Xprinters</filename> and append this line: +<screen> +Printer myscriptprinter +</screen> + </para> + </step> + </procedure></blockquote> + + </para> + </listitem> + </orderedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I disable "xp_ps_spooldir_tmp_Xprintjobs" / "xp_pdf_spooldir_tmp_Xprintjobs" printer targets ? + </para> + </question> + <answer> + <para> + Edit <filename><envar>${XPCONFIGDIR}</envar>/C/print/Xprinters</filename> and + remove or comment-out (using '#') the lines "Printer xp_ps_spooldir_tmp_Xprintjobs" + and "Printer xp_pdf_spooldir_tmp_Xprintjobs". + + <note> + <title>Note:</title> + <para> + Note that Xprt will <emphasis>NOT</emphasis> start if this printer has been removed/disabled + and no other print queue is available (e.g. if "xp_ps_spooldir_tmp_Xprintjobs" + and "Printer xp_pdf_spooldir_tmp_Xprintjobs" are the only printer target available). + </para> + </note> + </para> + </answer> +</qandaentry> + +</qandadiv> + + +<qandadiv id="faq_troubleshooting"> +<title>Troubleshooting</title> + +<qandaentry> + <question> + <para> + Xprt refuses to start with the message "sh: lpc: command not found" on + my Linux machine. What does that mean ? + </para> + </question> + <answer> + <para> + Some versions of Xprt look up printer queues using "lpc" on Linux. + In this case "lpc" cannot be found for some reason. + Solution: + Find the place where "lpc" is installed on your machine (some + distributions put it into <filename>/usr/sbin</filename>, some into <filename>/usr/bin/</filename>) and check + whether your <envar>PATH</envar> env var includes this directory. + Example (if "lpc" is located in <filename>/usr/sbin/</filename>): +<screen> + % <userinput>which lpc</userinput> + <computeroutput>/usr/sbin/lpc</computeroutput> + % <userinput>export PATH=$PATH:/usr/sbin</userinput> + # Start Xprt ... + % <userinput>Xprt <your-options-come-here></userinput> +</screen> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + When the application (=client side) tries to connect to the Xprt + (Xserver) side it fails with a +<screen> +<computeroutput>Xlib: connection to "meridian:52.0" refused by server +Xlib: Client is not authorized to connect to Server</computeroutput> +</screen> + What does that mean ? + </para> + </question> + <answer> + <para> + X11 implements access control. You can have host-based, cookie-based (a + "cookie" is used like a passport) or user-based (SecureRPC or Kerberos5) + authentification. <citerefentry><refentrytitle>Xsecurity</refentrytitle><manvolnum>__miscmansuffix__</manvolnum></citerefentry> + has most of the details. + <orderedlist> + <listitem> + <formalpara> + <title> + No access control: + </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>) + to disable the access control. + Example: +<screen> + % <userinput>Xprt -ac -audit 4 :12</userinput> +</screen> + will start Xprt with access control disabled and with auditing enabled + (e.g. the "-audit 4" option). + <warning> + <title> + WARNING + </title> + <para> + Disabling the access control will enable <emphasis>everyone</emphasis> who can + access Xprt to print on your printers (that's why the above example + shows how to use auditing, too - that you can see who does something + with Xprt...) !! + </para> + </warning> + </para> + </formalpara> + </listitem> + <listitem> + <formalpara> + <title> + Host-based access control: + </title> + <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> + manual page for further details)). + <blockquote><procedure> + <title>Example</title> + <step> + <para> + Add the following line to `<filename>/etc/X12.hosts</filename>' (assuming you want that + the hosts 'merkur' and 'mars' should be able to access the Xprt + server running as display 12 on your host 'neptun'): +<screen> +INET:merkur +INET:mars +</screen> + </para> + </step> + <step> + <para> + Start Xprt + </para> + </step> + <step> + <para> + Verify that Xprt is correctly configured: +<screen> +% <userinput>export DISPLAY=neptun:12</userinput> +% <userinput>xhost</userinput> +<computeroutput>access control enabled, only authorized clients can connect +INET:localhost +LOCAL: +INET:merkur +INET:mars</computeroutput> +</screen> + </para> + </step> + </procedure></blockquote> + </para> + </formalpara> + </listitem> + </orderedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Xprt refuses to start with the message "failed to set default font path + '...' Fatal server error: could not open default font 'fixed'". + What does that mean ? + </para> + </question> + <answer> + <para> + This means one or more components in the font path (set via the option + "-fp") are either... + <itemizedlist> + <listitem> + <para> + ... not valid + </para> + </listitem> + <listitem> + <para> + ... contain fonts not supported by this Xserver (e.g. support has not + be compiled "in" (usually happens for TrueType (which are only support for Solaris version + of Xprt and xprint.mozdev.org releases ≥ 008), OpenType (which are only supported by + xprint.mozdev.org releases 009 or higher) or F3 fonts (Sunsoft/F3 fonts are Solaris-specific + and <emphasis>not</emphasis> supported by other vendors (AFAIK)) + when support for these fonts was not enabled at build time)) + </para> + </listitem> + <listitem> + <para> + ... no font or font alias in the font path matches the name "fixed" + </para> + </listitem> + <listitem> + <para> + ... an entry in <filename>fonts.dir</filename> or <filename>fonts.alias</filename> + with the name "fixed" which references a non-existing or non-readable file + </para> + </listitem> + </itemizedlist> + + </para> + </answer> +</qandaentry> + + +<qandaentry> + <question> + <para> + Just copying my fonts into a directory and adding the path to my Xprt + command line didn't work - I always get "Fatal server error: could not + open default font 'fixed'". What am I doing wrong ? + </para> + </question> + <answer> + <para> + Every Xserver needs an index file called <filename>fonts.dir</filename> to tell it which + fonts are available in this directory and which properties these fonts + have. + </para> + <para> + If you are lucky there may be already a <filename>fonts.scale</filename> file which can be + used by "mkfontdir" to create the <filename>fonts.dir</filename> file. + If there is no <filename>fonts.scale</filename> then you have to create your own + <filename>fonts.dir</filename>/<filename>fonts.scale</filename> either by hand or + via tools like "mkfontscale" (works for all types of scaleable fonts), + "type1inst" (for PS Type1 fonts; see + <ulink url="http://packages.debian.org/stable/utils/type1inst.html">http://packages.debian.org/stable/utils/type1inst.html</ulink>) + or "ttmkfdir" (for TrueType fonts; see + <ulink url="http://packages.debian.org/stable/x11/ttmkfdir.html">http://packages.debian.org/stable/x11/ttmkfdir.html</ulink>). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Xprt refuses to start with the message "Fatal server error: Cannot + establish any listening sockets - Make sure an X server isn't already + running". What does that mean ? + </para> + </question> + <answer> + <para> + There is already a Xserver running at the display ID you have specified + to start Xprt (for example your framebuffer Xserver runs at ":0" then + Xprt can't run at the same display display). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Xprt refuses to start with the message "Fatal server error: Failed to + establish all listening sockets". What does that mean ? + </para> + </question> + <answer> + <para> + This means that the Xserver could not open one of it's sockets. Check + the permission of /tmp/.X11-pipe and /tmp/.X11-unix (on Solaris a + 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> + manual page for the side-effects of this option). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Xprt refuses to start with the message "Fatal server error: could not + open default font 'fixed'" or "Fatal server error: could not open default + cursor font 'cursor'". + </para> + </question> + <answer> + <para> + All Xservers at least two fonts as the minimum: One fixed-width font + ("fixed") and one font for the cursor ("cursor"). Be sure that the font + path contains these fonts. +<!-- XXX/FixMe: puck is dead, need replacement... ;-( + I created a tarball which contains only these two fonts, get it from + <ulink url="http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/Xp_dummyfonts.tar.gz"> + http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/Xp_dummyfonts.tar.gz</ulink> +--> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Xprt refuses to start with the message "Fatal server error: no screens + found". What does that mean ? + </para> + </question> + <answer> + <formalpara> + <title>Cause:</title> + <para> + This means that Xprt could not find any printers. Either there are no + printers installed, "lpstat"/"lpc" could not find any printers or the + configuration does not contain any manual printer configurations + (see Q/A item "Which program is used by default by Xprt to enumerate the + printers on my system" for further details...). + </para> + </formalpara> + + <formalpara> + <title>Solution:</title> + <para> + Two solutions: + <orderedlist> + <listitem> + <formalpara> + <title> + Using "PSspooldir" model: + </title> + <para> + Xprt releases from <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink> provide the "PSspooldir" + model config for such cases. Just edit the "<filename>Xprinters</filename>" file and add + this line: +<screen> +Printer xp_ps_spooldir_tmp_Xprintjobs +</screen> + this will add the pre-configured (see + <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/printer</filename>) "xp_ps_spooldir_tmp_Xprintjobs" + printer which will send jobs to the directory "/tmp/Xprintjobs/" + instead to a printer queue. + (This feature was added in the xprint.mozdev.org release 007, see + <ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=2475">xprint.mozdev.org bug 2475 ("RFE: Need + model-config which spools print jobs in a predefined directory")</ulink>.) + </para> + </formalpara> + </listitem> + <listitem> + <formalpara> + <title> + Manual setup (task list): + </title> + <para> + <blockquote> + <procedure> + <step> + <para> + Provide a simple "Xprinters" spec file which contains a dummy + queue. + Example: +<screen> +# Create "Xprinters_onlydummy" file which turns autolookup of printers +# OFF (using "Augment_Printer_List %none%") and provides one dummy +# queue called "ps_myscript" instead (using "Printer ps_myscript") +% <userinput>echo "Augment_Printer_List %none%" >Xprinters_onlydummy</userinput> +% <userinput>echo "Printer ps_myscript" >>Xprinters_onlydummy</userinput> +</screen> + </para> + </step> + <step> + <para> + Edit <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/printer</filename> and add these + two lines: +<screen> +ps_myscript.xp-model-identifier: PSdefault +ps_myscript.xp-spooler-command: /home/sanja/xprint_test/my_xprt_cat_script.sh +</screen> + This means that the printer "ps_myscript" now uses the "PSdefault" + printer model and it will feed the jobs to the script + "/home/sanja/xprint_test/my_xprt_cat_script.sh" (via stdin). + Note that the absolute path is required for "*xp-spooler-command". + </para> + </step> + <step> + <para> + Start Xprt on display 18, passing the "Xprinters_onlydummy" + using the "-XpFile" option: +<screen> +% <userinput>Xprt -XpFile ./Xprinters_onlydummy -pn -ac -audit 4 :18</userinput> +</screen> + </para> + </step> + </procedure> + </blockquote> + </para> + </formalpara> + </listitem> + </orderedlist> + </para> + </formalpara> + </answer> +</qandaentry> + +<qandaentry id="printout_only_covers_1_4_of_the_paper"> + <question> + <para> + "Printing itself works but the printout covers only 1/4 of the paper - what am I doing wrong ?" + </para> + </question> + <answer> + <para> + This is usually an indicator for a wrong DPI setting. The default + "PSdefault" model config uses 300 DPI but some printers only support + 600 DPI. + </para> + <formalpara> + <title>Workaround:</title> + <para> + Edit <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename> and replace the line + "*default-printer-resolution: 300" with + "*default-printer-resolution: 600" + (Note that locale-specific settings in + <filename><envar>${XPCONFIGDIR}</envar>/<envar>${LANG}</envar>/print/attributes/document</filename> always override values + set in <filename><envar>${XPCONFIGDIR}</envar>/C/print/attributes/document</filename>.) + </para> + </formalpara> + <formalpara> + <title>Solution:</title> + <para> + Create a model-config for your printer which only contains attributes + supported by your printer ("printer-resolutions-supported" is the + attribute in the "model-config" which holds the space-seperated list + of DPI values which are supported by the printer). + </para> + </formalpara> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + "Printing works but I get large borders/margins..." / "[Top] margin is too small" / + "Margins are wrong" / etc. + </para> + </question> + <answer> + <para> + Two possible causes: + <itemizedlist> + <listitem> + <para> + Usually same issue as "Printing itself works but the printout covers + only 1/4 of the page"-issue: Wrong DPI. + Solution: Check the DPI value and adjust it as described in the FAQ item + above. Common DPI values for the PostScript DDX are 240, 300, 360, 400 + and 600 DPI. + </para> + </listitem> + <listitem> + <para> + You are trying to print "US-letter" on a "DIN-A4" paper or "DIN-A4" on + "US-letter". + </para> + <para> + Solution: Check your paper settings + </para> + <para> + Note that the default papersize for Xprt depends on the locale + (e.g. on the env var <envar>${LANG}</envar>) Xprt is running in - "en_US"&co. get + US-letter, all others use DIN-A4 (incl. german/austrian etc. locales)). + Exception from this rule: If the selected printer does not support the + default paper size it will set no default paper size for this printer + (then the application side has to make an explicit choice). + </para> + </listitem> + </itemizedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Xprt prints a warning like "Xp Extension: could not find config dir + /usr/X11R6/lib/X11/C/print" - what does that mean ? + </para> + </question> + <answer> + <para> + This is actually the worst case what can happen. + The message indicates that Xprt was unable to find it's configuration + data. + </para> + <formalpara> + <title>Solution:</title> + <para> + Two solutions are possible: + <itemizedlist> + <listitem> + <para> + Install the configuration data at the requested location + (<filename>/usr/X11R6/lib/X11/C/print/</filename> in this example) + </para> + </listitem> + <listitem> + <para> + Set the <envar>${XPCONFIGDIR}</envar> env var to the location of the Xprt + configuration directory. + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Xprt crashes with "Fatal server error: Beziers this big not yet supported" + What does that mean ? + </para> + </question> + <answer> + <para> + This is a known issue in the X11R6.5.1 code. In rare cases some PostScript + Type1 fonts can trigger this. + See "My PS Type1 font does not work with my Xserver" ... + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + "My PS Type1 font does not work with my Xserver - how can I fix this ?" + </para> + </question> + <answer> + <para> + Some PS Type1 do not work out-of-the-box with all PS Type1 font engines - + some will work with the Adobe font engine (used in Solaris Xsun) but not + with the X.org font engine (or the other way round) or the fonts are + simply broken. + + The following procedure will try to fix this problem: + Get the "type1fix" perl script the TeXTrace package + (<ulink url="http://www.inf.bme.hu/~pts/textrace-latest.tar.gz">http://www.inf.bme.hu/~pts/textrace-latest.tar.gz</ulink>) + and run it over the fonts. + + Example 1 (filter fonts): +<screen> +# Broken PFA fonts are in broken_fonts/ +% <userinput>mkdir fixed_fonts ; cd fixed_fonts</userinput> +% <userinput>for i in ../broken_fonts/*.pfa ; do + echo " ------- $i" ; + type1fix.pl --ofmt=pfa --infile=$i --outfile=$(basename ${i}) ; + done</userinput> +</screen> + + Example 2 (filter fonts and convert them to PFB on-the-fly; do not forget + to update <filename>fonts.scale</filename> and run "mkfontdir" (to update <filename>fonts.dir</filename>) ; + systems which use the Adobe font engine (like Solaris/Xsun) may require + to run "makepsres", too): +<screen> +# Broken PFA fonts are in broken_fonts/ +% <userinput>mkdir fixed_fonts ; cd fixed_fonts</userinput> +% <userinput>for i in ../broken_fonts/*.pfa ; do + echo " ------- $i" ; + type1fix.pl --ofmt=pfb --infile=$i --outfile=$(basename ${i%.pfa}.pfb) ; + done</userinput> +</screen> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + I can't get it working. I have set <envar>${DISPLAY}</envar> correctly to point to the + Xprt display and... ... What is going wrong ? + </para> + </question> + <answer> + <para> + Do not set <envar>${DISPLAY}</envar> to the Xprt server. You still need your normal + Xserver for your video card - Xprt is only for your printer(s). + Applications look up Xprt servers via the <envar>${XPSERVERLIST}</envar> env var, <emphasis>NOT</emphasis> + via the <envar>${DISPLAY}</envar> env var. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + When I try to print via Xprint I get the message "Fatal server error: + unable to exec '/usr/bin/lp'". What is going wrong here ? + </para> + </question> + <answer> + <para> + This usually means that the spooler application "<filename>/usr/bin/lp</filename>" + could not be launched. This is usually the result when + <filename>/usr/bin/lp</filename> does not exist or + cannot be executed (for example, shell scripts without the +x (executable) flag etc.). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + The Solaris Xprt prints some error messages about PostScript fonts like + "FOOBAR not found, using Courier. CMEX0123 not found, using Courier." + etc. and uses "Courier" instead of these fonts... + </para> + </question> + <answer> + <formalpara> + <title>Cause:</title> + <para> + The Solaris (Adobe-based) PostScript font engine requires a "PostScript + resource database" file named "<filename>PSres.upr</filename>" to use the PostScript fonts + correctly. + </para> + </formalpara> + <formalpara> + <title>Solution:</title> + <para> + Create the missing <filename>PSres.upr</filename> database. + <blockquote> + <procedure> + <title>Steps to create the missing "<filename>PSres.upr</filename>" file (task list):</title> + <step> + <para> + Go to the location where the matching fonts are installed (we're using + <filename>/home/sanja/mathml_fonts/tex_cmps/Type1/</filename> in this example): +<screen> +% <userinput>cd /home/sanja/mathml_fonts/tex_cmps/Type1//</userinput> +</screen> + </para> + </step> + <step> + <para> + Create "<filename>PSres.upr</filename>" using the "makepsres" command. +<screen> +% <userinput>makepsres</userinput> +</screen> + </para> + </step> + <step> + <para> + Validation: + Make sure the file has been created: +<screen> +% <userinput>ls -l PSres.upr</userinput> +</screen> + </para> + </step> + <step> + <para> + Restart Xprt server(s): +<screen> +% <userinput>/etc/init.d/xprint restart</userinput> +</screen> + </para> + </step> + <step> + <para> + Restart application which uses these fonts + </para> + </step> + </procedure> + </blockquote> + </para> + </formalpara> + <formalpara> + <title>References:</title> + <para> + <itemizedlist> + <listitem><para><citerefentry><refentrytitle>makepsres</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page</para></listitem> + <listitem><para><ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=120560">bugzilla.mozilla.org 120560 ("Solaris Xsun does not like CMEX10/CMSY10 Type1 fonts")</ulink></para></listitem> + <listitem><para><ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=142718">bugzilla.mozilla.org 142718 ("Document how to get the MathML fonts to work on Solaris")</ulink></para></listitem> + </itemizedlist> + </para> + </formalpara> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + "Xprt refused to start, complaining about a missing dir + (<filename>/etc/X11/xserver/C/print/</filename> directory)... I created it by hand (empty) and + started Xprt but it still does not work properly..." + </para> + </question> + <answer> + <para> + Xprt expects some config data in this directory. Just making it an + existing but empty dir will work around the error message but will not + result in a properly working Xprt since it has no (usefull) builtins + which would make it possible to run the binary without the config data. + Your X11 binary distribution should always come with the config data + (for example <filename>/usr/openwin/server/etc/XpConfig/</filename> on Solaris) or you will not + be able to use Xprint (however it is possible to copy the config data + from another system :) + BTW: Source for the configs can be found under <filename>xc/programs/Xserver/XpConfig/</filename> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + My Linux system already shipps with a '<filename>/usr/X11R6/bin/Xprt</filename>'-binary. + Do I need the binary distribution from <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink> ? + </para> + </question> + <answer> + <para> + This depends on what is shipped with your Linux distribution. + Please check the "vendor" string of the Xprt server: +<screen> +% <userinput>Xprt :10 &</userinput> +% <userinput>xdpyinfo -display :10 | grep -i "vendor string"</userinput> +</screen> + If this outputs a line like "vendor string: The XFree86 Project, Inc" + then you have the Xprt binary build from Xfree86 sources - which are + broken - even the newest version [I'll update this as soon as Xfree86 + shipps with a working version]. + Xprt from Solaris, HP-UX and my own builds (which identifies itself as + "vendor string: xprint.mozdev.org" for releases >= 007, older releases + (e.g. <= 006) identify itself as as "vendor string: The X.Org Group") + are known to work proprtly. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + I am getting the error message "error opening security policy file + /usr/X11R6/lib/X11/xserver/SecurityPolicy". What does that mean ? + </para> + </question> + <answer> + <para> + The policy file for the SECURITY extension cannot be found. + This is not serious unless you want to make use of features of the + SECURITY extensions (like treating clients as "untrusted", e.g. restrict + their access to certain Xserver resources). + Normally the missing policy file is a problem with your Unix/Linux X11 + distribution; consult your vendor where to get the missing file from. + Alternatively you can get the plain X11R6.6 security policy file from + <ulink url="ftp://ftp.x.org/pub/R6.6/xc/programs/Xserver/Xext/SecurityPolicy">ftp://ftp.x.org/pub/R6.6/xc/programs/Xserver/Xext/SecurityPolicy</ulink> + (copy it to the matching location - but be sure that you do not overwrite any + existing security policy file). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + I have modified the "HPLJ4family" [or "HPDJ1600C" etc.] printer model to + work with my PostScript printer, but when I print I get empty places + where some text should be - what am I doing wrong here ? + </para> + </question> + <answer> + <para> + The "HPLJ4family" and "HPDJ1600C" models are PCL-only, check + the model-config spec + (<filename><envar>${XPCONFIGDIR}</envar>/C/print/models/${MODEL_NAME}/model-config</filename>) - if the + "xp-ddx-identifier" attribute says something with "PCL" (like + "XP-PCL-MONO" etc.) in the value string then this model-config is for + the PCL-DDX <emphasis>only</emphasis> (e.g. their PMF fonts do not supply the neccesary + information (e.g. the "_ADOBE_POSTSCRIPT_FONTNAME" chunk is missing; + they only provide the "PCL_FONT_NAME" chunk) nor are these fonts + accessible via the PostScript-support in these printers. + A solution is to use the "PSdefault" model instead (and/or create your + customized own version of this model) - or look if there is a + model-config beginning with the same name and ending with "PS" (e.g. + "HPLJ4family-PS"). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Xprt outputs warning messages like: +<screen> +<computeroutput> +Xp Extension: Can't load driver XP-PCL-MONO + init function missing +Xp Extension: Can't load driver XP-RASTER + init function missing +</computeroutput> +</screen> + What does that mean ? + </para> + </question> + <answer> + <para> + Two possible problems: + <orderedlist> + <listitem> + <para> + The requested driver is not supported by that version of Xprt. + For example Solaris 2.7 Xprt does not support XP-PCL-MONO nor the + XP-RASTER driver. + Valid values for the "xp-ddx-identifier" attribute in + <filename><envar>${XPCONFIGDIR}</envar>/*/print/attributes/printers</filename> and/or + <filename><envar>${XPCONFIGDIR}</envar>/*/print/models/*/model-config</filename> are + <itemizedlist> + <listitem> + <para> + Solaris 2.7: XP-POSTSCRIPT and XP-PCL-COLOR + </para> + </listitem> + <listitem> + <para> + Solaris >=2.8: XP-POSTSCRIPT, XP-PCL-COLOR, XP-PCL-MONO and XP-RASTER + </para> + </listitem> + <listitem> + <para> + HP-UX: XP-POSTSCRIPT, XP-PCL-COLOR, XP-PCL-MONO, XP-PCL-LJ3, + XP-PCL-DJ1200 and XP-RASTER + </para> + </listitem> + <listitem> + <para> + xprint.mozdev.org release 007: XP-POSTSCRIPT and XP-RASTER + </para> + </listitem> + <listitem> + <para> + xprint.mozdev.org release 008: XP-POSTSCRIPT, XP-PCL-COLOR, + XP-PCL-MONO, XP-PCL-LJ3 and XP-RASTER + </para> + </listitem> + <listitem> + <para> + xprint.mozdev.org release >=2.0 (planned): XP-POSTSCRIPT, XP-PCL-COLOR, + XP-PCL-MONO, XP-PCL-LJ3, XP-RASTER, XP-PDF and XP-SVGPRINT. + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + <listitem> + <para> + There may be too many drivers loaded into one Xprt instance. + By default a single Xserver instance can only handle three screens - and + since one Xprint DDX maps to one Xserver screen this limit applies to + the number of loaded Xprt drivers, too. + Starting with xprint.mozdev.org release 008 the per-Xserver screen limit + was increased from "3" to "8" to avoid this issue... + Workaround: Start a 2nd instance of Xprt which handles the other + drivers which do not fit into the first instance. + </para> + </listitem> + </orderedlist> + </para> + </answer> +</qandaentry> + +<qandaentry id="bug_solaris_xprt_removes_spaces_between_words"> + <question> + <para> + Printing on Solaris with Mozilla/Eclipse [or any other Xprint client] + removes spaces between words. What is going wrong ? + </para> + </question> + <answer> + <formalpara> + <title>Cause:</title> + <para> + This is a bug in the Solaris Xprint server binary (<filename>/usr/openwin/bin/Xprt</filename>). + Various bug reports have been filed, see + <itemizedlist> + <listitem> + <para> + <ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353">xprint.mozdev.org bug 3353 + ("Solaris Xprt looses space when rendering with '-monotype-arial-*'-fonts")</ulink> + </para> + </listitem> + <listitem> + <para> + <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=199957">bugzilla.mozilla.org bug 199957 ("Solaris 8 Mozilla + removes spaces for text within <font face="Arial">...</font>"</ulink>) + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> + + <formalpara> + <title>Solution:</title> + <para> + Solution: + Please apply the following OS patches from <ulink url="http://sunsolve.sun.com/">http://sunsolve.sun.com/</ulink>: + <table frame="all" orient="port" tocentry="1"> + <title> + Solaris patches to fix <ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353">xprint.mozdev.org bug 3353 + ("Solaris Xprt looses space when rendering with '-monotype-arial-*'-fonts")</ulink> + </title> + <tgroup cols="6" colsep="1" rowsep="1"> + <colspec colname="col_s27_sparc" /> + <colspec colname="col_s27_x86" /> + <colspec colname="col_s28_sparc" /> + <colspec colname="col_s28_x86" /> + <colspec colname="col_s29_sparc" /> + <colspec colname="col_s29_x86" /> + <spanspec spanname="span_s27" namest="col_s27_sparc" nameend="col_s27_x86" align="center" /> + <spanspec spanname="span_s28" namest="col_s28_sparc" nameend="col_s28_x86" align="center" /> + <spanspec spanname="span_s29" namest="col_s29_sparc" nameend="col_s29_x86" align="center" /> + <thead> + <row> + <entry spanname="span_s27">Solaris 2.7</entry> + <entry spanname="span_s28">Solaris 2.8</entry> + <entry spanname="span_s29">Solaris 2.9</entry> + </row> + <row> + <entry>SPARC</entry> + <entry>x86</entry> + <entry>SPARC</entry> + <entry>x86</entry> + <entry>SPARC</entry> + <entry>x86</entry> + </row> + </thead> + <tbody> + <row> + <entry><link linkend="bug_solaris_xprt_removes_spaces_between_words_s27_no_patches_yet">n/a</link></entry> + <entry><link linkend="bug_solaris_xprt_removes_spaces_between_words_s27_no_patches_yet">n/a</link></entry> + + <entry><ulink url="http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=108652&collection=fpatches">108652-73</ulink></entry> + <entry><ulink url="http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=108653&collection=fpatches">108653-62</ulink></entry> + + <entry><ulink url="http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=112785&collection=fpatches">112785-21</ulink></entry> + <entry><ulink url="http://sunsolve.sun.com/pub-cgi/retrieve.pl?patchid=112786&collection=fpatches">112786-11</ulink></entry> + </row> + </tbody> + </tgroup> + </table> + + <note id="bug_solaris_xprt_removes_spaces_between_words_s27_no_patches_yet"> + <para> + For Solaris 2.7 (both SPARC and x86 platforms) there are currently + <ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353#c24">no patches available</ulink>... + <literal>;-(</literal> + </para> + </note> + </para> + </formalpara> + + <formalpara> + <title>Known workarounds:</title> + <para> + <itemizedlist> + <listitem> + <para> + Remove the '-monotype-arial-*' fonts from the font path + </para> + </listitem> + <listitem> + <para> + Use an alternate Xprint server like available in the "GISWxprint" package + (this package is identical to the "GISWxprintglue" package except that it + uses a Xprint server build from xprint.mozdev.org sources and not the + <filename>/usr/openwin/bin/Xprt</filename> binary from Solaris) + </para> + </listitem> + <listitem> + <para> + Mozilla-only: Adding +<programlisting role="javascript"> + user_pref("print.xprint.font.rejectfontpattern", + "fname=-dt-.*;scalable=.*;outline_scaled=false;xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*|" + + "fname=-monotype-arial.*;scalable=.*;outline_scaled=.*;xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*"); +</programlisting> + to <filename>prefs.js</filename> works around the problem (see + <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=199957#c6">bugzilla.mozilla.org bug 199957 comment #6</ulink>, + too). + <note> + <para> + Note that this workaround may render various locales completly + inaccessible for printing since many of them only employ MonoType fonts. + </para> + </note> + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> + + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Installation of the "GISWxprint" / "GISWxprintglue" packages fails like this: +<screen># <userinput>pkgadd -d /space/staging/xprint/GISWxprint.pkg</userinput> +<computeroutput>pkgadd: ERROR: no packages were found in </var/tmp/dstreAAA5Jayyz></computeroutput></screen> + Any idea what I am doing wrong ? + </para> + </question> + <answer> + <para> + The target machine misses a patch to cure SunSolve bug 4025718 ("pkginfo: allow greater than nine characters for PKG parameter value"). + Please apply the patches listed in the "Installation Requirements" section in the README + for the <ulink url="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/packager/solaris/GISWxprint/README">GISWxprint</ulink> / + <ulink url="http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/packager/solaris/GISWxprintglue/README">GISWxprintglue</ulink> package. + </para> + </answer> +</qandaentry> + + +<qandaentry id="multiple_leading_blank_pages"> + <question> + <para> + Printing page results in [two/three/.../16] leading blank pages, followed by a correct (but offset) page. + Any idea what is going wrong ? + </para> + </question> + <answer> + <para> + This symptom depends on the CUPS GhostScript driver used, however the exact cause is currently unknown + (see comments in <ulink url="http://sdb.suse.de/en/sdb/html/jsmeix_print-81-cups-formfeed.html">SuSE + support database entry SDB-2002/11/jsmeix_print-81-cups-formfeed ("Blank Pages When Printing with + CUPS")</ulink>). + </para> + <formalpara> + <title>Solution:</title> + <para> + Disable the CUPS accounting functionality in the cupsomatic filter by changing the line +<programlisting> + my $ps_accounting = 1; +</programlisting> + to +<programlisting> + my $ps_accounting = 0; +</programlisting> + in the filter script <filename>/usr/lib/cups/filter/cupsomatic</filename> as the user root. + If you use <filename>/etc/foomatic/filter.conf</filename>, disable ps_accounting there. + </para> + </formalpara> + <formalpara> + <title>References:</title> + <para> + <itemizedlist> + <listitem><para><ulink url="http://sdb.suse.de/en/sdb/html/jsmeix_print-81-cups-formfeed.html">SuSE support database entry SDB-2002/11/jsmeix_print-81-cups-formfeed ("Blank Pages When Printing with CUPS")</ulink></para></listitem> + <listitem><para><ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=4181">xprint.mozdev.org bug 4181 ("Two empty pages printed first")</ulink></para></listitem> + <listitem><para><ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=180602#c7">bugzilla.mozilla.org bug 180602 comment #7 ("Printing page results in 16 leading blank pages, followed by a correct, but offset, page")</ulink></para></listitem> + </itemizedlist> + </para> + </formalpara> + </answer> +</qandaentry> + +</qandadiv> + + +<qandadiv id="faq_development"> +<title>Software development</title> + +<qandaentry> + <question> + <para> + How does the X print server (Xprt) and the Xlib client side differ + from the "normal" video Xserver/video client side ? + </para> + </question> + <answer> + <para> + The X Print Service expands on the traditional X-Server and Xlib world + in the following 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 (<link linkend="what_does_pdl_mean">PDL</link>)" output (such as PCL, PDF, PostScript, SVGprint, etc.) + or sends the print rendering instructions to a platform-specific + print API (like Win32/GDI). + </para> + <para> + Once a print ddx driver generates <link linkend="what_does_pdl_mean">PDL</link> output, it can be sent to + a spooler + (using <function>XpuStartJobToSpooler</function>) + or retrieved by the client (to implement functionality like "print-to-file" + with functions such as <function>XpuStartJobToFile</function>). + </para> + </listitem> + <listitem> + <para> + Since printers support "paged" output, unlike video, a portion + of the Xp Extension supports APIs to delineate printed output + into a print job. + </para> + <para> + A "print job" in Xprint consists of one or more "documents" which itself + consists of one or more "pages". + </para> + + <para> + A client starts a job sequence with <function>XpStartJob</function> and + ends it with <function>XpEndJob</function> or <function>XpCancelJob</function> to cancel the + generation of the current print job. + Any document-specific print attributes MUST be changed before <function>XpStartJob</function>. + </para> + + <para> + A client starts a document sequence with <function>XpStartDoc</function> and + ends it with <function>XpEndDoc</function> or <function>XpCancelDoc</function> to cancel the + generation of the current document. + Any document-specific print attributes MUST be changed before <function>XpStartDoc</function> + or after <function>XpEndDoc</function> (to affect the following document). + </para> + + <para> + A client starts a page sequence with <function>XpStartPage</function> and + ends it with <function>XpEndPage</function> or <function>XpCancelPage</function> to cancel the + generation of the current page. + Any page-specific print attributes MUST be changed before <function>XpStartDoc</function> + or after <function>XpEndDoc</function> (to affect the following document). + </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> + <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 rendering calls use the resolution of the current page + (or if not given, the resolution of the current document or + the current resolution for this print job). + The screen's resolution is INVALID in this case. + XprintUtils has the functions <function>XpuGetResolution</function> + (to get the current print resolution (searching page, document and + job level attributes (in that order)), <function>XpuSetPageResolution</function> + (to set the current page resolution), <function>XpuSetDocResolution</function> + (to set the current document resolution), <function>XpuGetResolutionList</function> (to + get the list of all resolutions supported by this printer) and <function>XpuFindResolution</function> + (to find a resolution in the list returned by <function>XpuGetResolutionList</function>) + to support getting/setting/queries of resolutions. + </para> + <para> + When a print context is created and set for a given printer, + the X image rendering calls (such as <function>XPutImage</function> support + scaling of images. + The Xp Extension API provides the functions <function>XpSetImageResolution</function> + and <function>XpSetImageResolution</function> to set and get an image resolution. + The scaling factor for an image printed on the paper can simply calculated via + <!-- inlineequation would be better --> + <literal>scaling_factor = curr_print_resolution_resolution / image_resolution</literal> + where <varname>curr_print_resolution_resolution</varname> is the value returned by a function such as + <function>XpuGetResolution</function>, <varname>image_resolution</varname> the resolution passed to + <function>XpSetImageResolution</function> and <varname>scaling_factor</varname> the resulting scaling factor. + Note that <function>XpSetImageResolution</function> will failure (=FALSE) when the print DDX + (for example the RASTER DDX) does not support scaling. + In that case the application has to scale the image manually. + </para> + </listitem> + </orderedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I get the printable area (e.g. the portion of the page on which + the printer is physically capable of placing ink) of the paper after I + have chosen a paper ? + </para> + </question> + <answer> + <para> + The <function>XpGetPageDimensions</function> function returns the printable area and other information + about the current page geometry. + Note that the page geometry changes when the page attributes such as <literal>content-orientation</literal> + or <literal>default-medium</literal> are changed by the application. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Do "offscreen" pixmaps work on Xprt ? + </para> + </question> + <answer> + <para> + Yes, "offscreen" pixmaps are working on Xprt. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I get the DPI value for the current Xprt server ? Can I use the + values from "xdpyinfo" ? + </para> + </question> + <answer> + <para> + The Xprt screen resolution defines only the maximum resolution configured + for the matching DDX, the printers real DPI is obtained via an another + API (XprintUtil has a bunch of functions to get/set the document/page + resolution, see <function>XpuGetResolutionList</function>, <function>XpuFreeResolutionList</function>, + <function>XpuGetResolution</function>, <function>XpuSetPageResolution</function>, + <function>XpuSetDocResolution</function> and <function>XpuFindResolution</function>). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Why does Xprt not offer the MIT-SHM protocol extension ? + </para> + </question> + <answer> + <para> + The MIT-SHM protocol extension is partially (<function>XShmPutImage</function> would work, + but others like <function>XShmGetImage</function> and esp. <function>XShmCreatePixmap</function> + cannot be implemented properly) incompatible to the way how some of the Xprint DDX are implemented. + For example the PostScript, PDF, PCL and SVGprint DDX do not rasterize any images on their side - instead they convert the + stream of X11 rendering instructions into the matching <link linkend="what_does_pdl_mean">PDL</link> instruction stream. + Only the printer side will (finally) do the rasterisation of the output image. This is the basically the same reason why + <link linkend="why_does_xgetimage_not_work"><function>XGetImage</function> does not work for those DDXs</link> - and + functions such as <function>XShmCreatePixmap</function> would be useless since drawing operations on the shared + pixmap would not be applied to the application (e.g. Xprint client) as well. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Does Xprint/Xprt support font rotation ? + </para> + </question> + <answer> + <para> + Yes - Xprint/Xprt supports font rotation at any angle via the matrix XLFD + enhancement (this even works for printer-builtin fonts !!). For details + see the paper "New Font Technology for X11R6" by Nathan Meyers (a copy can be found in the + Xprint.org source tree under <filename>xc/doc/hardcopy/XLFD/x11r6_fonts_94_paper.PS.gz</filename>) + </para> + <para> + Short: + The transformation-matrix for rotation can be calculated like this: +<programlisting> ++-- --+ +| cos(angle) sin(angle)| +| | +|-sin(angle) cos(angle)| ++-- --+ +</programlisting> + Examples: + <orderedlist> + <listitem> + <para> + the following code fragment obtains a 180 degree rotated font (matrix [-1 0 0 -1]): +<programlisting> + ... = XLoadQueryFont(..., "-adobe-courier-bold-r-normal--*-[~24 0 0 ~24]-0-0-m-*-iso8859-1"); +</programlisting> + </para> + </listitem> + <listitem> + <para> + the following code fragment obtains a 90 degree rotated font (matrix [0 1 -1 0]): +<programlisting> + ... = XLoadQueryFont(..., "-adobe-courier-bold-r-normal--*-[0 24 ~24 0]-0-0-m-*-iso8859-1"); +</programlisting> + </para> + </listitem> + </orderedlist> + </para> + <para> + Future versions of Xprint will support the <ulink url="http://stsf.sourceforge.net/">STSF</ulink> + font API which supports matrix transformations as well. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + When I render something on my window and call <function>XpStartPage</function> all the + rendered stuff is gone, I only get a white, empty paper. + What is going wrong here ? + </para> + </question> + <answer> + <para> + Remember the rule that "only those drawings are printed on the paper which + were rendered between <function>XpStartPage</function> and <function>XpEndPage</function>". + <function>XpStartPage</function> clears the window you passed as argument, e.g. it creates + a new, blank sheet of paper where you can do your rendering stuff on. + <function>XpEndpage</function> then pushes the "paper sheet" to the stash of papers from the + document in process. + + <tip> + <para> + If you want to render something once for multiple or all pages: + Render on a offscreen pixmap and copy (with <function>XCopyArea</function>) the content to + the "paper" drawable (after calling <function>XpStartPage</function>) - <function>XpStartpage</function> only + affects the window passed as parameter. + </para> + </tip> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + What is <function>XpStartDoc</function> for ? + </para> + </question> + <answer> + <para> + ISO 10175 and some advanced printing systems by IBM and HP had set forth + the standard that a "Job" is made up of one or more "Documents", and + each document is made up of one or more "Pages". Xprint was designed that + in a true ISO 10175 environment/implementation (<citerefentry><refentrytitle>lp</refentrytitle><manvolnum>1</manvolnum></citerefentry> on steroids, and + with an API), Xprt can actually learn about all printers and their + capabilities though API's into the printer subsystem (vs. using config + files), map Job/Doc/Page directly into ISO 10175 equivalents, and use + APIs to view job status and kill jobs (vs. + <citerefentry><refentrytitle>cancel</refentrytitle><manvolnum>1</manvolnum></citerefentry>, + <citerefentry><refentrytitle>lpcancel</refentrytitle><manvolnum>1</manvolnum></citerefentry>, + <citerefentry><refentrytitle>lpstatus</refentrytitle><manvolnum>1</manvolnum></citerefentry>). + Because most applications of the day are only printing one document per + job, <function>XpStartPage</function> was designed that it generates a "synthetic" + <function>XpStartDoc</function> if it has not been called yet. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How does the XLFD for printer-builtin fonts look like ? / How can I find/identify printer-builtin fonts ? + </para> + </question> + <answer> + <para> + There is no special XLFD scheme for printer-builtin fonts. + Instead the <literal>xp-listfonts-modes-supported</literal> is used to define + whether <function>XListFonts</function> and co. return printer-builtin fonts or not. + By default the attribute looks is set to + <literal>*xp-listfonts-modes-supported: xp-list-internal-printer-fonts xp-list-glyph-fonts</literal> which defines + thaht <function>XListFonts</function> and co. return both printer-builtin and normal fonts. + Removing <literal>xp-list-internal-printer-fonts</literal> will make printer-builtin fonts disappear, + removing <literal>xp-list-glyph-fonts</literal> will make normal glyph fonts disappear from font lists. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I scale images using the Xprint API ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Can I pass my own PostScript code (fragment) to the print spooler instead of letting + Xprt's PostScript DDX generate it ? + </para> + </question> + <answer> + <para> + XXX <!-- use XpPutDocumentData --> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + When I use <function>XpPutDocumentData</function> I get a + <literal>BadValue</literal> X protocol error. Any idea what am I doing wrong ? + </para> + </question> + <answer> + <para> + XXX + <!-- references: bugzilla.mozilla.org bug and xprint.mozdev.org bug about the case sensitivy --> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How do I use the XprintUtil library ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry id="why_does_xgetimage_not_work"> + <question> + <para> + Why does the <function>XGetImage</function> not work for Xprt ? + </para> + </question> + <answer> + <para> + There are at least three reasons why <function>XGetImage</function> does not work for Xprt: + <orderedlist> + <listitem> + <para> + Most of the Xprt DDX implementations do not render itself on any + bitmaps like the framebuffer(=video) DDX do, they translate the + rendering commands into the matching commands of the printer language + (it is technically possible to implement such support for <function>XGetImage</function> + even for those drivers - but there are more reasons:) + </para> + </listitem> + <listitem> + <para> + Xprt usually operates at high resolutions which results in very large + dimensions. If a client would request the 24bit TrueColor <emphasis>bitmap</emphasis> + data for a <emphasis>whole</emphasis> DIN-A4 page at 2400 DPI a data chunk of ~173 + megabytes would be the response. This would be more or less a + DOS(=Denial of Service) for either the client, the network and/or the + server. + </para> + </listitem> + <listitem> + <para> + The printer-builtin fonts only provide metrics information - there is no real "outline" + information at that time (these fonts reside only in the printer's ROM and are only + available at the time the printer rasterizes the incoming <link linkend="what_does_pdl_mean">PDL</link> + (e.g. PCL/PostScript) data stream) which could be used to rasterize the matching glyphs + (which means: A <function>XGetImage</function> implementation would return image + data but glyphs rendered using the printer-builtin fonts would be missing). + </para> + </listitem> + </orderedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How to print with Xt/Athena widgets ? + </para> + </question> + <answer> + <para> + There are two examples in the Xprint.org source tree which demonstrate how to use Xprint using + Athena widgets: + <orderedlist> + <listitem> + <para> + <filename>xc/programs/xphelloworld/xpawhelloworld/</filename> contains a simple + demo application which prints a Athena widget using the <function>XawPrintShell</function> widget class. + </para> + </listitem> + <listitem> + <para> + <filename>xc/programs/xphelloworld/xpxthelloworld/</filename> contains a simple + demo application which prints a Athena widget without using a special print + widget class (however, if possible a print shell such as <function>XawPrintShell</function> or + <function>XmPrintShell</function> should be used since this is the easier way to add print + support to an Athena application). + </para> + </listitem> + </orderedlist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How to print with Xt/Motif widgets ? + </para> + </question> + <answer> + <para> + The Xprint.org source tree contains the xpxmhelloworld (xc/programs/xphelloworld/xpxmhelloworld/) + application to demonstrate how to print using the Motif2 toolkit. + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + What are the differences between normal display and Xprint display ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How do I scale images ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + libXp Image scaling vs. max. request size ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How can I use XprintUtils ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How do I calculate the DPI values for Xprt DDX screens ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How do I find scaleable fonts ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + How do I find printer-builtin fonts ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + The XLFD for Printer-builtin fonts look like bitmap fonts - is that bad ? + </para> + </question> + <answer> + <para> + No, this is not "bad". The XLFD of a printer-builtin font only looks like a bitmap font since + the *.pmf (Printer metrics file) format is a PCF file format variant (the DPI values in the XLFD + 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). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + When printing using the <function>XawPrintShell</function>/<function>XmPrintShell</function> print shells my PostScript output + is always corrupt. What am I doing wrong ? + </para> + </question> + <answer> + <para> + Make sure the widgets (such as text input widgets) have the (blinking) cursor turned-off. + Setting the <literal>XmNcursorPositionVisible,</literal> to <literal>False</literal> usually + solves the problem (for Motif2 widgets). + Example: + <informalexample> +<programlisting> +... +XtSetArg(args[n], XmNcursorPositionVisible, False); +... +</programlisting> + </informalexample> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + When printing using the <function>XawPrintShell</function>/<function>XmPrintShell</function> + print shells I always get a grey/dithered background on paper. + Any idea how to change that to "white" ? + </para> + </question> + <answer> + <para> + XXX + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Are there any caveats/suggestions when printing via Xt/Motif2 widgets ? + </para> + </question> + <answer> + <para> + There are a couple of Xt resources which may likely differ from the normal values (e.g. those values + used for a video Xserver): + <variablelist> + <varlistentry> + <term><literal>Core</literal> class level</term> + <listitem> + <para> + <variablelist> + <varlistentry> + <term><literal>XmNbackground</literal> resource</term> + <listitem> + <para> + The application will probably want to set the <literal>XmNbackground</literal> resource + to "white" to match the default paper color. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><literal>XmNborderWidth</literal> resource</term> + <listitem> + <para> + The application will probably want to set the <literal>XmNborderWidth</literal> resource + to "0" (usually the default value) to avoid that a black border appears around the widget. + </para> + </listitem> + </varlistentry> + </variablelist> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><function>XmPrimitive</function> class</term> + <listitem> + <para> + <variablelist> + <varlistentry> + <term><literal>XmNshadowThickness</literal> and <literal>XmNhightlightThickness</literal> resources</term> + <listitem> + <para> + The application will probably want to set <literal>XmNshadowThickness</literal> and + <literal>XmNhightlightThickness</literal> to "0" (usually the default value) to avoid + 3D border effects on the printout (depends on application and author's preference... + <literal>:-)</literal>). + </para> + </listitem> + </varlistentry> + </variablelist> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><function>XmText</function> and <literal>XmTextField</literal> classes</term> + <listitem> + <para> + <variablelist> + <varlistentry> + <term><literal>XmNcursorPositionVisible</literal> resource</term> + <listitem> + <para> + The application will probably want to set <literal>XmNcursorPositionVisible</literal> + to <literal>False</literal> to avoid that the cursor is visible on printouts (and to avoid + problems with some nasty implementation details which may cause corrupted PostScript output). + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><literal>XmNscrollHorizontal</literal> and <literal>XmNscrollVertical</literal> resources</term> + <listitem> + <para> + The application will probably want to set the <literal>XmNscrollHorizontal</literal> and + <literal>XmNscrollVertical</literal> resources to <literal>False</literal> to suppress printing + of scrollbars (on paper "scrolling" is replaced with "pagination" except for rare exceptions + (like 1:1 WYSIWYG-printing)). + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><literal>XmNmarginWidth</literal> and <literal>XmNmarginHeight</literal> resources</term> + <listitem> + <para> + The application will probably want to recalculate the <literal>XmNmarginWidth</literal> and + <literal>XmNmarginHeight</literal> resources based on the (far) higher print resolution + (or reverse: set them to "0" - depending on what style matches + the application needs better...). + </para> + </listitem> + </varlistentry> + </variablelist> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><function>XmLabel</function> class</term> + <listitem> + <para> + <variablelist> + <varlistentry> + <term><literal>XmNmarginTop</literal>, <literal>XmNmarginBottom</literal>, + <literal>XmNmarginRight</literal>, <literal>XmNmarginLeft</literal>, + <literal>XmNmarginWidth</literal>, <literal>XmNmarginHeight</literal> and + <literal>XmNalignment</literal> resources</term> + <listitem> + <para> + The application will probably want to use different value for <literal>XmLabel</literal> class's + <literal>XmNmarginTop</literal>, <literal>XmNmarginBottom</literal>, <literal>XmNmarginRight</literal>, + <literal>XmNmarginLeft</literal>, <literal>XmNmarginWidth</literal>, <literal>XmNmarginHeight</literal> and + <literal>XmNalignment</literal> resources. These resources are mainly usefull when the widget holds a + border, highlight or shadow of some kind. If borders are not to be transferred there is no real need to transfer + a margin either. + </para> + </listitem> + </varlistentry> + </variablelist> + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <para> + Can I change the paper size/resolution/page orientation/etc. when printing using the + <function>XawPrintShell</function>/<function>XmPrintShell</function> print shells ? + </para> + </question> + <answer> + <para> + Yes, it is allowed to change the page attributes in the page setup callback + (e.g. <literal>XawNpageSetupCallback</literal> or <literal>XmNpageSetupCallback</literal>) + since this callback is always called before <function>XpStartPage</function> + (for the 2nd and following pages: between <function>XpEndPage</function> and + <function>XpStartPage</function>). + Note that changing page attributes will automagically update the print shell widget size + (e.g. attributes <literal>XawNminX</literal>, <literal>XawNminY</literal>, <literal>XawNmaxX</literal> and <literal>XawNmaxX</literal> (<function>XawPrintShell</function>) + or + <literal>XmNminX</literal>, <literal>XmNminY</literal>, <literal>XmNmaxX</literal> and <literal>XmNmaxX</literal> (<function>XmPrintShell</function>) are updated based + on events send by the Xp Extension and then the print shell is resized based on the new values (<function>XawPrintShell</function> is slightly more flexible + since the size mode can be defined using the <literal>XawNlayoutMode</literal> attribute)). + </para> + </answer> +</qandaentry> + +</qandadiv> +</qandaset> +</simplesect> + + +<simplesect id="knownbugs"> +<title>Known bugs</title> +<qandaset> +<qandadiv> +<qandaentry> + <question> + <label>Problem</label> + <para> + Xprt build from Xfree86 sources is completely broken and unuseable. + </para> + </question> + <answer> + <label>Solution</label> + <para> + Build Xprt from the CVS tree at <ulink url="http://xprint.mozdev.org/">http://xprint.mozdev.org/</ulink> or the + X.org X11R6.5.1 sources (note that the client side Xprint extension + library ("<filename>libXp.so</filename>") from Xfree86 is not broken and do not need to be + replaced). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <label>Problem</label> + <para> + 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. + </para> + </question> + <answer> + <label>Solution</label> + <para> + Patch available, I am looking for a way to get the patch into the X11 + and Solaris source trees... + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <label>Problem</label> + <para> + 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". + </para> + </question> + <answer> + <label>Solution</label> + <para> + Either convert PFB (PS Type 1 binary font) to PFA format and adjust + the <filename>fonts.dir</filename> and <filename>fonts.scale</filename> file or get a patch for the sources. + 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). + </para> + </answer> +</qandaentry> + +<qandaentry> + <question> + <label>Problem</label> + <para> + 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). + </para> + </question> + <answer> + <label>Solution</label> + <para> + Xprt build from xprint.mozdev.org sources has been fixed in release + 007, see <ulink url="http://xprint.mozdev.org/bugs/show_bug.cgi?id=1378">xprint.mozdev.org bug 1378 + ("PS DDX creates n^2 copies of a job instead of n copies")</ulink> and + <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=140030">bugzilla.mozilla.org 140030 + ("Setting number of copies causes too many copies to print")</ulink> for details. + Solaris 2.7 Xprt still suffers from this issue... <literal>;-(</literal> + </para> + </answer> +</qandaentry> + +</qandadiv> +</qandaset> +</simplesect> + + +<simplesect id="unanswered_questions"> + <title>Unanswered questions</title> + <para> + (My small ToDo list what I will write soon; 379 items missing... <literal>=:-)</literal> + Email me if you want one of these answered "now" and/or to contribute + an answer... :) + <simplelist type="vert"> + <member>How do I create a model-config for my printer ?</member> + <member>How can I customize a model-config for my site/machine ?</member> + <member>Which attributes/values can be set in a model-config ?</member> + <member>Why can't I set default values (for my {paper size, resolution, ...}) in the model-config ?</member> + <member>Should I add the fonts in the model-config dir to the Xserver's font path ?</member> + <member>What are the fonts in the model-config dir for ?</member> + <member>Can I use a font server for all fonts instead of passing then directly to the Xprint server ?</member> + <member>Does the Xprint PostScript driver do full rasterisation of the print job ?</member> + <member>Is it possible to prepare a printer config entry so that the PS + output is piped to "ps2pdf" and will produce directly a PDF file? + It would be nice to have mozilla directly producing PDF files when + printing. + </member> + <member>Problem: I have changed the Xprt config - but "xplsprinters -l"</member> + <member>(or any other Xprint application) does not show the change.</member> + <member>Any idea what I am doing wrong ?</member> + <member>How can I add a font path to Xprt ?</member> + <member>Why does "xset +fp path_to_font" not work in some cases ?</member> + <member>How can I get a "core"-dump when Xprt crashes ?</member> + <member>How can I debug Xprt (hint: use "-audit 4") ?</member> + <member>How can I debug Xprt with Sun Workshop (hint: "check -access") ?</member> + <member>How can I check whether Xprint is "active" ? / How can I verify that a Xprint is working ?</member> + </simplelist> + </para> +</simplesect> + +<simplesect id="acknowledgements"> + <title>Acknowledgements</title> + <para> + We'd like like to express their gratitude to the whole community for + providing insightful answers to innumerable questions. In particular, + the following people (listed alphabetically) have contributed to this + FAQ (apologies, in advance, if anyone has been forgotten): + </para> + <para> + <simplelist type="vert"> + <member><othercredit><firstname>Alan</firstname> <surname>Coopersmith</surname></othercredit> <email>alan.coopersmith@sun.com</email></member> + <member><othercredit><firstname>Giuseppe</firstname> <surname>Ghibò</surname> </othercredit> <email>ghibo@mandrakesoft.com</email></member> + <member><othercredit><firstname>Thomas</firstname> <surname>Gilg</surname> </othercredit> <email>thomas_gilg@hp.com</email></member> + <member><othercredit><firstname>Jay</firstname> <surname>Hobson</surname> </othercredit> <email>jay.hobson@sun.com</email></member> + <member><othercredit><firstname>Masaki</firstname> <surname>Katakai</surname> </othercredit> <email>katakai@japan.sun.com</email></member> + <member><othercredit><firstname>Simon</firstname> <surname>Montagu</surname> </othercredit> <email>smontagu@smontagu.org</email></member> + <member><othercredit><firstname>Drew</firstname> <surname>Parsons</surname> </othercredit> <email>dparsons@debian.org</email></member> + <member>(and many many others)</member> + </simplelist> + </para> +</simplesect> + + +</article> + +<!-- # EOF. --> + diff --git a/hardcopy/XPRINT/Xprint_old_FAQ.txt b/hardcopy/XPRINT/Xprint_old_FAQ.txt new file mode 100644 index 0000000..250c582 --- /dev/null +++ b/hardcopy/XPRINT/Xprint_old_FAQ.txt @@ -0,0 +1,1634 @@ +Archive-name: Xprint/FAQ_OLD +Version: 0.8 +Last-Modified: 2003/08/04 15:20:19 +Maintained-by: Roland Mainz <Roland.Mainz@informatik.med.uni-giessen.de> + +NOTE: This version of the FAQ has been discontinued and was replaced by the +DocBook-based version available under xc/doc/hardcopy/XPRINT/Xprint_FAQ.xml +(available through http from +<http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_FAQ.xml>) + +The following is a list of questions that are frequently asked about +Xprint. + +You can help make it an even better-quality FAQ by writing a short +contribution or update and sending it BY EMAIL ONLY to me. +A contribution should consist of a question and an answer, and increasing +number of people sends me contributions of the form "I don't know the +answer to this, but it must be a FAQ, please answer it for me". Please +read the FAQ first and then feel free to ask me if it is not in the FAQ. + +Thanks! + +The latest Xprint FAQ and some other goodies can be obtained through http from +<http://xprint.mozdev.org/lxr/http/source/xprint/src/xprint_main/xc/doc/hardcopy/XPRINT/Xprint_old_FAQ.txt> + +Note that the FAQ has not been finished yet (nor is it half-finished...), +many items marked with "XXX" as the answer have still to be written (or have +to be copy&pasted from my item collection... :) + +1. GENERAL +- Q: What is "Xprint" ? + A: In short, "Xprint" is an advanced printing system which enables X11 + applications to use devices like printers, FAX or create documents in + formats like PostScript or PDF. + + In long, "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... + +- Q: Where can I get Xprint/Xprt from ? + A: Xprint is client-server based, therefore two answers: + - The server side is available by default on Solaris[1] and HP-UX (Xfree86 + ships a "Xprt" binary, but that is broken and the server config files + are missing, too). + For those platforms who do not have a (working) Xprt server the you + can get source, binary tarballs and Linux RPMs from + http://xprint.mozdev.org/ , Debian Linux has a package based on the + same sources (see http://packages.qa.debian.org/x/xprint-xprintorg.html) + - The client-side Xprint support library (libXp.so) is available on all + X11 platforms >=R6.4, including Linux, Solaris, HP-UX, AIX etc. + if you do not have it you can build it from the sources available at + http://xprint.mozdev.org/ + + [1]=(for Solaris >= 2.7 xprint.mozdev.org provides the "GISWxprintglue" + and "GISWxprint" packages (available from + http://xprint.mozdev.org/download.html) which provides a single-step + drop-in way to configure and start Xprint at system startup and/or + per-user for all applications and users (the package provides only + startup scripts and some config data and uses the Xprt binary provided + with Solaris (/usr/openwin/bin/Xprt)) + +- Q: What is "Xprt" ? + A: Xprt is the server-side of Xprint. It's just like any other Xserver - it + uses only an other kind of output device (printer instead of framebuffer) + and implements an extra X11 extension ("XpExtension") to handle the + special features/requirements of a "paged device"(=printer etc.). + +- Q: "Why do some people like Xprint ?" / "What are the advantages of Xprint ?" + A: - Xprint allows an application to query what features (paper size, trays, + orientation, resolutions, plexes, fonts and much more) a printer supports. + For example it is avoidable that a user accidently prints DIN-A4 on a + DIN-A0 poster printer (the print dialog would only offer DIN-A0 as paper + size, e.g. offers only choices which are valid for this printer). + - Server-side, localizeable configuration - changes to the server + config apply to all users without the need to change/updating anything + on the user side (the user may still start his/her own Xprt instance + using his/her preferred configuration). + - Small footprint - ideal for for mobile devices (client side does not + need to process any fonts - that's the job of the server side) + - API not restriced to PostScript (X11R6.5.1 comes with PCL and Raster + implementations - and PDF/G3-FAX/SVG would be possible without problems) + - Scaleable - Xprint can use as many Xprt servers as the user/admin wants + - "Xprint is designed for the enterprise", e.g. Xprint was designed to + match the needs of large company networks. + - Automatic font handling - font download or the existence of + printer-builtin fonts is automagically handled by Xprt - the application + does not need to know/handle any details (but the application can + optionally get information and control the usage of printer builtin + fonts) + - You can print anything what you can render on the framebuffer(=video + card) Xserver + - Existing code can be reused 1:1 for printing - which means reduced + development costs + - Easy support for I18N (internationalization) - you simply render any + fonts in any language with Xprint + - Network-transparent design - Client can use local or remote Xprt servers + like any other Xserver + - Uses the X11 protocol - easy adoption of existing code to implement + printer support. And all the network goodies like firewall proxies, + compressors etc. can be used for Xprint without modifications. + - Security: Xprint can use all authentification schemes available in X11 + (like Kerberos5, SecureRPC, MIT-MAGIC-COOKIE or host-based + authentification). + - Enhachements on the server side (Xprt) to not require the change of + client-side code. + - Optimized job output (like the PostScript created by the PostScript DDX) + is usually a lot smaller than the PS code created by other PostScript + engines. + +- Q: Why do some people dislike Xprint? + A: There are a few common misconceptions about Xprint. + Let's take a look some of these "myths", some background - and the facts: + + - Myth: "Xprint prints just a XWD dump of the Xserver bitmap" + Fact: Whoever says Xprint simply does an "xwd"-like dump is wrong. + + In short, Xprint _currently_ (X11R6.5.1) supports *four* drivers: + 1) X to native Postscript + 2) X to native PCL5 + 3) X to native PCL3 + 4) X to a raster which is then feed to something like xpr to + create PS or PCL5 wrapped rasters. + + In long, the original X Print Service ("XPS") was attempted + during CDE 1.0, and they only got so far as the "raster" driver. + + As CDE 2.0 came around, Bob Schiefler and others at the X + Consortium agreed that the X Consortium would work on a X to + native PS Level 2 driver and HP would work on a X to native + PCL5 driver. + + It was probably the CDE 1.0 effect that left many people with + the impression that Xprint is all about xwd-like window dumps. + NO! Xprint has native PostScrpt and PCL5 printing and more + drivers (like a PDF DDX etc.) are in the development. + + - Myth: "Xprint cannot handle non-'ISO Latin 1' chars" + - Fact: Xprint can print any chars incl. those required for MathML, + Hebrew, Arabic, Japanese etc. etc. + For example - the Xprint module for Mozilla5 is the only print + module which can proprtly print MathML. + + - Myth: "Xprint uses a 1024x768 screen resolution to render the stuff on + the paper - therefore it will never be able to do high-resolution + stuff" + Fact: Xprt uses the screen resolution requested by the application or + the printers default resolution. + For example a 300 DPI printer which supports paper sizes up to + DIN-A4 will get a screen with 3300x3300 pixels (screen width and + height are usually equal to support per-page changes in the + orientation (potrait/landscape etc.), the window size would be + 2400x3149 for "portrait" orientation) - and larger resolutions + will result in larger screens. + + - Myth: "Xprint prints only graphics(=bitmap/gfx) fonts" + - Fact: In short, Xprt supports printer-builtin fonts and can + download fonts to the printer if they do not exist on the printer. + + In long, this myth seems to have it's root in a _feature_ of + Xprt which can - if Xprt gets misconfigured - disable the use of + printer-builtin fonts and the ability to download fonts. + + Xprt's PostScript and PCL DDX have the _unique_ feature to create + font glyphs from bitmap fonts if they are not available as + printer-builtin fonts nor as PostScipt Type1 fonts. However this + is the fallback - the _last_ option used by Xprt. Used if + everything else fails. + But when someone does not pass any PS Type1 fonts with the font + path nor configures a printer model-config (which contains a + description of the features&fonts supported by the printer) Xprt + will never have a chance to use them. And if everything else + fails it has no other option than using what has been left - the + bitmap fonts... + + - Myth: "Xprint does not support pages sizes larger than DIN-A4" + Fact: There is no such limitation. + The only limit is the 16bit coordinate system of the X11 + protocol - which is large enougth that Xprint can support paper + sizes _larger_ than DIN-A0 oversize papers. There is no problem + with creating your own monster-size DIN-A0 posters using + Xprint-based applications. + + - Myth: "Xprint does not support rotated text" + Fact: Xprint and all it's drivers support the X11 matrix XLFD + enhancement introduced in X11R6. Fonts can be rotated at any + angle. Take a look at the "SOFTWARE DEVELOPMENT" section in this + FAQ for examples... + +- Q: Does Xprint support anti-aliased fonts ? + A: Question back: When do we need anti-aliased fonts ? + Anti-aliasing is a "hack" to work around the limitations caused by the + low resolution of monitors - they usually operate between 72 DPI and + 150 DPI. + But Xprint operates on printers where the usual _minimum_ resolution is + 300 DPI (today's normal office printers support resolutions ranging from + 300 DPI up to 2400 DPI depending on the model; most common is 600 DPI). + Anti-aliasing at those resolutions is not required anymore. + Additionally many printers support their own font anti-aliasing at lower + resolutions which is far better and faster than it could be "done" on the + client side. + +- Q: How can I check if Xprint is working and should be used ? + A: Check whether the ${XPSERVERLIST} env var is set or not. + If ${XPSERVERLIST} is set then Xprint is available and should be used. + +- Q: How can I view PS(=PostScript) files ? + A: - On Unix/Linux (general): + - GhostScript ("gs") and GhostView ("gv") + - Solaris: + - /usr/dt/bin/sdtimage (DPS-based image viewer for CDE) + - /usr/openwin/bin/pageview (DPS-based image viewer for OpenWindows) + +- Q: How can I view PCL files ? + A: XXX - http://xprint.mozdev.org/bugs/show_bug.cgi?id=2261 has been filed + for that issue. + +- Q: How does Xprt find fonts ? + A: Lookup-rule for Xprt's PostScript DDX to find fonts: + 1. Printer-builtin fonts (defined by the fonts/-dir in the model-config) + 2. PostScript fonts (will be downloaded via generated print job) + 3. GFX-fonts build from X11 scaleable fonts + 4. GFX-fonts build from X11 bitmap fonts + +- Q: How can I print TrueType fonts with Xprint ? + A: 1. Linux Xprt build from http://xprint.mozdev.org 's source supports + TrueType fonts out-of-the-box (starting with the 008 development tree; + xprint.mozdev.org's releases <= 007 do not support TrueType fonts) and + and does not require any special actions. + 2. Sun's Xprt on Solaris (/usr/openwin/bin/Xprt) has TrueType font + support out-of-the-box and does not require any special actions + 3. You can setup a TTF-aware X font server ("xfs", see xfs(1)) with the + matching TrueType fonts and add the font server location to Xprt's font + path. + 4. Sourceforge has a TrueType to PostScript Type 1 converter project, + see http://ttf2pt1.sourceforge.net/download.html + You may convert the TTF files into PT1 files that Xprt can download them + to the printer on demand... + +- Q: What does "DDX" mean ? + A: DDX is a short term for "Device Dependent X" - the device-specific layer + of a Xserver ("DIX"(="Device Independent X") is the counterpart). + +- Q: What does "DIX" mean ? + A: DIX is a short term for "Device Independent X" - the non-device specific + code of a Xserver ("DDX"(="Device Dependent X") is the counterpart). + +- Q: I have twenty printers installed on my system - but Xprt only shows two + screens. Where are all the other printers ? + A: A Xprt screen does not represent a single printer. A Xprt screen + represents a single DDX (currently supported are PostScript, PCL3/5 color, + PCL mono and "raster" output(=1bit deep bitmap). + +- Q: Which platforms support Xprint ? + A: All platforms which support X11 >= R6.4 can use Xprint. The client side + (libXp.so) is available on Linux/FreeBSD(=Xfree86), Solaris, HP-UX and AIX + and the Xprt server side is available by default on Solaris and HP-HX + (Xfree86 shipps with a Xprt binary - but that is broken and unuseable). + The client-side extension library (libXp.so) can be compiled on any + platform, the Xprt server needs minor adjustments for the specific + platforms... + If your platform does not have Xprint (client-side and/or server-side) + you can get the sources from http://xprint.mozdev.org/ + +- Q: I have the broken Xfree86 Xprt binary on my system. Do I need a new + version of "libXp.so" (the client side X11 extension library for Xprint), + too ? + A: No, the libXp.so shared library shipped with Xfree86 or build from + Xfree86 sources is not broken, only the server side ("Xprt") is buggy. + There is no need to replace the library. + +- Q: Which spelling is correct - "Xprint", "XPrint", "Xprinter" or Xprt" ? + A: "Xprint" is the correct one - "XPrint" is just a typo, "Xprinter" is a + complety different product not related to X11/Xprint and "Xprt" is only + the "X11 print server"(=the server side of Xprint). + +- Q: Which applications support Xprint ? + A: There are various applications which support Xprint: + - Motif/LessTif (full framework incl. special widgets like XmPrintShell) + - Common Desktop Environment (CDE) 2.x + - Mozilla + - Eclipse + - KDE/Qt support is comming is planned for the end of Dec/2002 + - StarOffice 5.x + etc. + +- Q: Is "Xprint" "mozilla"-only (I saw that it's hosted by mozdev.org) ? + A: No, Xprint is a general-purpose print API based on the X11 API used by + many applications (mozdev.org is just hosting the development area, but + this does not mean the project is limited to mozilla... :) + +- Q: Under which license is the source code from xprint.mozdev.org distributed + under ? + A: That's the plain "MIT" license, the same as used by Xfree86.org and X.org: + -- snip -- + Copyright (c) <year> <copyright holders> + + Permission is hereby granted, free of charge, to any person obtaining a copy of this software + and associated documentation files (the "Software"), to deal in the Software without + restriction, including without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the + Software is furnished to do so, subject to the following conditions: + + The above copyright notice and this permission notice shall be included in all copies or + substantial portions of the Software. + + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING + BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, + DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING + FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + -- snip -- + +2. USAGE +- Q: How do I configure Xprint on the client side ? + A: There are two env vars which control Xprint on the client side: + 1. The env variable ${XPSERVERLIST} contains a list of display identifiers + (seperated by whitespace) to tell the application where it can find + the Xprt servers. + Usually ${XPSERVERLIST} is set by the profile startup scripts (e.g. + /etc/profile or /etc/profile.d/xprint.sh) using the output of + "/etc/init.d/xprint get_xpserverlist". + Example: + % export XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`" + Alternativly ${XPSERVERLIST} can be set manually: + Example: + % export XPSERVERLIST="littlecat:80 bitdog:72" + instructs an application to look at the displays 80 on the machine + "littlecat" and display 72 on the machine bigdog to look for Xprt + servers. + 2. The env variable ${XPRINTER} defines the default printer used by print + applications. The syntax is either <printername> or + <printername>@<display> + - Examples: + 1. % export XPRINTER=ps003 + tells an application to look for the first printer named "ps003" on + all Xprt servers. + 2. % export XPRINTER="hplaser19@littlecat:80" + tells an application to look for the printer "hplaser19" on the Xprt + display "littlecat:80". + * If ${XPRINTER} is not set the applications will examine the values of + the ${PDPRINTER}, ${LPDEST}, and ${PRINTER} env vars (in that order). + +- Q: How do I start Xprt ? + A: 1. Linux RPM installations on Mandrake/RedHat/SuSE Linux: + Binary RPM packages provided by xprint.mozdev.org (or based on the same + source :) will install /etc/init.d/xprint and related glue (see [4]) + automatically; after a reboot a Xprt instance will be started at system + startup and ${XPSERVERLIST} should be populated for all users. + Note that you can start/stop per-user instances using /etc/init.d/xprint + (see [4]), too... + + 2. Debian Linux: + Same as [1], however Debian does not support /etc/profile.d/ - you have + to add the following line to /etc/profile (for sh/ksh/bash) to populate + ${XPSERVERLIST}: + -- snip -- + export XPSERVERLIST="`/bin/sh /etc/init.d/xprint get_xpserverlist`" + -- snip -- + See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=171174 + ('"xprint-xprintorg" should automatically populate $XPSERVERLIST') for + further details on this issue... + + 3a. Solaris using the "GISWxprintglue" package: + http://xprint.mozdev.org/ provides a Solaris package called "GISWxprintglue" + which contains all the neccesary configuration files and startup scripts + to use Xprint; after a reboot a Xprt instance will be started at system + startup and ${XPSERVERLIST} should be populated for all users. + Note that you can start/stop per-user instances using /etc/init.d/xprint + (see [4]), too... + + 3b. Solaris using the "GISWxprint" package: + http://xprint.mozdev.org/ provides a Solaris package called "GISWxprint" + which is technically identical to the "GISWxprintglue" (see [3a]) but + provides a Xprt binary build from the xprint.mozdve.org sources + ("GISWxprintglue" uses the /usr/openwin/bin/Xprt binary provided by Solaris). + + 4. General: Using /etc/init.d/xprint and related glue: + There are startup/shutdown scripts in xc/programs/Xserver/Xprint/etc/ + to start/stop/restart Xprt per-machine and/or per-user and to populate the + ${XPSERVERLIST} env var: + - "xc/programs/Xserver/Xprint/etc/init.d/xprint" is a script for SystemV + and Linux to start/stop/restart Xprt. The script includes installation + and usage details and can be used by both "root" (to start Xprt for all + users) or by a single (non-priviledged, plain) user (to start Xprt + instances only for his/her own use) + - "xc/programs/Xserver/Xprint/etc/profile.d/xprint.csh" and + "xc/programs/Xserver/Xprint/etc/profile.d/xprint.sh" are scripts for + Linux (which support /etc/profile.d/ ; note that this does not include + Debian) to populate the ${XPSERVERLIST} env var for each user. + + 5. Starting Xprt "manually" (without using /etc/init.d/xprint): + Set the ${XPCONFIGDIR} env variable to the directory where Xprt can find + it's configuration data. + | WARNING: If Xprt cannot find it's configuration data it will not be + | able to use printer-builtin fonts (which are defined by the + | model-config in the configuration dir). Without printer-builtin fonts + | Xprt _may_ fall back to generate font glyphs from bitmap fonts (this + | resulted in the MYTH that "Xprt can only print gfx fonts". This is not + | _TRUE_ - this only happens if Xprt is either misconfigured or no + | matching builtin or PS Type1 font is available). + You may want to make a copy of the default configuration directory and + modify it to match your needs. + + Starting Xprt is just as easy as starting any other Xserver: + % Xprt :12 + will start Xprt on display 12 (e.g. set ${XPSERVERLIST} to ":12" or + "myhostname:12". + + You may want to copy your framebuffer Xserver's font path to be able to + print all fonts which can be displayed on that Xserver. + % Xprt -fp $(xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }") :12 + + Notes: + - The /etc/init.d/xprint has a more advanched filtering scheme based on + regex patters to "accept" and/or "reject" font paths + - 'xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }"' + may be too simple-minded if your Xserver does not support TrueType + fonts. The following statemement is better in this case since it + filters the font path and removes all path elements which have TrueType + fonts (*.ttf, *.TTF) or TrueType font collections (*.ttc, *.TTC) in + "fonts.dir": + -- snip -- + % xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }" | + tr "," "\n" | while read i ; do \ + if [ "$(cat ${i}/fonts.dir | egrep -i "ttf|ttc" 2>/dev/null)" == "" ] \ + ; then echo $i ; fi ; done | (fontpath="" ; fpdelim=""; while read i ; \ + do fontpath=${fontpath}${fpdelim}${i} ; fpdelim="," ; done ; echo \ + $fontpath) + -- snip -- + - It may be easier to just feed all available font paths to Xprt + (BTW: mozilla 1.0 had a bug in that case which resulted in the problem + that it used many many bitmap fonts in that case - this has been fixed + for 1.0.1 and Netscape 7 (that's the reason why the quickguides for + hebrew/cyrillic use the "Xp_dummyfonts" fonts instead of + /usr/openwin/lib/X11/fonts/misc/ - to avoid that Mozilla finds bitmap + fonts for the same locale). + The following "small" one-liner finds all fonts (except printer builtin + fonts): + -- snip -- + % find /usr/openwin -name fonts.dir | while read i ; do echo + ${i%/fonts.dir} ; done | fgrep -v "models/" + -- snip -- + Plug it into the filter above to remove the Truetype fonts and you are + "done"... :) + + See TROUBLESHOOTING if you run into problems... + +- Q: How can I get a list of printers managed by Xprint ? + A: The tool "xplsprinters" is designed for that purpose. It can deliver both + list of printers and attributes supported for a specific list of printers. + Use % xplsprinters -h # to obtain usage information. + Example: + - Get list of available printers: + -- snip -- + % xplsprinters + printer: hplaserjet001@castor:19 + printer: hpcolor001@castor:19 + printer: laser1@jason:5 + printer: david_dj01@jason:5 + -- snip -- + - Get information about the supported attrbites of printer "ps002": + -- snip -- + % xplsprinters -printer ps002 -l + printer: ps002@castor:18 + comment= + model-identifier=HPDJ1600C + default-medium=iso-a4 + default-input-tray= + medium-source-sizes-supported=iso-a4 false 6.35 203.65 6.35 290.65 + medium-source-sizes-supported=na-letter false 6.35 209.55 6.35 273.05 + default-printer-resolution=300 + resolution=300 + default_orientation= + orientation=portrait + orientation=landscape + default_plex= + plex=simplex + -- snip -- + +- Q: How can I start Xprt at boot time ? + A: "xc/programs/Xserver/Xprint/etc/init.d/xprint" is a script for SystemV + and Linux to start/stop/restart Xprt at system startup (e.g. per-machine) + or for a single user (e.g. per-user). + The script includes installation and usage details. + +- Q: How can I start Xprt per-user ? + A: "xc/programs/Xserver/Xprint/etc/init.d/xprint" is a script for SystemV + and Linux to start/stop/restart Xprt at system startup (e.g. per-machine) + or for a single user (e.g. per-user). + The script includes installation and usage details. + +- Q: How can I start Xprt only for one application ? + A: Create your own version/copy of /etc/init.d/xprint and modify it to fit + your requirements and then make sure that you issue a + "my_xprint_startscript start" before starting the application and a + "my_xprint_startscript stop" after leaving the application. + +- Q: How can I filter the font path which should be passed to Xprt for + certain fonts ? + A: XXX + +- Q: How can I manage access control to the Xprt server ? + A: Access control to Xprt is not differently as to any other Xserver and + 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 xhost(1))) + and/or per-machine (using "xhost" (see xhost(1)) and/or + /etc/X<dpy>.hosts (<dpy> == display number, e.g. /etc/X0.hosts for + display 0) (see Xserver(1))) + Consult manual pages Xsecurity(7), xhost(1), Xserver(1) etc. for further + details. + +- Q: How can I log access to the Xprt server ? + A: Logging access to Xprt can be done using the standard Xserver auditing, + see the Xserver(1) manual page, option "-audit" + +- Q: Does it require "root" permissions to use Xprt/Xprint ? + A: No, both Xprint clients and Xprint server(s) do not require root rights + to work. + Xprint clients are handled like any other X11 application and the Xprt + servers can run without any special requirements. + Solaris is an exception here since it requires to start any Xserver + (incl. Xprt) setgid "root" (set-group-id "root", this is _not_ + set-user-id "root") since the sockets/pipe files in /tmp/.X11-pipe/ and + /tmp/.X11-unix/ are only accessible for the group "root". + The workaround is to start Xprt with the option "-pn"; therefore even + Xprt server binaries which are not setgid "root" can run without + problems). + +- Q: How can I see the attributes of a printer managed by Xprint ? + A: "xplsprinters -printer myprinter004 -l" will do the job for printer + "myprinter004". See xlsfonts(1) for futher usage and a description of + the output. + +- Q: How can I list the font path used by a Xprt server ? + A: Figure out the display id of the server which should be queried (we are + using "foobar:98" in this example) and then try this: + -- snip -- + % (DISPLAY=foobar:98 xset q | awk "/Font Path:/ { i=1 ; next } i==1 { print \$0 ; i=0 }" | tr "," "[\n]") + # Output may look like: + PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/HPDJ1600C/fonts/ + PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/SPSPARC2/fonts/ + PRINTER:/usr/openwin/server/etc/XpConfig/C/print/models/HPLJ3Si-PS/fonts/ + /usr/openwin/lib/X11/fonts/F3/ + /usr/openwin/lib/X11/fonts/F3bitmaps/ + /usr/openwin/lib/X11/fonts/Type1/ + /usr/openwin/lib/X11/fonts/Speedo/ + /usr/openwin/lib/X11/fonts/misc/ + /usr/openwin/lib/X11/fonts/75dpi/ + /usr/openwin/lib/X11/fonts/100dpi/ + -- snip -- + Note that the font path items which start with "PRINTER:" are _only_ be + sourced _after_ the matching printer has been selected and configured + (for developers: After |XpSetContext()| has been called). + +- Q: "xset q" lists all model-specific font dirs (like + PRINTER:/myxpcfg/C/print/models/SPSPARC2/fonts/") - is that a bug ? + A: No, this is normal. Xprt will add all fonts of all printer models to the + font path - but font path items starting with "PRINTER:" are _only_ + available for an application _after_ the matching printer has been + selected and configured (for developers: After |XpSetContext()| has been + called), _before_ that point fonts in these dirs are not available for + an application. + +- Q: My application lists a printer called "spooldir_tmp_Xprintjobs" in the + print dialog but I do not have such a print queue installed anywhere. + What is that for a thing ?! + A: "spooldir_tmp_Xprintjobs" is a special Xprint printer target which uses + the "PSspooldir" printer model. This model config sends PostScript jobs + to the /tmp/Xprintjobs/ directory instead to a physical printer (quite + usefull for people who want to get the PostScript files as output instead + of printed pages). + +3. CONFIGURATION +- Q: How do I change the defaults for double-sided/single-sided/etc. + printing ? + A: This is controlled via the "plex" attribute in the document attribute + pool (${XPCONFIGDIR}/${LANG}/print/attributes/document and/or + ${XPCONFIGDIR}/C/print/attributes/document). + Examples: + 1. Adding/modifying the following line to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default plex for + all printers to "duplex": + -- snip -- + *plex: duplex + -- snip -- + 2. Adding/modifying the following two lines to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default plex for + all printers to "duplex" except for printer "ps003" which should + default to "simplex": + -- snip -- + *plex: duplex + ps003.plex: simplex + -- snip -- + Notes: + - Not all printers support all plex modes. The model-config may restrict + the available plex modes. + - Setting a plex mode which is not supported by either the DDX(=driver) + or not specified in the model-config will cause Xprt to not set a + default plex. + - The PostScript DDX supports plex modes "simplex", "duplex" and "tumble". + - Verification: + Use '% xplsprinters -l | egrep "^printer:|default_plex=|plex="' to view + the plex settings for all printers. + +- Q: I am in America and I don't have any ISO A4 paper. How do I change the + default paper size to 8.5 inch x 11 inch (US-Letter) ? + A: This is controlled via the "default-medium" attribute in the document + attribute pool (${XPCONFIGDIR}/${LANG}/print/attributes/document and/or + ${XPCONFIGDIR}/C/print/attributes/document). + Examples: + 1. Adding/modifying the following line to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default paper size + for all printers to "na-letter": + -- snip -- + *default-medium: na-letter + -- snip -- + 2. Adding/modifying the following two lines to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default paper size + for all printers to "na-letter" except for printer "ps003" which should + default to "iso-a4": + -- snip -- + *default-medium: na-letter + ps003.default-medium: iso-a4 + -- snip -- + Notes: + - xprint.mozdev.org releases >= 007 provides a seperate "document" + attribute pool for en_US(-like) locales (see + ${XPCONFIGDIR}/en_US/print/attributes/document) which will override the + default ISO-A4 with US-Letter (this feature assumes that ${LANG} is set + to "en_US" (or a locale which has similar defaults as "en_US", those + are currently linked to "en_US" in ${XPCONFIGDIR}/)) + - Not all printers support all paper sizes. The model-config may restrict + the available paper sizes. + - Setting a paper size which is not supported by either the DDX(=driver) + or not specified in the model-config will cause Xprt to not set a + default paper size. + - The PostScript DDX supports the following paper sizes: + - X.org release 6.6 (X116.6): + "iso-a4", "na-letter", "na-legal", "executive", + "iso-designated-long", "na-number-10-envelope" + - xprint.mozdev.org release >= 006: + "na-letter", "na-legal", "executive", "folio", "invoice", + "ledger", "quarto", "a", "b", "c", "d", "e", + "na-6x9-envelope", "na-10x15-envelope", "monarch-envelope", + "na-10x13-envelope", "na-9x12-envelope", "na-number-10-envelope", + "na-7x9-envelope", "na-9x11-envelope", "na-10x14-envelope", + "na-number-9-envelope", + "iso-a0", "iso-a1", "iso-a2", "iso-a3", "iso-a4", + "iso-a5", "iso-a6", "iso-a7", "iso-a8", "iso-a9", + "iso-a10", + "iso-b1", "iso-b2", "iso-b3", "iso-b4", "iso-b5", + "iso-b6", "iso-b7", "iso-b8", "iso-b9", "iso-b10", + "jis-b1", "jis-b2", "jis-b3", "jis-b4", "jis-b5", + "jis-b6", "jis-b7", "jis-b8", "jis-b9", "jis-b10", + "iso-c3", "iso-c4", "iso-c5", "iso-c6", + "iso-designated-long" + - Verification: + Use 'xplsprinters -l | egrep "^printer:|default-medium=|medium-source-sizes-supported="' + to view the medium settings for all printers. + The 'medium-source-sizes-supported='-lines have the format XXX. + +- Q: How do I change the default printer resolution ? + A: This is controlled via the "default-printer-resolution" attribute in the + document attribute pool (${XPCONFIGDIR}/${LANG}/print/attributes/document + and/or ${XPCONFIGDIR}/C/print/attributes/document). + Examples: + 1. Adding/modifying the following line to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default + resolution for all printers to 600 DPI: + -- snip -- + *default-printer-resolution: 600 + -- snip -- + 2. Adding/modifying the following two lines to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default resolution + for all printers to 300 DPI except for printer "tekcolor_ps" which + should default to 1200 DPI: + -- snip -- + *default-printer-resolution: 300 + tekcolor_ps.default-printer-resolution: 1200 + -- snip -- + Notes: + - Not all printers support all resolutions. The model-config may restrict + the available resolutions. + - Setting a resolution which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt to + not set a default resolution. + - The PostScript DDX supports the following default resolutions + - X.org release 6.6 (X116.6): + 300, 600, 720, 940, 1200, 1440, 2400 + - xprint.mozdev.org release >= 006: + 75, 100, 120, 150, 180, 200, 240, 300, 360, 400, 600, 720, 940, + 1200, 1440, 2400 + - Verification: + Use 'xplsprinters -l | egrep "^printer:|default-printer-resolution=|resolution="' + to view the resolution settings for all printers. + +- Q: How do I change the default settings for "portrait"/"landscape"/"seascape" + (=page orientation) ? + A: This is controlled via the "content-orientation" attribute in the + document attribute pool (${XPCONFIGDIR}/${LANG}/print/attributes/document + and/or ${XPCONFIGDIR}/C/print/attributes/document). + Examples: + 1. Adding/modifying the following line to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default + orientation for all printers to "portrait": + -- snip -- + *content-orientation: portrait + -- snip -- + 2. Adding/modifying the following two lines to/in + ${XPCONFIGDIR}/C/print/attributes/document sets the default orientation + for all printers to "portrait" except for printer "ps003" which should + default to "landscape": + -- snip -- + *content-orientation: portrait + ps003.content-orientation: landscape + -- snip -- + Notes: + - Not all printers support all orientations. The model-config may + restrict the available orientations. + - Setting an orientation which is not supported by either the + DDX(=driver) or not specified in the model-config will cause Xprt to + not set a default orientation. + - The PostScript DDX supports the following orientations: + "portrait", "landscape", "reverse-portrait" and "reverse-landscape". + - Verification: + Use 'xplsprinters -l | egrep "^printer:|default_orientation=|orientation="' + to view the orientation settings for all printers. + +- Q: How can I prevent Xprt from using any bitmap(=gfx) fonts ? + A: Do not pass any bitmap fonts with the "-fp" (=font path) argument. + However you have to provide a 'fixed' and a 'cursor' font, a Xserver + can't start without having these fonts. + Task list: + 1. Create a new directory: + % mkdir Xp_dummyfonts + % cd Xp_dummyfonts + 2. Create a fonts.alias file with the following content: + -- snip -- + ! alias for "fixed" font + ! original from /usr/openwin/lib/X11/fonts/misc/fonts.alias looks like this: + ! fixed "-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1" + fixed -*-r-*--*-*-*-*-*-*-iso8859-1 + ! EOF. + -- snip -- + 3. Copy or link "6x13.pcf.Z" and "cursor.pcf.Z" and create fonts.dir + % ln -s /usr/openwin/lib/X11/fonts/misc/6x13.pcf.Z . + % ln -s /usr/openwin/lib/X11/fonts/misc/cursor.pcf.Z . + % mkfontdir $PWD + 4. Verify: The directory should now look like this: + -- snip -- + % ls -1 + 6x13.pcf.Z + cursor.pcf.Z + fonts.alias + fonts.dir + -- snip -- + 5. Add the full path (e.g. /home/xp/Xp_dummyfonts) as last element + of the font path when starting Xprt: + % Xprt -fp /usr/openwin/lib/X11/fonts/Type1/,/home/xp/Xp_dummyfonts :12 + + | I created a tarball from these instructions, get it from + | http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/Xp_dummyfonts.tar.gz + | Unpack it and add the new dir to your fontpath) + +- Q: I want only my manually added printers managed by Xprint. How can I + prevent Xprt from looking-up the printer names automatically ? + A: Add a line with "Augment_Printer_List %none%" to + ${XPCONFIGDIR}/C/print/Xprinters (or + ${XPCONFIGDIR}/${LANG}/print/Xprinters) and add lines with + "Printer <name>" for each printer <name>. + Example: + -- snip -- + Augment_Printer_List %none% + Printer ps001 + Printer ps003 + Printer hplaser6 + -- snip -- + will add only the printers "ps001", ps003" and "hplaser6". + +- Q: How can I specifc an own program/script to enumerate the printers on by system ? + A: Add "Augment_Printer_List my_script" to ${XPCONFIGDIR}/C/print/Xprinters (or + ${XPCONFIGDIR}/${LANG}/print/Xprinters). + The script must return the printer names - one per line, ASCII-only - to stdout. + +- Q: Which program is used by default by Xprt to enumerate the printers on + my system ? + A: This depends on the OS: + - On Solaris (and most other OSes exclusing AIX and Linux): + % lpstat -a | cut -d " " -f 1 + - On Linux: + - For Xprt build from X11R6.x X.org sources: + % lpc status | grep -v '^\t' | sed -e /:/s/// # '\t' means TAB + - For Xprt build from xprint.mozdev.org sources (both lines are executed + to support both LPng and CUPS): + % lpc status | awk '/:$/ && !/@/ { print $1 }' | sed -e /:/s/// ; + lpc -a status | awk '/@/ && !/:/ { split( $1, name, \"@\" ); print name[1]; }' + - On AIX v4: + % lsallq | grep -v '^bsh$' + * See xc/programs/Xserver/Xprint/Init.c for a complete list of commands + used on the specific platforms to enumerate the printers. + * Note that the output is always piped through "sort" to get an + alphabetical order (the "default" printer is not chosen/defined + here(=server side), the client side is responsible to choose a default + printer. + See FAQ item about the ${XPRINTER} env var how to set your default + printer). + +- Q: Where can I get more PostScript Type1 fonts from ? + A: Some sources: + - Adobe: + - Commercial fonts: + http://www.adobe.com/type/main.html + - Free Euro font: + - Single-glyph (e.g. it contains _only_ the euro char) euro font: + http://www.adobe.com/type/eurofont.html or + ftp://ftp.adobe.com/pub/adobe/type/win/all/ + ("eurofont.exe" can be unzipped using "unzip") + - ISO8859-15: + WANTED!! + - Solaris shipps with various PS Type 1 fonts: + - Arabic: + /usr/openwin/lib/locale/ar/X11/fonts/Type1 + ("fonts.dir" and "fonts.scale" missing, maybe they miss the + presentation forms a&b, too [unconfirmed]) + - ISO-8859-13 (Latin 8): + /usr/openwin/lib/locale/iso_8859_13/X11/fonts/Type1 + - ISO-8859-5 (Latin 5): + /usr/openwin/lib/locale/iso_8859_9/X11/fonts/Type1 + - ISO-8859-8/Hebrew: + /usr/openwin/lib/locale/iso_8859_8/X11/fonts/Type1 + (BROKEN, even "type1fix" cannot fix them. Use the hebrew fonts from + http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/PS_Type1_iso8859-8.tar.gz) + - ISO-8859-7/Modern greek: + /usr/openwin/lib/locale/iso_8859_7/X11/fonts/Type1 + - ISO-8859-5/Cryrillic: + /usr/openwin/lib/locale/iso_8859_5/X11/fonts/Type1 + - ISO-8859-4 (Latin 4): + /usr/openwin/lib/locale/iso_8859_4/X11/fonts/Type1 + - ISO-8859-2 (Latin 2): + /usr/openwin/lib/locale/iso_8859_2/X11/fonts/Type1 + - ISO-8859-1 (Latin 1) and Symbol fonts: + /usr/openwin/lib/X11/fonts/Type1/ + - Some of my own collections: + (see http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/): + - KOI8-R: + http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/PS_Type1_koi8-r.tar.gz + - ISO-8859-8/Hebrew: + http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/postscript_type_1/PS_Type1_iso8859-8.tar.gz + +- Q: What are PMF fonts (e.g. the *.pmf fonts in + ${XPCONFIGDIR}/C/print/models/%model_name%/fonts/ (or + ${XPCONFIGDIR}/${LANG}/print/models/%model_name%/fonts/)) ? + A: PMF "fonts" are "printer metric files" (.pmf) that describe the metrics + of the fonts (which means they do not contain any data to render the + fonts - they contain only the plain metrics of a font) which are built + into the printer (ROM or via font catridge etc.). + +- Q: Can I use the fontserver ("xfs") with Xprt ? + A: You can use Xprt with the font server ("xfs") like with any other + Xserver - but it is not recommded since the font server protocol does + not allow access to the native font format and therefore disables font + download, e.g. both PS Type1 and TrueType fonts cannot be downloaded + anymore and Xprt will fall-back to embed them as bitmap glyphs in the + print job (e.g. the fonts will still appear correctly in the printout, + but the quality may be reduced since downloaded fonts are always better + than bitmap glyphs). + (users of xprint.mozdev.org-release <= 006 may see + http://xprint.mozdev.org/bugs/show_bug.cgi?id=2092 if they use "xfs"; + this has been fixed in the 007 release!) + +- Q: What is a "model-config" ? + A: The term "model-config" refers to the subdirs in + ${XPCONFIGDIR}/${LANG}/print/models/. There subdirs contain information + about the attributes for a specific printer model or family/class of + printer models. In particular there are two kinds of information: + - "${XPCONFIGDIR}/${LANG}/print/models/${NAME_OF_MODEL}/model-config" + this file defines a set of attributes supported by this specific printer + (-family/-class/etc.) + and + - "${XPCONFIGDIR}/${LANG}/print/models/${NAME_OF_MODEL}/fonts/" - a + directory which contains a set of PMF (printer metrics file) fonts + builtin into the printer itself (actually the PMF "font" format + contains only metrics information and no glyphs). + These fonts are only available to the application _after_ the + application has selected a printer and configured it (for developers: + After |XpSetContext()| has been called). + +- Q: Where can I store the default values for printers ? + A: XXX + +- Q: How can I create my own model-config ? + A: XXX + +- Q: How can I create my own PMF "fonts" ? + A: XXX - no solution yet, but + http://xprint.mozdev.org/bugs/show_bug.cgi?id=2430 ("RFE: Need tool to + create PMF (printer metrics file) fonts") has been fixed to create a + freeware tool to create such fonts. + +- Q: Where can I get more model-configs from ? + A: If you miss a model-config for your printer please open a bug/RFE at + http://xprint.mozdev.org/bugs/enter_bug.cgi?product=xprint&component=Server%3A+Config%3A+model-configs + (e.g. ttp://xprint.mozdev.org/bugs/ , product "Xprint", component + "Server Config: model-configs"). + +- Q: If I install Xprt&co. as "root" in the default location and don't need + to set ${XPCONFIGDIR} - where are my configuration files located then ? + A: This is platform-specific, based on the "XPrintDir" Imake variable set + at build time. Default location for plain X11R6.x is + "${XProjectRoot}/lib/X11/xserver" (set at build time), but some + platforms modify "XPrintDir" to alternate locations: + - Solaris sets ${XPCONFIGDIR} to /usr/openwin/server/etc/XpConfig/ + - Linux (non-Debian) sets ${XPCONFIGDIR} to /usr/X11R6/lib/X11/xserver/ + or /etc/X11/xserver/ + - Debian Linux sets ${XPCONFIGDIR} to /usr/share/Xprint/xserver + * If you don't know where the default location for ${XPCONFIGDIR} is + located try + % strings -a /usr/openwin/bin/Xprt | grep XPRINTDIR # - it _may_ + return some debug info from the binary containing the builtin XpConfig + path. + +- Q: Are config files and/or the PMF fonts architecture dependent ? + A: The PMF fonts are AFAIK a variant of the PCF font format, they are + (like the PCF format) architecture-independent. + These fonts must be kept together with the other model config data since + they depend on the printer model (de facto + ${XPCONFIGDIR}/C/print/models/ (and/or + ${XPCONFIGDIR}/${LANG}/print/models/) should be supplied by the printer + vendors (but most people will create their own models on demand since + I doubt that any vendor except HP, Sun and xprint.mozdev.org staff ever + looked at that stuff)). + Per definition they are read-only data supplied by the vendor, but + modifying them may be usefull, too. + I would say it is recommended to put treat all Xprint files in + ${XPCONFIGDIR} as read-only vendor data; admins should create copies of + this tree on demand (and/or (soft-)link some files) and set + ${XPCONFIGDIR} to the modified config data. + +- Q: Can I localise my Xprint/Xprt configuration ? + A: Yes, Xprt supports localisation ("l10n") by default. Default values for + all locales are stored in ${XPCONFIGDIR}/C/print/, locale-specific + settings can be set in ${XPCONFIGDIR}/${LANG}/print/ + Rules: + - Attribute pools + ("${XPCONFIGDIR}/*/print/attributes/document", + "${XPCONFIGDIR}/*/print/attributes/job", + "${XPCONFIGDIR}/*/print/attributes/printer" and + "${XPCONFIGDIR}/*/print/models/*/model-config"): + "document", "job" and "printer" attribute pools and printer + model-configs are sourced first from the + "${XPCONFIGDIR}/C/print/"-directory, then they are overridden by any + attributes from the locale-specific pools (in + "${XPCONFIGDIR}/${LANG}/print/"), e.g. any values set in + "${XPCONFIGDIR}/C/print/attributes/*" and + "${XPCONFIGDIR}/C/print/models/*/model-config" will automatically + apply to all other locales unless they are overridden by + locale-specific versions of these files + ("${XPCONFIGDIR}/${LANG}/print/attributes/*", + "${XPCONFIGDIR}/${LANG}/print/models/*/model-config") + - "Xprinters" (list of printers): + If there is a locale-specific ${XPCONFIGDIR}/${LANG}/Xprinters present + it will be used instead of ${XPCONFIGDIR}/C/Xprinters (e.g. values set + in ${XPCONFIGDIR}/C/Xprinters will be ignored and the values from + ${XPCONFIGDIR}/${LANG}/Xprinters will be used instead). + - Xprt will determinate the locale which should be used based on the + ${LANG}-environment vaiable at startup time. If there is no such + variable set at that time LANG="C" is assumed. + * Notes: + - Attribute values for paper names and orientation names refer to + builtin strings in the DDX code (which are itself based on + international standards), these cannot be changed to your own + "inventions" (it does it make sense to try to "localize" paper names - + "ISO-A4" is "ISO-A4" even in japanese/hebrew/german etc.). + Locale-spefific attribute pools can set their own, different values - + but only within the allowed range of values supported by the DDX and + printers's model-config. + +- Q: Can I execute my own scripts to process the PostScript files generated + by Xprt ? + A: Yes, there are at least two possible solutions: + 1. Create your own model-config which uses a custom "xp-spooler-command" + value - the xprint.mozdev.org's "PSspooldir" model config (see + "${XPCONFIGDIR}/C/print/models/PSspooldir/" and + "${XPCONFIGDIR}/C/print/attributes/printer" and + "${XPCONFIGDIR}/C/print/Xprinters") is a good example for that. + 2. Use an existing "model-config" (which would normally send it's data to + a printer using the default print spooler command) and provide a + custom "xp-spooler-command". + Example (using "SPSPARC2" as printer model and "myscriptprinter" as + name of the printer): + 1. Edit ${XPCONFIGDIR}/C/print/attributes/printer and add these lines + (Xprt will replace "%printer-name%" with the printer's name, + "%copy-count%" with the number of job copies, "%job-name%" with the + job's title and "%options%" with any custom spooler options): + -- snip -- + myscriptprinter.xp-model-identifier: SPSPARC2 + myscriptprinter.xp-spooler-command: -printer %printer-name% -copies %copy-count% -title %job-name% -options "%options%" + -- snip -- + 2. Edit ${XPCONFIGDIR}/C/print/Xprinters and append this line: + -- snip -- + Printer myscriptprinter + -- snip -- + +- Q: How can I disable "spooldir_tmp_Xprintjobs" printer target ? + A: Edit ${XPCONFIGDIR}/C/print/Xprinters and remove or comment-out the line + "Printer spooldir_tmp_Xprintjobs". + Note that Xprt will _NOT_ start if this printer has been removed/disabled + and no other print queue is available (e.g. if "spooldir_tmp_Xprintjobs" + is the only printer target available). + +4. TROUBLESHOOTING +- Q: Xprt refuses to start with the message "sh: lpc: command not found" on + my Linux machine. What does that mean ? + A: Xprt looks up printers using "lpc" on Linux. In this case "lpc" cannot be + found for some reason. + Solution: + Find the place where "lpc" is installed on your machine (some + distributions put it into /usr/sbin, some into /usr/bin) and check + whether your PATH env var includes this directory. + Example (if "lpc" is located in /usr/sbin): + % which lpc + /usr/sbin/lpc + % export PATH=$PATH:/usr/sbin + # Start Xprt ... + % Xprt <your-options-come-here> + +- Q: When the application (=client side) tries to connect to the Xprt + (Xserver) side it fails with a + -- snip -- + Xlib: connection to "meridian:52.0" refused by server + Xlib: Client is not authorized to connect to Server + -- snip -- + What does that mean ? + A: X11 implements access control. You can have host-based, cookie-based (a + "cookie" is used like a passport) or user-based (SecureRPC or Kerberos5) + authentification. Xsecurity(7) has most of the details. + a. No access control: + If you do not want to use access control for Xprt then you can start it + with the option "-ac" (see XSERVER(1)) to disable the access control. + Example: + % Xprt -ac -audit 4 :12 + will start Xprt with access control disabled and with auditing enabled + (e.g. the "-audit 4" option). + WARNING: Disabling the access control will enable _everyone_ who can + access Xprt to print on your printers (that's why the above example + shows how to use auditing, too - that you can see who does something + with Xprt...) !! + + b. Host-based access control: + Host-based access control can be archived using /etc/X<dpy>.hosts + (<dpy> == display number, e.g. /etc/X0.hosts for display 0 (see + Xserver(1) manual page for further details)). + Example: + 1. Add the following line to `/etc/X12.hosts' (assuming you want that + the hosts 'merkur' and 'mars' should be able to access the Xprt + server running as display 12 on your host 'neptun'): + -- snip -- + INET:merkur + INET:mars + -- snip -- + 2. Start Xprt + 3. Verify that Xprt is correctly configured: + -- snip -- + % export DISPLAY=neptun:12 + % xhost + access control enabled, only authorized clients can connect + INET:localhost + LOCAL: + INET:merkur + INET:mars + -- snip -- + +- Q: Xprt refuses to start with the message "failed to set default font path + '...' Fatal server error: could not open default font 'fixed'". + What does that mean ? + A: This means one or more components in the font path (set via the option + "-fp") are either... + - ... not valid + - ... contain fonts not supported by this Xserver (e.g. support has not + be compiled "in" (usually happens for TrueType or F3 fonts (Sunsoft/F3 + fonts are Solaris-specific and _not_ supported by other vendors (AFAIK)) + when support for these fonts was not enabled at build time)) + - ... no font or font alias in the font path matches the name "fixed" + +- Q: Just copying my fonts into a directory and adding the path to my Xprt + command line didn't work - I always get "Fatal server error: could not + open default font 'fixed'". What am I doing wrong ? + A: Every Xserver needs an index file called "fonts.dir" to tell it which + fonts are available in this directory and which properties these fonts + have. + If you are lucky there may be already a "fonts.scale" file which can be + used by "mkfontdir" to create the "fonts.dir" file. + If there is no "fonts.scale" then you have to create your own + fonts.dir/fonts.scale either by hand or via a tool like "type1inst" (see + http://packages.debian.org/stable/utils/type1inst.html) for PS Type1 + fonts and "ttmkfdir" (see + http://packages.debian.org/stable/x11/ttmkfdir.html) for TrueType fonts. + +- Q: Xprt refuses to start with the message "Fatal server error: Cannot + establish any listening sockets - Make sure an X server isn't already + running". What does that mean ? + A: There is already a Xserver running at the display ID you have specified + to start Xprt (for example your framebuffer Xserver runs at ":0" then + Xprt can't run at the same display display). + +- Q: Xprt refuses to start with the message "Fatal server error: Failed to + establish all listening sockets". What does that mean ? + A: This means that the Xserver could not open one of it's sockets. Check + the permission of /tmp/.X11-pipe and /tmp/.X11-unix (on Solaris a + 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 _always_ with + <hostname>:<displaynum> (see Xserver(1) manual page for the side-effects + of this option). + +- Q: Xprt refuses to start with the message "Fatal server error: could not + open default font 'fixed'" or "Fatal server error: could not open default + cursor font 'cursor'". + A: All Xservers at least two fonts as the minimum: One fixed-width font + ("fixed") and one font for the cursor ("cursor"). Be sure that the font + path contains these fonts. + I created a tarball which contains only these two fonts, get it from + http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/fonts/Xp_dummyfonts.tar.gz + +- Q: Xprt refuses to start with the message "Fatal server error: no screens + found". What does that mean ? + A: This means that Xprt could not find any printers. Either there are no + printers installed, "lpstat"/"lpc" could not find any printers or the + configuration does not contain any manual printer configurations + (see Q/A item "Which program is used by default by Xprt to enumerate the + printers on my system" for further details...). + + Two solutions: + 1. Using "PSspooldir" model: + Xprt releases from http://xprint.mozdev.org/ provide the "PSspooldir" + model config for such cases. Just edit the "Xprinters" and add + this line: + -- snip -- + Printer spooldir_tmp_Xprintjobs + -- snip -- + this will add the pre-configured (see + ${XPCONFIGDIR}/C/print/attributes/printer) "spooldir_tmp_Xprintjobs" + printer which will send jobs to the directory "/tmp/Xprintjobs/" + instead to a printer queue. + (This feature was added in the xprint.mozdev.org release 007, see + http://xprint.mozdev.org/bugs/show_bug.cgi?id=2475 ("RFE: Need + model-config which spools print jobs in a predefined directory")) + + 2. Manual setup: + Step 1: Provide a simple "Xprinters" spec file which contains a dummy + queue. + Example: + # Create "Xprinters_onlydummy" file which turns autolookup of printers + # OFF (using "Augment_Printer_List %none%") and provides one dummy + # queue called "ps_myscript" instead (using "Printer ps_myscript") + % echo "Augment_Printer_List %none%" >Xprinters_onlydummy + % echo "Printer ps_myscript" >>Xprinters_onlydummy + Step 2: Edit ${XPCONFIGDIR}/C/print/attributes/printer and add these + two lines: + -- snip -- + ps_myscript.xp-model-identifier: PSdefault + ps_myscript.xp-spooler-command: /home/sanja/xprint_test/my_xprt_cat_script.sh + -- snip -- + This means that the printer "ps_myscript" now uses the "PSdefault" + printer model and it will feed the jobs to the script + "/home/sanja/xprint_test/my_xprt_cat_script.sh" (via stdin). + Note that the absolute path is required for "*xp-spooler-command". + Step 3: Start Xprt on display 18, passing the "Xprinters_onlydummy" + using the "-XpFile" option: + % Xprt -XpFile ./Xprinters_onlydummy -pn -ac -audit 4 :18 + +- Q: "Printing itself works but the printout covers only 1/4 of the paper + - what am I doing wrong ?" + A: This is usually an indicator for a wrong DPI setting. The default + "PSdefault" model config uses 300 DPI but some printers only support + 600 DPI. + - Workaround: + Edit ${XPCONFIGDIR}/C/print/attributes/document and replace the line + "*default-printer-resolution: 300" with + "*default-printer-resolution: 600" + (Note that locale-specific settings in + ${XPCONFIGDIR}/${LANG}/print/attributes/document always override values + set in ${XPCONFIGDIR}/C/print/attributes/document.) + - Solution: + Create a model-config for your printer which only contains attributes + supported by your printer ("printer-resolutions-supported" is the + attribute in the "model-config" which holds the space-seperated list + of DPI values which are supported by the printer). + +- Q: "Printing works but I get large borders/margins..." / "[Top] margin is too small" / + "Margins are wrong" / etc. + A: Two possible causes: + - Usually same issue as "Printing itself works but the printout covers + only 1/4 of the page"-issue: Wrong DPI. + Solution: Check the DPI value and adjust it as described in the FAQ item + above. Common DPI values for the PostScript DDX are 240, 300, 360, 400 + and 600 DPI. + - You are trying to print "US-letter" on a "DIN-A4" paper or "DIN-A4" on + "US-letter". + Solution: Check your paper settings + Note that the default papersize for Xprt depends on the locale + (e.g. on the env var ${LANG}) Xprt is running in - "en_US"&co. get + US-letter, all others use DIN-A4 (incl. german/austrian etc. locales)). + Exception from this rule: If the selected printer does not support the + default paper size it will set no default paper size for this printer + (then the application side has to make an explicit choice). + +- Q: Xprt prints a warning like "Xp Extension: could not find config dir + /usr/X11R6/lib/X11/C/print" - what does that mean ? + A: This is actually the worst case what can happen. + The message indicates that Xprt was unable to find it's configuration + data. + Solution: + - Install configuration data at the requested location + OR + - Set the ${XPCONFIGDIR} env var to the location of the Xprt + configuration directory. + +- Q: Xprt crashes with "Fatal server error: Beziers this big not yet supported" + What does that mean ? + A: This is a known issue in the X11R6.5.1 code. In rare cases some PostScript + Type1 fonts can trigger this. + See "My PS Type1 font does not work with my Xserver" ... + +- Q: "My PS Type1 font does not work with my Xserver - how can I fix this ?" + A: Some PS Type1 do not work out-of-the-box with all PS Type1 font engines - + some will work with the Adobe font engine (used in Solaris Xsun) but not + with the X.org font engine (or the other way round) or the fonts are + simply broken. + + The following procedure will try to fix this problem: + Get the "type1fix" perl script the TeXTrace package + (http://www.inf.bme.hu/~pts/textrace-latest.tar.gz) and run it over + the fonts. + + Example 1 (filter fonts): + # Broken PFA fonts are in broken_fonts/ + % mkdir fixed_fonts ; cd fixed_fonts + % for i in ../broken_fonts/*.pfa ; do + echo " ------- $i" ; + type1fix.pl --ofmt=pfa --infile=$i --outfile=$(basename ${i}) ; + done + + Example 2 (filter fonts and convert them to PFB on-the-fly; do not forget + to update "fonts.scale" and run "mkfontdir" (to update "fonts.dir") ; + systems which use the Adobe font engine (like Solaris/Xsun) may require + to run "makepsres", too): + # Broken PFA fonts are in broken_fonts/ + % mkdir fixed_fonts ; cd fixed_fonts + % for i in ../broken_fonts/*.pfa ; do + echo " ------- $i" ; + type1fix.pl --ofmt=pfb --infile=$i --outfile=$(basename ${i%.pfa}.pfb) ; + done + +- Q: I can't get it working. I have set ${DISPLAY} correctly to point to the + Xprt display and... ... What is going wrong ? + A: Do not set ${DISPLAY} to the Xprt server. You still need your normal + Xserver for your video card - Xprt is only for your printer(s). + Applications look up Xprt servers via the ${XPSERVERLIST} env var, _NOT_ + via the ${DISPLAY} env var. + +- Q: When I try to print via Xprint I get the message "Fatal server error: + unable to exec '/usr/bin/lp'". What is going wrong here ? + A: It usually means that the spooler application "/usr/bin/lp" would not be + launched. This is usually the result when /usr/bin/lp does not exist or + cannot be executed (for example, shell scripts without the +x flag etc.). + +- Q: The Solaris Xprt prints some error messages about PostScript fonts like + "FOOBAR not found, using Courier. CMEX0123 not found, using Courier." + etc. and uses "Courier" instead of these fonts... + A: The Solaris (Adobe-based) PostScript font engine requires a "PostScript + resource database" file named "PSres.upr" to use the PostScript fonts + correctly. + * Solution: + Steps to create the missing file: + 1. Go to the location where the matching fonts are installed (we're using + /home/sanja/mathml_fonts/tex_cmps/Type1/ in this example): + % cd /home/sanja/mathml_fonts/tex_cmps/Type1/ + 2. Create "PSres.upr" using the "makepsres" resource file + % makepsres + 3. Validation: + Make sure the file has been created: + % ls -l PSres.upr + 4. Restart Xprt server(s): + % /etc/init.d/xprint restart + 5. Restart application which uses these fonts + + The makepsres(1) manual page has some additional details about this + subject... + +- Q: "Xprt refused to start, complaining about a missing dir + (/etc/X11/xserver/C/print directory)... I created it by hand (empty) and + started Xprt but it still does not work properly..." + A: Xprt expects some config data in this directory. Just making it an + existing but empty dir will work around the error message but will not + result in a properly working Xprt since it has no (usefull) builtins + which would make it possible to run the binary without the config data. + Your X11 binary distribution should always come with the config data + (for example /usr/openwin/server/etc/XpConfig/ on Solaris) or you won't + be able to use Xprint (however it is possible to copy the config data + from another system :) + BTW: Source for the configs can be found under xc/programs/Xserver/XpConfig + +- Q: My Linux system already shipps with a '/usr/X11R6/bin/Xprt'-binary. + Do I need the binary distribution from http://xprint.mozdev.org/ ? + A: This depends on what is shipped with your Linux distribution. + Please check the "vendor" string of the Xprt server: + % Xprt :10 & + % xdpyinfo -display :10 | grep -i "vendor string" + If this outputs a line like "vendor string: The XFree86 Project, Inc" + then you have the Xprt binary build from Xfree86 sources - which are + broken - even the newest version [I'll update this as soon as Xfree86 + shipps with a working version]. + Xprt from Solaris, HP-UX and my own builds (which identifies itself as + "vendor string: xprint.mozdev.org" for releases >= 007, older releases + (e.g. <= 006) identify itself as as "vendor string: The X.Org Group") + are known to work proprtly. + +- Q: I am getting the error message "error opening security policy file + /usr/X11R6/lib/X11/xserver/SecurityPolicy". What does that mean ? + A: The policy file for the SECURITY extension cannot be found. + This is not serious unless you want to make use of features of the + SECURITY extensions (like treating clients as "untrusted", e.g. restrict + their access to certain Xserver resources). + Normally the missing policy file is a problem with your Unix/Linux X11 + distribution; consult your vendor where to get the missing file from. + Alternatively you can get the plain X11R6.6 security policy file from + ftp://ftp.x.org/pub/R6.6/xc/programs/Xserver/Xext/SecurityPolicy (copy it + to the matching location - but be sure that you do not overwrite any + existing security policy file). + +- Q: I have modified the "HPLJ4family" [or "HPDJ1600C" etc.] printer model to + work with my PostScript printer, but when I print I get empty places + where some text should be - what am I doing wrong here ? + A: The "HPLJ4family" and "HPDJ1600C" models are PCL-only, check + the model-config spec + (${XPCONFIGDIR}/C/print/models/${MODEL_NAME}/model-config) - if the + "xp-ddx-identifier" attribute says something with "PCL" (like + "XP-PCL-MONO" etc.) in the value string then this model-config is for + the PCL-DDX _only_ (e.g. their PMF fonts do not supply the neccesary + information (e.g. the "_ADOBE_POSTSCRIPT_FONTNAME" chunk is missing; + they only provide the "PCL_FONT_NAME" chunk) nor are these fonts + accessible via the PostScript-support in these printers. + A solution is to use the "PSdefault" model instead (and/or create your + customized own version of this model) - or look if there is a + model-config beginning with the same name and ending with "PS" (e.g. + "HPLJ4family-PS"). + +- Q: Xprt outputs warning messages like: + -- snip -- + Xp Extension: Can't load driver XP-PCL-MONO + init function missing + Xp Extension: Can't load driver XP-RASTER + init function missing + -- snip -- + What does that mean ? + A: Two possible problems: + 1. The requested driver is not supported by that version of Xprt. + For example Solaris 2.7 Xprt does not support XP-PCL-MONO nor the + XP-RASTER driver. + Valid values for the "xp-ddx-identifier" attribute in + ${XPCONFIGDIR}/*/print/attributes/printers and/or + ${XPCONFIGDIR}/*/print/models/*/model-config are + - Solaris 2.7: XP-POSTSCRIPT and XP-PCL-COLOR + - Solaris >=2.8: XP-POSTSCRIPT, XP-PCL-COLOR, XP-PCL-MONO and XP-RASTER + - HP-UX: XP-POSTSCRIPT, XP-PCL-COLOR, XP-PCL-MONO, XP-PCL-LJ3, + XP-PCL-DJ1200 and XP-RASTER + - xprint.mozdev.org release 007: XP-POSTSCRIPT and XP-RASTER + - xprint.mozdev.org release 008: XP-POSTSCRIPT, XP-PCL-COLOR, + XP-PCL-MONO, XP-PCL-LJ3 and XP-RASTER + - xprint.mozdev.org release >=1.0 (planned): XP-POSTSCRIPT, XP-PCL-COLOR, + XP-PCL-MONO, XP-PCL-LJ3, XP-RASTER and XP-PDF + 2. There may be too many drivers loaded into one Xprt instance. + By default a single Xserver instance can only handle three screens - and + since one Xprint DDX maps to one Xserver screen this limit applies to + the number of loaded Xprt drivers, too. + Starting with xprint.mozdev.org release 008 the per-Xserver screen limit + was increased from "3" to "8" to avoid this issue... + Workaround: Start a 2nd instance of Xprt which handles the other + drivers which do not fit into the first instance. + +- Q: Printing on Solaris with Mozilla/Eclipse [or any other Xprint client] + removes spaces between words. What is going wrong ? + A: This is a bug in the Solaris Xprint server binary (/usr/openwin/bin/Xprt). + Various bug reports have been filed, see + - http://xprint.mozdev.org/bugs/show_bug.cgi?id=3353 ("Solaris Xprt looses + space when rendering with '-monotype-arial-*'-fonts") + - http://bugzilla.mozilla.org/show_bug.cgi?id=199957 ("Solaris 8 Mozilla + removes spaces for text within <font face="Arial">...</font>") + Known workarounds: + - Remove the '-monotype-arial-*' fonts from the font path + - Use an alternate Xprint server like available in the "GISWxprint" package + (this package is identical to the "GISWxprintglue" package except that it + uses a Xprint server build from xprint.mozdev.org sources and not the + /usr/openwin/bin/Xprt binary from Solaris) + - Mozilla-only: Adding + -- snip -- + user_pref("print.xprint.font.rejectfontpattern", + "fname=-dt-.*;scalable=.*;outline_scaled=false;xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*|" + + "fname=-monotype-arial.*;scalable=.*;outline_scaled=.*;xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*"); + -- snip -- + to prefs.js works around the problem (see + http://bugzilla.mozilla.org/show_bug.cgi?id=199957#c6 , too). + +5. SOFTWARE DEVELOPMENT +- Q: How can I get the printable area (e.g. the portion of the page on which + the printer is physically capable of placing ink) of the paper after I + have chosen a paper ? + A: XpGetPageDimensions() returns the printable area and other information + about the page geometry. + +- Q: Do "offscreen" pixmaps work on Xprt ? + A: Yes, "offscreen" pixmaps are working on Xprt. + +- Q: How can I get the DPI value for the current Xprt server ? Can I use the + values from "xdpyinfo" ? + A: The Xprt screen resolution defines only the maximum resolution configured + for the matching DDX, the printers real DPI is obtained via an another + API (XprintUtil has a bunch of functions to get/set the document/page + resolution, see XpuGetResolutionList(), XpuFreeResolutionList(), + XpuGetResolution(), XpuSetPageResolution(), XpuSetDocResolution() and + XpuFindResolution()). + +- Q: Does Xprint/Xprt support font rotation ? + A: Yes - Xprint/Xprt supports font rotation at any angle via the matrix XLFD + enhancement (this even works for printer-builtin fonts !!). For details + see the paper "New Font Technology for X11R6" by Nathan Meyers <XXX: URL ?>. + Short: + The transformation-matrix for rotation can be calculated like this: + +-- --+ + | cos(angle) sin(angle)| + | | + |-sin(angle) cos(angle)| + +-- --+ + Examples: + 1. the following code fragment obtains a 180 degree rotated font (matrix [-1 0 0 -1]): + -- snip -- + ... = XLoadQueryFont(..., "-adobe-courier-bold-r-normal--*-[~24 0 0 ~24]-0-0-m-*-iso8859-1"); + -- snip -- + 2. the following code fragment obtains a 90 degree rotated font (matrix [0 1 -1 0]): + -- snip -- + ... = XLoadQueryFont(..., "-adobe-courier-bold-r-normal--*-[0 24 ~24 0]-0-0-m-*-iso8859-1"); + -- snip -- + +- Q: When I render something on my window and call XpStartPage() all the + rendered stuff is gone, I only get a white, empty paper. + What is going wrong here ? + A: Remember the rule that "only those drawings are printed on the paper which + were rendered between XpStartPage() and XpEndPage()". + XpStartPage() clears the window you passed as argument, e.g. it creates + a new, blank sheet of paper where you can do your rendering stuff on. + XpEndpage() then pushes the "paper sheet" to the stash of papers from the + document in process. + Solution - if you want to render something once for multiple or all pages: + Render on a offscreen pixmap and copy (with XCopyArea()) the content to + the "paper" drawable (after calling XpStartPage()) - XpStartpage() only + affects the window passed as parameter. + +- Q: What is XpStartDoc() for ? + A: ISO 10175 and some advanced printing systems by IBM and HP had set forth + the standard that a "Job" is made up of one or more "Documents", and + each document is made up of one or more "Pages". Xprint was designed that + in a true ISO 10175 environment/implementation (lp(1) on steroids, and + with an API), Xprt can actually learn about all printers and their + capabilities though API's into the printer subsystem (vs. using config + files), map Job/Doc/Page directly into ISO 10175 equivalents, and use + APIs to view job status and kill jobs (vs. cancel(1), lpcancel(1), + lpstatus(1)). + Because most applications of the day are only printing one document per + job, XpStartPage() was designed that it generates a "synthetic" + XpStartDoc() if it has not been called yet. + +- Q: How does the XLFD for printer-builtin fonts look like ? + A: XXX + +- Q: How can I scale images using the Xprint API ? + A: XXX + +- Q: How do I use the XprintUtil library ? + A: XXX + +- Q: Why does XGetImage() not work for Xprt ? + A: There are at least two reasons why XGetImage() does not work for Xprt: + 1. Most of the Xprt DDX implementations do not render itself on any + bitmaps like the framebuffer(=video) DDX do, they translate the + rendering commands into the matching commands of the printer language + (it is technically possible to implement such support for XGetImage() + even for those drivers - but there is reason [2]:) + 2. Xprt usually operates at high resolutions which results in very large + dimensions. If a client would request the 24bit TrueColor _bitmap_ + data for a _whole_ DIN-A4 page at 2400 DPI a data chunk of ~173 + megabytes would be the response. This would be more or less a + DOS(=Denial of Service) for either the client, the network and/or the + server. + +- Q: How to print with Xt/Athena widgets ? + A: XXX + +- Q: How to print with Xt/Motif widgets ? + A: XXX + +- Q: What are the differences between normal display and Xprint display ? + A: XXX + +- Q: How can I find/identify printer-builtin fonts ? + A: XXX + +- Q: How do I scale images ? + A: XXX + +- Q: libXp Image scaling vs. max. request size ? + A: XXX + +- Q: How can I use XprintUtils ? + A: XXX + +- Q: How do I calculate the DPI values for Xprt DDX screens ? + A: XXX + +- Q: How do I find scaleable fonts ? + A: XXX + +- Q. How do I find printer-builtin fonts ? + A: XXX + +- Q: The XLFD for printer-builtin fonts look like bitmap fonts - is that bad ? + A: XXX + +- Q: When can I use printer-buildin fonts ? + A: XXX + +- Q: Where can I find examples fir adding Xprint support to my Xt/Athena application ? + A: XXX + +- Q: Where can I find examples fir adding Xprint support to my Xt/Motif application + (without the need for CDE's DtPrint library) ? + A: XXX + +- Q: Where can I find examples fir adding Xprint support to my Qt application ? + A: XXX + + +6. KNOWN BUGS: + ('P'=Problem, 'S'=Solution) + - P: Xprt build from Xfree86 sources is completely broken and unuseable. + S: Build Xprt from the CVS tree at http://xprint.mozdev.org/ or the + X.org X11R6.5.1 sources (note that the client side Xprint extension + library ("libXp.so") from Xfree86 is not broken and do not need to be + replaced). + + - 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 + download PS Type1 fonts. + S: Patch available, I am looking for a way to get the patch into the X11 + and Solaris source trees... + + - 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". + S: Either convert PFB (PS Type 1 binary font) to PFA format and adjust + the fonts.dir and fonts.scale file or get a patch for the sources. + 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: 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). + S: Xprt build from xprint.mozdev.org sources has been fixed in release + 007, see http://xprint.mozdev.org/bugs/show_bug.cgi?id=1378 ("PS DDX + creates n^2 copies of a job instead of n copies") and + http://bugzilla.mozilla.org/show_bug.cgi?id=140030 ("Setting number + of copies causes too many copies to print") for details. + Solaris 2.7 Xprt still suffers from this issue... ;-( + + XXX XXX XXX + +7. UNANSWERED QUESTIONS + (My small ToDo list what I will write soon; 379 items missing... =:-) + Email me if you want one of these answered "now" and/or to contribute + an answer... :) + - Q: How do I create a model-config for my printer ? + - Q: How can I customize a model-config for my site/machine ? + - Q: Which attributes/values can be set in a model-config ? + - Q: Why can't I set default values (for my {paper size, resolution, ...}) + in the model-config ? + - Q: Should I add the fonts in the model-config dir to the Xserver's + font path ? + - Q: What are the fonts in the model-config dir for ? + - Q: Can I use a font server for all fonts instead of passing then directly + to the Xprint server ? + - Q: Does the Xprint PostScript driver do full rasterisation of the + print job ? + - Q: Is it possible to prepare a printer config entry so that the PS output + is piped to "ps2pdf" and will produce directly a PDF file? It would be + nice to have mozilla directly producing PDF files when printing. + - Q: Problem: I have changed the Xprt config - but "xplsprinters -l" + (or any other Xprint application) does not show the change. + Any idea what I am doing wrong ? + - Q: How can I add a font path to Xprt ? + - Q: Why does "xset +fp path_to_font" not work in some cases ? + - Q: How can I get a "core"-dump when Xprt crashes ? + - Q: How can I debug Xprt (hint: use "-audit 4") ? + - Q: How can I debug Xprt with Sun Workshop (hint: "check -access") ? + - Q: How can I check whether Xprint is "active" ? / How can I verify that a Xprint is working ? + + XXXX XXXX XXXX + +8. ACKNOWLEDGEMENTS + We'd like like to express their gratitude to the whole community for + providing insightful answers to innumerable questions. In particular, + the following people (listed alphabetically) have contributed to this + FAQ (apologies, in advance, if anyone has been forgotten): + + Alan Coopersmith <alan.coopersmith@sun.com> + Thomas Gilg <thomas_gilg@hp.com> + Jay Hobson <jay.hobson@sun.com> + Masaki Katakai <katakai@japan.sun.com> + Simon Montagu <smontagu@netscape.com> + Drew Parsons <dparsons@debian.org> + (and many many others) + +# EOF. + + diff --git a/hardcopy/XPRINT/docbook.css b/hardcopy/XPRINT/docbook.css new file mode 100644 index 0000000..878d4cd --- /dev/null +++ b/hardcopy/XPRINT/docbook.css @@ -0,0 +1,570 @@ + +/* Catch-all */ +* { display: inline; } + +/* + * Headers + */ +bookinfo, bookinfo > *, +articleinfo, articleinfo > * { + display: block; +} + +address > * { + display: block; +} + +copyright { + margin: 0.5cm; + text-align: center; + font-weight: bold; +} + +year:before { + content: "Copyright \00a9 "; +} + +phone:before { + content: "Tel: "; +} + +fax:before { + content: "Fax: "; +} + +email:before { + content: "Email: "; +} + +address *, +authorgroup * { + text-align: center; + display: block; +} + +productname { + display: none; +} + +/* + * Basic elements + */ +set, book, article, preface, chapter, appendix, bibliography, +section, sect1, sect2, sect3, sect4, sect5, +title, subtitle, simpara, para, +itemizedlist, orderedlist, glosslist, glossentry, glossterm, variablelist, +mediaobject, imageobject, imagedata, caption, example, informalexample, screen, programlisting, footnote +{ + display: block; + font-family: serif; +} + +para { + text-align: justify; +} + +set { +/* + background-image: url("citeclogo.png"); +*/ + background-color: white; + background-repeat: no-repeat; + color: black; + padding-top: 60px; +} + +set, book, article { + margin-right: 0pt; + padding-right: 0pt; +} + +book:before, article:before { +/* + content: url(citec-globe.png); +*/ +} + +glossentry, varlistentry { + padding-left: 2em; +} + +glossdef, +glossdef > para { + display: inline; + margin-left: 0pt; +} + +varlistentry > listitem { + display: block; +} + +varlistentry > term { + margin-right: 1em; + position: relative; + left: -2em; +} + +glossterm { + margin-right: 1em; + position: relative; + left: -1em; +} + +sect1, sect2, sect3, sect4, sect5, section, para, itemizedlist, orderedlist, variablelist { + margin: 0.5em; + margin-right: 0pt; + padding: 0.5em; + padding-right: 0pt; +} + +sect2 { + margin-top: 3ex; + padding-top: 0pt; + margin-bottom: 3ex; + padding-bottom: 0pt; +} + +sect2 { + margin-left: 0.5em; + padding-left: 0.5em; + border-left: 10px solid lightgrey; +} + +title { + display: block; + font-family: sans-serif; + font-size: larger; + font-weight: bold; + text-align: left; +} + +example * { + background-color: transparent; + color: #8b0000; + font-weight: normal; +} + +example literallayout { + background-color: transparent; + color: black; +} + +example > title { + font-size: medium; + text-decoration: underline; + margin-bottom: 1ex; +} + +example > title:after { + content: ":"; +} + +book > * > title, +article > * > title { + font-size: xx-large; +} + +book > * > * > title, +article > * > * > title { + font-size: x-large; +} + +book > * > * > * > title, +article > * > * > * > title { + font-size: large; + font-weight: bold; +} + +book > * > * > * > * > title, +article > * > * > * > * > title { + font-size: larger; + font-weight: normal; +} + +book > * > * > * > * > * > title, +article > * > * > * > * > * > title { + font-size: medium !important; + font-weight: normal !important; +} + +title + subtitle { + display: block; + font-weight: bold; + font-size: smaller; +} + +book > title, +article > title, +book > subtitle, +article > subtitle { + text-align: center; + font-size: xx-large; + font-weight: bold; + padding-top: 1ex; + padding-left: 2em; + padding-right: 2em; + margin-top: 1ex; + margin-bottom: 1ex; +} + +book > subtitle, +article > subtitle { + font-size: x-large; + font-style: italic; +} + +preface, chapter, appendix, bibliography { + padding: 1em; + padding-top: 2ex; + border-top: 8px solid #bebebe; + page-break-before: always; +} + +preface:before { + content: "Preface:"; + font-size: large; + font-style: italic; +} + +appendix:before { + content: "Appendix:"; + font-size: large; + font-style: italic; +} + +preface > *, chapter > *, appendix > *, bibliography > * { + margin-right: 1em; +} + +itemizedlist > *, +orderedlist > * { + margin-top: 0.5em; + margin-bottom: 0.5em; +} + +itemizedlist > listitem, +orderedlist > listitem { + display: list-item; + position: relative; + left: 1em; +} + +varlistentry { + display: list-item; + list-style-type: none; +} + +listitem > para { + margin: 0pt !important; + padding: 0pt !important; +} + +itemizedlist > listitem > itemizedlist > listitem { + list-style-type: circle; +} + +orderedlist > listitem { +/* list-style-type: decimal; */ + list-style-type: square; +} + +glossterm, term { + font-weight: bold; +} + +note, note * { + color: #505000; + background-color: transparent; +} + +note { + display: block; + margin: 1em; + padding: 0.3em; + border: 2px dotted #505000; +} + +quote { + font-style: italic; +} + +mediaobject { + text-align: center; +} + +entry[morerows] { + background-color: lightgreen; + color: black; + font-weight: bold; +} + +entry { + font-family: sans-serif; +} + +thead entry { + font-weight: bold; + font-size: larger; + background-color: #bebebe; + color: white; +} + +superscript { + vertical-align: super; + font-size: smaller; +} + +emphasis { + font-style: italic; +} + +@media print { + ulink:after { + content: " [URL: " attr(url) "]"; + } +} + +computeroutput, userinput { + font-family: monospace; + font-weight: bold; + text-align: left; + white-space: inherit; +} + +literallayout, programlisting { + font-family: monospace; + white-space: pre; +} + +informalexample, example, programlisting { + border: 2px dotted darkred; + padding: 0.5em; + margin: 0.5em; +} + +footnote { + float: right; + width: 50%; + font-size: smaller; + margin: 0.5em; + margin-right: 0pt; + padding: 0.5em; + border: 1px solid darkred; +} + +footnote > * { + margin: 0pt; + padding: 0pt; +} + +programlisting, example { + clear: right; +} + +/* ---------------------------------- */ +abbrev, accel, acronym, action, application, artpagenums, authorinitials, +bibliocoverage, biblioid, bibliomisc, bibliorelation, bibliosource, citation, +citebiblioid, citerefentry, citetitle, city, classname, co, command, +computeroutput, constant, coref, country, database, date, email, emphasis, +envar, errorcode, errorname, errortext, errortype, exceptionname, fax, +filename, firstname, firstterm, funcdef, funcparams, function, group, +guibutton, guiicon, guilabel, guimenu, guimenuitem, guisubmenu, hardware, +honorific, initializer, inlineequation, inlinegraphic, inlinemediaobject, +interface, interfacename, invpartnumber, isbn, issn, keycap, keycode, +keycombo, keysym, lineage, lineannotation, link, literal, markup, medialabel, +member, menuchoice, methodname, methodparam, modifier, mousebutton, olink, +ooclass, ooexception, oointerface, option, optional, orgdiv, orgname, +otheraddr, othername, pagenums, paramdef, parameter, phone, phrase, pob, +postcode, productname, productnumber, prompt, property, pubdate, pubsnumber, +quote, refpurpose, replaceable, returnvalue, revnumber, seriesvolnums, +sgmltag, shortcut, state, street, structfield, structname, subscript, +superscript, surname, symbol, systemitem, token, trademark, type, ulink, +userinput, varname, volumenum, wordasword, year { + display:inline; +} + +abstract, ackno, address, answer, appendix, article, attribution, authorblurb, +bibliodiv, biblioentry, bibliography, bibliomixed, bibliomset, biblioset, +blockquote, book, callout, calloutlist, caption, caution, chapter, +cmdsynopsis, colophon, constraintdef, dedication, epigraph, equation, example, +figure, formalpara, glossary, glossdef, glossdiv, glossentry, glosslist, +graphic, graphicco, highlights, imageobjectco, important, index, indexdiv, +indexentry, informalequation, informalexample, informalfigure, informaltable, +itemizedlist, legalnotice, listitem, lot, lotentry, mediaobject, +mediaobjectco, msg, msgentry, msgexplan, msgmain, msgset, note, orderedlist, +para, part, partintro, personblurb, preface, primaryie, printhistory, +procedure, productionset, programlistingco, qandadiv, qandaentry, qandaset, +question, refentry, refentrytitle, reference, refnamediv, refsect1, refsect2, +refsect3, refsection, refsynopsisdiv, revhistory, screenco, screenshot, +secondaryie, sect2, sect3, sect4, sect5, section, seealsoie, seeie, set, +setindex, sidebar, simpara, simplemsgentry, simplesect, step, substeps, +subtitle, synopfragment, synopfragmentref, table, term, tertiaryie, tip, +title, toc, tocback, tocchap, tocentry, tocfront, toclevel1, toclevel2, +toclevel3, toclevel4, toclevel5, tocpart, variablelist, varlistentry, warning, +sect1 { + display:block; +} + +appendixinfo, area, areaset, areaspec, articleinfo, bibliographyinfo, +blockinfo, bookinfo, chapterinfo, colspec, glossaryinfo, indexinfo, itermset, +modespec, objectinfo, partinfo, prefaceinfo, primary, refentryinfo, +referenceinfo, refmeta, refsect1info, refsect2info, refsect3info, +refsectioninfo, refsynopsisdivinfo, screeninfo, secondary, sect1info, +sect2info, sect3info, sect4info, sect5info, sectioninfo, see, seealso, +setindexinfo, setinfo, sidebarinfo, spanspec, tertiary { + display:none; +} + +classsynopsisinfo, funcsynopsisinfo, literallayout, programlisting, screen, +synopsis { + white-space:pre; + font-family:monospace; + display:block; +} +/* + * CSS2 styling for DocBook XML + */ + +article, book { + margin:.5em; +} + +title { + font-weight:bolder; + margin-top:1em; + margin-bottom:.5em; + font-family:sans-serif; +} +section>* { + margin-left:10%; + margin-right:10%; +} +section>section, section>title { + margin-left:0; + margin-right:0; +} + +book>title, article>title { + font-size:xx-large; + text-align:center; + border-bottom-style:solid; +} + +chapter>title { + font-size:xx-large; + text-align:center; +} + +section>title { + font-size:xx-large; +} + +section>section>title { + font-size:x-large; + margin-left:5%; +} + +section>section>section>title { + font-size:large; + margin-left:7.5%; +} + +section>section>section>section>title { + margin-left:10%; +} + +section>section>section>section>section>title { + font-size:normal; + margin-left:10%; +} + + +*+para { + margin-top:.5em; +} + +example, informalexample { + background-color:#dddddd; +} + +quote:before { + content: open-quote; +} + +quote:after { + content: close-quote; +} + +question, answer { + margin-top:.5em; + display:list-item; +} + +question>para, answer>para { + display:inline; +} + +question:before { + display:marker; + content:"Q: "; + font-weight:bolder; +} + +answer:before { + display:marker; + content: "A: "; + font-weight: bolder; +} + +emphasis { + font-style:italic; +} + +sgmltag[class="starttag"]:before { + content: "<" +} + +sgmltag[class="starttag"]:after { + content: ">" +} + +sgmltag[class="endtag"]:before { + content: "</" +} + +sgmltag[class="endtag"]:after { + content: ">" +} + +keycap+keycap:before { + content:"-" +} + +ulink { + color:#0000ff; + text-decoration:underline; +} +ulink:hover { + cursor:pointer; +} + +blockquote { + padding-left:3em; +} + +attribution { + text-align:right; +} +attribution:before { + content:"--" +} + +itemizedlist>listitem { + display:list-item; +} + +filename, literal { + font-family:monospace; +} + +/* EOF. */ diff --git a/hardcopy/XPRINT/dtprint_fspec.PS.gz b/hardcopy/XPRINT/dtprint_fspec.PS.gz Binary files differnew file mode 100644 index 0000000..ad5d1ab --- /dev/null +++ b/hardcopy/XPRINT/dtprint_fspec.PS.gz diff --git a/hardcopy/XProtocol/proto.PS.gz b/hardcopy/XProtocol/proto.PS.gz Binary files differindex 3b5297f..490b303 100644 --- a/hardcopy/XProtocol/proto.PS.gz +++ b/hardcopy/XProtocol/proto.PS.gz diff --git a/hardcopy/XProtocol/proto.idx.PS.gz b/hardcopy/XProtocol/proto.idx.PS.gz Binary files differindex 6b31657..5b2a4f2 100644 --- a/hardcopy/XProtocol/proto.idx.PS.gz +++ b/hardcopy/XProtocol/proto.idx.PS.gz diff --git a/hardcopy/Xaw/widg.idx.PS.gz b/hardcopy/Xaw/widg.idx.PS.gz Binary files differindex a0f6240..b7981d4 100644 --- a/hardcopy/Xaw/widg.idx.PS.gz +++ b/hardcopy/Xaw/widg.idx.PS.gz diff --git a/hardcopy/Xaw/widgets.PS.gz b/hardcopy/Xaw/widgets.PS.gz Binary files differindex 078b7d7..6b1bd1f 100644 --- a/hardcopy/Xaw/widgets.PS.gz +++ b/hardcopy/Xaw/widgets.PS.gz diff --git a/hardcopy/Xext/DPMS.PS.gz b/hardcopy/Xext/DPMS.PS.gz Binary files differindex 543f8c5..b34f290 100644 --- a/hardcopy/Xext/DPMS.PS.gz +++ b/hardcopy/Xext/DPMS.PS.gz diff --git a/hardcopy/Xext/DPMSLib.PS.gz b/hardcopy/Xext/DPMSLib.PS.gz Binary files differindex 8bb9254..74c01d1 100644 --- a/hardcopy/Xext/DPMSLib.PS.gz +++ b/hardcopy/Xext/DPMSLib.PS.gz diff --git a/hardcopy/Xext/bigreq.PS.gz b/hardcopy/Xext/bigreq.PS.gz Binary files differindex 63e884e..3bb2419 100644 --- a/hardcopy/Xext/bigreq.PS.gz +++ b/hardcopy/Xext/bigreq.PS.gz diff --git a/hardcopy/Xext/evi.PS.gz b/hardcopy/Xext/evi.PS.gz Binary files differindex 385ec8b..705e20e 100644 --- a/hardcopy/Xext/evi.PS.gz +++ b/hardcopy/Xext/evi.PS.gz diff --git a/hardcopy/Xext/record.PS.gz b/hardcopy/Xext/record.PS.gz Binary files differindex a75c54e..c6137f4 100644 --- a/hardcopy/Xext/record.PS.gz +++ b/hardcopy/Xext/record.PS.gz diff --git a/hardcopy/Xext/recordlib.PS.gz b/hardcopy/Xext/recordlib.PS.gz Binary files differindex 79a95b2..149cd22 100644 --- a/hardcopy/Xext/recordlib.PS.gz +++ b/hardcopy/Xext/recordlib.PS.gz diff --git a/hardcopy/Xext/security.PS.gz b/hardcopy/Xext/security.PS.gz Binary files differindex 740b427..a4c0ffc 100644 --- a/hardcopy/Xext/security.PS.gz +++ b/hardcopy/Xext/security.PS.gz diff --git a/hardcopy/Xext/shape.PS.gz b/hardcopy/Xext/shape.PS.gz Binary files differindex a0e1330..d270ae4 100644 --- a/hardcopy/Xext/shape.PS.gz +++ b/hardcopy/Xext/shape.PS.gz diff --git a/hardcopy/Xext/shapelib.PS.gz b/hardcopy/Xext/shapelib.PS.gz Binary files differindex 8785f61..13b1990 100644 --- a/hardcopy/Xext/shapelib.PS.gz +++ b/hardcopy/Xext/shapelib.PS.gz diff --git a/hardcopy/Xext/sync.PS.gz b/hardcopy/Xext/sync.PS.gz Binary files differindex 24c369c..18692a4 100644 --- a/hardcopy/Xext/sync.PS.gz +++ b/hardcopy/Xext/sync.PS.gz diff --git a/hardcopy/Xext/synclib.PS.gz b/hardcopy/Xext/synclib.PS.gz Binary files differindex 11fa3e9..344c000 100644 --- a/hardcopy/Xext/synclib.PS.gz +++ b/hardcopy/Xext/synclib.PS.gz diff --git a/hardcopy/Xext/tog-cup.PS.gz b/hardcopy/Xext/tog-cup.PS.gz Binary files differindex d6836c6..fe9d7e7 100644 --- a/hardcopy/Xext/tog-cup.PS.gz +++ b/hardcopy/Xext/tog-cup.PS.gz diff --git a/hardcopy/Xext/xc-misc.PS.gz b/hardcopy/Xext/xc-misc.PS.gz Binary files differindex 1eae2f9..b9ecebe 100644 --- a/hardcopy/Xext/xc-misc.PS.gz +++ b/hardcopy/Xext/xc-misc.PS.gz diff --git a/hardcopy/Xi/lib.PS.gz b/hardcopy/Xi/lib.PS.gz Binary files differindex d96925d..45c64c6 100644 --- a/hardcopy/Xi/lib.PS.gz +++ b/hardcopy/Xi/lib.PS.gz diff --git a/hardcopy/Xi/port.PS.gz b/hardcopy/Xi/port.PS.gz Binary files differindex 19e9651..32d716d 100644 --- a/hardcopy/Xi/port.PS.gz +++ b/hardcopy/Xi/port.PS.gz diff --git a/hardcopy/Xi/proto.PS.gz b/hardcopy/Xi/proto.PS.gz Binary files differindex 30eb0eb..bd45e61 100644 --- a/hardcopy/Xi/proto.PS.gz +++ b/hardcopy/Xi/proto.PS.gz diff --git a/hardcopy/Xmu/xmu.PS.gz b/hardcopy/Xmu/xmu.PS.gz Binary files differindex eabecfb..69c72ec 100644 --- a/hardcopy/Xmu/xmu.PS.gz +++ b/hardcopy/Xmu/xmu.PS.gz diff --git a/hardcopy/Xt/intr.idx.PS.gz b/hardcopy/Xt/intr.idx.PS.gz Binary files differindex d6bca14..4b15faf 100644 --- a/hardcopy/Xt/intr.idx.PS.gz +++ b/hardcopy/Xt/intr.idx.PS.gz diff --git a/hardcopy/Xt/intrinsics.PS.gz b/hardcopy/Xt/intrinsics.PS.gz Binary files differindex e0cee8f..ca2efad 100644 --- a/hardcopy/Xt/intrinsics.PS.gz +++ b/hardcopy/Xt/intrinsics.PS.gz diff --git a/hardcopy/i18n/Framework.PS.gz b/hardcopy/i18n/Framework.PS.gz Binary files differindex 7c48a4d..b95fcfd 100644 --- a/hardcopy/i18n/Framework.PS.gz +++ b/hardcopy/i18n/Framework.PS.gz diff --git a/hardcopy/i18n/LocaleDB.PS.gz b/hardcopy/i18n/LocaleDB.PS.gz Binary files differindex 7cc6db2..3c7eb55 100644 --- a/hardcopy/i18n/LocaleDB.PS.gz +++ b/hardcopy/i18n/LocaleDB.PS.gz diff --git a/hardcopy/i18n/Trans.PS.gz b/hardcopy/i18n/Trans.PS.gz Binary files differindex 1d66350..8c7fa29 100644 --- a/hardcopy/i18n/Trans.PS.gz +++ b/hardcopy/i18n/Trans.PS.gz diff --git a/man/general/Consortium.man b/man/general/Consortium.man index 1a433c5..b708019 100644 --- a/man/general/Consortium.man +++ b/man/general/Consortium.man @@ -24,7 +24,7 @@ .\" dealing in this Software without prior written authorization from the .\" X Consortium. .\" -.\" $XFree86: xc/doc/man/general/Consortium.man,v 1.4 2001/01/27 18:20:38 dawes Exp $ +.\" $XFree86$ .\" .TH XCONSORTIUM __miscmansuffix__ __xorgversion__ .SH NAME diff --git a/man/general/Standards.man b/man/general/Standards.man index a253a34..74da041 100644 --- a/man/general/Standards.man +++ b/man/general/Standards.man @@ -1,169 +1,159 @@ .\" $Xorg: Standards.cpp,v 1.3 2000/08/17 19:42:04 cpqbld Exp $ -.\" Copyright (c) 1993, 1994, 1996 X Consortium -.\" -.\" Permission is hereby granted, free of charge, to any person obtaining -.\" a copy of this software and associated documentation files (the +.\" $XdotOrg$ +.\" Copyright (c) 1993, 1994, 1996, 2004 The Open Group +.\" +.\" All rights reserved. +.\" +.\" Permission is hereby granted, free of charge, to any person obtaining a +.\" copy of this software and associated documentation files (the .\" "Software"), to deal in the Software without restriction, including .\" without limitation the rights to use, copy, modify, merge, publish, -.\" distribute, sublicense, and/or sell copies of the Software, and to -.\" permit persons to whom the Software is furnished to do so, subject to -.\" the following conditions: -.\" -.\" The above copyright notice and this permission notice shall be included -.\" in all copies or substantial portions of the Software. -.\" +.\" distribute, and/or sell copies of the Software, and to permit persons +.\" to whom the Software is furnished to do so, provided that the above +.\" copyright notice(s) and this permission notice appear in all copies of +.\" the Software and that both the above copyright notice(s) and this +.\" permission notice appear in supporting documentation. +.\" .\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS .\" OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF -.\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. -.\" IN NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR -.\" OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, -.\" ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR -.\" OTHER DEALINGS IN THE SOFTWARE. -.\" -.\" Except as contained in this notice, the name of the X Consortium shall -.\" not be used in advertising or otherwise to promote the sale, use or -.\" other dealings in this Software without prior written authorization -.\" from the X Consortium. +.\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT +.\" OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR +.\" HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL +.\" INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING +.\" FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, +.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION +.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. .\" -.\" $XFree86: xc/doc/man/general/Standards.man,v 1.4 2001/01/27 18:20:38 dawes Exp $ +.\" Except as contained in this notice, the name of a copyright holder +.\" shall not be used in advertising or otherwise to promote the sale, use +.\" or other dealings in this Software without prior written authorization +.\" of the copyright holder. .\" +.\" X Window System is a trademark of The Open Group. .\" .TH XSTANDARDS __miscmansuffix__ __xorgversion__ .SH NAME -XStandards \- X Consortium Standards and X Project Team Specifications +XStandards \- X Window System Standards and Specifications .SH SYNOPSIS The major goal of the X Consortium was to promote cooperation within the computer industry in the creation of standard software interfaces at -all layers in the X Window System environment. +all layers in the X Window System environment. The X Consortium produced standards - documents which defined network protocols, programming interfaces, and other aspects of the X environment. These standards -continue to exist in The Open Group's X Project Team -releases. The X Project Team produces specifications. -Like X Consortium Standards, these are documents +continue to exist in the X.Org Foundation releases. +The X.Org Foundation also produces specifications. +Like X Window System Standards, these are documents which define network protocols, programming interfaces, and other aspects of the X environment. Under the aegis -of The Open Group, X Consortium standards, X Project -Team specifications, and other specifications are the +of The Open Group, X Window System standards, X.Org Foundation +specifications, and other specifications are the basis for portions of The Open Group's various CAE specifications. .PP The status of various standards, specifications, and -the software in the X11R6.4 distribution, is explained below. +the software in the X11R6.7 distribution, is explained below. .SH STANDARDS -The following documents are X Consortium standards: +The following documents are X Window System standards: .nf X Window System Protocol -X Version 11, Release 6.4 +X Version 11, Release 6.7 Robert W. Scheifler Xlib \- C Language X Interface -X Version 11, Release 6.4 +X Version 11, Release 6.7 James Gettys, Robert W. Scheifler, Ron Newman X Toolkit Intrinsics \- C Language Interface -X Version 11, Release 6.4 +X Version 11, Release 6.7 Joel McCormack, Paul Asente, Ralph R. Swick, Donna Converse Bitmap Distribution Format Version 2.1 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Inter-Client Communication Conventions Manual Version 2.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 David Rosenthal, Stuart W. Marks Compound Text Encoding Version 1.1 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Robert W. Scheifler X Logical Font Description Conventions Version 1.5 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Jim Flowers, Stephen Gildea X Display Manager Control Protocol -Version 1.0 -X Version 11, Release 6.4 +Version 1.1 +X Version 11, Release 6.7 Keith Packard X11 Nonrectangular Window Shape Extension -Version 1.0 -X Version 11, Release 6.4 +Version 1.0.1 +X Version 11, Release 6.7 Keith Packard X11 Input Extension Protocol Specification Version 1.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 George Sachs, Mark Patrick X11 Input Extension Library Specification -X Version 11, Release 6.4 +X Version 11, Release 6.7 Mark Patrick, George Sachs The X Font Service Protocol Version 2.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Jim Fulton -PEX Protocol Specification -Version 5.1 -Cheryl Huntington (architect), Paula Womack (editor) - -PEXlib Specification and C Language Binding -Version 5.1 -Jeff Stevenson - Inter-Client Exchange (ICE) Protocol Version 1.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Robert Scheifler, Jordan Brown Inter-Client Exchange (ICE) Library Version 1.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Ralph Mor X Session Management Protocol Version 1.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Mike Wexler X Session Management Library Version 1.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Ralph Mor The Input Method Protocol Version 1.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Masahiko Narita, Hideki Hiura X Synchronization Extension Version 3.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Tim Glauert, Dave Carver, Jim Gettys, David P. Wiggins -X Image Extension, Protocol Reference Manual -Version 5.0 -X Version 11, Release 6.4 -Bob Shelley - XTEST Extension Version 2.2 Kieron Drake Big Requests Extension Version 2.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Bob Scheifler XC-MISC Extension Version 1.1 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Bob Scheifler, Dave Wiggins Double Buffer Extension @@ -179,41 +169,41 @@ Version 1.13 Martha Zimet, Stephen Gildea X Keyboard Extension Protocol -X Version 11, Release 6.4 +X Version 11, Release 6.7 Erik Fortune X Keyboard Extension Library -X Version 11, Release 6.4 +X Version 11, Release 6.7 Amber J. Benson, Gary Aitken, Erik Fortune, Donna Converse, George Sachs, and Will Walker X Print Extension Protocol -X Version 11, Release 6.4 +X Version 11, Release 6.7 X Print Extension Library -X Version 11, Release 6.4 +X Version 11, Release 6.7 X Application Group Extension Protocol and Library Version 1.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Kaleb Keithley X Security Extension Protocol and Library Version 4.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Dave Wiggins X Proxy Manager Protocol -X Version 11, Release 6.4 +X Version 11, Release 6.7 Ralph Swick LBX Extension Protocol and Library -X Version 11, Release 6.4 +X Version 11, Release 6.7 Keith Packard, Dave Lemke, Donna Converse, Ralph Mor, Ray Tice Remote Execution MIME Type Version 1.0 -X Version 11, Release 6.4 +X Version 11, Release 6.7 Arnaud Le Hors .fi .SH SPECIFICATIONS @@ -232,23 +222,6 @@ X Display Power Management (DPMS) Extension Protocol and Library Version 1.0 Rob Lembree -.SH "DRAFT STANDARDS" -The following documents are currently draft standards of the X Consortium. -.nf - -X Image Extension Library -Public Review Draft -Gary Rogers - -PEX Protocol Specification -Version 5.2 -Jeff Stevenson (architect), Jane Sczechowski (editor) - -PEXlib Specification and C Language Binding -Version 5.2 -Karl Schultz -.fi - .SH "INCLUDE FILES" The following include files are part of the Xlib standard. .PP @@ -305,16 +278,6 @@ The following include files are part of the X Input Extension standard. <X11/extensions/XIproto.h> .fi .PP -The following include files are part of the PEXlib standard. -.PP -.nf -<X11/PEX5/PEX.h> -<X11/PEX5/PEXlib.h> -<X11/PEX5/PEXlibint.h> -<X11/PEX5/PEXproto.h> -<X11/PEX5/PEXprotost.h> -.fi -.PP The following include files are part of the ICElib standard. .PP .nf @@ -340,15 +303,6 @@ The following include file is part of the Synchronization standard. <X11/extensions/sync.h> .fi .PP -The following include files are part of the XIElib draft standard. -.PP -.nf -<X11/extensions/XIE.h> -<X11/extensions/XIElib.h> -<X11/extensions/XIEproto.h> -<X11/extensions/XIEprotost.h> -.fi -.PP The following include file is part of the XTEST standard. .PP .nf @@ -417,7 +371,7 @@ The following include files are part of the LBX Extension library standard. <X11/extensions/lbxzlib.h> .fi .PP -The following include files are part of the Colormap Utilization +The following include files are part of the Colormap Utilization Policy and Extention specification. .PP .nf @@ -442,14 +396,14 @@ Signaling Extension specification. .fi .SH "NON STANDARDS" -The X11R6.4 distribution contains \fIsample\fP implementations, not +The X11R6.7 distribution contains \fIsample\fP implementations, not \fIreference\fP implementations. Although much of the code is believed to be correct, the code should be assumed to be in error wherever it conflicts with the specification. .PP -The only X Consortium standards are the ones listed above. -No other documents, include files, or software in X11R6.4 carry special -status within the X Consortium. For example, none of the following +The only X Window System standards are the ones listed above. +No other documents, include files, or software in X11R6.7 carry special +status within the X Window System. For example, none of the following are standards: internal interfaces of the sample server; the MIT-SHM extension; @@ -458,10 +412,10 @@ the Xmu library; the Xau library; the RGB database; the X Locale database; -the fonts distributed with X11R6.4; -the applications distributed with X11R6.4; +the fonts distributed with X11R6.7; +the applications distributed with X11R6.7; the include files <X11/XWDFile.h>, <X11/Xfuncproto.h>, <X11/Xfuncs.h>, -<X11/Xosdefs.h>, <X11/Xos.h>, <X11/Xos_r.h>, <X11/Xwinsock.h>, and +<X11/Xosdefs.h>, <X11/Xos.h>, <X11/Xos_r.h>, <X11/Xwinsock.h>, and <X11/Xthreads.h>; the bitmap files in <X11/bitmaps>. .PP @@ -469,15 +423,13 @@ The Multi-Buffering extension was a draft standard of the X Consortium but has been superseded by DBE as a standard. .SH "X REGISTRY" -The X Consortium maintained a registry of certain X-related items, to +The X.Org Foundation maintains a registry of certain X-related items, to aid in avoiding conflicts and to aid in sharing of such items. .PP -The registry is published as part of the X Consortium software +The registry is published as part of the X Window System software release. -The latest version may also be available by sending a message to -xstuff@x.org. The message can have a subject line and no body, or a -single-line body and no subject, in either case the line looking like: +The latest version may also be found at .nf - send docs registry + ftp://ftp.x.org/pub/DOCS/registry .fi -The X Registry and the names in it are not X Consortium standards. +The X Registry and the names in it are not X Window System standards. diff --git a/man/general/X.man b/man/general/X.man index ff610b1..96b2004 100644 --- a/man/general/X.man +++ b/man/general/X.man @@ -1,31 +1,39 @@ .\" $Xorg: X.cpp,v 1.3 2000/08/17 19:42:04 cpqbld Exp $ -.\" Copyright (c) 1994 X Consortium +.\" $XdotOrg$ +.\" +.\" Copyright (c) 1994, 2004 The Open Group .\" Copyright \(co 2000 The XFree86 Project, Inc. .\" +.\" All rights reserved. +.\" .\" Permission is hereby granted, free of charge, to any person obtaining a -.\" copy of this software and associated documentation files (the "Software"), -.\" to deal in the Software without restriction, including without limitation -.\" the rights to use, copy, modify, merge, publish, distribute, sublicense, -.\" and/or sell copies of the Software, and to permit persons to whom the -.\" Software furnished to do so, subject to the following conditions: -.\" -.\" The above copyright notice and this permission notice shall be included in -.\" all copies or substantial portions of the Software. -.\" -.\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -.\" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -.\" FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL -.\" THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, -.\" WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF -.\" OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -.\" SOFTWARE. -.\" -.\" Except as contained in this notice, the name of the X Consortium shall not -.\" be used in advertising or otherwise to promote the sale, use or other -.\" dealing in this Software without prior written authorization from the -.\" X Consortium. +.\" copy of this software and associated documentation files (the +.\" "Software"), to deal in the Software without restriction, including +.\" without limitation the rights to use, copy, modify, merge, publish, +.\" distribute, and/or sell copies of the Software, and to permit persons +.\" to whom the Software is furnished to do so, provided that the above +.\" copyright notice(s) and this permission notice appear in all copies of +.\" the Software and that both the above copyright notice(s) and this +.\" permission notice appear in supporting documentation. .\" -.\" $XFree86: xc/doc/man/general/X.man,v 1.8 2002/10/12 16:06:41 herrb Exp $ +.\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS +.\" OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +.\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT +.\" OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR +.\" HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL +.\" INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING +.\" FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, +.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION +.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" Except as contained in this notice, the name of a copyright holder +.\" shall not be used in advertising or otherwise to promote the sale, use +.\" or other dealings in this Software without prior written authorization +.\" of the copyright holder. +.\" +.\" X Window System is a trademark of The Open Group. +.\" +.\" $XFree86: xc/doc/man/general/X.man,v 1.7 2001/10/01 13:43:56 eich Exp $ .\" .TH X __miscmansuffix__ __vendorversion__ .SH NAME @@ -34,11 +42,11 @@ X \- a portable, network-transparent window system .PP The X Window System is a network transparent window system which runs on a wide range of computing and graphics machines. It should be -relatively straightforward to build the X Consortium software +relatively straightforward to build the X.Org Foundation software distribution on most ANSI C and POSIX compliant systems. Commercial implementations are also available for a wide range of platforms. .PP -The X Consortium requests that the following names be used when +The X.Org Foundation requests that the following names be used when referring to this software: .sp .ce 5 @@ -53,7 +61,7 @@ X Window System, Version 11 X11 .PP .I "X Window System" -is a trademark of X Consortium, Inc. +is a trademark of The Open Group. .SH DESCRIPTION X Window System servers run on computers with bitmap displays. The server distributes user input to and accepts output requests from various @@ -74,7 +82,7 @@ the \fIX Toolkit Intrinsics - C Language Interface\fP manual, and various toolkit documents. .PP The number of programs that use \fIX\fP is quite large. -Programs provided in the core X Consortium distribution include: +Programs provided in the core X.Org Foundation distribution include: a terminal emulator, \fIxterm\fP; a window manager, \fItwm\fP; a display manager, \fIxdm\fP; @@ -94,7 +102,6 @@ screen image manipulation utilities, \fIxwd\fP, \fIxwud\fP, and \fIxmag\fP; a performance measurement utility, \fIx11perf\fP; a font compiler, \fIbdftopcf\fP; a font server and related utilities, \fIxfs\fP, \fIfsinfo\fP, \fIfslsfonts\fP, \fIfstobdf\fP; -an X Image Extension exerciser, \fIxieperf\fP; a display server and related utilities, \fIXserver\fP, \fIrgb\fP, \fImkfontdir\fP; remote execution utilities, \fIrstart\fP and \fIxon\fP; a clipboard manager, \fIxclipboard\fP; @@ -110,7 +117,7 @@ an RX MIME-type helper program, \fIxrx\fP; and a utility to cause part or all of the screen to be redrawn, \fIxrefresh\fP. .PP Many other utilities, window managers, games, toolkits, etc. are included -as user-contributed software in the X Consortium distribution, or are +as user-contributed software in the X.Org Foundation distribution, or are available using anonymous ftp on the Internet. See your site administrator for details. .SH "STARTING UP" @@ -364,12 +371,12 @@ to explicitly draw the window's region on the screen with the pointer, for example). .PP Since window managers are regular (albeit complex) client programs, -a variety of different user interfaces can be built. The X Consortium distribution +a variety of different user interfaces can be built. The X.Org Foundation distribution comes with a window manager named \fItwm\fP which supports overlapping windows, popup menus, point-and-click or click-to-type input models, title bars, nice icons (and an icon manager for those who don't like separate icon windows). .PP -See the user-contributed software in the X Consortium distribution for other +See the user-contributed software in the X.Org Foundation distribution for other popular window managers. .SH "FONT NAMES" Collections of characters for displaying text and symbols in X are known as @@ -505,7 +512,7 @@ implementation dependent. If the name is not found, the color is looked up in the X server's database. The text form of this database is commonly stored in the file -\fI__projectroot__/lib/X11/rgb.txt\fP. +\fI\__projectroot__/lib/X11/rgb.txt\fP. .PP A numerical color specification consists of a color space name and a set of values in the following syntax: @@ -1016,12 +1023,12 @@ to enable a particular input method. See .B XLOCALEDIR This must point to a directory containing the locale.alias file and Compose and XLC_LOCALE file hierarchies for all locales. The default value -is \fI__projectroot__/lib/X11/locale\fP. +is\fI __projectroot__/lib/X11/locale\fP. .TP .SM .B XENVIRONMENT This must point to a file containing X resources. The default is -\fI$HOME/.Xdefaults-<hostname>\fP. Unlike \fI__projectroot__/lib/X11/Xresources\fP, +\fI$HOME/.Xdefaults-<hostname>\fP. Unlike\fI __projectroot__/lib/X11/Xresources\fP, it is consulted each time an X application starts. .TP .SM @@ -1094,17 +1101,17 @@ XUSERFILESEARCHPATH is not set. .SM .B XKEYSYMDB This must point to a file containing nonstandard keysym definitions. -The default value is \fI__projectroot__/lib/X11/XKeysymDB\fP. +The default value is\fI __projectroot__/lib/X11/XKeysymDB\fP. .TP .SM .B XCMSDB This must point to a color name database file. The default value is -\fI__projectroot__/lib/X11/Xcms.txt\fP. +\fI\__projectroot__/lib/X11/Xcms.txt\fP. .TP .SM .B XFT_CONFIG This must point to a configuration file for the Xft library. The default -value is \fI__projectroot__/lib/X11/XftConfig\fP. +value is\fI __projectroot__/lib/X11/XftConfig\fP. .TP .SM .B RESOURCE_NAME @@ -1186,7 +1193,7 @@ A wide variety of error messages are generated from various programs. The default error handler in \fIXlib\fP (also used by many toolkits) uses standard resources to construct diagnostic messages when errors occur. The defaults for these messages are usually stored in -\fI__projectroot__/lib/X11/XErrorDB\fP. If this file is not present, +\fI\__projectroot__/lib/X11/XErrorDB\fP. If this file is not present, error messages will be rather terse and cryptic. .PP When the X Toolkit Intrinsics encounter errors converting resource strings to @@ -1255,7 +1262,6 @@ the appropriate instance name can be placed before the asterisk: .BR xfs (1), .BR xfwp (1), .BR xhost (1), -.BR xieperf (1), .BR xinit (1), .BR xkbbell (1), .BR xkbcomp (1), @@ -1291,7 +1297,7 @@ the appropriate instance name can be placed before the asterisk: .BR Xsun (1), .BR Xnest (1), .BR Xvfb (1), -.BR XFree86 (1), +.BR Xorg (1), .BR XDarwin (1), .BR kbd_mode (1), .\" specifications @@ -1300,21 +1306,24 @@ and .I "X Toolkit Intrinsics \- C Language Interface" .SH TRADEMARKS .PP -X Window System is a trademark of X Consortium, Inc. +X Window System is a trademark of The Open Group. .SH AUTHORS .PP -A cast of thousands, literally. The Release 6.3 distribution is -brought to you by X Consortium, Inc. The names of all people who +A cast of thousands, literally. The Release 6.7 distribution is +brought to you by the X.Org Foundation, LLC. The names of all people who made it a reality will be found in the individual documents and -source files. The staff members at the X Consortium responsible -for this release are: Donna Converse (emeritus), Stephen Gildea -(emeritus), Kaleb Keithley, Matt Landau (emeritus), Ralph Mor -(emeritus), Janet O'Halloran, Bob Scheifler, Ralph Swick, Dave -Wiggins (emeritus), and Reed Augliere. +source files. +.PP +Releases 6.6 and 6.5 were done by The X.Org Group. Release 6.4 was done by +The X Project Team. The Release 6.3 distribution was from The X Consortium, +Inc. The staff members at the X Consortium responsible for that release +were: Donna Converse (emeritus), Stephen Gildea (emeritus), Kaleb Keithley, +Matt Landau (emeritus), Ralph Mor (emeritus), Janet O'Halloran, Bob +Scheifler, Ralph Swick, Dave Wiggins (emeritus), and Reed Augliere. .PP The X Window System standard was originally developed at the Laboratory for Computer Science at the Massachusetts Institute of Technology, and all rights thereto were assigned to the X Consortium on January 1, 1994. X Consortium, Inc. closed its doors on December 31, 1996. All rights to the -X Window System have been assigned to the Open Software Foundation. +X Window System have been assigned to The Open Group. diff --git a/man/general/XOrgFoundation.man b/man/general/XOrgFoundation.man new file mode 100644 index 0000000..9c0697c --- /dev/null +++ b/man/general/XOrgFoundation.man @@ -0,0 +1,72 @@ +.\" +.\" Copyright 2004 XOrg Foundation +.\" Copyright (c) 1993, 1994, 1996 X Consortium +.\" +.\" Permission is hereby granted, free of charge, to any person obtaining a +.\" copy of this software and associated documentation files (the "Software"), +.\" to deal in the Software without restriction, including without limitation +.\" the rights to use, copy, modify, merge, publish, distribute, sublicense, +.\" and/or sell copies of the Software, and to permit persons to whom the +.\" Software furnished to do so, subject to the following conditions: +.\" +.\" The above copyright notice and this permission notice shall be included in +.\" all copies or substantial portions of the Software. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +.\" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +.\" FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +.\" THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, +.\" WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF +.\" OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +.\" SOFTWARE. +.\" +.TH XORGFOUNDATION __miscmansuffix__ __xorgversion__ +.SH NAME +XOrg Foundation \- XOrg Foundation information +.SH SYNOPSIS +Release 6.7 of X Version 11 is brought to you by the XOrg Foundation, Inc. +.SH DESCRIPTION +The XOrg Foundation is an independent, not-for-profit 501(c)(3) charity +corporation. It was formed in 2004 as the successor to the XOrg Group at +The Open Group. The purpose of the XOrg Foundation is to foster the +development, evolution, and maintenance of the X Window System, a +comprehensive set of vendor-neutral, system-architecture neutral, +network-transparent windowing and user interface standards. Membership +in the XOrg Foundation is free and open to anyone. The XOrg Foundation +hosts a public CVS repository of the source code on Freedesktop.Org. +.PP +The X Window System was created in the mid-1980s at the Massachusetts +Institute of Technology. In 1988, MIT formed a member-funded consortium to +provide the technical and administrative leadership necessary to support +further development of the X Window System. In 1992, MIT and the membership +decided it was in their best interests to move the consortium out of MIT and +create an independent, stand-alone organization. All rights to the X Window +System were assigned by MIT to X Consortium, Inc. on January 1, 1994. On +December 31, 1996 the X Consortium, Inc. closed its doors and all rights +to the X Window System were assigned to The Open Group (then known as the +Open Software Foundation.) +.PP +.SH INTERIM BOARD +.nf +Stuart Anderson, Free Standards Group +Egbert Eich, SUSE Linux +Mattias Ettrich, KDE +Jim Gettys, Hewlett Packard +Georg Greve, Free Software Foundation Europe +Alan Hourihane +Stuart Kreitman, Sun Microsystems +Kevin Martin, Red Hat Linux +Jim McQuillan, Linux Terminal Server Project +Leon Shiman, Shiman Associates +Jeremy White, Code Weavers +.fi +.SH "ADDRESSES" +The XOrg Foundation's web site is http://www.x.org/ +.PP +The XOrg Foundation's public ftp site is ftp://ftp.x.org/ +.PP +The Open Group's web site is http://www.opengroup.org/ +.PP +Information about the XOrg Foundation CVS repository is on the +Freedesktop.Org web site at http://www.freedesktop.org/Software/xorg/ +.fi diff --git a/man/general/XProjectTeam.man b/man/general/XProjectTeam.man index 0914c53..d7673da 100644 --- a/man/general/XProjectTeam.man +++ b/man/general/XProjectTeam.man @@ -25,9 +25,9 @@ .\" dealing in this Software without prior written authorization from the .\" X Consortium. .\" -.\" $XFree86: xc/doc/man/general/XProjectTeam.man,v 1.3 2001/12/19 21:37:27 dawes Exp $ +.\" $XFree86: xc/doc/man/general/XProjectTeam.man,v 1.2 2001/01/27 18:20:38 dawes Exp $ .\" -.TH X.Org __miscmansuffix__ __xorgversion__ +.TH XORG __miscmansuffix__ __xorgversion__ .SH NAME X.Org, XProjectTeam \- X.Org Group information .SH SYNOPSIS @@ -35,14 +35,13 @@ Release 6.5 and 6.6 of X Version 11 was brought to you by The X.Org Group. Release 6.4 of X Version 11 was brought to you by The X Project Team. .SH DESCRIPTION The Open Group's X Project Team was created as the successor -to the X Consortium, Inc., after the X Consortium was merged into -The Open Group. -The X.Org Group (hereinafter called "X.Org") was created as the successor -to The X Project Team after the The Open Group ceased operating -The X Project Team. -The purpose of X.Org is to foster development, evolution, and -maintenance of the X Window System. X.Org operates under the corporate -umbrella of The Open Group. +to the X Consortium, Inc., after the X Consortium ceased operations and +transferred ownership of X11 to The Open Group. The X.Org Group +(hereinafter called "X.Org") was created as the successor to The X Project +Team after the The Open Group ceased operating The X Project Team. The +purpose of X.Org was to foster development, evolution, and maintenance of +the X Window System. X.Org operates under the corporate umbrella of The +Open Group. .PP The X Consortium was an independent, not-for-profit Delaware membership corporation. It was formed in 1993 as the successor to the MIT X @@ -55,9 +54,9 @@ support further development of the X Window System. In 1992, MIT and the membership decided it was in their best interests to move the consortium out of MIT and create an independent, stand-alone organization. All rights to the X Window System were assigned by MIT to X Consortium, -Inc. on January 1, 1994. X Consortium, Inc. closed its doors on December -31, 1996. All rights to the X Window System have been assigned to The -Open Group, for the benefit of the members of X.Org. +Inc. on January 1, 1994. On December 31, 1996 the X Consortium, Inc. +closed its doors and all rights to the X Window System were assigned to +The Open Group. .PP .SH "ADDRESS" To reach The Open Group public World Wide Web server, use diff --git a/man/general/security.man b/man/general/security.man index a51e386..4219a2f 100644 --- a/man/general/security.man +++ b/man/general/security.man @@ -26,7 +26,7 @@ .\" from the X Consortium. .\" .\" -.\" $XFree86: xc/doc/man/general/security.man,v 1.5 2003/07/09 15:27:25 tsi Exp $ +.\" $XFree86: xc/doc/man/general/security.man,v 1.4tsi Exp $ .\" .nr )S 12 .TH XSECURITY __miscmansuffix__ __xorgversion__ @@ -1,4 +1,5 @@ /* $Xorg: registry,v 1.7 2001/06/01 18:55:58 coskrey Exp $ */ +/* $XdotOrg$ */ X Registry @@ -11,8 +12,8 @@ or to The X.Org Group -- X11 Registry c/o Ienup Sung Sun Microsystems, Inc. - 901 San Antonio Road, MS SJC07-201 - Palo Alto, CA 94303-4900 + 4150 Network Circle, MS SJC07-201 + Santa Clara, CA 95054 Electronic mail will be acknowledged upon receipt. Please allow up to 4 weeks for a formal response to registration and inquiries. @@ -448,6 +449,7 @@ Value Name Reference 0 Internet [23] 1 DECnet [23] 2 Chaos [23] +5 ServerInterpreted [23] 6 InternetV6 [23] 33 Amoeba [8] 252 LocalHost [105] @@ -1026,6 +1028,21 @@ See XIM_ENCODING_NEGOTIATION in section 4.6 of the XIM standard. "COMPOUND_TEXT" [104] +23. SERVER INTERPRETED ADDRESS TYPES + +Types of addresses used in the ChangeHosts protocol request. +See the description of ChangeHosts in section 9 of the X11 Protocol standard. + +Registered address types: + +Name Reference +---- --------- +"hostname" [135 - xc/doc/spec/SIAddresses/hostname.txt] +"IPv6" [135 - xc/doc/spec/SIAddresses/IPv6.txt] + +Vendor-specific prefixes: + +None registered yet. REFERENCES @@ -1087,8 +1104,8 @@ REFERENCES X.Org Chair: Steve Swales Sun Microsystems, Inc. - 901 San Antonio Road, MS SJC07-201 - Palo Alto, CA 94303-4900 + 4150 Network Circle, MS SJC07-201 + Santa Clara, CA 95054 steve.swales@sun.com X.Org Co-Chair: @@ -1326,8 +1343,8 @@ REFERENCES [57] (Originally David Rosenthal) Steve Swales Sun Microsystems, Inc. - 901 San Antonio Road, MS SJC07-201 - Palo Alto, CA 94303-4900 + 4150 Network Circle, MS SJC07-201 + Santa Clara, CA 95054 steve.swales@sun.com [58] (Originally Murali V. Srinivasan) @@ -1415,11 +1432,8 @@ REFERENCES P.O. Box 58700 Salt Lake City, UT 84158 -[76] Cheryl Huntington - MS. MTV21-04 - Sun Microsystems - 2550 Garcia Ave. - Mountain View, CA. 94043-1100 +[76] (Originally Cheryl Huntington) + See Reference [57] [77] Junichi Hiramoto Manager, Engineering Department @@ -1680,12 +1694,16 @@ REFERENCES Markus G. Kuhn University of Cambridge Computer Laboratory - New Museums Site, Pembroke Street - Cambridge CB2 3QG + 15 JJ Thomson Avenue + Cambridge CB3 0FD United Kingdom [134] In R6.6 X.Org is reserving the string UTF8_STRING for use as an ICCCM property type and selection target. The ICCCM spec will be updated in a future release to fully specify UTF8_STRING. +[135] X.Org Foundation source implementation + See Reference [8] + /* $XFree86: xc/registry,v 1.8 2003/07/09 15:27:23 tsi Exp $ */ + diff --git a/sgml/Darwin.sgml b/sgml/Darwin.sgml index c64cfe0..8017c6a 100644 --- a/sgml/Darwin.sgml +++ b/sgml/Darwin.sgml @@ -1,40 +1,41 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN" [ +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN" [ <!ENTITY % defs SYSTEM "defs.ent"> %defs; ]> <article> -<title>XFree86 on Darwin and Mac OS X +<title>X.org X on Darwin and Mac OS X <author>Torrey T. Lyons <date>15 December 2003 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml,v 1.10 2003/12/15 20:47:41 torrey Exp $ +$XdotOrg$ </ident> <toc> <sect>Introduction <p> -<htmlurl url="http://www.xfree86.org/" name="XFree86">, a freely -redistributable open-source implementation of the <htmlurl -url="http://www.x.org/" name="X Window System">, has been ported to <htmlurl +<htmlurl url="http://www.freedesktop.org/Software/xorg" name="Xorg">, a freely +redistributable open-source implementation of the +<htmlurl url="http://www.x.org/" name="X Window System">, +has been ported to <htmlurl url="http://www.opensource.apple.com/projects/darwin/" name="Darwin"> and <htmlurl url="http://www.apple.com/macosx/" name="Mac OS X">. This document is a collection of information for anyone -running XFree86 on Apple's next generation operating system. +running Xorg's X server on Apple's next generation operating system. <p> -Most of the current work on XFree86 for Darwin and Mac OS X is centered +Most of the current work on X for Darwin and Mac OS X is centered around the <htmlurl url="http://sourceforge.net/projects/xonx/" name="XonX project"> at <htmlurl url="http://sourceforge.net" name="SourceForge">. If you are interested in up-to-date status, want to -report a bug, or are interested in working on XFree86 for Darwin, stop by the +report a bug, or are interested in working on Xorg for Darwin, stop by the <htmlurl url="http://sourceforge.net/projects/xonx/" name="XonX project">. <sect>Hardware Support and Configuration <p> The X window server for Darwin and Mac OS X provided by the <htmlurl -url="http://www.XFree86.Org/" name="XFree86 Project, Inc."> is called +url="http://www.X.Org/" name="X.Org Foundation."> is called XDarwin. XDarwin can run in three different modes. On Mac OS X, XDarwin runs in parallel with Aqua in full screen or rootless modes. These modes are called Quartz modes, named after the Quartz 2D compositing @@ -56,18 +57,18 @@ all the other windows. The X11 root window is not displayed in rootless mode as Aqua handles the desktop background. <p> -From the console, the Darwin port of XFree86 uses the IOKit for device -driver loading and discovery, rather than the XFree86 module loader. -Because of this, the XFree86 configuration file is not used on Darwin +From the console, the Darwin port of X11R&relvers; uses the IOKit for device +driver loading and discovery, rather than the X11R&relvers; module loader. +Because of this, the X11R&relvers; configuration file is not used on Darwin or Mac OS X systems. The descriptions found elsewhere of devices -supported by XFree86 for other operating systems also do not apply. +supported by X11R&relvers; for other operating systems also do not apply. <p> -XFree86 for Darwin or Mac OS X will work with any video card that +X11R&relvers; for Darwin or Mac OS X will work with any video card that you have an IOKit driver for. If you are running Mac OS X, this typically means any card that has been shipped by Apple. If a card works for you with the Mac OS X GUI, it will work on the same machine with -XFree86. If you have a pure Darwin installation, you may need to download +X11R&relvers;. If you have a pure Darwin installation, you may need to download additional third-party drivers from <htmlurl url="http://developer.apple.com/darwin/" name="Apple's Darwin site">. IOKit drivers are typically installed in @@ -82,23 +83,11 @@ will work on an ADB mouse. <sect>Getting Started <p> Following are instructions for building and running your own copy of -XFree86. The procedure for getting your X server up and running on +X11R&relvers;. The procedure for getting your X server up and running on Darwin and Mac OS X are very similar. Where there are differences -I have noted them below. Note that to build XFree86 for yourself on +I have noted them below. Note that to build X11R&relvers; for yourself on Mac OS X, you need to install the Developers' Tools. -<p> -If you don't feel the need to live on the cutting edge, you can save -some time and effort by using the precompiled binaries available on -the XFree86 FTP server at <url -url="ftp://ftp.xfree86.org/pub/XFree86/&relvers;/binaries/">. -Follow the instructions in the <htmlurl -url="http://www.xfree86.org/&relvers;/Install.html" name="Install"> -document to install it. This will create three new directory trees, -<tt>/usr/X11R6</tt>, <tt>/etc/X11</tt> and <tt>/etc/fonts</tt>. On -Mac OS X the Xquartz.tgz tarball is required in addition to the -other tarballs required on other platforms. With Mac OS X Quartz -support, the XDarwin application will be installed in <tt>/Applications</tt>. <p> @@ -111,14 +100,14 @@ below. <p> The first thing you need to do is to get the source code from the -XFree86 project. +X.Org Foundation project. <itemize> <item> Setup CVS: Both Darwin and Mac OS X include CVS (Concurrent Versions System), which is an easy way to download and keep up to date -with open source code released by XFree86 and others. You do have to +with open source code released by the X.Org Foundation and others. You do have to setup CVS properly, however, to tell it where to look. Follow the -<htmlurl url="http://www.xfree86.org/cvs/" name="XFree86 instructions"> on +<htmlurl url="http://x.org/" name="X.Org CVS instructions"> on how to do this either via ssh or via the cvs pserver. <item> Now make a directory in some convenient place which will serve @@ -135,10 +124,10 @@ Wait for all the files to complete downloading. </itemize> -<sect1> Build XFree86 +<sect1> Build X11R&relvers; <p> Once you have everything ready it is easy to build and install -XFree86. From the command line: +X11R&relvers;. From the command line: <tscreen><verb> cd sandbox/xc @@ -173,14 +162,14 @@ shell you are using. This is described in the man page documentation for the shell. <p> -In addition you may also want to add the man pages from XFree86 to the list +In addition you may also want to add the man pages from X11R&relvers; to the list of pages to be searched when you are looking for documentation. The X11 man pages are located in <tt>/usr/X11R6/man</tt> and the <tt>MANPATH</tt> environment variable contains the list of directories to search. <sect1>Starting the X Server <p> -On Mac OS X, you can run XFree86 from the Darwin +On Mac OS X, you can run X11R&relvers; from the Darwin text console or in parallel with Aqua. To get to the text console in Mac OS X you need to logout and type ``>console'' as the user name. This will shutdown Core Graphics and @@ -189,7 +178,7 @@ From the text console you can start the X Window System by typing ``exec startx''. <p> -When you are ready to quit XFree86 type ``exit'' in the main +When you are ready to quit X11R&relvers; type ``exit'' in the main terminal window or quit with the window manager if you have one running. Unfortunately in IOKit mode, the X server does not shutdown correctly and if you did not start with ``exec startx'', you @@ -202,7 +191,7 @@ Mac OS X, Core Graphics will restart and you should be given a login window. <p> -To start XFree86 in Quartz mode you can launch the XDarwin application +To start X11R&relvers; in Quartz mode you can launch the XDarwin application in the <tt>/Applications</tt> folder, or from the command line type ``startx -- -quartz''. By default this will give you a mode picker to choose between full screen or rootless mode. You can change the default @@ -237,7 +226,7 @@ The X Window System is very customizable and you will certainly want to change some things. There is a lot you can do to control how your windows look, how the windows are moved, resized, etc. You will likely want to get a fancier window manager than twm, which is included with -XFree86. The <tt>.xinitrc</tt> file in your home directory controls what +X11R&relvers;. The <tt>.xinitrc</tt> file in your home directory controls what programs are run when you start the X Window System. You can find a sample <tt>.xinitrc</tt> file in <tt>/etc/X11/xinit/xinitrc</tt>. diff --git a/sgml/Install.sgml b/sgml/Install.sgml index 69bcc4c..8dd9861 100644 --- a/sgml/Install.sgml +++ b/sgml/Install.sgml @@ -1,20 +1,21 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN" [ +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN" [ <!ENTITY % defs SYSTEM "defs.ent"> %defs; ]> <article> -<title>Installation Details for XFree86™ &relvers; -<author>The XFree86 Project, Inc +<title>Installation Details for X11R&relvers; +<author>The X.org Foundation <date>23 February 2004 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Install.sgml,v 1.18 2004/02/24 03:41:39 dawes Exp $ +$Id$ </ident> <abstract> -How to install XFree86. +How to install the X.Org Foundation's X Window System release version +X11R&relvers;. </abstract> @@ -22,502 +23,20 @@ How to install XFree86. <sect>Introduction <p> -This document contains information about installing the XFree86 binaries -provided by The XFree86 Project. - -<p> -The XFree86 binaries that we provide for UNIX-like OS's (Linux, the -BSDs, Solaris, etc) are packaged in a platform-independent gzipped tar -format (aka "tarballs" identified by the <tt>.tgz</tt> suffix). Along -with the binaries we provide a customized version of the GNU tar utility -called "extract" and an installation script. We recommend that these -be used to install the binaries. (The source for this customized version -of GNU tar can be found in the XFree86 CVS repository's "utils" module, -and from our <url name="ftp site" -url="ftp://ftp.xfree86.org/pub/XFree86/misc/utils-&utilsvers;.tgz">.) - -<![ %snapshot [ -<p> -Note: for snapshot releases like this one, binaries are only available for -a small number of platforms. -]]> - - -<sect>Downloading the XFree86 &relvers; binaries -<p> - -<![ %updaterel [ -XFree86 &relvers; is an update release. The most recent full release -(&fullrelvers;) needs to be installed before installing this update. -Information about downloading and installing &fullrelvers; can be found -in the installation document for that version, which can be found -on the <url name="XFree86 web site" -url="http://www.xfree86.org/&fullrelvers/Install.html">. -]]> - -We provide XFree86 &relvers; <![ %updaterel [update ]]>binaries for a range -of operating systems at our -<![ %snapshot; [ -<url name="ftp site" -url="ftp://ftp.xfree86.org/pub/XFree86/snapshots/&relvers/binaries/"> -]]> -<![ %release; [ -<url name="ftp site" -url="ftp://ftp.xfree86.org/pub/XFree86/&relvers/binaries/"> -]]> -and our -<![ %snapshot; [ -<url name="web site" -url="http://ftp.xfree86.org/pub/XFree86/snapshots/&relvers/binaries/">. -]]> -<![ %release; [ -<url name="web site" -url="http://ftp.xfree86.org/pub/XFree86/&relvers/binaries/">. -]]> -Often during releases our site is heavily loaded. Instead of downloading -directly from us we recommend that instead you use one of our mirror -sites. - -<p> -Our binaries are organized by sub-directories which correspond to each -of the OS/platforms for which we provide binaries. First go to the -sub-directory that represents your OS platform. In some cases (e.g., -Linux) there may be a number of choices depending on the architecture -or libc version your platform uses. In all case we recommend that you -first download the <tt>Xinstall.sh</tt> script, and run it as in the -following example to find out which binary distribution you should -download. - -<tscreen><verb> -sh Xinstall.sh -check -</verb></tscreen> - -The output of this utility tells you which is the correct set of binaries -for you to download. If you are careful with this step you will save -yourself a lot time and trouble from NOT downloading an incompatible -distribution. - -<bf>NOTES</bf>: - -<itemize> - <item>The Xinstall.sh script must be downloaded in binary mode, - otherwise it will not run correctly. If you get lots of "command - not found" messages when you try to run it, then it is most - likely because the script was not downloaded in binary mode. - Some web browsers will not do this for files of that name, so we - also have a copy of it called "<tt>Xinstall.bin</tt>", and most - browsers should download that correctly. When downloading it - under this name, select "save as" on your browser, and save the - file under the name "<tt>Xinstall.sh</tt>". - - <item>The Xinstall.sh script requires some system commands and - utilities to function correctly. While most systems will have - these, some Linux installations may not. If the - script fails because of some missing system command, you - need to install it before you can continue. If you do not - know how to do this, then we recommend that you obtain this - version of XFree86 from your Operating System distributor. - - <item>Always use the version of the Xinstall.sh script that is provided - with the release. Older versions of the script - may not install newer releases correctly. - - <item>If the binary distribution reported by the Xinstall.sh script - is not present on the XFree86 site, then there are two possibilities: - first is that it has not uploaded yet. This is likeliest - possibility if you are looking shortly after the release date. - The second possibility is that your target will not be be - available at for this release. This is likeliest possibility - if you are looking about two weeks after the release date. - Check <url name="here" - url="http://www.xfree86.org/&relvers;/UPDATES.html"> for - information about updates to our binary distributions, and <url - name="here" url="http://www.xfree86.org/&relvers;/ERRATA.html"> - for errata related to this release. - -</itemize> - -Assuming that you have run the <tt>Xinstall.sh</tt> script and found the binary -<![ %updaterel; [update ]]>distribution suitable for your system, -download the necessary files. The <![ %fullbinaries [twelve (12)]]><![ -%updaterel [four (4)]]> mandatory files for all installations are listed -below. The installer script will complain if you do not have all four (4) -files in the same directory. - -<![ %fullbinaries [ -<quote><verb> -1. Xinstall.sh The installer script -2. extract The utility for extracting tarballs -3. Xbin.tgz X clients/utilities and run-time libraries -4. Xlib.tgz Some data files required at run-time -5. Xman.tgz Manual pages -6. Xdoc.tgz XFree86 documentation -7. Xfnts.tgz Base set of fonts -8. Xfenc.tgz Base set of font encoding data -9. Xetc.tgz Run-time configuration files -10. Xvar.tgz Run-time data -11. Xxserv.tgz XFree86 X server -12. Xmod.tgz XFree86 X server modules -</verb></quote> -]]> - -<![ %updaterel [ -<quote><verb> -1. Xinstall.sh The installer script -2. extract The utility for extracting tarballs -3. Xupdate.tgz Updated files except X server drivers -4. Xdrivers.tgz Updated X server drivers -</verb></quote> -]]> - -NOTES: -<itemize> - <item>Some web browsers have a problem downloading the <tt>extract</tt> - utility correctly. If you encounter this problem, download the - version called <tt>extract.exe</tt>. (NOTE: This is not a - MS-DOS/Windows executable.) - -<![ %fullbinaries [ - <item>Some distributions do not require the <tt>Xvar.tgz</tt> - tarball. If it is present in the <tt>binaries</tt> sub-directory - for your platform, then it is required. -]]> - - <item>The Darwin/Mac OS X distribution do not have or require the - <![ %fullbinaries [<tt>Xmod.tgz</tt>]]><![ %updaterel - [<tt>Xdrivers.tgz</tt>]]> tarball. - - <item>Some distributions may have additional mandatory tarballs. - While rare, the installer script will tell you if any are missing. - -</itemize> - -<![ %fullbinaries [ -The following eleven (11) tarballs are optional. You should download -the ones you want to install. - -<quote><verb> -1. Xdrm.tgz Source for DRM kernel modules -2. Xfsrv.tgz Font server -3. Xnest.tgz Nested X server -4. Xprog.tgz X header files, config files and compile-time libs -5. Xprt.tgz X Print server -6. Xvfb.tgz Virtual framebuffer X server -7. Xf100.tgz 100dpi fonts -8. Xfcyr.tgz Cyrillic fonts -9. Xfscl.tgz Scalable fonts (Speedo, Type1 and TrueType) -10. Xhtml.tgz HTML version of the documentation -11. Xps.tgz PostScript version of the documentation -12. Xpdf.tgz PDF version of the documentation -13. Xjdoc.tgz Documentation in Japanese -</verb></quote> - -NOTES: -<itemize> - <item>Some distributions may have some additional optional tarballs. - -</itemize> - -If you miss some and want to install them later, go to the -<ref id="manual-install" name="Manual Installation"> section. -]]> - -<sect>Installing XFree86 &relvers; using the <tt>Xinstall.sh</tt> script -<p> -We strongly recommend that our XFree86 &relvers; binaries be installed -using the <tt>Xinstall.sh</tt> script we provide. -<![ %updaterel [It is also important that the previous full release -(&fullrelvers;) is installed before installing this update release. -Make sure that you use the &relvers; version of the <tt>Xinstall.sh</tt> -script to install this update. Older versions may not be able to do it -correctly.]]> -There are a lot of -steps in the manual installation process, and those steps can vary -according to the platform and hardware setup. <![ %fullbinaries [There is a description of -the manual installation process for the most common cases <ref -id="manual-install" name="below">.]]> - -You must login as the super user (root) to run the installer script and -place all of the downloaded files into a single directory. -Use the cd command to change to the chosen directory and -run the installer script as follows: - -<tscreen><verb> -sh Xinstall.sh -</verb></tscreen> - -Answer the prompts as they come up. If you are missing something that -is required, the installer may tell you to install it before trying -again. If the problem is that you did not download all of mandatory -files aforementioned, then the installer will tell you which ones are -missing and ask you to download them before proceeding. - -<sect1>Questions the installer may ask -<p> -The installer asks some questions that may not have obvious answers. The -information here should help you answer them. In most cases, apart from -the first question, the default answers should be OK. - -If you run the installer from within an X session (the installer checks -if <tt>$DISPLAY</tt> is set), you will be warned that doing so is not -a good idea. Unless you have a good reason for knowing that this will not -be a problem, you should exit your X session, including stopping xdm or -equivalent if it is running, before continuing. If you ignore this -warning and run into problems, well, you were warned! - -<![ %fullbinaries [If you have an existing X installation, you]]> -<![ %updaterel [You ]]> -will be warned that proceeding -with this installation will overwrite it. Only those things that are -part of our standard distribution will be overwritten. Other X -applications that you may have installed will not be removed. Some -configuration files may be overwritten though, but the installer should -prompt you before doing so. As the opening greeting says, it is -<bf>strongly</bf> recommended that you backup any existing installation -before proceeding. If you want your old applications to still be there -after you've installed, do not do the "backup" by simply renaming -your old <tt>/usr/X11R6</tt> directory. It is better to make a copy of -it, and then install over the top of the original one. If you run into -problems and want to revert to the old installation, you can then -delete the overwritten one and copy the saved version back. - -During the first part of the installation over an existing version, the -script may remove some old files or directories that would get in the -way of the new installation. It will list which files/directories have -been removed. If none are listed, then none were removed. - -<![ %fullbinaries [ -The next step when installing over an existing version is to check for -existing configuration files. As of XFree86 version 3.9.18, the run-time -configuration files are installed by default under <tt>/etc/X11</tt> -instead of under <tt>/usr/X11R6/lib/X11</tt>. The installer will move -the existing ones for you and create the necessary symbolic links. If -you do not want to have these configuration files under <tt>/etc/X11</tt>, -then you should answer "no" when asked about it. Answering "no" here -also means that the new configuration files will be installed in the -old <tt>/usr/X11R6/lib/X11</tt> location. - -Note: for the rare systems that do not have symbolic links, this question -will not be asked. The default answer is "yes" because that is best -for most situations. It is our new default. It makes it easier to -share the <tt>/usr/X11R6</tt> directory between multiple hosts, and -allows it to be mounted read-only. If you do not need these features, -then you can safely answer "no" if you do not want them moved. - -When installing over an existing version, you will be prompted before -each set of configuration files is installed. If you haven't made any -Customisations to your existing configuration files, then you can safely -answer "yes" for each of these. If you have made customisations, you -can try answering "no". If you run into problems later, you may need -to manually merge your customisations into the the new version of the -configuration files. The configuration files can all be found in the -<tt>Xetc.tgz</tt> tarball. See the <ref id="manual-install" name="section -below"> about manual installation for information about extracting them -separately. - -After the configuration files have been dealt with, the other mandatory -components of the binary distribution will be installed. This should -proceed without any user intervention. - -If you downloaded any of the optional components, the installer will -ask you about each one before it is installed. The default answer is -"yes". If there are any that you've since decided that you do not want -to install, answer "no" when prompted. - -After that is done, the main part of the installation is complete. The -next steps are to tidy up some aspects of the installation. The first -of these is to run "<tt>ldconfig</tt>" on systems that require it, so -that the newly installed shared libraries are accessible. Then -the <tt>fonts.dir</tt> files in some directories are updated so that -the fonts can be accessed correctly. Next, the installer checks to -see if your system has a termcap file or terminfo files. If it finds -the former, it tells you how you may update the entries in that file. -If it finds the latter, it asks you if you want it to update them -for you. - -You may be asked if you want to create links for the GL libraries and -header files. The OpenGL standard on some platforms (Linux in particular) -says that these should be installed in the standard system locations -(<tt>/usr/lib</tt> and <tt>/usr/include</tt>), so the installer offers -to create the appropriate links. If you're running Linux, you should -probably answer yes. For other platforms it is your choice. If you -already have another version of libGL in /usr/lib, answering "yes" will -remove it and replace it with a link to the version we supply. The -installer will show you a listing of any existing versions before asking -if they should be replaced. - -Finally, the installer asks you if you want a link created for the -<tt>rstart</tt> utility. On most modern systems the link isn't essential, -so the default answer is "no". Answer "yes" if you know that you need -it. If you find later that you need it, you can create it easily by -running: - -<tscreen><verb> -rm -f /usr/bin/rstartd -ln -s /usr/X11R6/bin/rstartd /usr/bin/rstartd -</verb></tscreen> - -]]> - -<sect1>After the installation is complete -<p> -The next step is to configure the X server. That is covered in detail -in an as-yet unwritten document :-(. In the meantime, there are three -ways to create a basic X server configuration file for XFree86 &relvers;. -One is to run the <tt>xf86config</tt> utility. Another is to run the -<tt>xf86cfg</tt> utility. The third option is to use the new -<tt>-configure</tt> X server option: - -<tscreen><verb> -XFree86 -configure -</verb></tscreen> - -Note that if you are running Darwin/Mac OS X, there is no step 3 :-). -You should skip this step, as configuration is not required or possible. -The X server configuration file is not used on Darwin/Mac OS X. - -The X server config file (<tt>XF86Config</tt>) format has changed -compared to 3.3.x. Also, its default location is now <tt>/etc/X11</tt>. -Finally, there is now only one X server for driving video hardware, -and it is called "<tt>XFree86</tt>". Once you're satisfied with the -operation of the new X server, you can safely remove the old -<tt>XF86_*</tt> and/or <tt>XF98_*</tt> X server binaries from -<tt>/usr/X11R6/bin</tt>. - -After the X server configuration is done, it may be advisable to reboot, -especially if you run xdm (or equivalent) or the font server (xfs). - -<![ %fullbinaries [ -<sect>Installing XFree86 &relvers; manually<label id="manual-install"> -<p> -This section contains information about manually installing the XFree86 -&relvers; binary distributions. You should only use this method if you -know what you're doing. The information here covers some common cases, -but not every possible case. It also may not be complete or up to date. -Use at your own risk. - -Put all of the downloaded files into a single directory (choose some -temporary location with enough space). Become the super user (root). -All of the following commands should be run as root, and they should be -run from the directory that has all of the downloaded files. The -"<tt>extract</tt>" utility should be used to unpack the tarballs. This -is a customised version of GNU tar that has the gzip code built-in, and -which has a different usage when run under the name "extract". One -important thing that <tt>extract</tt> does that most versions of tar do -not do by default is that it unlinks existing files before writing new -ones. This is important when installing over an existing version of X. -If you choose to use some other utility to extract the tarballs, you're -on your own. - -<sect1>A new installation -<p> -The simplest case is when there is no existing X installation. The -installation procedure for this case is as follows: - -<tscreen><verb> -chmod +x extract -mkdir /usr/X11R6 -mkdir /etc/X11 -./extract -C /usr/X11R6 X[a-df-uw-z]*.tgz -./extract -C /usr/X11R6 Xvfb.tgz # If you are installing Xvfb -./extract -C /etc/X11 Xetc.tgz -./extract -C /var Xvar.tgz -ln -s /etc/X11/app-defaults /usr/X11R6/lib/X11 -ln -s /etc/X11/fs /usr/X11R6/lib/X11 -ln -s /etc/X11/lbxproxy /usr/X11R6/lib/X11 -ln -s /etc/X11/proxymngr /usr/X11R6/lib/X11 -ln -s /etc/X11/rstart /usr/X11R6/lib/X11 -ln -s /etc/X11/twm /usr/X11R6/lib/X11 -ln -s /etc/X11/xdm /usr/X11R6/lib/X11 -ln -s /etc/X11/xinit /usr/X11R6/lib/X11 -ln -s /etc/X11/xsm /usr/X11R6/lib/X11 -ln -s /etc/X11/xserver /usr/X11R6/lib/X11 -chmod ug-w /usr/X11R6/lib # Make sure the permissions are OK -/sbin/ldconfig /usr/X11R6/lib # For Linux -/sbin/ldconfig -m /usr/X11R6/lib # For FreeBSD, NetBSD, OpenBSD -/usr/X11R6/bin/mkfontdir /usr/X11R6/lib/X11/fonts/misc -</verb></tscreen> - -<sect1>Installing over an old installation -<p> -If you have an existing installation of X, you should make a backup copy -of it before installing the new version over the top of it. - -Before doing anything else, make sure the <tt>extract</tt> command is -executable, and also link it to the name "<tt>gnu-tar</tt>" so that it -can be used as a regular <tt>tar</tt> command: - -<tscreen><verb> -chmod +x extract -rm -f gnu-tar -ln extract gnu-tar -</verb></tscreen> - -The first part of the procedure is to move the old run-time config files -from <tt>/usr/X11R6/lib/X11</tt> to <tt>/etc/X11</tt>. Create -<tt>/etc/X11</tt> if it doesn't already exist. For each of the following -sub-directories (<tt>app-defaults</tt>, <tt>fs</tt>, <tt>lbxproxy</tt>, -<tt>proxymngr</tt>, <tt>rstart</tt>, <tt>twm</tt>, <tt>xdm</tt>, -<tt>xinit</tt>, <tt>xsm</tt>, <tt>xserver</tt>) that you want to move, -check that there is a sub-directory of this name in -<tt>/usr/X11R6/lib/X11</tt>. Create a sub-directory of the same name -under <tt>/etc/X11</tt>, then copy the files over by running: - -<tscreen><verb> -./gnu-tar -C /usr/X11R6/lib/X11/subdir -c -f - . | \ - ./gnu-tar -C /etc/X11/subdir -v -x -p -U -f - -</verb></tscreen> - -For each subdirectory that is moved, remove the one under -<tt>/usr/X11R6/lib/X11</tt> and create a symbolic link to the new -location: - -<tscreen><verb> -rm -fr /usr/X11R6/lib/X11/subdir -ln -s /etc/X11/subdir /usr/X11R6/lib/X11 -</verb></tscreen> - -For those subdirectories that didn't already exist under -<tt>/usr/X11R6/lib/X11</tt>, create one under <tt>/etc/X11</tt> and -create the symbolic link to it: - -<tscreen><verb> -mkdir /etc/X11/subdir -ln -s /etc/X11/subdir /usr/X11R6/lib/X11 -</verb></tscreen> - -Once that is done, extract the config files from the <tt>Xetc.tgz</tt> -tarball into a temporary directory: - -<tscreen><verb> -mkdir tmpdir -./extract -C tmpdir Xetc.tgz -</verb></tscreen> - -and then copy each sub-directory over to the installed location: - -<tscreen><verb> -./gnu-tar -C tmpdir/subdir -c -f - . | \ - ./gnu-tar -C /usr/X11R6/lib/X11/subdir -v -x -p -U -f - -</verb></tscreen> - -If you have customised any config files in your old installation, you -may want to omit those sub-directories, or copy selected files over by -hand. - -Once that's done, the main part of the installation can be done: - -<tscreen><verb> -./extract -C /usr/X11R6 `pwd`/X[a-df-uw-z]*.tgz -./extract -C /usr/X11R6 Xvfb.tgz # If you are installing Xvfb -./extract -C /var Xvar.tgz -chmod ug-w /usr/X11R6/lib # Make sure the permissions are OK -/sbin/ldconfig /usr/X11R6/lib # For Linux -/sbin/ldconfig -m /usr/X11R6/lib # For FreeBSD, NetBSD, OpenBSD -/usr/X11R6/bin/mkfontdir /usr/X11R6/lib/X11/fonts/misc -</verb></tscreen> - -]]> - +At this time, the X.org Foundation is not making binary releases; this +will likely change in the not-distant future as our tinderbox system +reaches its full potential. +<p> +However, people are already packaging the distribution +for release in many of the common distributions (e.g. RedHat Fedora, +SuSE Linux, Debian), and you may wish to work with those distributors +on their packaged binaries. +<p> +In the meanwhile, we recommend building X from source and doing +install on top of your running X installation *after* having carefully +backed up /usr/X11R6 to allow restoration in case of some unanticipated +problems. +See the file INSTALL.TXT in the root of the source distribution for +build and install details. </article> diff --git a/sgml/LICENSE.sgml b/sgml/LICENSE.sgml index c074d34..b44491d 100644 --- a/sgml/LICENSE.sgml +++ b/sgml/LICENSE.sgml @@ -1,16 +1,27 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN"[ +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN"[ <!ENTITY % defs SYSTEM "defs.ent"> %defs; ]> <article> <title>Licenses</title> -<author>The XFree86 Project</author> -<date>February 2003</date> +<author>The X.Org Foundation</author> +<date>March 2004</date> <ident> -$XFree86$ +$Id$ </ident> +<sect>Introduction +<p> + +The X.org Foundation X Window System distribution is a compilation of code and +documentation from many sources. This document is intended primarily +as a guide to the licenses used in the distribution: you must check +each file and/or package for precise redistribution +terms. None-the-less, this summary may be useful to many users. +No software incorporating the XFree86 1.1 license has been incorporated. + +This document is based on the compilation from XFree86. <sect>XFree86 License <p> XFree86 code without an explicit copyright is covered by the following @@ -105,7 +116,7 @@ in this Software without prior written authorization from The Open Group. <sect1>Berkeley-based copyrights: <p> -<sect2>General +o<sect2>General <p> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions @@ -753,6 +764,61 @@ Copyright (c) 1994-1999 Silicon Graphics, Inc. All Rights Reserved. solely in object code form, Recipient may replace the words "this file" with "this software" in both the first and second sentences.] +<sect1>Bitstream Vera Fonts Copyright +<p> +The fonts have a generous copyright, allowing derivative works (as +long as "Bitstream" or "Vera" are not in the names), and full +redistribution (so long as they are not *sold* by themselves). They +can be be bundled, redistributed and sold with any software. + +The fonts are distributed under the following copyright: +<p> +Copyright (c) 2003 by Bitstream, Inc. All Rights Reserved. Bitstream +Vera is a trademark of Bitstream, Inc. + +Permission is hereby granted, free of charge, to any person obtaining +a copy of the fonts accompanying this license ("Fonts") and associated +documentation files (the "Font Software"), to reproduce and distribute +the Font Software, including without limitation the rights to use, +copy, merge, publish, distribute, and/or sell copies of the Font +Software, and to permit persons to whom the Font Software is furnished +to do so, subject to the following conditions: + +The above copyright and trademark notices and this permission notice +shall be included in all copies of one or more of the Font Software +typefaces. + +The Font Software may be modified, altered, or added to, and in +particular the designs of glyphs or characters in the Fonts may be +modified and additional glyphs or characters may be added to the +Fonts, only if the fonts are renamed to names not containing either +the words "Bitstream" or the word "Vera". + +This License becomes null and void to the extent applicable to Fonts +or Font Software that has been modified and is distributed under the +"Bitstream Vera" names. + +The Font Software may be sold as part of a larger software package but +no copy of one or more of the Font Software typefaces may be sold by +itself. + +THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT +OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL +BITSTREAM OR THE GNOME FOUNDATION BE LIABLE FOR ANY CLAIM, DAMAGES OR +OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, +OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR +OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT +SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE. + +Except as contained in this notice, the names of Gnome, the Gnome +Foundation, and Bitstream Inc., shall not be used in advertising or +otherwise to promote the sale, use or other dealings in this Font +Software without prior written authorization from the Gnome Foundation +or Bitstream Inc., respectively. For further information, contact: +fonts at gnome dot org. + <sect1>Bigelow & Holmes Inc and URW++ GmbH Luxi font license <p> diff --git a/sgml/LynxOS.sgml b/sgml/LynxOS.sgml index 94684b5..1e61e3e 100644 --- a/sgml/LynxOS.sgml +++ b/sgml/LynxOS.sgml @@ -3,97 +3,72 @@ ]> <article> -<title>README for XFree86 &relvers; on LynxOS +<title>README for X11R&relvers; on LynxOS <author>Thomas Mueller <date>25 February 2000 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/LynxOS.sgml,v 3.20 2000/06/17 00:27:32 dawes Exp $ </ident> <toc> -<sect>What and Where is XFree86? +<sect>What and Where is X11R&relvers;? <p> -XFree86 is a port of X11R6.4 that supports several versions of -Intel-based Unix. It is derived from X386 1.2, which was the X server +X11R&relvers; is a port of X11R6.4 that supports several versions of +Intel-based Unix. It is derived from XFree86 4.4 rc2 which was +derived from X386 1.2, which was the X server distributed with X11R5. This release consists of many new features and performance improvements as well as many bug fixes. See the <htmlurl url="COPYRIGHT.html" name="Copyright Notice">. -The sources for XFree86 &relvers; are available by anonymous ftp from: - -<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/&relvers;" -url="ftp://ftp.XFree86.org/pub/XFree86/&relvers;"> - -Binaries of XFree86 for LynxOS x86 are available from: - -<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/&relvers;/binaries/LynxOS" -url="ftp://ftp.XFree86.org/pub/XFree86/&relvers;/binaries/LynxOS"> - -A list of mirror sites is provided by -<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/MIRRORS" -url="ftp://ftp.XFree86.org/pub/XFree86/MIRRORS"> - -The binaries on the FTP site were built on the latest released LynxOS -version at the time XFree86 &relvers; was released. In this case it is -`LynxOS x86 3.0.1'. Because of changes made to the object format they -don't run on LynxOS versions earlier than 3.0.0. - -Building of this XFree86 version has never been tested on LynxOS versions -earlier than 2.5.1. +Building of this X11R&relvers; version has never been tested on LynxOS. This release contains preliminary build support for `LynxOS 3.1.0'. Since this OS release was not available long enough for serious testing `LynxOS 3.1.0' support has to be considered to be in `alpha state'. -Initial tests were performed on LynxOS x86 only! -XFree86 &relvers; supports LynxOS on the x86 and on +X11R&relvers; supports LynxOS on the x86 and on the PowerPC platform. X servers are currently available only on the x86 platform. The X server may work with some PowerPC platforms supported by LynxOS though this has not (yet) been thoroughly tested. -If you need binaries for other platforms than the one on the -XFree86 FTP server or if you have comments or suggestions about this -document contact me (<email>tmueller@sysgo.de</email>). - -<sect>Installing the Binaries +<sect>Installing X11R&relvers; <p> Please refer to the <htmlurl name="Installation Document" url="Install.html"> for detailed installation instructions. It may be necessary to increase the process stack limit in order to -run XFree86 on your system. Edit <tt>/etc/startab</tt> and reboot your +run X11R&relvers; on your system. Edit <tt>/etc/startab</tt> and reboot your system to make the changes active before you begin the installation. Also, be sure to include <tt>/usr/X11R6/bin</tt> in your PATH environment variable. -Refer to the next section <ref id="running" name="Running XFree86"> for +Refer to the next section <ref id="running" name="Running X11R&relvers;"> for further information on necessary configuration steps before running -XFree86 on LynxOS. +X11R&relvers; on LynxOS. -<sect1>Accessing XFree86 manual pages +<sect1>Accessing X11R&relvers; manual pages <p> Include <tt>/usr/X11R6/man</tt> in the MANPATH environment variable or add the directory <tt>/usr/X11R6/man</tt> to <tt>/usr/Lib/man.config</tt> -<sect>Running XFree86<p><label id="running"> +<sect>Running X11R&relvers;<p><label id="running"> This section describes the changes to the LynxOS environment -which may be necessary to successfully run XFree86. +which may be necessary to successfully run X11R&relvers;. <!-- Read <htmlurl url="QuickStart.html" name="Quick-Start Guide -to XFree86 Setup"> to learn more about how to configure XFree86 for +to X11R&relvers; Setup"> to learn more about how to configure X11R&relvers; for your hardware. --> <sect1>System tuning<p> <sect2>Tunable parameters<p> -To reasonably run XFree86 you may have to adjust a few system parameters. +To reasonably run X11R&relvers; you may have to adjust a few system parameters. On LynxOS 2.5.x and 3.0.x include a line <verb> @@ -118,7 +93,7 @@ more xterms. You may replace <tt>/sys/cfg/pty.cfg</tt> with If you're using an Intel PentiumPRO or Pentium II (or higher) class CPU you might want to install the MTRR device driver. This driver -enables the XFree86 X server to manipulate the CPU memory type range +enables the X11R&relvers; X server to manipulate the CPU memory type range registers which may improve performance on certain systems. To install the driver (on LynxOS x86 2.5.0 systems an higher) follow @@ -149,10 +124,10 @@ now: # reboot -N </verb></tscreen> -<sect1>Mouse support in XFree86<p> +<sect1>Mouse support in X11R&relvers;<p> -XFree86 includes support for PnP mice (see also <htmlurl -url="mouse.html" name="Mouse Support in XFree86">). The current LynxOS +X11R&relvers; includes support for PnP mice (see also <htmlurl +url="mouse.html" name="Mouse Support in X11R&relvers;">). The current LynxOS TTY device driver doesn't allow the necessary manipulation of the RTS line and therefore the support for PnP mice has been disabled for LynxOS. @@ -193,9 +168,9 @@ terminals in <tt>/etc/ttys</tt>, e.g. <tt>/dev/atc3</tt>: <sect1>X Server debug diagnostics output and other VT peculiarities<p> -Output made by the XFree86 X on its stdout or stderr will be lost -after the server switches to graphics mode. The XFree86 &relvers; -server stores its output in <tt>/usr/adm/XFree86.n.log</tt> (where +Output made by the X11R&relvers; X on its stdout or stderr will be lost +after the server switches to graphics mode. The X11R&relvers; +server stores its output in <tt>/usr/adm/X11R&relvers;.n.log</tt> (where <tt>n</tt> is the screen number). When the X server is running output made to other consoles will be @@ -204,11 +179,11 @@ be inconsistent with what one would expect (i.e. random). <!-- -<sect>Using XFree86 with Motif<p> +<sect>Using X11R&relvers; with Motif<p> The Motif libraries shipped with LynxOS AT 2.3.0 and 2.4.0 can be - used with the XFree86 libraries. Follow the steps outlined below after - you have installed XFree86 and LynxOS Motif on your system. + used with the X11R&relvers; libraries. Follow the steps outlined below after + you have installed X11R&relvers; and LynxOS Motif on your system. <sect1>Copy Motif files<p> @@ -233,7 +208,7 @@ be inconsistent with what one would expect (i.e. random). <sect1>Motif library patch for LynxOS AT 2.3.0<p> - The XFree86 libraries are compiled with the -mposix compiler option + The X11R&relvers; libraries are compiled with the -mposix compiler option while the Motif libraries shipped with LynxOS AT 2.3.0 are not. This incompatibility will cause Motif <tt>XmFileSelection</tt> widgets to be linked with the wrong (i.e. POSIX) directory routines. To circumvent this @@ -266,7 +241,7 @@ be inconsistent with what one would expect (i.e. random). <sect1>Motif config file patch<p> The file <tt>Motif.tmpl</tt> shipped with LynxOS Motif must be -modified to work with XFree86. In every reference to +modified to work with X11R&relvers;. In every reference to <tt>UnsharedLibReferences</tt> the first argument must be changed <tscreen> from @@ -282,22 +257,22 @@ modified to work with XFree86. In every reference to --> -<sect>Compiling the XFree86 Distribution<p> +<sect>Compiling the X11R&relvers; Distribution<p> <!-- out of date -Before trying to rebuild XFree86 from source read <htmlurl url="BUILD.html" -name="Building XFree86"> for a detailed description of the build +Before trying to rebuild X11R&relvers; from source read <htmlurl url="BUILD.html" +name="Building X11R&relvers;"> for a detailed description of the build process. -->The next sections contain LynxOS specific notes with respect to the build process. <sect1>Disk space requirements<p> Currently there is no support for shared libraries in the LynxOS -XFree86 port. A complete binary installation along with manual pages +X11R&relvers; port. A complete binary installation along with manual pages will require approximately 100 MBytes of disk space. To compile the system you will need at least 250 MBytes of free disk space. <sect1>Changes to system environment (LynxOS x86)<p> -Before compiling the XFree86 distribution you will have to make a +Before compiling the X11R&relvers; distribution you will have to make a few little adjustments to your system: <itemize> @@ -338,8 +313,8 @@ calls in <tt>libc</tt>. To reduce confusion you should modify <sect1> make World<p> <!-- out of date -Read <htmlurl url="BUILD.html" name="Building XFree86"> before trying -to rebuild XFree86 from the source distribution. +Read <htmlurl url="BUILD.html" name="Building X11R&relvers;"> before trying +to rebuild X11R&relvers; from the source distribution. --> If you have the MTRR device driver installed, add a line @@ -356,8 +331,8 @@ You may then issue a make World </verb></tscreen> -to compile XFree86. After a few hours (and hopefully a successful -build of the XFree86 system) you can install the software using +to compile X11R&relvers;. After a few hours (and hopefully a successful +build of the X11R&relvers; system) you can install the software using <tscreen><verb> make install @@ -370,19 +345,19 @@ On LynxOS x86 2.5.0 you may encounter problems with <tt>make</tt> in deeply nested subdirectories (eg core dumps, hangups). In this case update to GNU make version 3.75 or higher. -<sect1>Installing XFree86 manual pages<p><label id="installman"> +<sect1>Installing X11R&relvers; manual pages<p><label id="installman"> LynxOS uses cat-able manual pages, and because a doc preparation system is definitely not a vital component of a real-time operating system you must first install groff-1.09 (or newer). -XFree86 manual pages may be installed using +X11R&relvers; manual pages may be installed using <tscreen><verb> make install.man </verb></tscreen> -The index and whatis database for the XFree86 manual pages will be +The index and whatis database for the X11R&relvers; manual pages will be created automatically. If you already have a whatis database or index file in the destination directories you should perform a sort/uniq operation to remove duplicate entries: @@ -402,7 +377,7 @@ operation to remove duplicate entries: <!-- <sect>Building on microSPARC and PowerPC<label id="others"><p> - XFree86 3.3 compiles on LynxOS microSPARC and on LynxOS PPC as well. On the + X11R&relvers; 3.3 compiles on LynxOS microSPARC and on LynxOS PPC as well. On the microSPARC there is X server support for the colour frame buffers CG3 and CG6 while on the PPC there is no X server available at this time. Before you start the build (on versions earlier than 2.5.0) you must create a symbolic diff --git a/sgml/NetBSD.sgml b/sgml/NetBSD.sgml index b943842..8ad293d 100644 --- a/sgml/NetBSD.sgml +++ b/sgml/NetBSD.sgml @@ -1,67 +1,45 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN" [ +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN" [ <!ENTITY % defs SYSTEM "defs.ent"> %defs; ]> <article> -<title>README for XFree86 &relvers; on NetBSD +<title>README for X11R&relvers; on NetBSD <author>Rich Murphey, David Dawes, Marc Wandschneider, Mark Weaver, Matthieu Herrb -<Date>Last modified on: 9 November 2002 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/NetBSD.sgml,v 3.68 2003/02/16 17:21:11 dawes Exp $ </ident> <toc> -<sect>What and Where is XFree86? +<sect>What and Where is X11R6.7? <p> -XFree86 is an Open Source version of the X Window System that supports +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. This version is compatible -with X11R6.6. +with X11R6.6, and is based on the XFree86 4.4.0RC2 code base, which, +in turn was based on the X consortium sample implementation. See the <htmlurl url="COPYRIGHT.html" name="Copyright Notice">. <![ %notsnapshot [ -The sources for XFree86 are available by anonymous ftp from: +The sources for X11R&relvers; are available from: -<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/&relvers;" -url="ftp://ftp.XFree86.org/pub/XFree86/&relvers;"> +<htmlurl name="http://wiki.x.org" +url="http://wiki.x.org">]]> -Binaries for NetBSD 1.5 and later are available from: -<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/&relvers;/binaries/NetBSD" -url="ftp://ftp.XFree86.org/pub/XFree86/&relvers;/NetBSD"> - - -A list of mirror sites is provided by -<htmlurl name="http://www.xfree86.org/MIRRORS.shtml" -url="http://www.xfree86.org/MIRRORS.shtml"> -]]> - - -XFree86 also builds on other NetBSD architectures. See section +X11R&relvers; also builds on other NetBSD architectures. See section <ref id="otherarchs" name="Building on other architectures"> for details. -XFree86 also supports NetBSD on PC98 machines. - - -<sect>Bug Reports for This Document - -<p> -Send email to <email>herrb@XFree86.Org</email> (Matthieu Herrb) or -<email>XFree86@XFree86.org</email> if you have comments or suggestions about -this file and we'll revise it. - <sect>New OS dependent features <p> <![ %haverelnotes [ See the <htmlurl url="RELNOTES.html" name="Release Notes"> for -non-OS dependent new features in XFree86 &relvers;. +non-OS dependent new features in X11R&relvers;. ]]> <sect1>New OS dependent features in 4.2.0 @@ -114,7 +92,7 @@ now possible using the x86emu real mode emulator. <itemize> <item>Support for <em>silken mouse</em> with the wsmouse protocol has been added. -<item>A new version of the XFree86 Aperture driver which provides MTRR +<item>A new version of the Aperture driver which provides MTRR support is included. </itemize> @@ -128,7 +106,7 @@ for detailed installation instructions. <sect>Configuring X for Your Hardware <p> -The <tt>/etc/X11/XF86Config</tt> file tells the X server what kind of +The <tt>/etc/X11/xorg.conf</tt> file tells the X server what kind of monitor, video card and mouse you have. You <em/must/ create it to tell the server what specific hardware you have. @@ -141,30 +119,24 @@ You'll need info on your hardware: </itemize> -The recommended way to generate an <tt/XF86Config/ file is to use the -<tt/xf86cfg/ utility. The xf86config text utility is still there -for the (few) cases where xf86cfg can't be used. Also, there is a -sample file installed as <tt>/usr/X11R6/lib/X11/XF86Config.eg</tt>, -which can be used as a starting point. - -For details about the <tt/XF86Config/ file format, refer to the -<em><htmlurl name="XF86Config(5)" url="XF86Config.5.html"></em> manual page. +For details about the <tt/xorg.conf/ file format, refer to the +<em><htmlurl name="xorg.conf(5)" url="xorg.conf.5.html"></em> manual page. -Once you've set up a XF86Config file, you can fine tune the video +Once you've set up a xorg.conf file, you can fine tune the video modes with the <tt>xvidtune</tt> utility. <sect1>About mouse configuration <p> -XFree86 &relvers; has support for the mouse driver included in +X11R&relvers; has support for the mouse driver included in the <bf/wscons/ console driver introduced by NetBSD 1.4. Specify ``<tt/wsmouse/'' as the protocol and ``<tt>/dev/wsmouse0</tt>'' as the -device in <tt>/etc/X11/XF86Config</tt> if you're using NetBSD 1.4 or later +device in <tt>/etc/X11/xorg.conf</tt> if you're using NetBSD 1.4 or later with a PS/2 mouse. <p> For older releases, the NetBSD <bf/pms/ mouse driver handles PS/2 style mice as Busmouse. Specify the protocol as ``<tt/busmouse/'' in the -mouse section of your <tt/XF86Config/ file if you're using a PS/2 +mouse section of your <tt/xorg.conf/ file if you're using a PS/2 mouse with NetBSD 1.3 or former releases. <p> Only standard PS/2 mice are supported by this driver. Newest PS/2 @@ -173,7 +145,7 @@ Intellimouse, or MouseMan+ with a wheel) are not supported by NetBSD 1.3 and former releases. <p> See <htmlurl url="mouse.html" name="README.mouse"> for general -instruction on mouse configuration in XFree86. +instruction on mouse configuration. <sect>Running X @@ -231,8 +203,6 @@ screen 5 - vt100 (Thanks to Mason Loring Bliss <tt><mason@acheron.middleboro.ma.us></tt> for this explanation) <p> -Note that the binary distributions of XFree86 for NetBSD don't include -support for the XDM-AUTHORIZATION-1 protocol. <sect>Kernel Support for X @@ -277,7 +247,7 @@ in your kernel config file, and rebuild and install your kernel. <p> <label id="wscons"> Wscons is the current console driver, included in NetBSD 1.4 and -later. For now, XFree86 supports wscons using the pcvt compatibility +later. For now, X supports wscons using the pcvt compatibility mode, so be sure to have the lines: <tscreen><verb> options WSDISPLAY_COMPAT_PCVT # emulate some ioctls @@ -293,11 +263,12 @@ informations on how to configure wscons into the kernel. <p> By default NetBSD include the BSD 4.4 kernel security feature that disable access to the <tt>/dev/mem</tt> device when in -multi-users mode. But XFree86 servers can take advantage (or require) +multi-users mode. But X.org foundation X servers can take advantage +(or require) linear access to the display memory. -Most XFree86 &relvers; card drivers require linear memory access. -There are two ways to allow XFree86 to access linear memory: +Most X11R&relvers; card drivers require linear memory access. +There are two ways to allow X to access linear memory: The first way is to disable the kernel security feature by adding ``<tt/option INSECURE/'' in the kernel configuration file and build a new @@ -306,7 +277,7 @@ kernel. The second way is to install the aperture driver, included in source form in <tt>xc/programs/Xserver/hw/xfree86/etc/apNetBSD.shar</tt> in the -XFree86 &relvers; source distribution. Unpack it in a new directory of your +X11R&relvers; source distribution. Unpack it in a new directory of your choice by running: <tscreen><verb> sh apNetBSD.shar @@ -322,7 +293,7 @@ add the following line to <tt>/etc/lkm.conf</tt>: </verb></tscreen> and set ``<tt/lkm=YES/'' in <tt>/etc/rc.conf</tt> -Reboot your system. XFree86 will auto-detect the aperture +Reboot your system. X will auto-detect the aperture driver if available. <bf/Warning 1:/ if you boot another kernel than <tt>/netbsd</tt>, @@ -343,7 +314,7 @@ and AMD K6 class processors. <sect1>MIT-SHM <p> -NetBSD 1.0 and later supports System V shared memory. If XFree86 +NetBSD 1.0 and later supports System V shared memory. If X detects this support in your kernel, it will support the MIT-SHM extension. @@ -359,7 +330,7 @@ extension. to your kernel config file. -<sect> Rebuilding the XFree86 Distribution +<sect> Rebuilding the X Distribution <p> You should configure the distribution by editing @@ -377,23 +348,23 @@ add the line <tscreen><verb> #define HasPerl YES </verb></tscreen> -in <tt>xc/config/cf/host.def</tt> before rebuilding XFree86. +in <tt>xc/config/cf/host.def</tt> before rebuilding X. <sect1>Aperture driver <p> -To build the XFree86 server with the Aperture driver enabled, you +To build the X server with the Aperture driver enabled, you should unpack <tt>apNetBSD.shar</tt> and install it first. Then edit <tt>xc/config/cf/host.def</tt> and add the line <tscreen><verb> #define HasNetBSDApertureDriver YES </verb></tscreen> -to it before rebuilding XFree86. +to it before rebuilding X. <sect1>Console drivers<label id="console-drivers"> <p> -XFree86 has a configuration option to select the console +X has a configuration option to select the console drivers to use in <tt/host.def/: <itemize> <item> if you're using pccons put: @@ -427,7 +398,7 @@ to use the pcvt compatibility mode of wscons: <p> Note that the NetBSD project has now its own source tree, based on the -XFree86 source tree, with some local modifications. You may want to +X source tree, with some local modifications. You may want to start with this tree to rebuild from sources. The NetBSD xsrc source tree is available at: <htmlurl url="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/xsrc/" diff --git a/sgml/OS2Notes.sgml b/sgml/OS2Notes.sgml index 6bdc7d1..36d9ac7 100644 --- a/sgml/OS2Notes.sgml +++ b/sgml/OS2Notes.sgml @@ -1,19 +1,20 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN"> +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN" [ +<!ENTITY % defs SYSTEM "defs.ent"> %defs; +]> <article> -<title>Notes on Rebuilding XFree86/OS2 from Scratch +<title>Notes on Rebuilding X11R&relvers;/OS2 from Scratch <author>Holger Veit <date>Last modified March 8th, 2000 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/OS2Notes.sgml,v 1.2 2003/01/04 04:20:23 dawes Exp $ </ident> <toc> <sect>Preface <p> -X11 and XFree86 were initially developed on Unix-based systems. Usually +X11 was initially developed on Unix-based systems. Usually Unix systems provide a rich number of tools and utilities to get certain things done. Under OS/2, these tools are not installed, but ports are available which are sometimes functionally equivalent to Unix utilities @@ -24,19 +25,11 @@ from scratch under OS/2. Please also read <htmlurl name=README.OS2 url=OS2.html> for end-user information, and set at least the environment variables described there. <p> -At the current time, the most recent version available is XFree86-4.0. +At the current time, the most recent version available is X11R&relvers; This is a full and unrestricted version which comes with complete source code. 4.0 is a highly experimental release, so many features that might have worked in earlier versions, may now no longer work, or work differently. -Be aware that for OS/2, XFree86-4.0 is considered to be alpha software. - -If you want to join the XFree86 developer team, e.g. to add support for -certain hardware, please send a request to <email>BOD@XFree86.org</email>. -Please think about such a step carefully before, though, since much work -is involved. Please use the XFree86-4.0 source code as a test example -how to compile the system. The ability to manage that is a basic -requirement for becoming a developer. - +Be aware that for OS/2, X11R&relvers; is considered to be alpha software. <sect>Tools required <p> @@ -71,9 +64,9 @@ If there is no version number given, any new version will do. Particularly critical is only EMX/gcc and GNU make. Note that the second GCC implementation which might still be available from some archives is NOT compatible. -Furthermore, you need the XFree86 sources. These are available from -the common XFree86 repositories. Look into a directory which is -often named /pub/XFree86/4.0/source. +Furthermore, you need the X11R&relvers; sources. These are available from +the common X.org repositories. Look into a directory which is +often named /pub/R&relvers;. <sect>Compiling and Installing <p> @@ -98,7 +91,7 @@ installed them. Nor did I install the test subtree. in the <tt>\x11</tt> directory. At the end you will usually see the irritating, but non-fatal message "gzip: stdout Broken pipe". Ignore it. <item>After that, is is likely necessary to apply some patches, either from - the XConsortium or from the XFree86 project. Before you do this, enter + the X.Org Foundation. Before you do this, enter <verb> chmod -R a+rw \x11\xc </verb> @@ -137,18 +130,18 @@ installed them. Nor did I install the test subtree. <verb> find \x11 -name *.orig -print -exec rm {} ; </verb> -<item>Go to the <tt>xc/config/cf</tt> directory and edit the <tt>xf86site.def</tt> +<item>Go to the <tt>xc/config/cf</tt> directory and edit the <tt>xorgsite.def</tt> file to match your requirements (you probably don't want to compile all X servers). Certain changes must be set to the following values: <itemize> - <item>Disable if not already done any PC98 server; PC98 (Japanese XFree86) + <item>Disable if not already done any PC98 server; PC98 (Japanese X11R&relvers;) does not work yet. Porters from Japan are welcome! <item><tt>#define WacomSupport NO #define ElographicsSupport NO</tt> Both options are not yet supported. <item>Tcl* and Tk* don't need to be set explicitly. Reasonable defaults are in the other config files, provided you have a complete - XFree86/OS2 binary tree with the tcl/tk runtime support installed. + X11R&relvers;/OS2 binary tree with the tcl/tk runtime support installed. <item><tt>#define BuildDynamicLoading NO</tt> This does not work. </itemize> @@ -161,13 +154,13 @@ installed them. Nor did I install the test subtree. compressed fonts are corrupt. <item>Set the environment variable <tt/X11ROOT/ to something different than it is; otherwise the installation process will overwrite your - original XFree86/OS2 installation. If you have not set this variable, + original X11R&relvers;/OS2 installation. If you have not set this variable, go back to the prefix section of this document: you have forgotten something. <item>Copy the file <tt>xc/programs/Xserver/hw/xfree86/etc/bindist/OS2/host.def.os2</tt> to the location <tt>xc/config/cf/host.def</tt>. Use this file to do any specific modifications to imake variables, rather than editing - the file xfree86.cf, imake.tmpl, or os2.cf directly. + the file xorg.cf, imake.tmpl, or os2.cf directly. <item>Copy the file <tt>xc/config/util/buildos2.cmd</tt> into the <tt/xc/ directory. If this is a second or later attempt, you might need to copy the saved toplevel Makefile.os2 back to Makefile. @@ -188,15 +181,11 @@ installed them. Nor did I install the test subtree. <enum> <item>The xdm and linkkit directories will fail in compile and installation. This is no problem and has no effect on the rest of the system. -<item>The imake.exe which is installed in <tt/\XFree86\bin/ is usually defective. +<item>The imake.exe which is installed in <tt/\X11R&relvers;\bin/ is usually defective. The one which was built initially and installed in the root directory of the drive where you have the source tree is okay. So simply copy - this <tt/\imake.exe/ to the <tt/\XFree86\bin/ directory + this <tt/\imake.exe/ to the <tt/\X11R&relvers;\bin/ directory manually. Some day this might be fixed. -<item><tt/XF86Setup/ is not ported yet and won't work with the tcl/tk port - available for XFree86/OS2. My idea was to replace this by some native - installation tool, which I didn't find the time to do yet. Feel free - to spend a bit of time to play with XF86Setup if you like. </enum> </enum> diff --git a/sgml/OpenBSD.sgml b/sgml/OpenBSD.sgml index e39aa46..3b2918b 100644 --- a/sgml/OpenBSD.sgml +++ b/sgml/OpenBSD.sgml @@ -1,64 +1,53 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN" [ +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN" [ <!ENTITY % defs SYSTEM "defs.ent"> %defs; ]> <article> -<title>README for XFree86 &relvers; on OpenBSD +<title>README for X11R&relvers; on OpenBSD <author> Matthieu Herrb -<Date>Last modified on: 9 December 2003 +<Date>Last modified on: 9 December 2003; updated 25 March 2004 by Jim Gettys +for X11R&relvers; <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/OpenBSD.sgml,v 1.33 2004/02/15 02:16:48 dawes Exp $ </ident> <toc> -<sect>What and Where is XFree86? +<sect>What and Where is X11R&relvers;? <p> -XFree86 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. This version is compatible -with X11R6.6. +and Solaris x86) on Intel and other platforms. See the <htmlurl url="COPYRIGHT.html" name="Copyright Notice">. <![ %notsnapshot [ -The sources for XFree86 &relvers; are available by anonymous ftp from: +The sources for X11R&relvers; are available from -<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/&relvers;" -url="ftp://ftp.XFree86.org/pub/XFree86/&relvers;"> - -Binaries for OpenBSD/i386 3.4 and later are available from: - -<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/&relvers;/binaries/OpenBSD" -url="ftp://ftp.XFree86.org/pub/XFree86/&relvers;/binaries/OpenBSD"> - -A list of mirror sites is provided by -<htmlurl name="http://www.xfree86.org/MIRRORS.shtml" -url="http://www.xfree86.org/MIRRORS.shtml"> -]]> +<htmlurl name="http://wiki.x.org" +url="http://wiki.x.org">]]> <p> -XFree86 also builds on other OpenBSD architectures. See section +X11R&relvers; also builds on other OpenBSD architectures. See section <ref id="otherarch" name="Building on other architectures"> for details. <sect>Bug Reports for This Document <p> -Use the XFree86 Bugzilla at <url url="http://bugs.xfree86.org"> -to submit comments or suggestions about this file. +Use the X.org Bugzilla at <url url="http://bugzilla.freedesktop.org"> +to submit comments or suggestions about this file, using the xorg product. <sect>New OS dependent features <p> See the <htmlurl url="RELNOTES.html" name="Release Notes"> for -non-OS dependent new features in XFree86 &relvers;. +non-OS dependent new features in X11R&relvers;. -<sect1>New OS related features in 4.4 +<sect1>New OS related features <p> <itemize> <item>The IPv6 support is enabled on OpenBSD, but XDMCP over IPv6 is @@ -150,7 +139,7 @@ for detailed installation instructions. <sect>Configuring X for Your Hardware <p> -The <tt>/etc/X11/XF86Config</tt> file tells the X server what kind of +The <tt>/etc/X11/xorg.conf</tt> file tells the X server what kind of monitor, video card and mouse you have. You <em/must/ create it to tell the server what specific hardware you have. @@ -162,30 +151,30 @@ You'll need info on your hardware: <item>Your monitor's sync frequencies. </itemize> -The recommended way to generate an <tt/XF86Config/ file is to use the -<tt/xf86cfg/ utility. The xf86config text utility is still there -for the (few) cases where xf86cfg can't be used. Also, there is a -sample file installed as <tt>/usr/X11R6/lib/X11/XF86Config.eg</tt>, +The recommended way to generate an <tt/xorg.conf/ file is to use the +<tt/xorgcfg/ utility. The xorgconfig text utility is still there +for the (few) cases where xorgcfg can't be used. Also, there is a +sample file installed as <tt>/usr/X11R6/lib/X11/xorg.conf.eg</tt>, which can be used as a starting point. -For details about the <tt/XF86Config/ file format, refer to the -<em><htmlurl name="XF86Config(5)" url="XF86Config.5.html"></em> manual page. +For details about the <tt/xorg.conf/ file format, refer to the +<em><htmlurl name="xorg.conf(5)" url="xorg.conf.5.html"></em> manual page. -Once you've set up a XF86Config file, you can fine tune the video +Once you've set up a xorg.conf file, you can fine tune the video modes with the <tt>xvidtune</tt> utility. <sect1>About mouse configuration <p> -XFree86 &relvers; has support for the mouse driver included in +X11R&relvers; has support for the mouse driver included in the new <bf/wscons/ console driver introduced by OpenBSD-2.9. Specify ``<tt/wsmouse/'' as the protocol and -``<tt>/dev/wsmouse0</tt>'' as the device in <tt>/etc/X11/XF86Config</tt> +``<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. <p> See <htmlurl url="mouse.html" name="README.mouse"> for general -instruction on mouse configuration in XFree86. +instruction on mouse configuration. <sect>Running X @@ -208,12 +197,6 @@ xdm_flags="" # for normal use: xdm_flags="" </verb></tscreen> in <tt>/etc/rc.conf</tt>. -<p> -Note that the binary distributions of XFree86 for OpenBSD on -ftp.xfree86.org and its mirrors don't include -support for the XDM-AUTHORIZATION-1 protocol, because of the US export -rules. - <sect1>Running X without the display manager <p> The easiest way for new users to start X windows is to type: ``<tt/startx @@ -247,7 +230,7 @@ The pcvt console driver which was the default up to OpenBSD <p> By default OpenBSD includes the BSD 4.4 kernel security feature that disables access to the <tt>/dev/mem</tt> device when in -multi-user mode. But the XFree86 server requires +multi-user mode. But the X server requires linear access to the display memory in most cases. OpenBSD requires the aperture driver to be enabled for all X @@ -276,11 +259,11 @@ Set <tt/securelevel/ to -1 if you need more that one X server at a time. <sect1>MIT-SHM <p> -OpenBSD supports System V shared memory. If XFree86 +OpenBSD supports System V shared memory. If X detects this support in your kernel, it will support the MIT-SHM extension. -<sect> Rebuilding the XFree86 Distribution +<sect> Rebuilding the X Distribution You should configure the distribution by editing <tt>xc/config/cf/host.def</tt> before compiling. To compile the @@ -288,8 +271,8 @@ sources, invoke ``<tt/make World/'' in the xc directory. <p> -Note that OpenBSD project now has its own source tree, based on -the XFree86 source tree, with some local modifications. You may want +Note that OpenBSD project now has its own source tree, +with some local modifications. You may want to start with this tree to rebuild from sources. The OpenBSD XF4 source tree is available by anoncvs from all OpenBSD anoncvs servers. See <htmlurl url="http://www.openbsd.org/anoncvs.html" @@ -298,10 +281,10 @@ name="http://www.openbsd.org/anoncvs.html"> for details on anoncvs. <label id="otherarch"> <p> -XFree86 also compiles on other OpenBSD architectures. -<sect1>XFree86 on OpenBSD/alpha +X11R&relvers; also compiles on other OpenBSD architectures. +<sect1>X11R&relvers; on OpenBSD/alpha <p> -The XFree86 server is known to work on some VGA cards in alpha +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. <p> The following cards have been successfully tested for now: @@ -313,37 +296,37 @@ The following cards have been successfully tested for now: <item>Matrox MGA 2064 (8, 16 and 24 bits depth) </itemize> <p> -Note that this version of XFree86 doesn't work on TGA cards. The +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>XFree86 on OpenBSD/macppc +<sect1>X11R&relvers; on OpenBSD/macppc <p> -The XFree86 server is currently known to work on the G4 Macs and new +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. <p> -Use xf86config to build a /etc/X11/XF86Config file before starting +Use xorgconfig to build a /etc/X11/xorg.conf file before starting the server for the first time. <p> For the Titanium Powerbook G4, you can try the following mode line in -<tt>/etc/X11/XF86Config</tt> to match the flat panel resolution: +<tt>/etc/X11/xorg.conf</tt> to match the flat panel resolution: <tscreen><verb> Modeline "1152x768" 64.995 1152 1213 1349 1472 768 771 777 806 -HSync -VSync </verb></tscreen> -<sect1>XFree86 on OpenBSD/sparc +<sect1>OpenBSD/sparc <p> OpenBSD 3.2 on sparc switched to the wscons device driver and now uses -the OS specific <em/wsfb/ driver in the XFree86 server. This driver is -not included in XFree86 4.3. Please use the version shipped with +the OS specific <em/wsfb/ driver in the X server. This driver is +not included in X11R&relvers;. Please use the version shipped with OpenBSD instead. -<sect1>XFree86 on OpenBSD/sparc64 +<sect1>OpenBSD/sparc64 <p> -This version of XFree68 only has support for X clients on +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. @@ -360,7 +343,7 @@ pages you should update <tt/whatis.db/ by running ``<tt>makewhatis <sect> Thanks <p> -Many thanks to all people who contributed to make XFree86 work on +Many thanks to all people who contributed to make X11R&relvers; work on *BSD, in particular: <bf/David Dawes/, <bf/Todd Fries/, diff --git a/sgml/README.sgml b/sgml/README.sgml index db1829f..9492882 100644 --- a/sgml/README.sgml +++ b/sgml/README.sgml @@ -1,43 +1,46 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN" [ +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN" [ <!ENTITY % defs SYSTEM "defs.ent"> %defs; <!ENTITY % onediff 'IGNORE'> <!-- patch is a single diff file --> <!ENTITY % twodiffs 'IGNORE'> <!-- patch is split into two diff files --> <!ENTITY % threediffs 'IGNORE'> <!-- patch is split into three diff files --> -<!ENTITY % fourdiffs 'INCLUDE'> <!-- patch is split into four diff files --> -<!ENTITY % difftar 'INCLUDE'> <!-- patch also contains a tarball --> -<!ENTITY % removefiles 'INCLUDE'> <!-- patching requires removing some files --> +<!ENTITY % fourdiffs 'IGNORE'> <!-- patch is split into four diff files --> +<!ENTITY % difftar 'IGNORE'> <!-- patch also contains a tarball --> +<!ENTITY % removefiles 'IGNORE'> <!-- patching requires removing some files --> ]> <article> -<title>README for XFree86&tm; &relvers; -<author>The XFree86 Project, Inc -<date>23 February 2004 +<title>README for X11R&relvers; +<author>The X.Org Foundation +<date>6 April 2004 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.141 2004/02/26 17:11:45 dawes Exp $ +$Id$. </ident> <abstract> -XFree86 is an Open Source version of the X Window System that supports +X11R&relvers; is an Open Source version of the X Window System that supports many UNIX(R) and UNIX-like operating systems (such as Linux, FreeBSD, NetBSD, OpenBSD and Solaris x86) on Intel and other platforms. This -version is compatible with X11R6.6. +version is compatible with X11R6.6, +and is based on the XFree86 4.4.0RC2 code base, which, +in turn was based on the X Consortium X11R6.6 and earlier sample implementations. + </abstract> <toc> -<sect>What is XFree86 &relvers;? +<sect>What is X11R&relvers;? <p> - <![ %updaterel [ -XFree86 &relvers; is the &whichupdaterel; update to &fullrelvers;, +X11R&relvers; is the &whichupdaterel; update to X11R&fullrelvers;, the &whichfullrel; full release in the <![ %earlyrel; [new]]> -XFree86 4.x series. +X11R6.7 series. + Update releases are taken from a stable/maintenance branch. They are designed to be installed on top of the full release that they are @@ -47,32 +50,33 @@ stability. ]]> <![ %fullrel [ -XFree86 &relvers; is the &whichfullrel; full release in the +X11R&relvers; is the &whichfullrel; full release in the <![ %earlyrel; [new]]> -XFree86 4.x series. +X11R6.7 series. ]]> <![ %snapshot [ -XFree86 &relvers; is a pre-release snapshot of XFree86 &fullrelvers;. +X11R&relvers; is a pre-release snapshot of X11R&fullrelvers;. <![ %relcandidate [ This snapshot is release candidate &rcnum; for version &fullrelvers;. ]]> Pre-release snapshots are provided for beta testing. You should only install snapshots if you're comfortable dealing with possibly unstable beta-level software. If you find problems with this snapshot, you are encouraged -to report your findings to the public XFree86 mailing list: -<email>devel@XFree86.org</email>. +to report your findings to the public X.Org server mailing list: +<email>xorg@freedesktop.org</email>. <![ %relcandidate [ -XFree86 &relvers; is a feature-complete snapshot of XFree86 -&fullrelvers;. +X11R&relvers; is a feature-complete snapshot of X11R&fullrelvers;. ]]> ]]> <p> -XFree86 4.x is the current XFree86 release series. The first release in -this series was in early 2000. The core of XFree86 4.x is a modular -X server. +X11R6.7 is the current X.Org Foundation release series, based on the +XFree86 4.x code base. +The first release in +the XFree86 4.x series was in early 2000. +The core of X11R6.7 is a modular X server. <![ %fullrel [The &relvers; version is a new release that includes additional hardware support, functional enhancements and bug fixes.]]> <![ %haverelnotes [ @@ -80,24 +84,39 @@ Specific release enhancements can be viewed in the <htmlurl name="Release Notes" url="RELNOTES.html">. ]]> -Most modern PC video hardware is supported in XFree86 &relvers;, and +Most modern PC video hardware is supported in X11R&relvers;, and most PC video hardware that isn't supported explicitly can be used with -the "vesa" driver. The <htmlurl name="Releaes Notes" url="RELNOTES3.html"> -has a table showing the drivers provided with XFree86 &relvers;, and links +the "vesa" driver. The <htmlurl name="Release Notes" url="RELNOTES3.html"> +has a table showing the drivers provided with X11R&relvers;, and links to related documentation. +The X.Org Foundation X releases are produced by the X.Org Foundation. +The X.Org Foundation has been formed as a Delaware corporation organized to operate as a +scientific charity under IRS code 501(c)(3) to chartered to develop and +execute effective strategies which provide world-wide stewardship of the +X Window System technology and standards. Membership in the X.Org +Foundation is free to all participants. +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 is based on the codebase found in XFree86&trade 4.4RC2, +which in turn was based on the original X Window System sample implementation +from the X Consortium and it's successors. +This release is dedicated to the greater X community, developers +and users alike. + + XFree86™ is produced by The XFree86 Project, Inc through the work of a group of volunteer independent developers. The XFree86 Project is a non-commercial organisation and XFree86 would not exist without the invaluable development contributions of volunteers from around the world. -This release is dedicated to the greater XFree86 community, developers -and users alike. <![ %snapshot [ <sect>Redistribution of Snapshots <p> -While the XFree86 <htmlurl name="License" url="LICENSE.html"> doesn't +While the X.Org Foundation <htmlurl name="License" url="LICENSE.html"> doesn't prohibit vendors and others redistributing binaries of this snapshot release, we don't recommend including them in production releases. ]]> @@ -105,7 +124,7 @@ release, we don't recommend including them in production releases. <sect>Licensing <p> -XFree86 source code is covered by many licenses. All of these licenses +X Window System source code is covered by many licenses. All of these licenses have in common the fact that they do not impose significant conditions on the modification or redistribution or either source code or binaries beyond requiring one or more of the following: @@ -124,89 +143,60 @@ url="http://www.opensource.org/docs/definition.php">, and most are consistent with the Free Software Foundation's <htmlurl name="Free Software Definition" url="http://www.fsf.org/philosophy/free-sw.html">. -Copyright and Licensing information for XFree86, including the reproduction +Copyright and Licensing information for X, including the reproduction of copyright and/or license notices and attributions required by some of the licenses for binary distributions, can be found in the <htmlurl name="License Document" url="LICENSE.html">. If you find any omissions in that document, please contact us with details at -<email>bod@XFree86.org</email>. - +<email>xf_board@x.org</email>. +While the current licenses are all open source licenses, the +X.Org Foundation is attempting, with time, to bring as much as +possible of the code's licenses in the distribution into compliance with the +<htmlurl name="Debian Free Software Guidelines" +url="http://www.debian.org/social_contract#guidelines">. <sect>Pointers to additional information <p> The documentation for this release can be found online at the <url -name="XFree86 web site" url="http://www.xfree86.org/&relvers;/">. -Documentation for the latest release version can always be found <url -name="here" url="http://www.xfree86.org/current/">, and documentation -for the latest pre-release snapshot can be found <url name="here" -url="http://www.xfree86.org/snapshot/">. Checking those last two links -is a good way of finding out the latest available versions of XFree86. - +name="X.Org web site" url="http://wiki.x.org/">. Information about binary distributions and the attendant installation instructions can be found in the <htmlurl name="Installation Document" url="Install.html">. -The XFree86 version numbering system (including historical information) +The X11 version numbering system (including historical information) can be found in the <htmlurl name="Versions Document" url="Versions.html">. Additional information may be available at the <url -name="XFree86 web site" url="http://www.xfree86.org/">, and pointers to -other information are available at the <url name="XFree86 support page" -url="http://www.xfree86.org/support.html">. +name="X.Org Foundation Wiki" url="http://wiki.x.org/">. <sect>The Public Mailing Lists <p> -Current information about the XFree86 public mailing lists can be found -at our <url name="web site" url="http://www.xfree86.org/lists.html">. - -<sect1>CVS Commit -<p> -For those who want to see what has been committed recently to our CVS -repository this is the list that will show you those updates. This list -is updated dynamically every time the repository is updated after the -the commit happens. - -<sect1>Devel -<p> -This list is available for discussions about XFree86 development and -for following up well-defined bug reports. Many experienced XFree86 -developers are present on this list. - -<sect1>XFree86 -<p> -This list is available for any discussions and questions related to XFree86. -Support related questions should be sent here. Many experienced XFree86 -developers monitor this list. +Current information about the X.Org Foundation public mailing lists +is available on <url name="the X.Org mailing list page" url="http://www.x.org/XOrg_Foundation_Join_OpenLists.html"> and related desktop technology +mailing lists can be found on <url name="Freedesktop.org's mailing list page" +url="http://freedesktop.org/mailman/listinfo">. -<sect1>Forum -<p> -This list is available for high level discussions about XFree86 and related -technologies, their future, and for inter-project communication. - -<sect>Contributing to XFree86 +<sect>Contributing to the X.Org Foundation's X efforts. <p> If you have any new work or enhancements/bug fixes for existing work, -please submit them to <email>patch@XFree86.org</email> or to our <url -name="bug tracking system" url="http://bugs.xfree86.org/">. This will -ensure that they are included in future releases. New works should be -discussed on our <email>devel@XFree86.org</email> list prior to submission. - -Current information about the XFree86 development process can be found -at our <url name="web site" url="http://www.xfree86.org/developer.html">. +please send them to <email>xorg@freedesktop.org</email> or to our <url +name="bug tracking system" url="http://bugzilla.freedesktop.org/"> using +the xorg component. This will +ensure that they are included in future releases. -<sect>How to get XFree86 &relvers; +<sect>How to get X11R&relvers; <p> <![ %snapshot; [ -XFree86 &relvers; can be found at the <url name="XFree86 ftp server" -url="ftp://ftp.xfree86.org/pub/XFree86/snapshots/&relvers;/">, and at -mirrors of this server. This snapshot is available primarily in binary -form for several popular platforms. +X11R&relvers; can be found from the <url name="X.Org Foundation wiki at" +url="http://wiki.x.org">, and at +mirrors of this server. ]]> <![ %release; [ -XFree86 &relvers; can be found at the <url name="XFree86 ftp server" -url="ftp://ftp.xfree86.org/pub/XFree86/&relvers;/">, -and at mirrors of this server. Information about obtaining and installing +X11R&relvers; can be found from the <url name="X.Org Foundation wiki at" +url="http://wiki.x.org">, and at +mirrors of this server. +Information about obtaining and installing binary distributions of this release can be found in the <htmlurl name="Installation Document" url="Install.html">. Information about obtaining the release in source form is given below. @@ -228,36 +218,36 @@ gzip -d < &prevrelvers;-&relvers;.diff.gz | patch -p0 -E Information about getting the source for &prevrelvers can be found in the README file for that version, which can be found on the -<url name="XFree86 web site" url="http://www.xfree86.org/pub/XFree86/&prevrelvers;/README.html">. +<url name="X.Org foundation wiki" url="http://wiki.x.org">. ]]> <![ %fullrel [ The source for version &fullrelvers; is split into seven tarballs: <tscreen><verb> -XFree86-&fullrelvers;-src-1.tgz -XFree86-&fullrelvers;-src-2.tgz -XFree86-&fullrelvers;-src-3.tgz -XFree86-&fullrelvers;-src-4.tgz -XFree86-&fullrelvers;-src-5.tgz -XFree86-&fullrelvers;-src-6.tgz -XFree86-&fullrelvers;-src-7.tgz +X11R&fullrelvers;-src1.tar.gz +X11R&fullrelvers;-src2.tar.gz +X11R&fullrelvers;-src3.tar.gz +X11R&fullrelvers;-src4.tar.gz +X11R&fullrelvers;-src5.tar.gz +X11R&fullrelvers;-src6.tar.gz +X11R&fullrelvers;-src7.tar.gz </verb></tscreen> The first three contain everything except the fonts and general X11 documentation. Those three are sufficient -for building XFree86 if you already have a set of fonts. The fourth +for building X11R&relvers; if you already have a set of fonts. The fourth and fifth contain the fonts. The sixth contains the source for the general X11 documentation. The seventh contains the general X11 documentation in hardcopy format. <![ %onediff; [ A source patch relative to version &prevfullrelvers; is also available. -The patch file is <tt>XFree86-&prevfullrelvers;-&fullrelvers;.diff.gz</tt>. +The patch file is <tt>X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff.gz</tt>. <![ %difftar; [ There is also a tarball that contains some files that have components that can't be included in a diff. It is -<tt>XFree86-&prevfullrelvers;-&fullrelvers;-diff0.tgz</tt>. +<tt>X11R&relvers;-&prevfullrelvers;-&fullrelvers;-diff0.tgz</tt>. ]]> The patch should be applied to a clean &prevfullrelvers; source tree, working from @@ -265,11 +255,11 @@ the directory containing the <tt>xc/</tt> directory. The patch should be applied by running: <tscreen><verb> -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff.gz | patch -p0 -E </verb></tscreen> <![ %difftar; [ <tscreen><verb> -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;-diff0.tgz | tar vxf - +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;-diff0.tgz | tar vxf - </verb></tscreen> ]]> ]]> @@ -277,11 +267,11 @@ gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;-diff0.tgz | tar vxf - <![ %twodiffs; [ A source patch relative to version &prevfullrelvers; is also available. Because of its size, it is split into two parts. The patch files are -<tt>XFree86-&prevfullrelvers;-&fullrelvers;.diff1.gz</tt> and -<tt>XFree86-&prevfullrelvers;-&fullrelvers;.diff2.gz</tt>. +<tt>X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff1.gz</tt> and +<tt>X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff2.gz</tt>. <![ %difftar; [ There is also a tarball that contains some files that have components that -can't be included in a diff. It is <tt>XFree86-&prevfullrelvers;-&fullrelvers;-diff0.tgz</tt>. +can't be included in a diff. It is <tt>X11R&relvers;-&prevfullrelvers;-&fullrelvers;-diff0.tgz</tt>. ]]> These patches should be applied to a clean &prevfullrelvers; source tree, working from the directory @@ -289,12 +279,12 @@ containing the <tt>xc/</tt> directory. The patches should be applied by running: <tscreen><verb> -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff1.gz | patch -p0 -E -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff2.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff1.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff2.gz | patch -p0 -E </verb></tscreen> <![ %difftar; [ <tscreen><verb> -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;-diff0.tgz | tar vxf - +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;-diff0.tgz | tar vxf - </verb></tscreen> ]]> ]]> @@ -305,15 +295,15 @@ Because of its size, it is split into three parts. The patch files are: <tscreen><verb> -XFree86-&prevfullrelvers;-&fullrelvers;.diff1.gz -XFree86-&prevfullrelvers;-&fullrelvers;.diff2.gz -XFree86-&prevfullrelvers;-&fullrelvers;.diff3.gz +X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff1.gz +X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff2.gz +X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff3.gz </verb></tscreen> <![ %difftar; [ There is also a tarball that contains some files that have components that can't be included in a diff. It is -<tt>XFree86-&prevfullrelvers;-&fullrelvers;-diff0.tgz</tt>. +<tt>X11R&relvers;-&prevfullrelvers;-&fullrelvers;-diff0.tgz</tt>. ]]> These patches should be applied to a clean &prevfullrelvers; source tree, working from the directory @@ -321,13 +311,13 @@ containing the <tt>xc/</tt> directory. The patches should be applied by running: <tscreen><verb> -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff1.gz | patch -p0 -E -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff2.gz | patch -p0 -E -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff3.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff1.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff2.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff3.gz | patch -p0 -E </verb></tscreen> <![ %difftar; [ <tscreen><verb> -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;-diff0.tgz | tar vxf - +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;-diff0.tgz | tar vxf - </verb></tscreen> ]]> ]]> @@ -338,10 +328,10 @@ Because of its size, it is split into four parts. The patch files are: <tscreen><verb> -XFree86-&prevfullrelvers;-&fullrelvers;.diff1.gz -XFree86-&prevfullrelvers;-&fullrelvers;.diff2.gz -XFree86-&prevfullrelvers;-&fullrelvers;.diff3.gz -XFree86-&prevfullrelvers;-&fullrelvers;.diff4.gz +X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff1.gz +X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff2.gz +X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff3.gz +X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff4.gz </verb></tscreen> <![ %difftar; [ @@ -349,8 +339,8 @@ There is also a tarball and a cleanup script that handle files that have components that can't be included in a diff. These are: <tscreen><verb> -XFree86-&prevfullrelvers;-&fullrelvers;-diff0.tgz -XFree86-&prevfullrelvers;-&fullrelvers;-cleanup.sh +X11R&relvers;-&prevfullrelvers;-&fullrelvers;-diff0.tgz +X11R&relvers;-&prevfullrelvers;-&fullrelvers;-cleanup.sh </verb></tscreen> ]]> @@ -360,15 +350,15 @@ containing the <tt>xc/</tt> directory. The patches should be applied by running: <tscreen><verb> -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff1.gz | patch -p0 -E -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff2.gz | patch -p0 -E -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff3.gz | patch -p0 -E -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;.diff4.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff1.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff2.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff3.gz | patch -p0 -E +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;.diff4.gz | patch -p0 -E </verb></tscreen> <![ %difftar; [ <tscreen><verb> -sh XFree86-&prevfullrelvers;-&fullrelvers;-cleanup.sh -gzip -d < XFree86-&prevfullrelvers;-&fullrelvers;-diff0.tgz | tar vxf - +sh X11R&relvers;-&prevfullrelvers;-&fullrelvers;-cleanup.sh +gzip -d < X11R&relvers;-&prevfullrelvers;-&fullrelvers;-diff0.tgz | tar vxf - </verb></tscreen> ]]> ]]> @@ -381,18 +371,15 @@ with a clean &prevrelvers; source tree. ]]> --> -To format the XFree86 documentation use the latest version of our doctools -package available from the XFree86 CVS repository's "doctools" module, -and from our <url name="ftp site" -url="ftp://ftp.xfree86.org/pub/XFree86/misc/doctools-&doctoolsvers;.tgz">. +To format the X11R&relvers; documentation use the latest version of our doctools +package available from the Xorg CVS repository's "doctools" module. ]]> <!-- fullrel --> -The XFree86 source code for this and all releases/snapshots as well as -development versions can also be accessed via the XFree86 CVS repository. -Information about accessing this can be found at the <url name="CVS page" -url="http://www.xfree86.org/cvs/"> on our web site. It's also possible -to browse the XFree86 CVS repository at our <url name="CVSWeb server" -url="http://cvsweb.xfree86.org/">. The CVS tag for this version is +The X source code for this and all releases/snapshots as well as +development versions can also be accessed via the Freedesktop.org +CVS repository. +It's also possible to browse the <url name="freedesktop CVS repository" +url="http://cvs.freedesktop.org/">. The CVS tag for this version is "&reltag;". <![ %notsnapshot [ The CVS tag for the stable branch for this release is "&relbranchtag;". @@ -403,13 +390,14 @@ To check out the latest development version, don't specify any tag. <sect>Reporting Bugs <p> -Bugs should be reported to <email>XFree86@XFree86.org</email>. Before -reporting bugs, please check the XFree86 server log file, which can be -found at <tt>/var/log/XFree86.0.log</tt> on most platforms. If you +Bugs should be reported to <url +name="bug tracking system" url="http://bugzilla.freedesktop.org/"> using +the xorg compoent. Before +reporting bugs, please check the server log file, which can be +found at <tt>/var/log/Xorg.0.log</tt> on most platforms. If you can't resolve the problem yourself, send the entire log file with your bug report but not the operating system core dump. Do not edit the log file as our developers use it to reproduce and debug your problem. - - +Please attach it to your bug report. </article> diff --git a/sgml/RELNOTES.sgml b/sgml/RELNOTES.sgml index ea2df51..e4499b2 100644 --- a/sgml/RELNOTES.sgml +++ b/sgml/RELNOTES.sgml @@ -1,38 +1,67 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN" [ +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN" [ <!ENTITY % defs SYSTEM "defs.ent"> %defs; ]> <article> -<title>Release Notes for XFree86™ &relvers; -<author>The XFree86 Project, Inc -<date>3 March 2004 +<title>Release Notes for X11R&relvers; +<author>The X.Org Foundation +<and>The XFree86 Project, Inc. +<date>31 March 2004 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.117 2004/03/03 18:02:11 dawes Exp $ +$ Id: RELNOTES.sgml,v 1.1.4.4.2.2.4.3 2004/03/30 03:55:47 jg Exp $ </ident> <abstract> -This document contains information about features and their status in XFree86 -&relvers;. - +These release notes contains information about features and their status in the +X.Org Foundation X11R&relvers; release. +It is based on the XFree86 4.4RC2 RELNOTES document published by +The XFree86™ Project, Inc. +There are significant updates and differences in the X.Org release +as noted below. </abstract> <toc> <p> +<sect>Introduction to the X11R6.7 Release Series +<p> +The release numbering is based on the original MIT X numbering system. +X11 refers to the version of the network protocol that the X Window +system is based on: Version 11 was first released in 1988 and has been +stable for 15 years, with only upward compatible additions to the +core X protocol, a record of stability envied in computing. +Formal releases of X started with X version 9 from MIT; +the first commercial X products were based on X version 10. +The MIT X Consortium and its successors, the X Consortium, the Open Group +X Project Team, and the X.Org Group released versions X11R3 through X11R6.6, +before the founding of the X.Org Foundation. +<p> +X11R&relvers; is based on the merger of the X11R6.6 and XFree86 4.4RC2 +codebases, with significant updates, noted below. +<p> +There will be future maintenance releases in the X11R6.7.x series. +However, efforts are well underway to split the X distribution into +its modular components to allow for easier maintenance and independent +updates. We expect a transitional period while both X11R6.7 releases +are being fielded and the modular release completed and deployed while both +will be available as different consumers of X technology have different +constraints on deployment. We have not yet decided how the modular +X releases will be numbered. +<p> +Due to the new XFree86 1.1 license introduced in XFree86 4.4 (final), +later additions to XFree86 may not be incorporated into our codebase. +We encourage you to submit bug fixes and enhancements to bugzilla.freedesktop.org +using the xorg product, and discussions on this server take +place on <email>xorg@freedesktop.org</email>. -<sect>Introduction to the 4.x Release Series +<sect>Introduction to the XFree86 4.x Release Series <p> XFree86 4.0 was the first official release of the new XFree86 4 series. -<![ %updaterel [ -XFree86 &relvers; is the &whichupdaterel; update to &fullrelvers;, which -is the latest full release in that series. -]]> -<![ %fullrel [ -The current release (&relvers;) is the latest in that series. -]]> +It was based on X11R6.4. +<p> XFree86 4 represents a significant redesign of the XFree86 X server. Not all of the hardware drivers from 3.3.x have been ported to 4.x yet, but @@ -41,39 +70,18 @@ in 3.3.x. Our <htmlurl name="Driver Status document" url="Status.html"> summarizes how the hardware driver support compares between &legacyvers; and &relvers;. -XFree86 4.4 introduces an automatic configuration mechanism for the -XFree86 server which makes it now possible to start XFree86 without first -creating a configuration file. The initial automatic configuration -support is targeted towards Linux and FreeBSD and it is hoped that -automatic configuration will be supported on other platforms in -future releases. - -If you are running either Linux or FreeBSD, try it out if you -do not already have a working <tt>XF86Config</tt> file. If you want to -customise things afterwards, you can cut and paste the automatically -generated configuration from the <tt>/var/log/XFree86.0.log</tt> file -into an <tt>XF86Config</tt> file and make your customisations there. - -If you do not have any luck with automatic configuration, or you are using -a platform that is not currently supported, try one of the older methods -for getting started. - -XFree86 comes with a graphical configuration tool called "<tt>xf86cfg</tt>", +X11R&relvers; comes with a graphical configuration tool called +"<tt>xorgcfg</tt>", which also has a text mode interface and can be used to create an initial configuration file. It can also be used to customise existing configurations. -Next in the order of configuration preferences is to use the XFree86 +Next in the order of configuration preferences is to use the Xorg server's ability to create a starting configuration file. Run as root: - -<tscreen><verb> -XFree86 -configure -</verb></tscreen> - -and follow the instructions. +<tscreen><verb>Xorg -configure</verb></tscreen> and follow the instructions. Finally, if all else fails, the trusty old standby text-based tool -"<tt>xf86config</tt>" can also be used for generating X server config +"<tt>xorgconfig</tt>" can also be used for generating X server config files. At least one, and hopefully, all of these configuration options will @@ -82,7 +90,7 @@ file. With the automatic mechanism you might even find that you don't need one! If you do need to customise the configuration file, see the <htmlurl -name="XF86Config manual page" url="XF86Config.5.html">. You can also +name="xorg.conf manual page" url="xorg.conf.5.html">. You can also check the driver-specific manual pages and the related documentation (found at <ref id="drivertables" name="tables below"> also. @@ -100,7 +108,7 @@ The next section describes what is new in the latest version (&relvers;) compared with the previous full release (&prevfullrelvers). ]]> The other sections below describe some of the new features and changes -between 3.3.x and 4.0. There are lot's of new features, and we definitely +between 3.3.x and 4.0. There are lots of new features, and we definitely don't have enough space to cover them all here. </sect> @@ -115,30 +123,251 @@ don't have enough space to cover them all here. <sect>Summary of new features in &fullrelvers;. <p> -This is a sampling of the new features in XFree86 &fullrelvers;. A more +This is a sampling of the new features in X11R&fullrelvers;. A more complete list of changes can be found in the CHANGELOG that is part of -the XFree86 source tree. It can also be viewed online at our <url -name="CVSweb server" -url="http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/CHANGELOG?rev=HEAD">. - -<sect1>Security Updates +the X source tree. +<sect1>Enhancements in X11R&relvers; beyond XFree86 4.4RC2 <p> -The following security issues have been fixed in this release: +<itemize> +<item>The final version of the X11R6.7 versions of the X Window System + standards and specification documents are included. Updates since + X11R6.6 include a small correction to the numbering of requests in + the Shape Extension Protocol specification; the addition of IPv6 + support to the X11 Protocol, Xlib, XDMCP, and Session Manager + specifications; and the addition of the ServerInterpreted Host family + to the X11 Protocol and Xlib specifications. + +<item>IPv6 support updated to the final X11R6.7 versions of the standards, + including the addition of the ServerInterpreted Host family for xhost + style authentication. See the IPv6 section below for further details. + +<item>Only files without the new XFree86 1.1 license are included in the + X11R&relvers; release. Additionally, X.Org will be attempting, + when possible, to contact copyright holders of + material in the distribution when those + copyrights do not follow the Debian Free Software guidelines + to see if they can be relicensed to adhere to those standards. + +<item>Trademark law requires that there be no ambiguity about + the use of a trademark, + so the documentation, error message, name of the X executable, + configuration file name, etc., have all been changed to + avoid confusion of X.Org's implementation with the XFree86™ + trademarked implementation. Some of the changes made include: + <itemize> + <item> The name of the X server is Xorg, rather than XFree86. + <item> The name of the X server configuration file is + /etc/X11/xorg.conf rather than /etc/X11/XF86Config. + If xorg.conf does not exist, the server will look + for the old name. + <item>The config file and servername in xorg.cf is build + time configurable. + <item>The vendor string was updated to "X.Org Foundation". + <item>The X server's log file name was changed to + Xorg.?.log. + <item>xf86cfg was renamed xorgcfg. + <item>xf86config was renamed xorgconfig. + <item>All messages emitted by the server in the log were + updated to reflect the change in name. + <item>The module loader was modified to accept either + XFree86 generated modules or X.Org generated modules. + <item>Manual pages and other documentation was updated. + </itemize> +<item>Projective affine transforms and + the trapezoid primitives were implemented in XFree86 4.3 + with suboptimal performance. Work is underway to accelerate + these primitives. The render extension and render library in + XFree86 4.4 are stale and + were updated to version 0.8.4 in X11R&relvers; to fix a number of bugs, by a backport + from the modular X window system tree. + The bugs fixed include checks for + X servers not implementing render properly (e.g. Solaris + X servers which advertized support for render but failed + to support 1, 4, 8, 24, 32 depth pixmaps.) and eliminating + an unneeded dependence on libXext. + +<item>Fontconfig will no longer be installed by default since that + has often/usually resulted in overwriting more recent versions. + The fontconfig version 2.2.2 shipped in X11R&relvers; + needs to be built to allow programs in the tree to build that + depend on it, but those programs will run fine using installed + versions of fontconfig. If you do want to install the version + shipped in X11R&relvers; add: + <tscreen><verb> #define InstallFontconfigLibrary YES</verb></tscreen> to your host.def. We recommend instead if you need + to install a current fontconfig version, to get the current version + from <url name="fontconfig.org" url="http://www.fontconfig.org">. + +<item>Freetype was updated to version 2.1.7. + But installing freetype from X distributions would often or + usually result in the replacement or use of "stale" versions + of freetype. On Linux, FreeBSD, Solaris 10, and SCO5, therefore, X11R&relvers; + will by default use the version of freetype2 that is installed + on the system. If your system doesn't come with an installed + freetype2 and you wish to use the version supplied with this + distribution, please add: + <tscreen><verb> #define HasFreetype2 NO </verb></tscreen> to config/cf/host.def. Additonally, the default font + renderer for TrueType that is loaded by the X server was changed + to freetype. + +<item>During the build, the version of expat that is + installed on the system is used by default on Microsoft + Windows, FreeBSD, Linux and SCO5. + If your system doesn't come with an installed expat and you wish to + use the version supplied with this tree please add: + <tscreen><verb> #define HasExpat NO </verb></tscreen> to + config/cf/host.def. <url name="Libexpat's" + url="http://www.libexpat.org"> web site has current versions. + +<item>During build the version of zlib that is installed on the system + is used by default on OpenBSD, FreeBSD, Mac OS (Darwin), + Microsoft Windows (Cygwin), Linux, Sun Solaris, and SCO5. + If your system doesn't come with an installed zlib and you wish to + use the version supplied with this tree please add: + <tscreen><verb>#define HasZlib NO </verb></tscreen> to + config/cf/host.def. + <url name="Zlib's" url="http://www.gzip.org/zlib/"> web site + has current versions of zlib. + +<item>You are likely to need the ncurses and libpng libraries including + the development header files. Builds will also require + groff, flex, and optionally, perl5. + +<item>The TinyX (kdrive) driver was removed entirely from the tree + in X11R&relvers;. The version in XFree86 4.4 was 15 + months out of date as of XFree86 4.4's release in February 2004, + and is not supported in the monolithic Xorg X server tree. + Please turn to + <url name="freedesktop.org's X Server project" + url="http://xserver.freedesktop.org"> for + current kdrive support, including the new composite, + damage, and X fixes extension under development. + +<item>Xft was updated to version 2.1.5, to fix bugs with Freetype + compatibility. + +<item>The remains of XIE and PEX extensions were removed completely. + Similarly, libxml2's remains were removed, as it is not used + at all in the distribution. + +<item>The new fonttosfnt utility to convert .bdf/.pcf fonts to .ttf + format was removed as it is not yet ready and working. + Please turn to + <url name="freedesktop.org's X Applications" + url="http://xapps.freedesktop.org"> for a newer version. + +<item>Allow left and right modifier keys to be distinguished on Mac OS X + 10.3. (Does not work on earlier versions.) + + </itemize> + +<sect1>Summary of new features in Cygwin/X +<p> +This is a sampling of the new features in Cygwin/X in X11R&fullrelvers;. +<sect2>Cygwin/X Notes +<p> +Cygwin/X has continued its rapid pace of development that it has +sustained since Spring 2001 and this release shows it, we now have: a +stable and fast multi-window mode, seamless clipboard integration, a +configurable tray menu icon, popups on error messages pointing users +to the log file and our mailing list, the beginnings of indirect 3D +acceleration for OpenGL applications, improved non-US keyboard and +clipboard support, and only a handful of bugs that continue to be +reported. +<p> +Between the XFree86 4.3.0 release and the X.Org X116.7 release the +Cygwin/XFree86 project broke away from The XFree86 Project, Inc. due +to a lack of support from the XFree86 project. As such, the Cygwin/XFree86 +project was renamed to the Cygwin/X project and the upstream source +code tree that Cygwin/X pulls from and pushes to is now the tree +managed by the X.Org Foundation. The Cygwin/X project has seen a rush +of development and interest in the project since the split; one metric +showing this is that the number of CVS committers we have has gone +from zero to six. +<sect2>Cygwin/X-specific Changes +<p> +[Note: This list is by no means complete and covers issues that were +either specific to the Cygwin/X DDX or were reported as problems by a +number of Cygwin/X users, thus creating an interest in such a problem +being fixed. The complete <url name="Cygwin/X-specific change logs" + url="http://x.cygwin.com/devel/server/changelog-full.html"> can be seen +at http://x.cygwin.com/devel/server/changelog-full.html] <itemize> -<item>Fixes for potential integer overflows in font libraries. -(CAN-2003-0730) +<item>Major multi-window mode performance improvements and bug fixes. (Takuma Murakami, Earle F. Philhower III) -<item>Better pseudo-random number generation for XDM session cookies. -(CAN-2003-0692) +<item>Initial version of indirect 3D acceleration by mapping GLX to Win32's + OpenGL implementation. (Alexander Gottwald, Harold L Hunt II) -<item>Check for failure of the pam_setcred() function in xdm session initialization. (CAN-2003-0690) +<item>Allow clipboard integration to work seamlessly with Xdmcp. (Harold L Hunt II) -<item>Font file buffer overlows. (CAN-2004-0083, CAN-2004-0084 and -CAN-2004-0106) +<item>Fix clipboard integration to stop stealing ownership of the selection + X (caused text to be unhighlighted in emacs, xterm, etc.). (Harold L + Hunt II) -</itemize> +<item>Improved Japanese keyboard and clipboard support.(Kensuke Matsuzaki, + Takuma Murakami, Alexander Gottwald) + +<item>Customizable tray menu icon allowing shortcuts to start programs, + etc.(Earle F. Philhower III) + +<item>Add an About Cygwin/X dialog box to the tray icon menu. (Harold L Hunt II) + +<item>Fix crash with 24 bpp icons. (Fabrizio Gennari) + +<item>Improve window positioning in multi-window mode.(Earle F. Philhower III) + +<item>Allow overriding the tray icon in the .XWinrc preferences file.(Earle F. Philhower III) + +<item>New icons.(Jehan Bing, Michael Bax, Benjamin Rienfenstahl) + +<item>Fix some multi-monitor problems.(Takuma Murakami) + +<item>Prevent multiple instances of XWin.exe listening on the same display + number. (Takuma Murakami, Harold L Hunt II) + +<item>Present user with a dialog box containing useful information when + FatalError is called. (Harold L Hunt II) +<item>Make the multi-window mode window manager detectable by other window + managers such as twm. (Takuma Murakami) + +<item>Center dialog boxes in the desktop window. (Earle F. Philhower III) + +<item>Fix multi-window mode crashes when there were multiple instances of + XWin.exe. (Kensuke Matsuzaki) + +<item>Don't send localhost and 0.0.0.0 when making Xdmcp connections. + (Matthieu Herrb, Harold L Hunt II) + +<item>Fix repeated key strokes. (Ivan Pascal) + +<item>Fix synchronization of mode key states between X and Win32. + (Takuma Murakami) + +<item>Enable remapping of mouse buttons. (Takuma Murakami) + +<item>Enable copying and pasting of non-ascii characters in Windows + 95/98/Me. (Kensuke Matsuzaki) + +<item>Fix multiple crashes in the clipboard code. (Kensuke Matsuzaki, + Harold L Hunt II) + +<item>Automatic keyboard layouts for the most frequently used keyboard + layouts. (Alexander Gottwald) + +<item>Fix problem with TweakUI's focus-follows-mouse behavior. (Harold L Hunt II) + +<item>Fix problem with TweakUI's and the AltGr key. (Harold L Hunt II) + +<item>Built in SHM support with detection of the SHM engine (cygserver). + (Ralf Habacker, Harold L Hunt II) + +<item>expat, freetype2, fontconfig, libXft, and xterm are now built and + distributed separately from the monolithic packages. (Gerrit + P. Haase, Harold L Hunt II, Alexander Gottwald, Nicholas Wourms) + +<item>Merged in work on the NativeGDI engine. (Alan Hourihane) +</itemize> <sect1>Video Driver Enhancements <p> @@ -149,7 +378,6 @@ CAN-2004-0106) BIOS remain, especially for some laptops. <item>The nv driver for NVIDIA cards has been updated as follows: - <itemize> <item>Support added to the nv driver for the GeForce FX 5700, which didn't work with XFree86 4.3. @@ -157,7 +385,7 @@ CAN-2004-0106) <item>The driver now does a much better job of auto-detecting which connector of dual output cards the monitor is attached to, and this should reduce or eliminate the - need for manual XF86Config overrides. + need for manual xorg.conf overrides. <item>The 2D acceleration for TNT and GeForce has been completely rewritten and its performance should be substantially @@ -167,9 +395,7 @@ CAN-2004-0106) does scaled YUV bit blits. </itemize> - <item>The SiS driver has seen major updates, including: - <itemize> <item>Support for 661/741/760 and support for 330 (Xabre). @@ -181,7 +407,6 @@ CAN-2004-0106) again. </itemize> - <item>A new driver for several VIA integrated graphics chipsets has been added. <item>Various updates and bug fixes have been made to most other drivers. @@ -194,17 +419,29 @@ CAN-2004-0106) <itemize> <item>The mouse driver has some support on Linux and FreeBSD for auto-detecting which device node to use. This makes it unnecessary - to supply this information in the XF86Config file in most cases. + to supply this information in the xorg.conf file in most cases. </itemize> <sect1>IPv6 support <p> -XFree86 4.4 supports IPv6, based on the code contributed by Sun -Microsystems, Inc. to X.Org. See <url name="X.org's document" +X11R&relvers; supports IPv6, based on the code contributed by Sun +Microsystems, Inc. to X.Org. See <url name="X.Org's document" url="http://www.x.org/IPV6_Specific_Changes.html"> for a detailed list of what these changes are and how your system is affected by them. - +<p> +Note that in most environments script kiddies have generated sniffer +scripts that will easily grab passwords on a network. By default, +therefore, many software vendors now ship X with remote access disabled. +<p> +Unless you are confident of your network, direct use of IPv6 (or, for +that matter, IPv4) over the network to your X server is not +recommended; instead, we recommend the use of ssh ("ssh -X -C") to +provide strong cryptography (and possibly compression) for network +transparent use of X. Work is beginning to address this with a more +fully integrated encryption scheme that would avoid the extra process +context switches and improve performance over ssh (how much is +unknown). <sect2>Protocol names and aliases. <p> <itemize> @@ -224,9 +461,22 @@ support binding a IPv6 socket to a IPv4 address. <p> The XDM-AUTHORIZATION-1 authentication scheme does not support IPv6 addresses but a new release of the protocol, XDM-AUTHORIZATION-2 has -been designed; this though is yet to be implemented. By default XFree86 +been designed; this though is yet to be implemented. By default builds do not enable the XDM-AUTHORIZATION-1 code. +<sect2>ServerInterpreted host authentication +<p> +The ServerInterpreted host family was added in response to comments received +during the X11 over IPv6 standards public review period. This family allows +registration of new subtypes and implementation of them by modifications +solely to the X server, without having to modify clients such as xhost or the +Xlib or X protocol standards. In the initial X11R6.7.0 release, two +subtypes are supported - "hostname" for hostnames resolved by the +server at connection time to better support dynamic DNS & mobile +IP, and "ipv6" to allow IPv6 literal addresses, including in the future, +scoped addresses. For more information on these features, see the +xhost manual page, X11 Protocol and Xlib standards, and the documents +in xc/doc/specs/SIAddresses. <sect1>X Server and Extension Updates @@ -269,12 +519,8 @@ The user-visible changes to xterm since XFree86 4.3 are: <item>Modify scroll-back and scroll-forw actions to accept an adjustment value, e.g., - - <tscreen><verb> -scroll-back(1, page-2) - </verb></tscreen> - - to scroll back by 2 lines less than a page. + <tscreen><verb>scroll-back(1, page-2)</verb></tscreen> to + scroll back by 2 lines less than a page. <item>Add visualBellDelay resource to modify the length of time used for visual bell, for very slow displays or @@ -327,7 +573,6 @@ scroll-back(1, page-2) <item>Implement underlining. </itemize> - <item>Implement boldMode for wide-characters. <item>Modified to work with CJK double-width (bi-width/monospace) @@ -400,21 +645,18 @@ scroll-back(1, page-2) <p> <itemize> -<item>FreeType2 updated to version 2.1.4. - <item>The "freetype" X server font backend has been updated by the <url name="After X-TT Project" url="http://x-tt.sourceforge.jp/"> to include the functionality previously provided by the "xtt" backend, and to fix some bugs. The "xtt" backend will be dropped in the next release in favour of the updated unified "freetype" backend. - <itemize> <item>The new "freetype" backend has the improved "very lazy" metric calculation method which enables super-fast loading of proportional CJKV fonts. <item>All of the servers, including xfs, Xnest, Xprt, Xvfb, the - Cygwin-XFree86 server (as well as the XFree86 server) + Cygwin-X server (as well as the Xorg server) can handle the perfect TTCap options. </itemize> @@ -444,14 +686,13 @@ scroll-back(1, page-2) <item>Added support for the Apple-WM extension so XDarwin interoperates with quartz-wm. </itemize> - <item>On Darwin, IOKit mode now uses shadowfb for much faster drawing. <item>Various GNU/Hurd support updates. <item>Experimental support added for GNU/KFreeBSD and GNU/KNetBSD systems. -<item>SCO OpenServer support updates. XFree86 4.4 now works on Release +<item>SCO OpenServer support updates. X11R6.7 now works on Release 5.0.7 with Maintenance Pack 1, or on prior releases through Release 5.0.4. Please consult the <htmlurl name="README.SCO" url="SCO.html"> file for details. @@ -469,7 +710,7 @@ file for details. <sect1>Video Drivers <p> -XFree86 &relvers; includes the following video drivers: +X11R&relvers; includes the following video drivers: <table border=1 align="center"> <tabular ca="|l|l|l|"> @@ -568,7 +809,7 @@ 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">. -XFree86 &relvers; includes the following input drivers: +X11R&relvers; includes the following input drivers: <sect1>Input Drivers <p> @@ -625,9 +866,7 @@ Drivers marked with (*) are available for Linux only. <p> <itemize> -<item>Known issues with this version of the SiS driver: - - <itemize> +<item>Known issues with this version of the SiS driver: <itemize> <item>The driver will not work with upcoming laptops/notebooks with 661/741/760 and 30xLV bridges as regards LCD output. This is due folks at SiS at the very moment writing an entirely new @@ -653,14 +892,14 @@ running 'xset q' from within your X session. </itemize> -<sect>Overview of XFree86 4.x. +<sect>Overview of X11R6.7.x <p> -XFree86 4.x has a single X server binary called <tt>XFree86</tt>. This -binary can either have one or more video and input drivers linked in +On most platforms, X11R6.7.x has a single X server binary called <tt>Xorg</tt>. +This binary can either have one or more video and input drivers linked in statically, or more usually, dynamically, and in that manner load the video drivers, input drivers, and other modules that are needed. -XFree86 &relvers; has X server support for most UNIX® and UNIX-like +X11R&relvers; has X server support for most UNIX® and UNIX-like operating systems on Intel/x86 platforms, plus support for Linux and some BSD OSs on Alpha, PowerPC, IA-64, AMD64, Sparc, and Mips platforms, and for Darwin on PowerPC. Support for additional architectures @@ -668,7 +907,7 @@ and operating systems is in progress and is planned for future releases. <sect1>Loader and Modules <p> -The XFree86 X server has a built-in run-time loader, which can load +The X server has a built-in run-time loader, which can load normal object files and libraries in most of the commonly used formats. The loader does not rely on an operating system's native dynamic loader support and it works on platforms that do not provide this feature. @@ -695,8 +934,8 @@ not guaranteed because new modules may rely on interfaces added in new releases. <bf>Note about module security</bf> -<quote><p> - The XFree86 X server runs with root privileges, i.e. +<quote> + The X server runs with root privileges, i.e. the X server loadable modules also run with these privileges. For this reason we recommend that all users be careful to only use loadable modules from reliable sources, otherwise the @@ -704,18 +943,17 @@ releases. wreak havoc on your system. We hope to have a mechanism for signing/verifying the modules that we provide available in a future release. - </quote> <sect1>Configuration File <label id="config"> <p> -The XFree86 server uses a configuration file as the primary mechanism +The X server uses a configuration file as the primary mechanism for providing configuration and run-time parameters. The configuration -file format is described in detail in the <htmlurl name="XF86Config(5)" -url="XF86Config.5.html"> manual page. +file format is described in detail in the <htmlurl name="xorg.conf(5)" +url="xorg.conf.5.html"> manual page. -The XFree86 server has support for automatically determining an initial +The X server has support for automatically determining an initial configuration on most platforms, as well as support or generating a basic initial configuration file. @@ -724,20 +962,23 @@ initial configuration file. Command line options can be used to override some default parameters and parameters provided in the configuration file. These command line options -are described in the <htmlurl name="XFree86(1)" -url="XFree86.1.html"> manual page. +are described in the <htmlurl name="Xorg(1)" +url="Xorg.1.html"> manual page. <sect1>XAA <p> The XFree86 Acceleration Architecture (XAA) was completely rewritten -from scratch for XFree86 4.x. Most drivers implement acceleration by +from scratch for XFree86 4.x and is used in X11R&relvers;. +Most drivers implement acceleration by making use of the XAA module. +The Xorg server will accept modules built either for XFree86 4.4 +servers or its own. <sect1>Multi-head <p> -Some multi-head configurations are supported in XFree86 4.x, primarily -with multiple PCI/AGP cards. +Some multi-head configurations are supported in XFree86 4.x and +X11R6.x, primarily with multiple PCI/AGP cards. One of the main problems is with drivers not sufficiently initialising cards that were not initialised at boot time. This has been improved @@ -760,7 +1001,8 @@ an 8-bit screen together with a 16-bit screen in Xinerama mode. Xinerama is not enabled by default, and can be enabled with the <tt>+xinerama</tt> command line option for the X server. -Xinerama was included with X11R6.4. The version included in XFree86 4.x +Xinerama was included with X11R6.4. The version included in X11R6.7.x +and XFree86 4.x was completely rewritten for improved performance and correctness. Known problems: @@ -769,7 +1011,7 @@ Known problems: operations like window placement and resizing might not behave in an ideal way. This is an issue that needs to be dealt with in the individual window managers, and isn't specifically an - XFree86 problem. + X server problem. </itemize> @@ -821,7 +1063,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 XFree86 4.x. +The XVideo extension is supported in X11R6.7.x. 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 @@ -843,11 +1085,6 @@ translucent image overlays and other image operations not possible with the core X rendering system. <p> -XFree86 &relvers; provides a partial implementation of Render sufficient -for drawing anti-aliased text and image composition. Still to be -implemented are geometric primitives and affine transformation of images. - -<p> Unlike the core protocol, Render provides no font support for applications, rather it allows applications to upload glyphs for display on the screen. This allows the client greater control over text rendering and complete @@ -859,45 +1096,35 @@ Render applications. <p> On the client side, the Xft library provides access to fonts for -applications using the FreeType library, version 2. FreeType currently -supports Type1 and TrueType font files, a future release is expected to -support BDF and PCF files as well, so Render applications will have access -to the complete range of fonts available to core applications. One +applications using the FreeType library, version 2. One important thing to note is that Xft uses the vertical size of the monitor to compute accurate pixel sizes for provided point sizes; if your monitor doesn't provide accurate information via DDC, you may want to add that -information to <tt>XF86Config</tt>. +information to <tt>xorg.conf</tt>. <p> To allow a graceful transition for applications moving from core text -rendering to the Render extension, Xft can use either core fonts or FreeType -and the Render extension for text. By default, Xft is configured to support -both core fonts and FreeType fonts using the supplied version of FreeType -2. See the section on FreeType support in Xft for instructions on -configuring XFree86 to use an existing FreeType installation. +rendering to the Render extension, Xft can use either the core rendering +requests or the Render extension for text. +See the section on FreeType support in Xft for instructions on +configuring X11R&relvers; to use an existing FreeType installation. <p> -The Xft library uses a configuration file, <tt>XftConfig</tt>, which +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. </sect2> -<sect2>FreeType support in Xft -<p> - -XFree86 &relvers; includes sources for FreeType version 2.1.4, and, by -default, they are built and installed automatically. - -</sect2> <sect2>Application Support For Anti-Aliased Text <p> -Only three applications have been modified in XFree86 &relvers; to work +Only three applications have been modified in X11R&relvers; to work with the Render extension and the Xft and FreeType libraries to provide -anti-aliased text. Xterm, xditview and x11perf. Migration of other +anti-aliased text: xterm, xditview and x11perf. Migration of other applications may occur in future releases. <p> @@ -958,27 +1185,27 @@ Xedit has several new features, including: <sect1>Font support <p> -Details about the font support in XFree86 4.x can be found +Details about the font support in X11R&relvers;.x can be found in the <htmlurl name="README.fonts" url="fonts.html"> document. <sect1>TrueType support <p> -XFree86 4.x comes with two TrueType backends, known as +X11R6.7.x and XFree86 4.x comes with two TrueType backends, known as "FreeType" backend (the <tt>"freetype"</tt> module) and `X-TrueType' (the <tt>"xtt"</tt> module). Both of these backends are based on the FreeType library. The functionality of X-TrueType has been merged into the FreeType backend by the After X-TT Project for XFree86 4.4. -Consequently, the old X-TrueType backend will be dropped as of XFree86 -4.5. +Consequently, the old X-TrueType backend will be dropped +in the next major release. <sect1>CID font support <p> -Support for CID-keyed fonts is included in XFree86 4.x. +Support for CID-keyed fonts is included in X11R&relvers;.x. The CID-keyed font format was designed by <url name="Adobe Systems" url="http://www.adobe.com"> for fonts with large character sets. The -CID-keyed font support in XFree86 was donated by <url name="SGI" +CID-keyed font support in X11R&relvers; was donated by <url name="SGI" url="http://www.sgi.com">. See the <htmlurl name="LICENSE" url="LICENSE.html"> document for a copy of the CID Font Code Public License. @@ -986,7 +1213,7 @@ License. <sect1>Internationalisation of the scalable font backends <p> -XFree86 4.x has a ``fontenc'' layer to allow the scalable font backends +X11R6.7.x has a ``fontenc'' layer to allow the scalable font backends to use a common method of font re-encoding. This re-encoding makes it possible to uses fonts in encodings other than their their native encoding. This layer is used by the Type1 and Speedo backends and the @@ -1004,7 +1231,7 @@ transmitted in a compressed format. <sect1>Unicode/ISO 10646 support <p> -What is included in 4.x: +What is included in X11R6.7.x <itemize> <item>All ``-misc-fixed-*'' BDF fonts are now available in the @@ -1047,7 +1274,8 @@ What is included in 4.x: <p> A more flexible Compose file processing system was added to Xlib in -XFree86 4.4.0. The compose file is searched for in the following order: +X11R6.7.0. The compose file is searched for in +the following order: <enum> <item>If the environment variable <bf>$XCOMPOSEFILE</bf> is set, its value @@ -1065,12 +1293,8 @@ Compose files can now use an "include" instruction. This allows local modifications to be made to existing compose files without including all of the content directly. For example, the system's iso8859-1 compose file can be included with a line like this: - -<tscreen><verb> -include "/usr/X11R6/lib/X11/locale/iso8859-1/Compose" -</verb></tscreen> - -There are two substitutions that can be made in the file name of the +<tscreen><verb>include "/usr/X11R6/lib/X11/locale/iso8859-1/Compose"</verb></tscreen>There +are two substitutions that can be made in the file name of the include instruction. <bf>%H</bf> expands to the user's home directory (the <bf>$HOME</bf> environment variable), and <bf>%L</bf> expands to the name of the locale specific Compose file (i.e., @@ -1078,36 +1302,25 @@ name of the locale specific Compose file (i.e., For example, you can include in your compose file the default Compose file by using: - -<tscreen><verb> -include "%L" -</verb></tscreen> - -and then rewrite only the few rules that you need to change. New compose +<tscreen><verb>include "%L"</verb></tscreen>and +then rewrite only the few rules that you need to change. New compose rules can be added, and previous ones replaced. Finally, it is no longer necessary to specify in the right part of a rule a locale encoded string in addition to the keysym name. If the string is omitted, Xlib figures it out from the keysym according to the current locale. I.e., if a rule looks like: - -<tscreen><verb> -<dead_grave> <A> : "\300" Agrave -</verb></tscreen> - -the result of the composition is always the letter with the "\300" code. +<tscreen><verb><dead_grave> <A> : "\300" Agrave</verb></tscreen>the +result of the composition is always the letter with the "\300" code. But if the rule is: - -<tscreen><verb> -<dead_grave> <A> : Agrave -</verb></tscreen> - -the result depends on how Agrave is mapped in the current locale. +<tscreen><verb><dead_grave> <A> : Agrave</verb></tscreen>the +result depends on how Agrave is mapped in the current locale. <sect1>Luxi fonts from Bigelow and Holmes <label id="luxi"> <p> -XFree86 now includes the ``Luxi'' family of Type 1 fonts and TrueType +The X distribution includes the ``Luxi'' family of Type 1 fonts and +TrueType fonts. This family consists of the fonts ``Luxi Serif'', ``Luxi Sans'' and ``Luxi Mono'' in Roman, oblique, bold and bold oblique variants. The TrueType version have glyphs covering the @@ -1146,12 +1359,84 @@ please contact <p> <![ %snapshot [ -<bf>THIS IS A DRAFT OF THE XFree86 &fullrelvers; CREDITS SECTION.</bf> +<bf>THIS IS A DRAFT OF THE X11R&fullrelvers; CREDITS SECTION.</bf> If you find missing credits, incorrect attributions, or other errors, please -send details to <email>devel@XFree86.org</email>. +send details to <email>xorg@freedesktop.org</email>. ]]> -This section lists the credits for the XFree86 &relvers; release. For +This section lists the credits for the X11R6.7; release and +is in addition to the credits for the XFree86 4.4 release +credits below. +For a more detailed breakdown, refer to the CHANGELOG file in the X.Org +source tree, the CHANGELOG's +in <url name="the xorg product in freedesktop.org's CVS" +url="http://freedesktop.org/cgi-bin/viewcvs.cgi/xorg/xc/Attic/"> +or the 'cvs log' information for individual source files. + +<descrip> +<tag>New Features, Enhancements and Updates:</tag> + <descrip> + <tag>Mac OS X enhancements:</tag>Torrey T. Lyons, John Harper. + <tag>Cygwin/X enhancements:</tag>Harold L Hunt II, + <tag>IPv6 and ServerInterpreted enhancements:</tag>Alan Coopersmith + <tag>Release Engineering:</tag>Egbert Eich + <tag>Documentation updates:</tag>Jim Gettys, Keith Packard + <tag>Updated render:</tag>Keith Packard + <tag>Updated Xft:</tag>Keith Packard + <tag>Updated fontconfig:</tag>Keith Packard + </descrip> +Note: the list below does not contain acknowlegements to those working on the new modular X release as their work is not present in this release. +Patches and other submissions (in alphabetical order): +Paul Anderson, +Michael Bax, +Jehan Bing, +Peter Breitenlohner, +Alan Coopersmith, +Egbert Eich, +John Dennis, +Fabrizio Gennari, +Jim Gettys, +Alexander Gottwald, +Ralf Habacker +Mike Harris, +Mattheiu Herrb +Alan Hourihane, +Harold L Hunt II, +Elliot Lee, +Jeremy Katz, +Kaleb Keithley, +Stuart Kreitman, +Andreas Luik, +Torrey Lyons, +Roland Mainz, +Takuma Murakami, +Kensuke Matsuzaki, +Keith Packard, +Ivan Pascal, +Earle F. Philhower III, +Benjamin Rienfenstahl, +Leon Shiman, +Toshimitsu Tanaka, +Nicholas Wourms. +<p> + +<tag>Release Engineering:</tag>Egbert Eich, Kaleb S. Keithley + +<tag>Webmaster:</tag>Daniel Stone, Keith Packard, Jim Gettys + +<tag>Tinderbox setup:</tag>Jim Gettys, John Dennis + +<tag>X.Org Hosting:</tag><url name="The Open Group" +url="http://www.tog.org/">. + +<tag>Freedesktop.org Hosting:</tag><url name="Portland State University" +url="http://www.pdx.edu">. + +<tag>Organization:</tag>Howard Greenwell + +</descrip> + +This section lists the credits for the XFree86 4.4; release. For a more detailed breakdown, refer to the CHANGELOG file in the XFree86 source tree, the <url name="cvs-commit archives" url="http://www.mail-archive.com/cvs-commit@xfree86.org/maillist.html">, @@ -1174,8 +1459,7 @@ or the 'cvs log' information for individual source files. the After X-TT Project. <tag>Xterm fixes, maintenance and enhancements:</tag>Thomas E. Dickey. <tag>Mac OS X enhancements:</tag>Torrey T. Lyons, John Harper. - <tag>GNU/Hurd updates and preliminary GNU/KFreeBSD and GNU/KNetBSD - support:</tag>Robert Millan. + <tag>GNU/Hurd updates and preliminary GNU/KFreeBSD and GNU/KNetBSD support:</tag>Robert Millan. <tag>SCO support updates:</tag>Kean Johnston. <tag>Bitstream Vera fonts:</tag>Bitstream, Inc, and the GNOME Foundation. </descrip> @@ -1409,15 +1693,267 @@ Hui Yu. <tag>Docbook/XML conversion:</tag>John Himpel and the XFree86 documentation team. -<tag>Webmaster:</tag>Georgina O. Economou +<tag>XFree86 Webmaster:</tag>Georgina O. Economou -<tag>Hosting:</tag><url name="Internet Systems Consortium, Inc" +<tag>XFree86 Hosting:</tag><url name="Internet Systems Consortium, Inc" url="http://www.isc.org/">. </descrip> <sect>Attributions/Acknowledgements <p> +The X Window System has been a collaborative effort from its inception. +Our apologies for anyone or organization inadvertently overlooked. +Many individuals (including major contributors) who worked on X are +represented by their employers in this list. +<p> +<descrip> +<tag>This product includes software developed by: </tag> +2d3d Inc., +Adam de Boor, +Adobe Systems Inc., +After X-TT Project, +AGE Logic Inc., +Alan Hourihane, +Andreas Monitzer, +Andrew C Aitchison, +Andy Ritger, +Ani Joshi, +Anton Zioviev, +Apollo Computer Inc., +Apple Computer Inc., +Ares Software Corp., +ATI Technologies Inc., +AT&T Inc., +Bigelow and Holmes, +Bill Reynolds, +Bitstream Inc., +Brian Fundakowski Feldman, +Brian Goines, +Brian Paul, +Bruno Haible, +Charles Murcko, +Chen Xiangyang, +Chris Constello, +Cognition Corp., +Compaq Computer Corporation, +Concurrent Computer Corporation, +Conectiva S.A., +Corin Anderson, +Craig Struble, +Daewoo Electronics Co. Ltd., +Dale Schumacher, +Damien Miller, +Daniver Limited, +Daryll Strauss, +Data General Corporation, +David Bateman, +David Dawes, +David E. Wexelblat, +David Holland, +David J. McKay, +David McCullough, +David Mosberger-Tang, +David S. Miller, +Davor Matic, +Digital Equipment Corporation, +Dirk Hohndel, +Doug Anson, +Edouard TISSERANT, +Eduardo Horvath, +Egbert Eich, +Eric Anholt, +Eric Fortune, +Eric Sunshine, +Erik Fortune, +Erik Nygren, +Evans & Sutherland Computer Corporation, +Finn Thoegersen, +Frederic Lepied, +Free Software Foundation Inc., +Fujitsu Limited, +Fujitsu Open Systems Solutions Inc., +Fuji Xerox Co. Ltd., +Geert Uytterhoeven, +Gerrit Jan Akkerman, +Gerry Toll, +Glenn G. Lai, +Go Watanabe, +Gregory Mokhin, +Greg Parker, +GROUPE BULL, +Hans Oey, +Harald Koenig, +Harm Hanemaayer, +Harry Langenbacher, +Henry A. Worth, +Hewlett-Packard Company, +Hitachi Ltd, +Holger Veit, +Hummingbird Communications Ltd., +IBM Corporation, +Intel Corporation, +INTERACTIVE Systems Corporation, +International Business Machines Corp., +Itai Nahshon, +Jakub Jelinek, +James Tsillas, +Jason Bacon, +Jean-loup Gailly, +Jeff Kirk, +Jeffrey Hsu, +Jim Tsillas, +J. Kean Johnston, +Jon Block, +Jon Tombs, +Jorge Delgado, +Joseph Friedman, +Joseph V. Moss, +Juliusz Chroboczek, +Jyunji Takagi, +Kaleb S. Keithley, +Kazushi (Jam) Marukawa, +Kazuyuki (ikko-) Okamoto, +Keith Packard, +Keith Whitwell, +Kevin E. Martin, +Larry Wall, +Lawrence Berkeley Laboratory, +Lennart Augustsson, +Lexmark International Inc., +Linus Torvalds, +Machine Vision Holdings Inc., +Manfred Brands, +Marc Aurele La France, +Mark Adler, +Mark J. Kilgard, +Mark Leisher, +Mark Smulders, +Massachusetts Institute Of Technology, +Matrox Graphics, +Matthew Grossman, +Matthieu Herrb, +Metro Link Inc., +Michael H. Schimek, +Michael P. Marking, +Michael Schimek, +Michael Smith, +Ming Yu, +MIPS Computer Systems Inc., +National Semiconductor, +NCR Corporation Inc., +Netscape Communications Corporation, +Network Computing Devices Inc., +Noah Levitt, +Novell Inc., +Nozomi YTOW, +NTT Software Corporation, +Number Nine Computer Corp., +Number Nine Visual Technologies, +NVIDIA Corp., +Oivier Danet, +Oki Technosystems Laboratory Inc., +OMRON Corporation, +Open Software Foundation, +Orest Zborowski, +Pablo Saratxaga, +Panacea Inc., +Panagiotis Tsirigotis, +Paolo Severini, +Pascal Haible, +Patrick Lecoanet, +Patrick Lerda, +Paul Elliott, +Peter Kunzmann, +Peter Trattler, +Philip Homburg, +Precision Insight Inc., +Prentice Hall, +Quarterdeck Office Systems, +Randy Hendry, +Ranier Keller, +Red Hat Inc., +Regents of the University of California, +Rene Cougnenc, +Regis Cridlig, +Richard A. Hecker, +Richard Burdick, +Rich Murphey, +Rickard E. Faith, +Robert Baron, +Robert Chesler, +Robert V. Baron, +Robin Cutshaw, +S3 Graphics Inc., +Sam Leffler, +SciTech Software, +Scott Laird, +Sebastien Marineau, +Shigehiro Nomura, +ShoGraphics Inc., +Shunsuke Akiyama, +Silicon Graphics Computer Systems Inc., +Silicon Integrated Systems Corp Inc., +Silicon Motion Inc., +Simon P. Cooper, +Snitily Graphics Consulting Services, +Sony Corporation, +SRI, +Stanislav Brabec, +Stephan Dirsch, +Stephan Lang, +Steven Lang, +Sun Microsystems Inc., +SunSoft Inc., +SuSE Inc., +Sven Luther, +Takis Psarogiannakopoulos, +Takuya SHIOZAKI, +Tektronix Inc., +The DOS-EMU-Development-Team, +The Institute of Software Academia Sinica, +The NetBSD Foundation, +Theo de Raadt, +Theodore Ts'o, +The Open Group, +The Open Software Foundation, +The Regents of the University of California, +The Santa Cruz Operation Inc., +The Weather Channel Inc., +The X Consortium, +The XFree86 Project Inc., +Thomas E. Dickey, +Thomas G. Lane, +Thomas Mueller, +Thomas Roell, +Thomas Thanner, +Thomas Winischhofer, +Thomas Wolfram, +Thorsten.Ohl, +Tiago Gons, +Todd C. Miller, +Tomohiro KUBOTA, +Torrey T. Lyons, +TOSHIBA Corp., +Tungsten Graphics Inc., +UCHIYAMA Yasushi, +Unicode Inc., +UniSoft Group Limited, +University of Utah, +UNIX System Laboratories Inc., +URW++ GmbH, +VA Linux Systems, +VIA Technologies Inc., +Video Electronics Standard, +VMware Inc., +Vrije Universiteit, +Wittawat Yamwong, +Wyse Technology Inc., +X Consortium, +Xi Graphics Inc., +X-Oz Technologies, +X-TrueType Server Project, +and their contributors. This product includes software developed by The XFree86 Project, Inc (http://www.xfree86.org/) and its contributors. @@ -1431,10 +1967,11 @@ Berkeley and its contributors. This product includes software developed by Christopher G. Demetriou. This product includes software developed by the NetBSD Foundation, Inc. and its -contributors +contributors. -This product includes software developed by X-Oz Technologies -(http://www.x-oz.com/). +This product includes software developed by the X-Oz Technologies and its +contributors. +</descrip> </article> diff --git a/sgml/SCO.sgml b/sgml/SCO.sgml index 46bb4bb..c49b0e4 100644 --- a/sgml/SCO.sgml +++ b/sgml/SCO.sgml @@ -1,4 +1,6 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN"> +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN" [ +<!ENTITY % defs SYSTEM "defs.ent"> %defs; +]> <article> <!-- TitleS information --> @@ -8,7 +10,7 @@ <date>14 February 2003 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/SCO.sgml,v 3.23 2003/12/18 16:38:38 dawes Exp $ +$XdotOrg$ </ident> <!-- Table of contents --> @@ -19,11 +21,11 @@ $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/SCO.sgml,v 3.23 2003/12/18 16: <sect>Requirements<p> Before you can either compile or execute a binary distribution of -XFree86, the following conditions must be met: +X11R&relvers, the following conditions must be met: <itemize> <item>Ensure that you are running Release 5.0.4 or later. This is required because OSS646 is only supported on those platforms. There are no plans - to support XFree86 on earlier releases of OpenServer. + to support X11R&relvers; on earlier releases of OpenServer. <item>Ensure that OSS646, the ``Execution Environment Update'' package is installed, if appropriate. Check the release notes for that update to see whether or not your current operating system requires this @@ -38,7 +40,7 @@ XFree86, the following conditions must be met: the release notes for GWXLIBS to see if your platform requires the update. The latest version can always be found at the <url name="SCO FTP site" url="ftp://ftp.sco.com/pub/openserver5/opensrc">. - <item>To compile XFree86, you must use the SCO-supported version of + <item>To compile X11R&relvers;, you must use the SCO-supported version of the GNU C Compiler. It is possible that Skunkware versions of the compiler will work too, but this has not been tested. The ``GNU Development System'' is available for all releases from (and including) @@ -50,7 +52,7 @@ XFree86, the following conditions must be met: <item>If you are not using OSR 5.0.7 or later, you need to get an updated console driver. See <url url="http://www.sco.com"> for details on OpenServer supplements. If you can't or don't want to upgrade your - console driver, XFree86 will still compile, but you may run into + console driver, X11R&relvers; will still compile, but you may run into problems with some cards such as the Riva TNT and ATI Rage cards. The problem with the console driver in 5.0.6A and earlier is that when the X server sets graphics mode, the driver does not set a @@ -60,20 +62,20 @@ XFree86, the following conditions must be met: happens to be slap bang in the middle of palette data for the Riva TNT, so you get color map corruption. The updated console driver also has an improved mechanism for allocating video memory that - XFree86 detects at compile time, and it will use it if it exists. + X11R&relvers; detects at compile time, and it will use it if it exists. It is STRONGLY recommended that you get the console driver update. </itemize> -<sect>Compiling XFree86<p> +<sect>Compiling X11&relvers;<p> -Using the GNU Development System, compiling XFree86 should be fairly +Using the GNU Development System, compiling the distribution should be fairly straightforward. Before attempting to compile the system though, you should make sure that you have met all of the requirements above. To actually start the compilation, perform the following steps: <itemize> - <item>Copy the unmodified <tt>xf86site.def</tt> in <tt>xc/config/cf</tt> + <item>Copy the unmodified <tt>xorgsite.def</tt> in <tt>xc/config/cf</tt> to <tt>host.def</tt>. Edit <tt>host.def</tt> and make any changes you think you need. The most useful options to change are <tt>HasTcl</tt>, <tt>HasTk</tt>, <tt>HasXdmAuth</tt> if you have the file @@ -101,23 +103,23 @@ To actually start the compilation, perform the following steps: <tt>make install.man 2>&1 | tee -a install.log</tt> as root. </itemize> -<sect>Before Running XFree86<p><label id="sec-runxf86"> +<sect>Before Running X11R&relvers;<p><label id="sec-runxorg"> The SCO <tt/xterm/ terminfo description is not compatible with the <tt/xterm/ in the R5 distribution.<p> To use a Bus/Keyboard or PS2 mouse you should configure the mouse drivers using '<tt>mkdev mouse</tt>'. You may then use the -<tt>OsMouse</tt> option in your <tt>XF86Config</tt> to specify that XFree86 +<tt>OsMouse</tt> option in your <tt>xorg.conf</tt> to specify that X should use the SCO mouse drivers. To do this, set the <tt>Protocol</tt> to "<tt>OsMouse</tt>" in the <tt>Pointer</tt> section of your -<tt>XF86Config</tt> file. You can also use "<tt>OsMouse</tt>" for your +<tt>xorg.conf</tt> file. You can also use "<tt>OsMouse</tt>" for your serial mouse, especially if you are having trouble getting your mouse to -work using the XFree86 mouse drivers.<p> +work using the X mouse drivers.<p> <sect>Switching Consoles<p> -XFree86 uses similar console switching keys as the SCO R4 and R5 +X11R&relvers; uses similar console switching keys as the SCO R4 and R5 servers. That is, <tt>Ctrl-PrntScr</tt> takes you to the next console along from the one X is running on. If this is the last console it will take you to console 1. <tt>Ctrl-Alt-FXX</tt>, where <tt>XX</tt> is a function @@ -136,7 +138,7 @@ applications to terminate in an unpredictable way. You can set the <sect>Setting up Man Pages<p> After compiling the tree, or after installing the binary distribution you -can get <tt>man</tt> to recognise the XFree86 man pages by adding +can get <tt>man</tt> to recognise the Xorg man pages by adding <tt>/usr/X11R6/man</tt> to the <tt>MANPATH</tt> in <tt>/etc/default/man</tt>. The line should look similar to: @@ -159,8 +161,8 @@ script to format the manual pages yourself. <sect>Using SCO binaries/servers.<p> -XFree86 will accept connections from SCO binaries (R3 upwards) and the -SCO R5 server will also accept connections from XFree86 binaries. This +X11R&relvers; will accept connections from SCO binaries (R3 upwards) and the +SCO R5 server will also accept connections from X11R&relvers binaries. This means you may mix and match the two if you have ODT. For example you may still use the Panning Motif window manager (pmwm) if you prefer. diff --git a/sgml/Solaris.sgml b/sgml/Solaris.sgml index 8061af8..2960dec 100644 --- a/sgml/Solaris.sgml +++ b/sgml/Solaris.sgml @@ -1,42 +1,24 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN"> +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN"[ +<!ENTITY % defs SYSTEM "defs.ent"> %defs; +]> <article> <!-- Title information --> <title>Information for Solaris <author>David Holland, modified by Marc Aurele La France -<date>2001 October 01 +<date>2004 April 02 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Solaris.sgml,v 1.4 2003/01/04 04:20:23 dawes Exp $ </ident> <!-- Table of contents --> <toc> <!-- Begin the document --> -<sect>What is XFree86<p> -XFree86 is a port of X11R6.5.1 that supports several versions of Unix. -It is derived from X386 1.2 which was the X server distributed with X11R5. -This release consists of many new features and performance improvements as well -as many bug fixes. -The release is available as a source code distribution, as well as binary -distributions for many architectures. -<p> -The sources for XFree86 are available by anonymous ftp from: -<quote> - <htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/current" - url="ftp://ftp.XFree86.org/pub/XFree86/current"> -</quote> -Solaris binaries for XFree86 are available for anonymous ftp at the same -address. -Currently, two binary distributions are available: one for Solaris 8 x86, the -other for previous Solaris x86 releases. -They are <it>not</it> interchangeable. -No binary distribution is available for Solaris/SPARC as it is still under -development.<p> <sect>The VT-switching sub-system in Solaris x86<p> The virtual terminal sub-system is a undocumented, and unsupported feature of -Solaris x86. +Solaris x86 releases 2.1 through 7. It is no longer present in Solaris 8 and +later releases. Therefore if you use virtual terminals, you do so at <bf>YOUR OWN RISK</bf>.<p> Virtual terminals are not available in Solaris SPARC, and their availability has been removed in Solaris8 x86.<p> @@ -100,14 +82,14 @@ There are only a total of 8 available VT's (7 normal VT's + 1 console) not the usual 15. If you have all 8 allocated, and you attempt to allocate a additional VT you will panic the system. -(This bug is worked around in the Solaris XFree86 Xserver.)<p> +(This bug is worked around in the Solaris X11R&relvers; Xserver.)<p> From a programming stand point, they work pretty much as documented in the AT&T Unix System V/386 Release 4 Integrated Software Development Guide, however a number of <tt>ioctl()</tt> calls are broken.<p> -<sect>Notes for building XFree86 on Solaris<p> +<sect>Notes for building X11R&relvers; on Solaris<p> <enum> <item> -Both GCC, and ProWorks are supported by XFree86. +Both GCC, and the Sun Studio compilers are supported by X11R&relvers;. The minimum recommended GCC release is 2.7.2. Some earlier GCC's are known to not work and should be avoided.<p> You should also make certain your version of GCC predefines `sun'. @@ -127,18 +109,18 @@ strange hangs. Most notably image viewers such as xv-3.10 exhibit this problem.<p> It is recommended that you set ThreadedX in <tt>~xc/config/cf/host.def</tt> to NO, if you are using GCC. -ProWorks does not have this problem. +Sun's compilers do not have this problem. Whether this behaviour still exists with newer GCC's has not been verified.<p> <item> -To build XFree86 with GCC you need gcc and (optionally) c++filt from GNU +To build X11R&relvers; with GCC you need gcc and (optionally) c++filt from GNU binutils. Don't install gas or ld from GNU binutils, use the one provided by Sun.<p> You might need to setup a /opt/SUNWspro/bin directory containing symbolic links named <tt/cc/, <tt/CC/, and <tt/c++filt/ pointing respectively to the actual <tt/gcc/, <tt/g++/ and <tt/c++filt/ commands.<p> <item> -If you are using ProWorks to compile the XFree86 distribution, you need to -modify your PATH appropriately so the ProWorks tools are available. +If you are using Sun compilers to compile the X11R&relvers; distribution, you need to +modify your PATH appropriately so the Sun compiler tools are available. Normally, they should be in <tt>/opt/SUNWspro/bin</tt><p> <item> You <bf>MUST</bf> put <tt>/usr/ccs/bin</tt> at the front of your PATH. @@ -148,7 +130,7 @@ So the <tt>/usr/ccs/bin</tt> versions of these programs must be found before any possible GNU versions. (Most notably GNU '<tt/ar/' does not work during the build).<p> </enum> -<sect>Notes for running XFree86 on Solaris<p> +<sect>Notes for running Xorg on Solaris<p> <enum> <item> Depending on the release or architecture of Solaris you are running, you might @@ -162,7 +144,7 @@ driver is included in <tt>xc/programs/Xserver/hw/xfree86/etc/apSolaris.shar</tt> of the source distribution. This file can usually also be found in the <tt>/usr/X11R6/lib/X11/etc</tt> -directory when XFree86 is installed. +directory when Xorg is installed. Building, and installing the driver is relatively straight forward. Please read its accompanying README file.<p> <item> @@ -176,12 +158,12 @@ so:<p> If you have made the virtual terminal devices you do not need to specify the VT to run the Xserver on.<p> <item> -For Solaris you will probably want to set your LD_LIBRARY_PATH to +For old releases of Solaris you will probably want to set your LD_LIBRARY_PATH to <tt>/usr/X11R6/lib:/usr/openwin/lib:/usr/dt/lib</tt>. Including <tt>/usr/X11R6/lib</tt> in your LD_LIBRARY_PATH is probably not necessary, however it doesn't hurt. :)<p> Including <tt>/usr/openwin/lib</tt> in the LD_LIBRARY_PATH is recommended -because some Sun supplied binaries were not compiled with LD_RUN_PATH set +on older releases because some Sun supplied binaries were not compiled with LD_RUN_PATH set properly at compile time.<p> Motif and CDE applications may require <tt>/usr/dt/lib</tt> in your LD_LIBRARY_PATH too. @@ -212,5 +194,6 @@ reported!). It might even have broken some aspects of the x86 port.<p> </enum> <sect>Bug Notification<p> -Bug reports should be sent to <email>XFree86@XFree86.org</email>. +Bug reports should be reported using the bugzilla.freedesktop.org using the +xorg product or sent to <email>xorg@freedesktop.org</email>. </article> diff --git a/sgml/Versions.sgml b/sgml/Versions.sgml index 4eea959..0111f6d 100644 --- a/sgml/Versions.sgml +++ b/sgml/Versions.sgml @@ -5,18 +5,22 @@ <article> -<title>XFree86 Version Numbering Schemes +<title>X.Org and XFree86 Version Numbering Schemes <author>The XFree86 Project, Inc -<date>23 February 2003 +<and>Updated for X11R&relvers; by Keith Packard +<date>25 March 2004 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Versions.sgml,v 1.4 2003/02/24 03:41:23 dawes Exp $ </ident> <abstract> +X.Org has adopted the same basic numbering scheme used by the XFree86 +Project, Inc. for their releases. The actual numbers are different, but the +basic scheme is the same. This document reflects the policy that X.Org uses. + The version numbering schemes used by XFree86 have changed from time to -time. The schemes used since version 3.3 are explained here. +time. </abstract> @@ -25,7 +29,7 @@ time. The schemes used since version 3.3 are explained here. <sect>Releases, Development Streams and Branches <p> -As of the release of version 4.0.2 in December 2000, XFree86 has three +As of the release of version 6.7.0 in March 2004, X.Org has three release branches. First is trunk of the CVS repository. This is the main development stream, where all new work and work for future releases is done. @@ -37,18 +41,12 @@ in the release will be added to this branch (as well as the trunk), and updates to this release (if any) will be cut from this branch. Similar stable branches are present for previous full releases. -Finally there is the 3.3.x legacy branch, which is called -"<tt>xf-3_3-branch</tt>". While this branch is not actively being -maintained, it does include some important post-3.3.6 bug fixes and -security updates. Relevant security updates in particular are usually -back-ported to this branch. - -XFree86 is planning to make full releases from the main development +X.Org is planning to make full releases from the main development stream at regular intervals in the 6-12 month range. The feature freezes for these releases will usually be 2-3 months before the release dates. This general plan is a goal, not a binding commitment. The actual release intervals and dates will depend to a large degree on the -resource available to XFree86. Full releases consist of full source +resource available to X.Org. Full releases consist of full source code tarballs, plus full binary distributions for a range of supported platforms. Update/bugfix releases will be made on an as-required basis, depending also on the availability of resources, and will generally be @@ -61,12 +59,6 @@ The next full release will be version &nextfullrelvers;. There is no scheduled update release, but if one is needed, the version will be &nextupdrelvers;. -<!-- -The next release on the legacy branch will be 3.3.7. There is currently -no schedule for that release. The 3.3.7 release is likely to be the -final release on that branch. ---> - Aside from actual releases, snapshots of the active release branches are tagged in the CVS repository from time to time. Each such snapshot has an identifiable version number. @@ -74,10 +66,8 @@ has an identifiable version number. <sect>Current (new) Version Numbering Scheme <p> -Starting with the main development branch after 4.0.2, the XFree86 +Starting with the main development branch after 6.7.0, the X.Org versions are numbered according to the scheme outlined here. -Both the 4.0.2 stable branch and the 3.3.x legacy branch continue -to use the previous scheme, which is outlined in the sections below. The version numbering format is <tt>M.m.P.s</tt>, where <tt>M</tt> is the major version number, <tt>m</tt> is the minor version number, @@ -93,34 +83,34 @@ of the development and stable branches. Immediately after forming a release stable branch, the patch level number for the main development branch is bumped to 99, and the snapshot number is reset. The snapshot number is incremented for each tagged development -snapshot. The CVS tag for snapshots is "<tt>xf-M_m_P_s</tt>". When +snapshot. The CVS tag for snapshots is "<tt>x-M_m_P_s</tt>". When the development branch enters feature freeze, the snapshot number may be bumped to 900, and a stable branch may be created for the next full release. -The branch is called "<tt>xf-M_m-branch</tt>". The snapshot number is +The branch is called "<tt>x-M_m-branch</tt>". The snapshot number is incremented from there until the release is finalised. Each of these snapshots is a "release candidate". When the release is finalised, the minor version is incremented, the patch level is set to zero, and the snapshot number removed. Here's an example which shows the version number sequence for the -development leading up to version 4.1.0: +development leading up to version 6.8.0: <descrip> - <tag><tt>4.0.99.1</tt></tag> - The first snapshot of the pre-4.1 development branch. - <tag><tt>4.0.99.23</tt></tag> - The twenty-third snapshot of the pre-4.1 development branch. - <tag><tt>4.0.99.900</tt></tag> - The start of the 4.1 feature freeze, which marks the creation of - the "<tt>xf-4_1-branch</tt>" branch. That branch is the "stable" - branch for the 4.1.x releases. - <tag><tt>4.0.99.903</tt></tag> - The third 4.1.0 release candidate. - <tag><tt>4.1.0</tt></tag> - The 4.1.0 release. - <tag><tt>4.1.99.1</tt></tag> - The first pre-4.2 development snapshot, which is the first main - branch snapshot after creating the 4.1 stable branch. + <tag><tt>6.7.99.1</tt></tag> + The first snapshot of the pre-6.8 development branch. + <tag><tt>6.7.99.23</tt></tag> + The twenty-third snapshot of the pre-6.8 development branch. + <tag><tt>6.7.99.900</tt></tag> + The start of the 6.8 feature freeze, which marks the creation of + the "<tt>x-6.8-branch</tt>" branch. That branch is the "stable" + branch for the 6.8.x releases. + <tag><tt>6.7.99.903</tt></tag> + The third 6.8.0 release candidate. + <tag><tt>6.8.0</tt></tag> + The 6.8.0 release. + <tag><tt>6.8.99.1</tt></tag> + The first pre-6.9 development snapshot, which is the first main + branch snapshot after creating the 6.8 stable branch. </descrip> <sect1>Stable Branch @@ -135,220 +125,58 @@ update release if finalised. The patch level value (<tt>P</tt>) is incremented for each update release. Here's an example which shows the version number sequence for the -4.1.x stable branch. +6.8.x stable branch. <descrip> - <tag><tt>4.0.99.900</tt></tag> - The start of the 4.1 feature freeze, which marks the creation of - the "<tt>xf-4_1-branch</tt>" branch. That branch is the "stable" - branch for the 4.1.x releases. - <tag><tt>4.0.99.903</tt></tag> - The third 4.1.0 release candidate. - <tag><tt>4.1.0</tt></tag> - The 4.1.0 release. - <tag><tt>4.1.0.901</tt></tag> - The first pre 4.1.1 snapshot. - <tag><tt>4.1.0.903</tt></tag> - The third pre 4.1.1 snapshot, also known as the third 4.1.1 release + <tag><tt>6.7.99.900</tt></tag> + The start of the 6.8 feature freeze, which marks the creation of + the "<tt>x-6.8-branch</tt>" branch. That branch is the "stable" + branch for the 6.8.x releases. + <tag><tt>6.7.99.903</tt></tag> + The third 6.8.0 release candidate. + <tag><tt>6.8.0</tt></tag> + The 6.8.0 release. + <tag><tt>6.8.0.901</tt></tag> + The first pre 6.8.1 snapshot. + <tag><tt>6.8.0.903</tt></tag> + The third pre 6.8.1 snapshot, also known as the third 6.8.1 release candidate. - <tag><tt>4.1.1</tt></tag> - The 4.1.1 release. - <tag><tt>4.1.1.901</tt></tag> - The first pre 4.1.2 snapshot. - <tag><tt>4.1.2</tt></tag> - The 4.1.2 release. + <tag><tt>6.8.1</tt></tag> + The 6.8.1 release. + <tag><tt>6.8.1.901</tt></tag> + The first pre 6.8.2 snapshot. + <tag><tt>6.8.2</tt></tag> + The 6.8.2 release. </descrip> -<sect>Version Numbering Scheme for XFree86 4.0.x. -<p> - -The version numbering format for XFree86 4.0.x releases is <tt>M.m.nx</tt>, -where <tt>M</tt> is the major version number (4), <tt>m</tt> is the -minor version number (0), <tt>n</tt> is the sub-minor version number, -and <tt>x</tt> is a letter. Full release versions up to and including -4.0.2 were 4.0, 4.0.1, and 4.0.2. Between-release snapshots are -indicated by including <tt>x</tt>, a lower case letter. For example, -the first post-4.0.1 snapshot was 4.0.1a. Release candidates have -been indicated by setting <tt>x</tt> to a one or two letter combination -with the first letter being "Z". For example, 4.0.1Z was the first -4.0.2 release candidate. - -The next 4.0.x release will be an update release, not a full release. -These update releases will be indicated by incrementing the sub-minor -version number. So, the first post-4.0.2 update release will be 4.0.3. -Between-release snapshots will continue to be indicated with a lower -case letter, so the first pre-4.0.3 snapshot will be 4.0.2a. - -The following example illustrates the release sequence from 4.0 through -to the post-4.0.2 update releases. - -<descrip> - <tag><tt>4.0</tt></tag> - The 4.0 release. - <tag><tt>4.0a</tt></tag> - The first post-4.0 development snapshot. - <tag><tt>4.0f</tt></tag> - The sixth post-4.0 development snapshot. - <tag><tt>4.0Z</tt></tag> - The 4.0.1 release candidate. - <tag><tt>4.0.1</tt></tag> - The 4.0.1 release. - <tag><tt>4.0.1a</tt></tag> - The first post-4.0.1 development snapshot. - <tag><tt>4.0.1f</tt></tag> - The sixth post-4.0.1 development snapshot. - <tag><tt>4.0Z</tt></tag> - The first 4.0.2 release candidate. - <tag><tt>4.0Zb</tt></tag> - The third 4.0.2 release candidate. - <tag><tt>4.0.2</tt></tag> - The 4.0.2 release. - <tag><tt>4.0.2a</tt></tag> - The first pre-4.0.3 snapshot/release candidate. - <tag><tt>4.0.2c</tt></tag> - The third pre-4.0.3 snapshot/release candidate. - <tag><tt>4.0.3</tt></tag> - The 4.0.3 update release. - <tag><tt>4.0.3a</tt></tag> - The first pre-4.0.4 snapshot/release candidate. - <tag><tt>4.0.4</tt></tag> - The 4.0.4 update release. -</descrip> - -<sect>Pre-4.0 Development Versions -<p> - -This section is included mostly for historical reasons. - -The development leading up to 4.0 started from version 3.2A, but much of -it happened on a separate development branch. The "new design" work on -that development branch was first folded into the main development branch -at version 3.9N. Up until the XFree86 CVS was made publicly available, -all versions containing one or more letters were internal development -snapshots. The internal development snapshots continued through the -following sequence: 3.9N, 3.9Na, ..., 3.9Nz, 3.9P, 3.9Pa, ..., 3.9Py, -3.9.15, 3.9.15a, ..., 3.9.16, 3.9.16a, ..., 3.9.17, 3.9.17a, ..., 3.9.18, -3.9.18a, ..., 4.0. The 3.9.15, 3.9.16, etc versions were public pre-4.0 -beta releases. - -<sect>Version Numbering Scheme for XFree86 3.3.x. -<p> - -The version numbering format for XFree86 3.3.x releases is <tt>M.m.nx</tt>, -where <tt>M</tt> is the major version number (3), <tt>m</tt> is the -minor version number (3), <tt>n</tt> is the sub-minor version number, -and <tt>x</tt> is a letter. Between-release snapshots are indicated by -including <tt>x</tt>, a lower case letter. An exception to this scheme -was the 3.3.3.1 release, which was an update to the 3.3.3 release. - -<descrip> - <tag><tt>3.3</tt></tag> - The 3.3 release. - <tag><tt>3.3a</tt></tag> - The first post-3.3 development snapshot. - <tag><tt>3.3.1</tt></tag> - The 3.3.1 release. - <tag><tt>3.3.1a</tt></tag> - The first post-3.3.1 development snapshot. - <tag><tt>3.3.2</tt></tag> - The 3.3.2 release. - <tag><tt>3.3.2a</tt></tag> - The first post-3.3.2 development snapshot. - <tag><tt>3.3.3</tt></tag> - The 3.3.3 release. - <tag><tt>3.3.3a</tt></tag> - The first post-3.3.3 development snapshot. - <tag><tt>3.3.3.1</tt></tag> - The 3.3.3.1 release. - <tag><tt>3.3.3.1a</tt></tag> - The first post-3.3.3.1 development snapshot. - <tag><tt>3.3.4</tt></tag> - The 3.3.4 release. - <tag><tt>3.3.4a</tt></tag> - The first post-3.3.4 snapshot. - <tag><tt>3.3.5</tt></tag> - The 3.3.5 release. - <tag><tt>3.3.5a</tt></tag> - The first post-3.3.5 snapshot. - <tag><tt>3.3.6</tt></tag> - The 3.3.6 release. - <tag><tt>3.3.6a</tt></tag> - The first post-3.3.6 snapshot. -</descrip> - -<sect>Finding the XFree86 X Server Version From a Client +<sect>Finding the X.Org X Server Version From a Client <p> -The XFree86 X servers report a <tt>VendorRelease</tt> value that matches -the XFree86 version number. There have been some cases of releases where +The X.Org X servers report a <tt>VendorRelease</tt> value that matches +the X.Org version number. There have been some cases of releases where this value wasn't set correctly. The rules for interpreting this value as well as the known exceptions are outlined here. -For 3.3.x versions, the <tt>VendorRelease</tt> value is <tt>Mmnp</tt>. -That is, version <tt>M.m.n.p</tt> has <tt>VendorRelease</tt> set to -<tt>M * 1000 + m * 100 + n * 10 + p</tt>. -Exceptions to this are: The value wasn't incremented for the 3.3.3.1 -release, and for the 3.3.4 and 3.3.5 releases the value was incorrectly -set to <tt>Mmn</tt> -(<tt>M * 100 + m * 10 + n</tt>). -This was corrected for the 3.3.6 release. - -For versions 3.9.15 to 4.0.x, the <tt>VendorRelease</tt> value is -<tt>Mmnn</tt>. That is, version <tt>M.m.n</tt> has <tt>VendorRelease</tt> -set to -<tt>M * 1000 + m * 100 + n</tt>. -There have been no exceptions to this rule. - -For post-4.0.2 development and release versions using the new numbering +For post-6.7.0 development and release versions using the new numbering scheme, the <tt>VendorRelease</tt> value is <tt>MMmmPPsss</tt>. That is, version <tt>M.m.P.s</tt> has <tt>VendorRelease</tt> set to <tt>M * 10000000 + m * 100000 + P * 1000 + s</tt>. -Note: 4.0.3 and any other 4.0.x releases will continue with the -<tt>Mmnn</tt> scheme. The following is a code fragment taken from <tt>xdpyinfo.c</tt> that shows how the <tt>VendorRelease</tt> information can be interpreted. <tscreen><verb> - if (strstr(ServerVendor(dpy), "XFree86")) { + if (strstr(ServerVendor(dpy), "X.Org")) { int vendrel = VendorRelease(dpy); - printf("XFree86 version: "); - if (vendrel < 336) { - /* - * vendrel was set incorrectly for 3.3.4 and 3.3.5, so handle - * those cases here. - */ - printf("%d.%d.%d", vendrel / 100, - (vendrel / 10) % 10, - vendrel % 10); - } else if (vendrel < 3900) { - /* 3.3.x versions, other than the exceptions handled above */ - printf("%d.%d", vendrel / 1000, - (vendrel / 100) % 10); - if (((vendrel / 10) % 10) || (vendrel % 10)) { - printf(".%d", (vendrel / 10) % 10); - if (vendrel % 10) { - printf(".%d", vendrel % 10); - } - } - } else if (vendrel < 40000000) { - /* 4.0.x versions */ - printf("%d.%d", vendrel / 1000, - (vendrel / 10) % 10); - if (vendrel % 10) { - printf(".%d", vendrel % 10); - } - } else { - /* post-4.0.x */ - printf("%d.%d.%d", vendrel / 10000000, - (vendrel / 100000) % 100, - (vendrel / 1000) % 100); - if (vendrel % 1000) { - printf(".%d", vendrel % 1000); - } - } + printf("X.Org version: "); + printf("%d.%d.%d", vendrel / 10000000, + (vendrel / 100000) % 100, + (vendrel / 1000) % 100); + if (vendrel % 1000) { + printf(".%d", vendrel % 1000); + } } </verb></tscreen> diff --git a/sgml/XKB-Config.sgml b/sgml/XKB-Config.sgml index c1b352b..3503053 100644 --- a/sgml/XKB-Config.sgml +++ b/sgml/XKB-Config.sgml @@ -1,4 +1,6 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN"> +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN" [ +<!ENTITY % defs SYSTEM "defs.ent"> %defs; +]> <article> <title>The XKB Configuration Guide @@ -6,11 +8,10 @@ <date>25 November 2002 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/XKB-Config.sgml,v 1.4 2003/09/21 01:55:03 dawes Exp $ </ident> <abstract> -This document describes how to configure XFree86 XKB from a user's point +This document describes how to configure X11R&relvers; XKB from a user's point a few. It converts basic configuration syntax and gives also a few examples. </abstract> @@ -44,17 +45,17 @@ composition </itemize> <p> The proper rules file depends on your vendor. In reality, the commonest -file of rules is <tt>xfree86</tt>. For each rules file there is a description -file named <tt><vendor-rules>.lst</tt>, for instance <tt>xfree86.lst</tt> +file of rules is <tt>xorg</tt>. For each rules file there is a description +file named <tt><vendor-rules>.lst</tt>, for instance <tt>xorg.lst</tt> which is located in xkb configuration subdirectory <tt>rules</tt> (for example <tt>/etc/X11/xkb/rules</tt>). <sect1>Basic Configuration <p> Let's say you want to configure a PC style America keyboard with 104 -keys as described in <tt>xfree86.lst</tt>. It can be done by simply writing -several lines from below to you XFree86 configuration file (often -found as <tt>/etc/X11/XF86Config-4</tt> or <tt>/etc/X11/XF86Config</tt>): +keys as described in <tt>xorg.lst</tt>. It can be done by simply writing +several lines from below to you xorg.conf configuration file (previously known +as <tt>/etc/X11/XF86Config-4</tt> or <tt>/etc/X11/XF86Config</tt>): <tscreen><verb> Section "InputDevice" Identifier "Keyboard1" @@ -73,14 +74,14 @@ That means the default variant named <tt>basic</tt> is loaded. Of course, this can be also done at runtime using utility setxkbmap. Shell command loading the same keyboard mapping would look like: <tscreen><verb> -setxkbmap -rules xfree86 -model pc104 -layout us -option "" +setxkbmap -rules xorg -model pc104 -layout us -option "" </verb></tscreen> The configuration and the shell command would be very analogical for most other layouts (internationalized mappings). <sect1>Advanced Configuration <p> -Since XFree86 4.3.x you can use multi-layouts xkb configuration. +You can use multi-layouts xkb configuration. What does it mean? Basically it allows to load up to four different keyboard layouts at a time. Each such layout would reside in its own group. The groups (unlike complete keyboard remapping) can be @@ -105,7 +106,7 @@ EndSection Of course, this can be also done at runtime using utility setxkbmap. Shell command loading the same keyboard mapping would look like: <tscreen><verb> -setxkbmap -rules xfree86 -model logicordless -layout "us,cz,de" \ +setxkbmap -rules xorg -model logicordless -layout "us,cz,de" \ -option "grp:alt_shift_toggle" </verb></tscreen> @@ -135,7 +136,7 @@ key). <p> Analogically, the loading runtime will change to: <tscreen><verb> -setxkmap -rules xfree86 -model logicordless -layout "us,cz,de" \ +setxkmap -rules xorg -model logicordless -layout "us,cz,de" \ -variant ",bksl," -option "grp:alt_shift_toggle" </verb></tscreen> @@ -154,7 +155,7 @@ xkb components should be used to form the resulting keyboard mapping. This method is rather "brute force". You precisely need to know the structure and the meaning of all of used configuration components. <p> -This method also exposes all xkb configuration details directly into XFree86 +This method also exposes all xkb configuration details directly into xorg.conf configuration file which is a not very fortunate fact. In rare occasions it may be needed, though. So how does it work? @@ -185,7 +186,7 @@ Section "InputDevice" Identifier "Keyboard0" Driver "Keyboard" - Option "XkbKeycodes" "xfree86" + Option "XkbKeycodes" "xorg" Option "XkbTypes" "default" Option "XkbSymbols" "en_US(pc104)+de+swapcaps" Option "XkbGeometry" "pc(pc104)" @@ -193,7 +194,7 @@ Section "InputDevice" EndSection </verb></tscreen> -This configuration sets the standard XFree86 default interpretation of keyboard +This configuration sets the standard X server default interpretation of keyboard keycodes, sets the default modificator types. The symbol table is composed of extended US keyboard layout in its variant for pc keyboards with 104 keys plus all keys diff --git a/sgml/XKB-Enhancing.sgml b/sgml/XKB-Enhancing.sgml index 44bc10f..265f232 100644 --- a/sgml/XKB-Enhancing.sgml +++ b/sgml/XKB-Enhancing.sgml @@ -1,4 +1,4 @@ -<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN"> +<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN"> <article> <title>How to further enhance XKB configuration @@ -6,7 +6,6 @@ <date>25 November 2002 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/XKB-Enhancing.sgml,v 1.2 2003/02/25 19:31:02 dawes Exp $ </ident> <abstract> @@ -35,7 +34,7 @@ document. <p> Note that this document covers only enhancements which -are to be made to XFree86 version 4.3.x and above. +are to be made to XFree86 version 4.3 and X11R6.7.0 and above. <sect>The Basics @@ -117,7 +116,7 @@ concepts and used tricks. <p> <sect1>Levels And Groups <p> -Since XFree86 4.3.0 you can use <bf>multi-layout</bf> concept of xkb +Since XFree86 4.3.0 and X11R6.7.0 you can use <bf>multi-layout</bf> concept of xkb configuration. Though it is still in boundaries of xkb protocol and general ideas, the keymap designer must obey new rules when creating new maps. In exchange @@ -453,7 +452,7 @@ rules file looks like this: ! model = keycodes macintosh_old = macintosh ... - * = xfree86 + * = xorg ! model = symbols hp = +inet(%m) @@ -478,7 +477,7 @@ of equal sign ('<tt>=</tt>') results in. For example a (keyboard) model <tt>macintosh_old</tt> instructs xkb to take definitions of keycodes from file <tt>keycodes/macintosh</tt> while the rest of models (represented by a wild card '<tt>*</tt>') instructs it to take them from -file <tt>keycodes/xfree86</tt>. The wild card represents all possible +file <tt>keycodes/xorg</tt>. The wild card represents all possible values on the left side which were not found in any of the previous rules. The more specialized (more complete) rules have higher precedence than general ones, i.e. the more general rules supply reasonable default values. diff --git a/sgml/add.sh b/sgml/add.sh index 86bc7e8..d97b845 100644 --- a/sgml/add.sh +++ b/sgml/add.sh @@ -1,6 +1,6 @@ #!/bin/sh # -# $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/add.sh,v 1.3 2003/10/19 00:58:11 dawes Exp $ +# $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/add.sh,v 1.2 2003/10/18 13:29:34 dawes Exp $ # name=`basename $1 .sgml` sgmlfmt -f index $name.sgml | \ diff --git a/sgml/dps.sgml b/sgml/dps.sgml index 77b4341..795bb77 100644 --- a/sgml/dps.sgml +++ b/sgml/dps.sgml @@ -1,19 +1,38 @@ -<!doctype LINUXDOC PUBLIC "-//XFree86//DTD linuxdoc//EN" [ +<!doctype LINUXDOC PUBLIC "-//Xorg//DTD linuxdoc//EN" [ <!ENTITY % defs SYSTEM "defs.ent"> %defs; ]> <article> -<title>XFree86 and DPS -<author>Juliusz Chroboczek, <email/jch@xfree86.org/ -<date>27 February 2001</date> +<title>X and DPS +<author>Juliusz Chroboczek, <email/jch@pps.jussieu.fr/ +<date>27 February 2001, updated 25 March 2004</date> -<ident>$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/dps.sgml,v 1.2 2003/01/20 03:43:07 dawes Exp $</ident> +<ident> +Updated by Jim Gettys. +$Id$ +</ident> <toc> <sect>Introduction +<p> Note that DPS is now obsolete. +<p> +At the time when I started this project, there was no decent rendering interface for X11 other than DPS. +<p> +Since then, there has been a large amount of work on a simple and clean X server extension, Xrender, which provides the basis for just such an interface. +<p> +Rendering libraries that are being built above Xrender include Xft, +a font rendering library built on FreeType; +Cairo, a geometry rendering library that provides PostScript-like +rendering primitives but with intrinsic support for Porter-Duff +compositing (transparency); Pango, a high-level typesetting library. +<p> +If your application uses DPS, please consider porting it to the above libraries. +See <url url="http://dps.sourceforge.net" name="the DPS extension site"> +for more details + <p>Display Postscript (or DPS for short) is a rendering extension for X11. DPS is slightly atypical in that it is based on <it/code mobility/, the ability to send executable code from client to server. @@ -23,7 +42,7 @@ line to be drawn. <p>This document does not aim at teaching programming with DPS; it is only a summary description of the DPS support code included with -XFree86. More information about DPS, including a DPS bibliography, is +X11&relvers;. More information about DPS, including a DPS bibliography, is available from <url url="http://dps.sourceforge.net" name="the DPS extension site">. @@ -40,7 +59,7 @@ side may consist either of an X server extension, or of a client-side process known as the ``DPS agent.'' In this latter case, the term ``server-side'' is somewhat misleading. -At the time of writing, only the client side is included with XFree86; +At the time of writing, only the client side is included with X11R&relvers;; the server side must be obtained separately. Please see <ref id="sec:server-side" name="server side"> later in this document for more information. @@ -49,7 +68,7 @@ more information. <p>The DPS client side consists of four libraries and a number of basic tools for programming and configuration; these are all included -with XFree86. +with X11&relvers;. <sect1>Libraries @@ -82,7 +101,7 @@ summary Scrolling Widget documentation is available in the <tt/doc/ subdirectory of the <tt/DPS.tar.gz/ file, available from <url url="ftp://dps.sourceforge.net/pub/dps/DPS.tar.gz">. -The source code for <tt/libdpstkXm/ is included with XFree86; however, +The source code for <tt/libdpstkXm/ is included with X11R&relvers;; however, as it depends on Motif, this library is not built by default. A GTK-based library providing some of the functionality of <tt/libdpstkXm/ is available from @@ -97,7 +116,7 @@ code on DPS events; with this addition, all programs that link with <tt/libdps/ need to link with <tt/libXt/, whether they use Xt or not. This state of affairs is unfortunately true of the version of -<tt/libdps/ included with XFree86. We are currently considering +<tt/libdps/ included with X11R&relvers;. We are currently considering various solutions to this problem (including the use of weak linker symbols or splitting off the guilty functions into a separate library). @@ -122,7 +141,7 @@ pre-tokenised form to the DPS extension. <tt/Pswrap/ is documented in <sect1>Sample clients -<p>XFree86 contains three sample DPS clients, <tt/dpsinfo/, +<p>X11R&relvers; contains three sample DPS clients, <tt/dpsinfo/, <tt/dpsexec/ and <tt/texteroids/. They are documented in their respective manual pages. diff --git a/sgml/fonts.sgml b/sgml/fonts.sgml index 7242abd..92e5254 100644 --- a/sgml/fonts.sgml +++ b/sgml/fonts.sgml @@ -1,24 +1,23 @@ -<!doctype LINUXDOC PUBLIC "-//XFree86//DTD linuxdoc//EN" [ +<!doctype LINUXDOC PUBLIC "-//Xorg//DTD linuxdoc//EN" [ <!ENTITY % defs SYSTEM "defs.ent"> %defs; ]> <article> -<title>Fonts in XFree86 -<author>Juliusz Chroboczek, <email/jch@xfree86.org/ -<date>17 November 2003</date> +<title>Fonts in X11R6.7 +<author>Juliusz Chroboczek, <email/jch@pps.jussieu.fr/ +<date>25 March 2004</date> <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/fonts.sgml,v 1.24 2003/12/20 19:30:35 dawes Exp $ </ident> <toc> <sect>Introduction -<p>This document describes the support for fonts in XFree86. <ref +<p>This document describes the support for fonts in X11R6.7. <ref id="sec:installing" name="Installing fonts"> is aimed at the -casual user wishing to install fonts in XFree86; the rest of the +casual user wishing to install fonts in X11R6.7 or XFree86; the rest of the document describes the font support in more detail. We assume some familiarity with digital fonts. If anything is not @@ -28,10 +27,10 @@ information. <sect1>Two font systems -<p>XFree86 includes two font systems: the core X11 fonts system, which +<p>X includes two font systems: the original core X11 fonts system, which is present in all implementations of X11, and the Xft fonts system, -which is not currently distributed with implementations of X11 that -are not based on XFree86 but will hopefully be included by them in +which may not be distributed with implementations of X11 that +are not based on X11&relvers; but will hopefully be included by them in the future The core X11 fonts system is directly derived from the fonts system @@ -49,7 +48,7 @@ installed system-wide for displaying documents with embedded fonts. Xft is not compatible with the core fonts system: usage of Xft requires making fairly extensive changes to toolkits (user-interface -libraries). While XFree86 will continue to maintain the core fonts +libraries). While X.org will continue to maintain the core fonts system, toolkit authors are encouraged to switch to Xft as soon as possible. @@ -62,14 +61,14 @@ system to access newly-installed fonts. <p>Xft has no configuration mechanism itself, rather it relies upon the fontconfig library to configure and customize fonts. That library -is not specific to XFree86 or indeed on any particular font output +is not specific to X11R&relvers; or indeed on any particular font output mechanism. This discussion describes how fontconfig, rather than Xft, works. <sect2>Installing fonts in Xft <p>Fontconfig looks for fonts in a set of well-known directories that -include all of XFree86's standard font directories +include all of X11R6.7's standard font directories (`<tt>/usr/X11R6/lib/X11/lib/fonts/*</tt>') by default) as well as a directory called `<tt>.fonts/</tt>' in the user's home directory. Installing a font for use by Xft applications is as simple @@ -137,7 +136,7 @@ Anti-aliasing can be disabled for all fonts by the following incantation: </match> </verb></tscreen> -Xft supports sub-pixel rasterisation on LCD displays. XFree86 should +Xft supports sub-pixel rasterisation on LCD displays. X11R67 should automatically enable this feature on laptops and when using an LCD monitor connected with a DVI cable; you can check whether this was done by typing @@ -196,8 +195,8 @@ anti-aliasing in case it was disabled by your Xft configuration file. <sect2>Troubleshooting <label id="sec:troubleshooting-xft"> <p>If some Xft-based applications don't seem to notice the changes you -are making to your configuration files, they may be linked against the -XFree86 4.2 version of Xft. In order to fix the problem, you should +are making to your configuration files, they may be linked against an +old version of Xft. In order to fix the problem, you should relink them against a current version of Xft; on most systems, it is enough to install the current version of the Xft and Fontconfig libraries. @@ -217,9 +216,9 @@ including it in the <it/font path/. <sect2>Installing bitmap fonts -<p>The XFree86 server can use bitmap fonts in both the cross-platform +<p>The X11R6.7 server can use bitmap fonts in both the cross-platform BDF format and the somewhat more efficient binary PCF format. -(XFree86 also supports the obsolete SNF format.) +(X11R6.7 also supports the obsolete SNF format.) Bitmap fonts are normally distributed in the BDF format. Before installing such fonts, it is desirable (but not absolutely necessary) @@ -251,7 +250,7 @@ server font path"> below. <sect2>Installing scalable fonts -<p>The XFree86 server supports scalable fonts in four formats: +<p>The X11R6.7 server supports scalable fonts in four formats: Type 1, Speedo, TrueType and CIDFont. This section only applies to the former three; for information on CIDFonts, please see <ref id="sec:cid-fonts" name="Installing CIDFonts"> later in this @@ -294,7 +293,7 @@ called Munhwa-Regular--UniKS-UCS2-H </verb></tscreen> -The CIDFont code in XFree86 requires a very rigid directory +The CIDFont code in X11R6.7 requires a very rigid directory structure. The main directory must be called `<tt/CID/' (its location defaults to `<tt>/usr/X11R6/lib/X11/fonts/CID</tt>' but it may be located anywhere), and it should contain a subdirectory for every CID @@ -357,8 +356,7 @@ For best results, scalable fonts should appear in the font path before the bitmap fonts; this way, the server will prefer bitmap fonts to scalable fonts when an exact match is possible, but will avoid scaling bitmap fonts when a scalable font can be used. (The `<tt/:unscaled/' -hack, while still supported, should no longer be necessary in XFree86 -4.0 and later.) +hack, while still supported, should no longer be necessary in X11R&relvers;.) You may check the font path of the running server by typing the command <tscreen><verb> @@ -388,7 +386,7 @@ url="xset.1.html"> manual page. <p>The default font path (the one used just after server startup or after `<tt/xset fp default/') is specified in the X server's -`<tt/XF86Config/' file. It is computed by appending all the +`<tt/xorg.conf/' file. It is computed by appending all the directories mentioned in the `<tt/FontPath/' entries of the `<tt/Files/' section in the order in which they appear. <tscreen><verb> @@ -397,8 +395,8 @@ FontPath "/usr/local/fonts/Type1" FontPath "/usr/local/fonts/bitmap" </verb></tscreen> -For more information, please consult the <htmlurl name="XF86Config(5)" -url="XF86Config.5.html"> manual page. +For more information, please consult the <htmlurl name="xorg.conf(5)" +url="xorg.conf.5.html"> manual page. <sect2>Troubleshooting <label id="sec:troubleshooting-core"> @@ -409,13 +407,13 @@ usually runs as root, beware of NFS-mounted font directories). If this doesn't help, it is quite possible that you are trying to use a font in a format that is not supported by your server. -XFree86 supports the BDF, PCF, SNF, Type 1, Speedo, TrueType, OpenType -and CIDFont font formats. However, not all XFree86 servers come with -all the font backends configured in. +X11R6.7 supports the BDF, PCF, SNF, Type 1, Speedo, TrueType, OpenType +and CIDFont font formats. However, not all X11R6.7 or XFree86 servers +come with all the font backends configured in. -On most platforms, the XFree86 servers are <it/modular/: the font +On most platforms, the X11R6.7 servers are <it/modular/: the font backends are included in modules that are loaded at runtime. The -modules to be loaded are specified in the `<tt/XF86Config/' file using +modules to be loaded are specified in the `<tt/xorg.conf/' file using the `<tt/Load/' directive: <tscreen><verb> Load "type1" @@ -423,7 +421,7 @@ Load "type1" If you have trouble installing fonts in a specific format, you may want to check the server's log file in order to see whether the relevant modules are properly loaded. The list of font modules -distributed with XFree86 is as follows: +distributed with X11R6.7 is as follows: <itemize> <item> <tt/"bitmap"/: bitmap fonts (`<tt/*.bdf/', `<tt/*.pcf/' and `<tt/*.snf/'); @@ -439,7 +437,7 @@ Type 1 fonts (`<tt/*.pfa/' and `<tt/*.pfb/'); Please note that the argument of the `<tt/Load/' directive is case-sensitive. -<sect>Fonts included with XFree86 +<sect>Fonts included with X11R6.7 <sect1>Standard bitmap fonts @@ -449,7 +447,7 @@ of Courier, Times, Helvetica and some members of the Lucida family. In the SI, these fonts are provided in the ISO 8859-1 encoding (ISO Latin Western-European). -In XFree86, a number of these fonts are provided in Unicode-encoded +In X11R6.7, a number of these fonts are provided in Unicode-encoded font files instead. At build time, these fonts are split into font files encoded according to legacy encodings, a process which allows us to provide the standard fonts in a number of regional encodings @@ -530,7 +528,7 @@ may be useful for improved presentation of text. <sect1>Standard scalable fonts -<p>XFree86 includes all the scalable fonts distributed with X11R6. +<p>X11R6.7 includes all the scalable fonts distributed with X11R6. <sect2>Standard Type 1 fonts @@ -555,7 +553,7 @@ and reside in the font files /usr/X11R6/lib/X11/fonts/Type1/UT*.pfa </verb></tscreen> -Finally, XFree86 also comes with Type 1 versions of Bitstream +Finally, X11R6.7 also comes with Type 1 versions of Bitstream Courier and Charter. These fonts have XLFD <tscreen><verb> -bitstream-courier-*-*-normal--0-0-0-0-m-0-iso8859-1 @@ -568,7 +566,7 @@ and reside in the font files <sect2>Standard Speedo fonts -<p>XFree86 includes Speedo versions of the Bitstream Courier and +<p>X11R6.7 includes Speedo versions of the Bitstream Courier and Charter fonts. In order to use these fonts, you should ensure that your X server is loading the `<tt/Speedo/' font backend; see <ref id="sec:troubleshooting-core" name="Troubleshooting">. @@ -586,7 +584,7 @@ and reside in the font files <sect1>The Bigelow & Holmes Luxi family -<p>XFree86 includes the <it/Luxi/ family of scalable fonts, in both +<p>X11R6.7 includes the <it/Luxi/ family of scalable fonts, in both TrueType and Type 1 format. This family consists of the fonts <it/Luxi Serif/, with XLFD <tscreen><verb> @@ -640,11 +638,11 @@ For more information, please contact An earlier version of the Luxi fonts was made available under the name <em/Lucidux/. This name should no longer be used due to trademark uncertainties, and all traces of the <em/Lucidux/ name have been -removed from XFree86. +removed from X11R6.7. <sect>More about core fonts <label id="sec:more-core"> -<p>This section describes XFree86-specific enhancements to the core +<p>This section describes X11R6.7-specific enhancements to the core X11 fonts system. <sect1>Core fonts and internationalisation <label id="sec:internationalisation"> @@ -722,7 +720,7 @@ files. Please see the <htmlurl name="mkfontdir(1)" url="mkfontdir.1.html"> manual page for more details. A number of encoding files for common encodings are included with -XFree86. Information on writing new encoding files can be found in +X11R6.7. Information on writing new encoding files can be found in <ref id="sec:format-encoding-directory-files" name="Format of encodings directory files"> and <ref id="sec:format-encoding-files" name="Format of encoding files"> later in this document. @@ -1093,7 +1091,7 @@ encodings, but instead uses its own database of encodings. Since the functionalities for CJKV support introduced by X-TT have been merged into the new <it/FreeType/ backend, the X-TT backend will be -removed from XFree86's tree near the future. Therefore, the use of +removed from X11R6.7's tree near the future. Therefore, the use of <it/FreeType/ backend is preferred over the X-TT backend. General information on X-TrueType may be found at <url @@ -1258,7 +1256,7 @@ have the last two fields of their XLFD set to `<tt/iso10646-1/'. <sect>References -<p>XFree86 comes with extensive documentation in the form of manual +<p>X11R6.7 comes with extensive documentation in the form of manual pages and typeset documents. Before installing fonts, you really should read the <htmlurl name="fontconfig(3)" url="fontconfig.3.html"> and <htmlurl name="mkfontdir(1)" url="mkfontdir.1.html"> manual pages; other @@ -1270,10 +1268,10 @@ url="showfont.1.html">. In addition, you may want to read the X Logical Font Description document, by Jim Flowers, which is provided in the file `<tt>xc/doc/xlfd.PS.Z</tt>'. -The latest released version of the XFree86 documentation (including -this document and all manual pages) is available as -<url name="current XFree86 documentation" - url="http://www.xfree86.org/current/">. +The latest released version of the X11R6.7 documentation (including +this document and all manual pages) can be found from +<url name="current X11R6.7 documentation" + url="http://wiki.x.org/">. The <url name="comp.fonts FAQ" url="http://www.netmeg.net/faq/computers/fonts/">, diff --git a/sgml/index.post b/sgml/index.post index 360a5e0..bfc866e 100644 --- a/sgml/index.post +++ b/sgml/index.post @@ -27,5 +27,5 @@ Other: </article> <!-- -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/index.post,v 1.3 2003/03/19 01:49:28 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/index.post,v 1.2 2000/03/21 19:57:10 dawes Exp $ --> diff --git a/sgml/index.pre b/sgml/index.pre index eee20af..65ce2d7 100644 --- a/sgml/index.pre +++ b/sgml/index.pre @@ -6,12 +6,12 @@ <article> <!-- Title information --> -<title>Documentation for XFree86™ version &relvers; -<author>The XFree86 Project, Inc -<date>29 February 2004 +<title>Documentation for the X Window System Version 11 Release &relvers; (X11R&relvers;) +<author>The X.Org Foundation +<date>6 April 2004 <!-- -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/index.pre,v 1.24 2004/02/24 03:41:40 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/index.pre,v 1.23 2004/02/15 02:16:49 dawes Exp $ --> <p> diff --git a/sgml/mdefs.pre b/sgml/mdefs.pre index 2c6993b..7ace207 100644 --- a/sgml/mdefs.pre +++ b/sgml/mdefs.pre @@ -1,4 +1,4 @@ -<!-- $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/mdefs.cpp,v 1.2 2003/03/19 01:49:28 dawes Exp $ --> +<!-- $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/mdefs.cpp,v 1.1 2000/03/21 19:57:11 dawes Exp $ --> <!-- entity definitions for man pages --> diff --git a/specs/BDF/bdf.ms b/specs/BDF/bdf.ms index 328e345..911ab42 100644 --- a/specs/BDF/bdf.ms +++ b/specs/BDF/bdf.ms @@ -6,9 +6,9 @@ \s+1\fBVersion 2.1\fP\s-1 -X Consortium Standard +X Window System Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 3 Copyright 1984, 1987, 1988 Adobe Systems, Inc. .sp 1 diff --git a/specs/CTEXT/ctext.tbl.ms b/specs/CTEXT/ctext.tbl.ms index 64b3f79..02d1013 100644 --- a/specs/CTEXT/ctext.tbl.ms +++ b/specs/CTEXT/ctext.tbl.ms @@ -1,40 +1,12 @@ +.\" $XdotOrg$ .\" Use tbl and -ms -.\" -.\" $XFree86: xc/doc/specs/CTEXT/ctext.tbl.ms,v 1.2 2000/12/11 19:39:40 dawes Exp $ -.\" -.\" --- bP --- bulleted paragraph macro -.\" -.de bP -.IP \(bu 4 -.. -.\" -.\" --- cT --- centered title; centers $1, adds TOC entry unless $2 is "no" -.\" -.de cT -\\& \" filler so that the following .sp really leaves a space -.sp 1 -.ce 1 -\\s+1\\fB\\$1\\fP\\s-1 -.sp 1 -.if !'\\$2'no' \{\ -.XS \\n(PN -\\$1 -.XE -\} -.. .sp 8 -.ce 9 +.ce 5 \s+2\fBCompound Text Encoding\fP\s-2 .sp 6p -Version 1.1.xf86.1 -XFree86 4.0.2 -XFree86, Inc. -.sp 6p -.I "based on" -.sp 6p Version 1.1 X Consortium Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 Robert W. Scheifler .sp 2 .LP @@ -249,7 +221,7 @@ _ .sp 4p _ .sp 6p -04/02 94 7-bit ASCII graphics (ANSI X3.4-1968), +4/02 94 7-bit ASCII graphics (ANSI X3.4-1968), Left half of ISO 8859 sets 04/09 94 Right half of JIS X0201-1976 (reaffirmed 1984), 8-Bit Alphanumeric-Katakana Code @@ -265,16 +237,10 @@ _ 04/08 96 Right half of ISO 8859-8, Latin/Hebrew alphabet 04/12 96 Right half of ISO 8859-5, Latin/Cyrillic alphabet 04/13 96 Right half of ISO 8859-9, Latin alphabet No. 5 -05/06 96 Right half of ISO 8859-10, Latin alphabet No. 6 -05/09 96 Right half of ISO 8859-13, Latin alphabet No. 7 (Baltic Rim) -05/15 96 Right half of ISO 8859-14, Latin alphabet No. 8 (Celtic) -06/02 96 Right half of ISO 8859-15, Latin alphabet No. 9 -06/06 96 Right half of ISO 8859-16, Latin alphabet No. 10 .sp 6p 04/01 94\u\s-22\s+2\d GB2312-1980, China (PRC) Hanzi -04/02 94\u\s-22\s+2\d JIS X0208-1983/1990, Japanese Graphic Character Set +04/02 94\u\s-22\s+2\d JIS X0208-1983, Japanese Graphic Character Set 04/03 94\u\s-22\s+2\d KS C5601-1987, Korean Graphic Character Set -04/02 94\u\s-22\s+2\d JIS X0212-1990, Supplementary Japanese Graphic Character Set .sp 6p _ .TE @@ -335,33 +301,9 @@ for example, they may contain octets in the C0 and C1 ranges, including 00/00, and octets comprising a given character may differ in their most significant bit. .LP -[Except for UTF-8, -ISO-registered ``other coding systems'' are not used in Compound Text; +[ISO-registered ``other coding systems'' are not used in Compound Text; extended segments are the only mechanism for non-2022 encodings.] .NH 1 -The UTF-8 encoding -.LP -Unicode characters that are not contained in one of the approved standard -encodings can be encoded using the UTF-8 encoding. The following escape -sequences are used: -.RS -.TS -l l. -01/11 02/05 04/07 switch into UTF-8 mode -01/11 02/05 04/00 return from UTF-8 mode -.TE -.RE -.LP -The first is the ISO registered sequence for UTF-8 (ISO-IR-196), the second -is the ISO-2022 ``standard return'' sequence. While in UTF-8 mode, the UTF-8 -encoding replaces the currently designated GL and GR encodings. After return -from UTF-8 mode, the previously designated GL and GR encodings are -reactivated. -.LP -[This is the only ``other coding system'' used in Compound Text.] -.LP -[This is an XFree86 extension introduced in XFree86 4.0.2.] -.NH 1 Directionality .LP If desired, horizontal text direction can be indicated using the following @@ -434,16 +376,9 @@ ISO8859-6 ISO 8859-6 Latin/Arabic alphabet ISO8859-7 ISO 8859-7 Latin/Greek alphabet ISO8859-8 ISO 8859-8 Latin/Hebrew alphabet ISO8859-9 ISO 8859-9 Latin alphabet No. 5 -ISO8859-10 ISO 8859-10 Latin alphabet No. 6 -ISO8859-13 ISO 8859-13 Latin alphabet No. 7 (Baltic Rim) -ISO8859-14 ISO 8859-14 Latin alphabet No. 8 (Celtic) -ISO8859-15 ISO 8859-15 Latin alphabet No. 9 -ISO8859-16 ISO 8859-16 Latin alphabet No. 10 JISX0201.1976-0 JIS X0201-1976 (reaffirmed 1984) 8-bit Alphanumeric-Katakana Code GB2312.1980-0 GB2312-1980, GL encoding China (PRC) Hanzi JISX0208.1983-0 JIS X0208-1983, GL encoding Japanese Graphic Character Set -JISX0208.1990-0 JIS X0208-1990, GL encoding Japanese Graphic Character Set -JISX0212.1990-0 JIS X0212-1990, GL encoding Supplementary Japanese Graphic Character Set KSC5601.1987-0 KS C5601-1987, GL encoding Korean Graphic Character Set .sp 6p _ @@ -513,28 +448,3 @@ If a Compound Text string does not match the specification here (e.g., uses undefined control characters, or undefined control sequences, or incorrectly formatted extended segments), it is best to treat the entire string as invalid, except as indicated by a version control sequence. -.bp -.\" Set registers to number the appendixes A.1, B.1, C.1, ... -.nr H1 0 -.af H1 A -.cT "Appendix A" no -.nH 1 "Revision History" -.LP -This appendix describes the revision history of this document and -summarizes the incompatibilities between this and earlier versions. -.nH 2 "Version 1.1" -.LP -Version 1.1 is the original X11 specification. -.nH 2 "Version 1.1.xf86.1" -.LP -Version 1.1.xf86.1 was released with XFree86 4.0.2 in December 2000. -It adds the following changes: -.bP -Added ISO 8859-10,13,14,15,16 and JIS X0212 to the list of standard -encodings. Mention the 1990 revision of JIS X0208 as an alternative to -the 1983 edition. -.bP -Added ISO8859-10, ISO8859-13, ISO8859-14, ISO8859-15, ISO8859-16, -JISX0208.1990-0, JISX0212.1990-0 to the list of font charsets. -.bP -The section about UTF-8 encoding was added. diff --git a/specs/FSProtocol/protocol.ms b/specs/FSProtocol/protocol.ms index 613e8c1..6945233 100644 --- a/specs/FSProtocol/protocol.ms +++ b/specs/FSProtocol/protocol.ms @@ -1,4 +1,5 @@ .\" $Xorg: protocol.ms,v 1.3 2000/08/17 19:42:07 cpqbld Exp $ +.\" $XdotOrg$ .\" Use tbl, -ms, and macros.t .EH '''' .OH '''' @@ -12,9 +13,9 @@ \s+3\fBThe X Font Service Protocol\fP\s-3 .sp \fBVersion 2.0\fP -\fBX Consortium Standard\fR +\fBX Window System Standard\fR .sp -\fBX Version 11, Release 6.4\fR +\fBX Version 11, Release 6.7\fR .sp 6 Jim Fulton Network Computing Devices, Inc. @@ -63,8 +64,8 @@ in this Software without prior written authorization from the X Consortium. .ps 11 .nr PS 11 .bp 1 -.EH '\fBX Font Service Protocol\fP''\fBX11, Release 6.4\fP' -.OH '\fBX Font Service Protocol\fP''\fBX11, Release 6.4\fP' +.EH '\fBX Font Service Protocol\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Font Service Protocol\fP''\fBX11, Release 6.7\fP' .EF ''\fB\\\\n(PN\fP'' .OF ''\fB\\\\n(PN\fP'' .NH 1 @@ -76,7 +77,7 @@ Introduction The management of fonts in large, heterogeneous environments is one of the hardest aspects of using the X Window System.* .FS -* \fIX Window System\fP is a trademark of X Consortium, Inc. +* \fIX Window System\fP is a trademark of The Open Group. .FE Multiple formats and the lack of a consistent mechanism for exporting font data to all displays on a network diff --git a/specs/ICCCM/icccm.ms b/specs/ICCCM/icccm.ms index 1a26c09..f21c84b 100644 --- a/specs/ICCCM/icccm.ms +++ b/specs/ICCCM/icccm.ms @@ -1,10 +1,5 @@ .\" $Xorg: icccm.ms,v 1.3 2000/08/17 19:42:08 cpqbld Exp $ -.\" -.\" -.\" -.\" -.\" $XFree86: xc/doc/specs/ICCCM/icccm.ms,v 1.3 2001/01/17 16:57:41 dawes Exp $ -.\" +.\" $XdotOrg$ .\" Use tbl, eqn, -ms, and macros.t .\" @(#)icccm.ms 1.50 16 Apr 1994 14:13:55 .EH '''' @@ -45,19 +40,11 @@ .B \s+2Inter-Client Communication Conventions Manual\s0 -Version 2.0.xf86.1 - -XFree86 4.0.2 - -XFree86, Inc. - -.I "based on" - Version 2.0 X Consortium Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 .R .ce 0 .sp 6 @@ -76,7 +63,7 @@ X Version 11, Release 6.4 .nr PS 9 .sp 8 .LP -X Window System is a trademark of X Consortium, Inc. +X Window System is a trademark of The Open Group .LP .LP Copyright \(co 1988, 1991, 1993, 1994 @@ -228,8 +215,8 @@ John Interrante John Thomas .De .bp 1 .af PN 1 -.EH '\fBInter-Client Communication Conventions\fP''\fBX11, Release 6.4\fP' -.OH '\fBInter-Client Communication Conventions\fP''\fBX11, Release 6.4\fP' +.EH '\fBInter-Client Communication Conventions\fP''\fBX11, Release 6.7\fP' +.OH '\fBInter-Client Communication Conventions\fP''\fBX11, Release 6.7\fP' .EF ''\fB % \fP'' .OF ''\fB % \fP'' .nH 1 Introduction @@ -1403,9 +1390,6 @@ T} USER TEXT T{ The name of the user running the owner T} -UTF8_STRING TEXT T{ -UTF-8 text -T} .sp 6p _ .TE @@ -1682,7 +1666,6 @@ T} PIXMAP 32 Fixed-size SPAN 32 Fixed-size STRING 8 Zero -UTF8_STRING 8 Zero WINDOW 32 Fixed-size .sp 6p _ @@ -1717,7 +1700,7 @@ The type would not actually be TEXT; it would be STRING or some other ATOM naming the encoding chosen by the owner. .LP STRING as a type or a target specifies the ISO Latin-1 character set plus the -control characters TAB (hex 09) and NEWLINE (hex 0A). +control characters TAB (octal 11) and NEWLINE (octal 12). The spacing interpretation of TAB is context dependent. Other ASCII control characters are explicitly not included in STRING at the present time. @@ -1725,9 +1708,6 @@ at the present time. COMPOUND_TEXT as a type or a target specifies the Compound Text interchange format; see the \fICompound Text Encoding\fP. .LP -UTF8_STRING as a type or a target specifies an UTF-8 encoded string, with -NEWLINE (U+000A, hex 0A) as end-of-line marker. -.LP There are some text objects where the source or intended user, as the case may be, does not have a specific character set for the text, but instead merely requires a zero-terminated sequence of bytes with no @@ -1750,9 +1730,9 @@ way to treat them as the same. Thus no character-set based property type is suitable. .NE .LP -Type STRING, COMPOUND_TEXT, UTF8_STRING, and C_STRING properties will -consist of a list of elements separated by null characters; other encodings -will need to specify an appropriate list format. +Type STRING, COMPOUND_TEXT, and C_STRING properties will consist of a list +of elements separated by null characters; other encodings will need to +specify an appropriate list format. .nH 3 "INCR Properties" .LP Requestors may receive a property of type INCR\** @@ -5221,10 +5201,11 @@ delim off .DE or to .DS - Registry - X Consortium - 201 Broadway - Cambridge, MA 02139-1955 + The X.Org Group -- X11 Registry + c/o Ienup Sung + Sun Microsystems, Inc. + 4150 Network Circle, MS SJC07-201 + Santa Clara, CA 95054 USA .DE Electronic mail will be acknowledged upon receipt. Please allow up to 4 diff --git a/specs/ICCCM/indexmacros.t b/specs/ICCCM/indexmacros.t index d7853fd..0520638 100644 --- a/specs/ICCCM/indexmacros.t +++ b/specs/ICCCM/indexmacros.t @@ -1,3 +1,3 @@ -.eh '\s+1\fBInter-Client Communication Conventions\fP''\fBX11, Release 6.4\fP\s-1' -.oh '\s+1\fBInter-Client Communication Conventions\fP''\fBX11, Release 6.4\fP\s-1' +.eh '\s+1\fBInter-Client Communication Conventions\fP''\fBX11, Release 6.7\fP\s-1' +.oh '\s+1\fBInter-Client Communication Conventions\fP''\fBX11, Release 6.7\fP\s-1' .so index.pageno diff --git a/specs/ICE/ICElib.ms b/specs/ICE/ICElib.ms index 36540f4..b7f4046 100644 --- a/specs/ICE/ICElib.ms +++ b/specs/ICE/ICElib.ms @@ -1,4 +1,5 @@ .\" $Xorg: ICElib.ms,v 1.3 2000/08/17 19:42:09 cpqbld Exp $ +.\" $XdotOrg$ .\" .\" Use tbl, -ms, and macros.t .\" @@ -28,7 +29,7 @@ Version 1.0 .sp X Consortium Standard .sp -X Version 11, Release 6.4 +X Version 11, Release 6.7 .AU Ralph Mor .AI @@ -60,10 +61,10 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 5 -X Window System is a trademark of X Consortium, Inc. +X Window System is a trademark of The Open Group. .bp -.EH '\fBInter-Client Exchange Library\fP''\fBX11, Release 6.4\fP' -.OH '\fBInter-Client Exchange Library\fP''\fBX11, Release 6.4\fP' +.EH '\fBInter-Client Exchange Library\fP''\fBX11, Release 6.7\fP' +.OH '\fBInter-Client Exchange Library\fP''\fBX11, Release 6.7\fP' .bp 1 .EF ''\- \\\\n(PN \-'' .OF ''\- \\\\n(PN \-'' diff --git a/specs/ICE/ice.ms b/specs/ICE/ice.ms index 144734a..3d4295d 100644 --- a/specs/ICE/ice.ms +++ b/specs/ICE/ice.ms @@ -1,4 +1,5 @@ .\" Use tbl macros.t ice.ms | troff -ms +.\" $XdotOrg$ .\" .\" TODO: .\" Think about connector/listener originator/answerer terminology. @@ -88,7 +89,7 @@ Version 1.1 .sp X Consortium Standard .sp -X Version 11, Release 6.4 +X Version 11, Release 6.7 @@ -150,9 +151,9 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 5 -X Window System is a trademark of X Consortium, Inc. -.EH '\fBInter-Client Exchange Protocol\fP''\fBX11, Release 6.4\fP' -.OH '\fBInter-Client Exchange Protocol\fP''\fBX11, Release 6.4\fP' +X Window System is a trademark of The Open Group. +.EH '\fBInter-Client Exchange Protocol\fP''\fBX11, Release 6.7\fP' +.OH '\fBInter-Client Exchange Protocol\fP''\fBX11, Release 6.7\fP' .bp 1 .EF ''\fB % \fP'' .OF ''\fB % \fP'' diff --git a/specs/SIAddresses/IPv6.txt b/specs/SIAddresses/IPv6.txt new file mode 100644 index 0000000..2d76f22 --- /dev/null +++ b/specs/SIAddresses/IPv6.txt @@ -0,0 +1,11 @@ +ServerInterpreted address definition for type "IPv6": + +The X.org Architecture Task Force reserves the ServerInterpreted +address type of "IPv6" for use with IPv6 literal address formats. +The syntax for the value will be defined as specified in RFC 3513 +and the IETF RFC to be published based on the current draft at +http://www.ietf.org/internet-drafts/draft-ietf-ipv6-scoping-arch-00.txt +This address type specification will be formally issued once the +IETF IPv6 Working Group issues the corresponding RFC. + +Version 0.9, March 2004 diff --git a/specs/SIAddresses/README b/specs/SIAddresses/README new file mode 100644 index 0000000..e6a3ff0 --- /dev/null +++ b/specs/SIAddresses/README @@ -0,0 +1,6 @@ +$XdotOrg$ + +This directory contains the specifications of address types for the +ServerInterpreted address family used in the ChangeHost and ListHosts +requests in the X11 Protocol. See Chapter 9 of the X11 Protocol spec +for more information. diff --git a/specs/SIAddresses/hostname.txt b/specs/SIAddresses/hostname.txt new file mode 100644 index 0000000..498fb01 --- /dev/null +++ b/specs/SIAddresses/hostname.txt @@ -0,0 +1,11 @@ +ServerInterpreted address definition for type "hostname": + +A ServerInterpreted address with type "hostname" shall have a value +representing a hostname as defined in IETF RFC 2396. Due to Mobile IP +and dynamic DNS, the name service should be consulted at connection +authentication time. Clients supporting Internationalized Domain +Names must convert to ASCII Compatible Encoding as specified in the +relevant IETF RFC's before use in the X11 protocol. Note that this +definition of hostname does not allow use of literal IP addresses. + +Version 1.0, March 2004 diff --git a/specs/SM/SMlib.ms b/specs/SM/SMlib.ms index 38fb64c..5f1c81a 100644 --- a/specs/SM/SMlib.ms +++ b/specs/SM/SMlib.ms @@ -1,4 +1,5 @@ .\" $Xorg: SMlib.ms,v 1.3 2000/08/17 19:42:19 cpqbld Exp $ +.\" $XdotOrg$ .\" .\" Use tbl, -ms, and macros.t .\" edited for DP edits and code consistency w/ core protocol/xlib 4/18/96 @@ -28,7 +29,7 @@ Version 1.0 .sp X Consortium Standard .sp -X Version 11, Release 6.4 +X Version 11, Release 6.7 .AU Ralph Mor .AI @@ -60,11 +61,11 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 3 -X Window System is a trademark of X Consortium, Inc. +X Window System is a trademark of The Open Group. .bp .bp 1 -.EH '\fBX Session Management Library\fP''\fBX11, Release 6.4\fP' -.OH '\fBX Session Management Library\fP''\fBX11, Release 6.4\fP' +.EH '\fBX Session Management Library\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Session Management Library\fP''\fBX11, Release 6.7\fP' .EF ''\- \\\\n(PN \-'' .OF ''\- \\\\n(PN \-'' .NH 1 diff --git a/specs/SM/xsmp.ms b/specs/SM/xsmp.ms index 0a962e4..b8a91c5 100644 --- a/specs/SM/xsmp.ms +++ b/specs/SM/xsmp.ms @@ -1,6 +1,5 @@ .\" Use tbl, -ms, and macros.t .\" $Xorg: xsmp.ms,v 1.3 2000/08/17 19:42:19 cpqbld Exp $ -.\" $XFree86: xc/doc/specs/SM/xsmp.ms,v 1.2 2003/07/09 15:27:25 tsi Exp $ .EH '''' .OH '''' .EF '''' @@ -59,8 +58,8 @@ CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. .OF ''\\\\n(PN'' .bp 1 .af PN 1 -.EH '\fBX Session Management Protocol\fP''\fBX11, Release 6.4\fP' -.OH '\fBX Session Management Protocol\fP''\fBX11, Release 6.4\fP' +.EH '\fBX Session Management Protocol\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Session Management Protocol\fP''\fBX11, Release 6.7\fP' .EF ''\fB\\\\n(PN\fP'' .OF ''\fB\\\\n(PN\fP'' .nH 1 "Acknowledgements" diff --git a/specs/X11/CH01 b/specs/X11/CH01 index 3d83ec4..528df0a 100644 --- a/specs/X11/CH01 +++ b/specs/X11/CH01 @@ -1,5 +1,4 @@ .\" Copyright \(co 1985, 1986, 1987, 1988, 1989, 1990, 1991, 1994, 1996 X Consortium -.\" Copyright \(co 2000 The XFree86 Project, Inc. .\" .\" Permission is hereby granted, free of charge, to any person obtaining .\" a copy of this software and associated documentation files (the @@ -40,11 +39,9 @@ .\" Digital and Tektronix makes no representations about the suitability .\" of this documentation for any purpose. .\" It is provided ``as is'' without express or implied warranty. -.\" -.\" $XFree86: xc/doc/specs/X11/CH01,v 1.3 2003/12/11 21:24:37 herrb Exp $ .\" -.EH '\fBXlib \- C Library\fP''\fBX11, Release 6.7 DRAFT\fP' -.OH '\fBXlib \- C Library\fP''\fBX11, Release 6.7 DRAFT\fP' +.EH '\fBXlib \- C Library\fP''\fBX11, Release 6.7\fP' +.OH '\fBXlib \- C Library\fP''\fBX11, Release 6.7\fP' .EF ''\fB % \fP'' .OF ''\fB % \fP'' .hw WM_NORMAL_HINTS @@ -590,7 +587,7 @@ in the host encoding. .IP \(bu 5 Latin-1 .IP -The coded character set defined by the ISO 8859-1 standard. +The coded character set defined by the ISO8859-1 standard. .IP \(bu 5 Latin Portable Character Encoding .IP @@ -604,11 +601,6 @@ STRING Encoding .IP Latin-1, plus tab and newline. .IP \(bu 5 -UTF-8 Encoding -.IP -The ASCII compatible character encoding scheme defined by the ISO 10646-1 -standard. -.IP \(bu 5 POSIX Portable Filename Character Set .IP The set of 65 characters, diff --git a/specs/X11/CH02 b/specs/X11/CH02 index df7d676..61554b8 100644 --- a/specs/X11/CH02 +++ b/specs/X11/CH02 @@ -40,7 +40,7 @@ .\" of this documentation for any purpose. .\" It is provided ``as is'' without express or implied warranty. .\" -.\" $XFree86: xc/doc/specs/X11/CH02,v 1.2 2003/07/09 15:27:25 tsi Exp $ +.\" $XFree86$ \& .sp 1 .ce 3 diff --git a/specs/X11/CH09 b/specs/X11/CH09 index 078bc19..2b79d38 100644 --- a/specs/X11/CH09 +++ b/specs/X11/CH09 @@ -40,7 +40,6 @@ .\" of this documentation for any purpose. .\" It is provided ``as is'' without express or implied warranty. .\" -.\" $XFree86: xc/doc/specs/X11/CH09,v 1.3 2003/07/18 15:53:24 tsi Exp $ \& .sp 1 .ce 3 @@ -970,6 +969,7 @@ The family member specifies which protocol address family to use (for example, TCP/IP or DECnet) and can be .PN FamilyInternet , .PN FamilyInternet6 , +.PN FamilyServerInterpreted , .PN FamilyDECnet , or .PN FamilyChaos . @@ -989,6 +989,30 @@ The second byte contains the most significant 2 bits of the node number in the least significant 2 bits of the byte and the area in the most significant 6 bits of the byte. .LP +For the ServerInterpreted family, the length is ignored and the address +member is a pointer to a +.PN XServerInterpretedAddress +structure, which contains: +.LP +.IN "XServerInterpretedAddress" "" "@DEF@" +.sM +.Ds 0 +.TA .5i 3i +.ta .5i 3i +typedef struct { + int typelength; /* length of type string, in bytes */ + int valuelength;/* length of value string, in bytes */ + char *type; /* pointer to where to find the type string */ + char *value; /* pointer to where to find the address */ +} XServerInterpretedAddress; +.De +.LP +.eM +The type and value members point to strings representing the type and value of +the server interpreted entry. These strings may not be NULL-terminated so care +should be used when accessing them. The typelength and valuelength members +specify the length in byte of the type and value strings. +.LP .sp To add a single host, use .PN XAddHost . diff --git a/specs/X11/CH13 b/specs/X11/CH13 index b9f0266..539743c 100644 --- a/specs/X11/CH13 +++ b/specs/X11/CH13 @@ -1,5 +1,4 @@ .\" Copyright \(co 1985, 1986, 1987, 1988, 1989, 1990, 1991, 1994, 1996 X Consortium -.\" Copyright \(co 2000 The XFree86 Project, Inc. .\" .\" Permission is hereby granted, free of charge, to any person obtaining .\" a copy of this software and associated documentation files (the @@ -40,8 +39,6 @@ .\" Digital and Tektronix makes no representations about the suitability .\" of this documentation for any purpose. .\" It is provided ``as is'' without express or implied warranty. -.\" -.\" $XFree86: xc/doc/specs/X11/CH13,v 1.5 2000/12/04 18:49:17 dawes Exp $ .\" \& .sp 1 @@ -348,9 +345,6 @@ Encoding of supplied/returned T} text (some WM_ property text in environment locale) - T{ -.PN Xutf8SetWMProperties -T} .sp 6p T{ .PN setlocale @@ -363,17 +357,11 @@ T} .PN XwcTextPropertyToTextList T} T{ -.PN Xutf8TextPropertyToTextList -T} - T{ .PN XmbTextListToTextProperty T} T{ .PN XwcTextListToTextProperty T} - T{ -.PN Xutf8TextListToTextProperty -T} .sp Text Input: .sp 6p @@ -419,9 +407,6 @@ T} T} T{ Encoding of returned text T} - T{ -.PN Xutf8LookupString -T} .sp Text Drawing: .sp 6p @@ -465,12 +450,6 @@ T} T{ Locale of supplied text T} T{ -.PN Xutf8DrawText , -and so on -T} T{ -Locale-dependent metrics -T} - T{ .PN XExtentsOfFontSet , and so on T} T{ @@ -480,10 +459,7 @@ T} .PN XmbTextExtents , T} T{ -.PN XwcTextExtents , -T} - T{ -.PN Xutf8TextExtents , +.PN XwcTextExtents , and so on T} .sp @@ -771,11 +747,7 @@ function presents a variable argument list programming interface for setting properties or features of the specified output method. This function returns NULL if it succeeds; otherwise, -it returns the name of the first argument that could not be set. -Xlib does not attempt to set arguments from the supplied list that -follow the failed argument; -all arguments in the list preceding the failed argument have been set -correctly. +it returns the name of the first argument that could not be obtained. .LP No standard arguments are currently defined by Xlib. .LP @@ -1856,7 +1828,7 @@ returns a valid .PN XFontSet to font_set. .LP -When an Xmb/wc/utf8 drawing or measuring function is called with an +When an Xmb/wc drawing or measuring function is called with an .PN XFontSet that has missing charsets, some characters in the locale will not be drawable. @@ -1929,7 +1901,7 @@ The .PN XFontsOfFontSet function returns a list of one or more .PN XFontStructs -and font names for the fonts used by the Xmb/wc/utf8 layer +and font names for the fonts used by the Xmb and Xwc layers for the given font set. A list of pointers to the .PN XFontStruct @@ -2108,10 +2080,9 @@ Regardless of the character rendering order, the origins of all characters are on the primary draw direction side of the drawing origin. The screen location of a particular character image may be determined with -.PN XmbTextPerCharExtents , -.PN XwcTextPerCharExtents +.PN XmbTextPerCharExtents or -.PN Xutf8TextPerCharExtents . +.PN XwcTextPerCharExtents . .LP The drawing functions are allowed to implement context-dependent rendering, where the glyphs drawn for a string are not simply a @@ -2225,10 +2196,9 @@ The max_ink_extent member gives the maximum extent, over all drawable characters the rectangles that bound the character glyph image drawn in the foreground color, relative to a constant origin. See -.PN XmbTextExtents , -.PN XwcTextExtents +.PN XmbTextExtents and -.PN Xutf8TextExtents +.PN XwcTextExtents for detailed semantics. .LP The max_logical_extent member gives the maximum extent, @@ -2247,10 +2217,9 @@ the string's extent by an amount other than that character's individual extent. .LP The rectangles for a given character in a string can be obtained from -.PN XmbPerCharExtents , -.PN XwcPerCharExtents +.PN XmbPerCharExtents or -.PN Xutf8PerCharExtents . +.PN XwcPerCharExtents . .LP .sp To obtain the maximum extents structure given an @@ -2272,7 +2241,7 @@ The .PN XExtentsOfFontSet function returns an .PN XFontSetExtents -structure for the fonts used by the Xmb/wc/utf8 layer +structure for the fonts used by the Xmb and Xwc layers for the given font set. .LP The @@ -2288,13 +2257,11 @@ Until freed, its contents will not be modified by Xlib. .sp To obtain the escapement in pixels of the specified text as a value, use -.PN XmbTextEscapement , -.PN XwcTextEscapement +.PN XmbTextEscapement or -.PN Xutf8TextEscapement . +.PN XwcTextEscapement . .IN "XmbTextEscapement" "" "@DEF@" .IN "XwcTextEscapement" "" "@DEF@" -.IN "Xutf8TextEscapement" "" "@DEF@" .sM .FD 0 int XmbTextEscapement\^(\^\fIfont_set\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^) @@ -2314,15 +2281,6 @@ int XwcTextEscapement\^(\^\fIfont_set\fP\^, \fIstring\fP\^, \fInum_wchars\fP\^) .br int \fInum_wchars\fP\^; .FN -.FD 0 -int Xutf8TextEscapement\^(\^\fIfont_set\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^) -.br - XFontSet \fIfont_set\fP\^; -.br - char *\fIstring\fP\^; -.br - int \fInum_bytes\fP\^; -.FN .IP \fIfont_set\fP 1i Specifies the font set. .IP \fIstring\fP 1i @@ -2334,10 +2292,9 @@ Specifies the number of characters in the string argument. .LP .eM The -.PN XmbTextEscapement , -.PN XwcTextEscapement +.PN XmbTextEscapement and -.PN Xutf8TextEscapement +.PN XwcTextEscapement functions return the escapement in pixels of the specified string as a value, using the fonts loaded for the specified font set. The escapement is the distance in pixels in the primary draw @@ -2348,23 +2305,15 @@ dependent on the supplied string. Regardless of the character rendering order, the escapement is always positive. .LP -The function -.PN Xutf8TextEscapement -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . -.LP .sp To obtain the overall_ink_return and overall_logical_return arguments, the overall bounding box of the string's image, and a logical bounding box, use -.PN XmbTextExtents , -.PN XwcTextExtents -or -.PN Xutf8TextExtents . +.PN XmbTextExtents + or +.PN XwcTextExtents . .IN "XmbTextExtents" "" "@DEF@" .IN "XwcTextExtents" "" "@DEF@" -.IN "Xutf8TextExtents" "" "@DEF@" .sM .FD 0 int XmbTextExtents\^(\^\fIfont_set\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^, \fIoverall_ink_return\fP\^, \fIoverall_logical_return\fP\^) @@ -2393,19 +2342,6 @@ int XwcTextExtents\^(\^\fIfont_set\fP\^, \fIstring\fP\^, \fInum_wchars\fP\^, .br XRectangle *\fIoverall_logical_return\fP\^; .FN -.FD 0 -int Xutf8TextExtents\^(\^\fIfont_set\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^, \fIoverall_ink_return\fP\^, \fIoverall_logical_return\fP\^) -.br - XFontSet \fIfont_set\fP\^; -.br - char *\fIstring\fP\^; -.br - int \fInum_bytes\fP\^; -.br - XRectangle *\fIoverall_ink_return\fP\^; -.br - XRectangle *\fIoverall_logical_return\fP\^; -.FN .IP \fIfont_set\fP 1i Specifies the font set. .IP \fIstring\fP 1i @@ -2422,19 +2358,17 @@ Returns the overall logical \*(Ov. .LP .eM The -.PN XmbTextExtents , -.PN XwcTextExtents +.PN XmbTextExtents and -.PN Xutf8TextExtents +.PN XwcTextExtents functions set the components of the specified overall_ink_return and overall_logical_return arguments to the overall bounding box of the string's image and a logical bounding box for spacing purposes, respectively. They return the value returned by -.PN XmbTextEscapement , -.PN XwcTextEscapement +.PN XmbTextEscapement or -.PN Xutf8TextEscapement . +.PN XwcTextEscapement . These metrics are relative to the drawing origin of the string, using the fonts loaded for the specified font set. .LP @@ -2475,22 +2409,14 @@ or to justify words, but for context-dependent rendering, the client should not assume that it can redraw the character by itself and get the same rendering. .LP -The function -.PN Xutf8TextExtents -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . -.LP .sp To obtain per-character information for a text string, use -.PN XmbTextPerCharExtents , -.PN XwcTextPerCharExtents +.PN XmbTextPerCharExtents or -.PN Xutf8TextPerCharExtents . +.PN XwcTextPerCharExtents . .IN "XmbTextPerCharExtents" "" "@DEF@" .IN "XwcTextPerCharExtents" "" "@DEF@" -.IN "Xutf8TextPerCharExtents" "" "@DEF@" .sM .FD 0 Status XmbTextPerCharExtents\^(\^\fIfont_set\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^, \fIink_array_return\fP\^, @@ -2538,29 +2464,6 @@ Status XwcTextPerCharExtents\^(\^\fIfont_set\fP\^, \fIstring\fP\^, \fInum_wchars .br XRectangle *\fIoverall_logical_return\fP\^; .FN -.FD 0 -Status Xutf8TextPerCharExtents\^(\^\fIfont_set\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^, \fIink_array_return\fP\^, -.br - \fIlogical_array_return\fP\^, \fIarray_size\fP\^, \fInum_chars_return\fP\^, \fIoverall_ink_return\fP\^, \fIoverall_logical_return\fP\^) -.br - XFontSet \fIfont_set\fP\^; -.br - char *\fIstring\fP\^; -.br - int \fInum_bytes\fP\^; -.br - XRectangle *\fIink_array_return\fP\^; -.br - XRectangle *\fIlogical_array_return\fP\^; -.br - int \fIarray_size\fP\^; -.br - int *\fInum_chars_return\fP\^; -.br - XRectangle *\fIoverall_ink_return\fP\^; -.br - XRectangle *\fIoverall_logical_return\fP\^; -.FN .IP \fIfont_set\fP 1i Specifies the font set. .IP \fIstring\fP 1i @@ -2586,10 +2489,9 @@ Returns the overall logical \*(Ov. .LP .eM The -.PN XmbTextPerCharExtents , -.PN XwcTextPerCharExtents +.PN XmbTextPerCharExtents and -.PN Xutf8TextPerCharExtents +.PN XwcTextPerCharExtents functions return the text dimensions of each character of the specified text, using the fonts loaded for the specified font set. Each successive element of ink_array_return and logical_array_return @@ -2632,22 +2534,14 @@ and num_chars_return is set to the number of rectangles required. Otherwise, the functions return a nonzero value. .LP If the overall_ink_return or overall_logical_return argument is non-NULL, -.PN XmbTextPerCharExtents , -.PN XwcTextPerCharExtents +.PN XmbTextPerCharExtents and -.PN Xutf8TextPerCharExtents +.PN XwcTextPerCharExtents return the maximum extent of the string's metrics to overall_ink_return or overall_logical_return, as returned by -.PN XmbTextExtents , -.PN XwcTextExtents +.PN XmbTextExtents or -.PN Xutf8TextExtents . -.LP -The function -.PN Xutf8TextPerCharExtents -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . +.PN XwcTextExtents . .NH 3 Drawing Text Using Font Sets .XS @@ -2663,8 +2557,6 @@ and .PN XDrawImageString except that they work with font sets instead of single fonts and interpret the text based on the locale of the font set -(for functions whose name starts with Xmb or Xwc) or as UTF-8 encoded -text (for functions whose name starts with Xutf8), instead of treating the bytes of the string as direct font indexes. See section 8.6 for details of the use of Graphics Contexts (GCs) and possible protocol errors. @@ -2678,10 +2570,9 @@ the font in the GC is ignored and may be modified by the functions. No validation that all fonts conform to some width rule is performed. .LP The text functions -.PN XmbDrawText , -.PN XwcDrawText +.PN XmbDrawText and -.PN Xutf8DrawText +.PN XwcDrawText use the following structures: .LP .IN "XmbTextItem" "" "@DEF@" @@ -2712,13 +2603,11 @@ typedef struct { .eM .sp To draw text using multiple font sets in a given drawable, use -.PN XmbDrawText , -.PN XwcDrawText +.PN XmbDrawText or -.PN Xutf8DrawText . +.PN XwcDrawText . .IN "XmbDrawText" "" "@DEF@" .IN "XwcDrawText" "" "@DEF@" -.IN "Xutf8DrawText" "" "@DEF@" .sM .FD 0 void XmbDrawText\^(\^\fIdisplay\fP\^, \fId\fP\^, \fIgc\fP\^, \fIx\fP\^, \fIy\fP\^, \fIitems\fP\^, \fInitems\fP\^) @@ -2750,21 +2639,6 @@ void XwcDrawText\^(\^\fIdisplay\fP\^, \fId\fP\^, \fIgc\fP\^, \fIx\fP\^, \fIy\fP\ .br int \fInitems\fP\^; .FN -.FD 0 -void Xutf8DrawText\^(\^\fIdisplay\fP\^, \fId\fP\^, \fIgc\fP\^, \fIx\fP\^, \fIy\fP\^, \fIitems\fP\^, \fInitems\fP\^) -.br - Display *\fIdisplay\fP\^; -.br - Drawable \fId\fP\^; -.br - GC \fIgc\fP\^; -.br - int \fIx\fP\^, \fIy\fP\^; -.br - XmbTextItem *\fIitems\fP\^; -.br - int \fInitems\fP\^; -.FN .IP \fIdisplay\fP 1i Specifies the connection to the X server. .IP \fId\fP 1i @@ -2784,10 +2658,9 @@ Specifies the number of text items in the array. .LP .eM The -.PN XmbDrawText , -.PN XwcDrawText +.PN XmbDrawText and -.PN Xutf8DrawText +.PN XwcDrawText functions allow complex spacing and font set shifts between text strings. Each text item is processed in turn, with the origin of a text element advanced in the primary draw direction by the escapement of the @@ -2802,19 +2675,18 @@ Leading text items with a font_set member set to .PN None will not be drawn. .LP -.PN XmbDrawText , -.PN XwcDrawText +.PN XmbDrawText and -.PN Xutf8DrawText +.PN XwcDrawText do not perform any context-dependent rendering between text segments. Clients may compute the drawing metrics by passing each text segment to -.PN XmbTextExtents , -.PN XwcTextExtents , -.PN Xutf8TextExtents -or -.PN XmbTextPerCharExtents , +.PN XmbTextExtents +and +.PN XwcTextExtents +or +.PN XmbTextPerCharExtents +and .PN XwcTextPerCharExtents . -.PN Xutf8TextPerCharExtents . When the .PN XFontSet has missing charsets, each unavailable character is drawn @@ -2822,21 +2694,13 @@ with the default string returned by .PN XCreateFontSet . The behavior for an invalid codepoint is undefined. .LP -The function -.PN Xutf8DrawText -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . -.LP .sp To draw text using a single font set in a given drawable, use -.PN XmbDrawString , -.PN XwcDrawString +.PN XmbDrawString or -.PN Xutf8DrawString . +.PN XwcDrawString . .IN "XmbDrawString" "" "@DEF@" .IN "XwcDrawString" "" "@DEF@" -.IN "Xutf8DrawString" "" "@DEF@" .sM .FD 0 void XmbDrawString\^(\^\fIdisplay\fP\^, \fId\fP\^, \fIfont_set\fP\^, \fIgc\fP\^, \fIx\fP\^, \fIy\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^) @@ -2872,23 +2736,6 @@ void XwcDrawString\^(\^\fIdisplay\fP\^, \fId\fP\^, \fIfont_set\fP\^, \fIgc\fP\^, .br int \fInum_wchars\fP\^; .FN -.FD 0 -void Xutf8DrawString\^(\^\fIdisplay\fP\^, \fId\fP\^, \fIfont_set\fP\^, \fIgc\fP\^, \fIx\fP\^, \fIy\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^) -.br - Display *\fIdisplay\fP\^; -.br - Drawable \fId\fP\^; -.br - XFontSet \fIfont_set\fP\^; -.br - GC \fIgc\fP\^; -.br - int \fIx\fP\^, \fIy\fP\^; -.br - char *\fIstring\fP\^; -.br - int \fInum_bytes\fP\^; -.FN .IP \fIdisplay\fP 1i Specifies the connection to the X server. .IP \fId\fP 1i @@ -2912,10 +2759,9 @@ Specifies the number of characters in the string argument. .LP .eM The -.PN XmbDrawString , -.PN XwcDrawString +.PN XmbDrawString and -.PN Xutf8DrawString +.PN XwcDrawString functions draw the specified text with the foreground pixel. When the .PN XFontSet @@ -2924,21 +2770,13 @@ with the default string returned by .PN XCreateFontSet . The behavior for an invalid codepoint is undefined. .LP -The function -.PN Xutf8DrawString -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . -.LP .sp To draw image text using a single font set in a given drawable, use -.PN XmbDrawImageString , -.PN XwcDrawImageString +.PN XmbDrawImageString or -.PN Xutf8DrawImageString . +.PN XwcDrawImageString . .IN "XmbDrawImageString" "" "@DEF@" .IN "XwcDrawImageString" "" "@DEF@" -.IN "Xutf8DrawImageString" "" "@DEF@" .sM .FD 0 void XmbDrawImageString\^(\^\fIdisplay\fP\^, \fId\fP\^, \fIfont_set\fP\^, \fIgc\fP\^, \fIx\fP\^, \fIy\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^) @@ -2974,23 +2812,6 @@ void XwcDrawImageString\^(\^\fIdisplay\fP\^, \fId\fP\^, \fIfont_set\fP\^, \fIgc\ .br int \fInum_wchars\fP\^; .FN -.FD 0 -void Xutf8DrawImageString\^(\^\fIdisplay\fP\^, \fId\fP\^, \fIfont_set\fP\^, \fIgc\fP\^, \fIx\fP\^, \fIy\fP\^, \fIstring\fP\^, \fInum_bytes\fP\^) -.br - Display *\fIdisplay\fP\^; -.br - Drawable \fId\fP\^; -.br - XFontSet \fIfont_set\fP\^; -.br - GC \fIgc\fP\^; -.br - int \fIx\fP\^, \fIy\fP\^; -.br - char *\fIstring\fP\^; -.br - int \fInum_bytes\fP\^; -.FN .IP \fIdisplay\fP 1i Specifies the connection to the X server. .IP \fId\fP 1i @@ -3014,17 +2835,15 @@ Specifies the number of characters in the string argument. .LP .eM The -.PN XmbDrawImageString , -.PN XwcDrawImageString +.PN XmbDrawImageString and -.PN Xutf8DrawImageString +.PN XwcDrawImageString functions fill a destination rectangle with the background pixel defined in the GC and then paint the text with the foreground pixel. The filled rectangle is the rectangle returned to overall_logical_return by -.PN XmbTextExtents , -.PN XwcTextExtents +.PN XmbTextExtents or -.PN Xutf8TextExtents +.PN XwcTextExtents for the same text and .PN XFontSet . .LP @@ -3034,12 +2853,6 @@ has missing charsets, each unavailable character is drawn with the default string returned by .PN XCreateFontSet . The behavior for an invalid codepoint is undefined. -.LP -The function -.PN Xutf8TextExtents -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . .NH 2 Input Methods .XS @@ -3382,10 +3195,9 @@ Getting Keyboard Input .LP To obtain characters from an input method, a client must call the function -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString or -.PN Xutf8LookupString +.PN XwcLookupString with an input context created from that input method. Both a locale and display are bound to an input method when it is opened, and an input context inherits this locale and display. @@ -3393,9 +3205,7 @@ Any strings returned by .PN XmbLookupString or .PN XwcLookupString -will be encoded in that locale. Strings returned by -.PN Xutf8LookupString -are encoded in UTF-8. +will be encoded in that locale. .NH 4 Focus Management .XS @@ -3403,10 +3213,9 @@ Focus Management .XE .LP For each text entry area in which the -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString or -.PN Xutf8LookupString +.PN XwcLookupString functions are used, there will be an associated input context. .LP @@ -3538,10 +3347,9 @@ Event Filtering A filtering mechanism is provided to allow input methods to capture X events transparently to clients. It is expected that toolkits (or clients) using -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString or -.PN Xutf8LookupString +.PN XwcLookupString will call this filter at some point in the event processing mechanism to make sure that events needed by an input method can be filtered by that input method. @@ -3578,10 +3386,9 @@ by the client itself, tightly coupled with the input method logic. .LP When the user enters a keystroke, the client calls -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString or -.PN Xutf8LookupString . +.PN XwcLookupString . At this point, in the on-the-spot case, the echo of the keystroke in the preedit has not yet been done. Before returning to the client logic that handles the input characters, @@ -3629,10 +3436,9 @@ As highlighted before, the input method architecture provides preediting, which supports a type of preprocessor input composition. In this case, composition consists of interpreting a sequence of key events and returning a committed string via -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString or -.PN Xutf8LookupString . +.PN XwcLookupString . This provides the basics for input methods. .LP In addition to preediting based on key events, a general framework @@ -3703,10 +3509,9 @@ and starts editing again. .sp For this reason, an input method supporting this type of conversion should take notice of when the client calls -.PN XmbResetIC , -.PN XwcResetIC +.PN XmbResetIC or -.PN Xutf8ResetIC , +.PN XwcResetIC , which is usually an indication of a context change. .LP Context-sensitive conversions just need a copy of the client's text, @@ -3714,10 +3519,9 @@ while other conversions replace the client's text with new text to achieve the reconversion or transliteration. Yet in all cases the result of a conversion, either immediately or via preediting, is returned by the -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString and -.PN Xutf8LookupString +.PN XwcLookupString functions. .LP String conversion support is dependent on the availability of the @@ -4884,13 +4688,11 @@ events from the input method that are directed to the focus window. .LP .sp To reset the state of an input context to its initial state, use -.PN XmbResetIC , -.PN XwcResetIC +.PN XmbResetIC or -.PN Xutf8ResetIC . +.PN XwcResetIC . .IN "XmbResetIC" "" "@DEF@" .IN "XwcResetIC" "" "@DE@" -.IN "Xutf8ResetIC" "" "@DE@" .sM .FD 0 char * XmbResetIC\^(\^\fIic\fP\^) @@ -4902,11 +4704,6 @@ wchar_t * XwcResetIC\^(\^\fIic\fP\^) .br XIC \fIic\fP\^; .FN -.FD 0 -char * Xutf8ResetIC\^(\^\fIic\fP\^) -.br - XIC \fIic\fP\^; -.FN .IP \fIic\fP 1i Specifies the input context. .LP @@ -4915,10 +4712,9 @@ When .PN XNResetState is set to .PN XIMInitialState , -.PN XmbResetIC , -.PN XwcResetIC +.PN XmbResetIC and -.PN Xutf8ResetIC +.PN XwcResetIC reset an input context to its initial state; when .PN XNResetState @@ -4929,21 +4725,14 @@ In both cases, any input pending on that context is deleted. The input method is required to clear the preedit area, if any, and update the status accordingly. Calling -.PN XmbResetIC , -.PN XwcResetIC +.PN XmbResetIC or -.PN Xutf8ResetIC +.PN XwcResetIC does not change the focus. .LP The return value of .PN XmbResetIC is its current preedit string as a multibyte string. -The return value of -.PN XwcResetIC -is its current preedit string as a wide character string. -The return value of -.PN Xutf8ResetIC -is its current preedit string as an UTF-8 string. If there is any preedit text drawn or visible to the user, then these procedures must return a non-NULL string. If there is no visible preedit text, @@ -4953,12 +4742,6 @@ whether these procedures return a non-NULL string or NULL. The client should free the returned string by calling .PN XFree . .LP -The function -.PN Xutf8ResetIC -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . -.LP .sp To get the input method associated with an input context, use .PN XIMOfIC . @@ -5493,10 +5276,9 @@ Reset State The .PN XNResetState argument specifies the state the input context will return to after calling -.PN XmbResetIC , -.PN XwcResetIC +.PN XmbResetIC or -.PN Xutf8ResetIC . +.PN XwcResetIC . .LP The XIC state may be set to its initial state, as specified by the .PN XNPreeditState @@ -5537,10 +5319,9 @@ T} If .PN XIMInitialState is set, then -.PN XmbResetIC , -.PN XwcResetIC +.PN XmbResetIC and -.PN Xutf8ResetIC +.PN XwcResetIC will return to the initial .PN XNPreeditState state of the XIC. @@ -5548,10 +5329,9 @@ state of the XIC. If .PN XIMPreserveState is set, then -.PN XmbResetIC , -.PN XwcResetIC +.PN XmbResetIC and -.PN Xutf8ResetIC +.PN XwcResetIC will preserve the current state of the XIC. .LP If @@ -6025,10 +5805,9 @@ is set to the .PN XNPreeditState value specified at the creation time will be reflected as the initial state for -.PN XmbResetIC , -.PN XwcResetIC +.PN XmbResetIC and -.PN Xutf8ResetIC . +.PN XwcResetIC . .LP Because this XIC value is optional, a client should call .PN XGetIMValues @@ -7225,13 +7004,11 @@ Getting Keyboard Input .LP To get composed input from an input method, use -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString or -.PN Xutf8LookupString . +.PN XwcLookupString . .IN "XmbLookupString" "" "@DEF@" .IN "XwcLookupString" "" "@DEF@" -.IN "Xutf8LookupString" "" "@DEF@" .sM .FD 0 int XmbLookupString\^(\^\fIic\fP\^, \fIevent\fP\^, \fIbuffer_return\fP\^, \fIbytes_buffer\fP\^, \fIkeysym_return\fP\^, \fIstatus_return\fP\^) @@ -7263,21 +7040,6 @@ int XwcLookupString\^(\^\fIic\fP\^, \fIevent\fP\^, \fIbuffer_return\fP\^, \fIbyt .br Status *\fIstatus_return\fP\^; .FN -.FD 0 -int Xutf8LookupString\^(\^\fIic\fP\^, \fIevent\fP\^, \fIbuffer_return\fP\^, \fIbytes_buffer\fP\^, \fIkeysym_return\fP\^, \fIstatus_return\fP\^) -.br - XIC \fIic\fP\^; -.br - XKeyPressedEvent *\fIevent\fP; -.br - char *\fIbuffer_return\fP\^; -.br - int \fIbytes_buffer\fP\^; -.br - KeySym *\fIkeysym_return\fP\^; -.br - Status *\fIstatus_return\fP\^; -.FN .IP \fIic\fP 1i Specifies the input context. .ds Ev key event to be used @@ -7298,10 +7060,9 @@ Returns a value indicating what kind of data is returned. .LP .eM The -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString and -.PN Xutf8LookupString +.PN XwcLookupString functions return the string from the input method specified in the buffer_return argument. If no string is returned, @@ -7314,9 +7075,7 @@ If both a string and a KeySym are returned, the KeySym value does not necessarily correspond to the string returned. .LP .PN XmbLookupString -and -.PN Xutf8LookupString -return the length of the string in bytes, and +returns the length of the string in bytes, and .PN XwcLookupString returns the length of the string in characters. Both @@ -7324,9 +7083,7 @@ Both and .PN XwcLookupString return text in the encoding of the locale bound to the input method -of the specified input context, and -.PN Xutf8LookupString -returns text in UTF-8 encoding. +of the specified input context. .LP Each string returned by .PN XmbLookupString @@ -7335,14 +7092,13 @@ and begins in the initial state of the encoding of the locale (if the encoding of the locale is state-dependent). .NT -To ensure proper input processing, +To insure proper input processing, it is essential that the client pass only .PN KeyPress events to -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString and -.PN Xutf8LookupString . +.PN XwcLookupString . Their behavior when a client passes a .PN KeyRelease event is undefined. @@ -7350,7 +7106,7 @@ event is undefined. .LP Clients should check the status_return argument before using the other returned values. -These three functions each return a value to status_return +These two functions both return a value to status_return that indicates what has been returned in the other arguments. The possible values returned are: .TS @@ -7359,10 +7115,9 @@ T{ .PN XBufferOverflow T} T{ The input string to be returned is too large for the supplied buffer_return. -The required size (for -.PN XmbLookupString , -.PN Xutf8LookupString -in bytes; for +The required size +.Pn ( XmbLookupString +in bytes; .PN XwcLookupString in characters) is returned as the value of the function, and the contents of buffer_return and keysym_return are not modified. @@ -7380,9 +7135,9 @@ T{ .PN XLookupChars T} T{ Some input characters have been composed. -They are placed in the buffer_return argument, using the encoding -described above, +They are placed in the buffer_return argument, and the string length is returned as the value of the function. +The string is encoded in the locale bound to the input context. The content of the keysym_return argument is not modified. T} T{ @@ -7405,24 +7160,16 @@ T} .TE .LP It does not make any difference if the input context passed as an argument to -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString and -.PN Xutf8LookupString +.PN XwcLookupString is the one currently in possession of the focus or not. Input may have been composed within an input context before it lost the focus, and that input may be returned on subsequent calls to -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString or -.PN Xutf8LookupString +.PN XwcLookupString even though it does not have any more keyboard focus. -.LP -The function -.PN Xutf8LookupString -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . .NH 3 Input Method Conventions .XS @@ -7455,10 +7202,9 @@ A .PN KeyPress event with a KeyCode of zero is used exclusively as a signal that an input method has composed input that can be returned by -.PN XmbLookupString , -.PN XwcLookupString +.PN XmbLookupString or -.PN Xutf8LookupString . +.PN XwcLookupString . No other use is made of a .PN KeyPress event with KeyCode of zero. diff --git a/specs/X11/CH14 b/specs/X11/CH14 index 16d66e7..34c09da 100644 --- a/specs/X11/CH14 +++ b/specs/X11/CH14 @@ -1,5 +1,4 @@ .\" Copyright \(co 1985, 1986, 1987, 1988, 1989, 1990, 1991, 1994, 1996 X Consortium -.\" Copyright \(co 2000 The XFree86 Project, Inc. .\" .\" Permission is hereby granted, free of charge, to any person obtaining .\" a copy of this software and associated documentation files (the @@ -40,8 +39,6 @@ .\" Digital and Tektronix makes no representations about the suitability .\" of this documentation for any purpose. .\" It is provided ``as is'' without express or implied warranty. -.\" -.\" $XFree86: xc/doc/specs/X11/CH14,v 1.2 2000/11/28 18:49:19 dawes Exp $ .\" \& .sp 1 @@ -502,29 +499,21 @@ typedef enum { XStringStyle, /* STRING */ XCompoundTextStyle, /* COMPOUND_TEXT */ XTextStyle, /* text in owner's encoding (current locale) */ - XStdICCTextStyle, /* STRING, else COMPOUND_TEXT */ - XUTF8StringStyle /* UTF8_STRING */ + XStdICCTextStyle /* STRING, else COMPOUND_TEXT */ } XICCEncodingStyle; .De .LP .eM -The value -.PN XUTF8StringStyle -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . -.LP .sp +.LP To convert a list of text strings to an .PN XTextProperty structure, use -.PN XmbTextListToTextProperty , -.PN XwcTextListToTextProperty +.PN XmbTextListToTextProperty or -.PN Xutf8TextListToTextProperty . +.PN XwcTextListToTextProperty . .IN "XmbTextListToTextProperty" "" "@DEF@" .IN "XwcTextListToTextProperty" "" "@DEF@" -.IN "Xutf8TextListToTextProperty" "" "@DEF@" .sM .FD 0 int XmbTextListToTextProperty\^(\^\fIdisplay\fP\^, \fIlist\fP\^, \fIcount\fP\^, \fIstyle\fP\^, \fItext_prop_return\fP\^) @@ -552,19 +541,6 @@ int XwcTextListToTextProperty\^(\^\fIdisplay\fP\^, \fIlist\fP\^, \fIcount\fP\^, .br XTextProperty *\fItext_prop_return\fP\^; .FN -.FD 0 -int Xutf8TextListToTextProperty\^(\^\fIdisplay\fP\^, \fIlist\fP\^, \fIcount\fP\^, \fIstyle\fP\^, \fItext_prop_return\fP\^) -.br - Display *\fIdisplay\fP\^; -.br - char **\fIlist\fP\^; -.br - int \fIcount\fP\^; -.br - XICCEncodingStyle \fIstyle\fP\^; -.br - XTextProperty *\fItext_prop_return\fP\^; -.FN .IP \fIdisplay\fP 1i Specifies the connection to the X server. .IP \fIlist\fP 1i @@ -580,20 +556,15 @@ structure. .LP .eM The -.PN XmbTextListToTextProperty , -.PN XwcTextListToTextProperty +.PN XmbTextListToTextProperty and -.PN Xutf8TextListToTextProperty +.PN XwcTextListToTextProperty functions set the specified .PN XTextProperty value to a set of null-separated elements representing the concatenation -of the specified list of null-terminated text strings. The input text -strings must be given in the current locale encoding (for -.PN XmbTextListToTextProperty -and -.PN XwcTextListToTextProperty ), -or in UTF-8 encoding (for -.PN Xutf8TextListToTextProperty ). +of the specified list of null-terminated text strings. +A final terminating null is stored at the end of the value field +of text_prop_return but is not included in the nitems member. .LP The functions set the encoding field of text_prop_return to an .PN Atom @@ -607,12 +578,6 @@ or .PN XCompoundTextStyle is specified, this encoding is ``STRING'' or ``COMPOUND_TEXT'', respectively. -If the style -.PN XUTF8StringStyle -is specified, -this encoding is ``UTF8_STRING''. (This is an XFree86 extension introduced in -XFree86 4.0.2. Its presence is indicated by the macro -.PN X_HAVE_UTF8_STRING .) If the style .PN XTextStyle is specified, @@ -622,8 +587,6 @@ If the style is specified, this encoding is ``STRING'' if the text is fully convertible to STRING, else ``COMPOUND_TEXT''. -A final terminating null byte is stored at the end of the value field -of text_prop_return but is not included in the nitems member. .LP If insufficient memory is available for the new value string, the functions return @@ -651,24 +614,16 @@ is guaranteed. .LP To free the storage for the value field, use .PN XFree . -.LP -The function -.PN Xutf8TextListToTextProperty -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . .sp .LP To obtain a list of text strings from an .PN XTextProperty structure, use -.PN XmbTextPropertyToTextList , -.PN XwcTextPropertyToTextList +.PN XmbTextPropertyToTextList or -.PN Xutf8TextPropertyToTextList . +.PN XwcTextPropertyToTextList . .IN "XmbTextPropertyToTextList" "" "@DEF@" .IN "XwcTextPropertyToTextList" "" "@DEF@" -.IN "Xutf8TextPropertyToTextList" "" "@DEF@" .sM .FD 0 int XmbTextPropertyToTextList\^(\^\fIdisplay\fP\^, \fItext_prop\fP\^, \fIlist_return\fP\^, \fIcount_return\fP\^) @@ -692,17 +647,6 @@ int XwcTextPropertyToTextList\^(\^\fIdisplay\fP\^, \fItext_prop\fP\^, \fIlist_re .br int *\fIcount_return\fP\^; .FN -.FD 0 -int Xutf8TextPropertyToTextList\^(\^\fIdisplay\fP\^, \fItext_prop\fP\^, \fIlist_return\fP\^, \fIcount_return\fP\^) -.br - Display *\fIdisplay\fP\^; -.br - XTextProperty *\fItext_prop\fP\^; -.br - char ***\fIlist_return\fP\^; -.br - int *\fIcount_return\fP\^; -.FN .IP \fIdisplay\fP 1i Specifies the connection to the X server. .IP \fItext_prop\fP 1i @@ -717,20 +661,13 @@ Returns the number of \*(Cn. .LP .eM The -.PN XmbTextPropertyToTextList , -.PN XwcTextPropertyToTextList +.PN XmbTextPropertyToTextList and -.PN Xutf8TextPropertyToTextList -functions return a list of text strings representing the +.PN XwcTextPropertyToTextList +functions return a list of text strings in the current locale representing the null-separated elements of the specified .PN XTextProperty -structure. The returned strings are encoded using the current locale encoding -(for -.PN XmbTextPropertyToTextList -and -.PN XwcTextPropertyToTextList ) -or in UTF-8 (for -.PN Xutf8TextPropertyToTextList ). +structure. The data in text_prop must be format 8. .LP Multiple elements of the property (for example, the strings in a disjoint @@ -739,10 +676,9 @@ The contents of the property are not required to be null-terminated; any terminating null should not be included in text_prop.nitems. .LP If insufficient memory is available for the list and its elements, -.PN XmbTextPropertyToTextList , -.PN XwcTextPropertyToTextList +.PN XmbTextPropertyToTextList and -.PN Xutf8TextPropertyToTextList +.PN XwcTextPropertyToTextList return .PN XNoMemory . If the current locale is not supported, @@ -753,7 +689,7 @@ to the encoding of the current locale, the functions return .PN XConverterNotFound . For supported locales, -existence of a converter from COMPOUND_TEXT, STRING, UTF8_STRING +existence of a converter from COMPOUND_TEXT, STRING or the encoding of the current locale is guaranteed if .PN XSupportsLocale returns @@ -765,15 +701,14 @@ In all of these error cases, the functions do not set any return values. .LP Otherwise, -.PN XmbTextPropertyToTextList , -.PN XwcTextPropertyToTextList +.PN XmbTextPropertyToTextList and -.PN Xutf8TextPropertyToTextList +.PN XwcTextPropertyToTextList return the list of null-terminated text strings to list_return and the number of text strings to count_return. .LP -If the value field of text_prop is not fully convertible to the -encoding of the current locale, +If the value field of text_prop is not fully convertible to the encoding of +the current locale, the functions return the number of unconvertible characters. Each unconvertible character is converted to a string in the current locale that is specific to the current locale. @@ -781,29 +716,20 @@ To obtain the value of this string, use .PN XDefaultString . Otherwise, -.PN XmbTextPropertyToTextList , -.PN XwcTextPropertyToTextList +.PN XmbTextPropertyToTextList and -.PN Xutf8TextPropertyToTextList +.PN XwcTextPropertyToTextList return .PN Success . .LP To free the storage for the list and its contents returned by -.PN XmbTextPropertyToTextList -or -.PN Xutf8TextPropertyToTextList , +.PN XmbTextPropertyToTextList , use .PN XFreeStringList . To free the storage for the list and its contents returned by .PN XwcTextPropertyToTextList , use .PN XwcFreeStringList . -.LP -The function -.PN Xutf8TextPropertyToTextList -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . .sp .LP To free the in-memory data associated with the specified @@ -975,8 +901,7 @@ Specifies the list of strings to be freed. The .PN XFreeStringList function releases memory allocated by -.PN XmbTextPropertyToTextList , -.PN Xutf8TextPropertyToTextList +.PN XmbTextPropertyToTextList and .PN XTextPropertyToStringList and the missing charset list allocated by @@ -2755,16 +2680,13 @@ Using Window Manager Convenience Functions .LP The .PN XmbSetWMProperties -and -.PN Xutf8SetWMProperties -functions store the standard set of window manager properties, +function stores the standard set of window manager properties, with text properties in standard encodings for internationalized text communication. The standard window manager properties for a given window are WM_NAME, WM_ICON_NAME, WM_HINTS, WM_NORMAL_HINTS, WM_CLASS, WM_COMMAND, WM_CLIENT_MACHINE, and WM_LOCALE_NAME. .IN "XmbSetWMProperties" "" "@DEF@" -.IN "Xutf8SetWMProperties" "" "@DEF@" .sM .FD 0 void XmbSetWMProperties\^(\^\fIdisplay\fP\^, \fIw\fP\^, \fIwindow_name\fP\^, \fIicon_name\fP\^, \fIargv\fP\^, \fIargc\fP\^, @@ -2789,29 +2711,6 @@ void XmbSetWMProperties\^(\^\fIdisplay\fP\^, \fIw\fP\^, \fIwindow_name\fP\^, \fI .br XClassHint *\fIclass_hints\fP\^; .FN -.FD 0 -void Xutf8SetWMProperties\^(\^\fIdisplay\fP\^, \fIw\fP\^, \fIwindow_name\fP\^, \fIicon_name\fP\^, \fIargv\fP\^, \fIargc\fP\^, -.br - \fInormal_hints\fP\^, \fIwm_hints\fP\^, \fIclass_hints\fP\^) -.br - Display *\fIdisplay\fP\^; -.br - Window \fIw\fP\^; -.br - char *\fIwindow_name\fP\^; -.br - char *\fIicon_name\fP\^; -.br - char *\fIargv\fP\^[]; -.br - int \fIargc\fP\^; -.br - XSizeHints *\fInormal_hints\fP\^; -.br - XWMHints *\fIwm_hints\fP\^; -.br - XClassHint *\fIclass_hints\fP\^; -.FN .IP \fIdisplay\fP 1i Specifies the connection to the X server. .IP \fIw\fP 1i @@ -2840,22 +2739,19 @@ structure to be used. .eM The .PN XmbSetWMProperties -and -.PN Xutf8SetWMProperties -convenience functions provide a simple programming interface +convenience function provides a simple programming interface for setting those essential window properties that are used for communicating with other clients (particularly window and session managers). .LP If the window_name argument is non-NULL, -they set the WM_NAME property. +.PN XmbSetWMProperties +sets the WM_NAME property. If the icon_name argument is non-NULL, -they set the WM_ICON_NAME property. -The window_name and icon_name arguments are null-terminated strings, for .PN XmbSetWMProperties -in the encoding of the current locale, for -.PN Xutf8SetWMProperties -in UTF-8 encoding. +sets the WM_ICON_NAME property. +The window_name and icon_name arguments are null-terminated strings +in the encoding of the current locale. If the arguments can be fully converted to the STRING encoding, the properties are created with type ``STRING''; otherwise, the arguments are converted to Compound Text, @@ -2863,24 +2759,18 @@ and the properties are created with type ``COMPOUND_TEXT''. .LP If the normal_hints argument is non-NULL, .PN XmbSetWMProperties -and -.PN Xutf8SetWMProperties -call +calls .PN XSetWMNormalHints , which sets the WM_NORMAL_HINTS property (see section 14.1.7). If the wm_hints argument is non-NULL, .PN XmbSetWMProperties -and -.PN Xutf8SetWMProperties -call +calls .PN XSetWMHints , which sets the WM_HINTS property (see section 14.1.6). .LP If the argv argument is non-NULL, .PN XmbSetWMProperties -and -.PN Xutf8SetWMProperties -set the WM_COMMAND property from argv and argc. +sets the WM_COMMAND property from argv and argc. An argc of zero indicates a zero-length command. .LP The hostname of the machine is stored using @@ -2889,9 +2779,7 @@ The hostname of the machine is stored using .LP If the class_hints argument is non-NULL, .PN XmbSetWMProperties -and -.PN Xutf8SetWMProperties -set the WM_CLASS property. +sets the WM_CLASS property. If the res_name member in the .PN XClassHint structure is set to the NULL pointer and the RESOURCE_NAME @@ -2904,34 +2792,24 @@ is substituted for res_name. .LP It is assumed that the supplied class_hints.res_name and argv, the RESOURCE_NAME environment variable, and the hostname of the machine -are in the encoding of the current locale. +are in the encoding of the locale announced for the LC_CTYPE category +(on POSIX-compliant systems, the LC_CTYPE, else LANG environment variable). The corresponding WM_CLASS, WM_COMMAND, and WM_CLIENT_MACHINE properties are typed according to the local host locale announcer. -No encoding conversion is performed for these strings prior to storage -in the properties. +No encoding conversion is performed prior to storage in the properties. .LP For clients that need to process the property text in a locale, .PN XmbSetWMProperties -and -.PN Xutf8SetWMProperties -set the WM_LOCALE_NAME property to be the name of the current locale. +sets the WM_LOCALE_NAME property to be the name of the current locale. The name is assumed to be in the Host Portable Character Encoding and is converted to STRING for storage in the property. .LP .PN XmbSetWMProperties -and -.PN Xutf8SetWMProperties can generate .PN BadAlloc and .PN BadWindow errors. -.LP -The function -.PN Xutf8SetWMProperties -is an XFree86 extension introduced in XFree86 4.0.2. Its presence is -indicated by the macro -.PN X_HAVE_UTF8_STRING . .sp .LP To set a window's standard window manager properties diff --git a/specs/X11/abstract.t b/specs/X11/abstract.t index ba651f2..b9c3ef1 100644 --- a/specs/X11/abstract.t +++ b/specs/X11/abstract.t @@ -1,4 +1,4 @@ -.\" $XFree86: xc/doc/specs/X11/abstract.t,v 1.3 2003/12/11 21:24:37 herrb Exp $ +.\" $XFree86: xc/doc/specs/X11/abstract.t,v 1.2 2003/07/09 15:27:26 tsi Exp $ .EH '''' .OH '''' .EF '''' @@ -10,9 +10,9 @@ .ce 6 \s+2\fBXlib \- C Language X Interface\fP\s-2 -\s+1\fBX Consortium Standard\fP\s-1 +\s+1\fBX Window System Standard\fP\s-1 -\s+1\fBX Version 11, Release 6.7 DRAFT\fP\s-1 +\s+1\fBX Version 11, Release 6.7\fP\s-1 .sp 6 .ce 4 \s-1James Gettys diff --git a/specs/X11/glossary b/specs/X11/glossary index 7aea056..a130928 100644 --- a/specs/X11/glossary +++ b/specs/X11/glossary @@ -1,6 +1,3 @@ -.\" -.\" $XFree86: xc/doc/specs/X11/glossary,v 1.2 2000/11/28 18:49:19 dawes Exp $ -.\" \& .sp 1 .ce 1 @@ -405,7 +402,7 @@ characters. The representations do not have to be of uniform length. Examples are an ISO2022 graphic set, a state-independent or state-dependent combination of graphic sets, possibly including control -sets, the X Compound Text encoding, and the UTF-8 ISO10646/Unicode encoding. +sets, and the X Compound Text encoding. .IP In X, encodings are identified by a string which appears as: the diff --git a/specs/X11/indexmacros.t b/specs/X11/indexmacros.t index e1b873d..1b616f8 100644 --- a/specs/X11/indexmacros.t +++ b/specs/X11/indexmacros.t @@ -1,3 +1,3 @@ -.eh '\fBXlib \- C Library\fP''\fBX11, Release 6.4\fP' -.oh '\fBXlib \- C Library\fP''\fBX11, Release 6.4\fP' +.eh '\fBXlib \- C Library\fP''\fBX11, Release 6.7\fP' +.oh '\fBXlib \- C Library\fP''\fBX11, Release 6.7\fP' .so index.pageno diff --git a/specs/XDMCP/xdmcp.ms b/specs/XDMCP/xdmcp.ms index 0728a53..ff7b42d 100644 --- a/specs/XDMCP/xdmcp.ms +++ b/specs/XDMCP/xdmcp.ms @@ -1,6 +1,7 @@ .\" Use eqn, tbl, and -ms .\" $Xorg: xdmcp.ms,v 1.3 2000/08/17 19:42:20 cpqbld Exp $ -.\" $XFree86: xc/doc/specs/XDMCP/xdmcp.ms,v 1.3 2003/11/22 04:50:59 dawes Exp $ +.\" $XdotOrg$ +.\" $Xorg: xdmcp.ms,v 1.3 2000/08/17 19:42:20 cpqbld Exp $ .EQ delim @@ define oc % "\\fR{\\fP" % @@ -17,7 +18,7 @@ define cc % "\\fR}\\fP" % .ce 7 \s+2\fBX Display Manager Control Protocol\fP\s-2 -\s+1\fBVersion 1.1 DRAFT +\s+1\fBVersion 1.1 X.Org Standard @@ -33,7 +34,7 @@ Massachusetts Institute of Technology\s+1 .br \& .sp 15 -Copyright \(co 1989, 2002 The Open Group +Copyright \(co 1989, 2004 The Open Group .sp 3 .LP Permission is hereby granted, free of charge, to any person obtaining a copy @@ -2056,13 +2057,10 @@ Other authentication protocols may be developed, depending on local needs. In an unsecure environment, the display must be able to verify that the source of the various packets is a trusted manager. These packets will contain authentication information. As an example of such a system, the -following discussion describes the "XDM-AUTHENTICATION-1" and -"XDM-AUTHENTICATION-2" authentication systems. The "XDM-AUTHENTICATION-1" -system uses a 56-bit shared private key, and 64 bits of -authentication data. "XDM-AUTHENTICATION-2" uses a 256 bit shared private key, -and 256 bits of authentication data. Associated example X authorization -protocol "XDM-AUTHORIZATION-1" and "XDM-AUTHORIZATION-2" will also be -discussed. The 56-bit key is represented +following discussion describes the "XDM-AUTHENTICATION-1" authentication +system. This system uses a 56-bit shared private key, and 64 bits of +authentication data. An associated example X authorization protocol +"XDM-AUTHORIZATION-1" will also be discussed. The 56-bit key is represented as a 64-bit number in network order (big endian). This means that the first octet in the representation will be zero. When incrementing a 64-bit value, the 8 octets of data will be interpreted in network order (big endian). @@ -2104,19 +2102,14 @@ sigma lineup = "per-session private key, generated by manager" beta lineup = "authorization data" .EN .LP -"XDM-AUTHENTICATION-1" encryption will use the Data Encryption Standard (DES, -FIPS 46-3); blocks shorter than 64 bits will be zero-filled on the right to -64 bits. Blocks longer than 64 bits will use block chaining: +Encryption will use the Data Encryption Standard (DES, FIPS 46-3); blocks +shorter than 64 bits will be zero-filled +on the right to 64 bits. Blocks longer than 64 bits will use block chaining: .EQ oc { D } cc sup kappa lineup = oc { D sub 1 } cc sup kappa " " oc { D sub 2 } " " xor " " oc { D sub 1 } cc sup kappa cc sup kappa .EN .LP -"XDM-AUTHENTICATION-2" encryption will use the Advanced Encryption Standard -(AES, FIPS-197); blocks shorter than 128 bits will be zero-filled on the right -to 128 bits. Blocks longer than 128 bits will use block chaining as shown -above. -.LP The display generates the first authentication data in the .PN Request packet: @@ -2176,15 +2169,6 @@ been received before, the current time is set to @T@. .IP \(bu 5 No packet containing the same pair (@N@, @T@) can have been received in the last 1200 seconds (20 minutes). -.LP -``XDM-AUTHORIZATION-2'' is identical to ``XDM-AUTHORIZATION-1'', except that -for TCP connections @N@ is 256 bits long and contains the 128 bit -IPv6 address of the client host followed by the 16 bit port number of the -client socket, with the remainder filled with zeros, and @T@ is extended to -64-bits. IPv4 addresses are represented as IPv4-mapped IPv6 addresses, with -an 80-bit prefix of zero bits, followed by a 16-byte value of 0xFFFF, -followed by the IPv4 address value, as defined in IETF RFC 2373. Formats for -other connections must be registered. .bp .EH '''' .OH '''' diff --git a/specs/XIM/xim.ms b/specs/XIM/xim.ms index c7f80c2..a7dea50 100644 --- a/specs/XIM/xim.ms +++ b/specs/XIM/xim.ms @@ -1,6 +1,6 @@ .\" $Xorg: xim.ms,v 1.3 2000/08/17 19:42:21 cpqbld Exp $ .\" To print this out, type tbl macros.t ThisFile | troff -ms -.\" $XFree86: xc/doc/specs/XIM/xim.ms,v 1.3 2001/01/17 16:57:42 dawes Exp $ +.\" $XFree86: xc/doc/specs/XIM/xim.ms,v 1.2 2000/12/14 17:48:58 dawes Exp $ .EH '''' .OH '''' .EF '''' @@ -16,7 +16,7 @@ .sp \fBX Consortium Standard\fP .sp -\fBX Version 11, Release 6.4\fP +\fBX Version 11, Release 6.7\fP .sp 3 .AU Masahiko Narita @@ -97,8 +97,8 @@ This documentation is provided as is without express or implied warranty. .ps 11 .nr PS 11 .bp 1 -.EH '\fBX Input Method Protocol\fP''\fBX11, Release 6.1\fP' -.OH '\fBX Input Method Protocol\fP''\fBX11, Release 6.1\fP' +.EH '\fBX Input Method Protocol\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Input Method Protocol\fP''\fBX11, Release 6.7\fP' .EF ''\fB % \fP'' .OF ''\fB % \fP'' .NH 1 diff --git a/specs/XLFD/xlfd.tbl.ms b/specs/XLFD/xlfd.tbl.ms index d761be4..17772b3 100644 --- a/specs/XLFD/xlfd.tbl.ms +++ b/specs/XLFD/xlfd.tbl.ms @@ -1,5 +1,6 @@ .\" Use tbl and -ms and macros.t -*- Nroff -*- .\" $Xorg: xlfd.tbl.ms,v 1.3 2000/08/17 19:42:22 cpqbld Exp $ +.\" $XdotOrg$ .nr sM 4 \" section on Matrix Transformations .nr sS 5 \" section on Scalable fonts .nr sP 6 \" section on Polymorphic font support @@ -19,7 +20,7 @@ \fBX Consortium Standard\fP -\fBX Version 11, Release 6.4\fP +\fBX Version 11, Release 6.7\fP .sp 6 \s+1Jim Flowers\s-1 .sp 6p @@ -35,7 +36,7 @@ .nr PS 9 .sp 8 .LP -\fIX Window System\fP is a trademark of X Consortium, Inc. +\fIX Window System\fP is a trademark of The Open Group. .LP Helvetica and Times are registered trademarks of Linotype Company. .LP @@ -88,8 +89,8 @@ This documentation is provided as is without express or implied warranty. .ps 11 .nr PS 11 .bp 1 -.EH '\fBX Logical Font Description Conventions\fP''\fBX11, Release 6.4\fP' -.OH '\fBX Logical Font Description Conventions\fP''\fBX11, Release 6.4\fP' +.EH '\fBX Logical Font Description Conventions\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Logical Font Description Conventions\fP''\fBX11, Release 6.7\fP' .EF ''\fB\\\\n(PN\fP'' .OF ''\fB\\\\n(PN\fP'' .NH 1 diff --git a/specs/XProtocol/X11.encoding b/specs/XProtocol/X11.encoding index 346a374..5233c2a 100644 --- a/specs/XProtocol/X11.encoding +++ b/specs/XProtocol/X11.encoding @@ -1,5 +1,5 @@ .\" $Xorg: X11.encoding,v 1.3 2000/08/17 19:42:23 cpqbld Exp $ -.\" $XFree86: xc/doc/specs/XProtocol/X11.encoding,v 1.2 2003/07/09 15:27:26 tsi Exp $ +.\" $XFree86$ \& .sp 1 .ps 11 diff --git a/specs/XProtocol/X11.protocol b/specs/XProtocol/X11.protocol index 0fe9615..140170e 100644 --- a/specs/XProtocol/X11.protocol +++ b/specs/XProtocol/X11.protocol @@ -1,9 +1,10 @@ .\" $Xorg: X11.protocol,v 1.4 $ +.\" $XdotOrg$ .\" .\" .\" .\" -.\" $XFree86: xc/doc/specs/XProtocol/X11.protocol,v 1.5 2003/12/11 21:24:37 herrb Exp $ +.\" $XFree86: xc/doc/specs/XProtocol/X11.protocol,v 1.4 2003/07/09 15:27:26 tsi Exp $ .EH '''' .OH '''' .EF '''' @@ -17,7 +18,7 @@ \s+1\fBX Consortium Standard\fP\s-1 -\s+1\fBX Version 11, Release 6.7 DRAFT\fP\s-1 +\s+1\fBX Version 11, Release 6.7\fP\s-1 .sp 6 .ce 5 \s-1Robert W. Scheifler @@ -31,7 +32,7 @@ X Consortium, Inc. .LP X Window System is a trademark of The Open Group. .LP -Copyright \(co 1986, 1987, 1988, 1994, 2002 The Open Group +Copyright \(co 1986, 1987, 1988, 1994, 2004 The Open Group .LP Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ``Software''), to deal @@ -124,8 +125,8 @@ Robert W. Scheifler X Consortium, Inc. .De .bp 1 -.EH '\fBX Protocol\fP''\fBX11, Release 6.7 DRAFT\fP' -.OH '\fBX Protocol\fP''\fBX11, Release 6.7 DRAFT\fP' +.EH '\fBX Protocol\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Protocol\fP''\fBX11, Release 6.7\fP' .EF ''\fB % \fP'' .OF ''\fB % \fP'' .NH 1 @@ -533,6 +534,7 @@ HOST T{ [family: .Pn { Internet , .PN InternetV6 , +.PN ServerInterpreted , .PN DECnet , .PN Chaos } T} @@ -941,7 +943,7 @@ requests in most applications. Note that they are predefined only in the sense of having numeric values, not in the sense of having required semantics. The core protocol imposes no semantics on these names, -but semantics are specified in other X.Org standards, +but semantics are specified in other X Window System standards, such as the \fIInter-Client Communication Conventions Manual\fP and the \fIX Logical Font Description Conventions\fP. .LP @@ -8708,16 +8710,6 @@ or an improper address length within a supported family results in a .PN Value error. .LP -Note that use of a host address in the ChangeHosts request is deprecated. -It is only useful when a host has a unique, constant address, a requirement -that is increasingly unmet as sites adopt dynamically assigned -addresses, network address translation gateways, IPv6 link local -addresses, and various other technologies. It also assumes all users of -a host share equivalent access rights, and as such has never been -suitable for many multi-user machine environments. Instead, more -secure forms of authentication, such as those based on shared secrets -or public key encryption, are recommended. -.LP For the Internet family, the address must be four bytes long. The address bytes are in standard IP order; @@ -8742,6 +8734,26 @@ the address must be two bytes long. The host number is always the first byte in the address, and the subnet number is always the second byte. The server performs no automatic swapping on the address bytes. +.LP +For the ServerInterpreted family, the address may be of any +length up to 65535 bytes. The address consists of two strings +of ASCII characters, separated by a byte with a value of 0. +The first string represents the type of address, and the second +string contains the address value. Address types and the syntax +for their associated values will be registered via the X.Org Registry. +Implementors who wish to add implementation specific types may register +a unique prefix with the X.Org registry to prevent namespace +collisions. +.LP +Use of a host address in the ChangeHosts request is deprecated. It is +only useful when a host has a unique, constant address, a requirement +that is increasingly unmet as sites adopt dynamically assigned +addresses, network address translation gateways, IPv6 link local +addresses, and various other technologies. It also assumes all users of +a host share equivalent access rights, and as such has never been +suitable for many multi-user machine environments. Instead, more +secure forms of authentication, such as those based on shared secrets +or public key encryption, are recommended. .sp .LP .sM diff --git a/specs/XProtocol/indexmacros.t b/specs/XProtocol/indexmacros.t index 3ceba91..2f7e703 100644 --- a/specs/XProtocol/indexmacros.t +++ b/specs/XProtocol/indexmacros.t @@ -1,3 +1,3 @@ -.eh '\s+1\fBX Protocol\fP''\fBX11, Release 6.4\fP\s-1' -.oh '\s+1\fBX Protocol\fP''\fBX11, Release 6.4\fP\s-1' +.eh '\s+1\fBX Protocol\fP''\fBX11, Release 6.7\fP\s-1' +.oh '\s+1\fBX Protocol\fP''\fBX11, Release 6.7\fP\s-1' .so index.pageno diff --git a/specs/Xaw/CH1 b/specs/Xaw/CH1 index 8262a86..f411717 100644 --- a/specs/Xaw/CH1 +++ b/specs/Xaw/CH1 @@ -3,7 +3,7 @@ .nr PS 11 .ds LH \fBAthena Widget Set\fP .ds CH -.ds RH \fBX11, Release 6.4\fP +.ds RH \fBX11, Release 6.7\fP .bp 1 .af PN 1 \& diff --git a/specs/Xaw/TPage_Credits b/specs/Xaw/TPage_Credits index 70418c6..fa0df8c 100644 --- a/specs/Xaw/TPage_Credits +++ b/specs/Xaw/TPage_Credits @@ -1,4 +1,5 @@ .\" $Xorg: TPage_Credits,v 1.3 2000/08/17 19:42:28 cpqbld Exp $ +.\" $XdotOrg$ .ds CH .ds CF .ps 11 @@ -10,7 +11,7 @@ \s+1\fBX Window System\fP\s-1 -\s+1\fBX Version 11, Release 6.4\fP\s-1 +\s+1\fBX Version 11, Release 6.7\fP\s-1 .sp 6 .ce 4 @@ -23,7 +24,7 @@ formerly MIT X Consortium .nr PS 9 .sp 8 .LP -X Window System is a trademark of X Consortium, Inc. +X Window System is a trademark of The Open Group. .LP Copyright \(co 1985, 1986, 1987, 1988, 1989, 1991, 1994 X Consortium .LP diff --git a/specs/Xaw/widg.idxmac.t b/specs/Xaw/widg.idxmac.t index e5a0527..1461abf 100644 --- a/specs/Xaw/widg.idxmac.t +++ b/specs/Xaw/widg.idxmac.t @@ -1,3 +1,3 @@ -.eh '\fBAthena Widget Set\fP''\fBX11, Release 6.4\fP' -.oh '\fBAthena Widget Set\fP''\fBX11, Release 6.4\fP' +.eh '\fBAthena Widget Set\fP''\fBX11, Release 6.7\fP' +.oh '\fBAthena Widget Set\fP''\fBX11, Release 6.7\fP' .so index.pageno diff --git a/specs/Xext/DPMS.ms b/specs/Xext/DPMS.ms index 5c87093..fac711e 100644 --- a/specs/Xext/DPMS.ms +++ b/specs/Xext/DPMS.ms @@ -1,5 +1,4 @@ .\" Use -ms and macros.t -.\" $XFree86: xc/doc/specs/Xext/DPMS.ms,v 1.2 1998/12/20 11:56:39 dawes Exp $ .EH '''' .OH '''' .EF '''' @@ -17,7 +16,7 @@ .ce 3 Version 1.0 X Project Team Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 6 .ce 4 Rob Lembree @@ -56,7 +55,7 @@ This extension provides X Protocol control over the VESA Display Power Management Signaling (DPMS) characteristics of video boards under control of the X Window System. .FS -1. \fIX Window System\fP is a trademark of X Consortium, Inc. +1. \fIX Window System\fP is a trademark of The Open Group. .FE .LP Traditionally, the X Window System has provided for both blanking and diff --git a/specs/Xext/DPMSLib.ms b/specs/Xext/DPMSLib.ms index 9b13a48..10ae2e6 100644 --- a/specs/Xext/DPMSLib.ms +++ b/specs/Xext/DPMSLib.ms @@ -1,4 +1,5 @@ .\" Use -ms and macros.t +.\" $XdotOrg$ .EH '''' .OH '''' .EF '''' @@ -16,7 +17,7 @@ .ce 3 Version 1.0 X Project Team Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 6 .ce 4 Rob Lembree @@ -55,7 +56,7 @@ This extension provides X Protocol control over the VESA Display Power Management Signaling (DPMS) characteristics of video boards under control of the X Window System. .FS -1. \fIX Window System\fP is a trademark of X Consortium, Inc. +1. \fIX Window System\fP is a trademark of The Open Group. .FE .LP Traditionally, the X Window System has provided for both blanking and diff --git a/specs/Xext/bigreq.ms b/specs/Xext/bigreq.ms index 06e56ed..a186ac2 100644 --- a/specs/Xext/bigreq.ms +++ b/specs/Xext/bigreq.ms @@ -1,5 +1,6 @@ .\" Use -ms and macros.t .\" $Xorg: bigreq.ms,v 1.3 2000/08/17 19:42:30 cpqbld Exp $ +.\" $XdotOrg$ .EH '''' .OH '''' .EF '''' @@ -14,7 +15,7 @@ .ce 3 Version 2.0 X Consortium Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 6 .ce 4 Bob Scheifler diff --git a/specs/Xext/buffer.ms b/specs/Xext/buffer.ms index 06a6013..8f4c085 100644 --- a/specs/Xext/buffer.ms +++ b/specs/Xext/buffer.ms @@ -3,7 +3,7 @@ .\" .\" .\" -.\" $XFree86: xc/doc/specs/Xext/buffer.ms,v 1.4 2001/01/17 16:57:43 dawes Exp $ +.\" $XFree86: xc/doc/specs/Xext/buffer.ms,v 1.3 2000/03/03 23:16:24 dawes Exp $ .TL Extending X for Double-Buffering, Multi-Buffering, and Stereo .AU diff --git a/specs/Xext/evi.ms b/specs/Xext/evi.ms index 52fe25f..0ae12b5 100644 --- a/specs/Xext/evi.ms +++ b/specs/Xext/evi.ms @@ -1,10 +1,11 @@ .\" Use -ms and macros.t .\" $Xorg: evi.ms,v 1.3 2000/08/17 19:42:31 cpqbld Exp $ +.\" $XdotOrg$ .\" .\" .\" .\" -.\" $XFree86: xc/doc/specs/Xext/evi.ms,v 1.4 2001/01/17 16:57:44 dawes Exp $ +.\" $XFree86: xc/doc/specs/Xext/evi.ms,v 1.3 2000/03/03 23:16:24 dawes Exp $ .EH '''' .OH '''' .EF '''' @@ -21,7 +22,7 @@ .ce 3 Version 1.0 X Project Team Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 6 .ce 4 Peter Daifuku diff --git a/specs/Xext/record.ms b/specs/Xext/record.ms index e536382..ffd5de1 100644 --- a/specs/Xext/record.ms +++ b/specs/Xext/record.ms @@ -1,6 +1,7 @@ .\" Record Extension Protocol, v1.13 .\" Use tbl, -ms and macros.t .\" $Xorg: record.ms,v 1.3 2000/08/17 19:42:36 cpqbld Exp $ +.\" $XdotOrg$ .\" ----------------------------------------------- .de Ip .IP \(bu 3 @@ -38,7 +39,7 @@ .sp \fBX Consortium Standard\fP .sp -\fBX Version 11, Release 6.4\fP +\fBX Version 11, Release 6.7\fP .sp 6 Martha Zimet Network Computing Devices, Inc. @@ -97,8 +98,8 @@ from the X Consortium. .nr LT 6.5i .nr FL 6.5i .ll 6.5i -.EH '\fBRecord Extension Protocol, Version 1.13\fP''\fBX11, Release 6.4\fP' -.OH '\fBX11, Release 6.4\fP''\fBRecord Extension Protocol, Version 1.13\fP' +.EH '\fBRecord Extension Protocol, Version 1.13\fP''\fBX11, Release 6.7\fP' +.OH '\fBX11, Release 6.7\fP''\fBRecord Extension Protocol, Version 1.13\fP' .bp 1 .EF ''\fB\\\\n(PN\fP'' .OF ''\fB\\\\n(PN\fP'' @@ -114,7 +115,7 @@ Several proposals have been written over the past few years that address some of the issues surrounding the recording and playback of user actions in the X Window System\**: .FS -\fIX Window System\fP is a trademark of X Consortium, Inc. +\fIX Window System\fP is a trademark of The Open Group. .FE .Ip \fISome Proposals for a Minimal X11 Testing Extension\fP, diff --git a/specs/Xext/recordlib.ms b/specs/Xext/recordlib.ms index 0d9a14d..41e5696 100644 --- a/specs/Xext/recordlib.ms +++ b/specs/Xext/recordlib.ms @@ -2,6 +2,7 @@ .\" Use -ms and macros.t .\" edited for DP edits and code consistency w/ core protocol/xlib 4/1/96 .\" $Xorg: recordlib.ms,v 1.3 2000/08/17 19:42:36 cpqbld Exp $ +.\" $XdotOrg$ .\" ----------------------------------------------- .de Ip .IP \(bu 5 @@ -41,7 +42,7 @@ .sp \fBX Consortium Standard\fP .sp -\fBX Version 11, Release 6.4\fP +\fBX Version 11, Release 6.7\fP .sp 6 Martha Zimet Network Computing Devices, Inc. @@ -100,8 +101,8 @@ from the X Consortium. .nr LT 6.5i .nr FL 6.5i .ll 6.5i -.EH '\fBX Record Extension Library, Version 1.13\fP''\fBX11, Release 6.4\fP' -.OH '\fBX11, Release 6.4\fP''\fBX Record Extension Library, Version 1.13\fP' +.EH '\fBX Record Extension Library, Version 1.13\fP''\fBX11, Release 6.7\fP' +.OH '\fBX11, Release 6.7\fP''\fBX Record Extension Library, Version 1.13\fP' .bp 1 .EF ''\fB\\\\n(PN\fP'' .OF ''\fB\\\\n(PN\fP'' diff --git a/specs/Xext/security.tex b/specs/Xext/security.tex index 269f363..103c5f9 100644 --- a/specs/Xext/security.tex +++ b/specs/Xext/security.tex @@ -50,7 +50,7 @@ \begin{document} -\title{Security Extension Specification\\Version 7.1\\X11 Release 6.4} +\title{Security Extension Specification\\Version 7.1\\X11 Release 6.7} \author{David P. Wiggins\\X Consortium, Inc.} \date{November 15, 1996} \maketitle diff --git a/specs/Xext/shape.ms b/specs/Xext/shape.ms index a39fd2a..e597718 100644 --- a/specs/Xext/shape.ms +++ b/specs/Xext/shape.ms @@ -1,5 +1,6 @@ .\" Use -ms and macros.t .\" $Xorg: shape.ms,v 1.3 2000/08/17 19:42:36 cpqbld Exp $ +.\" $XdotOrg$ .\" edited for DP edits and code consistency w/ core protocol/xlib 4/1/96 .EH '''' .OH '''' @@ -15,9 +16,9 @@ Shape Extension Protocol\fP\s-2 .sp 3 .ce 3 -Version 1.0 -X Consortium Standard -X Version 11, Release 6.4 +Version 1.0.1 +X.Org Standard +X Version 11, Release 6.7 .sp 6 .ce 4 \s-1Keith Packard @@ -27,7 +28,7 @@ MIT X Consortium .nr PS 9 .sp 8 .LP -Copyright \(co 1989 X Consortium +Copyright \(co 1989, 2004 The Open Group .LP Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ``Software''), to deal @@ -42,13 +43,13 @@ all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN +OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. .LP -Except as contained in this notice, the name of the X Consortium shall not be +Except as contained in this notice, the name of the Open Group shall not be used in advertising or otherwise to promote the sale, use or other dealings -in this Software without prior written authorization from the X Consortium. +in this Software without prior written authorization from the Open Group. .ps 10 .nr PS 10 .bp 1 @@ -736,7 +737,7 @@ Requests .PN ShapeInputSelected .sp 6p 1 CARD8 opcode - 1 6 shape opcode + 1 7 shape opcode 2 2 request length 4 WINDOW destination window .De @@ -759,7 +760,7 @@ Requests .PN ShapeGetRectangles .sp 6p 1 CARD8 opcode - 1 7 shape opcode + 1 8 shape opcode 2 3 request length 4 WINDOW window 1 SHAPE_KIND source kind @@ -877,3 +878,10 @@ the default clip region, the client clip region (if any) and the client bounding region (if any). Otherwise, the effective clip region is the same as the default clip region. .KE +.NH 1 +Revision History +.LP +1.0 - 1989 - Original Revision +.LP +1.0.1 - March 2004 - Corrected misnumbering of \fIShapeInputSelected\fP +and \fIShapeGetRectangles\fP requests in encoding section. diff --git a/specs/Xext/shapelib.ms b/specs/Xext/shapelib.ms index b42befc..cf5116e 100644 --- a/specs/Xext/shapelib.ms +++ b/specs/Xext/shapelib.ms @@ -1,5 +1,6 @@ .\" Use -ms and macros.t .\" $Xorg: shapelib.ms,v 1.3 2000/08/17 19:42:36 cpqbld Exp $ +.\" $XdotOrg$ .\" edited for DP edits and code consistency w/ core protocol/xlib 4/1/96 .EH '''' .OH '''' @@ -17,7 +18,7 @@ Shape Extension Library\fP\s-2 .ce 3 Version 1.0 X Consortium Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 6 .ce 4 \s-1Keith Packard diff --git a/specs/Xext/sync.tex b/specs/Xext/sync.tex index 22a2884..94ae6b8 100644 --- a/specs/Xext/sync.tex +++ b/specs/Xext/sync.tex @@ -1,4 +1,5 @@ % $Xorg: sync.tex,v 1.3 2000/08/17 19:42:37 cpqbld Exp $ +% $XdotOrg$ % % Copyright 1991 by Olivetti Research Limited, Cambridge, England and % Digital Equipment Corporation, Maynard, Massachusetts. @@ -20,7 +21,7 @@ % IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT % OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. % -% $XFree86: xc/doc/specs/Xext/sync.tex,v 1.3 2001/04/27 12:58:27 dawes Exp $ +% $XFree86$ %\documentstyle[a4]{article} \documentstyle{article} @@ -84,7 +85,7 @@ {\large X Synchronization Extension Protocol}\\[10pt] {\large Version 3.0}\\[15pt] {\large X Consortium Standard}\\[15pt] -{\large X Version 11, Release 6.4}\\[15pt] +{\large X Version 11, Release 6.7}\\[15pt] {\it Tim Glauert}\\[0pt] {\tt thg@cam-orl.co.uk}\\[0pt] {\bf Olivetti Research / MultiWorks}\\[5pt] diff --git a/specs/Xext/synclib.tex b/specs/Xext/synclib.tex index d48d1d7..de2ef4a 100644 --- a/specs/Xext/synclib.tex +++ b/specs/Xext/synclib.tex @@ -1,4 +1,5 @@ % $Xorg: synclib.tex,v 1.3 2000/08/17 19:42:37 cpqbld Exp $ +% $XdotOrg$ % % Copyright 1991 by Olivetti Research Limited, Cambridge, England and % Digital Equipment Corporation, Maynard, Massachusetts. @@ -82,7 +83,7 @@ {\large X Synchronization Extension Library}\\[10pt] {\large Version 3.0}\\[15pt] {\large X Consortium Standard}\\[15pt] -{\large X Version 11, Release 6.4}\\[15pt] +{\large X Version 11, Release 6.7}\\[15pt] {\it Tim Glauert}\\[0pt] {\tt thg@cam-orl.co.uk}\\[0pt] {\bf Olivetti Research / MultiWorks}\\[5pt] diff --git a/specs/Xext/tog-cup.ms b/specs/Xext/tog-cup.ms index 9a44753..9b9427f 100644 --- a/specs/Xext/tog-cup.ms +++ b/specs/Xext/tog-cup.ms @@ -1,5 +1,6 @@ .\" Use -ms and macros.t .\" $Xorg: tog-cup.ms,v 1.3 2000/08/17 19:42:37 cpqbld Exp $ +.\" $XdotOrg$ .EH '''' .OH '''' .EF '''' @@ -16,7 +17,7 @@ .ce 3 Version 1.0 X Project Team Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 6 .ce 4 Kaleb S. KEITHLEY diff --git a/specs/Xext/xc-misc.ms b/specs/Xext/xc-misc.ms index 464b86e..ecf74e0 100644 --- a/specs/Xext/xc-misc.ms +++ b/specs/Xext/xc-misc.ms @@ -1,5 +1,6 @@ .\" Use -ms and macros.t .\" $Xorg: xc-misc.ms,v 1.3 2000/08/17 19:42:37 cpqbld Exp $ +.\" $XdotOrg$ .EH '''' .OH '''' .EF '''' @@ -14,7 +15,7 @@ .ce 3 Version 1.1 X Consortium Standard -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 6 .ce 4 Bob Scheifler diff --git a/specs/Xi/library.ms b/specs/Xi/library.ms index e2f5522..0ceaad8 100644 --- a/specs/Xi/library.ms +++ b/specs/Xi/library.ms @@ -1,4 +1,5 @@ .\" $Xorg: library.ms,v 1.3 2000/08/17 19:42:38 cpqbld Exp $ +.\" $XdotOrg$ .\" Input Extension now coded to macros.t .\" edited for DP edits and code consistency w/ core protocol/xlib 4/5/96 .EH '''' @@ -16,7 +17,7 @@ .sp 2 X Consortium Standard .sp 1 -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 16 .ps 15 \fBMark Patrick\0\0\0\0Ardent Computer @@ -61,12 +62,12 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 3 -\fIX Window System\fP is a trademark of X Consortium, Inc. +\fIX Window System\fP is a trademark of The Open Group. .ps .vs .bp 1 -.EH '\fBX Input Extension Library\fP''\fBX11, Release 6.4\fP' -.OH '\fBX Input Extension Library\fP''\fBX11, Release 6.4\fP' +.EH '\fBX Input Extension Library\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Input Extension Library\fP''\fBX11, Release 6.7\fP' .EF ''\fB\\\\n(PN\fP'' .OF ''\fB\\\\n(PN\fP'' .\" Force the heading counter for level 1 to one diff --git a/specs/Xi/porting.ms b/specs/Xi/porting.ms index 0298957..b4792cb 100644 --- a/specs/Xi/porting.ms +++ b/specs/Xi/porting.ms @@ -1,4 +1,3 @@ -.\" $XFree86: xc/doc/specs/Xi/porting.ms,v 1.2 2000/12/04 23:25:59 dawes Exp $ .\" Input Extension Porting Document .EH '''' .OH '''' @@ -11,7 +10,7 @@ \fBX11 Input Extension Porting Document .sp 2 .ps 12 -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 16 .ps 15 George Sachs\0\0\0\0Hewlett-Packard @@ -56,10 +55,10 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 3 -\fIX Window System\fP is a trademark of X Consortium, Inc. +\fIX Window System\fP is a trademark of The Open Group. .bp 1 -.EH '\fBX Input Extension Porting Document\fP''\fBX11, Release 6.4\fP' -.OH '\fBX Input Extension Porting Document\fP''\fBX11, Release 6.4\fP' +.EH '\fBX Input Extension Porting Document\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Input Extension Porting Document\fP''\fBX11, Release 6.7\fP' .EF ''\fB % \fP'' .OF ''\fB % \fP'' .\" Force the heading counter for level 1 to one diff --git a/specs/Xi/protocol.ms b/specs/Xi/protocol.ms index 50c56c9..105200c 100644 --- a/specs/Xi/protocol.ms +++ b/specs/Xi/protocol.ms @@ -1,4 +1,5 @@ .\" $Xorg: protocol.ms,v 1.3 2000/08/17 19:42:40 cpqbld Exp $ +.\" $XdotOrg$ .\" Input Extension .EH '''' .OH '''' @@ -17,7 +18,7 @@ Version 1.0 .sp 1 X Consortium Standard .sp 1 -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 16 .ps 15 \fBMark Patrick\0\0\0\0Ardent Computer @@ -62,12 +63,12 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 3 -\fIX Window System\fP is a trademark of X Consortium, Inc. +\fIX Window System\fP is a trademark of The Open Group. .ps .vs .bp 1 -.EH '\fBX Input Extension Protocol Specification\fP''\fBX11, Release 6.4\fP' -.OH '\fBX Input Extension Protocol Specification\fP''\fBX11, Release 6.4\fP' +.EH '\fBX Input Extension Protocol Specification\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Input Extension Protocol Specification\fP''\fBX11, Release 6.7\fP' .EF ''\fB\\\\n(PN\fP'' .OF ''\fB\\\\n(PN\fP'' .\" Force the heading counter for level 1 to one diff --git a/specs/Xmu/Xmu.ms b/specs/Xmu/Xmu.ms index dadbfb8..c6ac607 100644 --- a/specs/Xmu/Xmu.ms +++ b/specs/Xmu/Xmu.ms @@ -1,11 +1,11 @@ -.\" -.\" $XFree86: xc/doc/specs/Xmu/Xmu.ms,v 1.2 2000/11/28 18:49:20 dawes Exp $ +.\" $XdotOrg$ +.\" $XFree86$ .\" .sp 8 .ce 2 \s+2\fBXmu Library\fP\s-2 .sp 6p -X Version 11, Release 6.4 +X Version 11, Release 6.7 .sp 1 .ce 1 ``\fIDon't ask.\fP'' @@ -34,7 +34,7 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 3 -\fIX Window System\fP is a trademark of X Consortium, Inc. +\fIX Window System\fP is a trademark of The Open Group. .bp .NH 1 Introduction diff --git a/specs/Xserver/analysis.tex b/specs/Xserver/analysis.tex index 87edc71..a2eeabd 100644 --- a/specs/Xserver/analysis.tex +++ b/specs/Xserver/analysis.tex @@ -2,7 +2,7 @@ \setlength{\parindent}{0 pt} \setlength{\parskip}{6pt} -% $XFree86: xc/doc/specs/Xserver/analysis.tex,v 1.2 2001/04/19 23:36:35 dawes Exp $ +% $XFree86$ \begin{document} diff --git a/specs/Xserver/secint.tex b/specs/Xserver/secint.tex index 3e17dba..56aac6c 100644 --- a/specs/Xserver/secint.tex +++ b/specs/Xserver/secint.tex @@ -2,7 +2,7 @@ \setlength{\parindent}{0 pt} \setlength{\parskip}{6pt} -% $XFree86: xc/doc/specs/Xserver/secint.tex,v 1.2 2001/04/19 23:36:35 dawes Exp $ +% $XFree86$ \begin{document} diff --git a/specs/Xt/strings.mit b/specs/Xt/strings.mit index 8df4a48..c40df4f 100644 --- a/specs/Xt/strings.mit +++ b/specs/Xt/strings.mit @@ -6,7 +6,7 @@ .ds xL Xlib \(em C Language X Interface .ds xC Inter-Client Communication Conventions Manual .ds xP X Window System Protocol -.ds Rn 6.4 +.ds Rn 6.7 .ds Vn 2.2 .ds oI Must be of class Object or any subclass thereof. .ds rI Must be of class RectObj or any subclass thereof. diff --git a/specs/i18n/Framework.ms b/specs/i18n/Framework.ms index 9366185..de727a3 100644 --- a/specs/i18n/Framework.ms +++ b/specs/i18n/Framework.ms @@ -1,6 +1,7 @@ .\" $Xorg: Framework.ms,v 1.3 2000/08/17 19:42:49 cpqbld Exp $ +.\" $XdotOrg$ .\" To print this out, type tbl macros.t ThisFile | troff -ms -.\" $XFree86: xc/doc/specs/i18n/Framework.ms,v 1.5 2001/02/09 00:02:52 dawes Exp $ +.\" $XFree86: xc/doc/specs/i18n/Framework.ms,v 1.4 2001/01/17 16:57:45 dawes Exp $ .EH '''' .OH '''' .EF '''' @@ -62,12 +63,12 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 3 -\fIX Window System\fP is a trademark of X Consortium, Inc. +\fIX Window System\fP is a trademark of The Open Group. .ps 11 .nr PS 11 .bp 1 -.EH '\fBSample Implementation Frame Work\fP''\fBX11, Release 6.4\fP' -.OH '\fBSample Implementation Frame Work\fP''\fBX11, Release 6.4\fP' +.EH '\fBSample Implementation Frame Work\fP''\fBX11, Release 6.7\fP' +.OH '\fBSample Implementation Frame Work\fP''\fBX11, Release 6.7\fP' .EF ''\fB % \fP'' .OF ''\fB % \fP'' .NH 1 diff --git a/specs/i18n/LocaleDB.ms b/specs/i18n/LocaleDB.ms index f83ccc7..2e3f3d0 100644 --- a/specs/i18n/LocaleDB.ms +++ b/specs/i18n/LocaleDB.ms @@ -1,4 +1,5 @@ .\" $Xorg: LocaleDB.ms,v 1.3 2000/08/17 19:42:49 cpqbld Exp $ +.\" $XdotOrg$ .\" To print this out, type tbl macros.t ThisFile | troff -ms .EH '''' .OH '''' @@ -66,13 +67,13 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 3 -\fIX Window System\fP is a trademark of X Consortium, Inc. +\fIX Window System\fP is a trademark of The Open Group. .LP .bp 1 .ps 11 .nr PS 11 -.EH '\fBX Locale Database Definition\fP''\fBX11, Release 6.4\fP' -.OH '\fBX Locale Database Definition\fP''\fBX11, Release 6.4\fP' +.EH '\fBX Locale Database Definition\fP''\fBX11, Release 6.7\fP' +.OH '\fBX Locale Database Definition\fP''\fBX11, Release 6.7\fP' .EF ''\fB % \fP'' .OF ''\fB % \fP'' .NH 1 diff --git a/specs/i18n/Trans.ms b/specs/i18n/Trans.ms index 40ed2e3..92ec898 100644 --- a/specs/i18n/Trans.ms +++ b/specs/i18n/Trans.ms @@ -1,4 +1,5 @@ .\" $Xorg: Trans.ms,v 1.3 2000/08/17 19:42:49 cpqbld Exp $ +.\" $XdotOrg$ .\" To print this out, type tbl macros.t This File | troff -ms .EH '''' .OH '''' @@ -16,7 +17,7 @@ .sp \fBRevision 0.1\fP .sp -\fBX Version 11, Release 6.4\fP +\fBX Version 11, Release 6.7\fP .sp 3 .AU Takashi Fujiwara @@ -71,12 +72,12 @@ Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. .sp 3 -\fIX Window System\fP is a trademark of X Consortium, Inc. +\fIX Window System\fP is a trademark of The Open Group. .ps 11 .nr PS 11 .bp 1 -.EH '\fBXIM Transport Specification\fP''\fBX11, Release 6.4\fP' -.OH '\fBXIM Transport Specification\fP''\fBX11, Release 6.4\fP' +.EH '\fBXIM Transport Specification\fP''\fBX11, Release 6.7\fP' +.OH '\fBXIM Transport Specification\fP''\fBX11, Release 6.7\fP' .EF ''\fB % \fP'' .OF ''\fB % \fP'' .NH 1 diff --git a/specs/rstart/rstart.ms b/specs/rstart/rstart.ms index 2800442..e243fdc 100644 --- a/specs/rstart/rstart.ms +++ b/specs/rstart/rstart.ms @@ -1,4 +1,4 @@ -.\" $XFree86: xc/doc/specs/rstart/rstart.ms,v 1.2 2001/05/29 18:14:12 dawes Exp $ +.\" $XFree86$ .ds iL Brown .ds iI J. .ds iO Quarterdeck Office Systems diff --git a/specs/specindex.html b/specs/specindex.html index efb630e..c7dd212 100644 --- a/specs/specindex.html +++ b/specs/specindex.html @@ -1,6 +1,6 @@ <html> <head> - <title>XFree86(TM): Documentation: Specification Documents</title> + <title>The X.Org Foundation: Documentation: Specification Documents</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <style type="text/css"> body { @@ -14,7 +14,7 @@ </head> <body> - <h2>XFree86™ Documentation: Specification and Related Documents</h2> + <h2>X.Org Documentation: Specification and Related Documents</h2> <p><i>The formatting of some of the HTML versions of these documents may have some problems. In such cases refer to the PDF versions.</i></p> @@ -100,14 +100,6 @@ <li><a href="xfs-design.html">Font Server Design</a> <a href="../PDF/xfs-design.pdf">[PDF]</a></li> </ul> - <h3>Xtest Suite</h3> - - <ul> - <li>Xtest User Guide <a href="../PDF/xtest-userguide.pdf">[PDF]</a></li> - <li>Xtest Programmers Guide <a href="../PDF/xtest-progguide.pdf">[PDF]</a></li> - <li>Xtest Release Notes <a href="../PDF/xtest-relnotes.pdf">[PDF]</a></li> - </ul> - <h3>Miscellaneous</h3> <ul> @@ -115,7 +107,6 @@ <li><a href="ctlseqs.html">Xterm control sequences</a> <a href="../PDF/ctlseqs.pdf">[PDF]</a></li> </ul> - <!-- $XFree86: xc/doc/specs/specindex.html,v 1.5 2003/12/06 19:24:38 dawes Exp $ --> </body> </html> diff --git a/specs/xtrans/Xtrans.mm b/specs/xtrans/Xtrans.mm index 4176ec0..0d39e7d 100644 --- a/specs/xtrans/Xtrans.mm +++ b/specs/xtrans/Xtrans.mm @@ -1,4 +1,4 @@ -.\" $XFree86: xc/doc/specs/xtrans/Xtrans.mm,v 1.3 2003/11/16 16:40:19 herrb Exp $ +.\" $XFree86: xc/doc/specs/xtrans/Xtrans.mm,v 1.2 2003/07/09 15:27:27 tsi Exp $ '\".nr Ej 1 .PH "'''" .ce |