Bookmarks in webhelp generated from Framemaker

Hi all
We're using the trial version of Framemaker 12 as part of the TCS5 suite.
I've been experimenting with the Publish pod to create WebHelp and am wondering how to specify which Framemaker headings appear in the Webhelp TOC?
I thought it might use settings in the Bookmarks tab in PDF setup - but have tried this to no effect.
Certain headings do appear in the TOC, but not a new ChapterTitleHelp style I've created. How do I get this to appear?
I've looked in the Style Mapping tab in the Publish Settings dialog (when you right-click Webhelp and select Edit Settings). However, this seems to be more to do with the look and feel and character format than determining which headings appear.
Can anyone help please? We do have Robohelp as part of the suite, but to the best of my knowlege you should be able to output directly from Framemaker without opening RH. Is there a file somewhere where you can specify which headings you want?
Many thanks
Laura

Of course, once I post, I work it out.
It seems that the styles have to appear in the Framemaker TOC. I had not done this because I was still in the hard copy mindset and would never add the ChapterTitleHelp to the hard copy TOC.
Hope this helps someone else anyway.
Laura

Similar Messages

Webhelp generated from Robohelp 7 doesnot work fine with Google Chrome

Why is it that Webhelp generated from Robohelp 7 doesnot work fine with Google Chrome? Are there any issues with browser compatibility for Google Chrome? Please let me know how to fix it.

You don't say what you mean by "doesn't work." It doesn't open at all, it opens but doesn't work?
See Item 2 at http://www.grainge.org/pages/snippets/snippets.htm#browsers Likely that is the answer but if not there is a link to another Google Chrome item.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

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

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

Web printing from a report generated from a bookmark

Hi,
I implemented the How to web printing last year. Eveything worked fine until someone tried to print a report generated from a bookmark. It opens the window where it shows the formatted report to be printed, but does not do anything else. The window remains blank. Anybody having an idea? I am sure it is related with the bookmark stuff, but can not get the finger on it.
Tks a lot,
Guylaine

Has the template that the bookmark is off of been changed? That might be causing the problem.
Thanks,
Jeff

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

Glossary from FrameMaker not appearing in RoboHelp output

We are using FrameMaker 10 and RoboHelp 9.
We have user guides in FrameMaker that we want to publish to WebHelp from within FrameMaker. The user guides in FrameMaker all have a glossary in its own chapter at the end of the guide.
In FrameMaker, with the user guide book file open/selected, we select File > Publish.
The Publish Settings window appears.
We select WebHelp, and specify an ISF file that breaks chapters down into individual HTML files by heading level, then click Publish.
RoboHelp opens and publishes the content from the user guide to WebHelp, then RoboHelp closes.
We navigate to the folder that contains the WebHelp files, and launch it.
There is a glossary node at the bottom of the TOC in the WebHelp, but it is always empty.
Can someone please explain how to get RoboHelp to include the glossary content from the Glossary chapter in the user guide when it publishes from FrameMaker to WebHelp? We were hoping that the handoff from FM to RH was seamless, but apparently it is not.
Thank you!
Tim

Hi Tim –
I am using a different process for single-sourcing our documentation in the TCS – FrameMaker 10 and Robohelp 9. I am creating the files in FrameMaker as book files, with TOCs, Glossaries, and Indexes. I am also conditionalizing some text for online and some for print. However, my workflow, based on a lot of research and watching tutorials, is to link the FrameMaker files in a RH9 project. Then, I use Robohelp to apply the .isf file settings, a FrameMaker template to use for conversion of things like cross-reference formats, a RH master page for the online help, the customized Webhelp skin I want to use, and to do any other small tweaks as necessary since the conversion process is about 90% seamless but not perfect.
I found that when linking the files (rather than importing, which is a static process), I also get “empty” default TOCs, Glossaries, and Indexes. The solution that I found is:
1.       After generating html topics from my linked FramMaker book files, I right-click on the book file in the Project Manager pod and select Properties.
2.       On the Contents tab of the “FrameMaker Document Settings” panel, I check all 3 boxes to “convert FrameMaker” TOC, Glossary, and Index files. For the TOC, I navigate to the FrameMaker TOC file of my book.
3.       I select the radio buttons to “Create new associated” TOC, Glossary, and Index and RH insists I name them, so I name them Contents, Glossary, and Index.
4.       Then, click OK to close this window.
5.       Back to the Project Manager pod, I right-click my new TOC, Glossary, and Index files (one at a time) and select the option to set these as the Default ones.
6.       I then have the option to right-click and delete the old (empty) ones (for simplicity’s sake). Everything is then right with my help files.
Yes, this is a lot of steps. It’s the only workflow I’ve found that produces the result I want (Webhelp versions of my FrameMaker generated files that contain all entries at the correct levels, and are automated). FWIW, I couldn’t find documentation on this process anywhere. I found it through trial and error and hair-pulling :o)
HTH!
Virginia Morgan | Technical Writer
TAKE Solutions, Inc.
O 512.735.4316 | M 512.426.8323
[email protected]

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.

