Re: Alternative to Pitstop?
Matt wrote +"The difficulty with SpeedFlow is that it is not (as best as I can remember) a native PDF editor and requires you to work the PDF outside of your workflow."+
I suppose it's important to understand the concept of "native PDF edtior". As far as I know, no application actually keeps a PDF as a PDF within the constraints of an application. Wether the file is opened in Acrobat, Pitstop, Speedflow Edit, etc, the file is seen in an application dependent internal structure. So when you open a PDF in Acrobat, it is not an PDF. It is the internal structure that Acrobat uses. If someone knows more info, I'd definitely be interested in knowing.
For me, "native PDF editor" indicates the file format is imported as a PDF and does not go through any intermediate file format. For example, a older rip which would go PDF -> PS -> 1-Bit Tiffs. A native PDF RIP could go directly from PDF --> 1-Bit Tiff.
With Speedflow Edit, the internal structure allows greater functionality that what can be found within a PDF. It allows us to do more with the file such as reflowing text from one page to another. When we write out a file, we write a completely new file instead of re-saving the original. All aspects of the PDF are "touched". This allows us full capabilities of going from one PDF version to another. A user can open a PDF 1.7 with layers and transparencies and if they want a PDF/X-1a 2001 for their workflow, SF Edit will write a brand new clean file according to the specification (PDF 1.3, CMYK, etc.). Neo, for example, can only save out a PDF in the version it came in as.
I guess the biggest question is what truelly defines a native PDF editor.
Regards,
Greg
Systems Engineer
OneVision, Inc.