Skip to main content
_
_Jonathan_Wexler_
Participant
January 23, 2007
Question

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

  • January 23, 2007
  • 24 replies
  • 6157 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

    Show previous replies
    _
    _Cheryl_Bowsher_
    Participant
    April 30, 2007
    I have had these exact same problems. It seemed to start when we upgraded to Acrobat 8 (from Acrobat 7). Using the info in this thread, I am now printing to Adobe PDF and then using Distiller to create the .pdf from the .ps file. It's an extra step but it works.

    Thanks!
    _
    _david1
    Known Participant
    April 25, 2007
    I've noticed the exact same messiness with .TPS files when making PDF's from Frame7.2 with Acrobat 8 - the resulting PDF also never opens in Acrobat automatically either.
    _
    _Kevin_Oblack_
    Participant
    April 20, 2007
    I have the same problem when using FM 7.2 build 158 and Acrobat 8 after using the Save As option in FM to save as PDF. The temporary files .tps and .tpdf are left in the folder. This is a huge issue when dealing with multiple manuals/books. I gained back over 40GB of memory after going through and deleting these two temporary files. Any know fix for automatically deleting the .tps and .tpdf files???
    _
    _Andy_Cromarty_
    Participating Frequently
    February 15, 2007
    Sorry, this appears to make no difference :-(
    _
    _Andy_Cromarty_
    Participating Frequently
    February 15, 2007
    I had the same problem after upgrading to Acrobat 8.0.
    Check your Distiller preferences (open Distiller and select File->Preferences). There are options here to select whether or not the log files are deleted for successful jobs.
    _
    _Tokend_
    Participant
    February 12, 2007
    Jonathan,

    It's obvious what is happening. TPS reports are now mandatory.

    "So, Peter, what's happening? Aahh, now, are you going to go ahead and have those TPS reports for us this afternoon?"

    --Bill Lumbergh, from the movie Office Space

    Ken

    (Sorry. Couldn't resist)
    _
    _thomas_bro_
    Known Participant
    February 10, 2007
    Arnis,

    Thanks, and:
    " ..So far, manually printing to a ps file and distilling always seems to work without any issues..."

    which is always the since Adobe invented Acrobat as a 'substitute' for PRINTING.

    I do know what you mean, I I too have impressions and experiencenses of exactly the opposite when I look into your comments. The PS might be smaller then the TPS, fonts drop out when distilling the PS file, PS can be slower (partiucularly if there are a lot of tables in the FM files)

    keep smiling
    thomas
    _
    _thomas_bro_
    Known Participant
    February 9, 2007
    Save As PDF isn't a recommended way to go, apparently because it has a few quirks

    Art, can you point out which quirks. It would be interesting to know. To my knowledge the Save As command invokes the AdobePDF printer anyway (same as print), create a PostScript file (that happens to be called TPS instead of PS, and should be deleted. And finally starts Distiller.

    keep smiling
    thomas
    Arnis Gubins
    Arnis Gubins
    Inspiring
    February 10, 2007
    Thomas,

    FWIW, speaking from experience with the Save As route, I've seen
    random "phunnies" in the final PDFs (such as the missing fonts
    issues), a bigger .tps file than the .ps file generated from directly
    printing to file, slower throughput in both the intermediate
    postscript file creation and actual distilling (probably tied in to
    the larger .tps file) and other differences from what the joboptions
    should have been.

    There should not have been any differences in the file sizes being
    created if the same printer instance/configuration was actually being
    used. I also see this on some automated runs with Miramo. It's not
    consistent either - sometimes it works fine and then the next run, the
    process is considerably slower and there are dropouts in the PDFs.

    So far, manually printing to a ps file and distilling always seems to
    work without any issues.

    Your mileage may vary.

    Arnis
    A
    Art Campbell
    Inspiring
    February 9, 2007
    John,

    I think Riley was pointing out that when it (the Delete Log Files checkbox) is checked, then any log files you find would be for unsuccessful jobs, which could be linked to your left-behind .TPS files.

    If the TPS file for a given job is delted, it is probably because the job completed without errors.

    So if you have log files, you also have clues...

    Art
    _
    _Jonathan_Wexler_Author
    Participant
    February 9, 2007
    Log files have nothing to do with the TPS files...
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices