Re: untagged RGB data
Re: untagged RGB data
- Subject: Re: untagged RGB data
- From: John Zimmerer <email@hidden>
- Date: Fri, 19 Dec 2003 15:10:24 -0800
On Dec 19, 2003, at 2:37 PM, Chris Murphy wrote:
On Dec 19, 2003, at 1:24 PM, John Zimmerer wrote:
The confusion is around the reason for having the ColorSync
preferences. Theses were never meant to be more than default
application preferences, not system preferences. That's one reason we
moved them to the ColorSync Utility. In other words, it has always
been
up to the individual applications to look to these "default" profiles.
That's been my understanding since OS 9 as well. But somewhere, around
10.1 I think, the description of these settings quite literally states
they WILL BE USED for documents that don't contain embedded profiles.
That's what changed, and that's what has changed people's perception
of these settings and why they wonder why they don't do anything. If
that description just went away, I don't think anything else needs to
be in its place. RGB Default would be set to sRGB and not changeable
(for reasons you bring up, about the possibility a user would select
something that would hose the entire OS), but still visible so people
can see the RGB Default is sRGB. CMYK Default setting becomes the
profile used as the "Quartz Default CMYK" for untagged CMYK object.
Application specific settings always override operating system
settings. The OS settings are fall backs only.
I see the (potential) confusion, giving the wording in the UI, and even
in the Help. I can address the help, but we'll have to tackle the UI in
user education until the next release.
I'm going to start another thread on using sRGB as the system default.
Reasonable or have I missed something obvious that could cause a
problem?
Seems to me that this issue goes away if we remove the ColorSync
preferences altogether.
For RGB yes. Maybe grayscale also (I'm on the fence on that). But for
CMYK, a user selectable option for how the OS will treat untagged CMYK
I think is necessary because tagged CMYK, unlike tagged RGB, can be
undesirable (sometimes very undesirable).
The Generic CMYK Profile is based on SWOP TR001, probably the CMYK
equivalent to sRGB, so it's not such a bad default.
I'm not sure I buy the need for "OS working spaces", since I truly
believe all data should be tagged. And ultimately, this is the domain
of the user space applications (including AppleScript and sips), since
they manipulate color directly. The OS should simply render source
color accurately, and have a single definition (across workflows and
continents) of how untagged source data is treated, per color space.
JZ
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.