FrameMaker 7.0p576 on the Windows platform has an issue with TIFF graphics imported by reference. After importing some TIFF graphics and upon scrolling using the mouse or the page up/down keys, FrameMaker may suddenly display an alert "cannot display some graphics" and shows the Tiff graphics as gray boxes.
FrameMaker 7.0p576 would crash on reopening the PDF Setup dialog box if "0" (zero) was previously entered in the "Bookmarks expanded through level" field in the PDF Setup, Bookmarks panel dialog box.
FrameMaker 7.0p576 sometimes crashed at the last page of the last document in the book when a large book was Saved as PDF or printed with Generate Acrobat Data selected.
- With FrameMaker 7.0p576 and Adobe Acrobat 6.0, the Save As PDF command will give an error "FrameMaker could not find Acrobat Distiller printer instance, which must be installed to execute save as PDF command."
Note: FrameMaker7.0p578 may have problems if both Distiller 5.0 and Distiller 6.0 are installed on the same machine. Adobe recommends that users uninstall Distiller 5.0 before installing Distiller 6.0. In addition, the placed PDF functionality of FrameMaker 7.0 will support only PDF 1.4 (Acrobat 5.0) files, not PDF 1.5 (Acrobat 6.0) files.
The maximum number of commands for all FM Api Clients has been increased to 2,017 in FrameMaker 7.0P578. Previously, the limit was 250.
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.
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. This has been fixed in this p578 release.
