Output intent ICC profile Xxxxx has the same name but is not equivalent

[macfocus]

Hi all,

I have multiple flow where we (Better said, our customers) preflight Press ready PDF files.
One of the checks is a validations for the correct ICC profile.

This works pretty OK, but on occasion I get the following error:

"Output intent ICC profile <Profile name is shown here> has the same name but is not equivalent"

What does this actually mean en more importantly, how to get around this issue?
The PDF seems to be fine and being created with/ using the correct ICC profile.

I use the Preflight option:
PDF standards- > ICC profile differs from: <Profile name is shown here>


Looking forwards to a hopefully correct answer.

Regards,

Arjen

[freddyp]

I have never seen this message. Can you share the file please.

I have a couple of ideas, but I do not want to give an incorrect answer

[macfocus]

I have never seen this message. Can you share the file please.

I have a couple of ideas, but I do not want to give an incorrect answer

Hi Freddy,

Please see the link below.
https://assets-p-publiqare.pqcloud.eu/?w=Kk8rawmAmM

Regards,

Arjen

[freddyp]

It was the idea at the top of my list, but Ben confirmed and clarified a few of the more in-depth aspects. Thanks for that!

When you create a profile (or action list for that matter) in which you use a resource (ICC profile, font, ...) that resource is embedded into the profile. So in your particular case the ICC profile with the output intent is embedded in your preflight profile.

When you check if the output intent of a PDF is different from "ISO Coated v2 300% (ECI)" then PitStop not only checks if the name of the ICC profile in your preflight profile is identical to that of the ICC profile in the PDF that is being checked, it also checks the ID (which is a checksum of the contents of the profile). In your case the names are identical, but the IDs are not.

In other words, the "ISO Coated v2 300% (ECI)" used by the person who sends you the PDFs is not the same one as the one that you use. This does not mean that the differences are important. As you wrote, the output seems to be correct, but they are not identical. They probably did not edit the ICC profile, so it must have come from a different source. The PDF was created with Adobe Indesign 17.3. Is it related to that version? Or did they download the profile from somewhere and are they using that version in the PDF export presets? That is for you to find out.

Conceptually you can solve it in two ways: you give your ICC profile to the person who is sending you those "bad" files, or you use their profile in your preflight profile that you then only use for them.

[macfocus]

Hi Freddy,

Thank you for the in-depth explanation.
I'll see if and how we can solve this issue in practice.

Kind regards,

Arjen

[macfocus]

Hi Freddy,

Question on this old topic.

Is it possible to just check on the ICC profile name in some way?
So, if name = identical = OK
If not identical = Not OK

Looking forward to your feedback.

Regards,
Arjen

[loicaigon]

Hi Arjen,

We do not check name = 'identical' for the very reasons Freddy provided. Imagine a ICC Profile whose name is the same but produces a complete different result? Would you be ok? Or even with the slightest deviation, wouldn't that be weird that two runs print different?

We might think of an option to only consider name, but I think that could be the pandora's box.

Feel free to share your thoughts,

Loic

[loicaigon]

There are two workarounds that you could investigate:

1) Gather info on the OutputIntent and generate a JSON or XML report


For example, the XML report would expose the following:

Code: Select all

<OutputIntentInfo>
    <DocumentOutputIntent type="GTS_PDFX">
      <Var name="Output condition identifier">Coated FOGRA39 (ISO 12647-2:2004)</Var>
      <Var name="Registry name">http://www.color.org</Var>
      <Var name="Additional information">Coated FOGRA39 (ISO 12647-2:2004)</Var>
      <Var name="Destination output profile">Coated FOGRA39 (ISO 12647-2:2004)</Var>
      <Var name="Destination output profile ID">74ff62f330bf0dbe4495b5720542d511</Var>
    </DocumentOutputIntent>
  </OutputIntentInfo>

That you could use after preflight to sort files based on whether the name is similar or not, independently of the profile internals.

2) Use FastLane to get info on the Output Intent before you run preflight

Then use FastLane Metadata to take actions



FastLane would be quick yet if you run a preflight anyway, it may not bring significant advantages here.