TRY TO PREFLIGHT THIS !!

[Dario]

Hi Folks!
Here are some "white" elements on a black background.
If you open the PDF using OsX Preview then you can see them, otherwise not.
But they are not the usual "white overprint"!
I can't figure out how they are made!
How about you?

 

[Ulrich]

the in Acrobat non visible elements mode is DeviceN, but the name of the DeviceN-color is "None" (in German: "Nicht drucken")

I am not 100% for sure, but if that alone does not force a disregard by previewing a RIP, i guess, that (the name "None") causes a mapping into the mode separation color (e.g. "All" is mode Separation color also...).

But "None" should expressly declared not to be reckognized by any RIP or professionel Preview interpreter like AcrobatPro and should expressivly not to be printed...

Remember e.g. a DeviceN-Cyan-object (mode DeviceN) in in a cmyk-file: you will not get a 5th separation/plate, it will be moved/mapped into the CMYK-mode/Separation-channel by RIPping...

But here it is "None"


May be someone had just called his own created spotcolor with that name or had klicked the None-filling in the color-palette, thinking that causes white/just not a filling or had changed it after export in PitStop or something else...

 

[abc]

What he said...
For the future you can preflight for a spot color called 'None' and although it's not in the output preview it will be flagged as an error.
It's mixed as Zero% CMYK
At least in PitStop, but I guess in others as well.

 

[abc]

BTW also just checked. The Ghent Workgroup preflight profiles (at least the 2015 ones) will flag this as an warning for overprinting white lineart.

 

[Macmann]

Just for kicks I opened the file in Esko PackEdge-the icons were filled with white-set to overprint. ¯\_(ツ)_/¯

 

[Gianni_S]

Curious,
looks like a custom spot color with no fill objects with a multiply transparency applied at 0%.
Callas Pdf Toolbox failed to detect and correct it.
Xitron rip rendered its black background only.
Xmf is still working on it… (35min)
Who is the criminal mind behind this file?

 

[Joe]

Pitstop shows it as DeviceN (Non-printing). Converting to CMYK makes it knockout white. OS X Preview will never display PDF's files transparency correctly. And as others have said pre-flight will flag it and correct it if you want to.

 

[chriscozi]

We always print 'None' ink.
Looks great on 'None' paper.
We get paid with 'None' money.
We end up with 'None' business.
More evil creation.

 

[Savage]

XMF preflight gives out an error that roughly translates to "White Vectors are not in knock out".

 

[Dario]

XMF preflight gives out an error that roughly translates to "White Vectors are not in knock out".

View attachment 290745

Hi savage,
could you show me how you set up that rule in Acrobat Preflight?
Mine says nothing, so I presume it'd be an easy fix.

 

[chriscozi]

Hi savage,
could you show me how you set up that rule in Acrobat Preflight?
Mine says nothing, so I presume it'd be an easy fix.

If you make a rule to spot this DON'T FIX IT until you know it SHOULD be fixed.
Sheesh.
'None' printing is HARD !

 

[Savage]

Hi savage,
could you show me how you set up that rule in Acrobat Preflight?
Mine says nothing, so I presume it'd be an easy fix.

Sorry, but it's not Acrobat Preflight that gives the error. It's Fujifilm's XMF which has Pitstop integrated and outputs the error on a PDF.
If you take a look at this screenshot, the error is reported by XMF and then it generates a PDF with the error report.
If Acrobar can do it, i don't know how.

 

[Puch]

Please see attachments for an Acrobat solution. Of course these profiles must be tested to avoid false positives.

 

[Dario]

...because we are so piss-poor we can't afford PitStop

 

[Dario]

Who is the criminal mind behind this file?

It came from InDesign and it's got "SONY" written on it

 

[abc]

I love this industry.

...because we are so piss-poor we can't afford PitStop

talk to me!

 

[keith1]

I see this sort of thing in PDF files from time to time. I've just considered it to be leftover objects from some past alteration in design from the customer (these are customer PDF's, not mine).
I've never given too much thought to how they would have accomplished this. That would give me a headache. Like wondering how people manage to make colossal 20MB PDF's out of a single page.
If I catch it I delete them. I'm sure some may have gotten through but they haven't created a problem that I'm aware of so it hasn't really been a concern.