Package: apsfilter
Version: 4.9.1-6
apsfilter considers a ljet4 and a ljet4l equivalent after setting the
options to dvips. However if you send raw postscript to it this is a
bug. The patch below corrects this, and a few more small glitches. It
seems the authors haven't used PRINT_DVI very much :-).
Carlos
--- apsfilter.orig Mon Jun 3 17:31:08 1996
+++ /usr/lib/apsfilter/bin/apsfilter Mon Jun 3 17:32:44 1996
@@ -318,7 +318,8 @@
#-------------------------------------------------------------------------------
case $PRINTER in
- ljet4l) # We can now act like a ljet4
+ ljet4l) # We can now act like a ljet4 - almost...
+ GS_RESOL=300x300
PRINTER=ljet4 ;;
*) ;;
esac
@@ -490,7 +491,7 @@
$DECOMPRESS $PRINT_DVI
fi
- if [ -z "$TMP_FILE" ]; then
+ if [ ! -z "$TMP_FILE" ]; then
rm -f $TMP_FILE
fi
}
@@ -895,7 +896,7 @@
*dvi*)
if [ "$HAVE_DVIPS" = "True" \
- -o -z "$PRINT_DVI" ]; then
+ -o ! -z "$PRINT_DVI" ]; then
print_dvi
else
fault_filetype
