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

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...

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.

Save as PDF and fonts

When I choose "save as pdf" in the print dialogue box, are the fonts used in the document automatically embedded in the PDF?
I would like to email this PDF to a Windows user, but want to ensure they see the same that I see on my Mac, wit all fonts and layout correctly displayed.
Thanks.
Simon

That is correct. The windows user will see the pdf the way you saved that document as a pdf, with the fonts and layout as you had saved it in the document.
hope this helps

Save as PDF - Change Author Name?

In any application when you go to Print, Save as PDF is there any way to change the default author name it already has written there?

Unfortunately, that's not the answer that anyone is looking for. It's not changing the author name that is desired, but changing the author name that comes up by default when you save as PDF so that you don't have to select the author field and change it from your username. The goal is to remove steps, not to add steps.

Illustrator crashes when using save as and changing the save location yosemite OS

I am having a problem with illustrator crashing when using save as to save a file to another location than the one it was previously saved in. It will save to the same location just fine but on macbook pro with yosemite os it crashes immediately when i change the save location. Tried reinstall and also tried other users and still does it. Any solutions?

Hi Parisian tiger
What happens when you try to open any file from the same location where you are saving the file using Save As command ?
Will it be possible to join a connect session with me ?
Please do let me know about your time availability ?
Thanks & Regards,
Raghuveer Singh
[email protected]
Time Zone: +5:30 GMT (IST)

"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!

Crystal Report to PDF change fonts, cut text and change lines

Post Author: jzwanziger
CA Forum: Exporting
Hello all, I am using Crystal Reports v10 and I created my report. The report works fine and the export function works fine in some particular servers. We were developing under Windows Server 2003 Service Pack 2 using Visual Studio 2005 Service Pack 1. We created the deployment and in our testing servers works fine (Windows Server 2003 and Windows XP these machines doesn't have any development tool).
When we installed the same deployment (MSI) file in the customer Windows Server 2003, the exporting function to PDF or using it the Crystal Reports viewer doesn't work (Same worng thing that is displayed in the viewer is in the PDF). We had detected labels cut in the middle, some fields changed the font size or alignment and some lines move it up, down or growing. Obviously this looks like a environment problem, but we don't have any idea how to fix it, or what is missed.
We tried to install, Windows Service Pack 2, install Acrobat Reader v8, verified the dll's, try to install the "dbex10win_en.zip" hot fix (we were not able to install it, setup file fail due some registry inconsistencies), Validate that the fonts are the same, and nothing fix the problem.
Could somebody help us, we are a little desperate.
thanks in advace for any idea.

See [this|https://forums.sdn.sap.com/click.jspa?searchID=29094456&messageID=7206473] forum thread for possible clues to a resolution. In a nut shell, as long as the Calibri font is up to date, the other two steps are;
1) Ensure you are using the latest Service Pack as suggested by Jonathan
2) See what USP10.dll is loading (use the [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] utility)
Also, if this is a win app, compile it to an exe and run the exe to see if the issue persists. (when running the app exe, the USP10 loaded should be from the CR bin directory. when running ion the .NET environment, the USP10 will load from win\system or other)
Ludek
Edited by: Ludek Uher on Jul 16, 2009 10:57 AM

Export to PDF - Change Font size

Hello everybody,
We were exporting reports to PDF file using te "Export to PDF" option in WAD. We recently have updated the BI environment with the SP17 patch. After the patch, the font size of the reports in the export PDF file has become very small and hence not clear.
Is there a place where we can adjust the font size of the Texts seen in the "Exported PDF reports"?
Please help me with your Knowledge and Experience,
Shameem

Hi Rane,
Thank you for your input. I am aware that we can zoom the document and see the content. However when we print the report, the reports are not as clear as it was before SP17 installation. Thats the problem.
Regards,
shameem

Export to PDF changing font size

Hi,
I have gone through the posts on this topic and was wondering if anyone has a formula to predict what will happen to the text or what looks best in PDF?
I am using Arial 10,11 and 12 on some reports and Times New Roman 8, 9, 10 and 11 on others.
The worst effect is that all reports have a group of text boxes on the top right hand corner which have borders.
The reports are basically text documents so have lots of word wrapped text. In CR these paragraphs are close to the right hand edge in line with the text boxes at the top.
In PDF the right hand edge of the paragraph moves in by 3-4cms. Setting the paragraph to Justify rather than left Justify keeps it at the right, but has lots of white space which looks bad.
regards
ps

