Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

apspreview(1) [debian man page]

APSPREVIEW(1)						    BSD General Commands Manual 					     APSPREVIEW(1)

NAME

     apspreview -- preview PostScript file(s) as generated by apsfilter

SYNOPSIS

     apspreview [-Pqueue] [-Zoptions] [input...]
     apspreview [-h]

DESCRIPTION

     With apspreview you can create a PostScript representation of the file(s) you are about to print in order to check it before actually print-
     ing.

     Your file(s) will be converted to PostScript according to the queue specific configuration, and afterwards you will be able to print all or
     some pages from your PostScript viewer application (gv, kghostview or ghostview).

OPTIONS

     -h 	 show help screen
     -Pqueue	 select a printer queue (different from the default one)
     -Zoptions	 use apsfilter command line options (comma-separated list)
     input...	 input file(s) [default: stdin]

NOTES

     If you use the -P option, please remember to pass the same printer queue on to the lpr(1) command.

     Be careful if your printer queue configuration includes a setting to create multiple pages per sheet (PS_NUP=2, PS_NUP=4 or PS_NUP=8).  In
     order to make sure that apsfilter(1) does not repeat n-up printing, use the 1pps command line option when actually printing the file.

     apspreview only works correctly with entries in /etc/printcap that have been created by /usr/share/apsfilter/SETUP. All configuration set-
     tings will be copied from the relevant apsfilterrc files.

FILES

     /etc/printcap			 printer capability data base
     /usr/share/apsfilter/bin/apsfilter  apsfilter script
     /usr/bin/aps2file			 tool to save apsfilter output to a file

SEE ALSO

     apsfilter(1), aps2file(1), apsfilter-bug(1), apsfilterrc(5), printcap(5)

BUGS

     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 wouldn't 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 would't work. If you don't 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).

DOCUMENTATION

     See official apsfilter homepage
     http://www.apsfilter.org/handbook.html   Apsfilter Handbook including the Frequently Asked Questions (FAQ)

USER FORUM

     Please send questions to the official apsfilter help channel apsfilter-help@apsfilter.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.

HISTORY

     The apspreview manpage has been written by Michael LoBin <phallobst@web.de> and first appeared in apsfilter V 7.1.0.

BSD
								   Dec 27, 2001 							       BSD

Check Out this Related Man Page

PSF(8)								   Netatalk 2.2 							    PSF(8)

NAME

       psf - PostScript filter

SYNOPSIS

       psf [-n name] [-h host] [-w width] [-l length] [-i indent] [-c]

DESCRIPTION

       psf is an lpd filter for PostScript printing.  psf interprets the name it was called with to determine what filters to invoke. First, if
       the string ``pap'' appears anywhere in the name, psf invokes pap to talk to a printer via AppleTalk. Next, if the string ``rev'' appears,
       psf invokes psorder to reverse the pages of the job. Finally, if psf was called with a filter's name as the leading string, it invokes that
       filter. If there is no filter to run, psf examines the magic number of the input, and if the input is not PostScript, converts it to
       PostScript.

KLUDGE

       In the default configuration, psf supports two kludges. The first causes psf to check its name for the letter `m'. If this letter is found
       and accounting is turned on, psf calls pap twice, once to get an initial page count and to print the job, and another time to get a final
       page count. This is a work-around for bugs in a variety of PAP implementions that cause printers to never properly close the PAP output
       file. A notable example is any printer by Hewlett-Packard.

       The second kludge causes psf to examine its name for the letter `w'. If this letter is found and accounting is turned on, psf calls pap
       with the -w flag. This flag causes pap to wait until the printer's status contains the string `idle'. Once this string is found, the job is
       printed as normal. This kludge is a work-around for printers, notably Hewlett-Packard's LaserJet IV, which will report a page count while a
       previous jobs is still printing.

EXAMPLE

       The sample printcap entry below invokes psf to print text files, PostScript files, troff's C/A/T output, and TeX's DVI output, to an
       AppleTalk connected LaserWriter Plus. Since the LaserWriter Plus stacks pages in descending order, we reverse the pages and print the burst
       page last.

	   laser|lp|LaserWriter Plus on AppleTalk:
	       :sd=/var/spool/lpd/laser:
	       :lp=/var/spool/lpd/laser/null:
	       :lf=/var/log/lpd-errs:pw#80:hl:
	       :of=/usr/lib/netatalk/ofpap:
	       :if=/usr/lib/netatalk/ifpaprev:
	       :tf=/usr/lib/netatalk/tfpaprev:
	       :df=/usr/lib/netatalk/dfpaprev:

       Note that if the host in question spools to more than one AppleTalk printer, /dev/null should not be used for the lp capability. Instead, a
       null device should be created with mknod for each printer, as has been done above.

       Finally, there is a file in the spool directory, /var/spool/lpd/laser, called .paprc, which pap reads for the AppleTalk name of the
       printer.

SEE ALSO

       psorder(1), printcap(5), lpd(1), mknod(1), pap(1).

Netatalk 2.2							    17 Dec 1991 							    PSF(8)
Man Page