Adobe Community : All Content - FrameMaker FAQ

Marking questions as answered

forums_noreply@adobe.com — Wed, 26 Sep 2012 17:14:12 GMT

FYI, Adobe is monitoring the support provided by the Adobe Forums. Part of this monitoring consists of data gathering on how effective the Replies and the Forums are.

When you post a problem to the forums, only you (or one of the Moderators), have the ability to mark a Reply as "Correct," or "Helpful." If "Correct" is chosen, then the thread is marked as "Answered." This does two things:

It provides the Adobe Forum Support Team with info to go to the upper-management of Adobe, to prove that the forums are viable for support.

It also provides users, who visit the forum later on, with the same, or similar problems, with knowledge that a particular threads HAS an answer, that was useful to the original poster (OP).

There is also a little set of buttons in the Replies, "Was this helpful? Yes - No" that anyone can choose. This also provides data to the Adobe Forum Support Team, as it shows that others, viewing the thread, found the Reply to bue helpful to them.

To all of you tthat have asked questions, please re-visit your threads and mark Replies as "Correct," or "Helpful," when they have helped you.That will mean a lot to the future of the Adobe Forums.

To all of you reading threads, if you find a Reply helpful to you, please take a moment to let Adobe know that it was helpful - anyone can do this, not just the OP.

Thank you.

FAQ Suggestions and Corrections

forums_noreply@adobe.com — Mon, 04 Dec 2000 21:19:43 GMT

This thread is available so you can recommend suggestions and corrections to the FAQ.

Please add only FrameMaker FAQ related entries here.

Please post software-related questions to the regular FrameMaker and FrameMaker+SGML forums and topics. Do not post them here. This topic only concerns suggestions and questions for the FAQ.

Thanks!

Sean

Disabling Format > Font flyout display

forums_noreply@adobe.com — Sat, 22 Dec 2007 22:34:22 GMT

As per instructions in the FM Online manual "Customizing Frame Products", here are the steps to disable the popup Format > Fonts display menu.

1. assuming that you do not already have a customui.cfg file: create a new text file named "customui.cfg".

2. add the following line to disable the fonts flyout:

<Remove !ShowFontChoices <Menu FontMenu>>

3. if you want FM to read this file automatically when FM starts, place it in the \fminit\configui subdirectory. Note that this is the directory as specified in the maker.ini line "ConfigCustomUIFile=fminit\configui\customui.cfg"

If you want to load the customui file manually, place the file outside of the "configui" subdirectory; when FM opens use View > Menus > Modify to read the file.

4. if you already have a customui.cfg file, the "Remove" line above can probably be added to it, but for safety be sure to make a backup of the original before modifying it.

Can't display the Structure View window

forums_noreply@adobe.com — Mon, 17 Dec 2007 22:41:01 GMT

A post from Jerry Casher 12/17/07, typical of this problem:

I'm working with FrameMaker 7.0 windows XP and for some reason can no longer display the structure view with a document open. The buttons at the upper right of the screen all work fine, except the "Display structure view" button. I've tried the shortcut also (Esc+F i v), but that doesn't work either. I've minimized the active window to see if the Structure view window is underneath it, but it is not there.

CAD and FrameMaker

forums_noreply@adobe.com — Mon, 12 Mar 2001 12:49:06 GMT

The question of getting CAD/CAM drawings into FrameMaker pops up regularly in the FrameMaker forum. If you have anything to add, please visit the "FAQ Corrections and Suggestions" topic and post your thoughts there.

Using variables in Index entries

forums_noreply@adobe.com — Tue, 09 Jan 2007 03:08:06 GMT

FrameMaker by itself does not support the use of variables in Index markers, except for a few special system ones ($startrange, $endrange, $nopage, $singlepage).

In order to reference user-defined variables in an index marker, there are a couple of third-party tools available to get around this limitation.

See:

IndexTools Professional from Silicon Prairie Software at
http://www.siliconprairiesoftware.com/

MarkerTools from Leximation at
http://www.leximation.com/tools/info/markertools.php

One Flow on Right Pages Different Flow on Left

forums_noreply@adobe.com — Fri, 29 Dec 2006 20:01:31 GMT

The issue is you want Flow A to be on right hand pages and Flow B to be on left hand pages, and you want autoconnect to work.

To borrow from a post in December 2006 from Peter Gold:

[quote]
The goal is to have on the Left Master Page, and the Right Master Page, one page-sized text frame tagged with the flow name (for example Flow [A]: for Right, and Flow B: for Left.) Also required on each master page is a very small tagged text frame of the opposite flow (Flow [B]: on the Right master, and Flow [A]: on the Left master.) The small frames need to be too small to contain any character, but I seem to recall that if they're too small, the process fails.

The underlying principle is that when the text frame, Flow A: on page 1, a Right-master-controlled body page, overflows, FM creates page 2, a Left-master-controlled body page, where the text moves through the too-small Flow: A text frame, then it creates page 3, and puts the text into the large Flow A: frame.

All the fiddling I've done seems to indicate that a too-small "helper" text frame might be the cause of failure. It might be good to start with two medium-sized text frames on the master pages, one tagged Flow A: and one tagged Flow B:, and test that this works as expected. Then, shrink the A flow text frame on the Left master, and the B flow text frame on the Right master, until they don't display text on their body pages.
[/quote]

I have posted a FrameMaker 7.1 file that follows Peter's steps and seems to work. The only thing I added was to make pagination even. (There's an oddity with end of flow tags and flow B, but this template, based on the default portrait template, seems to work.)

http://www.pubsink.com/FM7_TwoFlowsDifferentPages.zip.

