|coated||Coated (inkjet) paper.|
|premium||Premium (photo) paper.|
|auto||Automatic filetype recognition and data conversion.|
|ascii||Force printing as ASCII document. For example to print Postscript source code without actually interpreting it.|
|raw||Pass-through mode, your print data wont be changed by any filter.|
|Text file filter to use, when printing ASCII documents.|
|tray0...tray9||Paper feed tray number.|
|pretty=N||highlight level for pretty-printing (N=0,1,2)|
|header|noheader||Whether you want headers in your text prints.|
|border|noborder||Whether you want borders in your text prints.|
|1pps|2pps|4pps|8pps||Pages per sheet.|
|book||Output pages in "book" format, implies "2pps,duplex,shortbind"|
|duplex|simplex||Whether to use duplex mode or not.|
|shortbind|longbind||Paper binding edge.|
|copies=N||Number of copies.|
lpr -C high:color:glossy file.gif tex.dvi.gz file.html ...
prints some files of different types no matter whether compressed or not on the Unix default printer (see lpr 1 ).
The -C option to the lpr command sets additional ghostscript driver-specific options. Here, high means high resolution (e. g. 600 dpi for an HP Printer using gss "cdj850" printer driver), color output (e.g. 32 bits per pixel), and the paper type is set to glossy paper
lpr -C duplex somefile
enables pseudo duplex printing by halting the print queue after printing a documents even pages and so giving the user a chance to flip paper and restart printing after executing a special user command on the command line.
User gets a notification mail containing a session oriented magic wakeup command and key which restarts printing of the odd pages of the print job.
The so called magic command makes sure that only the initiator of the print job is able to restart printing after reinserting the paper.
Beware, if you have nasty users, this can cause print jobs to hang, filling up the print queue and at least the /var file system.
/etc/printcap printer capability data base /usr/local/share/apsfilter/bin/apsfilter apsfilter script /usr/local/share/apsfilter/SETUP printer installation script, creates/updates /etc/printcap /usr/local/share/apsfilter/SETUP.cfg saved settings from last printer setup /usr/local/share/doc/apsfilter/handbook.html the apsfilter handbook in HTML format /usr/local/etc/apsfilter/ configuration directory /usr/local/etc/apsfilter/apsfilterrc global configuration file /usr/local/etc/apsfilter/apsN/ printer specific configuration directory /usr/local/etc/apsfilter/apsN/apsfilterrc printer specific configuration file $HOME/.apsfilter/apsfilterrc.apsN user definable printer specific configuration file /usr/local/etc/apsfilter/apsN/smbclient.conf smbclient config file for printing on Windows remote printer /usr/local/etc/apsfilter/apsN/pap.conf pap config file for printing on AppleTalk printer /usr/local/etc/apsfilter/apsN/lpr.conf config file for remote printer that needs special treatment
aps2file(1), apsfilter-bug(1), apspreview(1), gs(1), gs-hpdj(1), lpr(1), smbclient(1), apsfilterrc(5), printcap(5), lpd(8)
See apsfilter software center - http://www.apsfilter.org/ - for new versions, bugfixes and known bugs.
Please use the new tool apsfilter-bug(1) to release bug- or problem reports. It automatically presents you a form in an editor window which asks you some standard questions. If you save and quit the editor session, then this report is sent automatically via e-mail to the proper apsfilter mailinglist.
If apsfilter fails to print something or prints it in a way you wouldnt expect and you want to report an apsfilter error then please save the debugging output of one print session using the new aps2file(1) utility by typing aps2file -D -Z options file > /dev/null 2> file.debug and including the debugging output in the file file.debug into the edit session of the apsfilter-bug utility, so that it is included into the mail to the apsfilter mailinglist.
Please note that you need to run /bin/sh (Bourne Shell), bash or a compatible shell, so that the above mentioned output redirection works. Under C-shell (/bin/csh) or tcsh it wouldt work. If you dont know, then simply make sure you use the Bournce shell by typing /bin/sh or bash, then you should have no problems with redirection of stdout and stderr (> /dev/null 2> file.debug).
See official apsfilter homepage
http://www.apsfilter.org/handbook.html Apsfilter Handbook including the Frequently Asked Questions (FAQ)
Please send questions to the official apsfilter help channel firstname.lastname@example.org. The above section BUGS and the file HOWTO-BUGREPORTS tells you how to report bugs. If you want to know how to troubleshoot your apsfilter installation, please read the manpage aps2file(1) and apsfilter-bug(1) as well as the Apsfilter Handbook carefully.
The apsfilter manpage appeared first in apsfilter V 5.4.0.