RE: ensuring no conversion
RE: ensuring no conversion
- Subject: RE: ensuring no conversion
- From: Eric Chan <email@hidden>
- Date: Tue, 23 Dec 2008 06:17:18 -0800 (PST)
Tyler and Roger,
Unfortunately this is not a long-term solution. It assumes, for instance, that Apple will be substituting Generic RGB and Generic Gray as the default profile in case the printer driver does not register a profile. That is true for 10.5.x (Leopard) but will not be true of 10.6 (Snow Leopard), when Apple will switch to using sRGB as the default profile. As you know, sRGB uses a gamma encoding that is approximately 2.2, whereas Generic RGB & Generic Gray of 1.8 gamma encodings. Thus you would still need to provide users with system-specific information, e.g., "If you are on 10.5.x, do this ... and if you are on 10.6.x, do that ..."
The real solution is to get all the clients (i.e., printing applications and printer drivers) fully compliant with the latest Apple printing APIs so that users don't have to resort to these (fragile) workarounds. Some apps and drivers are already there, but others require an update.
Eric
> To me, any DeviceRGB_X to DeviceRGB_X should result in a
> null conversion. But is that always the case, provided a
> RelCol rendering intent? I can't say for sure but it seems
> the way to go. I agree.
>> If I have an RGB chart (or anything RGB I want to print
>> un-managed to consider raw output), if I assign "generic
>> RGB", have Photoshop manage colors, and then select
>> "generic RGB" again for output profile, can I force a
>> null conversion, and insure a tag OSX feels all warm and
>> fuzzy about passing on to printer drivers unaltered?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden