syncing files from 3.0 into HEAD again

(This used to be commit bca0bba209255d0effbae6a3d3b6d298f0952c3a)

1 files changed, 1069 insertions, 1219 deletions

diff --git a/docs/docbook/projdoc/CUPS-printing.xml b/docs/docbook/projdoc/CUPS-printing.xml
index 252da6f4ef..945092d413 100644
--- a/docs/docbook/projdoc/CUPS-printing.xml
+++ b/docs/docbook/projdoc/CUPS-printing.xml
@@ -5,7 +5,7 @@
 	<author>
 		<firstname>Kurt</firstname><surname>Pfeifle</surname>
 		<affiliation>
-			<orgname> Danka Deutschland GmbH </orgname>
+			<orgname>Danka Deutschland GmbH </orgname>
                         <address><email>kpfeifle@danka.de</email></address>
 		</affiliation>
 	</author>
@@ -17,6 +17,8 @@
 		<contrib>drawings</contrib>
 	</author>
 
+	<author>&person.jelmer;<contrib>drawings</contrib></author>
+
 	<pubdate> (3 June 2003) </pubdate>
 </chapterinfo>
 
@@ -30,20 +32,15 @@
 		<title>Features and Benefits</title>
 
 		<para>
-			The Common Unix Print System (<ulink
-				url="http://www.cups.org/">CUPS</ulink>) has become very popular. All
-			big Linux distributions now ship it as their default printing
-			system. But to many it is still a very mystical tool.  Normally it
-			"just works" (TM). People tend to regard it as a sort of "black box",
-			which they don't want to look into, as long as it works OK. But once
+			The Common UNIX Print System (<ulink
+			url="http://www.cups.org/">CUPS</ulink>) has become very popular. All
+			major Linux distributions now ship it as their default printing
+			system. To many it is still a very mystical tool.  Mostly, it
+			"just works" (TM). People tend to regard it as a "black box"
+			which they don't want to look into, as long as it works. But once
 			there is a little problem, they are in trouble to find out where to
-			start debugging it. Also, even the most recent and otherwise excellent
-			printed Samba documentation has only limited attention paid to CUPS
-			printing, leaving out important pieces or even writing plain wrong
-			things about it. This demands rectification.  But before you dive into
-			this chapter, make sure that you don't forget to refer to the
-			"Classical Printing" chapter also. It contains a lot of information
-			that is relevant for CUPS too.
+			start debugging it.  Refer to the "Classical Printing" chapter also, it
+			contains a lot of information that is relevant for CUPS.
 		</para>
 
 		<para>
@@ -51,12 +48,10 @@
 			basic functions may be grasped quite easily, they are also
 			new. Because they are different from other, more traditional printing
 			systems, it is best to try and not apply any prior knowledge about
-			printing upon this new system. Rather try to start understand CUPS
-			from the beginning. This documentation will lead you here to a
-			complete understanding of CUPS, if you study all of the material
-			contained. But lets start with the most basic things first. Maybe this
-			is all you need for now. Then you can skip most of the other
-			paragraphs.
+			printing upon this new system. Rather, try to understand CUPS
+			from the beginning. This documentation will lead you to a
+			complete understanding of CUPS. Let's start with the most basic
+			things first.
 		</para>
 
 	</sect2>
@@ -71,11 +66,10 @@
 			and IETF (<emphasis>Internet Engineering Task Force</emphasis>)
 			standard for network printing. Many of its functions can be managed
 			remotely (or locally) via a web browser (giving you a
-			platform-independent access to the CUPS print server). In addition it
-			has the traditional commandline and several more modern GUI interfaces
+			platform-independent access to the CUPS print server). Additionally, it
+			has the traditional command line and several more modern GUI interfaces
 			(GUI interfaces developed by 3rd parties, like KDE's
-			overwhelming <ulink
-				url="http://printing.kde.org/">KDEPrint</ulink>).
+			overwhelming <ulink url="http://printing.kde.org/">KDEPrint</ulink>).
 		</para>
 
 		<para>
@@ -95,31 +89,24 @@
 	<title>Basic Configuration of CUPS support</title>
 
 	<para>
-		Printing with CUPS in the most basic <filename>smb.conf</filename>
-		setup in Samba 3.0 (as was true for 2.2.x) only needs two
-		settings: <parameter>printing = cups</parameter> and <parameter>printcap
-			= cups</parameter>. CUPS itself doesn't need a printcap file
-		anymore. However, the <filename>cupsd.conf</filename> configuration
-		file knows two related directives: they control if such a file should
-		be automatically created and maintained by CUPS for the convenience of
-		third party applications (example: <parameter>Printcap
-			/etc/printcap</parameter> and <parameter>PrintcapFormat
-			BSD</parameter>). These legacy programs often require the existence of
-		printcap file containing printernames or they will refuse to
-		print. Make sure CUPS is set to generate and maintain a printcap! For
-		details see <command>man cupsd.conf</command> and other CUPS-related
-		documentation, like the wealth of documents on your CUPS server
-		itself: <ulink
-			url="http://localhost:631/documentation.html">http://localhost:631/documentation.html</ulink>.
+		Printing with CUPS in the most basic &smb.conf; setup in Samba 3.0 (as was true for 2.2.x) only needs two
+		settings: <smbconfoption><name>printing</name><value>cups</value></smbconfoption> and
+		<smbconfoption><name>printcap</name><value>cups</value></smbconfoption>. CUPS does not need a printcap file.
+		However, the <filename>cupsd.conf</filename> configuration file knows of two related directives that control
+		how such a file will be automatically created and maintained by CUPS for the convenience of third party
+		applications (example: <parameter>Printcap /etc/printcap</parameter> and <parameter>PrintcapFormat BSD</parameter>).
+		Legacy programs often require the existence of a printcap file containing printer names or they will refuse to
+		print. Make sure CUPS is set to generate and maintain a printcap file! For details see
+		<command>man cupsd.conf</command> and other CUPS-related documentation, like the wealth of documents on your CUPS server
+		itself: <ulink noescape="1" url="http://localhost:631/documentation.html">http://localhost:631/documentation.html</ulink>.
 	</para>
 
 	<sect2>
 		<title>Linking of smbd with libcups.so</title>
 
 		<para>
-			Samba has a very special relationship to CUPS. The reason is: Samba
-			can be compiled with CUPS library support. Most recent installations
-			have this support enabled, and per default CUPS linking is compiled
+			Samba has a very special relationship to CUPS. Samba can be compiled with CUPS library support.
+			Most recent installations have this support enabled. Per default CUPS linking is compiled
 			into smbd and other Samba binaries. Of course, you can use CUPS even
 			if Samba is not linked against <filename>libcups.so</filename> -- but
 			there are some differences in required or supported configuration
@@ -127,69 +114,65 @@
 		</para>
 
 		<para>
-			If SAMBA is compiled against libcups, then <parameter>printcap =
-				cups</parameter> uses the CUPS API to list printers, submit jobs,
-			query queues, etc.  Otherwise it maps to the System V commands with an
-			additional <command>-oraw</command> option for printing. On a Linux
-			system, you can use the <command>ldd</command> utility to find out
-			details (ldd may not be present on other OS platforms, or its function
-			may be embodied by a different command):
+			When Samba is compiled against libcups, <smbconfoption><name>printcap</name><value>cups</value></smbconfoption>
+			uses the CUPS API to list printers, submit jobs, query queues, etc.  Otherwise it maps to the System V
+			commands with an additional <command>-oraw</command> option for printing. On a Linux
+			system, you can use the <command>ldd</command> utility to find out details (ldd may not be present on
+			other OS platforms, or its function may be embodied by a different command):
 		</para>
 
-		<para><screen>
-				transmeta:/home/kurt # ldd `which smbd`
-				libssl.so.0.9.6 =&gt; /usr/lib/libssl.so.0.9.6 (0x4002d000)
-				libcrypto.so.0.9.6 =&gt; /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
-				libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
-				[....]
-		</screen></para>
+<para><screen>
+&rootprompt;<userinput>ldd `which smbd`</userinput>
+libssl.so.0.9.6 =&gt; /usr/lib/libssl.so.0.9.6 (0x4002d000)
+libcrypto.so.0.9.6 =&gt; /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
+libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
+[....]
+</screen></para>
 
 		<para>
-			The line <computeroutput>libcups.so.2 =&gt; /usr/lib/libcups.so.2
-				(0x40123000)</computeroutput> shows there is CUPS support compiled
-			into this version of Samba. If this is the case, and printing = cups
-			is set, then <emphasis>any otherwise manually set print command in
-				<filename>smb.conf</filename> is ignored</emphasis>. This is an
-			important point to remember!
+			The line <computeroutput>libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)</computeroutput> shows
+			there is CUPS support compiled into this version of Samba. If this is the case, and printing = cups
+			is set, then <emphasis>any otherwise manually set print command in &smb.conf; is ignored</emphasis>.
+			This is an important point to remember!
 		</para>
 
-		<tip><para> Should you require -- for any reason -- to set your own
-				print commands, you can still do this by setting <parameter>printing =
-					sysv</parameter>. However, you'll loose all the benefits from the
-				close CUPS/Samba integration. You are on your own then to manually
-				configure the rest of the printing system commands (most important:
-				<parameter>print command</parameter>; other commands are
-				<parameter>lppause command, lpresume command, lpq command, lprm
-					command, queuepause command </parameter> and <parameter>queue resume
-					command</parameter>).</para></tip>
+		<tip><para> Should it be necessary, for any reason, to set your own print commands, you can do this by setting
+		<smbconfoption><name>printing</name><value>sysv</value></smbconfoption>. However, you will loose all the benefits
+		of tight CUPS/Samba integration. When you do this you must manually configure the printing system commands
+		(most important: <smbconfoption><name>print command</name></smbconfoption>; other commands are
+				<smbconfoption><name>lppause command</name></smbconfoption>,
+				<smbconfoption><name>lpresume command</name></smbconfoption>,
+				<smbconfoption><name>lpq command</name></smbconfoption>,
+				<smbconfoption><name>lprm command</name></smbconfoption>,
+				<smbconfoption><name>queuepause command</name></smbconfoption> and
+				<smbconfoption><name>queue resume command</name></smbconfoption>).</para></tip>
 	</sect2>
 
 	<sect2>
-		<title>Simple <filename>smb.conf</filename> Settings for CUPS</title>
+		<title>Simple &smb.conf; Settings for CUPS</title>
 
 		<para>
-			To summarize, here is the simplest printing-related setup
-			for <filename>smb.conf</filename> to enable basic CUPS support:
+			To summarize, here is the simplest printing-related setup for &smb.conf; to enable basic CUPS support:
 		</para>
 
-		<para><screen>
-
-				[global]
-				load printers = yes
-				printing = cups
-				printcap name = cups
-
-				[printers]
-				comment = All Printers
-				path = /var/spool/samba
-				browseable = no
-				public = yes
-				guest ok = yes
-				writable = no
-				printable = yes
-				printer admin = root, @ntadmins
-
-		</screen></para>
+		<para><smbconfexample>
+		<title>Simplest printing-related smb.conf</title>
+		<smbconfsection>[global]</smbconfsection>
+		<smbconfoption><name>load printers</name><value>yes</value></smbconfoption>
+		<smbconfoption><name>printing</name><value>cups</value></smbconfoption>
+		<smbconfoption><name>printcap name</name><value>cups</value></smbconfoption>
+
+		<smbconfsection>[printers]</smbconfsection>
+		<smbconfoption><name>comment</name><value>All Printers</value></smbconfoption>
+		<smbconfoption><name>path</name><value>/var/spool/samba</value></smbconfoption>
+		<smbconfoption><name>browseable</name><value>no</value></smbconfoption>
+		<smbconfoption><name>public</name><value>yes</value></smbconfoption>
+		<smbconfoption><name>guest ok</name><value>yes</value></smbconfoption>
+		<smbconfoption><name>writable</name><value>no</value></smbconfoption>
+		<smbconfoption><name>printable</name><value>yes</value></smbconfoption>
+		<smbconfoption><name>printer admin</name><value>root, @ntadmins</value></smbconfoption>
+
+		</smbconfexample></para>
 
 		<para>
 			This is all you need for basic printing setup for CUPS. It will print
@@ -210,63 +193,57 @@
 	</sect2>
 
 <sect2>
-<title>More complex <filename>smb.conf</filename> Settings for
+<title>More complex &smb.conf; Settings for
 CUPS</title>
 
 <para>
 Here is a slightly more complex printing-related setup
-for <filename>smb.conf</filename>. It enables general CUPS printing
+for &smb.conf;. It enables general CUPS printing
 support for all printers, but defines one printer share which is set
 up differently.
 </para>
 
