<div class="gmail_quote">On Fri, May 15, 2009 at 9:11 PM, Hal V. Engel <span dir="ltr"><<a href="mailto:hvengel@astound.net">hvengel@astound.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">> Poppler doesn't support overprinting, so #27 and #28 fail.<br>
> I'm not sure poppler support spot color.<br>
<br>
</div></div>It appears that it does not.<br>
<div class="im"></div></blockquote><div><br></div><div>Xpdf/Poppler support spot colors by using the alternate value - which is correct.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Looking at the PDF specification I see that it is possible for the the<br></div>
dictionary for a Device* object to have a default color space specified. I<br>
don't know if the altona document has this but looking at the code it is clear<br>
that no attempt is made to get or use the default color space for the Device*<br>
objects. If it is in the document it should be used any time the Device*<br>
color space is not a match with the output device color space.<br></blockquote><div><br></div><div>Correct, DefaultXXX colors aren't well supported - but should be. Be aware that DefaultXXX colorspace can appear at any "rendering level" that has a resource dictionary, and that the proper "inheritance" of that value applies...</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Looking at the code it is always using INTENT_RELATIVE_COLORIMETRIC and there<br>
is no attempt to get the Intent from the dictionary in<br>
GfxICCBasedColorSpace::parse(). So the code is not parsing out the intent and<br>
using that to create the transforms. I had a look at the code but I was not<br>
able to get the Intent from the dictionary since I am not at all familiar with<br>
the code base. Perhaps someone who understands how the dictionary stuff<br>
works could take a look at adding this to GfxICCBasedColorSpace::parse().<br>
<div class="im"></div></blockquote><div><br></div><div>Intent can come from there places - the 'i' operator in the content stream, the /Intent key in an ExGState resource dictionary and the /Intent key on an Image XObject. You will need to correct handle all of these case to get intent correct - which may mean having to improve the graphic state stack since I don't recall if Xpdf/Poppler correctly save/restore the value.</div>
<div><br></div><div>Leonard </div></div>