Richard Man wrote:
> For web and printing, you MUST convert to sRGB, not Adobe RGB.
MUST? Weeeellll, not quite.
For the web, Safari and IE are color aware, and will correctly interpret
and display files with embedded aRGB profiles. FireFox doesn't do that
by default, but is easy to switch. And there ARE differences for some
colors.
For printing, most inkjets are actually CYMK internally. Either color
aware apps like PS or the printer driver are perfectly capable of doing
the necessary conversion to print from an aRGB file. The dedicated
printer driver or RIP will likely do a better job working directly from
aRGB, if that's what you have, than letting your editor do the aRGB to
sRGB conversion.
Most commercial labe doing laser prints will accept either, and do their
own conversion. They may advise that you do your own conversion and
proofing to retain the most complete control over the results.
> The usual workflow recommendation is to work in Adobe RGB and convert at the
> end, but some people just stay with sRGB throughout. It makes the most
> difference if you do do lots of color manipulations.
>
Or if your source file is aRGB. The issues around color space can be
pretty complex.
Moose
--
_________________________________________________________________
Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
Archives: http://lists.thomasclausen.net/mailman/private/olympus/
Themed Olympus Photo Exhibition: http://www.tope.nl/
|