Re: [SLE] SuSE and Printing (contains bug report for 7.3 apsfilter)
True I guess. I never tried the ascii or raw device which get set up by yast2 when you create a printer. I tend to just go the usual route, generic lp that is). Fact is I used the generic type under 7.2 and it worked. So there must be something different in apsfilter package between 7.2 and 7.3 which makes it seem buggy to me. Anyhow I am not too fond of the "ascii,generic,raw" method. When I want to print to a printer I want to say 'print printername filename' and I as a user don't want to have to worry which device I have to queue it to. Imagine somebody develops 15 more device types and in the future we have to set up 15 queues for a single printer. What a mess... I want the printer/software to have it figure out to get the file on paper. =) I suppose since ifhp is optimized for HP it does this sort of thing since you specify in printcap which exact printer you have. ZEUS:cm=Network Printer ZEUS:\ :lp=/dev/lp0:\ :sd=/var/spool/lpd/ZEUS:\ :lf=/var/spool/lpd/ZEUS/log:\ :af=/var/spool/lpd/ZEUS/acct:\ :ifhp=model=hp6p,status@:\ :filter=/usr/local/libexec/filters/ifhp:\ :la@:mx#0:\ :tr=:cl:sh: mk
From: Anders Johansson
To: suse-linux-e@suse.com Subject: Re: [SLE] SuSE and Printing (contains bug report for 7.3 apsfilter) Date: Sat, 8 Dec 2001 11:49:56 +0100 MIME-Version: 1.0 Received: from [202.58.118.7] by hotmail.com (3.2) with ESMTP id MHotMailBDDB3B690089400431E5CA3A760709F70; Sat, 08 Dec 2001 02:50:20 -0800 Received: (qmail 11870 invoked by alias); 8 Dec 2001 10:47:47 -0000 Received: (qmail 11858 invoked from network); 8 Dec 2001 10:47:46 -0000 From suse-linux-e-return-83089-purpleshirt Sat, 08 Dec 2001 02:51:17 -0800 Mailing-List: contact suse-linux-e-help@suse.com; run by ezmlm Precedence: bulk X-No-Archive: yes list-help: mailto:suse-linux-e-help@suse.com list-unsubscribe: mailto:suse-linux-e-unsubscribe@suse.com list-post: mailto:suse-linux-e@suse.com X-MIME-Notice: attachments may have been removed from this message X-Mailinglist: suse-linux-e Delivered-To: mailing list suse-linux-e@suse.com Message-Id: <200112081049.fB8AngU23479@cicada.linux-site.net> X-Mailer: KMail [version 1.3.2] References: In-Reply-To: On Saturday 08 December 2001 11.34, Purple Shirt wrote:
This was never a problem until 7.3. The Windows machine has locally the 'HP 6P Enhanced' drivers from hp.com installed.
When I was fiddling around with samba printer sharing, I had tremendous problems until I let the win-machines print through the 'raw' device created with apsfilter. It sends through the spool file directly to the printer without trying to interpret it. The output you give looks very much like some sort of printer control language, so my guess would be that apsfilter interprets it as ascii and escapes it to the printer. The raw device wouldn't do that, if my guess is correct.
//Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
On Saturday 08 December 2001 12.14, Purple Shirt wrote:
Anyhow I am not too fond of the "ascii,generic,raw" method. When I want to print to a printer I want to say 'print printername filename' and I as a user don't want to have to worry which device I have to queue it to. Imagine somebody develops 15 more device types and in the future we have to set up 15 queues for a single printer. What a mess...
Yep. That's the idea behind auto (not generic). It tries to determine through various more or less ingenious methods what type of file you're trying to print, and handle it accordingly. This autodetection is probably what broke between 7.2 and 7.3 in your case. apsfilter is just a wrapper. IIRC it uses the ghostscript drivers for HP which I believe are written by HP themselves nowadays. The raw device is ideal for networked printing, where the client's driver has already converted the spool file to a format recognizable by the printer. I haven't heard about ifhp, since gs works for my deskjet, but that's linux in a nutshell: use whatever works best for you. //Anders
participants (2)
-
Anders Johansson
-
Purple Shirt