PE4: Using Save As... PDF

Hello:
I have loaded 3 jpg files in Elements. Is there a way I can have all three jpg photos saved into one PDF file? End result would be a 3 page PDF file.
Tony

>I was wondering about PSE 2 and the Mac versions - I think they have some kind of slideshow stuff.
This is not a problem for macs, since you can create a pdf from anything in the print dialog. In the case of non-slideshow files in PE it would make one-page pdfs, but there are a number of free utilities that will combine them into one, if needed.

Similar Messages

FAQ: Creating PDF Files from FrameMaker v.6 & earlier Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!

An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
GOOD NEWS
I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
DON'T USE "SAVE AS PDF"
But what's wrong with "save as PDF" as currently implemented?
The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
(1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
(2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
(3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
(4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
(5) Some or all text in the resultant PDF file cannot be searched or indexed.
(6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
(7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
(8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
(9) Some or all page content is missing (other than margin areas).
(10) Relatively inefficient PDF is generated.
If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
Whether the printer supports color (Acrobat Distiller does)
What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
Resident fonts (Acrobat Distiller doesn't really have resident fonts)
Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
DON'T USE PDFWRITER
The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
Case 3: Acrobat 3
Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
- Dov

You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

Using "Save as PDF" changes fonts

I have some documents in czech in FrameMaker 12. When I print to pdf the documents converts all right, but when using "save as pdf" all arial fonts are replaced with Times New Roman and the entire process seems to use a lot of time and computer memory. The Save as PDF always have been buggy, but some of my customers apparently seems to need this feature. How does one troubleshoot the strange behaviour of font replacement ?
Best regards
Bjørn

Usual suspects:
AdobePDF printer instance is not set as the default (use SetPrint utility available from http://sundorne.com/FrameMaker/Freeware/setPrint.htm).
Printer vs. soft fonts (i.e. installed fonts)
Are you using a codepage Arial font for Czech or a unicode enabled version?
Distiller joboptions - embed & subset all fonts; Cancel if embedding fails
Avoid CMYK option with OTF Pro and WGL-TT fonts unless you specifically are creating output for colour press work

"reference count underflow" printing NSDocument using "Save as PDF"

Hello, I'm getting a "reference count underflow" error trying to do a "Save as PDF" in a NSDocument class using the printOperationWithSettings method. There are no errors sending to the printer or viewing the output in preview. I found the post http://discussions.apple.com/thread.jspa?messageID=8708986&tstart=0 which was posted a year ago showing a 10 line program with the same error. I've got garbage collection turned on.
Is this still a know problem?
Thanks

Oh I do get the "reference count underflow" when compiling and running the above 10-line program.
If I create a new "Document-based" project and setting "Garbage Collection" to required, add an IBOutlet variable to reference the NSTextField generated, and add the following required method for printing:
- (NSPrintOperation *)printOperationWithSettings:(NSDictionary *)printSettings error:(NSError **)outError
NSPrintInfo *tempPrintInfo = [self printInfo];
if ([printSettings count]) {
tempPrintInfo = [[tempPrintInfo copy] autorelease];
[[tempPrintInfo dictionary] addEntriesFromDictionary:printSettings];
// textField is an IBOutlet variable
NSPrintOperation *op = [NSPrintOperation printOperationWithView:textField printInfo:tempPrintInfo];
return op;
I can print and "Open PDF in Preview" without errors, but get the "reference count underflow" with the "Save as PDF".
The sample application "SimpleStickies" created in 2009-10-14 and has by default Garbage Collection required, gets the same errors.
Is there a simple solution to creating a document-based project that allows "Save as PDF" to work.
This is a common function. I know I'm missing something obvious.
Thanks!

Save as PDF option in MS Word 2007 does not create TOC links

Hello All,
i am using Microsoft Office Word 2007 to create How to Guides, Installation Manuals, and other technical documents. I send these documents to customer in PDF format.
When i use "Save as PDF" option of MS Word 2007 to generate PDF file, it creates the PDF but without TOC links. TOC entries are there but hyperlinks are missing.
Can anyone please provide me a solution to work around this issue.
Thanks in Advance.
Anax Thomas
http://www.msentouragerecovery.com

Hi,
It seems that you are trying to insert a Hyperlink in you document which you want to save as a PDF file from Word 2007,
but when you open the PDF file there is no such a Hyperlink but only the website address.
If there is anything misunderstanding, please feel free to let me know.
Try this:
When you have inputted the website address, enter an “Space” or “Enter” behind it to make it
turn into a Hyperlink before you save the document into PDF file.
Sincerely,
Fangfang

Why won't Save as PDF work?

iPhoto hangs up on the first photo book page with an image containing a warning triangle if I try to use Save as PDF. Has anyone else had this happen? I presume it means that the image won't send to the printer, either? Yet, The Missing Manual says you can send photos with warning triangles and let them be printed blurry. Who knows about this? I'd appreciate real experience. Thanks.

Try previewing (and saving the PDF) using this method - http://support.apple.com/kb/HT1040
LN

Save as PDF changes file hyperlinks

I have a folder containing hundreds of PDF files and a single XLS sheet
as an Index containing hyperlinks to these files
and the hyperlinks in the XLS correctly call Adobe Reader direct.
For portability I decided to convert the XLS to another PDF.
This worked fine in Excel 2003 using the Adobe Add-In from Acrobat 8.1
But when I try the same process with Excel 2010 or 2013 using Save As PDF
I get security errors because the hyperlinks have been modified during the Save As,
The original hyperlinks in the XLS file have the form
file:///C:\..\..\...\a.pdf and this is retained in the 2003 conversion.
and the PDF version the loads the selected PDF directly.
After using Save As PDF in Excel 2010 or 2013 they take the form file:///C|/../../.../a.pdf
This causes the PDF to attempt launch IE and open the PDF in browser after 2 security warnings.
Note the slashes are reversed and the colon becomes a vertical bar.
How to I get the new version to behave like the original?
I am not sure if I have an Excel problem or a PDF problem.
Bill

Use the Adobe Add-In in Excel.

Can't Save As PDF in 7.2 after upgrade to 9.0

Hello again, Framers,
In 7.2 we routinely used Save As PDF without problem. Now that we also have FM 9 on our systems, however, it appears that the newer Distiller overwrote the older one (the one that worked well with 7.2) because now when trying to Save As PDF (in FM 7.2), we often have problems. It all seems very random and we are at a loss as to understand.what is happening, why, or how to fix it.
The symptom is a FrameMaker error saying "Can't launch Acrobat Distiller to create a PDF file."
Double-clicking acro.exe won't open Distiller -- nothing happens. (Can't open acrodist.exe or acrotray.exe under any circumstances.)
Printing to .ps and double-clicking the .ps file sometimes works, sometimes not.
Deleting the .tps files and others backups sometimes works, sometimes not.
Retrying Save As PDF multiple times sometimes works, sometimes not.
We three tech writers have similar setups: We're using XP, have all the latest FM patches, plenty of RAM, etc.
I hope the answer isn't "get rid of 7.2 and use only 9.0" -- our deadlines are such that it's hard to work only in the new version. The UI is different and some functionality is different, so the learning curve will take at least a bit of time.
Could it be as simple as having MIS re-install the 7.2 version of Distiller? Although we specifically requested they leave FrameMaker 7.2 when installing 9.0, we didn't think to mention Distiller, which was apparently overwritten.
If anyone has any experience with this issue, your advice is most welcome.
TIA,
Gay Alson

Thanks both Arnis and Mike --
Interesting suggestions from both of you.
Arnis, we're putting the cleanup utility on the back burner for the moment, since in our company, we can get in trouble using third-party software. However, it's good to know about this utility and we will use if it we have to. (Occcasionally we are forced to put our careers on the line for issues like this...)
Mike, we created a folder called "PDFSettings" in the 7.2 "fminit" folder and copied over the six joboptions files from 9.0. Rebooted, rePDFed and voila, that worked. (Mind you, we can't say for sure that's what worked, because as I said in my original post, the simple act of rebooting "sometimes works, sometimes not...")
Eventually this problem will go away by itself because eventually we will get rid of 7.2 -- it's only deadline time-crunches that have made us reluctant to jump fully-clothed into 9.0...
I really appreciate the two of you taking your time to offer suggestions and help. I can't imagine life in the FrameMaker world without you!
Cheers,
Gay

"Save as PDF" quit working in FM 9

I've been using Save As PDF to create PDFs of our books, and it's worked great. But yesterday, it stopped working. I probably did something or changed some setting, but I have no idea what it could be.
Now, when I click "Set" in the PDF Setup dialog box, FrameMaker quickly runs through the files in the book (the file names flash by in the lower left corner), but then it stops. Turns out, it also creates a .tps file of 0 size in the destination folder. There is no error message; it just stops.
I can still create PDFs with the Print function, but I'd really appreciate it if someone could help me get Save As PDF working again.
Thanks,
Chris

I have version 9.0p250 of FM. I also have Acrobat Pro with Distiller. They were installed together.
When Save as PDF was working, the Distiller always came up as a tab on the Task Bar. But it doesn't get that far anymore.
When I use the Print Book feature, the Distiller tab doesn't come up but I see the Distiller icon twirling in the system tray. I assume that's how Print Book is supposed to work.
Chris

Save as PDF generates SPLWOW64.EXE error

Just moved to new Windows 7 box
Using Frame v 8.0p236
Have book, used Save as PDF option, click "Set".
Get a popup box with big red "X" says: c:\windows\SPLWOW64.EXE
Ideas?
TIA,
Theresa

Stuck files in the queue sounds like a problem I had with Acrobat X. The
10.0.1 patch broke the Adobe PDF printer, so that it tried to use the
COM1: port, instead of the Documents or Desktop port. (You can check for
this by right-clicking the Adobe PDF printer, choosing "Printer
Properties," then selecting the "Ports" tab.) In fact, it deleted those
ports! (Here's a link to that problem:
http://kb2.adobe.com/cps/893/cpsid_89330.html). The result was PDFs that
would not print, and would be left stuck in the printer queue. The fix
was to delete the Adobe PDF printer, then run the Acrobat repair option
to regenerate it. You might want to do this. Following are the
directions for Windows 7. Windows XP instruction are included at the
link above.
          *Windows Vista (UAC on, nonadmin user), Windows 7 (UAC on,
          admin user)*
1. Close all PDF files.
2. Go to Printers and Faxes (Windows XP), Printers (Vista) or Devices
    and Printers (Windows 7).
3. Right-click the Adobe PDF printer and click Delete (Windows XP,
    Vista) or Remove Device (Windows 7).
4. Enter the admin credentials. This step deletes the Adobe PDF printer.
5. Go to Programs and Features (Vista and Windows 7).
6. Select Adobe Acrobat X Pro or Standard and click Change.
7. Select Repair and follow instructions to complete repair.**
By the way, I don't think this was mentioned earlier, but another cause
of problems with PDF generation is having more than one installation
and/or version of Acrobat, Adobe Reader, or the PDF creation add-on that
comes with FrameMaker installed simultaneously. If you have Acrobat, you
should NOT have Adobe Reader or the PDF creation add-on installed on the
same computer, and you should have only one version of Acrobat installed.

"Save as PDF" - pages truncated - whole right side missing

When using "Save as PDF", the resulting image has the right margins truncated.
The right margins are cropped off so document is displayed in very large characters (although I'm in 80 %) and the whole right side of the page is non-existent.
Problem occurs with Firefox 3.6.14 in my main account.
When creating a test account, problem disappear.
I tried to ditch all Adobe Acrobat preferences and Firefox Profiles.
No avail.
Problem never occur in Safari 5.03
In my second machine (Mac Book Pro), the problem does not occur.

Yes, Acrobat is my default viewer so far.
Until a few days ago, when I "Save as Pdf" from the printing menu,
I had a regular PDF created from the web page I was in.
Since a few days, I have that clipped unusable page.
When doing the same in Safaru, no problem at all.
That bug has several occurrences from other users in Mozilla forums.
There is also one instance in this Apple Discussions forum.
No reply though.
In Preferences, I only found Page Display and don't see nothing related
to Page Setup. I only find Page Layout which is set on Automatic. Any other setup don't change anything.
When using the same feature ion my Mac Book Pro, same Firefox, same everything, no proiblem at all. So it's related to pref in my iMac and I don't know what because I didn't change anything recently. Really annoying because I need that feature very often.

Save as PDF Files too large, Remove Embedded Fonts/Compress Fonts

When I create PDF's using "Save as PDF" in Mac OS X, the file sizes are much larger than is acceptable for my application. For example, a recent PDF I created ended up at 1.7 MB and I need it to be around 150 kB.
When I open the file in Acrobat Pro 6.0 and audit the file, I see that 94% of the file size is taken up by embedded fonts. I can then Optimize PDF with Acrobat Pro and remove the embedded fonts. The file size drops to around 145 kB.
Is there any way to NOT embed fonts when creating PDF's with Mac OS X? Also, is there any way to compress with Mac OS X in a manner similar to Acrobat Pro?

Hi LD,
I don't think so that this is possible.
I have the same problem to ... even when I open a existing PDF file that I downloaded from the net. It was 150 Kb an after I work in it to make same changes I save it an turns up to be 2 to 3 Mb or sometimes even more ...
I open de PDF than in Acrobat pro and remove everything I don't want ... I select in Acrobat Pro an select 'optimise PDF'
Dimaxum

Sizing Save as PDF Output

One of the volunteer activities I do is to help manage the photograph archive of the family data pages in historic and fragile family Bibles. I like to first produce the data pages in a PDF so that nearly anyone transcribing can use a PDF reader to zoom in on a particular portion of the old handwriting. Where others have first photographed with basic digital cameras and the file is a modest size JPEG, going to Print Images, and then using Save as PDF produces a multi-page PDF containing all the images that is manageable by nearly any computer.
My last effort was with images taken by me with my D300 in RAW. The images clean up really well, but producing a PDF in similar manner creates a rather huge PDF file (over 1.2 GB for a 20 page document) that is sluggish to use even on my Mac Pro -- but you sure can read it.
Therefore I am trying to understand the "science" of how all the conversions take place to produce the PDF when the underlying images in Aperture are high resolution files of significant size. I cannot find that Export preferences have any bearing on this, but maybe I am missing something.
Ernie

It sounds like you are printing a PDF from a raw file.
I don't understand the science, but I did a test recently in a similar situation.... the PDF of a 12 Mgb raw file ballooned to over 60 Mgb! So I exported the raw file as an original size jpeg, which trimmed it to just over 8 Mgb.... and then "printed" a PDF from that, and it stayed at just over 8 Mgb.
That should reduce your file to about 153 Mgb, which will be much more manageable.
Also, you can play around with either the export settings for jpeg, or the PDF print options to get that down even more.

Fm9p237, probs with Save As PDF, turns *some* anchored frames blue

I am using Save As PDF because have to create CMYK PDF. I know how to do that. The issue now is that FrameMaker is sticking blue boxes around only *some* of the graphics.
They are all EPS graphics imported by reference into anchored frames. These boxes do not appear in the FM file.
The boxes clearly are the anchored frame bounding boxes.
Any ideas? Any switch I should set? Any ritual incantations that will appease the FM Postscript generator?
Thanks for your help, Becky

Hi Bernd and Art,
Yes, I am using spot colors. I did some more testing and here is what I found:
Use Save As PDF in FM-->all colors except for spots are correctly converted to CMYK. Bitmap screenshots are also converted to CMYK. If I convert the spot colors to CMYK SWOP in Acrobat 9, using its preflight tool, the spots are all converted to the same CMYK values that they were assigned in Frame. BUT there are random blue boxes in the doc, clearly where FM for some reason colored the bounding box of an anchored frame or a table cell.
Print to Adobe Printer instance in FM with the Press Quality job options-->All colors come out CMYK, including spot colors and bitmapped
and there are no random blue boxes BUT the CMYK conversions of the spot colors are wrong.
My choice: Save As PDF. I will just remove the blue boxes with Acrobat.
I considered PitStop Pro and downloaded the trial copy, but its userdoc is terrible and I can't figure out how to batch-convert the incorrect CMYK colors t. Can't find any good help on line either. Too much bother.
Sigh. Adobe, are you listening? It's ridiculous that the company that produces Photoshop can't make CMYK color conversion work in Frame.
TThank you, Bernd and Art. I appreciate your feedback very much.
--becky

FrameMaker 10 and Save as PDF

Why does it take so long to produce a PDF when you use Save as PDF? I was running prior, FrameMaker 8 and on XP platform. I still use XP, but it takes a long time before the PDF is produced. Is there a patch/update/something that will speed this performance?

MRDAKOTA
I am using FM9 and have the same issue with PDF's. Below is a link to another thread about the same problem.
Nothing actually worked for me...but thought you might want to read through it.
http://forums.adobe.com/thread/757124
ls

PE4: Using Save As... PDF

Similar Messages

Maybe you are looking for