Adobe FrameMaker | Fixed issues

Fixed Issues

Update 1 of FrameMaker (September 2022 release) has many improvements like removing system-generated prefixes from named destinations, better handling of SVGs, improved handling of conditional tags in faster PDF publishing route, and security issues.

For more information, see What's new in Update 1 of FrameMaker (September 2022 release).

• Frame data is getting exported as JPEG instead of SVG in the CHM output format. 
  (Ref – 12113)
• Naming convention is inconsistent in the Japanese folders. 
  (Ref – 12314)
• Table footnotes are not exported well to the XLIFF format. 
  (Ref – 12531)
• When connecting to AEM Guides from Update 4 of FrameMaker Summer 2020 release (through Use Single Sign-On feature), a pop-up browser window appears that must be closed before the connection completes. 
  (Ref – 12296)
• On publishing any CHM output of an SVG image, the SVG image location is different in comparison to the authoring and basic HTML output.
  (Ref – 12520)
• SVG import uses points instead of pixels as the size calculator and ignores width or height values defined in the SVG root element.
  (Ref – 4499)
• FrameMaker hangs on opening, saving, or publishing a specific set of books. 
  (Ref – 12452)
• Unexpected characters are added (due to the use of color names) in filenames generated by the graphics process of the Publishing module. 
  (Ref – 11487)
• Some symbols are not displayed correctly when the PDF output is generated for a DITA file in Right-To-Left language scripts (Arabic and Hebrew).
  (Ref – 11541)
• The Preferences > Variables > Enable Highlight check box is getting truncated for the French version. 
  (Ref – 11517)
• Ignore autonumbering is not working for TOC in the unstructured FrameMaker Book 2020. 
  (Ref – 12357)
• While converting the DITA map into .fm book, conditional tag information applied on text gets lost and results in a different output of Show/Hide text using conditional tags.
  (Ref – 12358)
• When publishing the PDF output of a DITA map via flat book route or by using the FrameMaker settings (.sts) file, an extra title banner is visible at the top of topic. 
  (Ref – 12359)
• Link to external PDFs is not working in HTML5 output.
  (Ref  – 12554)
  
• SVG files were not getting imported with the correct defined sizes. 
  (Ref – 11764)
• Background color in CheckOut dialog is turned black. 
  (Ref – 11406)
• If text is rotated in SVG, then it does not render correctly in FrameMaker. 
  (Ref – 10920)
• Checkout/Checkin workflow is not working for SharePoint Online when the user who last modified the file is different from the user who checked it out. 
  (Ref – 11851)
• Keyword or Copyright text added in File Info appears at the bottom of the HTML5 output. 
  (Ref – 11017)
• On dragging the title bar to move the FrameMaker window, it horizontally centers the window on the mouse cursor. 
  (Ref – 11041)
• Text frames added to an image are shown as black rectangles in an SVG within the responsive HTML5 output.
  (Ref – 11033)
• Sometimes .lck files are not deleted, although the corresponding .fm file is closed.
  (Ref – 9180)
• While saving the DITA map into .fm book (using Save As), conditional tags are lost, resulting in a different output of Show/Hide conditional text using conditional tags.
  (Ref – 12457)
• While connecting to AEM, FrameMaker crashes if Java is not found. 
  (Ref – 12323)
• DITAVAL filter doesn’t implement the logic that if any single attribute evaluates to exclude, the element is excluded in the PDF output. 
  (Ref – 12405)
• % sign is changed to %25 during HTML5 conversion. 
  (Ref – 12607)
  

• Fixed security vulnerabilities related to fonts handling and improper input validation remote code execution. More details about the security fixes are available in the Adobe Security Bulletin. 
  (Ref – 12344, 12432, 12441, 12442, and 12439)