> From [EMAIL PROTECTED] Wed Dec 10 00:20:05 2003 > Subject: lprngtool !? (1.3.2) > From: Uwe Dippel <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Wed, 10 Dec 2003 16:19:26 +0800 > > ... has always been my friend. I used it on Debian, and suddenly it > seemed broken; I could not print any more. > lprngtool showed 'invalid printcaps'. > Breakage is always a problem ... ! > It took me more than half a day to bring it back to work, despite all > efforts and all 'Help'. > The problem is really on the side of HCI. > > Good, after so much rant: > Please, please, keep up the good work ! Lprngtool *is* good work !! > > And try to follow common user guidance, please, get the system printcaps > up *before* user printcaps; This is really a flaw !
The idea is that your users can 'override' on a local basis the various printcap options. But I will rethink this. > Counterintuitive, especially compared to earlier versions and common > sense. > Check for the existence of spool directories before throwing out the > test prints, etc. Yes. checkpc -f should be done. > > 3 attempts failed > '[EMAIL PROTECTED]' - no network support for 'lpq' operation > > are so disheartening.... > > Just start lprngtool: fine, the spools show. But then ? No 'Add' / 'Add > Printer'. How is Joe Sixpack to assume he has to 'View printcap' ?? He / Oops! This is bad... > she doesn't even have to know such existed !! Even if - out of despair - > they ever click 'View printcap'; there is still no 'Add Printer'. No, > you add a printcap instead. Plus, the wrong one: the user printcap which > will never see you printing anything on a JetDirect. No, you have to do > the experiment again: 'View System Printcap'. And still, you don't want > to add a printcap, but a *printer* ! Yes. > > And then the test tool !! > I've been in Linux for 5 years and still, this is gibberish ! Right. > > Look, what it says is: > > Line1 > Line2 > > If you see: > > Line1 > Line2 > Your printer needs to do LF to CRLF translation. > - If you have a vintage text-only printer, then use the legacy > lpf filter - > lp > :filter=/usr/.../lpf > - If you have a PCL capable printer then use IFHP > lp > :filter/usr/.../ifhp > > - If this page did not eject automatically, add ":fq" (formfeed on > close) > to the printcap options > lp > :fq > > I don't have a text-only printer; I have no clue if my printers are PCL > > What to do if not ?? Isn't that CRLF a symptom of a printer and > therefore part of the database ? No, okay. But why not a check box like > earlier instead of fiddling with vi and printcap !? > Plus, there it says you shouldn't edit manually. > And remains incomprehensible. OK , I get the idea. It needs to be fixed up. > > Mine looks like > Line1 > Line2 > If you see: > Line1 > Line2 > ..... > > though the ASCII Test Page comes out in a good order. > > > Kind regards, > > Uwe, > who is really interested in useability on the desktop > > ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
