[Openicc] Printing Plans GhostScript

[Kai-Uwe Behrmann]

Am 03.03.11, 00:42 +0100 schrieb Gerhard Fuernkranz:
> Am 03.03.2011 00:06, schrieb Chris Murphy:
>> I think the print pipeline can and should handle all PDF.
>
> And if this is granted, then you get PostScript printing almost for free
> as well (either with an additional PS to PDF pre-filter, or by directly
> feeding PS instead of PDF into a ghostscript-based ...toRaster filter).
>
> The more special case is IMO PDF with OutputIntent. I'm not sure,
> whether an OutputIntent (if present in the PDF) would be honored and
> assumes as DefaultXXX color space by ghostscript. So either the
> ...toRaster filter would need to extract the OutputIntent and pass it to
> ghostscript as DefaultXXX, or ghostscript would need to be enhanced so
> that it (optionally?) honors the OutputIntent, overriding the built-in
> DefaultXXX and the DefaultXXX given on the command line with the
> OutputIntent color space.

The interpretation of a standard PDF feature like the OutputIntent should 
IMO not be optional. If the OutputIntent is to be ignored than that is 
already data manipulation and can not easily be part of a standard conform 
data flow. Irgnoring the OutputIntent is comparable to strip a ICC profile 
from a AdobeRGB Jpeg.

> Michael, maybe you can comment whether and how ghostscript honors an
> OutputIntent present in a PDF?

Michael Vrhel wrote on 1. March [1]:
> We are adding in the proper required support for the output rendering 
> intent right now.  It will probably be in the trunk within the next 
> month.


kind regards
Kai-Uwe Behrmann
-- 
developing for colour management 
www.behrmann.name + www.oyranos.org


[1] http://lists.freedesktop.org/archives/openicc/2011q1/003188.html