Johan W. Elzenga wrote:
Joel wrote:
Johan W. Elzenga wrote:
I’m sorry, but that is nonsense. Most (but not all) web browsers do not
understand color spaces, so they interpret every image as if it was sRGB, even if the image is correctly profiled as AdobeRGB or any other
color space. That is why AdobeRGB on the web is not a good idea. It has
nothing to do with a limitation of displaying colors. If you use AdobeRGB (and your image is tagged), people who use Apple Safari will see the correct colors, because Safari is one of the few browsers which
does understand color profiles.
You said it! Wed browser can’t see all colors and that’s why it loves the
sRGB because it’s fewer color and it’s the reason why sRGB looks brighter/richer by web browser.
You still don’t understand. Web browsers can ‘see’ every color the image has. A color is just three numbers between zero and 255, no matter what color space you used. What (most) web browsers do not do however, is interpret these numbers correctly. They don’t know how to relate them against a known standard, a process called ‘color management’. That is completely different from ‘not seeing’ them.
I actually understand more than some people can Web can see more than 256 colors. Because it doesn’t doesn’t mean it ca’nt see color #256, but it can’t see some specific color
Example, you give it color # 3,000,001 through color # 3,000,010 but it can’t display all 10 color but may by #3,000,000,3 only. And #3,000.003 may look better than other 9 colors
Web has nothing to do with color management nor I said anything about color management. Or color management probably use for Printing and web browser doesn’t do the printing (it may send the printing command to printer but it doesn’t care what the printer does).
I don’t have any experience with Safari, but as long as it can benefit
from sRGB, Adobe RGB or whatever color space then sure it can display whatever the color space has to ofter. Same with printer, you may applying
some color the printer doesn’t have, so it may not print the exact color the
color space tells it to print.
The comparison is utterly flawed. A printer is a hardware device, capable of printing certain colors and not capable of printing other colors. Safari is software, so Safari doesn’t display anything itself. All it does is send the color numbers to the device that does the displaying: your monitor. The difference between Safari and a non-color managed browser is not that Safari can ‘display’ something the other browser can’t. It’s that Safari can correctly read and interpret color profiles, so it can use color management to correct the colors before it sends them to your monitor. The non-color managed browser can’t do that, so it sends the colors to your monitor unaltered. Because most monitors can only display sRGB, only an unaltered sRGB image will look more or less correct without color management. Wider color spaces will look washed out, because they are not corrected for the smaller color space of the monitor. However, if you used a wide gamut monitor, with a color gamut close to AdobeRGB, the result would be the opposite. AdobeRGB images would look fine, sRGB would become highly oversaturated.
The printer itself can’t print nothing, it’s no more than a piece of steal covered by plastic, and filled with ink. The printer just do what the software tells it to do, and the software can’t do by itself but sending the command to the driver, the driver works with whatever software (color space, color manmager whatever) to communicate with the printer, driver, color space and so on.
IOW, you try to correct thing I haven’t said a word about it/them yet. And if you have read me talking about color and printing, then you may have known that I know more than what I am saying here.
