Docbook XML conversion: projdoc

[samba.git] / docs / docbook / projdoc / CUPS-printing.xml

diff --git a/docs/docbook/projdoc/CUPS-printing.sgml b/docs/docbook/projdoc/CUPS-printing.xml
similarity index 99%
rename from docs/docbook/projdoc/CUPS-printing.sgml
rename to docs/docbook/projdoc/CUPS-printing.xml
index 57faebdcd664918a34a0c78c8c35436474239162..7e302000e6009cf944069b796fceafae01a8c73a 100644 (file)
--- a/docs/docbook/projdoc/CUPS-printing.sgml
+++ b/docs/docbook/projdoc/CUPS-printing.xml
@@ -1177,7 +1177,6 @@ Summary - You need:
 
 <para>
 <simplelist>
-
        <member>A "foomatic+<replaceable>something</replaceable>" PPD is not enough to print with CUPS (but it is *one* important component)</member>
        <member>The "cupsomatic" filter script (Perl) in <filename>/usr/lib/cups/filters/</filename></member>
        <member>Perl to make cupsomatic run</member>
@@ -1427,15 +1426,15 @@ download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal
 the files:
 </para>
 
-       <para>
-       <computeroutput>
-          cups-samba.install
-          cups-samba.license
-          cups-samba.readme
-          cups-samba.remove
-          cups-samba.ss
-       </computeroutput>
-       </para>
+<para>
+<computeroutput>
+   cups-samba.install
+   cups-samba.license
+   cups-samba.readme
+   cups-samba.remove
+   cups-samba.ss
+</computeroutput>
+</para>
 
 <para>
 These have been packaged with the ESP meta packager software "EPM". The
@@ -1444,13 +1443,13 @@ These have been packaged with the ESP meta packager software "EPM". The
 into <filename>/usr/share/cups/drivers/</filename>. Its contents are 3 files:
 </para>
 
-       <para>
-       <computeroutput>
-          cupsdrvr.dll
-          cupsui.dll
-          cups.hlp
-       </computeroutput>
-       </para>
+<para>
+<computeroutput>
+   cupsdrvr.dll
+   cupsui.dll
+   cups.hlp
+</computeroutput>
+</para>
 
 <caution><para>
 Due to a bug one CUPS release puts the <filename>cups.hlp</filename>
@@ -1460,8 +1459,8 @@ the file after running the "./cups-samba.install" script manually to the right p
 </para>
 
        <para>
-       <userinput> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
-       </userinput>
+<userinput> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
+</userinput>
        </para></caution>
 
 <note>
@@ -1535,16 +1534,16 @@ as compared to the Adobe drivers?
 </para>
        
 <para>
-<itemizedlist>
-       <listitem><para>
+<simplelist>
+       <member><para>
        no hassle with the Adobe EULA
-       </para></listitem>
+       </para></member>
 
-       <listitem><para>
+       <member><para>
        no hassle with the question "where do I get the ADOBE*.* driver files from?"
-       </para></listitem>
+       </para></member>
 
-       <listitem><para>
+       <member><para>
        the Adobe drivers (depending on the printer PPD associated with them)
        often put a PJL header in front of the core PostScript part of the print
        file (thus the file starts with "<replaceable>1B</replaceable>%-12345X"
@@ -1557,47 +1556,47 @@ as compared to the Adobe drivers?
        leads to the page accounting in "/var/log/cups/page_log" not receiving
        the exact mumber of pages; instead the dummy page number of "1" is
        logged in a standard setup)
-       </para></listitem>
+       </para></member>
 
-       <listitem><para>
+       <member><para>
        the Adobe driver has more options to "mis-configure" the PostScript
        generated by it (like setting it inadvertedly to "Optimize for Speed",
        instead of "Optimize for Portability", which could lead to CUPS being
        unable to process it)
-       </para></listitem>
+       </para></member>
 
-       <listitem><para>
+       <member><para>
        the CUPS PostScript driver output sent by Windows clients to the CUPS
        server will be guaranteed to be auto-typed as generic MIME type
        "application/postscript", thusly passing thru the CUPS "pstops" filter
        and logging the correct number of pages in the page_log for accounting
        and quota purposes
-       </para></listitem>
+       </para></member>
 
-       <listitem><para>
+       <member><para>
        the CUPS PostScript driver supports the sending of additional print
        options by the Win NT/2k/XP clients, such as naming the CUPS standard
        banner pages (or the custom ones, should they be installed at the time
        of driver download), using the CUPS "page-label" option, setting a
        job-priority and setting the scheduled time of printing (with the option
        to support additional useful IPP job attributes in the future).
-       </para></listitem>
+       </para></member>
 
-       <listitem><para>
+       <member><para>
        the CUPS PostScript driver supports the inclusion of the new
        "*cupsJobTicket" comments at the beginnig of the PostScript file (which
        could be used in the future for all sort of beneficial extensions on
        the CUPS side, but which will not disturb any other application as those
        will regard it as a comment and simply ignore it).
-       </para></listitem>
+       </para></member>
 
-       <listitem><para>
+       <member><para>
        the CUPS PostScript driver will be the heart of the fully fledged CUPS
        IPP client for Windows NT/2k/XP to be released soon (probably alongside
        the first Beta release for CUPS 1.2).
-       </para></listitem>
+       </para></member>
 
-</itemizedlist>
+</simplelist>
 </para>
 </sect1>