Re: Safari color management
Re: Safari color management
- Subject: Re: Safari color management
- From: Roger Howard <email@hidden>
- Date: Thu, 4 Nov 2004 11:18:03 -0800
On Nov 4, 2004, at 11:09 AM, Roger Breton wrote:
Thank you Roger. Your account makes 100% sense to me. And I don't mind
what
Safari does presently in the interest of performance. *BUT* I'd like
to have
it as a preference: please, please, Mr. Steve Jobs, add in a small
ColorSync
section in Safari's preferences to let me choose how I want Safari to
handle
the display of untagged RGB (and why not CMYK too) images to my
display! Let
me be the judge of performance. I sort of find fishy the argument that,
somehow, color managing images to the screen is a performance hit in
OSX?
When we have Gworld going on at the system level and plenty of CPU
power in
IBM G5 processors.
Not everyone who uses Safari has a G5. Heck, I don't. Besides, again,
as I believe Microsoft discovered, that kind of choice is not
necessarily a good thing in a browser; in fact, Safari is NOT designed
to be all things to all people (OmniWeb or Opera is a better choice if
you want tons of options). As such, I think the current model of color
handling in Safari is correct, as far as you can ever be correct when
dealing with untagged images.
Let me ask - if you could define a default space for all untagged
images besides monitor space, then you'd also expect that to apply to
HTML colors right? How about colors in a Flash movie? What about
Quicktime movies? The problem is, designers match raw RGB values in
images to other elements in a page - if you try to color manage
untagged images, you really have to color manage everything, or your
seamless blending from JPEG to HTML table backgrounds to Flash marquee
will look like crud on a Mac - and that is where performance will
become a problem, I'd guess.
Ideally, I'd love to see all of it managed; I think all elements on a
page should be assumed to be sRGB - per the W3C; but until that can
happen, then I think the best tactic is to avoid the disjunction
between untagged image, HTML, and plugin colors by treating them all as
monitor space. I think a better solution for today would be Apple
encouraging Mac folks to drop the Macs = 1.8, PC = 2.2 argument, and
encourage regular users to work in a 2.2 space. That would go a longer
way towards getting a match with our PC friends than would a flakey
browser color management policy.
-R
_______________________________________________
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