65 | | The solution is to plug the pykota filter into the |
66 | | filtering chain when the print job is still in |
67 | | PostScript format, before being converted to the |
68 | | dumb printer's native format. You can't use the |
69 | | cupspykota CUPS backend with 'dumb printers'. |
| 65 | You have to use a software accounter directive, and |
| 66 | create a script which understands your printer's |
| 67 | Page Description Language. |
71 | | Here's how to do : |
72 | | |
73 | | - Disable raw mode by modifying *.convs and |
74 | | *.types files in /etc/cups, then restart |
75 | | CUPS. |
76 | | |
77 | | - If you print from Windows through Samba, |
78 | | don't put '-o raw' in the print command |
79 | | definition in smb.conf |
80 | | |
81 | | - Under Windows, use a PostScript driver |
82 | | set to maximum compatibility mode. |
83 | | |
84 | | - Modify *.convs and *.types files to |
85 | | insert the pykota filter into the |
86 | | filtering chain, as described |
87 | | here (url should be on a single line) : |
88 | | |
89 | | http://cgi.librelogiciel.com/pipermail/ ... |
90 | | ... pykota/attachments/20030721/753239b5/attachment.eml |
91 | | |
92 | | and restart CUPS. |
| 69 | PyKota natively understands PostScript and PCL5, |
| 70 | but PCL6 support is in the works, and more PDLs |
| 71 | will be added in the future. However you can always |
| 72 | plug your own PDL analyzer in PyKota. |
121 | | |
122 | | * Some, not all, print jobs are never accounted for, why ? |
123 | | |
124 | | From version 1.16alpha7, you can now use the cupspykota |
125 | | CUPS backend, which ensures that all print jobs will be |
126 | | accounted for. The use of the old pykota filter is deprecated |
127 | | with CUPS. It remains the filter of choice for LPRng though, |
128 | | or when you absolutely need to support a 'dumb printer' (see |
129 | | definition above). |
130 | | |
131 | | * When printing from Windows, the jobs are never accounted for, |
132 | | but from *nix they are. Could you explain the reason for this ? |
133 | | |
134 | | First refer to the point above. If this doesn't solve your |
135 | | problem, try to set your print driver to PostScript mode |
136 | | and check the "maximum compatibility" box in its configuration, |
137 | | instead of "maximum speed". Often HP printers come with both |
138 | | a PCL and a PostScript driver under Windows. Don't install the |
139 | | PCL one. |