FrameMaker Annoyances: Bugs & Issues
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. AdobeTutorialz is not responsible for bug/issue descriptions, suggested workarounds and fixes
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).
- FMSGML indicates FrameMaker+SGML 5.x, 6.0 or Structured FrameMaker 7.x
- Bugs/issues specifically relating to FrameMaker versions earlier than 5.0 are not included in this list
- 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
- 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
- Graphics or Anchored Frames are Missing When Opening an MML File in FrameMaker (ATN 319721)
- Using F10 as Macro Trigger Deactivates Shortcuts in FrameMaker (ATN 316487)
Comments