If this link doesn't work, see the next post.

I cannot promise that the file will be available in a year from now, but will try to keep it there.

Cheers,

Sean

Problems Creating PDFs

forums_noreply@adobe.com — Mon, 04 Dec 2000 20:45:53 GMT

A lot of problems creating PDFs come from using the wrong printer to create the PDF or underlying printfile.

You should use Adobe's Distiller printer instance to create a PDF. This comprises the latest Adobe Postscript printer for your operating system plus the Distiller PPD.
Don't use an HP printer to create your PDF. PostScript, or otherwise.
Don't use a Xerox printer to create your PDF. PostScript or otherwise.
See #1.

Note: If you are outputting to a service bureau, you might want to use something other than the Distiller printer instance. However, if you encounter problems with your particular PDFs, try using the official method with the Distiller printer to see whether any problems are limited just to your setup. If problems persist, you might have to create your PostScript output using one printer driver and the PDF using Adobe's Distiller printer instance.

Common problems include:

Black and white, or greyscale, PDFs created from color FrameMaker books and documents.
Distiller terminating the PDF creation process early, thus no PDF is created.

Troubleshooting:

For lack-of-color problems, first check you don't have Spot as Black set in the Frame Print dialog.
Update the printer you are using to the latest Adobe PostScript printer driver version.
Uninstall the printer you are using to create PDFs and to reinstall the latest version from scratch.

Scroll wheel on my mouse won't work in FrameMaker (Macintosh)

forums_noreply@adobe.com — Sun, 17 Sep 2006 02:43:30 GMT

