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

Timestamp:

07/25/03 15:10:58 (21 years ago)

Author:

jalet

Message:

Improved documentation

Files:

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

pykota/trunk/docs/filterpykota.sgml

@@ -7 +7 @@
   
   <para>
-    To account for pages or eventually ink usage, you must plug your accounting
+    To account for pages or eventually ink usage 
+    <footnote>
+      <para>
+        PyKota doesn't currently account for ink usage, it only accounts
+        pages. To account for ink usage, you should use PrintBill instead.
+      </para>  
+    </footnote>  
+    , you must plug your accounting
     system somewhere into the printing system you use, be it either <application>CUPS</application>
     or <application>LPRng</application>. One way to do this without having
@@ -54 +61 @@
     When used with an <application>LPRng</application> backend, the accounting filter is not defined the same way 
     input filters are, so the problem described above doesn't exist, and <application>PyKota</application>
-    may work with non-postscript printers, provided they can report their page counter and you know how to do
-    this.
+    may work with non-postscript printers, provided they can report their page counter and you know how to retrieve
+    it.
   </para>
   
@@ -71 +78 @@
     page counter for this printer when the previous job was launched, computes the difference, and report it as the 
     previous job's size in the Quota DataBase. It then updates the last user's print quota and account balance, and
-    warn him if he is over quota or his account balance below 0. Finally it checks if the user who launched the 
+    warn him if he is over quota or if his account balance is below 0. Finally it checks if the user who launched the 
     current job is below or above his print quota, and either allow or deny the job's datas to pass to the underlying 
     layer (the printer itself).
@@ -83 +90 @@
     pages on a single line on its standard output. This number is then
     read by PyKota and used to update the current user's quota information.
+    Of course checks are also done like with the <literal>querying</literal>
+    accounting method, to see if the current job is allowed to be printed or not.
   </para>
   
@@ -97 +106 @@
 
 $Log$
+Revision 1.6  2003/07/25 13:10:58  jalet
+Improved documentation
+
 Revision 1.5  2003/07/25 10:41:29  jalet
 Better documentation.