|
Re: Re: Re: How to replicate old LPD filter functionality?: msg#00026printing.cups.devel
Morgan wrote: > Helge Blischke wrote: > > What type of filter was that in your former printcap file? > > If I knew how your old filter "ticked", I probably may give you some > > hints how to rebuild this functionality with CUPS (no guarantee, > though). > > > > Helge > > The script was called as a printcap input filter (if=). However, it > didn't really "filter" anything. It simply captured the input, reformatted > it and stored it into separate text files in another spool directory. > The original print job is removed. The queue is processed later by > another application outside of the lpd/printing system. > > In short, I basically want to be able to accept the data from a print > job, massage it, store it somewhere else, and then be done. If you > can suggest how one might replicate this functionality using CUPS, > that would be very helpful. Basically you can do it by writing your own "backend". This may be a shellscript. For an example of a simple backend (this one does the conversion of any printjob to PDF and stores it somewhere) look at the "distiller" script at http://printing.kde.org/downloads/ Cheers, Kurt |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Re: How to replicate old LPD filter functionality?: 00026, Dominik Kubla |
|---|---|
| Next by Date: | Re: Re: Re: How to replicate old LPD filter functionality?: 00026, Anonymous |
| Previous by Thread: | Re: Re: How to replicate old LPD filter functionality?i: 00026, Dominik Kubla |
| Next by Thread: | Re: Re: Re: Re: How to replicate old LPD filter functionality?: 00026, Morgan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |