Michael Fontana
pro member
A post in the landscape-board rises the question, how CM savy/aware webbrowser like Safari or IE handle the untagged webjpg.
In my usual workflow, the tiffs were converted to sRGB, prior to be °saved for web°.
In the settings, I did through the profile away, so basically, this produced a untagged sRGB-jpg:
The browsers not beeing ICC-aware (like FireFox) display the image "normally"; this means it looks like the tiff in PS, within its working space.
For the ICC-aware browsers, we have two options:
A) The profile is added in °save for web° and the browser recognises the tag (sRGB), and shows therefore the image properly. Perfect!
B) Nativly this beeing a sRGB, but throwing the profile away, (screenshot above), the ICC-aware browsers doesn't know, what native colorspace it had and display it differently. This is correct on the CM-level, but bad for the viewer. "Nativ" means here not the workspace of the tiff; but the sRGB profile, beeing converted in, prior to be send to °sace for web°
So what colorspace does a ICC-aware browser displays, when it doesn't finds a profile?
Is it the monitor profile? This has been my first guess, but its not!
Any insights?
Maybe I should check the profile-box, to tag the jpg with the sRGB-profile; the °profile-through- away° might come from the days whit lowspeed modems. (??)
By adding the profile, the NON-ICC-aware browser will not recognise any profile, but as sRGB is the webstandart, it will show it properly. Is this correct?
Here the examples, one jpg is °saved to web° with the profile, the other one without.
In my usual workflow, the tiffs were converted to sRGB, prior to be °saved for web°.
In the settings, I did through the profile away, so basically, this produced a untagged sRGB-jpg:
The browsers not beeing ICC-aware (like FireFox) display the image "normally"; this means it looks like the tiff in PS, within its working space.
For the ICC-aware browsers, we have two options:
A) The profile is added in °save for web° and the browser recognises the tag (sRGB), and shows therefore the image properly. Perfect!
B) Nativly this beeing a sRGB, but throwing the profile away, (screenshot above), the ICC-aware browsers doesn't know, what native colorspace it had and display it differently. This is correct on the CM-level, but bad for the viewer. "Nativ" means here not the workspace of the tiff; but the sRGB profile, beeing converted in, prior to be send to °sace for web°
So what colorspace does a ICC-aware browser displays, when it doesn't finds a profile?
Is it the monitor profile? This has been my first guess, but its not!
Any insights?
Maybe I should check the profile-box, to tag the jpg with the sRGB-profile; the °profile-through- away° might come from the days whit lowspeed modems. (??)
By adding the profile, the NON-ICC-aware browser will not recognise any profile, but as sRGB is the webstandart, it will show it properly. Is this correct?
Here the examples, one jpg is °saved to web° with the profile, the other one without.