-<para><screen>
-<![CDATA[
- [global]
-         printing = cups
-         printcap name = cups
-         load printers = yes
-
- [printers]
-         comment = All Printers
-         path = /var/spool/samba
-         public = yes
-         guest ok = yes
-         writable = no
-         printable = yes
-         printer admin = root, @ntadmins
- 
- [special_printer]
-         comment = A special printer with his own settings
-         path = /var/spool/samba-special
-         printing = sysv
-         printcap = lpstat
-         print command = echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ;\
-                         echo "     `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ;\
-                         echo "     `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log :\
-                         rm %f
-         public = no
-         guest ok = no
-         writeable = no
-         printable = yes
-         printer admin = kurt
-         hosts deny = 0.0.0.0
-         hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60
-]]>
-</screen></para>
-
-<para>
-This special share is only there for my testing purposes. It doesn't
-even write the print job to a file. It just logs the job parameters
-known to Samba into the <filename>/tmp/smbprn.log</filename> file and
-deletes the jobfile. Moreover, the <parameter>printer
-admin</parameter> of this share is "kurt" (not the "@ntadmins" group);
-guest access is not allowed; the share isn't announced in Network
-Neighbourhood (so you need to know it is there), and it is only
-allowing access from three hosts. To prevent CUPS kicking in and
-taking over the print jobs for that share, we need to set
-<parameter>printing = sysv</parameter> and <parameter>printcap =
-lpstat</parameter>.
+<para><smbconfexample>
+<title>Overriding global CUPS settings for one printer</title>
+<smbconfsection>[global]</smbconfsection>
+<smbconfoption><name>printing</name><value>cups</value></smbconfoption>
+<smbconfoption><name>printcap name</name><value>cups</value></smbconfoption>
+<smbconfoption><name>load printers</name><value>yes</value></smbconfoption>
+
+<smbconfsection>[printers]</smbconfsection>
+<smbconfoption><name>comment</name><value>All Printers</value></smbconfoption>
+<smbconfoption><name>path</name><value>/var/spool/samba</value></smbconfoption>
+<smbconfoption><name>public</name><value>yes</value></smbconfoption>
+<smbconfoption><name>guest ok</name><value>yes</value></smbconfoption>
+<smbconfoption><name>writable</name><value>no</value></smbconfoption>
+<smbconfoption><name>printable</name><value>yes</value></smbconfoption>
+<smbconfoption><name>printer admin</name><value>root, @ntadmins</value></smbconfoption>
+
+<smbconfsection>[special_printer]</smbconfsection>
+<smbconfoption><name>comment</name><value>A special printer with his own settings</value></smbconfoption>
+<smbconfoption><name>path</name><value>/var/spool/samba-special</value></smbconfoption>
+<smbconfoption><name>printing</name><value>sysv</value></smbconfoption>
+<smbconfoption><name>printcap</name><value>lpstat</value></smbconfoption>
+<smbconfoption><name>print command</name><value>echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; \</value></smbconfoption>
+<member><parameter>echo "     `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; \</parameter></member>
+<member><parameter>echo "     `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log : rm %f</parameter></member>
+<smbconfoption><name>public</name><value>no</value></smbconfoption>
+<smbconfoption><name>guest ok</name><value>no</value></smbconfoption>
+<smbconfoption><name>writeable</name><value>no</value></smbconfoption>
+<smbconfoption><name>printable</name><value>yes</value></smbconfoption>
+<smbconfoption><name>printer admin</name><value>kurt</value></smbconfoption>
+<smbconfoption><name>hosts deny</name><value>0.0.0.0</value></smbconfoption>
+<smbconfoption><name>hosts allow</name><value>turbo_xp, 10.160.50.23, 10.160.51.60</value></smbconfoption>
+</smbconfexample></para>
+
+<para>
+This special share is only there for testing purposes. It does not write the print job to a file. It just logs the job parameters
+known to Samba into the <filename>/tmp/smbprn.log</filename> file and deletes the jobfile. Moreover, the
+<smbconfoption><name>printer admin</name></smbconfoption> of this share is "kurt" (not the "@ntadmins" group);
+guest access is not allowed; the share isn not published to the Network Neighbourhood (so you need to know it is there), and it only
+allows access from only three hosts. To prevent CUPS kicking in and taking over the print jobs for that share, we need to set
+<smbconfoption><name>printing</name><value>sysv</value></smbconfoption> and
+<smbconfoption><name>printcap</name><value>lpstat</value></smbconfoption>.
 </para>
 </sect2>
 </sect1>
@@ -275,20 +252,23 @@ lpstat</parameter>.
 <title>Advanced Configuration</title>
 
 <para>
-Before we dive into all the configuration options, let's clarify a few
+Before we delve into all the configuration options, let us clarify a few
 points. <emphasis>Network printing needs to be organized and setup
 correctly</emphasis>. Often this is not done correctly. Legacy systems
-or small LANs in business environments often lack a clear design and
-good housekeeping.
+or small business LAN environments often lack design and good housekeeping.
 </para>
 
+
 <sect2>
 <title>Central spooling vs. "Peer-to-Peer" printing</title>
 
+<indexterm><primary>spooling</primary><secondary>central</secondary></indexterm>
+<indexterm><primary>spooling</primary><secondary>peer-to-peer</secondary></indexterm>
+
 <para>
 Many small office or home networks, as well as badly organized larger
 environments, allow each client a direct access to available network
-printers. Generally, this is a bad idea. It often blocks one client's
+printers. This is generally a bad idea. It often blocks one client's
 access to the printer when another client's job is printing. It also
 might freeze the first client's application while it is waiting to get
 rid of the job. Also, there are frequent complaints about various jobs
@@ -304,19 +284,22 @@ printer(s) in the correct order.
 <title>CUPS/Samba as a "spooling-only" Print Server; "raw" printing
 with Vendor Drivers on Windows Clients</title>
 
+<indexterm><primary>spooling-only</primary></indexterm>
+<indexterm><primary>"raw" printing</primary></indexterm>
+
 <para>
-Most traditionally configured Unix print servers acting on behalf of
+Most traditionally configured UNIX print servers acting on behalf of
 Samba's Windows clients represented a really simple setup. Their only
 task was to manage the "raw" spooling of all jobs handed to them by
 Samba. This approach meant that the Windows clients were expected to
-prepare the print job file in such a way that it became fit to be fed to
-the printing device. Here a native (vendor-supplied) Windows printer
+prepare the print job file that it s ready to be sent to the printing
+device. Here a native (vendor-supplied) Windows printer
 driver for the target device needed to be installed on each and every
 client.
 </para>
 
 <para>
-Of course you can setup CUPS, Samba and your Windows clients in the
+It is possible to configure CUPS, Samba and your Windows clients in the
 same, traditional and simple way. When CUPS printers are configured
 for RAW print-through mode operation it is the responsibility of the
 Samba client to fully render the print job (file). The file must be
@@ -341,9 +324,12 @@ one by one; this yields the old <emphasis>LanMan</emphasis> style
 printing; it uses a <filename>\\sambaserver\printershare</filename>
 type of connection.</para></listitem>
 
-<listitem><para>deposit and prepare the drivers (for later download) on
+
+<listitem><para>
+<indexterm><primary>point and print</primary></indexterm>
+		deposit and prepare the drivers (for later download) on
 the print server (Samba); this enables the clients to use
-"Point'n'Print" to get drivers semi-automatically installed the
+"Point and Print" to get drivers semi-automatically installed the
 first time they access the printer; with this method NT/2K/XP
 clients use the <emphasis>SPOOLSS/MS-RPC</emphasis>
 type printing calls.</para></listitem>
@@ -358,6 +344,8 @@ The second method is recommended for use over the first.
 <title>Explicitly enable "raw" printing for
 <emphasis>application/octet-stream</emphasis>!</title>
 
+<indexterm><primary>application/octet-stream</primary></indexterm>
+
 <para>
 If you use the first option (drivers are installed on the client
 side), there is one setting to take care of: CUPS needs to be told
@@ -381,9 +369,7 @@ present:
 </para>
 
 <para><screen>
-
  application/octet-stream
-
 </screen></para>
 
 <para>
@@ -391,10 +377,10 @@ In <filename>/etc/cups/mime.convs</filename>,
 have this line:
 </para>
 
-<para><screen>
+<indexterm><primary>application/vnd.cups-raw</primary></indexterm>
 
+<para><screen>
  application/octet-stream   application/vnd.cups-raw   0   - 
-
 </screen></para>
 
 <para>
@@ -411,6 +397,8 @@ convert file 0</computeroutput> in your CUPS error_log file.
 
 <formalpara><title>Background</title>
 
+<indexterm><primary>application/octet-stream</primary></indexterm>
+
 <para>
 CUPS being a more security-aware printing system than traditional ones
 does not by default allow a user to send deliberate (possibly binary)
@@ -437,9 +425,11 @@ of this chapter.
 <sect2>
 <title>Three familiar Methods for driver upload plus a new one</title>
 
+<indexterm><primary>point and print</primary></indexterm>
+
 <para>
 If you want to use the MS-RPC type printing, you must upload the
-drivers onto the Samba server first (<parameter>[print$]</parameter>
+drivers onto the Samba server first (<smbconfsection>[print$]</smbconfsection>
 share). For a discussion on how to deposit printer drivers on the
 Samba host (so that the Windows clients can download and use them via
 "Point'n'Print") please also refer to the previous chapter of this
@@ -447,6 +437,8 @@ HOWTO Collection. There you will find a description or reference to
 three methods of preparing the client drivers on the Samba server:
 </para>
 
+<indexterm><primary>add printer wizard</primary></indexterm>
+
 <itemizedlist>
 <listitem><para>the GUI, "Add Printer Wizard"
 <emphasis>upload-from-a-Windows-client</emphasis>
@@ -456,16 +448,21 @@ method;</para></listitem>
 <emphasis>upload-from-a-UNIX-workstation</emphasis>
 method;</para></listitem>
 
-<listitem><para>the <emphasis>Imprints</emphasis> Toolset
+
+<listitem><para>
+<indexterm><primary>imprints</primary></indexterm>
+		the <emphasis>Imprints</emphasis> Toolset
 method.</para></listitem>
 </itemizedlist>
 
 <para>
 These 3 methods apply to CUPS all the same. A new and more
 convenient way to load the Windows drivers into Samba is provided
-provided if you use CUPS:
+if you use CUPS:
 </para>
 
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+
 <itemizedlist>
 <listitem><para>the <emphasis>cupsaddsmb</emphasis>
 utility.</para></listitem>
@@ -483,8 +480,10 @@ UNIX printing architectures.
 <title>Using CUPS/Samba in an advanced Way -- intelligent printing
 with PostScript Driver Download</title>
 
+<indexterm><primary>PostScript</primary><seealso>Ghostscript</seealso></indexterm>
+
 <para>
-Still reading on? Good. Let's go into more detail then. We now know
+Are you still following this? Good. Let's go into more detail then. We now know
 how to set up a "dump" printserver, that is, a server which is spooling
 printjobs "raw", leaving the print data untouched.
 </para>
@@ -521,12 +520,15 @@ how CUPS works and how you can enable its features.
 
 <para>
 What follows is the comparison of some fundamental concepts for
-Windows and Unix printing; then is the time for a description of the
+Windows and UNIX printing; then is the time for a description of the
 CUPS filtering system, how it works and how you can tweak it.
 </para>
 
-<sect2>
-<title>GDI on Windows -- PostScript on Unix</title>
+<sect2 id="gdipost">
+<title>GDI on Windows -- PostScript on UNIX</title>
+
+<indexterm><primary>GDI</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
 
 <para>
 Network printing is one of the most complicated and error-prone
@@ -534,6 +536,9 @@ day-to-day tasks any user or an administrator may encounter. This is
 true for all OS platforms. And there are reasons for this.
 </para>
 
+<indexterm><primary>PCL</primary></indexterm>
+<indexterm><primary>PDL</primary></indexterm>
+
 <para>
 You can't expect for most file formats to just throw them towards
 printers and they get printed. There needs to be a file format
@@ -552,6 +557,10 @@ interpreters, etc.).
 <sect2>
 <title>Windows Drivers, GDI and EMF</title>
 
+<indexterm><primary>GDI</primary></indexterm>
+<indexterm><primary>EMF</primary></indexterm>
+<indexterm><primary>WYSIWYG</primary></indexterm>
+
 <para>
 In Windows OS, the format conversion job is done by the printer
 drivers. On MS Windows OS platforms all application programmers have
@@ -571,29 +580,30 @@ converted to the printer-specific file format.
 </para>
 
 <note><para>
+<indexterm><primary>PDF</primary></indexterm>
 To the GDI foundation in MS Windows, Apple has chosen to
 put paper and screen output on a common foundation for their
-(BSD-Unix-based, did you know??) Mac OS X and Darwin Operating
-Systems.Their <emphasis>Core Graphic Engine</emphasis> uses a
-<emphasis>PDF</emphasis> derivate for all display work.
+(BSD-UNIX-based, did you know??) Mac OS X and Darwin Operating
+Systems. Their <emphasis>Core Graphic Engine</emphasis> uses a
+<emphasis>PDF</emphasis> derivative for all display work.
 </para></note>
 
 <para>
 
-<figure><title>Windows Printing to a local Printer</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/1small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/1small.png"/></imageobject>
-</mediaobject>
-</figure>
+<image id="small1"><imagedescription>Windows Printing to a local Printer</imagedescription><imagefile>1small</imagefile></image>
 </para>
 </sect2>
 
 <sect2>
-<title>Unix Printfile Conversion and GUI Basics</title>
+<title>UNIX Printfile Conversion and GUI Basics</title>
+
+<indexterm><primary>X Window System</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>PCL</primary></indexterm>
+<indexterm><primary>Xprint</primary></indexterm>
 
 <para>
-In Unix and Linux, there is no comparable layer built into the OS
+In UNIX and Linux, there is no comparable layer built into the OS
 kernel(s) or the X (screen display) server. Every application is
 responsible for itself to create its print output.  Fortunately, most
 use PostScript. That gives at least some common ground. Unfortunately,
@@ -617,6 +627,8 @@ to be used on paper.
 <formalpara>
 <title>Background</title>
 
+<indexterm><primary>PostScript</primary></indexterm>
+
 <para>
 The PostScript programming language is an "invention" by Adobe Inc.,
 but its specifications have been published to the full. Its strength
@@ -637,12 +649,16 @@ program or on paper by a printer.
 </formalpara>
 </sect2>
 
-<sect2>
+<sect2 id="post-and-ghost">
 <title>PostScript and Ghostscript</title>
 
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>GhostScript</primary><seealso>PostScript</seealso></indexterm>
+<indexterm><primary>PostScript</primary><secondary>RIP</secondary></indexterm>
+
 <para>
-So, Unix is lacking a common ground for printing on paper and
-displaying on screen. Despite this unfavorable legacy for Unix, basic
+So, UNIX is lacking a common ground for printing on paper and
+displaying on screen. Despite this unfavorable legacy for UNIX, basic
 printing is fairly easy: if you have PostScript printers at your
 disposal! The reason is: these devices have a built-in PostScript
 language "interpreter", also called a <emphasis>Raster Image
@@ -654,30 +670,30 @@ you see it on paper, in a resolution as done by your printer. This is
 no different to PostScript printing of a file from a Windows origin.
 </para>
 
-<note><para>Traditional Unix programs and printing systems -- while
+<note><para>
+<indexterm><primary>PPD</primary></indexterm>
+Traditional UNIX programs and printing systems -- while
 using PostScript -- are largely not PPD-aware. PPDs are "PostScript
 Printer Description" files. They enable you to specify and control all
 options a printer supports: duplexing, stapling, punching... Therefore
-Unix users for a long time couldn't choose many of the supported
+UNIX users for a long time couldn't choose many of the supported
 device and job options, unlike Windows or Apple users. But now there
-is CUPS.... ;-)
+is CUPS....
 </para>
 </note>
 
 <para>
-<figure><title>Printing to a Postscript Printer</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/2small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/2small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small2"><imagedescription>Printing to a Postscript Printer</imagedescription>
+		<imagefile>2small</imagefile></image>
 </para>
 
+<indexterm><primary>PDL</primary></indexterm>
+
 <para>
 However, there are other types of printers out there. These don't know
 how to print PostScript. They use their own <emphasis>Page Description
 Language</emphasis> (PDL, often proprietary). To print to them is much
-more demanding. Since your Unix applications mostly produce
+more demanding. Since your UNIX applications mostly produce
 PostScript, and since these devices don't understand PostScript, you
 need to convert the printfiles to a format suitable for your printer
 on the host, before you can send it away.
@@ -687,10 +703,12 @@ on the host, before you can send it away.
 <sect2>
 <title>Ghostscript -- the Software RIP for non-PostScript Printers</title>
 
+<indexterm><primary>GhostScript</primary></indexterm>
+
 <para>
 Here is where <emphasis>Ghostscript</emphasis> kicks in. Ghostscript is
 the traditional (and quite powerful) PostScript interpreter used on
-Unix platforms. It is a RIP in software, capable to do a
+UNIX platforms. It is a RIP in software, capable to do a
 <emphasis>lot</emphasis> of file format conversions, for a very broad
 spectrum of hardware devices as well as software file formats.
 Ghostscript technology and drivers is what enables PostScript printing
@@ -698,12 +716,9 @@ to non-PostScript hardware.
 </para>
 
 <para>
-<figure><title>Ghostscript as a RIP for non-postscript printers</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/3small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/3small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small3"><imagedescription>Ghostscript as a RIP for non-postscript printers</imagedescription>
+	<imagefile>3small</imagefile>
+</image>
 </para>
 
 <tip><para>
@@ -718,7 +733,7 @@ intervals, now by artofcode LLC. They are initially put under the
 "AFPL" license, but re-released under the GNU GPL as soon as the next
 AFPL version appears. GNU Ghostscript is probably the version
 installed on most Samba systems. But it has got some
-deficiencies. Therefore ESP Ghostscript was developed as an
+deficiencies. <indexterm><primary>Ghostscript</primary><secondary>ESP</secondary><see>ESP GhostScript</see></indexterm>Therefore ESP Ghostscript was developed as an
 enhancement over GNU Ghostscript, with lots of bug-fixes, additional
 devices and improvements. It is jointly maintained by developers from
 CUPS, Gimp-Print, MandrakeSoft, SuSE, RedHat and Debian. It includes
@@ -729,6 +744,8 @@ the "cups" device (essential to print to non-PS printers from CUPS).
 <sect2>
 <title>PostScript Printer Description (PPD) Specification</title>
 
+<indexterm><primary>PPD</primary></indexterm>
+
 <para>
 While PostScript in essence is a <emphasis>Page Description
 Language</emphasis> (PDL) to represent the page layout in a
@@ -761,6 +778,7 @@ file created by the driver.
 </para>
 
 <warning><para>
+<indexterm><primary>PDF</primary></indexterm>
 A PostScript file that was created to contain device-specific commands
 for achieving a certain print job output (e.g. duplexed, stapled and
 punched) on a specific target machine, may not print as expected, or
@@ -775,7 +793,7 @@ for further processing by software (e.g. by a PDF distilling program).
 <para>
 CUPS can handle all spec-compliant PPDs as supplied by the
 manufacturers for their PostScript models. Even if a
-Unix/Linux-illiterate vendor might not have mentioned our favorite
+UNIX/Linux-illiterate vendor might not have mentioned our favorite
 OS in his manuals and brochures -- you can safely trust this:
 <emphasis>if you get hold of the Windows NT version of the PPD, you
 can use it unchanged in CUPS</emphasis> and thus access the full
@@ -784,7 +802,7 @@ power of your printer just like a Windows NT user could!
 
 <tip><para>
 To check the spec compliance of any PPD online, go to <ulink
-url="http://www.cups.org/testppd.php">http://www.cups.org/testppd.php</ulink>
+noescape="1" url="http://www.cups.org/testppd.php">http://www.cups.org/testppd.php</ulink>
 and upload your PPD. You will see the results displayed
 immediately. CUPS in all versions after 1.1.19 has a much more strict
 internal PPD parsing and checking code enabled; in case of printing
@@ -792,6 +810,8 @@ trouble this online resource should be one of your first pitstops.
 </para></tip>
 
 <warning><para>
+<indexterm><primary>foomatic</primary></indexterm>
+<indexterm><primary>cupsomatic</primary></indexterm>
 For real PostScript printers <emphasis>don't</emphasis> use the
 <emphasis>Foomatic</emphasis> or <emphasis>cupsomatic</emphasis>
 PPDs from Linuxprinting.org. With these devices the original
@@ -863,7 +883,7 @@ Make sure your Ghostscript version has the "cups" device compiled in
 may encounter the dreaded <computeroutput>Unable to convert file
 0</computeroutput> in your CUPS error_log file. To have "cups" as a
 device in your Ghostscript, you either need to <emphasis>patch GNU
-Ghostscript</emphasis> and re-compile or use <ulink
+Ghostscript</emphasis> and re-compile or use <indexterm><primary>ESP</primary><secondary>Ghostscript</secondary></indexterm><ulink
 url="http://www.cups.org/ghostscript.php">ESP Ghostscript</ulink>. The
 superior alternative is ESP Ghostscript: it supports not just CUPS,
 but 300 other devices too (while GNU Ghostscript supports only about
@@ -873,6 +893,8 @@ Linuxprinting.org for all spoolers.
 </para>
 
 <para>
+<indexterm><primary>cupsomatic</primary></indexterm>
+<indexterm><primary>foomatic</primary></indexterm>
 CUPS printers may be setup to use <emphasis>external</emphasis>
 rendering paths. One of the most common ones is provided by the
 <emphasis>Foomatic/cupsomatic</emphasis> concept, from <ulink
@@ -880,6 +902,7 @@ url="http://www.linuxprinting.org/">Linuxprinting.org</ulink>.  This
 uses the classical Ghostscript approach, doing everything in one
 step. It doesn't use the "cups" device, but one of the many
 others. However, even for Foomatic/cupsomatic usage, best results and
+<indexterm><primary>ESP</primary><secondary>Ghostscript</secondary></indexterm>
 broadest printer model support is provided by ESP Ghostscript (more
 about cupsomatic/Foomatic, particularly the new version called now
 <emphasis>foomatic-rip</emphasis>, follows below).
@@ -889,6 +912,7 @@ about cupsomatic/Foomatic, particularly the new version called now
 <title>MIME types and CUPS Filters</title>
 
 <para>
+	<indexterm><primary>MIME</primary></indexterm>
 CUPS reads the file <filename>/etc/cups/mime.types</filename>
 (and all other files carrying a <filename>*.types</filename> suffix
 in the same directory) upon startup. These files contain the MIME
@@ -899,10 +923,10 @@ for <filename>mime.types</filename> and in the comments section of the
 like this:
 </para>
 
-<para><screen>
-
+<para>
+<indexterm><primary>application/pdf</primary></indexterm>
+<screen>
  application/pdf         pdf string(0,%PDF)
-
 </screen></para>
 
 <para>
@@ -915,9 +939,7 @@ Another rule is this:
 </para>
 
 <para><screen>
-
  application/postscript  ai eps ps string(0,%!) string(0,&lt;04&gt;%!)
-
 </screen></para>
 
 <para>
@@ -961,6 +983,8 @@ with its filters.
 <sect2>
 <title>MIME type Conversion Rules</title>
 
+<indexterm><primary>MIME</primary></indexterm>
+
 <para>
 CUPS reads the file <filename>/etc/cups/mime.convs</filename>
 (and all other files named with a <filename>*.convs</filename>
@@ -972,9 +996,7 @@ reads like this:
 </para>
 
 <para><screen>
-
  application/pdf         application/postscript   33   pdftops
-
 </screen></para>
 
 <para>
@@ -985,10 +1007,10 @@ cost of this operation is 33 CUPS-$. The next filter is more
 expensive, costing 66 CUPS-$:
 </para>
 
-<para><screen>
+<indexterm><primary>pdf</primary></indexterm>
 
+<para><screen>
  application/vnd.hp-HPGL application/postscript   66   hpgltops
-
 </screen></para>
 
 <para>
@@ -996,21 +1018,21 @@ This is the <emphasis>hpgltops</emphasis>, which processes HP-GL
 plotter files to PostScript.
 </para>
 
-<para><screen>
+<indexterm><primary>application/octet-stream</primary></indexterm>
 
+<para><screen>
  application/octet-stream
-
 </screen></para>
 
 <para>
 Here are two more examples: 
 </para>
 
-<para><screen>
+<indexterm><primary>text/plain</primary></indexterm>
 
+<para><screen>
  application/x-shell     application/postscript   33    texttops
  text/plain              application/postscript   33    texttops
-
 </screen></para>
 
 <para>
@@ -1024,6 +1046,8 @@ this differentiation is needed for the syntax highlighting feature of
 <sect2>
 <title>Filter Requirements</title>
 
+<indexterm><primary>MIME</primary></indexterm>
+
 <para>
 There are many more combinations named in mime.convs.  However, you
 are not limited to use the ones pre-defined there. You can plug in any
@@ -1053,25 +1077,25 @@ name of the filter being run)</para></listitem>
 printed</para></listitem>
 </varlistentry>
 
-<varlistentry><term>Printer</term>
+<varlistentry><term>user</term>
 <listitem><para>The string from the originating-user-name
 attribute</para></listitem>
 </varlistentry>
 
-<varlistentry><term>Printer</term>
+<varlistentry><term>title</term>
 <listitem><para>The string from the job-name attribute</para></listitem>
 </varlistentry>
 
-<varlistentry><term>Printer</term>
+<varlistentry><term>copies</term>
 <listitem><para>The numeric value from the number-copies
 attribute</para></listitem>
 </varlistentry>
 
-<varlistentry><term>Printer</term>
+<varlistentry><term>options</term>
 <listitem><para>The job options</para></listitem>
 </varlistentry>
 
-<varlistentry><term>Printer</term>
+<varlistentry><term>filename</term>
 <listitem><para>(Optionally) The print request file (if missing,
 filters expected data fed through <filename>stdin</filename>). In most
 cases it is very easy to write a simple wrapper script around existing
@@ -1084,8 +1108,10 @@ filters to make them work with CUPS.</para></listitem>
 <sect2>
 <title>Prefilters</title>
 
+<indexterm><primary>PostScript</primary></indexterm>
+
 <para>
-As was said, PostScript is the central file format to any Unix based
+As was said, PostScript is the central file format to any UNIX based
 printing system. From PostScript, CUPS generates raster data to feed
 non-PostScript printers.
 </para>
@@ -1106,12 +1132,9 @@ print options already embedded into the file.
 </para>
 
 <para>
-<figure><title>Prefiltering in CUPS to form Postscript</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/4small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/4small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small4" scale="25"><imagedescription>Prefiltering in CUPS to form Postscript</imagedescription>
+	<imagefile>4small</imagefile>
+</image>
 </para>
 </sect2>
 
@@ -1128,12 +1151,9 @@ stapling an punching it, etc.) into the PostScript file.
 </para>
 
 <para>
-<figure><title>Adding Device-specific Print Options</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/5small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/5small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small5" scale="25"><imagedescription>Adding Device-specific Print Options</imagedescription>
+		<imagefile>5small</imagefile>
+	</image>
 </para>
 
 <para>
@@ -1172,12 +1192,7 @@ that are able to generate device-specific printer data.
 </para>
 
 <para>
-<figure><title>Postscript to intermediate Raster format</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/6small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/6small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small6" scale="25"><imagedescription>Postscript to intermediate Raster format</imagedescription><imagefile>6small</imagefile></image>
 </para>
 
 <para>
@@ -1186,7 +1201,7 @@ able to include per-page information, color profiles and more to be
 used by the following downstream raster drivers. Its MIME type is
 registered with IANA and its specification is of course completely
 open. It is designed to make it very easy and inexpensive for
-manufacturers to develop Linux and Unix raster drivers for their
+manufacturers to develop Linux and UNIX raster drivers for their
 printer models, should they choose to do so. CUPS always takes care
 for the first stage of rasterization so these vendors don't need to care
 about Ghostscript complications (in fact, there is currently more
@@ -1194,12 +1209,9 @@ than one vendor financing the development of CUPS raster drivers).
 </para>
 
 <para>
-<figure><title>CUPS-raster production using Ghostscript</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/7small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/7small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small7"><imagedescription>CUPS-raster production using Ghostscript</imagedescription>
+		<imagefile>7small</imagefile>
+	</image>
 </para>
 
 <para>
@@ -1233,12 +1245,9 @@ filtering:
 </para>
 
 <para>
-<figure><title>Image format to CUPS-raster format conversion</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/8small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/8small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small8"><imagedescription>Image format to CUPS-raster format conversion</imagedescription>
+		<imagefile>8small</imagefile>
+	</image>
 </para>
 
 </sect2>
@@ -1249,9 +1258,9 @@ filtering:
 <para>
 CUPS ships with quite some different raster drivers processing CUPS
 raster. On my system I find in /usr/lib/cups/filter/ these:
-<parameter>rastertoalps, rastertobj, rastertoepson, rastertoescp,
-rastertopcl, rastertoturboprint, rastertoapdk, rastertodymo,
-rastertoescp, rastertohp</parameter> and
+<parameter>rastertoalps</parameter>, <parameter>rastertobj</parameter>, <parameter>rastertoepson</parameter>, <parameter>rastertoescp</parameter>,
+<parameter>rastertopcl</parameter>, <parameter>rastertoturboprint</parameter>, <parameter>rastertoapdk</parameter>, <parameter>rastertodymo</parameter>,
+<parameter>rastertoescp</parameter>, <parameter>rastertohp</parameter> and
 <parameter>rastertoprinter</parameter>. Don't worry if you have less
 than this; some of these are installed by commercial add-ons to CUPS
 (like <parameter>rastertoturboprint</parameter>), others (like
@@ -1261,12 +1270,9 @@ closely as possible with CUPS.
 </para>
 
 <para>
-<figure><title>Raster to Printer Specific formats</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/9small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/9small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small9"><imagedescription>Raster to Printer Specific formats</imagedescription>
+		<imagefile>9small</imagefile>
+	</image>
 </para>
 </sect2>
 
@@ -1356,7 +1362,7 @@ This backend sends printfiles to printers shared by a Windows
 host. An example for CUPS device-URIs to use are:
 <filename>smb://workgroup/server/printersharename</filename>
 Or
-<filename>Smb://server/printersharename</filename>
+<filename>smb://server/printersharename</filename>
 or
 <filename>smb://username:password@workgroup/server/printersharename</filename>
 or
@@ -1387,20 +1393,21 @@ printername).
 Not all of the mentioned backends may be present on your system or
 usable (depending on your hardware configuration). One test for all
 available CUPS backends is provided by the <emphasis>lpinfo</emphasis>
-utility. Used with the <parameter>-v</parameter> parameter, it lists
+utility. Used with the <option>-v</option> parameter, it lists
 all available backends:
 </para>
 
 <para><screen>
-
- lpinfo -v
-
+&prompt;<userinput>lpinfo -v</userinput>
 </screen></para>
 </sect2>
 
 <sect2>
 <title>cupsomatic/Foomatic -- how do they fit into the Picture?</title>
 
+<indexterm><primary>cupsomatic</primary></indexterm>
+<indexterm><primary>foomatic</primary></indexterm>
+
 <para>
 "cupsomatic" filters may be the most widely used on CUPS
 installations. You must be clear about the fact that these were not
@@ -1419,9 +1426,7 @@ You can recognize these PPDs from the line calling the
 </para>
 
 <para><screen>
-
  *cupsFilter: "application/vnd.cups-postscript  0  cupsomatic"
-
 </screen></para>
 
 <para>
@@ -1434,6 +1439,8 @@ auto-constructed from the selected PPD and commandline options give to
 the printjob.
 </para>
 
+<indexterm><primary>point and print</primary></indexterm>
+
 <para>
 However, cupsomatic is now deprecated. Its PPDs (especially the first
 generation of them, still in heavy use out there) are not meeting the
@@ -1515,9 +1522,7 @@ associating any PPD with it. This command:
 </para>
 
 <para><screen>
-
- lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E
-
+&prompt;<userinput>lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E</userinput>
 </screen></para>
 
 <para>
@@ -1550,9 +1555,7 @@ message in your CUPS logs like:
 </para>
 
 <para><screen>
-
  Unable to convert file 0 to printable format for job
-
 </screen></para>
 
 <para>
@@ -1573,10 +1576,10 @@ application/octet-stream. In <filename>/etc/cups/mime.types</filename>
 make sure this line is present:
 </para>
 
-<para><screen>
+<indexterm><primary>application/octet-stream</primary></indexterm>
 
+<para><screen>
  application/octet-stream
-
 </screen></para>
 
 <para>
@@ -1587,11 +1590,11 @@ line:
 </para>
 
 <para><screen>
-
  application/octet-stream   application/vnd.cups-raw   0   -
-
 </screen></para>
 
+<indexterm><primary>MIME</primary></indexterm>
+
 <para>
 This line tells CUPS to use the <emphasis>Null Filter</emphasis>
 (denoted as "-", doing... nothing at all) on
@@ -1631,6 +1634,8 @@ conversion filter(s) may be applied to which MIME types.
 <sect2>
 <title>PostScript Printer Descriptions (PPDs) for non-PS Printers</title>
 
+<indexterm><primary>PPD</primary></indexterm>
+
 <para>
 Originally PPDs were meant to be used for PostScript printers
 only. Here, they help to send device-specific commands and settings
@@ -1648,10 +1653,10 @@ PPDs for a non-PS printer have a few lines that are unique to
 CUPS. The most important one looks similar to this:
 </para>
 
-<para><screen>
+<indexterm><primary>application/vnd.cups-raster</primary></indexterm>
 
+<para><screen>
  *cupsFilter: application/vnd.cups-raster  66   rastertoprinter
-
 </screen></para>
 
 <para>
@@ -1673,74 +1678,50 @@ different paper trays, or you may get larger margins than your
 specific model supports):
 </para>
 
