Re: [Gnome-print] Re: [Gimp-print-devel] An introduction to gnome-print (fwd)
- From: Ben Woodard <ben valinux com>
- To: Michael Sweet <mike easysw com>
- cc: Hrafnkell Eiriksson <he kvintus dk>, Miguel de Icaza <miguel helixcode com>, Sven Neumann <neumanns uni-duesseldorf de>, gimp-print-devel lists sourceforge net, gnome-print helixcode com
- Subject: Re: [Gnome-print] Re: [Gimp-print-devel] An introduction to gnome-print (fwd)
- Date: Tue, 06 Jun 2000 20:57:16 -0700
> Ben Woodard wrote:
> > ...
> > 1) We modify libppd to handle PPD files that specify hex encodings of
> > binary strings. These encodings will be pretty much limited to the
> > beginning and the end of the documents.
>
Hadn't noticed that. (I've always been a hack first read standards
later kind of guy.) Good that means that the job is almost trivial. I
love it when most of the work has already been done for me.
> This already exists - see the JCLBegin, etc. attributes.
>
> Also, I'm not sure what this buys you with Ghostscript drivers...
> (i.e. where are you going with this? :)
Very simple. In the LPD setup that I have been working on you can
insert arbitrary filters into the processing path. That is what I took
pstops and turned it into ppdfilt for. I stick it in the filter path
just before something is sent to the printer and voila I have PPD
support. I figure I can get ppdfilt or another program to do the same
sort of thing without much trouble for binary non-PS files. Then I
just stick it in the filter chain after gs and viola limited PPD
support for non-PS printers.
>
> --
> ______________________________________________________________________
> Michael Sweet, Easy Software Products mike@easysw.com
> Printing Software for UNIX http://www.easysw.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]