| Andreas Klemm on Sat, 4 May 2002 20:11:05 +0200 (CEST)(envelope-from owner-apsfilter-help@apsfilter.org) |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| Re: apsfilter not quite bug |
This should go to the mailinglist ... On Fri, May 03, 2002 at 05:51:37PM +0100, David Boyes wrote: > A problem that I (and I see on general news groups a few others) have seen > because of Ghostscript, not your excellent filter. apsfilter uses the gs > argument "-sOutputFile=-". A problem with this is that some > Postscript/printer combinations force interesting messages on stdout, even > with the -q option, which are added to the printout I have seen various > promises to fix gs by allowing only DEVICE output on stdout, but in any > case there are a lot of versions which still do this. OK, the fault is > with gs, but I hacked my apsfilter(s) by something like : > > ... -sOutputFile=$APS_TMPDIR/gsout ... >/tmp/apsreport ; cat $APS_TMPDIR | > > AFAICS gsout gets rm'ed, but apsreport - should you wish - remains. This > could I guess be done nicer with pipes, and maybe the newest version of gs > doesn't need this - I stayed with 5.x because early 6.x versions at least > do nasty things with fonts for pdf. > > Best regards, > David Boyes -- Andreas Klemm /\/\/\/\/\/\/\/\/\/\/\ http://www.64bits.de < Powered by FreeBSD > http://www.apsfilter.org/ \ www.FreeBSD.org / http://people.FreeBSD.ORG/~andreas \/\/\/\/\/\/\/\/\/\/