After reading about CM (also on this forum) I am more confused than ever.

- Why are Web pictures limited to sRGB? Is that a limitation of the browser ?
- If so, is that the reason why colors and resolution look different in Frontpage
preview and IE7 ?
- I have prepared a file with different color blocks usinf Adobe PSE and I used discrete values for the colors. When I "measure" the fields in other tools I get similar values, but in some they are significantly changed (Bible). Is that a function of the colorspace used ?
- Does anybody know a free utility to (a) inspect which profile is attached to a file and/or (b) to "batch" change the profile.

Eli, you threw in so many questions... :) Let's try to narrow it down and take it slow...

-Web pictures have a limited colourspace taking into consideration that most browsers display images differently.

-If you're using FP actually, that shouldn't be the case... I wonder why.

-What kind of file are you measuring anyway?

-It's written in the exif of your image. You can still read this granting that you do not save your image for web or if you do not recopy your image and save it as a new file in PS.

HTH :)

Thanks Earl. I prepared two versions of the file TIF and JPG. I can send them if you want.

Thanks Earl. I prepared two versions of the file TIF and JPG. I can send them if you want.

No problem Eli... Fire away! :)

Hi Eli,

Thanks for joining the forum. I too had my problems with color management but it gets clearer and clearer everyday. Its not that color management is difficult because its not. What is difficult is color reproduction. The managing part is easy, its being able to reproduce the same color across different devices, outputs, media that is tricky.

I'll try to answer your questions as best as possible. Hopefully someone like Louie Aguinaldo catches on this thread.

1) The wed standard is sRGB. I can't remember why in particular but if you use Adobe RGB for web, your images will not look correct.
2) I'm not familiar with the workings of programs such as Front Page. However, if FP doesn't have color management functions such as Adobe, then that can be the reason why.
3) Your preparing blocks with similar value should read the same in other programs unless you Convert the numbers to a different color space. If you don't do any conversion and the numbers stay the same, they will all present different depending on the color space that the numbers are plotted to. For instance, lets take a RGB color of 150-1-1. This will be a medium dark red in Adobe RGB. But plot these same numbers to the sRGB space and the red will turn darker and a bit more muted. When the same numbers are mapped to a different color space the colors change.
The hard part here is being able to present the same red across different devices. Lets take 150-1-1 again in the Adobe RGB space. Will you see the same red in your monitor as I would? How about when you display your image on the web? Will it show the same red? Or how about when you decide to print yoiur image on paper? How do you print the same red as your monitor?

The management part is easy. Its the reproduction part that is difficult.

Hi Eli,
1) The wed standard is sRGB. I can't remember why in particular but if you use Adobe RGB for web, your images will not look correct.


Nick, I too have read almost everywhere that the web standard is sRGB. However what still boggles me is why non-ICC compliant browsers still cannot display sRGB images properly. IE, Firefox, and other Mozilla derivatives will always display images with less saturation compared to an ICC-compliant browser like Safari.

However what still boggles me is why non-ICC compliant browsers still cannot display sRGB images properly. IE, Firefox, and other Mozilla derivatives will always display images with less saturation compared to an ICC-compliant browser like Safari.

Some Points:
- The reason why Safari can display colours a bit more accurately is because it assumes your existing monitor profile when viewing images which are untagged or saved for the web; as opposed to other browsers which some inherently do not manage colour profiles or you still need to activate this option within it...

- There is always abit of confusion with regards to images with embedded ICC profiles, not being viewed correctly in browsers... One should make sure in the output process that if you intend to display your image in sRGB; you have to convert your image to sRGB and NOT just assign it with the sRGB profile. The effects of this is very obvious the image's hue and saturation. :) Like the one you pointed out...

- Colour Management can be simplified as the congruent relationship between Sourcespace; Monitor RGB and Target Space... SourceSpace is Converted into MonitorRGB and PROOFed accurately on screen (Like when you manage your photos within applications like PS which does this by default). Then, SourceSpace is Converted into the TargetSpace and PROOFed accurately on paper.

HTH :Grin:

Thanks Earl. I guess I am just peeved that browsers other than Safari are not using current monitor profiles.

Thanks Earl. I guess I am just peeved that browsers other than Safari are not using current monitor profiles.

You're welcome Nono. Glad to be of assistance. :)