Cups > 1.6 without Ghostscript,via. poppler on Slackware 14

[pipitas]

On 10/26/12 21:11, Andrew Robinson wrote:
>> Andrew Robinson <andrew3 at r3dsolutions.com> writes:
>
>>
>>> Regarding filtering in general (and not the alternate set); are you
>>> aware of any test files that one could attempt to print (for example a
>>> raster file) so that only the rastertoepson filter and the cups 1.6.1
>>> backend would be involved (to see if the ppd file & cups 1.6.1 is good
>>> exclusive of the other package?)
>>>
>>> Or is there a debugging switch and a way to capture the raster file
>>> generated so I can see what it attempted to send to the epson raster
>>> program/backend ?
>>>
>>> (I'm trying to find easy ways to isolate the problem(s).)
>>
>> You could activate output to file, for debugging, and then, e.g.,
>> /tmp/foo would hold the raster image that would have gone to your
>> printer.
>>
>> In /etc/cups/cupsd.conf you need to add:
>>
>> FileDevice Yes
>>
>> And then you need, AFAIK, create the file printer with lpadmin. Then,
>> in CUPS GUI you can set its driver to be the R200. For example, after
>> that, my printers.conf ends up with the following entry, using a Canon
>> printer driver here:
>>
>> <Printer foofile>
>> UUID urn:uuid:fedae68d-3fa7-3aa3-73c9-0eba1ee02721
>> Info foofile
>> MakeModel Canon BJC-5500 - CUPS+Gutenprint-CVS v5.2.9
>> DeviceURI file:/tmp/foo
>> State Idle
>> StateTime 1344670554
>> Type 8450060
>> Accepting Yes
>> Shared No
>> JobSheets none none
>> QuotaPeriod 0
>> PageLimit 0
>> KLimit 0
>> OpPolicy default
>> ErrorPolicy retry-job
>> </Printer>
>>
>> --
>> Gernot Hassenpflug
>>
>
> Hi Gernot!
>
> Your suggestion is good,useful ... and still bad. :)
> It's not the cups raster file which was produced when I tried your suggestion -- but rather the actual printer encoding.  I have a work-around, but I thought I'd share what happened... (If your eyes glaze over, I have a simple question at the end of the post... ;) )

That's exactly what Gernot suggested when saying "/tmp/foo
would hold the raster image that would have gone to your
printer".

> Here's what I did
> [...]

If you want to get hold of the generic "CUPS-Raster" data
(not the printer specific raster data) in the output file
then add the following line(s) to the FileDevice printer's
PPD file (somewhere within the first few lines of the PPD):

   *cupsFilter:	"application/vnd.cups-raster 0 -"

This line tells CUPS 2 things:

1. "Whatever the input, try to construct a filter chain
     that which outputs CUPS-Raster."

2. "As the last filter in the chain, use the 'nullfilter'
    ("-") on it and then hand that result to the backend."

Cheers,
Kurt Pfeifle