-<variablelist>
-<varlistentry><term>deskjet.ppd</term>
-<listitem><para>older HP inkjet printers and compatible
-</para></listitem>
-</varlistentry>
+<table frame="all">
+	<title>PPD's shipped with CUPS</title>
+	<tgroup cols="2" align="left">
+		<colspec align="left"/>
+		<colspec align="justify"/>
+		<thead><row><entry>PPD file</entry><entry>Printer type</entry></row></thead>
+		<tbody>
+			<row><entry>deskjet.ppd</entry><entry>older HP inkjet printers and compatible</entry></row>
 
-<varlistentry><term>deskjet2.ppd</term>
-<listitem><para>newer HP inkjet printers and compatible
-</para></listitem>
-</varlistentry>
+		<row><entry>deskjet2.ppd</entry> <entry>newer HP inkjet printers and compatible </entry> </row>
 
-<varlistentry><term>dymo.ppd</term>
-<listitem><para>label printers
-</para></listitem>
-</varlistentry>
+		<row><entry>dymo.ppd</entry> <entry>label printers </entry> </row>
 
-<varlistentry><term>epson9.ppd</term>
-<listitem><para>Epson 24pin impact printers and compatible
-</para></listitem>
-</varlistentry>
+		<row><entry>epson9.ppd</entry> <entry>Epson 24pin impact printers and compatible </entry> </row>
 
-<varlistentry><term>epson24.ppd</term>
-<listitem><para>Epson 24pin impact printers and compatible
-</para></listitem>
-</varlistentry>
+		<row><entry>epson24.ppd</entry> <entry>Epson 24pin impact printers and compatible </entry> </row>
 
-<varlistentry><term>okidata9.ppd</term>
-<listitem><para>Okidata 9pin impact printers and compatible
-</para></listitem>
-</varlistentry>
+		<row><entry>okidata9.ppd</entry> <entry>Okidata 9pin impact printers and compatible </entry> </row>
 
-<varlistentry><term>okidat24.ppd</term>
-<listitem><para>Okidata 24pin impact printers and compatible
-</para></listitem>
-</varlistentry>
+		<row><entry>okidat24.ppd</entry> <entry>Okidata 24pin impact printers and compatible </entry> </row>
 
-<varlistentry><term>stcolor.ppd</term>
-<listitem><para>older Epson Stylus Color printers
-</para></listitem>
-</varlistentry>
+		<row><entry>stcolor.ppd</entry> <entry>older Epson Stylus Color printers </entry> </row>
 
-<varlistentry><term>stcolor2.ppd</term>
-<listitem><para>newer Epson Stylus Color printers
-</para></listitem>
-</varlistentry>
+		<row><entry>stcolor2.ppd</entry> <entry>newer Epson Stylus Color printers </entry> </row>
 
-<varlistentry><term>stphoto.ppd</term>
-<listitem><para>older Epson Stylus Photo printers
-</para></listitem>
-</varlistentry>
+		<row><entry>stphoto.ppd</entry> <entry>older Epson Stylus Photo printers </entry> </row>
 
-<varlistentry><term>stphoto2.ppd</term>
-<listitem><para>newer Epson Stylus Photo printers
-</para></listitem>
-</varlistentry>
+		<row><entry>stphoto2.ppd</entry> <entry>newer Epson Stylus Photo printers </entry> </row>
+
+		<row><entry>laserjet.ppd</entry> <entry>all PCL printers. Further below is a discussion of several other driver/PPD-packages suitable for use with CUPS.  </entry> </row>
+
+		</tbody>
+	</tgroup>
+</table>
 
-<varlistentry><term>laserjet.ppd</term>
-<listitem><para>all PCL printers. Further below is a discussion
-of several other driver/PPD-packages suitable fur use with CUPS.
-</para></listitem>
-</varlistentry>
-</variablelist>
 </sect2>
 
 <sect2>
 <title>Difference between <emphasis>cupsomatic/foomatic-rip</emphasis> and
 <emphasis>native CUPS</emphasis> printing</title>
 
+<indexterm><primary>cupsomatic</primary></indexterm>
+<indexterm><primary>foomatic-rip</primary></indexterm>
+
 <para>
 Native CUPS rasterization works in two steps.
 </para>
@@ -1748,6 +1729,7 @@ Native CUPS rasterization works in two steps.
 <itemizedlist>
 <listitem><para>
 First is the "pstoraster" step. It uses the special "cups"
+<indexterm><primary>ESP</primary><secondary>Ghostscript</secondary></indexterm>
 device from ESP Ghostscript 7.05.x as its tool
 </para></listitem>
 
@@ -1764,12 +1746,9 @@ advantages) than other methods.
 </para>
 
 <para>
-<figure><title>cupsomatic/foomatic processing versus Native CUPS</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/10small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/10small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small10"><imagedescription>cupsomatic/foomatic processing versus Native CUPS</imagedescription>
+		<imagefile>10small</imagefile>
+	</image>
 </para>
 
 <para>