RoboHelp 9 Crashes When Publishing From Framemaker 10

Hello,
I am attempting to publish my Framemaker 10 doc in Robohelp 9. When I click publish, RoboHelp launches, and then quickly crashes while it says it's "loading components".
Both products are part of the TechComm Suite.
Anyway, it doesn't matter if I choose HTML Help, Adobe Air, WebHelp, for Flashhelp...this problem surfaces in exactly the same way.
The installation and output folders are all located on my local machine.
I can go to my Robohelp project and import my FM Book and get it to generate from there, but the problem with this approach is that it imports all of the xref references with each TOC entry, so this is unusable and impractical to edit by hand.
Is there an error log saved somewhere, so I can get more details on when exactly the application is crashing?

Not sure what you mean if you go into RH and import it – that’s basically what publishing is doing in FM. Have you set up a project and saved off the setting in the .isf file first? I believe you need to do that before the publish option really works.

How Do RoboHelp 9 WebHelp Generated Files Handle Map IDs and Aliases?

The text below was written by our team's developer/architect. I am the help author who uses RoboHelp to write content and generate the help files, but I am clueless how it all gets generated and is deployed. Please help. We use RoboHelp 9. I use it in Windows XP and our app and help run on IE 7, 9, and Firefox (multiple versions).
"Our application uses the numeric identifiers associated with the Map ID. For example, to get to the <appname>_home_page.htm file, we use the number 1053. <appname> = pecs, in this example.
All of this is used in a call to a RoboHelp method defined in the RoboHelp_CSH.js file. The mehtod we are calling is the RH_ShowHelp() JavaScript method and the code to perform the call, when you click on Page Help, is this:
RH_ShowHelp(0, ''/pecsHelp/index.htm>pecsHelp',HH_HELP_CONTEXT,topic);
Topic is translated to the Map ID number for the page help. HH_HELP_CONTEXT is defined in the RoboHelp_CSH.js file. This method translates into a URL and from what I have seen, the URL that gets generated is this:
http://{server}[:port]/pecsHelp/index.htm/{server}[:port]/pecsHelp/index.htm#<id=1053>>pecsHelp
Server and port get replaced with the appropriate values. I have no clue how id=1053 is supposed to get translated to mean "pecs_home_page.htm". If you check the PECS_help.h file, you will see the following entry:
#define PECS_Home_Page1 1053
Then in the RoboHelp alias file (PECS 3.0.ali), the following line is in the file:
<alias name="PECS_Home_Page1" link="pecs_home_page.htm"> </alias>
But both of these files are used during the WebHelp generation process and I don't know how the WebHelp generated files handle the Map ID and aliases."

You need to assign the numbers you find in the pecs_help.h file to topics in your help. You do this in Context Sensitive Help > Map Files > All Map IDs. (From RH7, but I assume the location is similar in RH9.) This creates the entries in the .ali file.
Peter Grainge suggests a couple of sites to read for a greater understanding here:
http://www.grainge.org/pages/authoring/calling_webhelp/using_map_ids.htm
(Although the second site is based on RH X5, the basic concepts and procedures should be very similar. )
HTH,
Amber

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

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

Best methods for creating e-books from FrameMaker 10 (TCS 3.5)

I would like to know your thoughts on which of the following methods is the best, and easiest, way to create e-books from FrameMaker. I will most likely be using Calibre to do the file conversion.
(1) Using File > Publish > ePub to create an ePub file, which can then be imported into Calibre.
(2) Using the File > Save Book As > HTM command (which creates a separate HTML file for each FM file), editing the HTML files in RoboHelp (or another HTML editing tool), then importing all of the HTML files into Calibre.
Note that when I published to HTML from FM, it appears that only an output file was created from RoboHelp, as I could not find any HTML files were actually created. Is that the case, or was I just not looking for the HTML files in the right place?
If anyone has any other recommendations, please let me know! Thanks!

I linked the FrameMaker book to RoboHelp, then generated an ePub file from RoboHelp, and have a couple of issues.
(1) When I open the ePub file in Calibre and Adobe Digital Editions, there is no contents section within the book. The only contents is the contents in the navigation bar. How do I generate a contents to appear in the front of the ebook, or do I have to create that manually in RH? I did specify the settings in RH to convert the FM contents.
(2) The ePub file looks much better in Calibre than Adobe Digital Editions. Should I be concerned about this? Which viewer should I rely on?

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

Bookmarks in webhelp generated from Framemaker

Similar Messages

Maybe you are looking for