Prepressforums.com

frailer · #1 (**permalink**) 08-06-2007, 02:59 AM

Posting here because no Fuji header.
Incoming PDF. Has elongated "star" replacing letter 'A' in a heading. Checks out in Pitstop OK. Has graduated fill across it. [smaller vector star inside larger to give fill area. This is one of 4 pages going into PREPS for a 4-up. Imposed Postscript+watched folder PDF generated. Can use either in Fuji Celebrant RIP.
Said object still looks OK in imposed PDF. But...when PDF goes through RIP, star becomes "rasterised-looking" and faint.
Send PostScript to RIP and it retains vector characteristics and fill values. Can't find anything in RIP settings. This is a very rare event with an up-to-date RIP.
Acrobat 6. Distilling to 1.4/Acrobat 5 compatible. I'd be happy if someone just said: "Shit happens in the PDF world sometimes". But maybe someone has an idea. I'm jumpy cos I missed it before proof went out, [of course], but client picked up. Whew. This was the 3rd proof due to client-caused re-dos. One of THOSE jobs. And aren't they on the nose from when you first open 'em up!
BTW, is it looking easier to attach images in the new "blue" world? Would love a pointer on this.

almaink · #2 (**permalink**) 08-06-2007, 05:40 AM

Are you sure it's a " graduated fill"? Is it a spot or Process? I no longer write postscript here as I've found going straight to PDF gives a more accurate PDF.
Don't use Preps here but it may be the problem.

frailer · #3 (**permalink**) 08-06-2007, 11:47 AM

It's a process job. Will have time today to try some other routes. One is to export manual imposed PDF from Indy and see what happens. Could also try PDF in>PDF out in PREPS. Usually convert to PS in PREPS because of extra functionality in job marking. But I reckon it's problematic doing that because of random events like this. We got Dynastrip with Celebrant when we went CTP. Gotta try and get some skill in that. This could be the motivator.

frailer · #4 (**permalink**) 08-06-2007, 07:32 PM

Conversation with Fuji apps person today whilst on other matters...she suggests plain old corruption. A resave and bring in again may have fixed it. Guess it was pretty atypical, so she's prolly right.