@@ -1777,7 +1756,7 @@ One other method is the <emphasis>cupsomatic/foomatic-rip</emphasis>
 way. Note that cupsomatic is <emphasis>not</emphasis> made by the CUPS
 developers. It is an independent contribution to printing development,
 made by people from Linuxprinting.org (see also <ulink
-url="http://www.cups.org/cups-help.html">http://www.cups.org/cups-help.html</ulink>).
+	noescape="1" url="http://www.cups.org/cups-help.html">http://www.cups.org/cups-help.html</ulink>).
 cupsomatic is no longer developed and maintained and is no longer
 supported. It has now been replaced by
 <emphasis>foomatic-rip</emphasis>. foomatic-rip is a complete re-write
@@ -1788,6 +1767,8 @@ too.
 </para>
 
 <para>
+	<indexterm><primary>cupsomatic</primary></indexterm>
+	<indexterm><primary>foomatic</primary></indexterm>
 Both the cupsomatic (old) and the foomatic-rip (new) methods from
 Linuxprinting.org use the traditional Ghostscript print file
 processing, doing everything in a single step. It therefore relies on
@@ -1855,12 +1836,10 @@ backend, which transfers the job to the printers.</para></listitem>
 </itemizedlist>
 
 <para>
-The resulting filter chain therefore is:
+	The resulting filter chain therefore is as drawn in <link linkend="pdftosocket">the image below</link>.
 </para>
 
-<para><screen>
-pdftops --&gt; pstops --&gt; socket
-</screen></para>
+<image><imagefile>pdftosocket</imagefile><imagedescription>PDF to socket chain</imagedescription></image>
 
 <para>
 Assume your want to print the same filter to an USB-connected
@@ -1904,12 +1883,10 @@ which transfers the job to the printers.</para></listitem>
 </itemizedlist>
 
 <para>
-The resulting filter chain therefore is:
+	The resulting filter chain therefore is as drawn in <link linkend="pdftoepsonusb">the image below</link>.
 </para>
 
-<para><screen>
-pdftops --&gt; pstops --&gt; pstoraster --&gt; rastertoepson --&gt; usb
-</screen></para>
+<image><imagefile>pdftoepsonusb</imagefile><imagedescription>PDF to USB chain</imagedescription></image>
 </sect2>
 
 <sect2>
@@ -1922,44 +1899,46 @@ supporting more than 1000 non-PostScript models.
 </para>
 
 <itemizedlist>
+<indexterm><primary>ESP</primary><secondary>Print Pro</secondary></indexterm>
+<indexterm><primary>PrintPro</primary><see>ESP Print Pro</see></indexterm>
 <listitem><para><ulink url="http://wwwl.easysw.com/printpro/">ESP
-PrintPro (http://wwwl.easysw.com/printpro/)</ulink> (commercial,
+PrintPro</ulink> (commercial,
 non-Free) is packaged with more than 3000 PPDs, ready for
 successful use "out of the box" on Linux, Mac OS X, IBM-AIX,
-HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital Unix and some
+HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital UNIX and some
 more commercial Unices (it is written by the CUPS developers
 themselves and its sales help finance the further development of
 CUPS, as they feed their creators).</para></listitem>
 
 <listitem><para>the <ulink
 url="http://gimp-print.sourceforge.net/">Gimp-Print-Project
-(http://gimp-print.sourceforge.net/)</ulink> (GPL, Free Software)
+</ulink> (GPL, Free Software)
 provides around 140 PPDs (supporting nearly 400 printers, many driven
 to photo quality output), to be used alongside the Gimp-Print CUPS
 filters;</para></listitem>
 
 <listitem><para><ulink url="http://www.turboprint.com/">TurboPrint
-(http://www.turboprint.com/)</ulink> (Shareware, non-Free) supports
+</ulink> (Shareware, non-Free) supports
 roughly the same amount of printers in excellent
 quality;</para></listitem>
 
 <listitem><para><ulink
 url="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/">OMNI
-(http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)</ulink>
+</ulink>
 (LPGL, Free) is a package made by IBM, now containing support for more
 than 400 printers, stemming from the inheritance of IBM OS/2 Know-How
 ported over to Linux (CUPS support is in a Beta-stage at
 present);</para></listitem>
 
 <listitem><para><ulink url="http://hpinkjet.sourceforge.net/">HPIJS
-(http://hpinkjet.sourceforge.net/)</ulink> (BSD-style licenses, Free)
+</ulink> (BSD-style licenses, Free)
 supports around 150 of HP's own printers and is also providing
 excellent print quality now (currently available only via the Foomatic
 path);</para></listitem>
 
 <listitem><para><ulink
 url="http://www.linuxprinting.org/">Foomatic/cupsomatic
-(http://www.linuxprinting.org/)</ulink> (LPGL, Free) from
+</ulink> (LPGL, Free) from
 Linuxprinting.org are providing PPDs for practically every Ghostscript
 filter known to the world (including Omni, Gimp-Print and
 HPIJS).</para></listitem>
@@ -1990,9 +1969,8 @@ the <command>-i</command> option:
 </para>
 
 <para><screen>
-
- lpadmin -p pclprinter -v socket://11.12.13.14:9100 -i /path/to/interface-script
-
+&rootprompt;<userinput>lpadmin -p pclprinter -v socket://11.12.13.14:9100 \
+  -i /path/to/interface-script</userinput>
 </screen></para>
 
 <para>
@@ -2001,7 +1979,7 @@ with CUPS they provide the most easy way to plug in your own
 custom-written filtering script or program into one specific print
 queue (some information about the traditional usage of interface scripts is
 to be found at <ulink
-url="http://playground.sun.com/printing/documentation/interface.html">http://playground.sun.com/printing/documentation/interface.html</ulink>).
+	noescape="1" url="http://playground.sun.com/printing/documentation/interface.html">http://playground.sun.com/printing/documentation/interface.html</ulink>).
 </para>
 </sect2>
 </sect1>
@@ -2024,6 +2002,9 @@ Windows clients printing to an NT-based print server have two
 options. They may
 </para>
 
+<indexterm><primary>GDI</primary></indexterm>
+<indexterm><primary>EMF</primary></indexterm>
+
 <itemizedlist>
 <listitem><para>execute the driver locally and render the GDI output
 (EMF) into the printer specific format on their own,
@@ -2045,45 +2026,45 @@ Both print paths are shown in the flowcharts below.
 <para>
 In the first case the print server must spool the file as "raw",
 meaning it shouldn't touch the jobfile and try to convert it in any
-way. This is what traditional Unix-based print server can do too; and
+way. This is what traditional UNIX-based print server can do too; and
 at a better performance and more reliably than NT print server. This
 is what most Samba administrators probably are familiar with. One
 advantage of this setup is that this "spooling-only" print server may
-be used even if no driver(s) for Unix are available it is sufficient
+be used even if no driver(s) for UNIX are available it is sufficient
 to have the Windows client drivers available and installed on the
 clients.
 </para>
 
 <para>
-<figure><title>Print Driver execution on the Client</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/11small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/11small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small11"><imagedescription>Print Driver execution on the Client</imagedescription>
+		<imagefile>11small</imagefile>
+	</image>
 </para>
 </sect2>
 
 <sect2>
 <title>Driver Execution on the Server</title>
 
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>PCL</primary></indexterm>
+<indexterm><primary>ESC/P</primary></indexterm>
+<indexterm><primary>EMF</primary></indexterm>
+<indexterm><primary>GDI</primary></indexterm>
+
 <para>
 The other path executes the printer driver on the server. The clients
 transfers print files in EMF format to the server. The server uses the
 PostScript, PCL, ESC/P or other driver to convert the EMF file into
-the printer-specific language. It is not possible for Unix to do the
+the printer-specific language. It is not possible for UNIX to do the
 same. Currently there is no program or method to convert a Windows
-client's GDI output on a Unix server into something a printer could
+client's GDI output on a UNIX server into something a printer could
 understand.
 </para>
 
 <para>
-<figure><title>Print Driver execution on the Server</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/12small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/12small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small12"><imagedescription>Print Driver execution on the Server</imagedescription>
+		<imagefile>12small</imagefile>
+	</image>
 </para>
 
 <para>
@@ -2130,20 +2111,19 @@ printer is a non-PostScript model. It also requires that you have a
 
 <para>
 Firstly, to enable CUPS based printing through Samba the
-following options should be set in your <filename>smb.conf</filename> file [globals]
+following options should be set in your &smb.conf; file [global]
 section:
 </para>
 
 <itemizedlist>
-<listitem><para><parameter>printing = CUPS</parameter></para></listitem>
+<listitem><para><smbconfoption><name>printing</name><value>cups</value></smbconfoption></para></listitem>
 
-<listitem><para><parameter>printcap = CUPS</parameter></para></listitem>
+<listitem><para><smbconfoption><name>printcap</name><value>cups</value></smbconfoption></para></listitem>
 </itemizedlist>
 
 <para>
 When these parameters are specified, all manually set print directives
-(like <parameter>print command =...</parameter>, or <parameter>lppause
-command =...</parameter>) in <filename>smb.conf</filename> (as well as
+(like <smbconfoption><name>print command</name></smbconfoption>, or <smbconfoption><name>lppause command</name></smbconfoption>) in &smb.conf; (as well as
 in samba itself) will be ignored. Instead, Samba will directly
 interface with CUPS through it's application program interface (API) -
 as long as Samba has been compiled with CUPS library (libcups)
@@ -2152,16 +2132,13 @@ other print commands are set up, then printing will use the
 <emphasis>System V</emphasis> AT&amp;T command set, with the -oraw
 option automatically passing through (if you want your own defined
 print commands to work with a Samba that has CUPS support compiled in,
-simply use <parameter>printing = sysv</parameter>).
+simply use <smbconfoption><name>printing</name><value>sysv</value></smbconfoption>).
 </para>
 
 <para>
-<figure><title>Printing via CUPS/samba server</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/13small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/13small.png"/></imageobject>
-</mediaobject>
-</figure>
+<image id="small13"><imagedescription>Printing via CUPS/samba server</imagedescription>
+	<imagefile>13small</imagefile>
+</image>
 </para>
 </sect2>
 
@@ -2170,10 +2147,10 @@ simply use <parameter>printing = sysv</parameter>).
 
 <para>
 Samba <emphasis>must</emphasis> use its own spool directory (it is set
-by a line similar to <parameter>path = /var/spool/samba</parameter>,
-in the <parameter>[printers]</parameter> or
-<parameter>[printername]</parameter> section of
-<filename>smb.conf</filename>). Samba receives the job in its own
+by a line similar to <smbconfoption><name>path</name><value>/var/spool/samba</value></smbconfoption>,
+in the <smbconfsection>[printers]</smbconfsection> or
+<smbconfsection>[printername]</smbconfsection> section of
+&smb.conf;). Samba receives the job in its own
 spool space and passes it into the spool directory of CUPS (the CUPS
 spooling directory is set by the <parameter>RequestRoot</parameter>
 directive, in a line that defaults to <parameter>RequestRoot
@@ -2196,6 +2173,10 @@ need to make sure the Samba host gets access to printing on CUPS.
 <title>Network PostScript RIP: CUPS Filters on Server -- clients use
 PostScript Driver with CUPS-PPDs</title>
 
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>PCL</primary></indexterm>
+<indexterm><primary>PJL</primary></indexterm>
+
 <para>
 PPDs can control all print device options. They are usually provided
 by the manufacturer; if you own a PostScript printer, that is. PPD
@@ -2211,7 +2192,7 @@ printer. Printer driver GUI dialogs translate these options
 CUPS can load, without any conversions, the PPD file from any Windows
 (NT is recommended) PostScript driver and handle the options. There is
 a web browser interface to the print options (select <ulink
-url="http://localhost:631/printers/">http://localhost:631/printers/</ulink>
+noescape="1" url="http://localhost:631/printers/">http://localhost:631/printers/</ulink>
 and click on one <emphasis>Configure Printer</emphasis> button to see
 it), or a commandline interface (see <command>man lpoptions</command>
 or see if you have lphelp on your system). There are also some
@@ -2223,6 +2204,8 @@ PostScript RIP on the real PostScript printer.
 <sect2>
 <title>PPDs for non-PS Printers on UNIX</title>
 
+<indexterm><primary>PPD</primary></indexterm>
+
 <para>
 CUPS doesn't limit itself to "real" PostScript printers in its usage
 of PPDs. The CUPS developers have extended the scope of the PPD
@@ -2248,6 +2231,7 @@ proper raster print format.
 <sect2>
 <title>PPDs for non-PS Printers on Windows</title>
 
+<indexterm><primary>PPD</primary></indexterm>
 <para>
 CUPS-PPDs can also be used on Windows-Clients, on top of a
 "core" PostScript driver (now recommended is the "CUPS PostScript
@@ -2309,7 +2293,7 @@ of Death" on a regular basis?
 PostScript drivers generally are very well tested. They are not known
 to cause any problems, even though they run in Kernel Mode too. This
 might be because there have so far only been 2 different PostScript
-drivers the ones from Adobe and the one from Microsoft. Both are
+drivers: the ones from Adobe and the one from Microsoft. Both are
 very well tested and are as stable as you ever can imagine on
 Windows. The CUPS driver is derived from the Microsoft one.
 </para>
@@ -2332,6 +2316,9 @@ better, if driven by a different driver! )
 <sect2>
 <title>CUPS: a "Magical Stone"?</title>
 
+<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+
 <para>
 Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very
 elegant way to overcome all these shortcomings. There are, depending
@@ -2351,6 +2338,7 @@ although the first feedbacks look very promising.
 <title>PostScript Drivers with no major problems -- even in Kernel
 Mode</title>
 
+<indexterm><primary>DDK</primary></indexterm>
 <para>
 More recent printer drivers on W2K and XP don't run in Kernel mode
 (unlike Win NT) any more. However, both operating systems can still
@@ -2372,7 +2360,7 @@ owner of an "MS DDK for Win NT", you can check the driver yourself.
 </sect1>
 
 <sect1>
-<title> Setting up CUPS for driver Download</title>
+<title>Setting up CUPS for driver Download</title>
 
 <para>
 As we have said before: all previously known methods to prepare client
@@ -2386,10 +2374,12 @@ relationship.
 <sect2>
 <title><emphasis>cupsaddsmb</emphasis>: the unknown Utility</title>
 
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+
 <para>
 The cupsaddsmb utility (shipped with all current CUPS versions) is an
 alternative method to transfer printer drivers into the Samba
-<parameter>[print$]</parameter> share. Remember, this share is where
+<smbconfsection>[print$]</smbconfsection> share. Remember, this share is where
 clients expect drivers deposited and setup for download and
 installation.  It makes the sharing of any (or all) installed CUPS
 printers very easy. cupsaddsmb can use the Adobe PostScript driver as
@@ -2427,68 +2417,66 @@ too if you need to support Windows 95, 98, and ME clients.
 </sect2>
 
 <sect2>
-<title>Prepare your <filename>smb.conf</filename> for
-cupsaddsmb</title>
+<title>Prepare your &smb.conf; for cupsaddsmb</title>
 
 <para>
 Prior to running cupsaddsmb, you need the following settings in
-<filename>smb.conf</filename>:
-</para>
-
-<para><screen>
-
- [global]
-         load printers = yes
-         printing = cups
-         printcap name = cups
-
- [printers]
-         comment = All Printers
-         path = /var/spool/samba
-         browseable = no
-         public = yes
-         guest ok = yes           # setting depends on your requirements
-         writable = no
-         printable = yes
-         printer admin = root
-
- [print$]
-         comment = Printer Drivers
-         path = /etc/samba/drivers
-         browseable = yes
-         guest ok = no
-         read only = yes
-         write list = root  
-
-</screen></para>
+&smb.conf;:
+</para>
+
+<para><smbconfexample>
+		<title>smb.conf for cupsaddsmb usage</title>
+<smbconfsection>[global]</smbconfsection>
+<smbconfoption><name>load printers</name><value>yes</value></smbconfoption>
+<smbconfoption><name>printing</name><value>cups</value></smbconfoption>
+<smbconfoption><name>printcap name</name><value>cups</value></smbconfoption>
+
+<smbconfsection>[printers]</smbconfsection>
+<smbconfoption><name>comment</name><value>All Printers</value></smbconfoption>
+<smbconfoption><name>path</name><value>/var/spool/samba</value></smbconfoption>
+<smbconfoption><name>browseable</name><value>no</value></smbconfoption>
+<smbconfoption><name>public</name><value>yes</value></smbconfoption>
+<smbconfcomment>setting depends on your requirements</smbconfcomment>
+<smbconfoption><name>guest ok</name><value>yes</value></smbconfoption>
+<smbconfoption><name>writable</name><value>no</value></smbconfoption>
+<smbconfoption><name>printable</name><value>yes</value></smbconfoption>
+<smbconfoption><name>printer admin</name><value>root</value></smbconfoption>
+ <smbconfsection>[print$]</smbconfsection>
+<smbconfoption><name>comment</name><value>Printer Drivers</value></smbconfoption>
+<smbconfoption><name>path</name><value>/etc/samba/drivers</value></smbconfoption>
+<smbconfoption><name>browseable</name><value>yes</value></smbconfoption>
+<smbconfoption><name>guest ok</name><value>no</value></smbconfoption>
+<smbconfoption><name>read only</name><value>yes</value></smbconfoption>
+<smbconfoption><name>write list</name><value>root</value></smbconfoption>
+</smbconfexample></para>
 </sect2>
 
 <sect2>
 <title>CUPS Package of "PostScript Driver for WinNT/2k/XP"</title>
+<indexterm><primary>PostScript</primary></indexterm>
 
 <para>
-CUPS users may get the exactly same packages from<ulink
-url="http://www.cups.org/software.html"><emphasis>http://www.cups.org/software.html</emphasis></ulink>.
+CUPS users may get the exactly same packages from <ulink
+noescape="1" url="http://www.cups.org/software.html">http://www.cups.org/software.html</ulink>.
 It is a separate package from the CUPS base software files, tagged as
-<emphasis>CUPS 1.1.x Windows NT/2k/XP Printer Driver for SAMBA
+<emphasis>CUPS 1.1.x Windows NT/2k/XP Printer Driver for Samba
 (tar.gz, 192k)</emphasis>. The filename to download is
 <filename>cups-samba-1.1.x.tar.gz</filename>. Upon untar-/unzip-ing,
 it will reveal these files:
 </para>
 
 <para><screen>
-
-# tar xvzf cups-samba-1.1.19.tar.gz 
-
-   cups-samba.install
-   cups-samba.license
-   cups-samba.readme
-   cups-samba.remove
-   cups-samba.ss
-
+&rootprompt;<userinput>tar xvzf cups-samba-1.1.19.tar.gz</userinput>
+cups-samba.install
+cups-samba.license
+cups-samba.readme
+cups-samba.remove
+cups-samba.ss
 </screen></para>
 
 <para>
+<indexterm><primary>ESP</primary><secondary>meta packager</secondary></indexterm>
+<indexterm><primary>EPM</primary><see>ESP meta packager</see></indexterm>
 These have been packaged with the ESP meta packager software
 "EPM". The <filename>*.install</filename> and
 <filename>*.remove</filename> files are simple shell scripts, which
@@ -2500,13 +2488,10 @@ files:
 </para>
 
 <para><screen>
-
-# tar tv cups-samba.ss
-
-    cupsdrvr.dll
-    cupsui.dll
-    cups.hlp  
-
+&rootprompt;<userinput>tar tv cups-samba.ss</userinput>
+cupsdrvr.dll
+cupsui.dll
+cups.hlp  
 </screen></para>
 
 <para>
@@ -2515,15 +2500,12 @@ handle:
 </para>
 
 <para><screen>
-
-# ./cups-samba.install
-
-   [....]
-   Installing software...
-   Updating file permissions...
-   Running post-install commands...
-   Installation is complete.        
-
+&rootprompt;<userinput>./cups-samba.install</userinput>
+[....]
+Installing software...
+Updating file permissions...
+Running post-install commands...
+Installation is complete.        
 </screen></para>
 
 <para>
@@ -2542,11 +2524,11 @@ right place.
 </para></warning>
 
 <para><screen>
-
-   cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
-
+&rootprompt;<userinput>cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/</userinput>
 </screen></para>
 
+<indexterm><primary>DDK</primary></indexterm>
+
 <para>
 This new CUPS PostScript driver is currently binary-only, but free of
 charge. No complete source code is provided (yet). The reason is this:
@@ -2567,14 +2549,15 @@ The CUPS drivers don't support the "older" Windows 95/98/ME, but only
 the Windows NT/2000/XP client:
 </para>
 
-<para><screen>
+<para>Windows NT, 2000, and XP are supported by:</para>
 
- [Windows NT, 2000, and XP are supported by:]
-         cups.hlp
-         cupsdrvr.dll
-         cupsui.dll
-
-</screen></para>
+<para>
+	<itemizedlist>
+		<listitem><para>cups.hlp</para></listitem>
+		<listitem><para>cupsdrvr.dll</para></listitem>
+		<listitem><para>cupsui.dll</para></listitem>
+	</itemizedlist>
+</para>
 
 <para>
 Adobe drivers are available for the older Windows 95/98/ME as well as
@@ -2582,22 +2565,29 @@ the Windows NT/2000/XP clients. The set of files is different for the
 different platforms.
 </para>
 
-<para><screen>
+<para>Windows 95, 98, and Me are supported by:</para>
 
- [Windows 95, 98, and Me are supported by:]
-         ADFONTS.MFM
-         ADOBEPS4.DRV
-         ADOBEPS4.HLP
-         DEFPRTR2.PPD
-         ICONLIB.DLL
-         PSMON.DLL
+<para>
+	<itemizedlist>
+	<listitem><para>ADFONTS.MFM</para></listitem>
+	<listitem><para>ADOBEPS4.DRV</para></listitem>
+	<listitem><para>ADOBEPS4.HLP</para></listitem>
+	<listitem><para>DEFPRTR2.PPD</para></listitem>
+	<listitem><para>ICONLIB.DLL</para></listitem>
+	<listitem><para>PSMON.DLL</para></listitem>
+</itemizedlist>
+</para>
 
- [Windows NT, 2000, and XP are supported by:]
-         ADOBEPS5.DLL
-         ADOBEPSU.DLL
-         ADOBEPSU.HLP
+<para>Windows NT, 2000, and XP are supported by:</para>
 
-</screen></para>
+<para>
+<itemizedlist>
+	<listitem><para>ADOBEPS5.DLL</para></listitem>
+	<listitem><para>ADOBEPSU.DLL</para></listitem>
+	<listitem><para>ADOBEPSU.HLP</para></listitem>
+</itemizedlist>
+
+</para>
 
 <note><para>
 If both, the Adobe driver files and the CUPS driver files for the
@@ -2620,7 +2610,7 @@ native installer and run the installation process on one client
 once. This will install the drivers (and one Generic PostScript
 printer) locally on the client.  When they are installed, share the
 Generic PostScript printer.  After this, the client's
-<parameter>[print$]</parameter> share holds the Adobe files, from
+<smbconfsection>[print$]</smbconfsection> share holds the Adobe files, from
 where you can get them with smbclient from the CUPS host. A more
 detailed description about this is in the next (the CUPS printing)
 chapter.
@@ -2631,19 +2621,22 @@ chapter.
 <title>ESP Print Pro Package of "PostScript Driver for
 WinNT/2k/XP"</title>
 
+
+<indexterm><primary>ESP</primary><secondary>Print Pro</secondary></indexterm>
+
 <para>
 Users of the ESP Print Pro software are able to install their "Samba
 Drivers" package for this purpose with no problem. Retrieve the driver
 files from the normal download area of the ESP Print Pro software
-at<ulink
-url="http://www.easysw.com/software.html">http://www.easysw.com/software.html</ulink>.
+at <ulink
+	noescape="1" url="http://www.easysw.com/software.html">http://www.easysw.com/software.html</ulink>.
 You need to locate the link labelled "SAMBA" amongst the
 <emphasis>Download Printer Drivers for ESP Print Pro 4.x</emphasis>
 area and download the package. Once installed, you can prepare any
 driver by simply highlighting the printer in the Printer Manager GUI
 and select <emphasis>Export Driver...</emphasis> from the menu. Of
 course you need to have prepared Samba beforehand too to handle the
-driver files; i.e.  mainly setup the <parameter>[print$]</parameter>
+driver files; i.e.  mainly setup the <smbconfsection>[print$]</smbconfsection>
 share, etc. The ESP Print Pro package includes the CUPS driver files
 as well as a (licensed) set of Adobe drivers for the Windows 95/98/ME
 client family.
@@ -2653,11 +2646,13 @@ client family.
 <sect2>
 <title>Caveats to be considered</title>
 
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+
 <para>
 Once you have run the install script (and possibly manually
 moved the <filename>cups.hlp</filename> file to
 <filename>/usr/share/cups/drivers/</filename>), the driver is
-ready to be put into Samba's <parameter>[print$]</parameter> share (which often maps to
+ready to be put into Samba's <smbconfsection>[print$]</smbconfsection> share (which often maps to
 <filename>/etc/samba/drivers/</filename> and contains a subdir
 tree with <emphasis>WIN40</emphasis> and
 <emphasis>W32X86</emphasis> branches): You do this by running
@@ -2666,6 +2661,7 @@ CUPS since release 1.1.16).
 </para>
 
 <tip><para>
+<indexterm><primary>Single Sign On</primary></indexterm>
 You may need to put root into the smbpasswd file by running
 <command>smbpasswd</command>; this is especially important if you
 should run this whole procedure for the first time, and are not
@@ -2674,7 +2670,7 @@ working in an environment where everything is configured for
 </para></tip>
 
 <para>
-Once the driver files are in the <parameter>[print$]</parameter> share
+Once the driver files are in the <smbconfsection>[print$]</smbconfsection> share
 and are initialized, they are ready to be downloaded and installed by
 the Win NT/2k/XP clients.
 </para>
@@ -2696,6 +2692,7 @@ automatically prefer "its own" drivers if it finds both.
 </para></listitem>
 
 <listitem><para>
+<indexterm><primary>"Printers" folder</primary></indexterm>
 Should your Win clients have had the old <filename>ADOBE*.*</filename>
 files for the Adobe PostScript driver installed, the download and
 installation of the new CUPS PostScript driver for Windows NT/2k/XP
@@ -2703,8 +2700,7 @@ will fail at first. You need to wipe the old driver from the clients
 first. It is not enough to "delete" the printer, as the driver files
 will still be kept by the clients and re-used if you try to re-install
 the printer. To really get rid of the Adobe driver files on the
-clients, open the "Printers" folder (possibly via <emphasis>Start
---&gt; Settings --&gt; Control Panel --&gt; Printers</emphasis>),
+clients, open the "Printers" folder (possibly via <emphasis>Start, Settings, Control Panel, Printers</emphasis>),
 right-click onto the folder background and select <emphasis>Server
 Properties</emphasis>. When the new dialog opens, select the
 <emphasis>Drivers</emphasis> tab. On the list select the driver you
@@ -2716,9 +2712,10 @@ Administrator privileges to do this.
 </para></listitem>
 
 <listitem><para>
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
 Once you have successfully downloaded the CUPS PostScript driver to a
 client, you can easily switch all printers to this one by proceeding
-as described elsewhere in the "Samba HOWTO Collection": either change
+as described in <link linkend="printing">the printing chapter</link>: either change
 a driver for an existing printer by running the "Printer Properties"
 dialog, or use <command>rpcclient</command> with the
 <command>setdriver</command> sub-command.
@@ -2728,8 +2725,8 @@ dialog, or use <command>rpcclient</command> with the
 </sect2>
 
 <sect2>
-<title>What are the Benefits of using the "CUPS PostScript Driver for
-Windows NT/2k/XP" as compared to the Adobe Driver?</title>
+<title>Benefits of using "CUPS PostScript Driver for
+Windows NT/2k/XP" instead of Adobe Driver</title>
 
 <para>
 You are interested in a comparison between the CUPS and the Adobe
@@ -2743,7 +2740,9 @@ items which weigh in favor of the CUPS ones:
 <listitem><para>no hassle with the question <quote>Where do I
 get the ADOBE*.* driver files from?</quote></para></listitem>
 
-<listitem><para>the Adobe drivers (on request of the printer PPD
+<listitem><para>
+<indexterm><primary>PJL</primary></indexterm>
+		the Adobe drivers (on request of the printer PPD
 associated with them) often put a PJL header in front of the main
 PostScript part of the print file. Thus the printfile starts with
 <parameter>&lt;1B &gt;%-12345X</parameter> or
@@ -2752,8 +2751,10 @@ of <parameter>%!PS</parameter>). This leads to the
 CUPS daemon auto-typing the incoming file as a print-ready file,
 not initiating a pass through the "pstops" filter (to speak more
 technically, it is not regarded as the generic MIME type 
+<indexterm><primary>application/postscript</primary></indexterm>
 <emphasis>application/postscript</emphasis>, but as
 the more special MIME type
+<indexterm><primary>application/cups.vnd-postscript</primary></indexterm>
 <emphasis>application/cups.vnd-postscript</emphasis>),
 which therefore also leads to the page accounting in
 <emphasis>/var/log/cups/page_log</emphasis> not
@@ -2801,42 +2802,33 @@ fully fledged CUPS IPP client for Windows NT/2K/XP to be released soon
 <sect2>
 <title>Run "cupsaddsmb" (quiet Mode)</title>
 
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+<indexterm><primary>point and print</primary></indexterm>
+
 <para>
 The cupsaddsmb command copies the needed files into your
-<parameter>[print$]</parameter> share. Additionally, the PPD
+<smbconfsection>[print$]</smbconfsection> share. Additionally, the PPD
 associated with this printer is copied from
 <filename>/etc/cups/ppd/</filename> to
-<parameter>[print$]</parameter>. There the files wait for convenient
+<smbconfsection>[print$]</smbconfsection>. There the files wait for convenient
 Windows client installations via Point'n'Print. Before we can run the
 command successfully, we need to be sure that we can authenticate
 towards Samba. If you have a small network you are probably using user
-level security (<parameter>security = user</parameter>). Probably your
-root has already a Samba account. Otherwise, create it now, using
-<command>smbpasswd</command>:
+level security (<smbconfoption><name>security</name><value>user</value></smbconfoption>). 
 </para>
 
-<para><screen>
-
- #  smbpasswd -a root 
- New SMB password: [type in password 'secret']
- Retype new SMB password: [type in password 'secret']
-
-</screen></para>
-
 <para>
 Here is an example of a successfully run cupsaddsmb command. 
 </para>
 
 <para><screen>
-
- #  cupsaddsmb -U root infotec_IS2027
- Password for root required to access localhost via SAMBA: [type in password 'secret']
-
+&rootprompt;<userinput>cupsaddsmb -U root infotec_IS2027</userinput>
+Password for root required to access localhost via Samba: <userinput>['secret']</userinput>
 </screen></para>
 
 <para>
 To share <emphasis>all</emphasis> printers and drivers, use the
-<parameter>-a</parameter> parameter instead of a printer name. Since
+<option>-a</option> parameter instead of a printer name. Since
 cupsaddsmb "exports" the printer drivers to Samba, it should be
 obvious that it only works for queues with a CUPS driver associated.
 </para>
@@ -2845,9 +2837,11 @@ obvious that it only works for queues with a CUPS driver associated.
 <sect2>
 <title>Run "cupsaddsmb" with verbose Output</title>
 
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+
 <para>
 Probably you want to see what's going on. Use the
-<parameter>-v</parameter> parameter to get a more verbose output. The
+<option>-v</option> parameter to get a more verbose output. The
 output below was edited for better readability: all "\" at the end of
 a line indicate that I inserted an artificial line break plus some
 indentation here:
@@ -2855,86 +2849,79 @@ indentation here:
 
 <warning><para>
 You will see the root password for the Samba account printed on
-screen. If you use remote access, the password will go over the wire
-unencrypted!
+screen. 
 </para></warning>
 
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
 <para><screen>
-
-  # cupsaddsmb -U root -v infotec_2105
-  Password for root required to access localhost via SAMBA:
-  Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put   \
-                   /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd;put           \
-                   /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll;put            \
-                   /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll;put                \
-                   /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
-  added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-  Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
-  NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
-  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \W32X86/infotec_2105.ppd (2328.8 kb/s) \
-               (average 2328.8 kb/s)
-  putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll (9374.3 kb/s)  \
-               (average 5206.6 kb/s)
-  putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll (8107.2 kb/s)      \
-               (average 5984.1 kb/s)
-  putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp (3475.0 kb/s)          \
-               (average 5884.7 kb/s)
+&rootprompt;<userinput>cupsaddsmb -U root -v infotec_2105</userinput>
+Password for root required to access localhost via &example.server.samba;:
+Running command: smbclient //localhost/print\$ -N -U'root%secret' \
+    -c 'mkdir W32X86; \
+    put /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd; \
+	put /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll; \
+    put /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll; \
+    put /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
+added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
+putting file /var/spool/cups/tmp/3e98bf2d333b5 as \W32X86/infotec_2105.ppd
+putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll
+putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll
+putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp
   
-  Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"   \
-                   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:   \
-                   RAW:NULL"'
-  cmd = adddriver "Windows NT x86" "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll: \
-                   cups.hlp:NULL:RAW:NULL"
-  Printer Driver infotec_2105 successfully installed.
+Running command: rpcclient localhost -N -U'root%secret' 
+   -c 'adddriver "Windows NT x86"   \
+   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:   \
+    RAW:NULL"'
+cmd = adddriver "Windows NT x86" \
+    "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"
+Printer Driver infotec_2105 successfully installed.
   
-  Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put    \
-                   /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; put           \
-                   /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put               \
-                   /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put             \
-                   /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put             \
-                   /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put             \
-                   /usr/share/cups/drivers/ICONLIB.DLL
-  WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
+Running command: smbclient //localhost/print\$ -N -U'root%secret' \
+-c 'mkdir WIN40; \
+    put /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; \
+	put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;   \
+    put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV; \
+    put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP; \
+    put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD; \
+	put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL; \
+	put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
   added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-  Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
+  Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
   NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
-  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \WIN40/infotec_2105.PPD (2328.8 kb/s)  \
-               (average 2328.8 kb/s)
-  putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (9368.0 kb/s)     \
-               (average 6469.6 kb/s)
-  putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (9958.2 kb/s)   \
-               (average 8404.3 kb/s)
-  putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (8341.5 kb/s)   \
-               (average 8398.6 kb/s)
-  putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (2195.9 kb/s)   \
-               (average 8254.3 kb/s)
-  putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (8239.9 kb/s)     \
-               (average 8253.6 kb/s)
-  putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (6222.2 kb/s)         \
-               (average 8188.5 kb/s)
+  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \WIN40/infotec_2105.PPD
+  putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM
+  putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV
+  putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP
+  putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD
+  putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL
+  putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL
   
-  Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"      \
-                   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP:          \
-                   PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL,     \
-                   ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+  Running command: rpcclient localhost -N -U'root%secret' \
+   -c 'adddriver "Windows 4.0"      \
+   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
+   PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL, \
+    ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
   cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:          \
-                   ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,  \
+    ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,  \
                    PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
   Printer Driver infotec_2105 successfully installed.
   
-  Running command: rpcclient localhost -N -U'root%secret'                                  \
-                             -c 'setdriver infotec_2105 infotec_2105'
+  Running command: rpcclient localhost -N -U'root%secret'  \
+   -c 'setdriver infotec_2105 infotec_2105'
   cmd = setdriver infotec_2105 infotec_2105
   Successfully set infotec_2105 to driver infotec_2105.
 
 </screen></para>
 
 <para>
-If you look closely, you'll discover your root password was transfered
+If you look closely, you'll discover your root password was transferred
 unencrypted over the wire, so beware! Also, if you look further her,
 you'll discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in
 between. They occur, because the directories WIN40 and W32X86 already
-existed in the <parameter>[print$]</parameter> driver download share
+existed in the <smbconfsection>[print$]</smbconfsection> driver download share
 (from a previous driver installation). They are harmless here.
 </para>
 </sect2>
@@ -2942,14 +2929,17 @@ existed in the <parameter>[print$]</parameter> driver download share
 <sect2>
 <title>Understanding cupsaddsmb</title>
 
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+
 <para>
 What has happened? What did cupsaddsmb do? There are five stages of
 the procedure
 </para>
 
 <orderedlist>
-
-<listitem><para>call the CUPS server via IPP and request the
+	<listitem><para>
+	<indexterm><primary>IPP</primary></indexterm>
+			call the CUPS server via IPP and request the
 driver files and the PPD file for the named printer;</para></listitem>
 
 <listitem><para>store the files temporarily in the local
@@ -2957,15 +2947,19 @@ TEMPDIR (as defined in
 <filename>cupsd.conf</filename>);</para></listitem>
 
 <listitem><para>connect via smbclient to the Samba server's
- <parameter>[print$]</parameter> share and put the files into the
+ <smbconfsection>[print$]</smbconfsection> share and put the files into the
  share's WIN40 (for Win95/98/ME) and W32X86/ (for WinNT/2k/XP) sub
  directories;</para></listitem>
 
-<listitem><para>connect via rpcclient to the Samba server and
+<listitem><para>
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+		connect via rpcclient to the Samba server and
 execute the "adddriver" command with the correct
 parameters;</para></listitem>
 
-<listitem><para>connect via rpcclient to the Samba server a second
+<listitem><para>
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+		connect via rpcclient to the Samba server a second
 time and execute the "setdriver" command.</para></listitem>
 </orderedlist>
 
@@ -2979,14 +2973,12 @@ same host):
 </para>
 
 <para><screen>
-
- # cupsaddsmb -H sambaserver -h cupsserver -v printername
-
+&rootprompt;<userinput>cupsaddsmb -H sambaserver -h cupsserver -v printername</userinput>
 </screen></para>
 </sect2>
 
 <sect2>
-<title>How to recognize if cupsaddsm completed successfully</title>
+<title>How to recognize if cupsaddsmb completed successfully</title>
 
 <para>
 You <emphasis>must</emphasis> always check if the utility completed
@@ -3010,7 +3002,7 @@ architecture...)</para></listitem>
 
 <para>
 These messages probably not easily recognized in the general
-output. If you run cupsaddsmb with the <parameter>-a</parameter>
+output. If you run cupsaddsmb with the <option>-a</option>
 parameter (which tries to prepare <emphasis>all</emphasis> active CUPS
 printer drivers for download), you might miss if individual printers
 drivers had problems to install properly. Here a redirection of the
@@ -3028,6 +3020,8 @@ might occur.
 <sect2>
 <title>cupsaddsmb with a Samba PDC</title>
 
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+
 <para>
 You can't get the standard cupsaddsmb command to run on a Samba PDC?
 You are asked for the password credential all over again and again and
@@ -3036,11 +3030,9 @@ variations:
 </para>
 
 <para><screen>
-
- # cupsaddsmb -U DOMAINNAME\\root -v printername
- # cupsaddsmb -H SAMBA-PDC -U DOMAINNAME\\root -v printername
- # cupsaddsmb -H SAMBA-PDC -U DOMAINNAME\\root -h cups-server -v printername
-
+&rootprompt;<userinput>cupsaddsmb -U &example.workgroup;\\root -v printername</userinput>
+&rootprompt;<userinput>cupsaddsmb -H &example.pdc.samba; -U &example.workgroup;\\root -v printername</userinput>
+&rootprompt;<userinput>cupsaddsmb -H &example.pdc.samba; -U &example.workgroup;\\root -h cups-server -v printername</userinput>
 </screen></para>
 
 <para>
@@ -3052,6 +3044,7 @@ variations:
 <sect2>
 <title>cupsaddsmb Flowchart</title>
 
+<indexterm><primary>cupsaddsmb</primary></indexterm>
 <para>
 Here is a chart about the procedures, commandflows and
 dataflows of the "cupaddsmb" command. Note again: cupsaddsmb is
@@ -3059,18 +3052,15 @@ not intended to, and does not work with, "raw" queues!
 </para>
 
 <para>
-<figure><title>cupsaddsmb flowchart</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/1small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/1small.png"/></imageobject>
-</mediaobject>
-</figure>
+	<image id="small14"><imagedescription>cupsaddsmb flowchart</imagedescription>
+		<imagefile>14small</imagefile></image>
 </para>
 </sect2>
 
 <sect2>
 <title>Installing the PostScript Driver on a Client</title>
 
+<indexterm><primary>point and print</primary></indexterm>
 <para>
 After cupsaddsmb completed, your driver is prepared for the clients to
 use. Here are the steps you must perform to download and install it
@@ -3080,6 +3070,8 @@ server;
 
 <itemizedlist>
 
+<indexterm><primary>"Printers" folder</primary></indexterm>
+
 <listitem><para>open the <emphasis>Printers</emphasis>
 share of Samba in Network Neighbourhood;</para></listitem>
 
@@ -3104,6 +3096,7 @@ dropdown list of available printers.
 </para>
 
 <note><para>
+<indexterm><primary>PPD</primary></indexterm>
 cupsaddsmb will only reliably work with CUPS version 1.1.15 or higher
 and Samba from 2.2.4. If it doesn't work, or if the automatic printer
 driver download to the clients doesn't succeed, you can still manually
@@ -3113,9 +3106,7 @@ share for a UNC type of connection:
 </para></note>
 
 <para><screen>
-
-  net use lpt1: \\sambaserver\printershare /user:ntadmin
-
+&dosprompt;<userinput>net use lpt1: \\sambaserver\printershare /user:ntadmin</userinput>
 </screen></para>
 
 <para>
@@ -3190,16 +3181,25 @@ printer should be there. We are providing the driver
 now);</para></listitem>
 
 <listitem><para>copy all files to
-<parameter>[print$]:</parameter></para></listitem>
+		<smbconfsection>[print$]</smbconfsection></para></listitem>
 
-<listitem><para>run <command>rpcclient adddriver</command>
+<listitem><para>
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+		run <command>rpcclient adddriver</command>
 (for each client architecture you want to support):</para></listitem>
 
-<listitem><para>run <command>rpcclient
+<listitem><para>
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+		run <command>rpcclient
 setdriver.</command></para></listitem>
 </orderedlist>
 
 <para>
+<indexterm><primary>rpcclient</primary><secondary>enumports</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>enumdrivers</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
 We are going to do this now. First, read the man page on "rpcclient"
 to get a first idea. Look at all the printing related
 sub-commands. <command>enumprinters</command>,
@@ -3265,7 +3265,7 @@ obtaining a list of installed printers and drivers.
 </sect2>
 
 <sect2>
-<title>Understanding the rpcclient man Page</title>
+<title>Understanding the rpcclient man page</title>
 
 <para>
 The <emphasis>exact</emphasis> format isn't made too clear by the man
@@ -3275,12 +3275,12 @@ command and indicated the breaks with "\". Usually you would type the
 command in one line without the linebreaks:
 </para>
 
-<para><screen>
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
 
+<para><screen>
  adddriver "Architecture" \
            "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
            LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
-
 </screen></para>
 
 <para>
@@ -3316,6 +3316,8 @@ now.
 <title>Producing an Example by querying a Windows Box</title>
 
 <para>
+	<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
+	<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
 We could run <command>rpcclient</command> with a
 <command>getdriver</command> or a <command>getprinter</command>
 subcommand (in level 3 verbosity) against it. Just sit down at UNIX or
@@ -3324,9 +3326,7 @@ following command:
 </para>
 
 <para><screen>
-
- rpcclient -U'USERNAME%PASSWORD' NT-SERVER-NAME -c 'getdriver printername 3'
-
+&rootprompt;<userinput>rpcclient -U'USERNAME%PASSWORD' NT-SERVER-NAME -c 'getdriver printername 3'</userinput>
 </screen></para>
 
 <para>
@@ -3334,9 +3334,10 @@ From the result it should become clear which is which. Here is an
 example from my installation:
 </para>
 
+	<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
 <para><screen>
-
-# rpcclient -U'Danka%xxxx' W2KSERVER -c'getdriver "DANKA InfoStream Virtual Printer" 3'
+&rootprompt;<userinput>rpcclient -U'Danka%xxxx' W2KSERVER \
+	-c'getdriver "DANKA InfoStream Virtual Printer" 3'</userinput>
  cmd = getdriver "DANKA InfoStream Virtual Printer" 3
 
  [Windows NT x86]
@@ -3379,17 +3380,18 @@ From the manpage (and from the quoted output
 of <emphasis>cupsaddsmb</emphasis>, above) it becomes clear that you
 need to have certain conditions in order to make the manual uploading
 and initializing of the driver files succeed. The two rpcclient
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
 subcommands (<command>adddriver</command> and
 <command>setdriver</command>) need to encounter the following
 pre-conditions to complete successfully:
 </para>
 <itemizedlist>
 
-<listitem><para>you are connected as "printer admin", or root (note,
+<listitem><para>you are connected as <smbconfoption><name>printer admin</name></smbconfoption>, or root (note,
 that this is <emphasis>not</emphasis> the "Printer Operators" group in
 NT, but the <emphasis>printer admin</emphasis> group, as defined in
-the <parameter>[global]</parameter> section of
-<filename>smb.conf</filename>);</para></listitem>
+the <smbconfsection>[global]</smbconfsection> section of
+&smb.conf;);</para></listitem>
 
 <listitem><para>copy all required driver files to
 <filename>\\sambaserver\print$\w32x86</filename> and
@@ -3402,13 +3404,16 @@ to escape the "$": <command>smbclient //sambaserver/print\$ -U
 root</command>);</para></listitem>
 
 <listitem><para>the user you're connecting as must be able to write to
