MicroType

"The most comprehensive and current FrameMaker resource, outside of the Adobe site" (Keith Soltys, Essential Resources for FrameMaker Users)

  

 


Resources: FAQ | FM Bugs & Issues | Templates | Tutorials | Articles | PDF Best Practices | Acrobat 6-8 Issues | Miscellaneous

FrameMaker Annoyances: Bugs & Issues (Version 2.76)

Bugs and issues and workarounds/solutions appearing in this list were collected from dusty corners in Adobe's Support Knowledgebase (some of these are currently non-functional) and from FrameMaker users. MicroType is not responsible for bug/issue descriptions, suggested workarounds and fixes -- Shlomo

Bug. A defect or fault in a machine, plan, or the like. Orig. U.S. "1889 Pall Mall Gaz. 11 Mar. 1/1 Mr. Edison, I was informed, had been up the two previous nights discovering 'a bug' in his phonograph -- an expression for solving a difficulty, and implying that some imaginary insect has secreted itself inside and is causing all the trouble." Oxford English Dictionary, 2nd Edition

Your bug submission, input and comments will help make it more comprehensive and useful and keep it accurate and updated. You are welcome to submit your own bugs/issues (please include workarounds and links to additional information, if available).

    • When producing sample files, if applicable: How to disguise confidential or proprietary text (ATN 311711)
    • For information on FrameMaker internal error numbers & the FrameLog file, see ATN 327050
    • Mac OS X Compatibility with FrameMaker, FrameMaker+SGML, and FrameViewer? see ATN 326100
    • FMSGML indicates FrameMaker+SGML 5.x, 6.0 or Structured FrameMaker
    • Bugs/issues specifically relating to FrameMaker versions earlier than 5.0 are not included in this list
    • Adobe's Support Policy for FrameMaker 6.0 and earlier versions running under WinMe or XP: ATN 320847
    • Considering an upgrade? Read "Knowing When to Upgrade Software" by Deborah and Eric Ray
    • You may also consult the FrameMaker FAQ.

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | FM 9.0 | Filters | PS Drivers | Documentation

FrameMaker 5.0-5.2, All Platforms

FrameMaker 5.0 released end of 1994, Adobe-branded FrameMaker 5.0 released early 1995

FrameMaker 5.0-5.1.2, Windows

FrameMaker 5.0-5.2, Mac

FrameMaker 5.0-5.1.2, Unix

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | FM 9.0 | Filters | PS Drivers | Documentation

FrameMaker 5.5.0-5.5.3, All Platforms

FrameMaker 5.5.0 released August 1997; FrameMaker 5.5.3 released February 1998

Note: See also issues present in previous releases of FrameMaker, as they may also apply to FrameMaker 5.5.x (unless indicateds otherwise)

FrameMaker 5.5.0-5.5.3, Windows

FrameMaker 5.5.0-5.5.3, Mac

FrameMaker 5.5.0-5.5.3, Unix

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | FM 9.0 | Filters | PS Drivers | Documentation

FrameMaker 5.5.6, All Platforms

released October 1998

Note: See also issues present in previous releases of FrameMaker, as they may also apply to FrameMaker 5.5.6 (unless indicated otherwise)

FrameMaker 5.5.6, Windows

FrameMaker 5.5.6, Mac

FrameMaker 5.5.6, Unix


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | FM 9.0 | Filters | PS Drivers | Documentation

FrameMaker 6.0

FM6.0p357, released April 2000

Note: See also issues present in previous releases of FrameMaker, as as they may also apply to FrameMaker 6.0 (unless indicated otherwise)

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | FM 9.0 | Filters | PS Drivers | Documentation

FrameMaker 7.0 (mostly Windows, may apply to other platforms)

FM7.0p492, released May 2002

Note: See also issues present in previous releases of FrameMaker, as they may also apply to FrameMaker 7.0 (unless indicated otherwise)

