[Openicc] Printing Plans GhostScript

[Kai-Uwe Behrmann]

Am 02.03.11, 13:25 -0700 schrieb Chris Murphy:
> On Mar 2, 2011, at 12:58 PM, Kai-Uwe Behrmann wrote:
>> Am 02.03.11, 10:53 -0700 schrieb Chris Murphy:
>>> On Mar 1, 2011, at 11:19 PM, Kai-Uwe Behrmann wrote:
>>>> Am 01.03.2011 23:52, schrieb Gerhard Fuernkranz:
>>>>> Am 01.03.2011 22:14, schrieb Kai-Uwe Behrmann:
>>>>>> Retargeting is a special feature. It makes sense to retarget
>>>>>> automatical if the DeviceXXX color space does not match. For instance
>>>>>> a DeviceCMYK PDF sent to a DeviceRGB device should be converted using
>>>>>> the OutputIntent. The same for displaying DeviceCMYK on the screen.
>>>>>> This was mentioned previously here on list. That seems easy to agree
>>>>>> about.
>>>>>>
>>>>>> A DeviceRGB sent to a RGB device should not be changed automatical IMO.
>>>>> Well, I'm not sure whether users would understand why their untagged
>>>>> sRGB documents are printed nicely on a CMYK printer, while the same
>>>>> documents are printed with wrong colors on a printer which happens to
>>>>> have a RGB ProcessColorModel, although they have profiled the RGB
>>>>> printer as well.
>>>>
>>>> agreed
>>>>
>>>> Please let me correct my sentence:
>>>> A DeviceRGB + OutputIntent sent to a RGB device should not be changed
>>>> automatical IMO.
>>>>
>>>> And sorry for the confusion.
>>>
>>> OK well, what about PostScript which doesn't have OutputIntent?
>>
>> pstopdf? and than its PDF.
>
> Yes but once it's at pstopdf it's already separated from the application 
> and the CPD, there's no way to know/communicate what the user intention 
> is: /Device = sRGB, or /Device = /Device.

Ah, I see. But if I read Till correctly the prefered Linux printing format 
is PDF. So PostScript might not play that important role any more and we 
do not need to suggest it to calibration software and early colour binding 
print file creators. If you had a actual example I might get a better idea 
what makes your concern around PostScript. Are you afraid that existing 
workflows and devices will somehow break?

> For PDF that outputintent is inserted by either the application or CPD 
> or whatever writes the PDF in the first place, well before it gets to 
> pdftopdf or pdftoraster. Once CUPS has it, the intention needs to be 
> communicated in the file.

Yes, thats the idea. And its based on PDF right from the beginning.

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