[gs-devel] upcoming freeze for the 8.63 release - Make CUPS filters/PPDs PDF ready

[Till Kamppeter]

Ralph Giles wrote:
> On 17-Jul-08, at 9:28 AM, Till Kamppeter wrote:
> 
>> Now my problem is how the options in the PPD have to be defined. Most 
>> of them are PostScript commands to be added to the data stream, but 
>> what happens if the data stream is PDF? Anyone has an idea how to do 
>> this correctly?
> 
> The Ghostscript PDF interpreter is still implemented in Postscript and 
> setting device parameters with a prepended postscript job will still 
> work. Beyond that I don't know exactly what you need to do for the cups 
> workflow, so I'd suggest just experimenting.
>

The insertion of the PostScript code of the PPD CUPS does with the 
pstops filter. When CUPS is used with a PDF printing workflow this 
filter is replaced by the pdftopdf filter from OpenPrinting Japan. 
Otani-san (or anyone else at OP Japan), does the pdftopdf filter somehow 
insert the Postscript code of the options in the PPD file into the PDF 
data stream? Or how should I proceed?

Ralph, can I simply preceed the PDF data stream with the PostScript code 
from the PPD, putting "%!PS-Adobe-3.1" at first, then the code of each 
option, and after that simply the PDF? Or how does it work?

> BTW, for the release after this one we're planning to implement 
> end-to-end ICC-based colour correction. Is there a PPD method for 
> describing the printer's with an ICC output profile?

See

http://www.cups.org/documentation.php/spec-ppd.html

section "Color Profiles", keyword "*cupsICCProfile".

    Till