	------------------------------------------------------------
	   A P S F I L T E R   V 4.8  -  "FAQ with answers ..."
	------------------------------------------------------------

                     copyright Andreas Klemm 1993, 1994

                            andreas@knobel.gun.de

                   ---------------------------------------

			co-author Thomas Bueschgens 

			    sledge@hammer.oche.de

                         ---------------------------

-------------------------------------------------
Apsfilter Frequently Asked Questions with answers
-------------------------------------------------

Q 1.1	I just installed dvips but I can't print dvi files.

A:	Perhaps you forgot to run $APS_BASEDIR/setup/filtersetup
	again as root. This script updates the file 
	$APS_BASEDIR/global/filters_found automatically this way:
		HAVE_DVIPS=True
	Without this definition apsfilter is unable to print dvi files.

	If this didn't solve your problem, then I assume, that you
	installed your dvips program in a very exotic path.
	Refer to the section, how to incorporate unusual searchpaths
	into apsfilter -> Q 1.5.

Q 1.2	Ok, I ran mksymlinks as root again, but I'm still unable to 
	print dvi files.

A:	Perhaps your dvips program is in a very tricky search path.
	Apsfilter only knows about search paths that are defined
	in the $APS_BASEDIR/global/GLOBAL.sh file.
	Add the path to your dvips binary to tat file and run
	$APS_BASEDIR/setup/mksymlinks (with root permissions)
	again !

Q 1.3	Do I have to invoke apsfilter directly ?

	No ! Apsfilter creates entries for your printer in /etc/printcap.
	You are now able to print the various file types by simply typing:
		lpr file

	If you don't tell lpr, which printer to use, lpr selects the
	default lineprinter, the printcap entry with the name "lp".
	The default lineprinter calls apsfilter as input filter with
	this default behaviour:
		- automatic filetype recognition enabled
		- monochrome printing enabled

	There are some special situations where you want to tell apsfilter
	to behave different. This is the reason for that many entries in
	/etc/printcap for only one printer !

	The -P option of the lpr command allows you to switch between
	the different printer entries... i.e.:
		lpr -P ascii
		lpr -P raw

Q 1.4	Printing of long ascii listings (C-Source,...) is dog slow

	You can disable the feature to pipe ascii text through
	a2ps and gs by using the printer alias "raw".
		lpr -Praw some_long_listing

	Your text will now be printed directly without time
	consuming filters ...

	If your printer is a HP printer, then he needs a special
	setup to break lines accordingly (cr/nl conversion).
	This can be done by hacking the needed escape sequences in
	into the environment variable
		PRINT_RAW_SETUP_PRINTER='\027E2'
	which is located in your $HOME/.apsfilterrc file.
	Remove the '#' sign in front of the environment variable
	to make it active and type in the correct escape sequence.

Q 1.5	How to manage strange search paths for filter programs in apsfilter

	Modify the file $APS_BASEDIR/global/GLOBAL.sh
	Append your very_special_searchpath to the variable
		LOCAL_PATH=/usr/local/bin:/local/bin

	i.e. if your dvips is located in /foo/bin and your 
	pbmplus utilities are located in /bar/bin, then
	modify that line into:
		LOCAL_PATH=/usr/local/bin:/local/bin:/foo/bin:/bar/bin

	After that re-run (as root) the program 
		$APS_BASEDIR/setup/filtersetup
	to create a new file:
		$APS_BASEDIR/global/filters_found

Q 1.6   I've installed apsfilter and still cannot print anything using
	lpr! Using cat <filename> | /dev/lp? works fine. Any ideas?

A:	Sure!! First check out wether lpr does work without apsfilter
	installed, if not, check out your documentation (for
	Linux-Users this would be the Printing-Howto).

	If this doesn't help you may need to reinstall lpr and
	friends to get the permissions right! Sometimes the Distribs
	have Printing f*cked up!
