OK, so to summarize:
- You print (presumably from MS-Word or something similar) to the PlanetPress Printer Driver.
- You capture that spool file with the WinQueue Input to convert it to PDF.
- Then you use that PDF as the Data File to feed to a PlanetPress Template that produces the PS file to send to Uniflow.
Given this, note that we have no control on how the RTF gets printed to the PlanetPress Printer Driver: the application that prints issues commands that the driver converts to PS. So depending on how many, and what type of commands the application issues, the resulting PS file can be very large. The Winqueue input then converts that PS file into a PDF (which is much smaller) but eventually, when it all gets sent again to Uniflow, the PDF gets reconverted back to PS, so we're still dealing with the same kind of PS code that was originally generated by the application/driver.
All in all, this is pretty standard stuff. I don't believe the 940Kb size of the final file is an issue: try loading the PDF received from the WinQueue input into Acrobat and selecting the Save As PS (or Save as EPS) option and you'll likely get a resulting file with the same kind of size (if not larger). PostScript is much more verbose than RTF, especially when converted from PDF.
_________________________
Technical Product Manager
I don't want to achieve immortality through my work; I want to achieve immortality through not dying - Woody Allen