-the <parameter>[print$]</parameter> share and create
+the <smbconfsection>[print$]</smbconfsection> share and create
 subdirectories;</para></listitem>
 
 <listitem><para>the printer you are going to setup for the Windows
 clients, needs to be installed in CUPS already;</para></listitem>
 
-<listitem><para>the CUPS printer must be known to Samba, otherwise the
+<listitem><para>
+	<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+	<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
+		the CUPS printer must be known to Samba, otherwise the
 <command>setdriver</command> subcommand fails with an
 NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by
 Samba you may use the <command>enumprinters</command> subcommand to
@@ -3421,7 +3426,7 @@ Samba.</para></listitem>
 </sect2>
 
 <sect2>
-<title>Manual Commandline Driver Installation in 15 little Steps</title>
+<title>Manual Driver Installation in 15 Steps</title>
 
 <para>
 We are going to install a printer driver now by manually executing all
@@ -3430,13 +3435,14 @@ first, we go through the procedure step by step, explaining every
 single action item as it comes up.
 </para>
 
-<sect3>
-<title>First Step: Install the Printer on CUPS</title>
-
-<para><screen>
+<procedure>
+	<title>Manual Driver Installation installation</title>
 
-# lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E -P /home/kurt/canonIR85.ppd
+<step>
+<title>Install the Printer on CUPS</title>
 
+<para><screen>
+&rootprompt;<userinput>lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E -P canonIR85.ppd</userinput>
 </screen></para>
 
 <para>
@@ -3445,21 +3451,19 @@ to the CUPS system. The printer is accessed via a socket
 (a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
 for this step
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Second Step (optional): Check if the Printer is recognized by
+<step>
+<title>(optional) Check if the Printer is recognized by
 Samba</title>
 
+	<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
 <para><screen>
-
- # rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn
-
-        flags:[0x800000]
-        name:[\\kde-bitshop\mysmbtstprn]
-        description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
-        comment:[mysmbtstprn]
-
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn</userinput>
+flags:[0x800000]
+name:[\\kde-bitshop\mysmbtstprn]
+description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
+comment:[mysmbtstprn]
 </screen></para>
 
 <para>
@@ -3471,32 +3475,35 @@ success. Note the "empty" field between the two commas in the
 already. You need to know root's Samba password (as set by the
 <command>smbpasswd</command> command) for this step and most of the
 following steps. Alternatively you can authenticate as one of the
-users from the "write list" as defined in <filename>smb.conf</filename> for
-<parameter>[print$]</parameter>.
+users from the "write list" as defined in &smb.conf; for
+<smbconfsection>[print$]</smbconfsection>.
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Third Step (optional): Check if Samba knows a Driver for the
+<step>
+<title>(optional) Check if Samba knows a Driver for the
 Printer</title>
 
+	<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
+	<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
 <para><screen>
-
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver
-         drivername:[]
- 
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep -C4 driv
-        servername:[\\kde-bitshop]
-        printername:[\\kde-bitshop\mysmbtstprn]
-        sharename:[mysmbtstprn]
-        portname:[Samba Printer Port]
-        drivername:[]
-        comment:[mysmbtstprn]
-        location:[]
-        sepfile:[]
-        printprocessor:[winprint]
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+			| grep driver </userinput>
+drivername:[]
+
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+	| grep -C4 driv</userinput>
+servername:[\\kde-bitshop]
+printername:[\\kde-bitshop\mysmbtstprn]
+sharename:[mysmbtstprn]
+portname:[Samba Printer Port]
+drivername:[]
+comment:[mysmbtstprn]
+location:[]
+sepfile:[]
+printprocessor:[winprint]
  
-#  rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
+&rootprompt;<userinput>rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost</userinput>
  result was WERR_UNKNOWN_PRINTER_DRIVER
 
 </screen></para>
@@ -3508,21 +3515,19 @@ attempt to connect to the printer at this stage will prompt the
 message along the lines: "The server has not the required printer
 driver installed".
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Fourth Step: Put all required Driver Files into Samba's
+<step>
+<title>Put all required Driver Files into Samba's
 [print$]</title>
 
 <para><screen>
-
-#  smbclient //localhost/print\$ -U 'root%xxxx'                        \ 
-                              -c 'cd W32X86;                                             \
-                                  put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD;     \
-                                  put /usr/share/cups/drivers/cupsui.dll cupsui.dll;     \
-                                  put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
-                                  put /usr/share/cups/drivers/cups.hlp cups.hlp'
-
+&rootprompt;<userinput>smbclient //localhost/print\$ -U 'root%xxxx' \
+	-c 'cd W32X86; \
+	put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD; \ 
+	put /usr/share/cups/drivers/cupsui.dll cupsui.dll; \
+	put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
+	put /usr/share/cups/drivers/cups.hlp cups.hlp'</userinput>
 </screen></para>
 
 <para>
@@ -3530,49 +3535,45 @@ driver installed".
 line. Line-breaks and the line-end indicating "\" has been inserted
 for readability reasons.) This step is <emphasis>required</emphasis>
 for the next one to succeed. It makes the driver files physically
-present in the <parameter>[print$]</parameter> share. However, clients
+present in the <smbconfsection>[print$]</smbconfsection> share. However, clients
 would still not be able to install them, because Samba does not yet
 treat them as driver files. A client asking for the driver would still
 be presented with a "not installed here" message.
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Fifth Step: Verify where the Driver Files are now</title>
+<step>
+<title>Verify where the Driver Files are now</title>
 
 <para><screen>
-
-#  ls -l /etc/samba/drivers/W32X86/
- total 669
- drwxr-sr-x    2 root     ntadmin       532 May 25 23:08 2
- drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
- -rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
- -rwxr--r--    1 root     ntadmin    278380 May 25 23:21 cupsdrvr.dll
- -rwxr--r--    1 root     ntadmin    215848 May 25 23:21 cupsui.dll
- -rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
-
+&rootprompt;<userinput>ls -l /etc/samba/drivers/W32X86/</userinput>
+total 669
+drwxr-sr-x    2 root     ntadmin       532 May 25 23:08 2
+drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
+-rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
+-rwxr--r--    1 root     ntadmin    278380 May 25 23:21 cupsdrvr.dll
+-rwxr--r--    1 root     ntadmin    215848 May 25 23:21 cupsui.dll
+-rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
 </screen></para>
 
 <para>
 The driver files now are in the W32X86 architecture "root" of
-<parameter>[print$]</parameter>.
+<smbconfsection>[print$]</smbconfsection>.
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Sixth Step: Tell Samba that these are
+<step>
+<title>Tell Samba that these are
 <emphasis>Driver</emphasis> Files
 (<command>adddriver</command>)</title>
 
+	<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
 <para><screen>
