HELP WANTED: kdeprint with GNUlpr

[James Richard Tyrer]

Goffioul Michael wrote:
>>>non-PS printers, a PPD file is bound to the driver.
>>
>>I don't think that this is necessary since it is first to 
>>describe the printer and second
>>to provide information for the *application's* PostScript driver.
> 
> 
> What I meant is that the options described in a PPD file
> (especially for non-PS printers) are bound to the underlying
> gs driver, because they must be supported by the driver,
> otherwise there's no point to have them. If you detach the
> PPD file from the driver, the only options you can put in
> a PPD file are page sizes and resolutions.
> 
Not exactly.  The PPD file can describe all of the capabilities of the printer and then 
the driver configuration can subset this.  But, yes this is a problem if the application 
only looks at the PPD.  The application doesn't know that the printer driver won't do 
this.  With the KDEPrint system this shouldn't be an issue since there is a common widget 
that is the interface for the print system which should be aware of the limitations of the 
driver.  Simple solution: the driver should support all of the printer's capabilities. :-)
> 
>>But, most applications and printer control widgets assume 
>>square resolution.
> 
> 
> Adobe specifications support different X and Y resolution, so
> it's better to know it and take it into account. You're then
> ready when application's PS driver support assymmetrical
> resolution.
> 
Agreed.
> 
>>>Did you try to contact linuxprinting.org guys to update the 
>>
>>DB? Did you try with a
>>
>>>generic driver? 
>>
>>It works fine with the GNUlpr filter.  I contacted the LPRng 
>>mailing list.
> 
> 
> Foomatic DB (like any other similar open project) heavily relies
> on users to complete the DB. You should definitively contact
> Till to add an entry for your printer.
> 
OK.  Added to the to do list.
> 
>>What I am suggesting that instead of being put in the PPD 
>>file that all GS Device (or 
>>other driver) information should be in a separate 
>>configuration file (like: "LibAPS":
>>
>>	http://sourceforge.net/projects/libaps/
>>
>>Yet Another Dead Printing Project. :-D
>>).
>>
>>I would suggest that the configure file contain:
>>
>><User assigned printer name>
>>     <PPD name with full path>
>>     "GhostScript" <device> | <Other device> | "PostScript"
>>     <resolution(s)> | "ALL"
>>	<Command line> | <other filter information>
>>	<other dependencies> | ""
>>             Capabilities supported
> 
> 
> All this information is already contained in the Foomatic DB.
> Please don't reinvent the wheel :-)

I'm just blabbing on about the theory that it might be better if this information wasn't 
embedded in the PPD.  I wouldn't reinvent the wheel, but it is always possible to think 
about improving things.  Those Rubber tires sure are better than the Iron ones that my 
ancestors used to put on wheels.  Have you ever looked at LibAPPS.  It is so simple that I 
have told newbies how to modify their configuration files.  Note: WordPerfect Office 2000 
for Linux uses it (Corel WINE uses it).

--
JRT