Important Reminder:
Important Reminder: |
Adobe will disable support for authoring with Type 1 fonts in January 2023. See the Postscript Type 1 End of Support help article for more details. |
This article contains a list of issues resolved in FrameMaker (2019 release) and subsequent patch releases.
Check FrameMaker community for solutions, workarounds, or any late-breaking information.
Update 8 is not offered to users on Update 7 through Help > Updates. Download Update 8 separately from here and install it manually.
Fixed Issues
Update 7 is not recommended for production. If you are currently using Update 7, we strongly recommend you to install Update 8. Update 8 is not available for users on Update 7 through Help > Updates. You can download it separately from here.
By default, when you download, check-out, or open a file from the AEM repository, FrameMaker resolves and downloads all dependent files as well. This behavior causes slight lag in opening the files. A new option is now introduced that allows you to choose how you want to resolve the dependent files. You can choose to limit resolving the dependent files to one-level only. By default, multi-level content references are resolved.
When working with image or multimedia files on a network drive, FrameMaker frequently checks for changes or updates in the referenced files. Such frequent checks cause blinking effect on the referred asset in the source content. In case of slower network bandwidth, this can cause a marginal lag while scrolling pages across your document.
You can now choose to ignore frequent refreshing or checking such image or multimedia files on your network drive. In the General settings in the Preferences dialog, select Do Not Check For Updated Images & Multimedia option. When this option is turned ON, FrameMaker will not check for updates in the referenced media files that are available on your network drive.
You must deselect (or disable) this option before generating output of your book or topic file, else any updates to the media file might not get reflected in the output.
A new option to automatically check-out files on opening or saving has been introduced in AEM connector preferences. In the Preferences dialog, access CMS > Adobe Experience Manager settings.
To enable the auto-file check-out feature, select the Enable Auto-Checkout option. Along with this option, you can choose whether you want to check-out file when they are opened or saved. After making a selection for the file check-out option, you can then choose the option to show a prompt.
If you are using a combination of check-out file on open with show prompt, then you see a prompt on opening a file from the AEM repository. If you choose to check out the file, you get an exclusive lock on the file and you can edit the file. If you choose not to check out the file, then the file is opened in read-only mode.
If you are using a combination of check-out file on save with show prompt, then you see a prompt to check out the file on save. If the file is not checked out and you try to save the file, then you are prompted if you want to check out the file. If you choose not to check-out file, then the updates are not saved.
You can also choose a combination of file check out on open and save with show prompt to get all above functionalities.
Earlier when you inserted an image in a table cell, the image was scaled down to fit into the cell. The auto-scaling behavior can now be controlled by adding a flag in the maker.ini file. To retain auto-scaling of an image in a cell, add the following flag in the Preferences section of the maker.ini file:
AutoScaleImageInTableCell=On
By default, this flag is not available in the maker.ini file and its value is set to false. This implies that when you insert an image in a table cell, it is inserted in the original size. If you add this flag and set it to On, then the image scales down to fit into the table cell.
Fixed crash issues in FrameMaker:
The following crash and freeze issues reported by users or found in FrameMaker have been fixed:
Fixed crash issues in FrameMaker:
The following crash and freeze issues reported by users or found in FrameMaker have been fixed:
You can now import DITA Templates directly from a folder. While publishing PDF output via Book with Components Route, you had to specify the output template file for every different type of template. Now, you can place all your template files in a single folder and specify the location of that folder to import all template files in a single click.
In case you want to use only a subset of templates, then place those template files in a folder. While importing, FrameMaker updates only those template files that are available in the folder and the other template files are not changed.
The updated DITA customization plugin now allows you to add constraints to the customized DITA shells. The user interface has also been updated and made more intuitive. With the enhanced DITA customization plugin, you will be able to quickly and easily customize DITA shells.
Fixed crash issues in FrameMaker
The following crash and freeze issues reported by users or found in FrameMaker have been fixed:
In Update 1, there are a number of enhancements made in the new PDF publishing engine. These enhancements include:
While saving a document in PDF, FrameMaker used the PDF publish settings defined in the Publish Settings dialog. The output location was also taken from the Publish pod. To change the output location for the final PDF, you were required to update the settings every time.
With the Update 1 release, you get the Save Document dialog whenever you choose to save a document as PDF from the File > Save As PDF menu. In the Save Document dialog, you can select a location to save the PDF file. This does not impact your PDF settings. The location specified in the settings file (in Publish pod) and the Save Document dialog are mutually exclusive.
This change in the workflow also resolved the issue of overwriting an existing PDF file. If you try to publish a PDF at the same location with the same filename, FrameMaker displays a warning message. Only if you confirm to overwrite the existing file, FrameMaker overwrites the older version of the file.
FrameMaker Update 1 now supports OpenSSL version 1.1.1. FrameMaker uses OpenSSL when establishing a connection with any HTTPS server using WebDAV.
Fazer logon em sua conta