-
-#  rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
-                                          cupsdrvr.dll:mysmbtstprn.PPD:                  \
-                                          cupsui.dll:cups.hlp:NULL:RAW<citation>:</citation>NULL"             \
-                                          localhost
-
- Printer Driver mydrivername successfully installed.
-
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
+  cupsdrvr.dll:mysmbtstprn.PPD: \
+  cupsui.dll:cups.hlp:NULL:RAW:NULL" \
+  localhost</userinput>
+Printer Driver mydrivername successfully installed.
 </screen></para>
 
 <para>
@@ -3586,70 +3587,65 @@ the printername; however, in big installations you may use this driver
 for a number of printers which have obviously different names. So the
 name of the driver is not fixed.
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Seventh Step: Verify where the Driver Files are now</title>
+<step>
+<title>Verify where the Driver Files are now</title>
 
 <para><screen>
-
-#  ls -l /etc/samba/drivers/W32X86/
- total 1
- drwxr-sr-x    2 root     ntadmin       532 May 25 23:22 2
- drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
-
- 
-#  ls -l /etc/samba/drivers/W32X86/2
- total 5039
- [....]
- -rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
- -rwxr--r--    1 root     ntadmin    278380 May 13 13:53 cupsdrvr.dll
- -rwxr--r--    1 root     ntadmin    215848 May 13 13:53 cupsui.dll
- -rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
-
+&rootprompt;<userinput>ls -l /etc/samba/drivers/W32X86/</userinput>
+total 1
+drwxr-sr-x    2 root     ntadmin       532 May 25 23:22 2
+drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
+
+&rootprompt;<userinput>ls -l /etc/samba/drivers/W32X86/2</userinput>
+total 5039
+[....]
+-rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
+-rwxr--r--    1 root     ntadmin    278380 May 13 13:53 cupsdrvr.dll
+-rwxr--r--    1 root     ntadmin    215848 May 13 13:53 cupsui.dll
+-rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
 </screen></para>
 
 <para>
 Notice how step 6 did also move the driver files to the appropriate
 subdirectory. Compare with the situation after step 5.
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Eighth Step (optional): Verify if Samba now recognizes the
+<step>
+<title>(optional) Verify if Samba now recognizes the
 Driver</title>
 
+	<indexterm><primary>rpcclient</primary><secondary>enumdrivers</secondary></indexterm>
 <para><screen>
-
-#  rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost | grep -B2 -A5 mydrivername
-
- Printer Driver Info 3:
-        Version: [2]
-        Driver Name: [mydrivername]
-        Architecture: [Windows NT x86]
-        Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
-        Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
-        Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
-        Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
-
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost \
+	| grep -B2 -A5 mydrivername</userinput>
+Printer Driver Info 3:
+Version: [2]
+Driver Name: [mydrivername]
+Architecture: [Windows NT x86]
+Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
+Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
+Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
+Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
 </screen></para>
 
 <para>
 Remember, this command greps for the name you did choose for the
 driver in step Six. This command must succeed before you can proceed.
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Ninth Step: Tell Samba which Printer should use these Driver
+<step>
+<title>Tell Samba which Printer should use these Driver
 Files (<command>setdriver</command>)</title>
 
-<para><screen>
-
-#  rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost
- 
- Successfully set mysmbtstprn to driver mydrivername
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
 
+<para><screen>
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost</userinput>
+Successfully set mysmbtstprn to driver mydrivername
 </screen></para>
 
 <para>
@@ -3660,63 +3656,69 @@ setdriver command to succeed. The only pre-conditions are:
 <command>enumdrivers</command> must find the driver and
 <command>enumprinters</command> must find the printer.
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Tenth Step (optional): Verify if Samba has this Association
+<step>
+<title>(optional) Verify if Samba has this Association
 recognized</title>
 
+<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
 <para><screen>
-
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver
-       drivername:[mydrivername]
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+  | grep driver</userinput>
+drivername:[mydrivername]
  
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep -C4 driv
-       servername:[\\kde-bitshop]
-       printername:[\\kde-bitshop\mysmbtstprn]
-       sharename:[mysmbtstprn]
-       portname:[Done]
-       drivername:[mydrivername]
-       comment:[mysmbtstprn]
-       location:[]
-       sepfile:[]
-       printprocessor:[winprint]
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+  | grep -C4 driv</userinput>
+servername:[\\kde-bitshop]
+printername:[\\kde-bitshop\mysmbtstprn]
+sharename:[mysmbtstprn]
+portname:[Done]
+drivername:[mydrivername]
+comment:[mysmbtstprn]
+location:[]
+sepfile:[]
+printprocessor:[winprint]
  
-#  rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
- [Windows NT x86]
- Printer Driver Info 3:
-       Version: [2]
-       Driver Name: [mydrivername]
-       Architecture: [Windows NT x86]
-       Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
-       Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
-       Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
-       Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
-       Monitorname: []
-       Defaultdatatype: [RAW]
-       Monitorname: []
-       Defaultdatatype: [RAW]
+&rootprompt;<userinput>rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost</userinput>
+[Windows NT x86]
+Printer Driver Info 3:
+     Version: [2]
+     Driver Name: [mydrivername]
+     Architecture: [Windows NT x86]
+     Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
+     Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
+     Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
+     Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
+     Monitorname: []
+     Defaultdatatype: [RAW]
+     Monitorname: []
+     Defaultdatatype: [RAW]
  
-#  rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep mysmbtstprn
-       name:[\\kde-bitshop\mysmbtstprn]
-       description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
-       comment:[mysmbtstprn]
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep mysmbtstprn</userinput>
+     name:[\\kde-bitshop\mysmbtstprn]
+     description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
+     comment:[mysmbtstprn]
 
 </screen></para>
 
 <para>
+<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
 Compare these results with the ones from steps 2 and 3. Note that
 every single of these commands show the driver is installed.  Even
 the <command>enumprinters</command> command now lists the driver
 on the "description" line.
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Eleventh Step (optional): Tickle the Driver into a correct
+<step>
+<title>(optional) Tickle the Driver into a correct
 Device Mode</title>
 
 <para>
+<indexterm><primary>"Printers" folder</primary></indexterm>
 You certainly know how to install the driver on the client.  In case
 you are not particularly familiar with Windows, here is a short
 recipe: browse the Network Neighbourhood, go to the Samba server, look
@@ -3731,56 +3733,53 @@ folder, named something like "printersharename on Sambahostname".
 
 <para>
 It is important that you execute this step as a Samba printer admin
-(as defined in <filename>smb.conf</filename>). Here is another method
+(as defined in &smb.conf;). Here is another method
 to do this on Windows XP. It uses a commandline, which you may type
 into the "DOS box" (type root's smbpassword when prompted):
 </para>
 
 <para><screen>
-
- C:\&gt; runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n \\sambacupsserver\mysmbtstprn"
-
+&dosprompt;<userinput>runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n\
+			\\sambacupsserver\mysmbtstprn"</userinput>
 </screen></para>
 
 <para>
-Change any printer setting once (like <emphasis>"portrait"
---&gt; "landscape"</emphasis>), click "Apply"; change the setting
+Change any printer setting once (like changing <emphasis>"portrait" to
+	"landscape"</emphasis>), click <guibutton>Apply</guibutton>; change the setting
 back.
 </para>
-</sect3>
+</step>
 
-<sect3>
-<title>Twelfth Step: Install the Printer on a Client
+<step>
+<title>Install the Printer on a Client
 ("Point'n'Print")</title>
 
-<para><screen>
-
- C:\&gt; rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"
+<indexterm significance="preferred"><primary>point and print</primary></indexterm>
 
+<para><screen>
+&dosprompt;<userinput>rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"</userinput>
 </screen></para>
 
 <para>
 If it doesn't work it could be a permission problem with the
-<parameter>[print$]</parameter> share.
+<smbconfsection>[print$]</smbconfsection> share.
 </para>
-</sect3>
+</step>
 
-<sect3>
+<step>
 <title>Thirteenth Step (optional): Print a Test Page</title>
 
 <para><screen>
-
- C:\&gt; rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"
-
+&dosprompt;<userinput>rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"</userinput>
 </screen></para>
 
 <para>
 Then hit [TAB] 5 times, [ENTER] twice, [TAB] once and [ENTER] again
 and march to the printer.
 </para>
-</sect3>
+</step>
 
-<sect3>
+<step>
 <title>Fourteenth Step (recommended): Study the Test Page</title>
 
 <para>
@@ -3789,18 +3788,17 @@ installations and you don't need to read a word. Just put it in a
 frame and bolt it to the wall with the heading "MY FIRST
 RPCCLIENT-INSTALLED PRINTER" - why not just throw it away!
 </para>
-</sect3>
+</step>
 
-<sect3>
+<step>
 <title>Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your
 Success</title>
 
 <para><screen>
-
-# echo "Cheeeeerioooooo! Success..." &gt;&gt; /var/log/samba/log.smbd     
-
+&rootprompt;<userinput>echo "Cheeeeerioooooo! Success..." &gt;&gt; /var/log/samba/log.smbd</userinput>
 </screen></para>
-</sect3>
+</step>
+</procedure>
 </sect2>
 
 <sect2>
@@ -3829,7 +3827,8 @@ a disappointing message like this one beneath?
 </screen></para>
 
 <para>
-It is not good enough that <emphasis>you</emphasis>
+<indexterm><primary>lpstat</primary></indexterm>
+It is not good enough that you
 can see the queue <emphasis>in CUPS</emphasis>, using
 the <command>lpstat -p ir85wm</command> command. A
 bug in most recent versions of Samba prevents the proper update of
@@ -3840,26 +3839,24 @@ execute the setdriver command successfully, check if Samba "sees"
 the printer: 
 </para>
 
+<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
 <para><screen>
-
-# rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep  ir85wm
+&rootprompt;<userinput>rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep  ir85wm</userinput>
         printername:[ir85wm]
-
 </screen></para>
 
 <para>
 An alternative command could be this: 
 </para>
 
+<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
 <para><screen>
-
-# rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' 
+&rootprompt;<userinput>rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' </userinput>
         cmd = getprinter ir85wm
         flags:[0x800000]
         name:[\\transmeta\ir85wm]
         description:[\\transmeta\ir85wm,ir85wm,DPD]
         comment:[CUPS PostScript-Treiber for WinNT/2K/XP]
-
 </screen></para>
 
 <para>
@@ -3873,6 +3870,19 @@ to install drivers on remote Windows NT print servers too!
 <title>The printing <filename>*.tdb</filename> Files</title>
 
 <para>
+<indexterm><primary>TDB</primary></indexterm>
+<indexterm><primary>connections.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>printing.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>share_info.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>ntdrivers.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>unexpected.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>brlock.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>locking.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>ntforms.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>messages.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>ntprinters.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>sessionid.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>secrets.tdb</primary><seealso>TDB</seealso></indexterm>
 Some mystery is associated with the series of files with a
 tdb-suffix appearing in every Samba installation. They are
 <filename>connections.tdb</filename>,
@@ -3892,12 +3902,13 @@ tdb-suffix appearing in every Samba installation. They are
 <sect2>
 <title>Trivial DataBase Files</title>
 
+<indexterm><primary>TDB</primary></indexterm>
 <para>
 A Windows NT (Print) Server keeps track of all information needed to serve
 its duty toward its clients by storing entries in the Windows
 "Registry". Client queries are answered by reading from the registry,
 Administrator or user configuration settings are saved by writing into
-the Registry. Samba and Unix obviously don't have such a kind of
+the Registry. Samba and UNIX obviously don't have such a kind of
 Registry. Samba instead keeps track of all client related information in a
 series of <filename>*.tdb</filename> files. (TDB = Trivial Data
 Base). These are often located in <filename>/var/lib/samba/</filename>
@@ -3946,6 +3957,9 @@ backup of the <filename>*.tdb</filename> files in time.
 <sect2>
 <title>Using <emphasis>tdbbackup</emphasis></title>
 
+<indexterm><primary>TDB</primary><secondary>backing up</secondary><see>tdbbackup</see></indexterm>
+<indexterm><primary>tdbbackup</primary></indexterm>
+
 <para>
 Samba ships with a little utility which helps the root user of your
 system to back up your <filename>*.tdb</filename> files. If you run it
@@ -3953,8 +3967,7 @@ with no argument, it prints a little usage message:
 </para>
 
 <para><screen>
-
-# tdbbackup
+&rootprompt;<userinput>tdbbackup</userinput>
  Usage: tdbbackup [options] &lt;fname...&gt;
  
  Version:3.0a
@@ -3969,16 +3982,16 @@ Here is how I backed up my printing.tdb file:
 </para>
 
 <para><screen>
-
-# ls 
- .           browse.dat       locking.tdb     ntdrivers.tdb   printing.tdb    share_info.tdb
- ..          connections.tdb  messages.tdb    ntforms.tdb     printing.tdbkp  unexpected.tdb
- brlock.tdb  gmon.out         namelist.debug  ntprinters.tdb  sessionid.tdb
+&rootprompt;<userinput>ls</userinput>
+.              browse.dat       locking.tdb     ntdrivers.tdb   printing.tdb
+..             share_info.tdb   connections.tdb messages.tdb    ntforms.tdb
+printing.tdbkp unexpected.tdb   brlock.tdb      gmon.out        namelist.debug  
+ntprinters.tdb sessionid.tdb
  
- kde-bitshop:/var/lock/samba # tdbbackup -s .bak printing.tdb
+&rootprompt;<userinput>tdbbackup -s .bak printing.tdb</userinput>
  printing.tdb : 135 records
  
- kde-bitshop:/var/lock/samba # ls -l printing.tdb*
+&rootprompt;<userinput>ls -l printing.tdb*</userinput>
  -rw-------    1 root     root        40960 May  2 03:44 printing.tdb
  -rw-------    1 root     root        40960 May  2 03:44 printing.tdb.bak
 
@@ -3989,23 +4002,25 @@ Here is how I backed up my printing.tdb file:
 <sect1>
 <title>CUPS Print Drivers from Linuxprinting.org</title>
 
+<indexterm><primary>Linuxprinting.org</primary></indexterm>
+
 <para>
 CUPS ships with good support for HP LaserJet type printers.  You can
 install the generic driver as follows:
 </para>
 
-<para><screen>
-
-lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
+<indexterm><primary>lpadmin</primary></indexterm>
 
+<para><screen>
+&rootprompt;<userinput>lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd</userinput>
 </screen></para>
 
 <para>
-The <parameter>-m</parameter> switch will retrieve the
+The <option>-m</option> switch will retrieve the
 <filename>laserjet.ppd</filename> from the standard repository for
 not-yet-installed-PPDs, which CUPS typically stores in
 <filename>/usr/share/cups/model</filename>. Alternatively, you may use
-<parameter>-P /path/to/your.ppd</parameter>.
+<option>-P /path/to/your.ppd</option>.
 </para>
 
 <para>
@@ -4014,7 +4029,7 @@ for every LaserJet-compatible model. It constitutes a sort of "least
 denominator" of all the models. If for some reason it is ruled out to
 you to pay for the commercially available ESP Print Pro drivers, your
 first move should be to consult the database on <ulink
-url="http://www.linuxprinting.org/printer_list.cgi">http://www.linuxprinting.org/printer_list.cgi</ulink>.
+noescape="1" url="http://www.linuxprinting.org/printer_list.cgi">http://www.linuxprinting.org/printer_list.cgi</ulink>.
 Linuxprinting.org has excellent recommendations about which driver is
 best used for each printer. Its database is kept current by the
 tireless work of Till Kamppeter from MandrakeSoft, who is also the
@@ -4022,11 +4037,12 @@ principal author of the foomatic-rip utility.
 </para>
 
 <note><para>
+<indexterm><primary>foomatic-rip</primary></indexterm>
 The former "cupsomatic" concept is now be replaced by the new, much
 more powerful "foomatic-rip". foomatic-rip is the successor of
 cupsomatic. cupsomatic is no longer maintained. Here is the new URL
 to the Foomatic-3.0 database:<ulink
-url="http://www.linuxprinting.org/driver_list.cgi">http://www.linuxprinting.org/driver_list.cgi</ulink>.
+noescape="1" url="http://www.linuxprinting.org/driver_list.cgi">http://www.linuxprinting.org/driver_list.cgi</ulink>.
 If you upgrade to foomatic-rip, don't forget to also upgrade to the
 new-style PPDs for your foomatic-driven printers. foomatic-rip will
 not work with PPDs generated for the old cupsomatic. The new-style
@@ -4038,6 +4054,9 @@ provide the driver files for the Windows clients also!
 <sect2>
 <title>foomatic-rip and Foomatic explained</title>
 
+<indexterm significance="preferred"><primary>foomatic</primary></indexterm>
+<indexterm significance="preferred"><primary>foomatic-rip</primary></indexterm>
+
 <para>
 Nowadays most Linux distros rely on the utilities of Linuxprinting.org
 to create their printing related software (which, BTW, works on all
@@ -4104,6 +4123,8 @@ of the data.
 <sect3>
 <title>Foomatic's strange Name</title>
 
+<indexterm><primary>foomatic</primary></indexterm>
+
 <para>
 "Why the funny name?", you ask. When it really took off, around spring
 2000, CUPS was far less popular than today, and most systems used LPD,
@@ -4143,6 +4164,10 @@ Ghostscript filters.</para></listitem>
 <sect3>
 <title>cupsomatic, pdqomatic, lpdomatic, directomatic</title>
 
+<indexterm><primary>cupsomatic</primary></indexterm>
+<indexterm><primary>CUPS-PPD</primary></indexterm>
+<indexterm><primary>PPD</primary><secondary>CUPS</secondary><see>CUPS-PPD</see></indexterm>
+
 <para>
 CUPS worked through a quickly-hacked up filter script named <ulink
 url="http://www.linuxprinting.org/download.cgi?filename=cupsomatic&amp;show=0">cupsomatic</ulink>.
@@ -4191,9 +4216,11 @@ configuration files..
 </sect3>
 
 <sect3>
-<title>7.13.1.5.The <emphasis>Grand Unification</emphasis>
+<title>The <emphasis>Grand Unification</emphasis>
 achieved...</title>
 
+<indexterm><primary>foomatic-rip</primary></indexterm>
+
 <para>
 This all has changed in Foomatic versions 2.9 (Beta) and released as
 "stable" 3.0. This has now achieved the convergence of all *omatic
@@ -4261,7 +4288,7 @@ the work is currently done in three projects. These are:
 url="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/">Omni</ulink>
 -- a Free Software project by IBM which tries to convert their printer
 driver knowledge from good-ol' OS/2 times into a modern, modular,
-universal driver architecture for Linux/Unix (still Beta).  This
+universal driver architecture for Linux/UNIX (still Beta).  This
 currently supports 437 models.</para></listitem>
 
 <listitem><para><ulink url="http://hpinkjet.sf.net/">HPIJS</ulink> --
@@ -4282,7 +4309,7 @@ platforms). This currently supports 522 models.</para></listitem>
 
 <sect3>
 <title>Forums, Downloads, Tutorials, Howtos -- also for Mac OS X and
-commercial Unix</title>
+commercial UNIX</title>
 
 <para>
 Linuxprinting.org today is the one-stop "shop" to download printer
@@ -4361,11 +4388,11 @@ Linuxprinting.org ensures you to get the latest driver/PPD files):
 </para>
 <itemizedlist>
 <listitem><para>Surf to <ulink
-url="http://www.linuxprinting.org/printer_list.cgi">http://www.linuxprinting.org/printer_list.cgi</ulink>
+noescape="1" url="http://www.linuxprinting.org/printer_list.cgi">http://www.linuxprinting.org/printer_list.cgi</ulink>
 </para></listitem>
 
 <listitem><para>Check the complete list of printers in the database:
-<ulink
+<ulink noescape="1" 
 url="http://www.linuxprinting.org/printer_list.cgi?make=Anyone">http://www.linuxprinting.org/printer_list.cgi?make=Anyone</ulink>
 </para></listitem>
 
@@ -4378,7 +4405,7 @@ with this model (for all printers, there will always be
 first).</para></listitem>
 
 <listitem><para>In our case ("HP LaserJet 4 Plus"), we'll arrive here:
-<ulink
+		<ulink noescape="1"
 url="http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus">http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus</ulink>
 </para></listitem>
 
@@ -4389,7 +4416,7 @@ visit them all, if you are not familiar with the Linuxprinting.org
 database.</para></listitem>
 
 <listitem><para>There is a link to the database page for the "ljet4":
-<ulink
+		<ulink noescape="1"
 url="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4">http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</ulink>
 On the driver's page, you'll find important and detailed information
 about how to use that driver within the various available
@@ -4399,23 +4426,23 @@ spoolers.</para></listitem>
 driver author or the driver.</para></listitem>
 
 <listitem><para>Important links are the ones which provide hints with