FM7.0-specific issues present in 7.0p578:

  • (fixed in FM7.1) Distilling fails consistently when a "message openfile" hypertext marker is used and Tagged PDF information is enabled:
    %%[ Error: typecheck; OffendingCommand: pdfmark; ErrorInfo: PUT _objdef ]%%
    Workaround: turn off Generate Tagged PDF in PDF Setup
  • (fixed in FM7.1, broken in FM7.2) File Info values (File > File Info) are reset when importing formats from other documents with the Document Properties category turned on.
  • After opening Word or RTF documents in FrameMaker each paragraph ends with an invisible but selectable Carriage Return character.
    Workarounds: (1) Do a find/replace in FrameMaker, searching for "\x0d" (without the quotes), replacing with nothing. (2) Saving the file as MIF also removes those characters. [Michael Müller-Hillebrand]
  • Book-wide searches may crash FrameMaker.
    Workaround: open all the files in the book before finding and replacing.
  • Save as PDF function does not report switching of drivers – output may not match current FrameMaker layout (line breaks, page breaks) or reflect missing fonts.
    A sample file (65K) has a FrameMaker document with a few lines that are split differently when different drivers are activated (eg AdobePS 5.2+Adist5.ppd and HP LaserJet 2200 Series PCL6); movie [AVI, 448K]
  • Incorrect paragraph format displayed in the paragraph drop-down box in the formatting bar or in the status bar (ATN 327771);
    demonstration (AVI) of how this happens in a new document (consistently repeatable)
    Fixed in FM7.2b144.
  • Distilling may fail when creating PDFs or distilling PS files with Tagged PDF information:
    (%%[ Error: undefined; OffendingCommand: pdfmark; ErrorInfo: StRetrieve P127021 ]%%
    Stack: /StRetrieve) ...
    Workaround: turn off Generate Tagged PDF in PDF Setup
  • When creating a tagged PDF and generating bookmarks from structure in Acrobat, the resulting bookmarks only show tag name (but no specific text).
  • Dialog boxes (eg Designers, Conditional Text) can be resized, but without affecting items -- either showing a larger gray empty area (without items being rearranged), or causing items to be cut/missing
  • Word97+ and RTF import filters are no longer installed using the [Filters] section of the maker.ini (they are commented). There is a filters/sangam/ folder which contains "Readers" and "Writers" obviously controlled by the Sangam.dll ("Adobe India Sangam Core Code") inside the installation folder. "I had a situation where I wanted to open a folder full of RTF files directly in FrameMaker using FrameScript and now could not specify the FilterId. I finally suppressed the User Notification to have a batch process with interruption." [Michael Müller-Hillebrand]
  • Can't save FrameMaker 7.x files in Microsoft Word 6.0 or 7.0 (.doc) format (ATN 332443)
  • FMSGML: Bookmarks for elements which use a Run-In Head setting include text from following element.
  • FMSGML: Hierarchy cannot be specified for bookmark levels when bookmark source is "elements".
  • When converting a FrameMaker [578-specific] book to PDF: default opening page in PS/PDF may be incorrectly set to be the first page of last chapter in a book; in other cases, the value in the "Open PDF Document on Page" field is ignored, and 1 is used by default (first page in first chapter, which may inappropriate if you have front-matter items). [The standard Ecology book (samples/overview/book) can be used to demonstrate these problems].
    Workarounds:
    (1) Modify the individual PDF in Acrobat (File > Document Properties > Open Options, Page Number)
    (2) Add a command controlling the opening page to the epilogue.ps file, so that all distilled files will be affected:
    [ /PageMode /UseOutlines /Page 1 /DOCVIEW pdfmark
    (3) Specify the opening page/destination through the Defaults Assistant (TimeSavers add-on)
  • Switching to documents by clicking the corresponding entry in the book window may not be possible if the Paragraph Designer or Table Designer are open.
  • When reading a FM7 MIF file, FrameMaker ignores some of the PDF Setup settings.
  • Microsoft Intellimouse Scroll wheel may lock up FrameMaker when it is pressed or scrolled.
    Workaround: minimize FrameMaker and then restore it [Rick Henkel]
  • Using FM 7.0/Win2000 with MS Outlook 9.0.0.4527 and MS ActiveSync 3.5 leads to an internal error in FM 7.0 [7004, 5899370, 7569858, 7568538] when copying/cutting from an FM 7.0 file. To reproduce the bug: (1) open a new FM file; (2) copy something from MS Outlook to FrameMaker; (3) copy another something from MS Outlook to FM; (4) In FM, triple-click to copy the entire paragraph from (2).
    Workarounds:
    (1) Closing MS Outlook and restarting Frame allows Frame copying function to resume temporarily if and only if MS ActiveSync is in dormant mode (associated PDA is disconnected).
    (2) If one is careful to avoid copying paragraph markers in FM, then the error can be postponed.
    [Jason Aiken]
  • Results of "Bookmarks Expanded through Level" settings may be inconsistent; "268435453" may be displayed instead of All, None or Default.
    Workarounds:
    (1) Type a number in the Bookmark Expanded through Level box, indicating the bookmark level.
    (2) Use the CollapseBookmarks function (TimeSavers/Bookmark Controller).
    (3) If you need help collapsing bookmarks manually in Acrobat, use the free PlanetPDF Collapse Bookmarks Plug-in.
  • Error When Creating a WebWorks Project in FrameMaker 7.0/Win (ATN 328048)
  • Win98: Custom page sizes may be cropped incorrectly when using Save as PDF
    Workaround: Print to a PS file and distill.
  • Win98: Text in rotated table cells becomes "invisible" if it uses a PostScript font (ATM4.1.1) -- format with TrueType fonts instead
  • Results of importing Word2000 files in .doc format may be unexpected -- showing wrong fonts, extra and missing letters.
    Workaround: try importing RTF files. [Michael Müller-Hillebrand]
  • German version: "Warnmeldung" is inserted in Hypertext marker instead of "alert"
  • Equations Have Wrong Symbols in FrameMaker 7.0/Win after you change the default printer or save as PDF (ATN 328011)
  • Inconsistent PDF default opening mode -- PDF may open in "Page Only" mode even though bookmarks are created (/DOCVIEW not included in PS file generated by FrameMaker)
  • FrameMaker 7.0 Doesn't Recognize Changes Made to the Maker.ini File (ATN 327344)
  • Custom Pages Are Rotated in a PDF File Created from FrameMaker 7.0 in Win98/ME (ATN 327421)
  • Acrobat 4.05 Is Missing After You Install FrameMaker 7.0/Win (ATN 324615)
  • Stroke Lines in CGM Graphics Don't Print in FrameMaker 7.0/Win Documents (ATN 328016)
  • Group4 fax encoded TIFF files are not displayed or printed correctly.
  • Embedded TIFF images slow the display significantly.
  • When opening file.sgm, FrameMaker displays the Unknown Filetype dialog box.
  • FMSGML: Marker Text is Included in Bookmarks from Elements
  • FMSGML: Spelling checker may skip elements, loop around elements, or not respond.
  • FMSGML: Marker element may be included in PDF bookmarks, merged with previous headings, even though they are listed under "don't include".
  • FMSGML: Space in the name of root element in a DTD causes an error

Apply Master Pages function:

  • Apply Master Pages function ignores paragraphs in tables (body, heading rows or title), footnotes, text frames in anchored frames
  • When a master page is triggered by an element, "Span pages" refers to pages spanned by the first paragraph of the element, not to pages spanned by the entire element. [Lynne A. Price]
  • When "Span pages" is specified and a page break occurs immediately after the triggering paragraph (or the first paragraph in the triggering element), FrameMaker applies the specified master pages to all pages of this paragraph and to the following page. [Lynne A. Price]
  • When File > Utilities > Convert Structured Documents is used to create FrameMaker documents from all SGML or XML documents in a directory, FrameMaker does not apply master pages. [Lynne A. Price]
  • Formatting and context labels in a structured book can be determined by elements and attributes in the book file as well as those in the individual book components. When import of an XML or SGML document causes FrameMaker to create a book, it applies master pages before considering the book structure. In particular, the context label for an element in a document may be determined by an attribute on the highest-level or other element in a book. The context label may be used in the master page map. Since the context label will not have been set when FrameMaker applies master pages, the results will be incorrect.
    Workaround: reapply master pages after opening the original XML or SGML document. [Lynne A. Price]

Fixed in version 7.0p578 (downloadable patch, Windows):

  • FrameMaker often crashes when printing books with Acrobat data (error: 7004,6055410,7657059,0)
    Workarounds:
    (1) Open the first chapter in the book (or the chapter which has the opening page, as specified in the PDF Setup, Settings, Open PDF Document on Page).
    also see ATN 328769, Internal Error "...7004, 6055410, 7657059, 0" When You Save or Print to Adobe PDF from FrameMaker (7.0 on Windows)
    (2) in the PDF Setup dialog box, Bookmarks tab, type 1 in the Bookmarks Expanded Through Level field.
    also see ATN 318572: Error "7004, 6055410 . . ", Crash, or Options for Bookmarks Aren't Retained in FrameMaker 7
  • Results of "Bookmarks Expanded through Level" settings are inconsistent; "268435453" may be displayed instead of All, None or Default; a value of 0 may crash FrameMaker (error: 7004, 4379400, 6666635, 6666549).
    Workarounds:
    (1) Type a number in the Bookmark Expanded through Level box.
    (2) Use the CollapseBookmarks function (TimeSavers/Bookmark Controller).
    (3) If you need help collapsing bookmarks manually in Acrobat, use the free PlanetPDF Collapse Bookmarks Plug-in.
  • Error "Cannot display some imported graphics..." in FrameMaker 7.0 Document with TIFF Images Imported by Reference (ATN 325394)
  • "The maximum number of commands for all FM API Clients has been increased to 2017 in FrameMaker 7.0P578. Previously the limit was 250. Beyond this limit a client will be able to add a menu item but it will not be able to receive the command when user presses that menu item." (quoted from ReadmeForPatch.txt, #584073)
  • "FrameMaker 7.0 adds xml:space attribute to an element and all it's children if the element has preserve line break rule specified in the read write rules file. Some times FrameMaker 7.0 adds multiple xml:space attributes to a single element. This was making the XML invalid as the DTD was not containing the xml:space attribute. This issue has been resolved in this patch release. FrameMaker 7.0P578 will not be adding xml:space for preserve line breaks rule applied to any element and its child elements. This is because preserve line breaks applies only to the element for which it is defined whereas xml:space is applied for children also. This means the two are not equivalent." (quoted from ReadmeForPatch.txt, #584083)
  • "In the DTD, an attribute can have a declared default value and also have an optional #FIXED keyword which means that the attribute must have the same default value that is declared in the DTD. In both these cases, FrameMaker 7.0 writes out these attributes to elements even though the element does not have the attributes specified in the input XML or the Frame structured document. This was working fine for SGML saving, but not for XML, and this has been fixed in this patch release." (quoted from ReadmeForPatch.txt, #584172)

U.K.-English Templates Update for FrameMaker 7.0p492: Windows, MacOS

Fixed by the Word/RTF/Excel Filter update (Win, MacOS, apply to FM7.0p576):

  • Word import (all languages): The filter deletes the first letter of the footnote description if there is no space after the footnote number
  • Word and Excel import, RTF import and export (Japanese only): The filter drops table border formatting
  • Word and Excel import, RTF import and export (CCK only): The filter translation of CCK characters results in garbage displayed.

Fixed in version 7.0p576: (downloadable patch, Windows, MacOS or Unix; see Adobe's list of bugs fixed in this patch -- English, German, French or Japanese):

The ReadMeFirst.html file found in the FM7 installation folder has more information on the following issues:

All platforms:

  • FMSGML: Core Element Hierarchy Indicator not Preserved across Languages (504367)
  • Apply Master Page table names are localized and will be duplicated across language versions (512646)
  • New date building blocks: <$currenttime>, <$modificationtime>, <$creationtime> (513145)
  • SVG facets appear differently on different platforms when imported by reference (496221)
  • FMSGML: The "pgwide" and other attributes on elements other than CALS table elements are dropped when opening or importing a DTD into an EDD (255731)
  • The read/write rule 'fm property dpi value' doesn't do anything (452193)
  • Processing instructions following the root element are ignored, and will cause a spurious error (498134)
  • Line spacing and display may be incorrect if Bold versions of fonts are not available, but Bold Italic versions are (501905)
  • FMSGML: FrameMaker may lose memory doing batch conversions of SGML documents (514700)
  • "reader character map is" rule does not apply to XML (469916)
  • Elements with namespace identifiers lose their colons when saved to XML from FM+SGML 6.0 (510757)
  • The root element name of an XML or SGML document and DTD may only use ASCII chars (512720)
  • XMLCss feature is available but obsolete in FrameMaker 7.0 (513485)
  • FMSGML: Element names in XML are limited to 255 bytes or less (500498)
  • Doc Compare with documents containing XML CDATA sections reports wrong differences in the composite document (515837)
  • Differing definitions of XML parsing error positions (515013)
  • Attributes defined with a default string containing only whitespace are treated as empty values (499685)
  • Use <No Application> when saving changes made to XML text insets (492905)
  • Picture bullets from Microsoft Word XP are not imported correctly (497458)
  • Paragraph styles other then Normal with overrides will not show the override asterisk in FrameMaker (503793)
  • Files saved as RTF and imported into FrameMaker or opened in Word loses Overline attribute (516363)

Windows

  • FrameMaker 7.0 documents may show FrameMaker 6.0 icons after installing FrameMaker 7.0; opening them will launch FrameMaker 6.0 (497761)
  • Additional keyboard navigation for Formatting Bar and Quick Access Bar (514635)
  • Applications creating PDF with Custom Page Sizes on Win98 or ME may get rotated pages in the PDF file (511538)
  • FrameMaker will crash if the splash screen is turned off and Help > About is selected (507486); see FrameMaker 6.x or 7.0 Crashes in Windows if You Choose Help > About FrameMaker (ATN 327291)
  • Opening Microsoft Office for Macintosh files with Import by Reference Graphics may display \BadFileName (510332 514182)

Mac

  • "FrameMaker PDF Writer" desktop printer use (508261 516227)
  • Save As PDF error on Mac with the LaserWriter printer driver selected (516068)
  • Damaged aliases may cause problems (510980)
  • Hidden Acrobat installation dialog may appear to be a system hang (512377)
  • Supported web browsers for Online Help, XML display (513443 514063)
  • First page too small when creating PDF files (516152 500198)
  • Set PlugIns path in CodeWarrior project for DocBook/xDocBook sample clients (512247)
  • Missing filename not always displayed in Missing File window for Import by Reference graphics (501512)
  • URL Access extension required for FrameMaker 7.0 (515807)
  • Additional memory requirements for large XML documents or large DTDs (470390)

Unix

  • Correction needed for "Enabling Asian Language Features" alert (411811)
  • xresources of the form makersgml.* no longer work; use Maker.* instead (453785)
  • FrameMaker will crash if read permissions are removed from Symbol font files in $FMHOME/fminit/fontdir (470171)
  • Initial launch times for FrameMaker 7.0 may be longer than previous versions (470324)
  • Understanding where FrameMaker looks for fonts (513775)
  • Updated patch requirements for FrameMaker 7.0 running on HP-UX (488998)
  • Improper exit, hang on second launch, or hang when printing with FrameMaker 7.0 (516014)
  • fmtooltalk is no longer supported for Solaris OpenWin or AIX CDE (494719)

FrameMaker 7.0, Unix

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | FM 9.0 | Filters | PS Drivers | Documentation

FrameMaker 7.1 (mostly Windows, may also apply to Solaris)

FM7.1b023, released January 2004; see Adobe's list of bug fixes implemented in FrameMaker 7.1

Note: See also issues present in previous releases of FrameMaker, as they may also apply to FrameMaker 7.1 (unless indicated otherwise)

Fixed in version FM7.1p116 (released March 2005; downloadable update, 52.6MB):

 

 

 

 

 

 

 

 

 

 

 

 

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | FM 9.0 | Filters | PS Drivers | Documentation

FrameMaker 7.2 (mostly Windows, may also apply to Solaris)

Note: See also issues present in previous releases of FrameMaker, as they may also apply to FrameMaker 7.2 (unless indicated otherwise)

FM7.2b128, released September 2005; see Adobe's description of New Features (PDF: 245K), Reviewer's Guide (PDF: 3.07M)

  • (fixed in FM7.2p158) Structured FrameMaker: Cannot delete the value of a required attribute
    When trying to delete the value of a required attribute from an element in FM7.2, the normal procedure is followed (and the standard warning is displayed), a confirmation is given... yet the attribute is left unchanged and it is not deleted. Using the same steps in FM7.1 or earlier does produce the expected result.
  • (fixed in FM7.2p158) In FM 7.1, 7.0 and 6.0 it is possible to drag files from a Windows Explorer window onto a FrameMaker book window to add files to a book. This also avoided the problem where (often) the files get added in the wrong order when clicking the "Add file to book" button . In FrameMaker 7.2, attempting to drag from an Explorer window has no effect, so the only option is to use the "Add file" button. [Jon White]
    Drag and drop doesn't work when you drop... (ATN 326392)
  • FrameMaker crashes when rotating an object using the mouse (Alt-drag), if it is a group of items and in the course of rotating, part of the object goes off-screen temporarily. To reproduce, open the Transport.fm file from the clip art library, go to page 2; select the ship, and Alt-drag a corner handle to rotate the object (error code: 7204, 6107874, 7775428, 0)
  • Control-drag to copy an object cannot be undone and clears the history stack; use Alt-drag instead.
  • (was fixed in FM7.1, but resurfaced in FM7.2) File Info values (File > File Info) are reset when importing formats from other documents with the Document Properties category turned on.
    Note: A new entry can be added to the Preferences section in maker.ini file in FM7.2p158 to control this behavior.
    See also: File Info metadata values are not imported from one document to another in FrameMaker (ATN 331895), where this problem is described as a feature
  • Imported CGM files are smaller than expected (ATN 331867)
  • Font size drop-down in the formatting bar (new in FM7.2/Windows) supports a limited set of font sizes (7, 9, 10, 12, 14, 18, 24, 36) and therefore may not reflect the text size at the cursor location (showing "Other" if the current size is not one of the supported set, or if there is a mix of sizes in the selected area).
  • Font choice drop-down in the formatting bar (new in FM7.2/Windows) shows the first font in the alphabetical list of fonts available when current selection has multiple fonts; names of CJK fonts may be displayed with additional non-text characters.
  • Understanding Multiple Undo (ATN 331774)
    The following commands clear the history palette: Print, Save, SaveAs, Revert, ImportFile (when an anchored frame is selected or if placed directly on a page), ImportFormats, DocumentNumbering, CombinedFonts, PageAdd, PageDelete, ColumnLayout, PageSize, Pagination, MasterPageUsage, UpdateColumnLayout, NewMasterPage, FreezePagination, ConnectTextFrames, CutBoth, EditMarkerTypes, ColorViews, ViewSeparation, AtomizeInset, SwapRedBlue, ColorDefinitions, DeleteWordFromDocDict, EditRulingStyle, ImportElementDefns, Update, NormalizeTags, InclusionElementGrouping, EditLinks, BookRenameFile
  • History palette is blank (ATN 331866)
  • Disable or enable the clear history stack warning (ATN 331868)
  • Troubleshoot errors or freezes during installation (ATN 331828)
  • ICU 2.8 libraries required to compile a mapping file into a binary converter file (ATN 322830)
  • Install and remove FrameMaker 7.2 and Acrobat Distiller 7 using the command line (ATN 331867)
  • Find/Change operations often cause a crash when searching for text and replacing "By Pasting", with a graphic item in the clipboard (internal error: 7204, 6964849, 6960269, 6966005); the same operation is successful in earlier versions of FrameMaker.

FM7.2b144 (released December 2005; downloadable update, 37.3MB); the ReadmeForPatch144.txt file reports the following fixes:

  • #1244994: FrameMaker 7.2b128, while adding TOC in book, adds an entry in the history palette of structured book, even if the operation is cancelled.
  • #1244610: FrameMaker 7.2b128 generates invalid content when exporting UTF-16 encoded XML.
  • #1244390: FrameMaker 7.2b128 makes the paragraph tag definition incorrect, if pgf unify command is applied twice with selection in different paragraphs and the second unify command is undone.
  • #1244353: The Set on "Numbering Properties" clears the undo history even on cancelling the action.
  • #1239625: FrameMaker 7.2b128 crashes when you rotate an object using the mouse (Alt-drag).
  • #1236151: FrameMaker 7.2b128 crashes/hangs/takes lot of time, when exporting XML in the case when the relative path of the DTD/Schema w.r.t. the output folder is greater than the absolute path of the DTD/Schema.
  • #1234318: In FrameMaker 7.2b128 Undo of color change does not work if a graphics group has a textline object in it.
  • #1232166: In FrameMaker 7.2b128, Undo of Split element leads to invalid structure. Undo all commands after that leads to a crash.
  • #1230468: In FrameMaker 7.2b128, UNIX: API clients are not getting initialized if language parameter passed is in uppercase.
  • #1225193: In FrameMaker 7.2b128, insert an image element in DITA template (at a location where it is valid with any graphic doc) and save the template as XML. Saved document has dpi and nsoffset attributes which are not defined for image element. Hence graphic object does not round trip.
  • #1225150: In FrameMaker 7.2b128, DITA: Online manuals should include DITA_Starter_Kit.pdf document for details of DITA application.
  • #1225114: In FrameMaker 7.2b128, Clicking on apply master page usage without changing anything clears Multiple undo history without any warning
  • #1224317: EPV: Moving anchor frame from outside the text frame into the text frame, does not get undone after some move and undo of graphic objects.
  • #1221337: FrameMaker 7.2b128 can not open primary document, if the filepath/stylesheet contains characters like "???"
  • #1221290: FrameMaker 7.2b128 FrameMaker Crashes if Undo-Redo is done after Drag and Drop of Book Component.
  • #1204754: FMR: Xalan:write extension should be provided with FrameMaker 7.2.
    The Xalan namespace "http://xml.apache.org/xalan" is used for namespace of the write extension element. The "write" element can have a file attribute and/or a select attribute to designate the output file, a method attribute to identify the method that should be used for outputting the subsidiary output file. The method attribute is optional.
    The file attribute takes a string which can be used to directly specify the output file name. The select attribute takes an XPath expression or a stylesheet parameter which allows dynamic generation of the output file name. If both attributes are used, the "write" extension first evaluates the select attribute, and falls back to the file attribute. The "write" extension element opens the specified file, writes to it using the output method specified in its method attribute, and closes the file at the end of the element.
    The following example shows the usage of this element in a stylesheet.
    Stylesheet Example:
    <?xml version="1.0" encoding="UTF-8" ?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xalan="http://xml.apache.org/xalan" extension-element-prefixes="xalan">
    <xsl:template match="/">
    <p>
    Hello from the main file.
    <xsl:comment>This is a comment in the main file.</xsl:comment>
    <xalan:write file="sub.html" method="html">
    <sub>
    <xsl:comment>This is a comment in the new file "sub.html".</xsl:comment>
    </sub>
    </xalan:write>
    </p>
    </xsl:template>
    </xsl:stylesheet>
  • #1245829: In FrameMaker 7.1p116, When "convert referenced graphics; export to file" rule is used, all the graphic files present within xml are exported in a specified format but the exported xml file refers to the original graphic file paths. Hence when you open the exported file, you will get the missing graphics dialog.
  • #1244634: FrameMaker 7.1P116 and earlier versions removed the pgfReferenced tag from MIF when a paragraph containing marker for named destination is deleted and then undone.
  • #1236208: FrameMaker 6.0 and later do not show the current Paragraph Format Name in the formatting toolbar.
  • #1219618: EPV: File attribute not generated when saving graphics to XML.
  • #1215327: structapps.fm does not include Schema in default application definition content model.
  • #1211754: EPV: French: URI notation not coming in XML files.
  • #1202191: When using the Find/Change box on to do a search and replace across a book, Internal Error occurs. [note]
  • #1165638: Command !pu (Update Page layout) places the insertion point into another text frame with same flow tag but not autoconnected.

FM7.2p158 (released April 2006; downloadable update, 39.5MB); the ReadmeForPatchp158.txt file reports the following fixes and corrections:

  • #0655371: Tagged PDF not getting generated for a book when option to generate separate PDFs is not checked
  • #1199273: CodePoint Correction: Support added for few missing characters on Cyrillic, Central European and Baltic Codepages for Windows.
    "Please note that we haven’t added full support for these codepages. We have just enabled these codepoints. You can enter these characters in a document and use them only for display/print and pdf creation. You, however still can’t use these characters for pdf bookmarks or save as html or save as xml. These codepoints are also not supported with WebWorks Publisher Standard Edition 8.0 and for RTF Import/Export. You can’t copy/paste these characters to/from other applications. Also, there is no dictionary or spell-check support for the languages supported by these code pages."
    (for additional details, see ATN 332864 for details; a message by Stefan Genz)
  • #1239618: When importing formats from one document to another, with the "Document Properties" category turned on, File Info items (such as Title) are reset as a result.
    The boolean flag "CopyFileInfoOnImport" can now be used in maker.ini (valid values: on/off) or .fmpreferences (valid values: true/false) to allow/disable import of File Info.
    (see "solution 3" in ATN 331895)
  • #1243985: FrameMaker 7.2b144 crashes on undo of import of 4th object.
  • #1248348: After importing an xml file, a vertically straddled cell in a table is not generated correctly when the table is forced across pages. If the table is forced into one page it is generated correctly.
  • #1249265: In FrameMaker 7.2b144, Undo of UpdateAll removes the table catalog entry from the table catalog.
  • #1249268: In FrameMaker 7.2b144, Undo of GlobalUpdate removes the table catalog entry from the table catalog.
  • #1253783: In FrameMaker 7.2b144, some CGM files from ISODraw import gives smaller dimensions than in 7.1 or 7.0 (or 6).
    (see ATN 332605 for details)
  • #1259520: In FrameMaker 7.2b144, you could not drag and drop files from windows explorer onto the FrameMaker book window.
  • #1260794: In FrameMaker 7.2b144, DITA/Samples/Concepts/garageconceptsovervi should be renamed to garageconceptsoverview.xml.
  • #1263600: If you roundtrip an xml document that uses a schema with higher ASCII characters in FrameMaker 7.2b144 using "no application", you get a "file does not exist" error during import.
  • #1263959: In FrameMaker 7.2b144, if you have the character "ƒ" within filename/filepath of xml file and you open this XML with a StyleSheet, FrameMaker does not open the file.
    Note: A similar issue is present for character "¥".
    Xerces replaces "¥" with slash and hence you should not use "¥" in your filename/filepath.
  • #1264951: In FrameMaker 7.2b144, History palette displays garbage text for "Delete Text" in Japanese version.
  • #1265686: In FrameMaker 7.2b144, attribute value deletion failed if the attribute is declared as #required.
  • #1265695, #1265699: In FrameMaker 7.2b144, when you import or export an XML file the DTD will be searched in the following order: $HOME, $SRCDIR, $STRUCTDIR. Hence if you have a "<!DOCTYPE root SYSTEM "./a.dtd">" and a.dtd also exists in your $HOME then the one in $HOME will be picked.
  • #1273612: In FrameMaker 7.2b144, an underline and strikethrough is applied when an equation is exported to RTF
  • #1266621: FrameMaker 7.2b128 and & 7.2 Updater can not be installed with Korean language settings on Chinese OS.
  • #1250031: In FrameMaker 7.1, In "Save As", when you select MicroSoft Word * options, the file gets saved with .msw extension.
  • #1207612: In FrameMaker 7.1 WMF/EMF import filter is weak -WMF couldn't be imported.
    (listing of maker.ini entries related to the WMF filter omitted -- please consult the readme file after applying the patch)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | FM 9.0 | Filters | PS Drivers | Documentation

FrameMaker 8.0 (mostly Windows, may also apply to Solaris)

FM8.0p236, released August 2007

Note: See also issues present in previous releases of FrameMaker, as they may also apply to FrameMaker 8.0 (unless indicated otherwise)

  • (fixed in FM8.0p273) Cross-file links in PDFs authored in FrameMaker 8.0 use Unicode-encoded file paths and file names, which are only supported in Windows Acrobat/Reader 8.x or MacOS Acrobat/Reader 7.x or later, when the PDF files are accessed locally.
    [Sample web-based PDFs, all distilled with Distiller 8.1: authored with FM8, authored with FM72; authored with FM8 + TimeSavers 5.5, with Unicode-encoded links converted to regular links]
    • When Unicode-encoded cross-file links are accessed through a web browser, including with Acrobat/Reader 8.x, an error message is displayed: "There was an error while performing an action. Attempt to call a method that has not been implemented".
    • When Unicode-encoded cross-file links are accessed locally using earlier Acrobat/Reader versions, the following message is displayed: "There was an error opening this document. The path does not exist".
    • In some cases, Unicode-encoded cross-file links trigger the following message upon opening in Acrobat/Reader versions earlier than 8: "This file appears to use a new format... Adobe recommends that you upgrade to the latest version of our Acrobat products...".
  • (fixed in FM8.0p273) Hyphenation does not work as expected when words include accented letters (incorrect hyphenation; prefix/suffix values not respected).
  • (fixed in FM8.0p273) Quick selection of paragraph/character tags, variables and conditions (e.g. with F8 or F9, Control-8, Control-9, Control-0 or the corresponding Escape key shortcuts, by typing a unique beginning and then pressing Enter) is often non-functional: the status bar is highlighted briefly, but without the option of making a selection. Closing the Paragraph and Character Designers may help prevent the problem. Opening the Find/Change dialog box may also trigger the problem (in some cases, closing the document and reopening it clears the problem, in other cases you have to restsart FrameMaker).
  • (fixed in FM8.0p273) In text fields in dialog boxes (variables, cross-references, pgf numbering, markers), some special characters indicated as backslash sequences (including a non-breaking hyphen, \+ and special spaces, \sm, \sn, \st, \s#) are displayed as a box (.notdef) once the dialog box is redisplayed. When the dialog box definition is updated, question marks appear in the document instead of the special character. To fix this problem, you need to edit the text in the dialog box (delete the box character and insert the backslash sequence again).
  • (fixed in FM8.0p273) Generating an index for a book in FM8.0 may cause a crash (internal error: 8004, 8443342, 4459945, 4414681);
    Crashes may also be experienced when generating/updating a book, with some index markers having references to character formats (internal error: 8004, 8443407, 4460228, 4414681);
    When character formats are used in markers for multi-level entries containing the same text, some entries are missing in the generated index
  • (fixed in FM8.0p266) A distilling error is encountered when printing a book to a single .PS file (or saving a book as a single PDF), and no PDF is created; pdfmark codes for links are written incorrectly (missing two angle brackets in the definition of the link's action).
    Workaround: turn Tagged PDF on (without selecting specific tags); FrameMaker's "Tagged PDF" has its own problems and side-effects
    [For a description of FrameMaker's Tagged PDF, see: Creating Accessible PDF Files from FrameMaker 6.0 in Windows (ATN 326295).]
  • (fixed in FM8.0p266) Tab character is not inserted in a table cell when using Escape Tab (# character inserted instead).
    Workaround: copy the tab character from another location in the document, paste inside table cell.
  • (fixed in FM8.0p273) Some characters added to the "Allow Line Breaks After" (Format>Document>Text Options) are ignored (including em dash, en dash, ellipsis). This may cause line-break changes when documents created in earlier FrameMaker versions are opened in FM8. [Mike Wickham]
  • (fixed in FM8.0p266) Automatic letter spacing is broken. In the paragraph designer, if you check the "Allow Automatic Letter Spacing" checkbox, when Alignment is set to "Justified", some text lines jump back from the right-hand margin. The lines that jump back are the same lines to which FrameMaker chooses to apply automatic letter spacing. [Mike Wickham]
  • (fixed in FM8.0p273) The closing smart quote character is always the right double quotation mark (\u201D or Alt+0148 with Windows-1252; \xd3 in FrameRoman), regardless of the SmartQuotes= settings in the maker.ini file. While this is not an issue for English-language documents, a different closing smart quote character is typically needed in other languages (including German, French, Swedish, Italian).
    Workaround: insert the required opening and closing quote characters directly.
  • (fixed in FM8.0p273) FrameMaker is not responding while selecting text by mouse on Vista if Mousekey is kept pressed for long time.
  • (fixed in FM8.0p273) Conversion of certain Unicode characters of Symbol / Dingbats / WebDings fonts is incorrect when an XML is opened in FrameMaker
  • Find/Change operations may cause a crash when there are many replacements (internal error: 8004, 8442924, 4906935, 4903184). For example, in chapter 2 of the sample Ecology book provided with FrameMaker, replace a space with a space (the same operation is successful in FrameMaker 7.2).
    Workaround: add the following line in the [Preferences] section in maker.ini (see issue #1555297 in FrameMaker 8.0's ReadMeFirst.html)
    ClearHistorySpecial=On
    After adding this entry, the History palette will be cleared when a global Find/Change action is executed, and the global Find/Change action cannot be undone.
  • Characters are missing or replaced with question marks when document is saved with 7.x compatibility (kb402419)
  • Unicode text pasted into FrameMaker 8.0 from Word appears as question marks or in a new anchored frame (Windows) (kb402417)

 

FM8.0p266 (released November 2007; 151MB) | update through Help > Updates, or download and apply

  • When you press Enter and the cursor is at the beginning of a paragraph, the NextPgfTag property is not applied to the new paragraph as expected. (Note: Autonumber is not considered as content).
  • Alan Pringle reports in Palimpsest: "If you have added a structured application to the default ones provided by FrameMaker 8, proceed with caution before you install the patch for FrameMaker 8.0p266. The install will replace your applications definition file (structapps.fm) file without making a backup version."
  • In FrameMaker 8.0p266, the "Save as PDF" command starts Distiller 8.1 with the -F flag, and "Save as PDF" can therefore be used in conjunction with FrameMaker-to-Acrobat TimeSavers.
    If Distiller 8.1 is used directly, it has to be started with the -F flag (set up a shortcut, or select Start > Run, and type type: acrodist -F )

The following fixes are reported in the readme file:

  • #1614109: <Unix> FM is not able to read or insert conref
  • #1608599: Equation does not appear in a tagged PDF if its inside a table which has shading and spans across two pages
  • #1607891: On generating tagged PDF for a document having a footnote inside a table crashes frame
  • #1602339: When multiple files (chapters) are selected from a book with all the files in the book open and build expression is selected from view->show/hide conditional text , All the tags from different chapters are not listed (hence cannot be applied)
  • #1601874: <Unix> " F_FdeInit() " call in asynchronous clients is resulting in Segmentation error when called before connecting to FM
  • #1600418: If there are two cross references on a single line in a book file and the PDF is made from a book level a pdfmark error occurs in Distiller 8
  • #1593518: saving DITA topic file crashes frame if it contains tracked element.
  • #1592587: When user saves a DITA-Topic as xml, the user variables are dropped because of Fm variable drop statement in read write rules file
  • #1591854: <Vista> Generating FrameMaker document from dita map will crash FrameMaker
  • #1589706: 3D/Flash do not get activated in PDF if sidehead option is checked in column layout and there is some text in sidehead section
  • #1589018: Cannot create an untagged PDF file from a book
  • #1588399: Flash files are not getting embedded in PDFs when a .book is saved to PDF but get rasterized instead.
  • #1578613: Frame crashes if we insert a row in a table with track change on in a structured document.
  • #1578305: <Solaris> Character width is wrong when Italic and bold style is applied together on non English text(multiple lines).
  • #1578304: <Solaris> spread and stretch if used together are not applied correctly sometimes(depending upon the sequence and values of spread and stretch).
  • #1572527: When generating FM document from DITA map, some elements and the 'Conref' that inserted to these elements are all lost.
  • #1572487: Crossref formats in legacy files are getting truncated at invalid UTF-8 boundaries leading to crash.
  • #1571299: Vista: Generate/update in book causes Frame 8 to crash: This bug was specific to some set of files where incompatible cross-reference format (FM7.1 v. FM8) was there. When "Update all Cross-References" is deselected in the Update Book dialog box, FM8 performs the generate/update and does not crash.
  • #1570010: Character '&' and '<' are not translated to entities on save xml if symbol font is applied over it.
  • #1548856: DITA -- spaces deleted from index entries. It happens when we use the Indexterm element instead of inserting an Index marker and round tripping.
  • #1541126: Opening a large XML file with many tags takes almost double the time when opened on Jackpot as compared to Indra
  • #1424913: Opening a file created with 7.2fm (with setting DisplayUsingPrinterMetrics=On) displays reformat document using available font matrices message.
  • #1418538: Articles "Thread by Text Frame" and "Thread by Column" in Pdf set up dialog box are not working properly
  • #1389944: Tag structure is incorrect for links in tagged PDF
  • #0666689: White Text on a colored background does not appear in the PDF generated from FM7.1 on Windows
  • PDF is missing text that is present on a colored background. This is actually a layering issue where the text is present in the PDF just "hidden" beneath the fill color object

FM8.0p273 (released February 2008; 30MB) | update through Help > Updates, or download and apply

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | FM 9.0 | Filters | PS Drivers | Documentation

FrameMaker 9.0 (mostly Windows, may also apply to Solaris)

FM9.0, released January 2009

Note: See also issues present in previous releases of FrameMaker, as they may also apply to FrameMaker 9.0 (unless indicated otherwise)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | Filters | PS Drivers | Documentation

Product Documentation

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 
Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | Filters | PS Drivers | Documentation

FrameMaker Filters

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Bugs/Issues: FM 5.0-5.2 | FM 5.5.0-5.5.3 | FM 5.5.6 | FM 6.0 | FM 7.0 | FM 7.1 | FM 7.2 | FM 8.0 | Filters | PS Drivers | Documentation

PostScript Drivers

  • AdobePS 4.5.3 (Win9x/ME): Reference frames may not be not represented correctly in PS/PDF output
  • AdobePS/PScript 5.2 (Win2K/XP): Characters in logo/icon PostScript Type 1 fonts (which do not have the entire character set) are not carried over to PS/PDF (displayed as white space).
    Workarounds: (1) Convert the custom font to TrueType, install it and use it instead of the Type 1 version; (2) Ask the font designer/foundry to add characters to the font so that is looks as a "complete" font; (3) Generate the PostScript output on Win98 or NT
  • Troubleshooting PostScript Errors (ATN 328515)
  • PostScript Error Types and Offending Commands
  • Troubleshooting Printing Problems in FrameMaker for Windows (ATN 324396)
  • FrameMaker/Win outputs its graphic objects to PostScript, split into multiple segments.
    Zip file (161K) has a MIF, PS and PDF files of a simple example; movie [AVI, 436K]