WOW! Did they use every font in existence, or what?

Quote from: DigitalCrapShoveler on November 06, 2014, 05:13:52 PMWOW! Did they use every font in existence, or what?

Yes and I think they made some new ones of their own.

When do you get the error in Prinergy?

Not sure. It isn't my job. It's just my job to fix it.

I'm well into trapping and no error on fonts yet.

Quote from: DigitalCrapShoveler on November 06, 2014, 05:22:29 PMI'm well into trapping and no error on fonts yet.

The first time they tried running it they started it at 12:47 and the errors started popping up at 1:30 ish.

Quote from: Joe on November 06, 2014, 05:26:31 PM

Quote from: DigitalCrapShoveler on November 06, 2014, 05:22:29 PMI'm well into trapping and no error on fonts yet.

The first time they tried running it they started it at 12:47 and the errors started popping up at 1:30 ish.

I'm getting that error now as well. It's happening on traps.

Quote from: DigitalCrapShoveler on November 06, 2014, 05:29:32 PM

Quote from: Joe on November 06, 2014, 05:26:31 PM

Quote from: DigitalCrapShoveler on November 06, 2014, 05:22:29 PMI'm well into trapping and no error on fonts yet.

The first time they tried running it they started it at 12:47 and the errors started popping up at 1:30 ish.

I'm getting that error now as well. It's happening on traps.

Kodak half-assed explained what is happening the last time we did a job for this customer. They say one process is trying to access a page while another process is still accessing it...both at the same time which is a programming no-no. Sounds like faulty coding to me but all they offered was to try splitting the file into single pages and run it through which I am going to try shortly.

Oh and they also blamed it on the font licensing issue.

Quote from: Joe on November 06, 2014, 05:34:41 PM

Quote from: DigitalCrapShoveler on November 06, 2014, 05:29:32 PM

Quote from: Joe on November 06, 2014, 05:26:31 PM

Quote from: DigitalCrapShoveler on November 06, 2014, 05:22:29 PMI'm well into trapping and no error on fonts yet.

The first time they tried running it they started it at 12:47 and the errors started popping up at 1:30 ish.

I'm getting that error now as well. It's happening on traps.

Kodak half-assed explained what is happening the last time we did a job for this customer. They say one process is trying to access a page while another process is still accessing it...both at the same time which is a programming no-no. Sounds like faulty coding to me but all they offered was to try splitting the file into single pages and run it through which I am going to try shortly.

Oh and they also blamed it on the font licensing issue.

I'm trying some shit as well. We'll figure it out.

So I take the 356 mb PDF and extract all 232 pages and it gives me 5.31 GB of single page PDF's.

Quote from: Joe on November 06, 2014, 05:54:42 PMSo I take the 356 mb PDF and extract all 232 pages and it gives me 5.31 GB of single page PDF's.

Probably due to the 99,000 fonts they used.

I'm still getting the same errors with single pages. Surely Kodak didn't mean to process them one at a time???

So two of the pages that failed...I went backed and processed those two again individually and they went through. That is messed up Kodak.

But....

We only see these issues with this one customer though so Kodak probably isn't to blame.

Pages 1-100 go through okay. No problemo minus the low rez shit.

Page 140 is BAD NEWS.