<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On Feb 8, 2011, at 1:25 PM, Hal V. Engel wrote:</div><div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Verdana; 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; font-size: medium; "><span class="Apple-style-span" style="font-family: 'DejaVu Sans'; font-size: 16px; "><pre style="margin-top: 0px; margin-bottom: 12px; margin-left: 0px; margin-right: 0px; text-indent: 0px; "><span style="font-family: 'dejavu sans'; ">So it appears </span></pre><pre style="margin-top: 0px; margin-bottom: 12px; margin-left: 0px; margin-right: 0px; text-indent: 0px; "><span style="font-family: 'dejavu sans'; ">that poppler currently always does relative colormetric intent regardless of what intents </span></pre><pre style="margin-top: 0px; margin-bottom: 12px; margin-left: 0px; margin-right: 0px; text-indent: 0px; "><span style="font-family: 'dejavu sans'; ">in coded into the PDF file for it's objects. I can live with this for initial testing of the </span></pre><pre style="margin-top: 0px; margin-bottom: 12px; margin-left: 0px; margin-right: 0px; text-indent: 0px; "><span style="font-family: 'dejavu sans'; ">workflow but it does need to be fixed before this is considered production. </span></pre></span></span></blockquote></div>Agreed. And it is a little dicey to sort out, we need to keep in mind the failure of color management with PNG before ICC was included in the spec. And the failure was two part, but in my view primarily one and that was the viewer. Some applications would include incorrect metadata (cHRM and gAMA chunks), and any application that honored them would display the PNG incorrectly. So those viewers, since they were blamed, would ignore cHRM and gAMA. The result is that cHRM and gAMA were considered unreliable and now no one honors them, that I know of and they probably shouldn't at this point.<div><br></div><div>If interpreters for PDF take this path, and ignore the intent in the PDF in the first transformation, we will create interoperability problems and reduce the reliability of the intent. So if the intent is present, it should be used. There is a default intent if it's not present, and I think that's RelCol without BPC which is really not good. But I hope I'm wrong and it's perceptual.</div><div><br></div><div>Chris Murphy</div></body></html>