This article contains a list of issues resolved in the 2020 release of Adobe FrameMaker and subsequent patch releases.
Check FrameMaker community for solutions, workarounds, or any late-breaking information.
Check FrameMaker User Guide for detailed explanation of features and "how-to" information.
Update 7 of FrameMaker Summer 2020 release addresses critical security vulnerabilities.
Fixed Issues
- Fixed remote code execution when importing a DOCX file.
- Fixed remote code execution through untrusted search path.
- Fixed remote code execution through malicious URL schemes.
- Fixed integer overflow and underflow vulnerability on parsing SVG files.
More details about the security fixes are available in the Adobe Security Bulletin.
Update 6 of FrameMaker Summer 2020 release contains fixes for important security vulnerabilities.
Fixed Issues
- Fixed file parsing heap memory corruption vulnerabilities.
(Ref – 14733, 14691 and 14682) - Fixed file parsing out of Read/Write bound vulnerabilities.
(Ref – 14683, 14679, 14678 and 14677) - Fixed XLS File Parsing Buffer Overflow vulnerabilities.
(Ref – 14693)
More details about the security fixes are available in the Adobe Security Bulletin.
Update 5 of FrameMaker Summer 2020 release has fixes for HTML5 TOC autonumbering, removing dependency on IE during login, and security issues.
Fixed Issues
- If space is present in the file name, then footnote is not working due to a mismatch in encoding.
(Ref – 11760)
- When publishing documents with table footnote the selected footnote style changes in the responsive HTML5 output.
(Ref – 11664)
- In the Responsive HTML5 output, TOC autonumbering is not getting removed if the style names contain spaces between them.
(Ref – 11514) - Split feature is not working correctly if the style name starts with a number.
(Ref – 12122) - A dependency exists on Internet Explorer during login.
(Ref – 12552)
- Fixed security vulnerabilities related to fonts handling and improper input validation remote code execution. More details about the security fixes are available in:
- Adobe Security Bulletin - APSB22-42 (Ref – 11601, 11546, and 12419)
- Adobe Security Bulletin - APSB23-06 (Ref – 12443, 12444, 12445, and 12446)
Starting with Update 4, Adobe FrameMaker 2020 is tested and certified on the latest Windows 11 operating system. All functionalities of FrameMaker Update 4 will work seamlessly with Windows 11 and Windows 10 as well. Update 3 and earlier releases of FrameMaker 2020 release will continue to work on Windows 10
Update 4 of FrameMaker Summer 2020 release has many improvements like support to author content using the UUID-based file referencing system, adding labels during the check-in process, and providing FDK as a downloadable ZIP file.
For more information, see What's new in Update 4 of FrameMaker.
Fixed Issues
- Mapping an output style to an auto-numbering paragraph style (in a settings file) does not render the auto-number list correctly in HTML5 output.
(Ref – 10940) - Hypertext markers do not appear correctly on publishing Responsive HTML5 output.
(Ref – 10867) - The language of the first paragraph changes from Deutsch 2006 to Deutsch 1901 on hitting the Enter key in a FrameMaker document within the German build.
(Ref – 11009) - Original Image names with Unicode characters are not retained, instead generated names are inconsistent in the output asset folder when Responsive HTML5 output is generated.
(Ref – 10725) - Position of anchored frames is modified when a book is updated to generate TOC or indexes.
(Ref – 10816) - In some cases, unwanted line breaks are found after each paragraph in Responsive HTML5 output.
(Ref – 10744) - Language tag, when defined in paragraph style, is not retained while generating the PDF output.
(Ref – 10676) - Original filename is not retained for a map file with .h extension when the Responsive HTML5 or the Microsoft HTML Help output is generated.
(Ref – 10551) - The file size of the output is huge for a PDF containing SVG images and text, and having opacity set to 0.
(Ref – 6591) - Scaled SVG images degrade and appear blurred in the PDF output.
(Ref – 10090)
This note is only specific for customers using FrameMaker and RoboHelp for their technical communication workflows.
Update 3 of FrameMaker Summer 2020 release is only compatible with Update 6 of RoboHelp Summer 2020 release.
For a seamless experience on Update 6 of RoboHelp, you need to upgrade to Update 3 of FrameMaker. Don’t upgrade to Update 3 of FrameMaker if you’re on any version prior to Update 6 of RoboHelp to avoid any compatibility issues in certain workflows.
Update 3 of FrameMaker Summer 2020 release has many improvements around handling of images in HTML5 output.
For more information, see What's new in Update 3 of FrameMaker.
Fixed Issues
- Cross-references when copied from one document to another in the same DITA book, open incorrect hyperlink destinations.
(Ref – 10563) - Names of sub-books are missing from the book-in-book TOC in the Responsive HTML5 output.
(Ref – 10561) - @href attribute of an image is not dynamically updated on changing the image's name inside an <image> element.
(Ref – 10556) - Dynamic HTML Drop Down Effects do not work as expected.
(Ref – 10550) - Content loss or distorted text appears in the PDF output if it contains Assistant or Source Sans Pro fonts.
(Ref – 10294) - The @lang attribute gets embedded in the meta content. The @lang attributes value doesn't adhere to standards and gets inserted even if the paragraph has the same language as that of the document.
(Ref – 10168) - Anchor tags are generated even when the corresponding @href is not defined.
(Ref – 10163) - Original image names are not retained, instead get renamed, when Responsive HTML5 output is generated.
(Ref – 10098) - Some spaces are trimmed when certain variables are used in files and Responsive HTML5 output is generated for them.
(Ref – 9950) - While generating Responsive HTML5 output, the post-processing of images resulted in a bit of (image) downsampling.
(Ref – 9626)
Fixed crash issues in FrameMaker:
- Cross-scripting vulnerability noticed in 'ehlpdhtm.js' file, which is used to generate Responsive HTML5 output.
(Ref – 10021) - For a specific set of files, FrameMaker crashes on editing the settings (.sts) file or generating Responsive HTML5 output.
(Ref –10347) - For a specific set of files, FrameMaker crashes on publishing Responsive HTML5 output.
(Ref – 10502)
Deprecated feature(s) in FrameMaker:
The following feature has been deprecated in FrameMaker:
Password-protected PDF
The feature to password-protect your PDF file has been deprecated in FrameMaker. As the password was being stored in the .sts file, which could have resulted in a security issue.
However, you can generate the PDF output from FrameMaker, open it in Adobe Acrobat, and then set a password. In Acrobat, you can choose File > Protect Using Password or you can choose Tools > Protect > Protect Using Password. For more details see, Securing PDFs with passwords in Adobe Acrobat documentation.
Update 2 of FrameMaker Summer 2020 release has many improvements and bug fixes spanning across authoring, publishing, and managing content.
For more information, see What's new in Update 2 of FrameMaker.
Fixed Issues
- The dynamic conditional filtering does not work correctly in Responsive HTML5 output of DITA map.
(Ref – 9611) - The dynamic conditional filtering on a table does not work as expected in Responsive HTML5 output.
(Ref – 9361) - Inserted equations when rotated, are not published correctly in the PDF output.
(Ref – 8945) - Binary ExtendScript Script Format files are executed twice on launching FrameMaker.
(Ref – 9473) - Files saved with the ExtendScript component do not produce the expected type of file format.
(Ref – 9560) - The support for importing a CSS3 file to an EDD is missing in LwDITA.
(Ref – 9477) - Characters with umlauts are not resolving to correct cross-references in Responsive HTML5 output.
(Ref – 9539) - The text on the buttons in the Learn and Support section is not localized.
(Ref – 9454) - Text truncation issues noticed in some dialogs in the localized versions.
(Ref – 9527, 9528) - Specific SVG files get truncated from top and right when imported into FrameMaker.
(Ref – 9236) - CCITTG4 images are not recognized as the valid file type in FrameMakerL5 output.
(Ref – 9485) - SVG images degrade and look pixelated when published as a PDF.
(Ref – 8526) - Embedded MP4 files do not have the proper MIME media type in the PDF output.
(Ref – 4038) - The whitespace between two consecutive character format elements is trimmed.
(Ref – 9467) - Table border is missing for a specific book containing special characters when published in Responsive HTML5 output.
(Ref – 9411) - Extra whitespaces are added with lists and tables in a structured document and PDF output.
(Ref – 9111) - Whitespace is added in a table cell entry when a document is opened or saved in XML/DITA.
(Ref – 8913) - Character formatting is not supported on linked headings in FrameMaker and subsequent PDF output.
(Ref – 8794) - In some cases, whitespace after a cross-reference is lost in the authoring mode as well as published output.
(Ref – 9173) - Paragraph and heading styles except Adobe styles are not supported in the headings and source headings columns of cross-reference pods.
(Ref – 8775) - The size of the tooltip text on the Welcome Screen is very small.
(Ref – 9970) - Tooltips do not appear on some specific screens for keyboard-only users.
(Ref – 7074) - MiniTOC component is lost on saving a PDF from the Publishing panel.
(Ref – 9316) - The reference and linking functionality of a footnote structure is not supported in PDF 2.0 output.
(Ref – 9284) - The last paragraph within the cell of a collapsed table inside a specific container is lost from the generated XML code.
(Ref – 8892) - Styles defined on external cross-references are not getting applied in HTML output.
(Ref – 8971) - The UniqueID attribute of an element gets deleted when a column is deleted in a table.
(Ref – 9088) - Dimensions of marks and circles of the registration marks do not render correctly in the PDF output.
(Ref – 9062) - Linking of the glossary terms and definitions is not working correctly in Responsive HTML5 output.
(Ref – 9339) - The launch of Help on pressing F1 is not supported appropriately.
(Ref – 9498) - Opening or closing of Review panel is not saved on the workspaces across the sessions.
(Ref – 9908) - An error occurs if check-out operation is attempted for already checked out files on SharePoint Online.
(Ref – 9518) - Updates made to the SharePoint Online repository files after check-out are not saved and reflected on check-in.
(Ref – 9472) - Downloading or uploading of files is slow while using LDAP (Lightweight Directory Access Protocol) account.
(Ref – 9472) - <note> element does not appear along with the previous paragraph in LwDITA files.
(Ref – 8993) - Figure title appears small in the PDF output.
(Ref – 9556)
Fixed crash issues in FrameMaker:
The following crash and freeze issues reported by users or found in FrameMaker have been fixed:
- FrameMaker crashes on exploring the directories under the Browse CMS in SharePoint Online.
(Ref – 9564) - A crafted PDF document is not supported and may result in Read Remote Code Execution Vulnerability.
(Ref – 9555) - FrameMaker crashes on opening Share Point Online repository files with missing images.
(Ref – 9551) - FrameMaker crashes on closing a file that has variables imported from another file.
(Ref – 9532) - FrameMaker crashes on changing the Show/Hide settings of the files in a book.
(Ref – 9455) - Cross-scripting vulnerability noticed in 'rh.min.js' file, which is used to generate Responsive HTML5 output.
(Ref – 9389) - Keyboard input in the Welcome screen causes FrameMaker to crash.
(Ref – 9362) - Using Accept all feature of Track Text Edits in a document causes FrameMaker to hang.
(Ref – 9357) - Searching for a specific element with a specific attribute causes FrameMaker to crash.
(Ref – 9190) - FrameMaker crashes on deleting the condition tags in a book.
(Ref – 9020) - Security issues fixed for the documents published in the Responsive HTML5 output.
(Ref – 7749)
Fixed Issues
- For a set of files, the dynamic conditional filtering does not work as expected.
(Ref – 9378) - Saving a file in MIF format results in loss of content where some special characters are used.
(Ref – 9355) - Missing entries found in the ToC in Responsive HTML5 output.
(Ref – 9325) - Importing FrameMaker documents in RoboHelp does now work as expected.
(Ref – 9311) - A nested <indexterm> or an <indexterm> defined inside prolog > metadata element does not render in the Responsive HTML5 or PDF output.
(Ref – 9297, 9193, 8997) - Special characters in index terms are getting replaced with an underscore.
(Ref – 9197) - Heading tags are lost in tagged PDF output for documents created in earlier version of FrameMaker.
(Ref – 9282) - SGML is not recognized as a valid file type in FrameMaker.
(Ref – 9275) - Whitespaces are lost in full-text preview and auto-suggest in Responsive HTML5 output.
(Ref – 9198) - The support for user-assistance context-string (@ux-context-string) is missing in DITA and subsequent Responsive HTML5 output.
(Ref – 9196) - Soft return (Shift+Enter) with paragraph justification formatting is not published correctly in the PDF or Responsive HTML5 output.
(Ref – 9069) - The XML code generated for adding an image element in LwDITA is invalid.
(Ref – 8974) - Styles defined on external cross-references are not getting applied in Responsive HTML5 output.
(Ref – 8971) - Cropped text noticed in the Rule File Maker dialog, which is used by the Structured Application Designer.
(Ref – 8897) - Paragraph numbering used in the ToC does not publish in the Responsive HTML5 output.
(Ref – 8805) - Opening the Review Panel for in-review document takes longer than expected time.
(Ref – 9255) - The default timeout setting for SharePoint CMS is not adequate to work with larger files.
(Ref – 8740) - For a set of files in Chinese locale, FrameMaker crashes on opening the file with unexpected characters.
(Ref – 9355) - When Auto Collapse panels option is turned ON, some specific operations cause FrameMaker to freeze.
(Ref – 6502)