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

    _
    _krygny_
    Participant
    February 27, 2008
    Thanks for the info, Arnis.

    I found the problem. Somehow I introduced a comma (,) into the pathname of the directory. Even smart people do dumb things.
    _
    _krygny_
    Participant
    February 27, 2008
    >Save as PDF is needed when dealing with cross-referenced books.
    >All the books need to be open in FM and saved as PDF or you can end up with bad links.

    Yes, printing to PDF is not an option for books.

    This problem just started allofasudden - Frame 7.2p158 and Acrobat Distiller 7.0.7

    Distiller cannot open the tps file and leaves behind a *.tpdf file. Changing the extension to .pdf, it opens and appears unchanged from the previous issue.

    Everything worked fine yesterday. Today, it doesn't.
    Arnis Gubins
    Arnis Gubins
    Inspiring
    February 27, 2008
    Printing (a book) to PDF is ALWAYS an option - you just have to do it
    properly.

    First make certain that all of your book component files are open
    (Shift + File > Open from the book file does this in one go).

    In the print window, select the AdobePDF printer instance and make
    sure that the output sheet size is what you want. If you're creating
    online PDFs, then set the Generate Acrobat Data option. Next, set the
    print to file check-box and let 'er rip. Once you have the postscript
    file, run this through Distiller (unless you've set-up watched
    folders, which makes this step superfluous) using the appropriate
    joboptions for the type of output required.

    Save As PDF is a background process that does these same steps for
    you, but it does trip up for any number of reasons and you often don't
    get to see any log files that might give you a clue as to what
    happened.
    _
    _Christophe_WERMELINGER_
    Participant
    September 12, 2007
    Well, I use Frame 7.2b144, Acrobat 7.0 (standard) and Distiller 7.0.

    I have the same problem of tps files left behind after having "save as PDF" from Frame.
    But this does not happen all the times and I have no explanation.

    I remember that in former version of Acrobat/Distiller, preferences menu allows the user to chose to delete or not tps files. With recent Acrobat/Distiller, this choice has disappeared (only remains the choice to delete or not log files).

    The point is not to chose between two way of creating PDF file ("print" or "save as") : there is a bug with Frame and/or Acrobat and Adobe shall solve it !

    Regards
    _
    _registration_stinks_
    Participant
    August 31, 2007
    Save as PDF is needed when dealing with cross-referenced books.

    All the books need to be open in FM and saved as PDF or you can end up with bad links.
    R
    Rob from Mustang land
    Participating Frequently
    June 7, 2007
    Hi Guys:
    maybe my experience can eliminate the Acrobat 7, 8 diagnostic issue. I do not own either 7 or 8, but am having *occasional* failures in "save as" in FM 7.2 build 158. By failures I mean pretty substantial crashes with the .tps file being left behind as debris.

    I have had a flawless performance from FM 7.2 in "save as" pdf until I installed the 158 patch. This could be coincidence but much more likely to be ignorance. I do not have a clue what goes wrong and am busy .MF'ing all the relevant files and trying again and again and again.
    Down with all old wive's tales [spouses' tales?]let's sort this out
    someone must know.

    Rob Shell
    _
    _sherman_watstein_
    Participating Frequently
    June 6, 2007
    Does this mean we can again print to a PS file and distill will work?
    Arnis Gubins
    Arnis Gubins
    Inspiring
    June 6, 2007
    Sherman,

    That's always worked. What's happened with the 8.1 Distiller is that
    the default mode will no longer allow the postscript file being
    distilled to access other external files (TimeSavers pulls in other
    .ps files to do its magic stuff). One needs to configure Distiller to
    start with the -F switch, which can't be done using Save As PDF (it
    always calls Distiller without the switch).
    _
    _Jeanie_Shoemaker_
    Participating Frequently
    June 6, 2007
    I just saw this from Shlomo Perets at www.Microtype.com:
    "...once Acrobat/Distiller is upgraded to 8.1, "Save as PDF" won't work with TimeSavers settings, until a future version of FrameMaker will modify the "Save as PDF" function so that it triggers Distiller with the -F flag (so that it is capable of processing external files).
    Obviously, you'll have to contact Adobe representatives with questions as to future FrameMaker versions and their "Save as PDF" capabilities."

    Jeanie
    _
    _Mark_Lehmann_
    Participant
    June 6, 2007
    No improvement after installing today's 8.1.0 patch. (Still have the TPS problem and "File cannot be found. Unable to open..." message.)
    Anyone else tried the patch yet?
    _
    _Mark_Lehmann_
    Participant
    May 16, 2007
    For what it's worth:
    I've been using "Save As PDF" in FrameMaker 7.0p578 with Distiller 6 & 7 and Acrobat 6 & 7 to create PDFs every day for years, and all has worked beautifully.
    But a few days ago I upgraded to Distiller 8 and Acrobat 8 and am now getting the TPS problem and "File cannot be found. Unable to open..." message in Acrobat EVERY TIME.
    _
    _david1
    Known Participant
    May 1, 2007
    Argh, these endless old-wives' tales about "Save as PDF" vs "Printing to Adobe PDF and then distilling" -
    the former route isn't deprecated in the FrameMaker user docs (infact, it's the suggested route).
    If it doesn't work properly, why is it in the application at all?
    What does it do differently to printing anyways? (since both routes proceed via an intermediate PostScript file, then invoke Distiller - Frame doesn't create PDF natively the way InDesign or Illustrator do).
    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