Re: Panther, sRGB, web browsers
Re: Panther, sRGB, web browsers
- Subject: Re: Panther, sRGB, web browsers
- From: email@hidden
- Date: Fri, 19 Dec 2003 10:35:58 EST
In a message dated 12/18/03 3:12:43 PM, email@hidden writes:
>
>
I'm sorry, but this is insane. Assuming the display profile as source
>
virtually guarantees that the color will be displayed incorrectly
>
unless it was created in a non-color-managed application on that
>
machine. Moreover, since it's exactly the result you'd get with no
>
color management, it's just adding a layer of redundant options whose
>
only function is to confuse the user, and ensure that they get the
>
same dark muddy web images they've come to know and hate. Assuming
>
sRGB for untagged RGB would at least have given us a fighting chance
>
to display web images correctly. I really hope this changes in teh
>
future, because for now it's a completely useless behavior.
>
--
>
I think Bruce has stated pretty clearly what a number of us have been saying
less emphatically throughout this dialog. I'd like to bring up a whole series
of questions that I haven't heard asked by Apple, but that appear to very much
need asking:
How should a default RGB source profile be chosen, and what should the
default-default be? (Which has a pretty clearly been answered here that it should
not be hardwired, but user selectable, and that the default choice for it should
be sRGB.)
Should tagged document profiles be checked for, and used if present? (Simply
put: Yes)
Should printer settings be accessible at the driver level, instead of the
Colorsync Utility? (Yes, if practical; if not practical, then a button to launch
the utility, and an explanation of how and where to change settings needs to
be available in the ColorSync pane of the driver)
Should the ColorSync setting in the driver be grayed out when not active?
(Absolutely, if possible... if not possible then text explaining exactly what
conditions these conversions will, and will not, be triggered should be included
in the pane.)
Should the ColorSync filters include non-color management tricks? (It doesn't
make the purpose of color management any clearer when they do...)
Should ColorSync, given its limited controls and out of the workflow
location, be limited to optional functions, not critical core functions? (Absolutely;
existing and third party workflows need to function correctly no matter what
settings are selected, or not selected, in the ColorSync control panel)
What features are most needed to make ColorSync conversion a practical
workflow alternative? (Control of rendering intents comes to mind, better
documentation, better explanations right in the window where you need them, easier
access to the panel from the printing process, direct control of conversions so
that a conversion can be forced, from non-savvy applications if desired...)
I would suggest that others add items they have stumbled across, since this
appears to be the only mechanism for input into ColorSync development.
C David Tobie
Product Technology Manager
ColorVision Inc
email@hidden
www.colorvision.com
_______________________________________________
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.