<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 22, 2010, at 12:46 AM, Richard Hughes wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">2010/1/21 Jon Cruz <<a href="mailto:jon@joncruz.org">jon@joncruz.org</a>>:<br><blockquote type="cite">So, does the W3C position of defaulting to sRGB come into play?<br></blockquote><br>Quite often. If the image doesn't have an embedded profile, then we<br>treat it as sRGB. If there is no output profile, then we treat it as<br>sRGB also. If we're doing sRGB -> sRGB then it's a NOP.<br><br>If you do gtk_color_transform_pixbuf_in_place (profile, NULL) then the<br>NULL implies sRGB, as it's such a common space.</span></blockquote></div><br><div>Uh oh... that sounds like doing color adjustment in several disjoint passes. That would be bad. Very different from "everything coming in gets converted to sRGB then we leave them alone."</div></body></html>