Skip to main content
Participant
January 23, 2007
Question

TPS file is not deleted after FrameMaker creates PDFs via Acrobat 8

  • January 23, 2007
  • 24 replies
  • 6190 views
Using FrameMaker 7.2 build 158, and Adobe Acrobat 8, when creating PDF files, the temporary PostScript file (*.tps), which is created before the final PDF, is not deleted after the creation of the PDF is complete.

This is a big deal for us because we are using a tool which hooks into the PDF-creation of FrameMaker/Distiller, and is reliant on this TPS file being deleted.

Is this a known bug? Does Adobe know about this? Do any other users have workarounds for this?
    This topic has been closed for replies.

    24 replies

    January 25, 2007
    Jonathan:

    In Acrobat Distiller, see if in "File > Preferences" there is a "Delete Log files for successful jobs" checkbox...(?)

    Cheers & hope this helps,
    Riley
    Inspiring
    January 25, 2007
    Jonathan,

    Save As PDF isn't a recommended way to go, apparently because it has a few quirks. Might try using the Adobe PDF logical printer and printing to that instead.

    Also, there's something in the back of my mind that's half remembering that the TPS files don't get wiped if the distillation process aborts or fails. If you're really into tracking down the problem, you may want to look at the Distiller logs to see if you can correlate the leftover TPS files to failures...

    Art
    Participant
    January 25, 2007
    Hi Art,

    Well, the TPS seems to be left behind only occasionnaly when using Save as PDF directly from FrameMaker.

    Our bigger problem is that we are using the SDK in a propriety program our company coded to hook into FrameMaker and created PDFs through Distiller in an automated fasion.

    The TPS problem shows up consistenly using this method. I guess it is more of an SDK thing, however as mentionned, I did notice left over TPS files occasionnaly using the standard Save as PDF method in Frame.

    Somehow the switch from Acrobat 7 to Acrobat 8 has caused the TPS not to be deleted using our propriety program. Looks like our programmer may have to dig into the code to figure out where the problem is being caused. We figured it is a FrameMaker bug, but only those using plugins may discover it, therefore we may have to code a workaround.

    Thanks for the help anyhow.
    Inspiring
    January 23, 2007
    I have exactly the same setup, but there isn't a TPS left behind.

    What is your process for distilling?

    Art