> From [EMAIL PROTECTED] Mon Nov 24 03:59:42 2003 > Date: Mon, 24 Nov 2003 11:26:38 +0100 > From: Till Kamppeter <[EMAIL PROTECTED]> > To: "For users and developers of KDEPrint, the KDE printing architecture" <[EMAIL > PROTECTED]>, > [EMAIL PROTECTED] > Subject: LPRng: KPE Print and LPRng > > I forward this to the LPRng mailing list as a suggestion to the LPRng > developers and contributers. > > Till > > Goffioul Michael wrote: > > IMHO, what's really missing in LPRng to build a decent support > > in KDEPrint is an API and a library. Any command/operation has > > to be made by executing a program and parsing its output, so this > > heavily relies on a specific syntax. This is a pain from the > > client programmer point of view. That's why CUPS support is much > > more developed in KDEPrint: it provides a full API. > > Another problem with LPRng is the *wide* variety of driver > > systems existing out there, each one using its own files, setup, > > DB syntax or whatever. Again here, CUPS is more easy to use: > > you can request the server for the driver file, and it's always > > a PPD file. Presenting print options is then quite easy. > > LPRng is probably a wonderful print spooler for the command-line, > > but it's really difficult to build a modern GUI on top of it. > > The first thing I would expect from LPRng is an API. > > > > Michael. > > > > > >>-----Original Message----- > >>From: Patrick Powell [mailto:[EMAIL PROTECTED] > >>Sent: Saturday, November 22, 2003 04:45 > >>To: Till Kamppeter > >>Cc: For users and developers of KDEPrint, the KDE printing > >>architecture > >>Subject: Re: HELP WANTED: kdeprint with GNUlpr > >> > >>I actually did some work on this a while ago. > >> > >>-- > >>Patrick Powell Astart Technologies > >>[EMAIL PROTECTED] 6741 Convoy Court > >>Network and System San Diego, CA 92111 > >> Consulting 858-874-6543 FAX 858-751-2435 > >>LPRng - Print Spooler (http://www.lprng.com) > > > > _______________________________________________ > > kde-print mailing list > > [EMAIL PROTECTED] > > https://mail.kde.org/mailman/listinfo/kde-print > > > >
I have been working with the Foomatic (Linuxprinting.org) folks. The goal is to come up with a SINGLE database for Foomatic-RIP and ifhp and LPRng, and then use a PPD file for configuring it. There are several parts to the system: a) specifying HOW you send the job (communications channel) b) HOW you monitor the job c) HOW you translate the job to a format compatible with the printer. a) is basically the [EMAIL PROTECTED] entry in the printcap file b) is basically the stuff in the IFHP file that has to do with job processing c) is really in the PPD file. After the next revision, you will probably see an ifhp.conf file that will consist only of communcation information, i.e. - [socket] status ps pjl sync [appsocket] appsocket [snmp] status sync=snmp pagecount=snmp waitend=snmp And you will have all of the other formatting options in the PPD file. This will allow you to do things like: lpinfo -Pprinter and get a list of the printer options. Coming soon. Patrick Powell ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
