[Openicc] Printing Plans GhostScript
Kai-Uwe Behrmann
ku.b at gmx.de
Tue Mar 1 14:06:55 PST 2011
Am 01.03.11, 22:14 +0100 schrieb Kai-Uwe Behrmann:
> Am 01.03.11, 09:47 -0800 schrieb Hal V. Engel:
>> On Tuesday, March 01, 2011 02:15:32 AM Kai-Uwe Behrmann wrote:
>>> Am 28.02.11, 22:09 -0800 schrieb Michael Vrhel:
>>>> The obvious example occurs if I have a document that has an RGB image and
>>>> a CMYK image and I am printing to a CMYK device. In this case, the RGB
>>>> image will have to be transformed in some manner. That transformation
>>>> is under your control by specifying the desired default RGB source
>>>> profile to use. For the CMYK image, if you did not want the data
>>>> touched, you should make sure that your default CMYK source profile is
>>>> the same as your destination profile. The CMYK data will then pass
>>>> through unmolested.
>>>
>>> Will adding a OutputIntent to a PDF/X (A/E) be honoured for DeviceXXX
>>> objects by Ghostscript? Leonard pointed this requirement out [1].
>>> It could then be used to pass through unmolested Cmyk or DeviceN to a
>>> according configured printer.
>>
>> Why not unmolested RGB and Gray as well? Any app that is smart enough to
>
> Oh, it was meant to be exclusive. Please read DeviceXXX.
Obviously only one is possible:
"Oh, it was meant to be non exclusive. Please read DeviceXXX."
Sorry.
kind regards
Kai-Uwe Behrmann
--
developing for colour management
www.behrmann.name + www.oyranos.org
More information about the openicc
mailing list