[cups.general] renderer command

[Till Kamppeter]

You can use Foomatic, but then you must use the Foomatic data which the 
Gimp-Print package generates. The "./configure" should auto-detect 
whether on your system is Foomatic installed and if so, it adds the 
necessary data to your local Foomatic database so that the KDE Printing 
Manager offers the appropriate "Foomatic + Gimp-Print" entries. The 
solution of CUPS PPDs needs one piece of software less, it does not need 
Foomatic, so it also works if Foomatic is not installed on your box. It 
needs only CUPS and ESP GhostScript (or another GhostScript which is 
patched to have the "cups" device).

    Till


Anonymous wrote:
> Thanks! will do that.
> Final (hopefuly) question:
> It is understood from your instructions that I should not use Foomatic. Is this correct?
> 
> Till Kamppeter wrote:
> 
>>Get the newest Gimp-Print sources, install the cups-devel,
>>libcups-devel, or cupsys-dev package (name depends on your distro),
>>compile with
>>
>>../configure --with-cups
>>make
>>make install
>>
>>do
>>
>>killall -HUP cupsd
>>
>>and try to set up your printer again. Use model/driver selections marked
>>with "CUPS + Gimp-Print".
>>
>>Report a bug to your distro, as it does not provide working PPDs or
>>Foomatic data for Gimp-Print.
>>
>>    Till
>>
>>
>>Anonymous wrote:
>>
>>>Thanks for all your help so far. What does it mean in my case?
>>>what should be my next steps to get the printer to work?
>>>
>>>Till Kamppeter wrote:
>>>
>>>
>>>>I have done some slight modifications on Foomatic now (in the Foomatic
>>>>CVS on linuxprinting.org, both stable and unstable branches), that PPD
>>>>files with blank *FoomaticRIPCommandLine cannot be generated any more.
>>>>In this case now an error is issued and so frontends like the KDE
>>>>Printing Manager should give an error message instead of creating a
>>>>broken print queue.
>>>>
>>>>The blank *FoomaticRIPCommandLine was caused by a driver entry in the
>>>>Foomatic database with an empty renderer command line prototype. This
>>>>means that the driver entry has no driver execution information. In most
>>>>cases the driver has several different GhostScript device names and the
>>>>execution information resides in the Foomatic entry with another name.
>>>>In the case of Gimp-Print there is no execution info as the execution
>>>>ifo is supplied with the driver package. See the text of the driver
>>>>entry in such cases (AFAIR the KDE Printing Manager has a button to
>>>>display it).
>>>>
>>>>   Till
>>>>
>>>>
>>>>Helge Blischke wrote:
>>>>
>>>>
>>>>>Anonymous wrote:
>>>>>
>>>>>
>>>>>
>>>>>>I believe this was generated by the kde control center when
>>>>>>configuring my printer. I have both the
>>>>>>Gimp-Print package installed and the foomatic one.
>>>>>>I'd try installing the printer straight from CUPS, but for some odd
>>>>>>reason I can't seem to connect to
>>>>>>localhost:631, although kcontrol does seem to connect there.
>>>>>>[...]
>>>>>
>>>>>
>>>>>There is a severe bug in your PPD. The line
>>>>>*FoomaticRIPCommandLine: ""
>>>>>defines an empty command to be executed by foomatic-rip, which is
>>>>>illegal. Instead, if your printer is a native PostScript printer,
>>>>>this keyword should *not* be present - foomatic-rip then uses the
>>>>>cat command to pass on the print stream.
>>>>>
>>>>>As it is, foomatic-rip tries to execute an empty command which fails,
>>>>>of course (and leads to a shell syntax error when using the
>>>>>debug switch).
>>>>>
>>>>>Get a correct PPD.
>>>>>
>>>>>Helge
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>_______________________________________________
>>>cups mailing list
>>>cups at easysw.com
>>>http://lists.easysw.com/mailman/listinfo/cups
>>>
>>>
>>
> 
> _______________________________________________
> cups mailing list
> cups at easysw.com
> http://lists.easysw.com/mailman/listinfo/cups
> 
>