A product called USB Overdrive (http://www.senlick.com/) enables at least the Logitech iFeel MouseMan optical USB as well as two no-name (corporate branded for promotion) mice, one optical, one ball.

How do I make a booklet in FrameMaker? [Windows & Macintosh]

forums_noreply@adobe.com — Thu, 24 Aug 2006 16:35:10 GMT

The process of making a booklet (i.e. pages printed out in a specific order so that the sheets can be folded and stapled together) is called imposition. It is usually best done after the fact on a PDF file. There are a number of utilities that can create booklets from PDFs (as a bonus the tools aren't specific to FrameMaker) or they act as printer drivers do this during the output stage to PDF.

Some of the PDF-based tools out there for this include:

Quite Imposing at http://www.quite.com
PDFSnake at http://www.pdfsnake.com
cutePDF at http://www.cutepdf.com/
PDFenhancer at http://www.apagoinc.com/prod_home.php?prod_id=2
CheapImpostor at http://www.cheapimpostor.com/
dots Pilot 2 http://www.dots-software.com/pilot_2.php

There are some printer drivers that will create booklets. However, they all do not support postscript in most cases, so if you have EPS or PDF graphics, you shouldn't use them.

FinePrint at http://www.fineprint.com/products/fineprint/index.html
ClickBook at http://www.bluesquirrel.com/clickbook/
CMYK PDF Creator (supports postscript and provides colour correction from FM) from Grafikhuset at
http://www.grafikhuset.net/international/chameleon/chameleon_cmykcreator_features.htm

Finally, there used to be a plug-in for FM available from Mekon called mPose (or something like that), but it seems to have disappeared from their website. See http://www.mekon.com

How do I make a booklet? = Imposition

forums_noreply@adobe.com — Wed, 25 Oct 2006 20:47:36 GMT

The process of creating a booklet is called imposition. It is usually best done after the fact on a PDF file. There are a number of utilities that can create booklets from PDFs (as a bonus the tools aren't specific to FrameMaker) or they act as printer drivers do this during the output stage to PDF.

Some of the PDF-based tools out there for this include:

Quite Imposing at http://www.quite.com
PDFSnake at http://www.pdfsnake.com
cutePDF at http://www.cutepdf.com/
PDFenhancer at http://www.apago.com/pdfe_imposition.html
CheapImpostor at http://www.cheapimpostor.com/
dots Pilot 2 http://www.dots-software.com/pilot.php

There are some printer drivers that will create booklets. However, they all do not support PostScript in most cases, so if you have EPS or PDF graphics, you shouldn't use them.

FinePrint at http://www.fineprint.com/products/fineprint/index.html
ClickBook at http://www.bluesquirrel.com/clickbook/
CMYK PDF Creator (supports postscript and provides colour correction from FM) from Grafikhuset at
http://www.grafikhuset.net/international/chameleon/chameleon_cmykcreator_features.htm

Finally, there used to be a plug-in for FM available from Mekon called mPose (or something like that), but it seems to have disappeared from their website. See http://www.mekon.com

Scroll wheel on my mouse won't work in FrameMaker (Windows)

forums_noreply@adobe.com — Tue, 26 Jun 2001 00:39:20 GMT

Introduction

Repeatedly, folks post about the scroll-wheel on their mouse not working in FrameMaker, while they state it does work in other software. First, it needs to be said that is not a universal that scroll wheels don't work in FrameMaker. Some users do report that they work fine.

Background

Windows 98 and up have mouse wheel support build into the operating system. However, in order to profit from this mouse wheel support, applications must either explicitly watch for mouse wheel messages or use current versions of the standard Windows GUI controls, such as scroll bars.

And here's the problem: FrameMaker, being an old cross-platform application, does neither. So by default, the mouse wheel should not work in FM -- at all.

But why then DOES it work sometimes? That's because the user installed an ADDITIONAL mouse driver that translates mouse wheel messages into scroll bar messages, or some other kind of input. Microsoft IntelliPoint does that, and also (apparently) the Logitech drivers.

Drivers and Versions

Depending on the individual driver and version, however, there may be some guesswork and silent assumptions involved on what constitutes, for instance, a scroll bar. The version used by FM may be so old, weird, or whatever, that some drivers don't recognize it, and thus don't correctly create scroll bar messages for mouse wheel input.

The obvious choice is to try the latest version of driver software, and to make sure that your driver matches the manufacturer of the mouse. But note that it's been reported that later Logitech drivers failed, while others worked.

Some users report that going back to older versions is what worked, or that certain combinations of operating system, Frame version work. For instance, it has been reported that FrameMaker 6 and the Microsoft IntelliPoint Mouse Driver version 3.2 work in Windows 2000.

Another working combination is FrameMaker 7, Windows XP, the IntelliMouse Optical mouse, and IntelliPoint driver 4.1.

Summary

It should become clear that there is no clear-cut solution, and, if your mouse is going to work on your system at all, it will require some experimenting with drivers. My suggestion is to try the latest, then work your way backward.

==============

Contributors: R. VanDyke, Sean, Dov, Tim

How do I set up Macintosh Classic printing to make PDFs?

forums_noreply@adobe.com — Sat, 16 Sep 2006 23:17:40 GMT

A set-up that works very well, and one that I recommend, is that you maintain the latest Acrobat on the OS X side, and use it to create your PDFs. The executive summary is (1) set up printers in Classic using OS X Acrobat PPDs; (2) print PostScript files; and (3) distill in OS X.

Locate an Acrobat 7 PPD, and copy it to the Classic System Folder's Extensions\Printer Descriptions folder. In OS X, look for ADPDF7.PPD in /Library/Printers/PPDs/Contents/Resources/en.lproj.
Create either or both of (i) an Adobe PDF printer instance using Desktop Printer Utility, or (ii) a Virtual Printer, properly attached to the version 7 PPD file. To date I have not found any difference in these two. Since they're both attached to the same PPD, I would think their behavior would be the same. Note that these steps have you use standard Mac dialogs to navigate to the PPD file you copied earlier from Step 1 -- if you get to the target folder and don't see the PPD, change its type:creator to TEXT:???? or TEXT:ttxt.
Set up some good defaults. In the PostScript Settings section, I recommend Level 3 Only, Binary, and Font inclusion=all (but note that you can also choose selections to make EPS, too. In Printer Specific Options, I usually drop it down to 600. If you created a printer using Apple Desktop Utility and one using Virtual Printer, you need to do these for both.
Print to a file from FrameMaker, using one of these printers. You will find the printing options you are familiar with in the Windows world in the FrameMaker 7.0 section.
Distill the resulting file in Acrobat from OS X.

Problem with duplicate and/or outlined fonts in Macintosh

forums_noreply@adobe.com — Sat, 31 Aug 2002 15:00:59 GMT

If you are using Frame for Macintosh and you find you have duplicate Arial and/or Times New Roman fonts, or, if these fonts show up on the screen as outlines, the problem may be that you have the 2.9x versions of these fonts, the latest as of this writing (31 August).

You can find older 2.60 versions on the Apple OS 9.2 Install CD, deep in a Microsoft Internet Explore install folder (a Sherlock search will find them).

DEAD LINK, LEFT HERE FOR HISTORICAL PURPOSES: In case you're interested, you can find the 2.9x versions at http://www.microsoft.com/mac/download/office2001/fontsupdate.asp. The page says "New Apple Macintosh versions of Times New Roman (2.91) and Arial (2.90) This update includes a fix for a problem that prevented certain characters from being printed on PostScript level 3 printers", so I'm hesitant to say that you should not use these newer fonts at all.

What happened to the FM "Tour" chapter?

forums_noreply@adobe.com — Tue, 16 May 2006 18:47:32 GMT

The Chapter on "A Quick Tour of FrameMaker" somehow got lost in the addition of all of the Structured components for the version 7.x releases. This material covered the "basics" in unstructured mode - there might have been reasons for this, but it orphaned the Tour folder contents.

Attached is the PDF from the FM5.5 User Guide for the quick tour chapter.

FrameMaker for the Mac End-of-Life (No more development)

forums_noreply@adobe.com — Tue, 23 Mar 2004 14:21:37 GMT

From Dov Isaacs, and Adobe employee and all-round guru, to the Framers list (http://www.frameusers.com):

~ Adobe FrameMaker End-of-Life for Macintosh Platform ~

On April 21, 2004 Adobe will discontinue Adobe(r) FrameMaker(r) software for the Apple Macintosh operating system. Adobe FrameMaker 7.1 will continue to be available on Microsoft(r) Windows(r) and Sun(tm) Solaris(tm) platforms. Complimentary and fee-based technical support for FrameMaker for Macintosh will be available for approximately one year running through April 21, 2005.

Frequently Asked Questions

Q. Why is Adobe discontinuing Macintosh support for FrameMaker altogether?

A. The decision to discontinue FrameMaker on the Macintosh operating systems was based on the market conditions for FrameMaker. The majority of our customers use FrameMaker on Microsoft Windows and Sun Solaris platforms.

Adobe is continuing Macintosh development for flagship print and web publishing solutions such as Adobe Creative Suite including InDesign(r) CS, Photoshop(r) CS, Illustrator(r) CS, GoLive(r) CS, and Acrobat(r).

Q. How much of your FrameMaker base is currently using Macintosh?

A. It is our policy to not comment on the size of our user base. However, sales of FrameMaker licenses have been greater on the Window sand Solaris platforms for a number of years.

Q. How much longer will FrameMaker 7.0 for Macintosh be available?

A. Adobe FrameMaker 7.0 for Macintosh will be available to distributors and licensing customers and through the Adobe Store, until April 21, 2004.

Q. Will Adobe release another version of FrameMaker for Solaris and Windows?

A. Its our policy not to disclose future product plans but moving forward, Adobe's planned development efforts for FrameMaker will focus on the Windows and Solaris platforms.

Q. Will Macintosh users continue to get support from Adobe on FrameMaker?

A. Adobe will continue to provide complimentary support for FrameMaker 7.0 for Macintosh until April 21, 2005, approximately one year. Adobe will honor fee-based technical support contracts for the Mac version until they expire. Adobe Open Option (AOO) maintenance contracts can no longer be ordered. For North America customers, please contact Adobe Customer Service at (800) 833-6687. For customers in other regions, please visit to contact your local customer service team.

Issues fixed in FM 7.1 release

forums_noreply@adobe.com — Thu, 11 Nov 2004 17:49:01 GMT

Adobe FrameMaker 7.1 for English, French and German was released on January 10, 2004. The following is a list of issues fixed in this release.

250374
FDK: FA_Note_PreSetAttrValue notification not sent for new elements. If a client subscribes to FA_Note_PreSetAttrValue events, it will get a notification when one changes an attribute by double clicking it in the Structure view. However, on creation of a new element through the element catalog, if an attribute is set, no notification is sent.

This issue has been resolved.

277554
FDK: F_ApiUnStraddleCells() does not work as expected.
When unstraddling cells through the API, all the cells except the leading cell have no paragraph end marks (they are completely empty). Clicking into such cells takes the text cursor to the location of the table anchor. Inserting a character into the paragraph with the table anchor seems to correct the table.

This issue has been resolved.

310049
FDK: F_ApiImport shows a dialog upon import of SGML entities.
When importing an SGML fragment by reference using F_ApiImport, FrameMaker displays a dialog asking whether the text inset should be updated automatic or manually. This setting should be controlled from import-parameters.
Currently there is no way of creating a client that imports a large number of SGML text-insets without having a user sitting by the keyboard and clicking OK for each imported entity.

This issue has been resolved.

314764
FDK: F_ApiDelete does not work properly on elements inside a TextInset. When you try to delete an element that is part of a TextInset, the whole TextInset is removed.

The work around for this is to unlock the text before calling F_ApiDelete and to lock the text after this call. The calls to unlock and lock the text are given below:

To unlock - F_ApiSetInt(docId, insetId, FP_TiLocked, False);

To lock - F_ApiSetInt(docId, insetId, FP_TiLocked, True);

387821
Microsoft Intellimouse Scroll wheel locks up FrameMaker when it's pressed or scrolled.

This issue has been resolved.

408675
Rotated PDF files do not appear on 24-bit or 32-bit displays.

This issue has been resolved.

463533
Non-unique ID tags cause inconsistent hypertext links due to multiple entries in the HTML export. If there are conflicting IDs in different documents of a book, non-unique ID tags are generated which cause this behavior.

This issue has been resolved.

507486
If you edit the MAKER.INI file by adding the line SplashScreen=Off, in the [Preferences] section, then the Help->About command crashes FrameMaker with Internal Error: 7004, 6048898, 7639747, 0

This issue has been resolved.

529757
(don't include) Marker element gets included and merged in PDF bookmarks with previous heading. In FrameMaker 6.0, the document prints to PDF as expected--the bookmarks in Acrobat PDF contain the Section2/Heading as expected, such as:

Spark Plug Threads
and Lamp Base and Electrical Fixture Threads

In FrameMaker 7.0, the document prints to PDF with the Section2/Heading merged with the Run.head marker element, even though Run.head is in the ''Don't include'' list of elements in the PDF Setup dialog box.

This issue has been resolved.

534856
The value of DPDFOpenBookmarkLevel is ignored when read in a MIF file.

This issue has been resolved.

534865
The values Default, All, and None of the ''Bookmarks expanded through level'' field (in Format > Document >PDF setup) are not retained when a FrameMaker document is saved and opened again.

This issue has been resolved.

535630
Windows Metafile (wmf) graphic (created from Microsoft VISIO 2002) causes "an error occurred while printing" but partially prints.

This issue has been resolved.

537955
ISOdraw CGM graphics and tables on the same page cause CGM stroke lines to be printed in White.

This issue has been resolved.

540408
Inconsistent dialog behavior between FrameMaker 6.0 and FrameMaker 7.0 when opening filename.sgm. Unlike FrameMaker 6.0, FrameMaker 7.0 displays the Unknown Filetype dialog.

This issue has been resolved.

540417
Inconsistent dialog behavior between opening filename.sgm and filename.sgml.

This issue has been resolved.

541912
TaggedPDF:fmpdfreflow plug-in - display of PDF file not good for shaded table cells. When table cells have shading in them, the PDF file does not show all the content of the shaded cells. This happens on Windows only.

This issue has been resolved.

565678
PDF generation on UNIX translates CMYK colors to RGB.

This issue has been resolved.

567784
FP_InsetFile has a value of "BadFileName" when SGML importing misses a graphic data file. If you import an SGML file that would read external graphic files and these data files are missing, then skipping or ignoring them results in "BadFileName" pathname for each object property. This makes FDK API Client not get FP_InsetFile property value for the FO_Inset object.

This issue has been resolved.

569092
FrameMaker7 server can't find default printer when launched as a service.

This issue has been resolved. To suppress the errors during initialization e.g.. No Default printer, invoke FrameMaker with the -silent option.

569969
When the Paragraph Designer is open, you can't switch to open documents using the book window.

This issue has been resolved.

581376
FrameMaker works very slowly or returns an internal error. When processing a document that includes many EPS image files, FrameMaker creates many FRMxxxx.tmp files in the C:\Documents and Settings\Account Name\Local Settings\temp\ folder. The xxxx is a hexadecimal number. Even after quitting FrameMaker, the FRMxxxx.tmp files are NOT deleted, and the same document creates different FRMxxxx.tmp files after being opened again. The template files pile up in the hard disk for the Account/user, until the xxxx reaches ffff, the maximum number for the 4 digits of a hexadecimal number. At or near this time, FrameMaker works very slowly or stops with internal error:7004,6643018,6765315,6712018.

This issue has been resolved.

581522
Imported PDF document with transparencies does not print correctly.

This issue has been resolved.

584633
Internal Error: 7004, 6055410, 7657059, 0 when saving/printing to PDF includes Bookmarks that include index elements. The crash occurs only on Windows. The problem occurs when you attempt File > Print to PDF, when you want to Generate PDF Bookmarks based on structure elements, and have the ''Sectlevel1'' element in the ''Include Elements'' pane, and that particular ''Sectlevel1'' element plus the length of the text in the index marker entries exceeds 256 characters.

This issue has been resolved.

589859
Post installation of Distiller 6.0, .tps file gets retained along with PDF and log file.

This issue has been resolved.

592974
Opening a large XML file in FrameMaker generates error 'Internal Error 7004, 6052770, 0....

When an XML file contained more than 65520(FFF0) children elements, FrameMaker crashed.

This issue has been resolved.

595875
Spell check skips elements, loops around elements, or gets completely stuck.

This issue has been resolved.

597276
The Save as PDF command does not create a PDF file (for certain files) when Generate Tagged PDF is ON

This issue has been resolved.

598056
Group4 fax encoded TIFF files imported in FrameMaker 7.0 don't display nor print--does not occur in previous versions.

This issue has been resolved.

600053
Display/Scrolling performance is very slow with documents having TIFF images imported by copy.

This issue has been resolved.

600497
Scrolling a document in FrameMaker using Page Up/Down button goes to previous/next page respectively. Scrolling a document using Page Up and Page Down button goes to the previous and next page respectively. User would expect to scroll to the previous/next screen instead of going to previous/next page using these buttons, as seen in other Windows applications like MS Word, etc.

This issue has been resolved.

601470
Links being dropped in SVG filter. Import an SVG file by reference (and the imported file has a link to another SVG file). Save this and reopen; the referenced SVG file is missing.

This issue has been resolved.

603668
The text in the markers gets included in the PDF Bookmarks. Do not include textual content of marker elements, such as Index markers. This is because if you do, the Acrobat bookmarks can appear created if the element has:

where Indexterm contains the marker text:
<$startrange>PDF Creation;<$endrange>PDF:Good;How To:Create Good PDF

... You will end up with an Acrobat Bookmark containing:
How To Create <$startrange>PDF Creation;<$endrange>PDF:Good;How To:Create Good PDFGood PDF ... which is not desirable.

This issue has been resolved.

606704
In Server Setup dialog box, user name of the form "domain\username" does not allow names starting with b, r, etc. While trying to get FrameMaker to talk to the WebDAV server, which is using Windows authentication, when we specify a user name of the form "domain\username" in the "Server Setup" dialog box (File | Workgroup | Workgroup Servers ...). For some user names this works; for others it doesn't.

This issue has been resolved.

607610
Framemaker crashes when Print is selected twice from the context menu for a book.

This issue has been resolved.

610099
Drop Caps are not imported as TextFrames (RTFImport).

This issue has been resolved.

610600
Words on which cross references are created are getting dropped while importing doc file (Word2000Import). Create a cross reference on some word in MS Word, and import the doc file into FrameMaker. The word on which the cross reference is created is getting dropped.

This issue has been resolved.

611165
Words on which cross references are created are getting dropped while importing rtf file (RTFImport). Create a cross reference on some word in MS Word, and import the rtf file into FrameMaker. The word on which the cross reference is created is getting dropped.

This issue has been resolved.

611802
Text which is rotated is lost when exporting to RTF.

This issue has been resolved.

611900
FrameMaker locks referenced files until the application closes.

This issue has been resolved.

613546
The filter name in the unknown file type for import is Microsoft RTF whereas for Export it is Microsoft RTF 1.6.

This issue has been resolved.

616153
Contents of anchored frames not visible after save as PDF with Tags. After saving a document with anchored frames as PDF with Tags enabled, the contents of the frame are not visible in the PDF generated.

This issue has been resolved.

624470
footnote element mapping to Frame Footnote is commented in Rules defined for XDocBook. In application definition of XDocBook in $FMHOME/structure/xml/xdocbook/app, footnote element mapping is to FM Footnote element. However, this rule is commented since past few releases. As a result, any (xdocbook) XML document with footnote is shown as invalid in FrameMaker.

This issue has been resolved.

624472
Revision remark (revremark) element is mapped to different element names in EDD and rules. Rules for XDocBook in $FMHOME/structure/xml/xdocbook/app translate revremark to RevRemark. However, EDD (ECM) defines Revremark as mapping for revremark element. Hence a valid xdocbook XML document with revremark is shown as invalid (with unknown RevRemark element) in FrameMaker.

This issue has been resolved.

624517
Unable to open FrameMaker 7.0-created fm file, which is created by importing a Word document.

This issue has been resolved.

625306
Office documents don't open in FrameMaker in absence of write permissions (UNIX).

This issue has been resolved.

626431
For line spacing, values that are beyond range are not mapped correctly (RTFExport). For line spacing in frame document which are beyond the max or min range of RTF, the mapping is not correct and same value of line space I mapped to three different values in RTF.

This issue has been resolved.

626434
For stretch, values that are more than 600 are not mapped correctly in RTF (RTFExport). For stretching in frame doc that are beyond max value in RTF (600), the mapping is not correct. There is no stretching (scaling in RTF) in effect in exported RTF for values greater than 600 specified in frame.

This issue has been resolved.

626450
Current date and time are not getting exported properly and are coming as 0's and XXX (RTFExport).

This issue has been resolved.

627855
After saving as PDF, headings are centered in reflow mode. After a particular file is saved as a PDF file and is viewed in reflow mode in Acrobat, the headings are centered.

This issue has been resolved.

631967
Installer does not recognize existing installation.
This issue has been resolved.

633133
Right indents are not mapped while importing Excel

This issue has been resolved.

633137
Data in the Custom formatted cell is lost while importing excel sheet.

This issue has been resolved.

633462
FrameMaker terminates while exporting to RTF.

This issue has been resolved.

633710
You have to give a filename with extension, while saving a file to RTF.

This issue has been resolved.

638750
A PS file generated from FrameMaker with Tagged PDF on and hypertext marker in the file, cannot be distilled to PDF

This issue has been resolved.

638824
Dialog Box indicating Unsaved changes made to file is not displayed on closing a document after importing an image using drag and drop.

This issue has been resolved.

639220
If you select a Master Page or a Reference Page and select Save as PDF, PDF generation fails without giving appropriate error message.

This issue has been resolved.

641918
When converting a FrameMaker book to PDF: default opening page in PS/PDF may be incorrectly set to be the first page of last chapter in a book.

This issue has been resolved.

642765
On drag and drop of a SVG file into FrameMaker, if you click on the cancel button on the Import SVG dialog, the cancel is ignored and the file is imported.

This issue has been resolved.

643092
If United Kingdom is chosen as the country of purchase, the EULA contains the string "FrameMakerDesktop _USEnglish_1.21.02_17:29".

This issue has been resolved.

644158
Following alerts can not be suppressed via command line option:
. Register now/later/never
. Adobe Online

These can be now suppressed using the -noaol command line option or by using the DisableAdobeOnline=On option in the maker.ini file.

644904
An empty merged cell(256 columns) created in Excel imports as a blank file.

This issue has been resolved.

645230
If you import a Word document having large number of footnotes in FrameMaker, the footnotes are overlapped.

This issue has been resolved.

645538
Cross reference text when exported to RTF has an additional space after the cross reference text.

This issue has been resolved.

645863
When an excel file containing cells applied with custom formatting is imported in FrameMaker, the font and color of these cells is different in FrameMaker.

This issue has been resolved.

646609
When a specific excel file is being imported the data in the first cell is lost.

This issue has been resolved.

646676
When saving a MIF file, then opening it in FrameMaker, the DPDFZoom settings are lost.

This issue has been resolved.

647770
User defined variables with _ in their name when saved to xml and opened again in Frame, round-trip as fmv1, fmv2 ...

This issue has been resolved.

648043
When you try to open/import a file with a name containing more than two % signs and at least 1 non-% character between the second and third % sign then FM gives an error saying the file is non-existent

This issue has been resolved.

648114
Info>Copyright>More crashes FrameMaker

This issue has been resolved.

648434
When you import an RTF file with a cropped image in FrameMaker, it is imported in its original uncropped form.

This issue has been resolved.

649640
When a word document having text with decimal numbering is imported, the sub points (1.1,1.2,...) are imported as (0.1,0.2,..)

This issue has been resolved.

650631
When you import a word document having numbering points with comment on each numbered point, the font size of the numbering point is reduced.

This issue has been resolved.

650962
FrameMaker crashes on scaling any anchored frame on reference pages.

This issue has been resolved.

652229
When you import a word file with ascending raised/lowered baselines then they are not imported correctly.

This issue has been resolved.

652433
When you import an excel file containing date formatting having mm format, FrameMaker inserts an extra zero before the date.

This issue has been resolved.

652752
If you install FrameMaker from network, the short cut to readme file opens it in notepad.

This issue has been resolved.

652794
The alert Inconsistent settings in Book" during F_ApiSilentPrintDoc() can not be suppressed.

This issue has been resolved.

654309
When you import a word document having numbering (1.1,1.2,..) placed after some non-decimal numbering(1,2,3), FrameMaker imports it as (3.1, 3.2,..).

This issue has been resolved.

654348
When you save an inline image as .doc in Acrobat6 and import this word file in FrameMaker, FrameMaker enlarges the graphics on import.

This issue has been resolved.

655072
When you have an user defined variable in the frame document as well as the template, you save this document as XML and open the XML file again in frame, the template definition overrides that of the document.

This issue has been resolved.

655726
Full license number is displayed in the Help>About FrameMaker 7.0 screen.

This issue has been resolved.

656171
Full license number is displayed in the FrameMaker 7.0 Splash screen.

This issue has been resolved.

656820
If you zoom or move frames after importing a graphic in FrameMaker, Framemaker logs out the user from Unix machine.

This issue has been resolved.

657053
If a frame document displays images from the reference page and you simultaneously open multiple such documents, then the images from the document opened first can replace the images in the other documents

This issue has been resolved.

658744
If you open an XML file locked by some other application, FrameMaker shows a Validation Error dialog box. For this to work, the XML locking feature should not be switched off.

This issue has been resolved.

658749
The German version of Online manual xmlcss.pdf has comments in it.

This issue has been resolved.

Known Issues
The printed user guide, on-line help and QRCs will not change between the FrameMaker 7.0 release and FrameMaker 7.1. Certain online manuals will be updated, and a new online supplement will be added to cover user documentation of the new release.

[Original message from Forrest_F accidentally deleted when Forum re-organized]

FrameMaker 7 Product Development

forums_noreply@adobe.com — Mon, 04 Dec 2000 23:09:25 GMT

Adobe actively prevents those in-the-know from talking about products under development.

Several rumors and questions about the future of FrameMaker keep appearing in the FrameMaker forums. Consider information posted here as from uninformed outsiders . . . informed insiders are prohibited from letting on . . ..

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

forums_noreply@adobe.com — Fri, 07 Dec 2001 04:02:21 GMT

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

Third-party FrameMaker Resources

forums_noreply@adobe.com — Mon, 04 Dec 2000 20:54:48 GMT

Some resources for you to checkout. These are not necessarily endorsed by anyone, myself included. Indeed, caveat emptor. These are third party with not necessarily any ties to or acceptance from Adobe.

Proceed at your own peril . . ..

FAQ: Fix for Problem Printing PostScript "to file" Under Windows 2000

forums_noreply@adobe.com — Fri, 18 Jan 2002 23:09:10 GMT

PROBLEM

A number of Acrobat users under Windows 2000 have reported a problem in which printing via the PostScript driver fails when printing "to file" instead of to a standard printer port (such an LPT, USB, TCP/IP port, or even Acrobat's internal port). Printing "to file" refers to the ability to check an option in programs such as FrameMaker or Microsoft Word that causes the PostScript that would have gone to a "real" printer port, to go to a specified file name, prompted for by the driver or application itself. The symptom of the failure may be either (1) no file produced and/or (2) a nondescript error message about "unable to print."

Although we have not yet heard of this problem occurring under Windows XP, we have no reason to believe it couldn't given the extreme similarity in architecture and software components. If you are seeing this with Windows XP, please advise me of this via email and simply substitute "Windows XP" for "Windows 2000" for your purposes in this posting.

CAUSE

The problem is caused by a missing printing port named "FILE:" used by the driver whenever it, guess what, prints "to file." This port is automatically created when Windows 2000 is installed and normally would never disappear. What seems to be happening, based upon reports that I have received from several end users, is that under some conditions yet unidentified, uninstalling one version of Acrobat in preparation for installation of another (newer) version of Acrobat causes the "FILE:" port to be deleted from the system. This printing port deletion does not appear to be caused by any end-user error.

Adobe's Acrobat Quality Assurance group has been alerted to the problem, but to date has been unable to internally reproduce the problem. We would appreciate any information from any user who encounters this problem in terms of exactly how the Acrobat Distiller printer instance was being used prior to an uninstall of Acrobat (for example, were you printing a FrameMaker book "to file" with the
Acrobat Distiller printer instance for purposes of subsequently distilling the whole book manually?)

FIX

Fortunately, it is very easy to add the "FILE:" port back into the operating system:

(1) Logon to Windows 2000 as a user with Administrator privileges.

(2) Go to Start=>Settings=>Printers.

(3) Select File=>Server Properties.

(4) Click the "Ports" tab.

(5) Click "Add Port".

(6) Select "Local Port" and click "New Port".

(7) In response to "Enter a port name:" respond "FILE:" (without the surrounding quote marks, of course) and click OK.

(8) The "FILE:" port should now be in the list of available ports. You may close the remaining dialogs.

At this point, printing "to file" should work correctly. Most likely, you will not see the problem reoccur unless you do another round of uninstalls of Acrobat.

- Dov

Frame won't add a new page at the end of a file

forums_noreply@adobe.com — Thu, 22 May 2003 15:25:16 GMT

Scenario: You are typing on the last page of a file, and you find that Frame does not add a new page; but instead seems to force text below the bottom edge of the text frame>

Solution: The frame has somehow turned its autoconnect. Select the frame, choose Object Properties, and enable Autoconnect.

Grey Box TIFF (not EPS) graphics and FM7

forums_noreply@adobe.com — Tue, 14 Jan 2003 23:11:19 GMT

There is an issue with some users getting grey-boxes instead of imported TIFF graphics in FrameMaker 7. Often, these TIFFs were fine in FrameMaker 6 and the system hardware did not change in the interim.

This has nothing to do with EPS files and grey boxes resulting from their preview.

Grammar Checker

forums_noreply@adobe.com — Mon, 04 Dec 2000 20:53:12 GMT

Revised:

There is a grammar-checker plug-in called MAXit FrameMaker from Smart Communications at http://www.smartny.com

For the FM specific version, see the product info PDF at http://www.smartny.com/sm_maxframe.pdf

Sean's original posting:

There isn't one. We could debate the pros and cons of this, but debate alone won't change things, so we won't.

Submitting a Feature Request

forums_noreply@adobe.com — Tue, 10 Dec 2002 16:24:39 GMT

You can submit ideas for new features that you would like to see in FrameMaker at the following url:

http://www.adobe.com/support/feature.html

Reporting a bug

forums_noreply@adobe.com — Tue, 10 Dec 2002 16:21:52 GMT

If you suspect that you've come across a bona fide "bug" in your version of FrameMaker (i.e. a repeatable and consistent behaviour that is not as expected or documented), then you can report this using the following url:

http://www.adobe.com/misc/bugreport.html

Missing Fonts Error

forums_noreply@adobe.com — Thu, 15 Mar 2001 13:31:57 GMT

A lot of people post questions or frustrations about missing font errors in FrameMaker. FrameMaker reports missing fonts because it can be a big expensive deal if you miss the mistake when going to press.

Blank Page Issues in FrameMaker

forums_noreply@adobe.com — Wed, 09 May 2001 12:40:24 GMT

This thread addresses the prevention and removal of unwanted blank pages in FrameMaker.

Sean

A general online resource

forums_noreply@adobe.com — Thu, 18 Jul 2002 17:33:56 GMT

At http://www.techknowledgecorp.com/help you will find general online help for Frame. The first thing that comes up is a set of info such as commands you may find handy or hex codes you can use in dialog-box fields. Note that the site uses frames.

Along the left side you will find specific how-to topics and other time-saving tips.

Interfacing with Microsoft Word

forums_noreply@adobe.com — Mon, 04 Dec 2000 21:00:29 GMT

Issues with taking Word to FrameMaker, FrameMaker to Word, and troubles with the Word and RTF import/export filters abound.

Setting Up Acrobat 5/Distiller 5

forums_noreply@adobe.com — Fri, 21 Jun 2002 20:49:36 GMT

The content of this thread comes from a collection of information mostly provided by Dov Isaacs on the Framers forum, .

Screen Captures Exposed

forums_noreply@adobe.com — Wed, 09 May 2001 17:20:21 GMT

This thread attempts to tackle the issue of screen captures in FrameMaker.

Please post questions about screen captures to the FrameMaker forum outside the FAQ thread using Add Topic. http://www.adobeforums.com/cgi-bin/webx?14@@.ee6b312
Please, post corrections and suggestions to the FAQ Corrections and Suggestions thread: DorothyK "FAQ Suggestions and Corrections" 5/9/01 7:12am.

Screen captures are a basic part of technical writing and even non-technical writers, who use FrameMaker to write about software, will more than likely end up using screen captures.

This thread attempts to clarify issues about screen captures. This thread concerns itself primarily with screen captures of software, not the screen capture of things like photographs.

Please post questions about screen captures to the FrameMaker forum outside the FAQ thread!http://www.adobeforums.com/cgi-bin/webx?14@@.ee6b312

FM 6 and Windows XP

forums_noreply@adobe.com — Thu, 28 Feb 2002 13:51:48 GMT

Issues with FM 6 and Windows XP.

FrameMaker 6.0 A.C.E. Test

forums_noreply@adobe.com — Fri, 19 Oct 2001 12:36:29 GMT

I've seen quite a few questions about the FrameMaker 6.0 A.C.E. test, but nobody seems willing to really talk about it. I have seen no prohibition from outlining the scope of this test, so here are my experiences.

Sean

sean.brierley@jenzabar.net

Color and FrameMaker

forums_noreply@adobe.com — Mon, 04 Dec 2000 21:03:14 GMT

This thread addresses color issues in FrameMaker.

Using the User to User Forums

forums_noreply@adobe.com — Mon, 04 Dec 2000 20:44:26 GMT

A note about the User to User Forums: Adobe does not maintain an offical support presence here. Questions are fielded by FrameMaker users who stop by between times to ask or answer questions. Please consider:

Escalating your support questions through official Adobe channels if your question warrants such. For example, if no one in the U2U forums can successfully answer your need.
Do search before you post a question. If the search yields no help, or too much irrelevant information, such that the search is unusable, feel free to post a new topic. To search only the forum that you are in (i.e. only FrameMaker), make sure to select this option button: Search forum messages only under the current topic (otherwise, you'll get results from all forums).
Do not post unrelated new questions in an existing thread. This is considered rude behaviour and detracts from the answers the initial poster receives.
Do post new questions as a new thread by clicking Add Topic in the main window of the FrameMaker or FrameMaker+SGML forum.
Do not post the same question several times in the same day. Especially, do not post the same question as a new topic and as additions to one or more existing threads. Spamming in this way is also rude.

Agreed, if your topic goes for several days without being answered, you might want to post a follow-up question in that topic. By reposting to the topic, the topic will jump to the top of the list for those who rank messages by date posted. Also, reposting to the same message will cause the topic to appear in message centers of those who subscribed to the forum.
If no one answers your post or question, it might be that no one has an answer. See #1.
For questions about non-FrameMaker software, go here: http://www.adobe.com/support/forums/main.html.
For questions about the forums themselves, not Adobe Software, such as questions about the layout or speed of the forums, go here: http://www.adobeforums.com/cgi-bin/webx?14@@.ee6b30e.

Books about FrameMaker

forums_noreply@adobe.com — Mon, 04 Dec 2000 21:01:50 GMT

"FrameMaker 5.5.6 for Dummies," by Sarah O'Keefe and IDG books. This has not been updated to FrameMaker 6 but it is close enough to still be useful.

"The Masters Series: FrameMaker 6," by Thomas Neuburger. Check out http://www.frameusers.com if you want to look into this. Thomas Neuburger authored a popular book for FrameMaker 5, also, but not FrameMaker 5.5.x.

"Adobe FrameMaker 6 Classroom in a Book," by the Adobe Creative Team (yup, Adobe itself). A tutorial-based book. This book is also available for earlier versions of FrameMaker.

PageMaker / InDesign / Quark and FrameMaker

forums_noreply@adobe.com — Mon, 04 Dec 2000 22:20:01 GMT

This thread considers FrameMaker and its relationship, if any, to PageMaker, InDesign, and Quark.

WebWorks Publisher and Online Help

forums_noreply@adobe.com — Mon, 04 Dec 2000 20:50:33 GMT

This thread, or topic, deals with both Quadralay's WebWorks Publisher Pro and WebWorks Publisher SE.

A late add-on is general online-help creation information (which I may split out if the topic is received with unbridled enthusiasm).