-setup instructions for CUPS (<ulink
+setup instructions for CUPS (<ulink noescape="1"
 url="http://www.linuxprinting.org/cups-doc.html">http://www.linuxprinting.org/cups-doc.html</ulink>),
-PDQ (<ulink
+PDQ (<ulink noescape="1"
 url="http://www.linuxprinting.org/pdq-doc.html">http://www.linuxprinting.org/pdq-doc.html</ulink>),
-LPD, LPRng and GNUlpr (<ulink
+LPD, LPRng and GNUlpr (<ulink noescape="1"
 url="http://www.linuxprinting.org/lpd-doc.html">http://www.linuxprinting.org/lpd-doc.html</ulink>)
-as well as PPR (<ulink
+as well as PPR (<ulink noescape="1"
 url="http://www.linuxprinting.org/ppr-doc.html">http://www.linuxprinting.org/ppr-doc.html)</ulink>
-or "spooler-less" printing (<ulink
+or "spooler-less" printing (<ulink noescape="1"
 url="http://www.linuxprinting.org/direct-doc.html">http://www.linuxprinting.org/direct-doc.html</ulink>
 ).</para></listitem>
 
 <listitem><para>You can view the PPD in your browser through this
-link: <ulink
+link: <ulink noescape="1"
 url="http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&amp;printer=HP-LaserJet_4_Plus&amp;show=1">http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&amp;printer=HP-LaserJet_4_Plus&amp;show=1</ulink>
 </para></listitem> <listitem><para>You can also (most importantly)
-generate and download the PPD: <ulink
+generate and download the PPD: <ulink noescape="1"
 url="http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&amp;printer=HP-LaserJet_4_Plus&amp;show=0">http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&amp;printer=HP-LaserJet_4_Plus&amp;show=0</ulink>
 </para></listitem>
 
@@ -4425,7 +4452,7 @@ for the user. Later you'll only need to choose resolution, paper size
 etc. from the web-based menu, or from the print dialog GUI, or from
 the commandline.</para></listitem>
 
-<listitem><para>Should you have ended up on the driver's page (<ulink
+<listitem><para>Should you have ended up on the driver's page (<ulink noescape="1"
 url="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4">http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</ulink>),
 you can choose to use the "PPD-O-Matic" online PPD generator
 program.</para></listitem>
@@ -4461,19 +4488,17 @@ e.g.:
 </para>
 
 <para><screen>
-
-lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd
-
+&rootprompt;<userinput>lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd</userinput>
 </screen></para></listitem>
 
 <listitem><para>Note again this: for all the new-style "Foomatic-PPDs"
 from Linuxprinting.org, you also need a special "CUPS filter" named
-"foomatic-rip".Get the latest version of "foomatic-rip" from: <ulink
+"foomatic-rip".Get the latest version of "foomatic-rip" from: <ulink noescape="1"
 url="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&amp;show=0">http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&amp;show=0</ulink>
 </para></listitem>
 
 <listitem><para>The foomatic-rip Perlscript itself also makes some
-interesting reading (<ulink
+interesting reading (<ulink noescape="1"
 url="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&amp;show=1">http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&amp;show=1</ulink>),
 because it is very well documented by Till's inline comments (even
 non-Perl hackers will learn quite a bit about printing by reading
@@ -4538,6 +4563,8 @@ foomatic-rip).</para></listitem>
 <sect1>
 <title>Page Accounting with CUPS</title>
 
+
+<indexterm><primary>CUPS</primary><secondary>Page Accounting</secondary></indexterm>
 <para>
 Often there are questions regarding "print quotas" wherein Samba users
 (that is, Windows clients) should not be able to print beyond a
@@ -4558,15 +4585,17 @@ period you want.
 <sect2>
 <title>Setting up Quotas</title>
 
+<indexterm><primary>CUPS</primary><secondary>quotas</secondary></indexterm>
 <para>
 This is an example command how root would set a print quota in CUPS,
 assuming an existing printer named "quotaprinter":
 </para>
 
-<para><screen>
-
-  lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 -o job-page-limit=100
+<indexterm><primary>lpadmin</primary></indexterm>
 
+<para><screen>
+&rootprompt;<userinput>lpadmin -p quotaprinter -o job-quota-period=604800 \
+	-o job-k-limit=1024 -o job-page-limit=100</userinput>
 </screen></para>
 
 <para>
@@ -4596,7 +4625,7 @@ printer is a non-PostScript model, you need to let CUPS do the job to
 convert the file to a print-ready format for the target printer. This
 will be working for currently about 1,000 different printer models,
 see <ulink
-url="http://www.linuxprinting.org/printer_list.cgi">http://www.linuxprinting.org/printer_list.cgi</ulink>).
+	url="http://www.linuxprinting.org/printer_list.cgi">the driver list at linuxprinting.org/</ulink>.
 </para>
 </sect2>
 
@@ -4621,6 +4650,7 @@ http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). It does
 </para>
 
 <itemizedlist>
+<indexterm><primary>PJL</primary></indexterm>
 
 <listitem><para>to not write an PJL-header</para></listitem>
 
@@ -4644,6 +4674,7 @@ current from CUPS 1.1.16).
 <sect2>
 <title>The page_log File Syntax</title>
 
+<indexterm><primary>page_log</primary></indexterm>
 <para>
 These are the items CUPS logs in the "page_log" for every
 single <emphasis>page</emphasis> of a job:
@@ -4675,13 +4706,11 @@ format and included items:
 </para>
 
 <para><screen>
-
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 1 3 #marketing 10.160.50.13
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 2 3 #marketing 10.160.50.13
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 3 3 #marketing 10.160.50.13
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 4 3 #marketing 10.160.50.13
-        DigiMaster9110 boss 402 [22/Apr/2003:10:33:22 +0100] 1 440 finance-dep 10.160.51.33
-
+infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 1 3 #marketing 10.160.50.13
+infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 2 3 #marketing 10.160.50.13
+infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 3 3 #marketing 10.160.50.13
+infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 4 3 #marketing 10.160.50.13
+DigiMaster9110 boss 402 [22/Apr/2003:10:33:22 +0100] 1 440 finance-dep 10.160.51.33
 </screen></para>
 
 <para>
@@ -4712,7 +4741,7 @@ of 1000 and the job is aborted by the printer, the "page count" will
 still show the figure of 1000 for that job</para></listitem>
 
 <listitem><para>all quotas are the same for all users (no flexibility
-to give the boss a higher quota than the clerk) no support for
+to give the boss a higher quota than the clerk), no support for
 groups</para></listitem>
 
 <listitem><para>no means to read out the current balance or the
@@ -4788,11 +4817,9 @@ away and re-directs it to go through Ghostscript. CUPS accepts this,
 because the associated CUPS-O-Matic-/Foomatic-PPD specifies:
 </para>
 
-<para><screen>
-
-   *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
-
-</screen></para>
+<para><programlisting>
+  *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
+</programlisting></para>
 
 <para>
 This line persuades CUPS to hand the file to cupsomatic, once it has
@@ -4809,12 +4836,10 @@ mechanism. Another workaround in some situations would be to have in
 <filename>/etc/cups/mime.types</filename> entries as follows:
 </para>
 
-<para><screen>
-
-   application/postscript           application/vnd.cups-raw  0  -
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  -
-
-</screen></para>
+<para><programlisting>
+ application/postscript           application/vnd.cups-raw  0  -
+ application/vnd.cups-postscript  application/vnd.cups-raw  0  -
+</programlisting></para>
 
 <para>
 This would prevent all Postscript files from being filtered (rather,
@@ -4824,11 +4849,9 @@ want to print PS code on non-PS printers (provided they support ASCII
 text printing) an entry as follows could be useful:
 </para>
 
-<para><screen>
-
-   */*           application/vnd.cups-raw  0  -
-
-</screen></para>
+<para><programlisting>
+ */*           application/vnd.cups-raw  0  -
+</programlisting></para>
 
 <para>
 and would effectively send <emphasis>all</emphasis> files to the
@@ -4839,11 +4862,9 @@ backend without further processing.
 Lastly, you could have the following entry:
 </para>
 
-<para><screen>
-
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter
-
-</screen></para>
+<para><programlisting>
+application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter
+</programlisting></para>
 
 <para>
 You will need to write a <emphasis>my_PJL_stripping_filter</emphasis>
@@ -4873,10 +4894,9 @@ requested by marketing for the mailing, etc.).
 
 <para>
 Samba print files pass through two "spool" directories. One is the
-incoming directory managed by Samba, (set in the <emphasis>path =
-/var/spool/samba</emphasis> directive in the
-<emphasis>[printers]</emphasis> section of
-<filename>smb.conf</filename>). The other is the spool directory of
+incoming directory managed by Samba, (set in the <smbconfoption><name>path</name><value>/var/spool/samba</value></smbconfoption> directive in the
+<smbconfsection>[printers]</smbconfsection> section of
+&smb.conf;). The other is the spool directory of
 your UNIX print subsystem. For CUPS it is normally
 <filename>/var/spool/cups/</filename>, as set by the cupsd.conf
 directive <filename>RequestRoot /var/spool/cups</filename>.
@@ -4938,17 +4958,20 @@ things:
 <listitem><para>a Samba-smbd which is compiled against "libcups" (Check
 on Linux by running "ldd `which smbd`")</para></listitem>
 
-<listitem><para>a Samba-<filename>smb.conf</filename> setting of
-"printing = cups"</para></listitem>
+<listitem><para>a Samba-&smb.conf; setting of
+		<smbconfoption><name>printing</name><value>cups</value></smbconfoption></para></listitem>
 
-<listitem><para>another Samba-<filename>smb.conf</filename> setting of
-"printcap = cups"</para></listitem>
+<listitem><para>another Samba-&smb.conf; setting of
+		<smbconfoption><name>printcap</name><value>cups</value></smbconfoption></para></listitem>
 </itemizedlist>
 
 <note><para>
 In this case all other manually set printing-related commands (like
-"print command", "lpq command", "lprm command", "lppause command" or
-"lpresume command") are ignored and they should normally have no
+<smbconfoption><name>print command</name></smbconfoption>, 
+<smbconfoption><name>lpq command</name></smbconfoption>, 
+<smbconfoption><name>lprm command</name></smbconfoption>, 
+<smbconfoption><name>lppause command</name></smbconfoption> or
+<smbconfoption><name>lpresume command</name></smbconfoption>) are ignored and they should normally have no
 influence what-so-ever on your printing.
 </para></note>
 </sect2>
@@ -4957,24 +4980,15 @@ influence what-so-ever on your printing.
 <title>Manual Configuration</title>
 
 <para>
-If you want to do things manually, replace the "printing =
-cups" by "printing = bsd". Then your manually set commands may work
-(haven't tested this), and a "print command = lp -d %P %s; rm %s"
+If you want to do things manually, replace the <smbconfoption><name>printing</name><value>cups</value></smbconfoption>
+by <smbconfoption><name>printing</name><value>bsd</value></smbconfoption>. Then your manually set commands may work
+(haven't tested this), and a <smbconfoption><name>print command</name><value>lp -d %P %s; rm %s"</value></smbconfoption>
 may do what you need.
 </para>
 </sect2>
 </sect1>
 
 <sect1>
-<title>When <emphasis>not</emphasis> to use Samba to print to
-CUPS</title>
-
-<para>
-[TO BE DONE]
-</para>
-</sect1>
-
-<sect1>
 <title>In Case of Trouble.....</title>
 
 <para>
@@ -4984,10 +4998,8 @@ relevant to your problem):
 </para>
 
 <para><screen>
-
-   grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
-   grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"
-
+&prompt;<userinput>grep -v ^# /etc/cups/cupsd.conf | grep -v ^$</userinput>
+&prompt;<userinput>grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"</userinput>
 </screen></para>
 
 <para>
@@ -4999,35 +5011,9 @@ for experts (and you are expecting experts to read them, right?
 ;-)
 </para>
 
-<sect2>
-<title>Where to find Documentation</title>
-
-<para>
-[TO BE DONE]
-</para>
-</sect2>
-
-<sect2>
-<title>How to ask for Help</title>
-
-<para>
-[TO BE DONE]
-</para>
-</sect2>
-
-<sect2>
-<title>Where to find Help</title>
-
-<para>
-[TO BE DONE]
-</para>
-</sect2>
 </sect1>
 
 <sect1>
-<title>Appendix</title>
-
-<sect2>
 <title>Printing <emphasis>from</emphasis> CUPS to Windows attached
 Printers</title>
 
@@ -5035,7 +5021,7 @@ Printers</title>
 From time to time the question arises, how you can print
 <emphasis>to</emphasis> a Windows attached printer
 <emphasis>from</emphasis> Samba. Normally the local connection
-"Windows host &lt;--&gt; printer" would be done by USB or parallel
+from Windows host to printer would be done by USB or parallel
 cable, but this doesn't matter to Samba. From here only an SMB
 connection needs to be opened to the Windows host. Of course, this
 printer must be "shared" first. As you have learned by now, CUPS uses
@@ -5049,27 +5035,25 @@ which file must exist and be executable:
 </para>
 
 <para><screen>
-
- # ls -l /usr/lib/cups/backend/   
- total 253
- drwxr-xr-x    3 root     root          720 Apr 30 19:04 .
- drwxr-xr-x    6 root     root          125 Dec 19 17:13 ..
- -rwxr-xr-x    1 root     root        10692 Feb 16 21:29 canon
- -rwxr-xr-x    1 root     root        10692 Feb 16 21:29 epson
- lrwxrwxrwx    1 root     root            3 Apr 17 22:50 http -&gt; ipp
- -rwxr-xr-x    1 root     root        17316 Apr 17 22:50 ipp
- -rwxr-xr-x    1 root     root        15420 Apr 20 17:01 lpd
- -rwxr-xr-x    1 root     root         8656 Apr 20 17:01 parallel
- -rwxr-xr-x    1 root     root         2162 Mar 31 23:15 pdfdistiller
- lrwxrwxrwx    1 root     root           25 Apr 30 19:04 ptal -&gt; /usr/local/sbin/ptal-cups
- -rwxr-xr-x    1 root     root         6284 Apr 20 17:01 scsi
- lrwxrwxrwx    1 root     root           17 Apr  2 03:11 smb -&gt; /usr/bin/smbspool
- -rwxr-xr-x    1 root     root         7912 Apr 20 17:01 socket
- -rwxr-xr-x    1 root     root         9012 Apr 20 17:01 usb
-
-# ls -l `which smbspool`
- -rwxr-xr-x    1 root     root       563245 Dec 28 14:49 /usr/bin/smbspool
-
+&rootprompt;<userinput>ls -l /usr/lib/cups/backend/</userinput>
+total 253
+drwxr-xr-x    3 root     root          720 Apr 30 19:04 .
+drwxr-xr-x    6 root     root          125 Dec 19 17:13 ..
+-rwxr-xr-x    1 root     root        10692 Feb 16 21:29 canon
+-rwxr-xr-x    1 root     root        10692 Feb 16 21:29 epson
+lrwxrwxrwx    1 root     root            3 Apr 17 22:50 http -&gt; ipp
+-rwxr-xr-x    1 root     root        17316 Apr 17 22:50 ipp
+-rwxr-xr-x    1 root     root        15420 Apr 20 17:01 lpd
+-rwxr-xr-x    1 root     root         8656 Apr 20 17:01 parallel
+-rwxr-xr-x    1 root     root         2162 Mar 31 23:15 pdfdistiller
+lrwxrwxrwx    1 root     root           25 Apr 30 19:04 ptal -&gt; /usr/sbin/ptal-cups
+-rwxr-xr-x    1 root     root         6284 Apr 20 17:01 scsi
+lrwxrwxrwx    1 root     root           17 Apr  2 03:11 smb -&gt; /usr/bin/smbspool
+-rwxr-xr-x    1 root     root         7912 Apr 20 17:01 socket
+-rwxr-xr-x    1 root     root         9012 Apr 20 17:01 usb
+
+&rootprompt;<userinput>ls -l `which smbspool`</userinput>
+-rwxr-xr-x    1 root     root       563245 Dec 28 14:49 /usr/bin/smbspool
 </screen></para>
 
 <para>
@@ -5077,9 +5061,7 @@ If this symlink doesn't exist, create it:
 </para>
 
 <para><screen>
-
-# ln -s `which smbspool` /usr/lib/cups/backend/smb
-
+&rootprompt;<userinput>ln -s `which smbspool` /usr/lib/cups/backend/smb</userinput>
 </screen></para>
 
 <para>
@@ -5102,9 +5084,8 @@ To install a printer with the smb backend on CUPS, use this command:
 </para>
 
 <para><screen>
-
-# lpadmin -p winprinter -v smb://WINDOWSNETBIOSNAME/printersharename -P /path/to/PPD
-
+&rootprompt;<userinput>lpadmin -p winprinter -v smb://WINDOWSNETBIOSNAME/printersharename \
+  -P /path/to/PPD</userinput>
 </screen></para>
 
 <para>
@@ -5117,13 +5098,11 @@ for: you can include the required parameters as part of the
 <filename>smb://</filename> device-URI. Like this:
 </para>
 
-<para><screen>
-
- smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename 
- smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename
- smb://username:password@WINDOWSNETBIOSNAME/printersharename
-
-</screen></para>
+<itemizedlist>
+	<listitem><para>smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename </para></listitem>
+	<listitem><para>smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename</para></listitem>
+	<listitem><para>smb://username:password@WINDOWSNETBIOSNAME/printersharename</para></listitem>
+</itemizedlist>
 
 <para>
 Note that the device-URI will be visible in the process list of the
@@ -5137,121 +5116,26 @@ working netbios name resolution up and running. Note that this is a
 feature of CUPS and you don't necessarily need to have smbd running
 (but who wants that? :-).
 </para>
-</sect2>
+</sect1>
 
-<sect2>
+<sect1>
 <title>More CUPS filtering Chains</title>
 
 <para>
 The following diagrams reveal how CUPS handles print jobs.
 </para>
 
-<screen>
-#########################################################################
-#
-# CUPS in and of itself has this (general) filter chain (CAPITAL
-# letters are FILE-FORMATS or MIME types, other are filters (this is
-# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#     somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#     pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      V
-#     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
-#      |           # installation on the system
-#      |  (= "postscipt interpreter")
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      V
-#     rastertosomething  (e.g. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      V
-#     backend
-#
-#
-# ESP PrintPro has some enhanced "rastertosomething" filters as compared to
-# CUPS, and also a somewhat improved "pstoraster" filter.
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-</screen>
+<image><imagefile>cups1</imagefile><imagedescription>Filtering chain 1</imagedescription></image>
 
-<screen>
-#########################################################################
-#
-# This is how "cupsomatic" comes into play:
-# =========================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#    somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#    pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          V
-#      V                                         cupsomatic
-#    pstoraster                                  (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
-#      |                                         call...)
-#      V                                          |
-#    rastertosomething                            V
-#      |    (= "raster driver")     +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      V                                          |
-#    backend &lt;------------------------------------+
-#      |
-#      V
-#    THE PRINTER
-#
-#
-# Note, that cupsomatic "kidnaps" the printfile after the
-# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it gh
-# the CUPS-external, systemwide Ghostscript installation, bypassing the
-# "pstoraster" filter (therefore also bypassing the CUPS-raster-drivers
-# "rastertosomething", and hands the rasterized file directly to the CUPS
-# backend...
-#
-# cupsomatic is not made by the CUPS developers. It is an independent
-# contribution to printing development, made by people from
-# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-</screen>
+<image><imagefile>cups2</imagefile><imagedescription>Filtering chain with cupsomatic</imagedescription></image>
+
+<note><para>
+Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+</para></note>
+
+<!--FIXME: Put this into diagrams... ?
 
-<screen>
 #########################################################################
 #
 # And this is how it works for ESP PrintPro from 4.3:
@@ -5311,7 +5195,7 @@ The following diagrams reveal how CUPS handles print jobs.
 #    pstops
 #      |
 #      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
+# APPLICATION/VND.CUPS-POSTSCRIPT ================+
 #      |                                          V
 #      V                                         cupsomatic
 #    gsrip                                       (constructs complicated
@@ -5322,13 +5206,13 @@ The following diagrams reveal how CUPS handles print jobs.
 #      |                                         call...)
 #      V                                          |
 #    rastertosomething                            V
-#      |   (= "raster driver")      +-------------------------+
+#      |   (= "raster driver")      +=========================+
 #      |                            | Ghostscript at work.... |
 #      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
+# SOMETHING-DEVICE-SPECIFIC         *=========================+
 #      |                                          |
 #      V                                          |
-#    backend &lt;------------------------------------+
+#    backend &lt;=================================+
 #      |
 #      V
 #    THE PRINTER
@@ -5357,8 +5241,8 @@ The following diagrams reveal how CUPS handles print jobs.
 #     pstops
 #      |
 #      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                  +------------------v------------------------------+
+# APPLICATION/VND.CUPS-POSTSCRIPT=====+
+#                  +==================v==============================+
 #                  | Ghostscript                                     |
 #                  | at work...                                      |
 #                  | (with                                           |
@@ -5366,9 +5250,9 @@ The following diagrams reveal how CUPS handles print jobs.
 #                  |                                                 |
 #                  |         (= "postscipt interpreter")             |
 #                  |                                                 |
-#                  +------------------v------------------------------+
+#                  +==================v==============================+
 #                                     |
-# APPLICATION/VND.CUPS-RASTER &gt;-------+
+# APPLICATION/VND.CUPS-RASTER &gt;====+
 #      |
 #      V
 #     rastertosomething
@@ -5416,8 +5300,8 @@ The following diagrams reveal how CUPS handles print jobs.
 #     pstops
 #      |
 #      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                  +------------------v------------------------------+
+# APPLICATION/VND.CUPS-POSTSCRIPT=====+
+#                  +==================v==============================+
 #                  | Ghostscript        . Ghostscript at work....    |
 #                  | at work...         . (with "-sDEVICE=           |
 #                  | (with              .            s.th."          |
@@ -5427,15 +5311,15 @@ The following diagrams reveal how CUPS handles print jobs.
 #                  |                    .                            |
 #                  |          (= "postscript interpreter")           |
 #                  |                    .                            |
-#                  +------------------v--------------v---------------+
+#                  +==================v==============v===============+
 #                                     |              |
-# APPLICATION/VND.CUPS-RASTER &gt;-------+              |
+# APPLICATION/VND.CUPS-RASTER &gt;=======+              |
 #      |                                             |
 #      V                                             |
 #     rastertosomething                              |
 #      |   (= "raster driver")                       |
 #      V                                             |
-# SOMETHING-DEVICE-SPECIFIC &gt;------------------------+
+# SOMETHING-DEVICE-SPECIFIC &gt;========================+
 #      |
 #      V
 #     backend
@@ -5445,76 +5329,72 @@ The following diagrams reveal how CUPS handles print jobs.
 #       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
 #
 ##########################################################################
-</screen>
-</sect2>
+</screen>-->
+</sect1>
 
-<sect2>
-<title>Trouble Shooting Guidelines to fix typical Samba printing
-Problems</title>
+<sect1>
+	<title>Common Errors</title>
 
-<para>
-This is a short description of how to debug printing problems
-with Samba. This describes how to debug problems with printing from
-a SMB client to a Samba server, not the other way around.
-</para>
+	<sect2>
+		<title>Win9x client can't install driver</title>
 
-<variablelist>
-<varlistentry><term>Win9x client can't install driver</term>
-<listitem><para>For Win9x clients require the printer names to be 8
+		<para>For Win9x clients require the printer names to be 8
 chars (or "8 plus 3 chars suffix") max; otherwise the driver files
 won't get transferred when you want to download them from
-Samba.</para></listitem></varlistentry>
-
-<varlistentry><term>testparm</term>
-<listitem><para>Run <command>testparm</command>: It will tell you if
-<filename>smb.conf</filename> parameters are in the wrong
-section. Many people have had the "printer admin" parameter in the
-<parameter>[printers]</parameter> section and experienced
-problems. "testparm" will tell you if it sees
-this.</para></listitem></varlistentry>
-
-<varlistentry><term>"cupsaddsmb" keeps asking for a root password in a
-neverending loop</term>
-<listitem><para>Have you <parameter>security = user</parameter>? Have
+Samba.</para>
+
+	</sect2>
+
+	<sect2>
+		<title>"cupsaddsmb" keeps asking for root password in
+			neverending loop</title>
+
+		<para>Have you <smbconfoption><name>security</name><value>user</value></smbconfoption>? Have
 you used <command>smbpasswd</command> to give root a Samba account?
 You can do 2 things: open another terminal and execute
 <command>smbpasswd -a root</command> to create the account, and
 continue with entering the password into the first terminal. Or break
 out of the loop by hitting ENTER twice (without trying to type a
-password).</para></listitem></varlistentry>
+password).</para>
 
-<varlistentry><term>"cupsaddsmb" gives "No PPD file for printer..."
-message (but I swear there is one!)</term>
+	</sect2>
 
-<listitem>
-<itemizedlist>
-<listitem><para>Have you enabled printer sharing on CUPS? This means:
+	<sect2>
+		<title>"cupsaddsmb" gives "No PPD file for printer..."
+			message while PPD file is present</title>
+
+		<para>Have you enabled printer sharing on CUPS? This means:
 do you have a <parameter>&lt;Location
 /printers&gt;....&lt;/Location&gt;</parameter> section in CUPS
 server's <filename>cupsd.conf</filename> which doesn't deny access to
 the host you run "cupsaddsmb" from?  It <emphasis>could</emphasis> be
 an issue if you use cupsaddsmb remotely, or if you use it with a
-<parameter>-h</parameter> parameter: <command>cupsaddsmb -H
-sambaserver -h cupsserver -v printername</command>.
-</para></listitem>
-<listitem><para>Is your
+<option>-h</option> parameter: <userinput>cupsaddsmb -H
+	sambaserver -h cupsserver -v printername</userinput>.
+</para>
+<para>Is your
 "TempDir" directive in
 <emphasis>cupsd.conf</emphasis>
 set to a valid value and is it writeable?
-</para></listitem></itemizedlist>
-</listitem></varlistentry>
+</para>
 
-<varlistentry><term>I can't connect client to Samba printer.</term>
-<listitem><para>Use <command>smbstatus</command> to check which user
+	</sect2>
+
+	<sect2>
+		<title>Client can't connect to Samba printer</title>
+	<para>Use <command>smbstatus</command> to check which user
 you are from Samba's point of view. Do you have the privileges to
-write into the <parameter>[print$]</parameter>
-share?</para></listitem></varlistentry>
-
-<varlistentry><term>I can't reconnect to Samba under a new account
-from Win2K/XP</term>
-<listitem><para>Once you are connected as the "wrong" user (for
-example as "nobody", which often occurs if you have <parameter>map to
-guest = bad user</parameter>), Windows Explorer will not accept an
+write into the <smbconfsection>[print$]</smbconfsection>
+share?</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Can't reconnect to Samba under new account
+			from Win2K/XP</title>
+	<para>Once you are connected as the "wrong" user (for
+example as "nobody", which often occurs if you have 
+<smbconfoption><name>map to guest</name><value>bad user</value></smbconfoption>), Windows Explorer will not accept an
 attempt to connect again as a different user. There won't be any byte
 transfered on the wire to Samba, but still you'll see a stupid error
 message which makes you think that Samba has denied access. Use
@@ -5527,89 +5407,90 @@ indicating a renewed connection attempt? Shut all Explorer Windows.
 This makes Windows forget what it has cached in its memory as
 established connections. Then re-connect as the right user. Best
 method is to use a DOS terminal window and <emphasis>first</emphasis>
-do <command>net use z: \\SAMBAHOST\print$ /user:root</command>. Check
+do <userinput>net use z: \\&example.server.samba;\print$ /user:root</userinput>. Check
 with <command>smbstatus</command> that you are connected under a
 different account. Now open the "Printers" folder (on the Samba server
 in the <emphasis>Network Neighbourhood</emphasis>), right-click the
 printer in question and select
-<emphasis>Connect...</emphasis></para></listitem></varlistentry>
+<emphasis>Connect...</emphasis></para></sect2>
 
-<varlistentry><term>Avoid being connected to the Samba server as the
-"wrong" user</term>
-<listitem><para>You see per <command>smbstatus</command> that you are
+<sect2>
+	<title>Avoid being connected to the Samba server as the
+		"wrong" user</title>
+	
+	<para>You see per <command>smbstatus</command> that you are
 connected as user "nobody"; while you wanted to be "root" or
-"printeradmin"? This is probably due to <parameter>map to guest = bad
-user</parameter>, which silently connects you under the guest account,
+"printeradmin"? This is probably due to 
+<smbconfoption><name>map to guest</name><value>bad user</value></smbconfoption>, which silently connects you under the guest account,
 when you gave (maybe by accident) an incorrect username. Remove
-<parameter>map to guest</parameter>, if you want to prevent
-this.</para></listitem></varlistentry>
+<smbconfoption><name>map to guest</name></smbconfoption>, if you want to prevent
+this.</para></sect2>
+
+<sect2><title>Upgrading to CUPS drivers from Adobe drivers on
+		NT/2K/XP clients gives problems</title>
 
-<varlistentry><term>Upgrading to CUPS drivers from Adobe drivers on
-NT/2K/XP clients gives problems</term>
-<listitem><para>First delete all "old" Adobe-using printers. Then
+	<para>First delete all "old" Adobe-using printers. Then
 delete all "old" Adobe drivers. (On Win2K/XP, right-click in
 background of "Printers" folder, select "Server Properties...", select
-tab "Drivers" and delete here).</para></listitem></varlistentry>
-
-<varlistentry><term>I can't use "cupsaddsmb"on a Samba server which is
-a PDC</term>
-<listitem><para>Do you use the "naked" root user name? Try to do it
-this way: <emphasis>cupsaddsmb -U DOMAINNAME\\root -v
-printername</emphasis> (note the two backslashes: the first one is
-required to "escape" the second one).</para></listitem></varlistentry>
-
-<varlistentry><term>I deleted a printer on Win2K; but I still see
-its driver</term>
-<listitem><para>Deleting a printer on the client won't delete the
+tab "Drivers" and delete here).</para></sect2>
+
+<sect2><title>Can't use "cupsaddsmb" on Samba server which is
+		a PDC</title>
+<para>Do you use the "naked" root user name? Try to do it
+this way: <userinput>cupsaddsmb -U <replaceable>DOMAINNAME</replaceable>\\root -v
+<replaceable>printername</replaceable></userinput>> (note the two backslashes: the first one is
+required to "escape" the second one).</para></sect2>
+
+<sect2><title>Deleted Win2K printer driver is still shown</title>
+<para>Deleting a printer on the client won't delete the
 driver too (to verify, right-click on the white background of the
 "Printers" folder, select "Server Properties" and click on the
 "Drivers" tab). These same old drivers will be re-used when you try to
 install a printer with the same name. If you want to update to a new
 driver, delete the old ones first. Deletion is only possible if no
-other printer uses the same driver.</para></listitem></varlistentry>
+other printer uses the same driver.</para></sect2>
 
-<varlistentry><term>Win2K/XP "Local Security
-Policies"</term>
-<listitem><para><emphasis>Local Security Policies</emphasis> may not
+<sect2><title>Win2K/XP "Local Security
+		Policies"</title>
+<para><emphasis>Local Security Policies</emphasis> may not
 allow the installation of unsigned drivers. "Local Security Policies"
 may not allow the installation of printer drivers at
-all.</para></listitem></varlistentry>
+all.</para></sect2>
 
-<varlistentry><term>WinXP clients: "Administrator can not install
-printers for all local users"</term>
-<listitem><para>Windows XP handles SMB printers on a "per-user" basis.
+<sect2><title>WinXP clients: "Administrator can not install
+		printers for all local users"</title>
+<para>Windows XP handles SMB printers on a "per-user" basis.
 This means every user needs to install the printer himself. To have a
 printer available for everybody, you might want to use the built-in
 IPP client capabilities of WinXP. Add a printer with the print path of
 <emphasis>http://cupsserver:631/printers/printername</emphasis>.
 Still looking into this one: maybe a "logon script" could
 automatically install printers for all
-users.</para></listitem></varlistentry>
+users.</para></sect2>
 
-<varlistentry><term>"Print Change Notify" functions on
-NT-clients</term>
-<listitem><para>For "print change notify" functions on NT++ clients,
+<sect2><title>"Print Change Notify" functions on
+		NT-clients</title>
+<para>For "print change notify" functions on NT++ clients,
 these need to run the "Server" service first (re-named to
 <emphasis>File &amp; Print Sharing for MS Networks</emphasis> in
-XP).</para></listitem></varlistentry>
+XP).</para></sect2>
 
-<varlistentry><term>WinXP-SP1</term>
-<listitem><para>WinXP-SP1 introduced a <emphasis>Point and Print
+<sect2><title>WinXP-SP1</title>
+<para>WinXP-SP1 introduced a <emphasis>Point and Print
 Restriction Policy</emphasis> (this restriction doesn't apply to
 "Administrator" or "Power User" groups of users).  In Group Policy
-Object Editor: go to <emphasis>User Configuration --&gt;
-Administrative Templates --&gt; Control Panel --&gt;
+Object Editor: go to <emphasis>User Configuration,
+	Administrative Templates, Control Panel,
 Printers</emphasis>. The policy is automatically set to
 <emphasis>Enabled</emphasis> and the <emphasis>Users can only Point
 and Print to machines in their Forest</emphasis> . You probably need
 to change it to <emphasis>Disabled</emphasis> or <emphasis>Users can
 only Point and Print to these servers</emphasis> in order to make
-driver downloads from Samba possible.</para></listitem></varlistentry>
+driver downloads from Samba possible.</para></sect2>
 
-<varlistentry><term>I can't set and save default print options for all
-users on Win2K/XP</term>
+<sect2><title>Print options for all	users can't be set on Win2K/XP</title>
 
-<listitem><para>How are you doing it? I bet the wrong way (it is not
+<para>How are you doing it? I bet the wrong way (it is not
 very easy to find out, though). There are 3 different ways to bring
 you to a dialog that <emphasis>seems</emphasis> to set everything. All
 three dialogs <emphasis>look</emphasis> the same. Only one of them
@@ -5687,16 +5568,16 @@ Do you see any difference? I don't either... However, only the last
 one, which you arrived at with steps "C.1.-6." will save any settings
 permanently and be the defaults for new users. If you want all clients
 to get the same defaults, you need to conduct these steps <emphasis>as
-Administrator</emphasis> (<parameter>printer admin</parameter> in
-<filename>smb.conf</filename>) <emphasis>before</emphasis> a client
+Administrator</emphasis> (<smbconfoption><name>printer admin</name></smbconfoption> in
+&smb.conf;) <emphasis>before</emphasis> a client
 downloads the driver (the clients can later set their own
 <emphasis>per-user defaults</emphasis> by following the
 procedures <emphasis>A.</emphasis> or <emphasis>B.</emphasis>
-above).</para></listitem></varlistentry>
+above).</para></sect2>
 
-<varlistentry><term>What are the most common blunders in driver
-settings on Windows clients?</term>
-<listitem><para>Don't use <emphasis>Optimize for
+<sect2><title>Most common blunders in driver
+		settings on Windows clients</title>
+	<para>Don't use <emphasis>Optimize for
 Speed</emphasis>: use <emphasis>Optimize for
 Portability</emphasis> instead (Adobe PS Driver) Don't use
 <emphasis>Page Independence: No</emphasis>: always
@@ -5708,11 +5589,11 @@ printer</emphasis> (Adobe PS Driver). For
 <emphasis>TrueType Download Options</emphasis>
 choose <emphasis>Outline</emphasis>. Use PostScript
 Level 2, if you are having trouble with a non-PS printer, and if
-there is a choice.</para></listitem></varlistentry>
+there is a choice.</para></sect2>
 
-<varlistentry><term>I can't make <command>cupsaddsmb</command> work
-with newly installed printer</term>
-<listitem><para>Symptom: the last command of
+<sect2><title><command>cupsaddsmb</command> does not work
+		with newly installed printer</title>
+<para>Symptom: the last command of
 <command>cupsaddsmb</command> doesn't complete successfully:
 <command>cmd = setdriver printername printername</command> result was
 NT_STATUS_UNSUCCESSFUL then possibly the printer was not yet
@@ -5721,29 +5602,29 @@ Neighbourhood</emphasis>? Did it show up in <command>rpcclient
 hostname -c 'enumprinters'</command>? Restart smbd (or send a
 <command>kill -HUP</command> to all processes listed by
 <command>smbstatus</command> and try
-again.</para></listitem></varlistentry>
+again.</para></sect2>
 
-<varlistentry><term>My permissions on
+<sect2><title>Permissions on
 <filename>/var/spool/samba/</filename> get reset after each
-reboot</term>
-<listitem><para>Have you by accident set the CUPS spool directory to
+reboot</title>
+<para>Have you by accident set the CUPS spool directory to
 the same location? (<parameter>RequestRoot
 /var/spool/samba/</parameter> in <filename>cupsd.conf</filename> or
 the other way round: <filename>/var/spool/cups/</filename> is set as
-<parameter>path</parameter> in the <parameter>[printers]</parameter>
+<smbconfoption><name>path</name></smbconfoption>> in the <smbconfsection>[printers]</smbconfsection>
 section). These <emphasis>must</emphasis> be different. Set
 <parameter>RequestRoot /var/spool/cups/</parameter> in
-<filename>cupsd.conf</filename> and <parameter>path =
-/var/spool/samba</parameter> in the <parameter>[printers]</parameter>
-section of <filename>smb.conf</filename>. Otherwise cupsd will
+<filename>cupsd.conf</filename> and <smbconfoption><name>path</name><value>
+/var/spool/samba</value></smbconfoption> in the <smbconfsection>[printers]</smbconfsection>
+section of &smb.conf;. Otherwise cupsd will
 sanitize permissions to its spool directory with each restart, and
-printing will not work reliably.</para></listitem></varlistentry>
+printing will not work reliably.</para></sect2>
 
-<varlistentry><term>My printers work fine: just the printer named "lp"
+<sect2><title>Printer named "lp"
 intermittently swallows jobs and spits out completely different
-ones</term>
-<listitem><para>It is a very bad idea to name any printer "lp". This
-is the traditional Unix name for the default printer. CUPS may be set
+ones</title>
+<para>It is a very bad idea to name any printer "lp". This
+is the traditional UNIX name for the default printer. CUPS may be set
 up to do an automatic creation of "Implicit Classes". This means, to
 group all printers with the same name to a pool of devices, and
 loadbalancing the jobs across them in a round-robin fashion.  Chances
@@ -5752,56 +5633,25 @@ receive his jobs and send your own to his device unwittingly. To have
 tight control over the printer names, set <parameter>BrowseShortNames
 No</parameter>. It will present any printer as "printername@cupshost"
 then, giving you a better control over what may happen in a large
-networked environment.</para></listitem></varlistentry>
-
-<varlistentry><term>How do I "watch" my Samba server?</term>
-<listitem><para>You can use <command>tail -f
-/var/log/samba/log.smbd</command> (you may need a different path) to
-see a live scrolling of all log messages.  <command>smbcontrol smbd
-debuglevel</command> tells you which verbosity goes into the
-logs. <command>smbcontrol smbd debug 3</command> sets the verbosity to
-a quite high level (you can choose from 0 to 10 or 100). This works
-"on the fly", without the need to restart the smbd daemon. Don't use
-more than 3 initially; or you'll drown in an ocean of
-messages.</para></listitem></varlistentry>
-
-<varlistentry><term>I can't use Samba from my WinXP Home box, while
-access from WinXP Prof works flawlessly</term>
-<listitem><para>You have our condolences! WinXP home has been
-completely neutered by Microsoft as compared to WinXP Prof: you can
-not log into a WinNT domain. It cannot join a Win NT domain as a
-member server. While it is possible to access domain resources, users
-don't have "single sign-on". They need to supply username and password
-each time they connect to a resource. Logon scripts and roaming
-profiles are not supported. It can serve file and print shares; but
-only in "share-mode security" level. It can not use "user-mode
-security" (what Windows 95/98/ME still can
-do).</para></listitem></varlistentry>
-
-<varlistentry><term>Where do I find the Adobe PostScript driver files
-I need for "cupsaddsmb"?</term>
-<listitem><para>Use <command>smbclient</command> to connect to any
+networked environment.</para></sect2>
+
+<sect2><title>Location of Adobe PostScript driver files necessary for "cupsaddsmb"</title>
+<para>Use <command>smbclient</command> to connect to any
 Windows box with a shared PostScript printer: <command>smbclient
 //windowsbox/print\$ -U guest</command>. You can navigate to the
 <filename>W32X86/2</filename> subdir to <command>mget ADOBE*</command>
 and other files or to <filename>WIN40/0</filename> to do the same. --
 Another option is to download the <filename>*.exe</filename> packaged
-files from the Adobe website.</para></listitem></varlistentry>
-</variablelist>
-</sect2>
+files from the Adobe website.</para></sect2>
 
-<sect2>
+</sect1>
+
+<sect1>
 <title>An Overview of the CUPS Printing Processes</title>
 
-<para>
-<figure><title>CUPS Printing Overview</title>
-<mediaobject>
-	<imageobject role="latex"><imagedata fileref="projdoc/imagefiles/a_small"/></imageobject>
-	<imageobject><imagedata fileref="projdoc/imagefiles/a_small.png"/></imageobject>
-</mediaobject>
-</figure>
-</para>
-</sect2>
+<image><imagedescription>CUPS Printing Overview</imagedescription>
+	<imagefile>a_small</imagefile>
+</image>
 </sect1>
 
 </chapter>