Changeset 2551 for pykota/trunk/docs/filterpykota.sgml

Timestamp:

10/09/05 22:39:06 (19 years ago)

Author:

jerome

Message:

Replaced some 'filename' tags with 'command' tags.
Improved pkbcodes' documentation.

Files:

• pykota/trunk/docs/filterpykota.sgml (modified) (4 diffs)

pykota/trunk/docs/filterpykota.sgml

@@ -22 +22 @@
     A filter is a computer program which takes data in one format as its input, and outputs the
     same data but transformed into another format. <application>CUPS</application> already
-    contains many filters. For example there's one filter named <filename>pstops</filename> which accepts 
+    contains many filters. For example there's one filter named <command>pstops</command> which accepts 
     PostScript data as its input, and, as its name implies, outputs PostScript data too, but after having
     eventually rearranged the pages to fit several pages on a single sheet of paper, or other manipulations
@@ -29 +29 @@
   
   <para>
-    The <filename>pstops</filename> filter described above is also in charge of doing basic page
+    The <command>pstops</command> filter described above is also in charge of doing basic page
     accounting, but <application>PyKota</application> currently doesn't use this facility since it may
     prove to be unreliable depending on the drivers used or if a paper jam occurs for example.
@@ -36 +36 @@
   <para>
     So to do its own accounting, <application>PyKota</application> has its own filters, for <application>CUPS</application>
-    it's named <filename>cupspykota</filename>, which is in fact a <application>CUPS</application> backends wrapper.
+    it's named <command>cupspykota</command>, which is in fact a <application>CUPS</application> backends wrapper.
     The procedure to plug the correct filter into your printing system is described in the 
     <xref linkend="installation" endterm="installation"> chapter.
@@ -42 +42 @@
   
   <para>
-    Currently with a <application>CUPS</application> internal accounting mechanism, the <filename>pstops</filename>
+    Currently with a <application>CUPS</application> internal accounting mechanism, the <command>pstops</command>
     filter can be bypassed. That's why <application>PyKota</application> uses its own backend.
-    The <filename>cupspykota</filename> backend wrapper ensures that jobs can't bypass it, so you can use
+    The <command>cupspykota</command> backend wrapper ensures that jobs can't bypass it, so you can use
     any printer with any driver and any command line option, and you can be sure that your
     print job will be correctly accounted for.