| RBE on Tue, 3 Jul 2001 15:52:53 +0200 (CEST) |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| Re: Apsfilter still f____ up |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 02 July 2001 19:51, John Culleton wrote: > You will need to talk to an lpr-ng expert on this. I still use > the original lpr. I do note that the two printers listed seem > to have an identical second term. Under lpr each printer has a > series of aliases separated by the | character. After the > first such term your two printer entries are identical. Maybe > this works in lpr-ng --- it wouldn't work with lpr. I have no idea what this LPRng would do. I got less output with the earlier LPRng. > My copy of Apsfilter issues a quite differnt printcap. Is this > the printcap issued by Apsfilter or did you build this one > yourself? This is the automatic Apsfilter (7.0) output. > The only cure I could suggest is to use the original lpr > package not lpr-ng and rebuild Apsfilter yet again. Hey, it > works for me and has for years. I'll give it a try. I'm still getting code output instead of the text. - -- Robert Black Eagle Bus Site: http://www.desertsilver.com Keep Private Mail Private: PGP or GNUPG Fix YOURSELF: http://www.hamr.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7Qc4mtjSYKkYJrmcRAuoNAJ9c5T7Y3OAEJhsUrDnyFsCFpELSSQCeILIb p+j33pjg7Urh1+hpdu0hBLA= =mryV -----END PGP SIGNATURE-----