PDF generation from FrameMaker v8

The "Save to PDF" feature (in FrameMaker v8) decided to stop working for me. I used to use it regularly, and it used to work just fine. I haven't been able to figure out why it is no longer working.
When I select it, I am shown the "PDF Setup for Selected Files" dialog, as usual, and I press [Set] as usual. The status bar displays "Opening Chapter1.fm", etc., for each chapter, but then it just quietly stops. When the target PDF file pre-existed, the target PDF was deleted, but no new PDF file appears in its place. It does produce a Book.log file which has the following contents:
%%[ ProductName: Distiller ]%%
%%[ Error: syntaxerror; OffendingCommand: %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
I had the installer attempt to repair the installation, and when that didn't work, I uninstalled, re-downloaded, and re-installed Adobe FrameMaker v8. I also had the installer repair "Adobe PDF Creation Add-on". None of this had any impact -- the symptom remains the same.
I also tried "Print Book..." with "Print to file: Book.ps" and "Generate Acrobat Data [PDF]" set, and Printer: Adobe PDF. This produced a Book.ps file, but no PDF file, nor did the PDF printer ask for a file name. I don't normally generate the PDF in this fashion, so I'm not as comfortable with this method, but as a diagnostic, the fact that it also didn't generate the PDF seems to be a clue. I assume Distiller is malfunctioning?
Can anyone give me some clues as to where I should look next? Can I do anything that would provide further diagnostic clues? Is there any paper that describes the architecture of Distiller / PDF-creator, which I might refer to for tracking down what configuration is messed up?
Thanks,
Lonnie

I re-installed the FM v8 patches, so that now I'm at FM 8.0p277. Problem still persists, no change to symptoms.
The hotfix link was an excellent suggestion. It definitely looked like it might be relevant. Unfortunately, the hotfix page does not provide a download for XP x64. I contemplated trying the Server 2003 x64 version, but after reading the warnings that came with it, I chicked out on trying that. I put in a request to Microsoft for the XP x64 hotfix, which I have not received, but as I studied the hotfix a bit more, it looked less and less likely that this would be the problem, and even that I should probably not install it. The hotfix itself replaces atmfd.dll with a new one labeled as version 5.1.2.277. So I checked the version of my atmdf.dll, and I'm at 5.2.2.232. The hotfix itself was put out in 2008. I suspect I'm way past it in my Windows updates, and seems like it would be a bad idea to revert back to an earlier version.
The other thing that deserves mention is the fact that Save to PDF was working for me for the past 3 years, so my system has probably had whatever hotfix it needs. I willingly concede that there are several holes in this, but it is still fairly compelling.
I clearly have something wrong with the "Adobe PDF Converter" printer driver. So I think it is a logical course of action to focus on it. For example, when I pull up any application (e.g., Notepad), and then Print... to the "Adobe PDF" printer, the "Creating Adobe PDF" progress dialog hangs indefinitely, usually with about 10% of the progress bar elapsed. It seems like a simpler piece to focus on for now -- solve that, and I'll bet the Framemaker problem gets fixed.
I don't know how one re-installs the "Adobe PDF Converter" printer driver. I'm pretty sure it got there when I installed FrameMaker v8. My "C:\Program Files (x86)\Adobe" directory has these subdirectories:
Acrobat 8.0
Adobe Help Viewer
Flash Player
FrameMaker8
Reader 10.0
Reader 8.0
There is a subdirectory C:\Program Files (x86)\Adobe\Acrobat 8.0\Acrobat\Xtras\AdobePDF\AMD64
which I think contains be the "Adobe PDF" printer driver files. The three DLLs in that directory all have valid digital signatures. I assume that if one of them became corrupted for some reason, the digital signature would be invalidated.
Are there any theories for what the "Adobe PDF Converter" might be hanging on? Anything relevant I can check or test via DevStudio (which I have)?
Continued thanks for all your efforts,
Lonnie

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

Problems Viewing and Printing PDFs Created from FrameMaker

I got no responses to this issue in the Acrobat forums (I posted 6 days ago), so since at least some of the PDFs were created through FrameMaker, I am posting here to see if anyone in this forum has seen the problem.
At our company, we regularly create PDFs, usually from FrameMaker version 9. In most cases, we have no problems with the PDFs, but once in a while, we are notified that customers get the following problems:
If they try to print the PDF, they see a series of messages which consistently include "The document could not be printed" and "There were no pages selected to print." If they choose a page or range to print, this often works, but certain pages will not print. In one case, I saw a message saying there was a problem with the PDF with the number 14, but this does not always appear.
Often, the pages that will not print, when viewed at a normal magnification, appear as very small thumbnails that look like the dotted line down a black highway. The rest of the pages are at a normal magnification and can be read.
Often, these same PDFs crash when certain bookmarks are clicked.
This always seems to happen when the PDFs are viewed within a browser on our website or in our web-based software. I've been told by our tech group that it happens in other browsers, not just Internet Explorer, and it still happens if they save the PDF out of the browser down to the desktop and try printing from there.
In the cases I've seen, when I go back and look at the original generated PDF file in Adobe Reader or Acrobat (not within a browser), none of these problems occur. Redelivering the file to the web location often fixes the problem.
I've read many posts about this in various locations on the Internet and one in the Adobe Forums, but none seem to come up with the cause to this problem - they just come up with workarounds for printing the file.
One other note - one of our engineers and tech writers found that one PDF with this problem appeared to have Fast Web Viewing turned off, even though nothing was done differently when the PDFs were generated.
Does anyone have any information on what causes this problem and how we can avoid it?
Tammy

I'm not sure why, but my original post came through blank. Here is a
second attempt:
> Often, the pages that will not print, when viewed at a normal
magnification, appear as very
> small thumbnails that look like the dotted line down a black highway.
The rest of the pages
> are at a normal magnification and can be read.
I almost didn't reply to your post because I'm not sure that I am making
anything but a wild guess. But I seem to recall many years ago that
there were some reports on the frameusers.com listserv of some PDF pages
showing up as tiny pages-- similar to what you describe. I'm not sure if
I can trust my recollection, but I THINK the fix was to go into the PDF
printer properties, and reduce the dpi setting from 1200 to 600 or even
300. I don't remember the exact reason, but I think it had something to
do with a problem in the way Windows GDI interacts with documents
containing large-size type (such as 72-point glyphs). Anyway, I may be
remembering it wrong, or may be off on the wrong track altogether, but
it won't hurt to make the change and try. You can always change the
setting back.
And if it doesn't work, consider posting your operating system, Acrobat
version number, and whether or not FrameMaker 9 is fully patched. It
might help someone else chime in with help.

Pdf created from FrameMaker book using FDK is of bigger size

Hi,
I am new to FrameMaker, when trying to generate a pdf document from a FrameMaker book using FDK, the size of the pdf file created is big when compared to the pdf created using “Save As PDF” from FrameMaker. I have tried setting Named Destinations to false and also “PDF Job Options” to “Smallest File Size”.
Below is the code we use to create a pdf file using FDK
//Open the frame book to process document by document
bookId = OpenFile(strFile);
/* Get docId in order to set Acrobat Bookmark levels */
docId = F_ApiGetId(FV_SessionId, FV_SessionId, FP_FirstOpenDoc);
F_ApiSetInt(FV_SessionId,bookId,FP_PDFBookmark,True);
F_ApiSetInt(FV_SessionId,bookId,FP_PDFJobOption,6);
/* Sets "Body" to the highest Acrobat Bookmark level. */
pgfId = F_ApiGetNamedObject(docId, FO_PgfFmt, StringT("Body"));
F_ApiSetInt(docId, pgfId, FP_AcrobatLevel, 1);
F_ApiSimpleSave(docId, name, False);
/* Sets the save parameters so as to save as PDF and allow user to name file.*/
params = F_ApiGetSaveDefaultParams();
i = F_ApiGetPropIndex(&params, FS_FileType);
params.val[i].propVal.u.ival = FV_SaveFmtPdf;
i = F_ApiGetPropIndex(&params, FP_PDFAllNamedDestinations);
params.val[i].propVal.u.ival = (IntT)False;
i = F_ApiGetPropIndex(&params, FP_PDFJobOption);
params.val[i].propVal.u.sval = F_StrCopyString ((StringT)"Smallest File Size");
/* Saves the book and all its components to one PDF file */
int_SaveID = F_ApiSave(bookId, StringT(strTargetFile), &params, &returnParams);
/* Close the open files.*/
F_ApiDeallocatePropVals(&params);
F_ApiDeallocatePropVals(returnParams);
CloseFile(bookId);
Can anyone suggest a way to reduce the size of the pdf file
Thanks,
Neeraja

Are these duplicates side-by-side (e.g. A and then A again) or one after another (A, B, C... and then A, B, C...)?
If they're one set after another, FM picks up the list of paratags to include in the bookmarks list from the first file in the book, so if this doesn' contain everything, it might help to import the additional formats into that one. Then clear/remove the exisiting bookmarks and only add back the Titles and Heading1 bookmarks (check that the TOC ones remain in the Don't include list).

Disappearing footers in PDF generated from FrameMaker 9

Myself and three other writers are having a problem with disappearing footers in FrameMaker. Here’s the problem: In FrameMaker, the footers display correctly. When we convert a book to PDF, many of the footers disappear. What we find is that a footer (or part of the footer) will appear on the first page of the chapter, but then the footers disappear in rest of the chapter.
Here is some more info:
·         We are using Frame 9. My version is 9.0p250. I'm also using Adobe Acrobat 9 Pro Extended, Version 9.3.2 and Adobe Distiller: Professional Version 8.1.3.
·         We have been able to duplicate this problem using multiple guides.
·         Oddly, footers DO appear correctly when I print just one chapter.
·         I’ve tried rebooting my machine and then loaded only FrameMaker (in case of memory issues).
·         I optimized the book file and associated chapters.
·         I experimented with different Distiller settings.
Anyone else having this problem?

It's probably a symptom of needing the MS Hotfix that corrected a problem with text disappearing from PDFs generated from several Windows apps (not just FM).
More info here:
PS Hotfix KB 952909
Adobe blog: Hotfix for FrameMaker
Please let us know if this does the trick --
Sheila

Keep getting "renderable text" error when I need to OCR PDF's from FrameMaker.

My solution has been to individually extract all those pages, then open them up in Photoshop, flatten them and
widen the canvas size to standard 8.5 x 11.
But that's a little tedious and time-consuming and you have to delete the original page from your document, after
importing the OCR-friendly page.
Is there a printer definition, or something you can set up when you're generating your PDF's in the first place,
that will get rid of that annoying "renderable text" error?

Ok...
I don’t know how it happens but after I save my work in FrameMaker or MS Word, and print
to PDF for the final output, there are often pages with text in them that isn’t recognizable,
or that can’t be found with a CTRL+F search.
That is a serious issue, and one we might be able to help you with, but really, quite separate from the issue here. It's too late to try and fix this once it is a PDF.
What is it that’s lost when OCR is run?
Quality. Small file size. Tags (which might be required legally). Almost everything except the basic text, and that might also be lost given that OCR is not guaranteed to work. This is NOT the right way to solve your problem.
The translator doesn’t have any Adobe products except Reader, so I’m limited to Acrobat
to show her how the words and pictures are laid out on a page.
In order for her to copy and paste that text – or search it, to find all of the places where the
same word might be used – I need to make sure every word is there for her to grab.
I have heard of translators trying to work with PDFs, and few that succeed. You can reasonably expect a transation service to support FrameMaker. But if they don't I recommend you extract the text from FrameMaker to a simple Word or text file. They should be fine using the PDF as a visual reference, and having the text to translate, and for you to flow back into the original layout. (Again, something I'd expect a full service translation to do themselves, but there are advantages to keeping control too).
Those were the 2 pages that gave the ‘renderable text’ error. Don’t ask me why or how, they
look like all the other pages in that document. Except Acrobat thinks they’re scanned graphics,
that’s how they present when you wave the cursor around in them, hunting for text.
Renderable text is just text. It means that somewhere on that page there is text. Surely there is layout, page numbers, whatever from FrameMaker on the pages. If not, we really need to look at your production methods - back to the first point.

Duplicate bookmarks in PDF created from Framemaker 8

Hello,
I'm working on some legacy content using Framemaker 8 p266. Every time I create a PDF, I get duplicate bookmarks. The first set is wrong, and the second set is formatted correctly and contains the right content.
For example, it basically looks like the PDF is grabbing all of the content from the Table of Contents page, and then listing the correct bookmarks (Section title, heading 1) after that.
I'm creating my PDF using the Save As PDF option. In the PDF Setup for Selected Files dialog, I do have the Generate PDF Booksmarks option enabled, "Bookmarks Expanded Through Level" is set to None, and in the Include Paragraphs field I have Appendix Title, Head 1, and Section Title.
I'm using Adobe Distiller XI, maybe that's my problem.
Any ideas? I would appreciate it.
Susan

Are these duplicates side-by-side (e.g. A and then A again) or one after another (A, B, C... and then A, B, C...)?
If they're one set after another, FM picks up the list of paratags to include in the bookmarks list from the first file in the book, so if this doesn' contain everything, it might help to import the additional formats into that one. Then clear/remove the exisiting bookmarks and only add back the Titles and Heading1 bookmarks (check that the TOC ones remain in the Don't include list).

PDF Bookmarks From FrameMaker Books

This question is about bookmarks in a PDF file generated from a Framemaker book where I want different bookmarks for different chapters. I am using FrameMaker 8.02 on Windows.
Here is a simplified view of my chapter files and the paragraph tags for which I want bookmarks:
Table of Contents.fm Title
Chapter 1.fm Title, Heading1, Heading2
Index.fm IndexTitle, GroupTitlesIX
I used the PDF Setup dialog to set the bookmarks for each chapter as shown above.
If I choose File->Save As PDF on the book, FrameMaker presents the PDF Setup dialog which overwrites my preset bookmarks settings in the individual chapters. I can not choose a superset of all the bookmarks because GroupTitlesIX does not appear in either of the lists of paragraph tags to be converted to bookmarks. Despite this, I do get a bookmark for the GroupTitlesIX paragraphs in the index.
If I choose File->Print Selected Files, Acrobat also changes the paragraph tags/bookmarks setting for each selected file.
What would clarify this is an explanation of how FrameMaker chooses which paragraph tags to convert to bookmarks and under what circumstances FrameMaker changes the paragraph tags/bookmarks setting for files of a book.
Or simply how to you use different paragraph tags for bookmarks in different files of a book?
Thanks.

Hey Howard,
We use the Save as PDF all the time and don't have any problems with our bookmarks. We did have to be a little creative in order to get the different headings in the different chapters to show up as bookmarks. All we do is to import the different paragraph styles into the first file in the book (in our case, it is "front.fm"), which usually involves importing the paragraph tags from the TOC, one chapter file, and then Index.
When you are ready to create your PDF file, make sure the first file (with all the required para tags) is selected, then do a Format > Document > PDF Setup and configure your bookmarks. Now do a Save as PDF on the book, still with that particular file selected, and double-check your bookmark settings. All required bookmarks should still be available.
Now they are forever configured and you can successfully do a Save as PDF file every time.
Sam

Randomly Missing Text in PDF Created from FrameMaker

This problem relates to a structured FM document, but I suspect it might be a general issue and have posted it here in the general forum for that reason.
I am generating PDFs that are missing text somewhat randomly throughout. I tried searching the forum for solutions, but none of the suggested fixes worked and none of the posts specifically addressed the issue I am experiencing.
I am working in structured FM. The templates we use were originally created for FM8. We use both FM8 and FM10 in our work group. We are able to duplicate the same problem in both versions and on multiple computers.
I thought I had narrowed the problem down to certain paragraph formatting, since it only ocurs in three or four paragraph formats (a bullet list, table text, etc.) Garden variety formatting. But in most places in the document, these formats appear perfectly. The strangest occurence is a single intance where the page number is missing from the footer.
I thought it might be a font issue, as I've had similar issues in the past. I had a missing font warning in the console, but I am pretty sure that this has nothing to do with it, since they are fonts we are not using and all the other text from the same formats appears.
I tried turning off "Remember Missing Font Names" in preferences. No help.
I checked that the fonts are in the local directory and appear as embedded subsets in the PDF.
I also tried checking and unchecking the "Rely on system fonts only; do not use document fonts" option in the PDF output settings. Also no help.
The randomness of the missing fonts bewilders me and I've exhausted my own troubleshooting abilities. I would be happy to share a source file if anyone thinks they could help me that way.
Thanks in advance,
Douglas

There is a known bug in Windows XP that causes random dropped text in
PDF. The hotfix is here, though the link does not seem to be working at
the moment:
http://support.microsoft.com/?id=952909
However, the above link directs you to a download link that is here:
http://support.microsoft.com/Hotfix/KBHotfix.aspx?kbnum=952909&kbln=en-us <http://support.microsoft.com/Hotfix/KBHotfix.aspx?kbnum=952909&kbln=en-us

PDF generation from Webdynpro for java application

Hi all,
I have a scenario in which a PDF has to be generated from the datils present in a table in the same view, on click of a button. I have found many solutions for generating interactive forms but I need to generate it from the code directly. I have also found an application for generating an excel sheet from the table data but it is not working with PDF.
So anybody suggest me how to do it or please refer any applications that have been done.
Thanks in advance.

Hi marco,
Sorry for the late reply.
I have got an application to generate an excel file and i will paste that code here for your reference.
    byte[] excelXMLFile;
    IWDCachedWebResource cachedExcelResource = null;
    String fileName = dataNode.getNodeInfo().getName() + ".xls";
    try {
      // create Excel 2003 XML data as a byte array for the given context node, attributes and headers
      excelXMLFile = this.toExcel(dataNode, columnInfos).getBytes("UTF-8");
      // create a cached Web Dynpro XLS Resource for the given byte array and filename
      cachedExcelResource = this.getCachedWebResource(excelXMLFile, fileName, WDWebResourceType.XLS);
      // Store URL and filename of cached excel resource in context.
      if (cachedExcelResource != null) {
        wdContext.currentContextElement().setExcelFileURL(cachedExcelResource.getURL());
        wdContext.currentContextElement().setExcelFileName(cachedExcelResource.getResourceName());
        // Open popup window with a link to the cached excel file web resource.
        this.openExcelLinkPopup();
      } else {
        wdComponentAPI.getMessageManager().reportException("Failed to create Excel file from table!", true);
    } catch (UnsupportedEncodingException e) {
      wdComponentAPI.getMessageManager().reportException(e.getLocalizedMessage(), true);
    } catch (WDURLException e) {
      wdComponentAPI.getMessageManager().reportException(e.getLocalizedMessage(), true);
In the above code "excelXMLFile" is a byte array in which the data that has to be appended to the pdf (in xml format) is present.
the toExcel method is used to convert the data in the table(i.e., the data that gets populated in the nodes of the view) in to XML format.
My Problem is when i change the filename to .pdf extension and the WDWebResourceType.XLS to WDWebResourceType.PDF and execute the application the Acrobat reader is getting opened but it says
"unsupported file type or the file has been damaged" .
I mean i am unable to put data into the file.
So, please help me in this regard.

Problem with PDF generation from Interactive Report

Greetings,
I created an interactive report and chose CSV and PDF download options. I am able to create CSV but when I try to download a PDF it says that that acrobat reader cannot open the created pdf file. I am not sure what I should do to make it work. Please help.
-Vatsa

Hey there,
That happened to me when I had an & sign in the page title name. If you have some weird symbols in the page title, try changing them. Then it will work.
PS
Make sure in the title name and page name there are no weird symbols.
Mike
Message was edited by:
weezy f

Unable to generae pdf from Framemaker

Hi All,
I am experincing some error while generating pdf from Framemaker 10. The generated pdf is not displaying the content in all the pages and even most of the tables are also appearing blank. Does anyone know what is the error behind this? Please help.
Thanks,

Hi Radhika,
Try creating a PDF file using file/print. Although this is unexpected behavior for Framemaker (sorry) - you should contact Adobe Support.
Kindest regards, Stacy

PDF is the wrong size from framemaker 8

I am trying to create a PDF from Framemaker 8. The page size of the doc is US letter (216mm x 279mm)
I am tring to change this to A4 (210mm x 297mm). Margins or extra white space is not an issue.
Not matter what setting I change in Framemaker 8, either in the print dialog under "PDF setup" or in "Setup"
where I am changing everything to A4 my PDF generates as 210mm x 279mm
I have tried various job options and but still the PDF is the wrong size
FYI I am using Frame 8/Distiller 9..
Any ideas..?

>Any ideas..?
Sure, ask in http://forums.adobe.com/community/framemaker

Dynamic HTML generation from a Dynamic PDF/XDP

I was wondering if LiveCycle is able to generate a dynamic HTML page from a dynamic XDP/PDF form in LiveCycle ES ?
I have read up on the help contents regarding HTML generation from PDF forms but its not mentioned anywhere whether LiveCycle supports the creation of an HTML page that mimics the dynamic behavior of a dynamic PDF/XDP form.
Thanks in advance

Yes it does ....
Paul

Just upgraded from FrameMaker 7.2 to version 12. When I try to create a pdf of a book using .ps file, this crashes. When I use the SaveAsPDF option, the graphics either missing or only partially shown in the resulting PDF. Any ideas?

I just upgraded from FrameMaker 7.2 to version 12. When I create the .pdf of a book using the SaveAsPDF option, the many of the graphics are either missing or partially missing. Any ideas why?

1. Check to see whether you're fully patched (the latest release is 12.0.4 - you need to install the patches in order).
2. Use the RGB option instead of the CMYK (unless you are creating output for press production).

PDF generation from FrameMaker v8

Similar Messages

Maybe you are looking for