Try with this:
To resolve the behavior
Set the resolution of the default printer of the local computer experiencing the issue to 1200 DPI. Most printers have a default setting of 600 DPI.
Create two registry keys to prevent the crxf_pdf.dll from decreasing in font size.
Click Start > Run. Type "regedit". The Registry Editor appears.
Create the following keys for Crystal Reports XI with the defined values:
HKEY_CURRENT_USER\Software\Business Objects\Suite 11.0\Crystal Reports\Export\PDF\ForceLargerFonts
Type: DWORD
Recognized Values: 0,1
Default Value: 1
Creation Method: manual
HKEY_LOCAL_MACHINE\Software\Business Objects\Suite 11.0\Crystal Reports\Export\PDF\ForceLargerFonts
Type: DWORD
Recognized Values: 0,1
Default Value: 1
Creation Method: manual
Set both registry key values to 1 to turn them on.
Create the following keys for Crystal Reports XI Release 2 with the defined values:
HKEY_CURRENT_USER\Software\Business Objects\Suite 11.5\Crystal Reports\Export\PDF\ForceLargerFonts
Type: DWORD
Recognized Values: 0,1
Default Value: 1
Creation Method: manual
HKEY_LOCAL_MACHINE\Software\Business Objects\Suite 11.5\Crystal eports\Export\PDF\ForceLargerFonts
Type: DWORD
Recognized Values: 0,1
Default Value: 1
Creation Method: manual
Set both registry key values to 1 to turn them on.
Hope this helps!!
Regards,
Shweta

Ps CS5 - Save as .pdf - serious font issues.

Hello.
I'm having seriuos issues with fonts while saving as .pdf from Ps.
No matter what pdf settins I use, the fonts result messed up one way or the other (see attachment).
It only happens when saving as .pdf from Ps, while all works fine when saving from Ai, Word, etc...
I have no idea what could be the reason. Please help.
Thanks in advance.
Attachment:
top: screen capture od .psd in Ps (with font/paragraph settings)
bottom: screen capture of saved .pdf in Acrobat
Microsoft Windows 7 x32/x64 (same issue on two machines)
Adobe Photoshop 12.0.3 x32/x64 respectively
Adobe Acrobat Pro 10.0.0 x64
Adobe Acrobat Pro 9.4.1 x32

I saved the test PDF I provided from Photoshop CS5 standard 64 bit on Windows 7 x64.
Your document looks fine here:
At 200%:
At 100%:
-Noel

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

Fonts not embedding when "save as" pdf

Version: Photoshop CS4 64 bit on Windows Vista 64.
Issue: fonts not getting embedded during conversion to pdf.
I am attempting to save files for commercial printing in Photoshop pdf format (file-save as-pdf). In the past, using previous versions of Photoshop, the fonts have always been embedded in the pdf document when I choose the "Press Quality" pdf preset. However, now, even when I simplify my Photoshop source file down to the most basic level (one non-background layer with one line of type using a font I KNOW has successfully embedded before) the resulting pdf reports NO embedded fonts (no fonts at all, actually) and when sized up a great deal in Acrobat Pro shows pixelation as though the type was converted to a graphic. If I open the resulting pdf file in Photoshop the text is still editable though...
I have Photoshop files that were built using a previous version of Photoshop (CS2). When I open these in Photoshop CS4 and save as pdf the fonts are embedded just as they always were so the problem lies not with the CS4 version of Photoshop itself but rather with NEW files created by it. It seems that any NEW files I create using Photoshop CS4 wil not embed their fonts when saved as pdfs.
Help !!?!! (example file attached)

Good points. To test that out I tried substituting different non-commercial fonts (Arial, Tahoma, Times, etc.) and then saving as a pdf. No matter what fonts I try they don't get embedded. So that would seem to rule out the idea that Photoshop CS4 is now restricting the embedding of fonts to non-commercial ones.
I have poured through the save-as-pdf options in GREAT detail - have tried many various options and don't see any settings that have either made a difference or seem relevant. According to Adobe documentation anytime you select "Press Quality" as the preset the fonts should automatically be embedded.
The really odd thing is, if I take a psd file that was originally created using a previous version of Photoshop, delete all the layers and then create one single line type layer so that it is identical in every way to my CS4 test file, any font I select gets embedded when I convert that file to pdf - same exact pdf preset - all file settings the same - everything! - except that it was originally created using a previous Photoshop version.
Does that make ANY sense??

"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.

Using "Save as PDF" changes fonts

Similar Messages

Maybe you are looking for