The Adobe® InDesign® 2.0.2 Text update includes the following fixes:
— If text contains characters with varying fonts and/or point sizes and optical kerning is applied to the text, the spacing between characters will be correct.
— If optical kerning is applied to text, the spacing will be the same whether the fonts are installed before or after the document is opened.
— If a Microsoft Word document or RTF file contains Macintosh or Windows® system fonts with bold or italic styling applied, and the document or file is placed into an InDesign document, InDesign may not report that fonts used by the file are missing if the fonts are installed or active.

The Adobe® InDesign® 2.0.2 Text update includes the following fixes:

— If text contains characters with varying fonts and/or point sizes and optical kerning is applied to the text, the spacing between characters will be correct.
— If optical kerning is applied to text, the spacing will be the same whether the fonts are installed before or after the document is opened.
— If a Microsoft Word document or RTF file contains Macintosh or Windows® system fonts with bold or italic styling applied, and the document or file is placed into an InDesign document, InDesign may not report that fonts used by the file are missing if the fonts are installed or active.

When using Adobe® InDesign® 2.0.x in Mac OS X on a computer that has more than 1.5GB of installed RAM, one or more of the following problems may occur:
- "Not enough memory" error is displayed when activating a clipping path from the Object menu.
- "Out of memory" error is displayed when selecting an EPS or TIFF file and trying to create a clipping path.
- Applying text wrap to an object using a contour option fails to respond.
The InDesign 2.0.2 Memory update resolves these issues. To verify how much RAM is installed on your computer, select About This Mac from the Apple menu.

When using Adobe® InDesign® 2.0.x in Mac OS X on a computer that has more than 1.5GB of installed RAM, one or more of the following problems may occur:

- "Not enough memory" error is displayed when activating a clipping path from the Object menu.
- "Out of memory" error is displayed when selecting an EPS or TIFF file and trying to create a clipping path.
- Applying text wrap to an object using a contour option fails to respond.

The InDesign 2.0.2 Memory update resolves these issues. To verify how much RAM is installed on your computer, select About This Mac from the Apple menu.

When using Adobe® InDesign® 2.0.x in Mac OS X on a computer that has more than 1.5GB of installed RAM, one or more of the following problems may occur:

- "Not enough memory" error is displayed when activating a clipping path from the Object menu.
- "Out of memory" error is displayed when selecting an EPS or TIFF file and trying to create a clipping path.
- Applying text wrap to an object using a contour option fails to respond.

The InDesign 2.0.2 Memory update resolves these issues. To verify how much RAM is installed on your computer, select About This Mac from the Apple menu.

This patch updates the p576 release of Adobe® FrameMaker® 7.0, released in September 2002.
The following is a summary of issues that are addressed in the current release of FrameMaker 7.0p578. Additional details can be found in the ReadMe file installed with the update.
- 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.

This patch updates the p576 release of Adobe® FrameMaker® 7.0, released in September 2002.

The following is a summary of issues that are addressed in the current release of FrameMaker 7.0p578. Additional details can be found in the ReadMe file installed with the update.

- 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.

This patch updates the p576 release of Adobe® FrameMaker® 7.0, released in September 2002.

The following is a summary of issues that are addressed in the current release of FrameMaker 7.0p578. Additional details can be found in the ReadMe file installed with the update.

- 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.

When text is reflowed in a document in Adobe® InDesign®, (for example, by adding text to a story or placing a frame with text wrap over a story), the text may be slow to recompose if the story contains a large amount of text. The Long Document Performance update resolves this issue.

When text is reflowed in a document in Adobe® InDesign® (for example, by adding text to a story or placing a frame with text wrap over a story), the text may be slow to recompose if the story contains a large amount of text. The Long Document Performance update resolves this issue.

When text is reflowed in a document in Adobe® InDesign®, (for example, by adding text to a story or placing a frame with text wrap over a story), the text may be slow to recompose if the story contains a large amount of text. The Long Document Performance update resolves this issue.

When text is reflowed in a document in Adobe® InDesign® (for example, by adding text to a story or placing a frame with text wrap over a story), the text may be slow to recompose if the story contains a large amount of text. The Long Document Performance update resolves this issue.

When text is reflowed in a document in Adobe® InDesign® (for example, by adding text to a story or placing a frame with text wrap over a story), the text may be slow to recompose if the story contains a large amount of text. The Long Document Performance update resolves this issue.

When text is reflowed in a document in Adobe® InDesign®, (for example, by adding text to a story or placing a frame with text wrap over a story), the text may be slow to recompose if the story contains a large amount of text. The Long Document Performance update resolves this issue.

The File Browser Update plug-in increases the stability of the File Browser in Adobe® Photoshop® 7 running on Mac OS X version 10.2. This plug-in addresses a specific issue that could occur when browsing a large number of files in a single folder.

The File Browser Update plug-in increases the stability of the File Browser in Adobe® Photoshop® 7 running on Mac OS X version 10.2. This plug-in addresses a specific issue that could occur when browsing a large number of files in a single folder.

The File Browser Update plug-in increases the stability of the File Browser in Adobe® Photoshop® 7 running on Mac OS X version 10.2. This plug-in addresses a specific issue that could occur when browsing a large number of files in a single folder.

The Adobe® Photoshop® 7.0.1 update fixes a number of problems discovered after Photoshop 7.0 was released.
The most significant fixes in the 7.0.1 release include the following:
• Type layers are no longer rasterized unnecessarily.
• Photoshop now saves alpha transparency data in Targa files in the same way it did in previous versions.
• If the color settings color management policy is set to "Off," Photoshop no longer asks to save changes unless other edits have been performed.
• The total ink now defaults to 300% as it did in previous versions of Photoshop.
• The color of white areas in CMYK files saved as JPEG files no longer shifts.
• TIFF files with LZW compression are now written correctly.
• Photoshop offers better compatibility with older G4 computers.
• Icons now resave as they did in previous versions of Photoshop.
• When installed on a hard drive whose name contains extended characters, Photoshop no longer reports that certain required files were not found in the Adobe Photoshop required folder.
• Metadata is better preserved in certain JPEG files.
• Photoshop now defaults to the last saved directory when saving new files. It no longer defaults to the TWAIN directory if one is present.
• Changing monitor configurations no longer causes problems while Photoshop or Adobe ImageReady® is running.
• Photoshop no longer produces a program error when resampling certain large 16-bit documents.
• An issue that prevented Photoshop 6.0 from opening certain files containing layer effects and edited in Photoshop 7.0 has been fixed.
• The Maximize Backwards Compatibility for Photoshop Files preference now correctly sets the state of the Maximize Compatibility checkbox in the Photoshop Format Options dialog box when you save a file as Photoshop (PSD) format.

The Adobe® Photoshop® 7.0.1 update fixes a number of problems discovered after Photoshop 7.0 was released.

The most significant fixes in the 7.0.1 release include the following:

• Type layers are no longer rasterized unnecessarily.
• Photoshop now saves alpha transparency data in Targa files in the same way it did in previous versions.
• If the color settings color management policy is set to "Off," Photoshop no longer asks to save changes unless other edits have been performed.
• The total ink now defaults to 300% as it did in previous versions of Photoshop.
• The color of white areas in CMYK files saved as JPEG files no longer shifts.
• TIFF files with LZW compression are now written correctly.
• Photoshop offers better compatibility with older G4 computers.
• Icons now resave as they did in previous versions of Photoshop.
• When installed on a hard drive whose name contains extended characters, Photoshop no longer reports that certain required files were not found in the Adobe Photoshop required folder.
• Metadata is better preserved in certain JPEG files.
• Photoshop now defaults to the last saved directory when saving new files. It no longer defaults to the TWAIN directory if one is present.
• Changing monitor configurations no longer causes problems while Photoshop or Adobe ImageReady® is running.
• Photoshop no longer produces a program error when resampling certain large 16-bit documents.
• An issue that prevented Photoshop 6.0 from opening certain files containing layer effects and edited in Photoshop 7.0 has been fixed.
• The Maximize Backwards Compatibility for Photoshop Files preference now correctly sets the state of the Maximize Compatibility checkbox in the Photoshop Format Options dialog box when you save a file as Photoshop (PSD) format.

The Adobe® Photoshop® 7.0.1 update fixes a number of problems discovered after Photoshop 7.0 was released.

The most significant fixes in the 7.0.1 release include the following:

• Type layers are no longer rasterized unnecessarily.
• Photoshop now saves alpha transparency data in Targa files in the same way it did in previous versions.
• If the color settings color management policy is set to "Off," Photoshop no longer asks to save changes unless other edits have been performed.
• The total ink now defaults to 300% as it did in previous versions of Photoshop.
• The color of white areas in CMYK files saved as JPEG files no longer shifts.
• TIFF files with LZW compression are now written correctly.
• Photoshop offers better compatibility with older G4 computers.
• Icons now resave as they did in previous versions of Photoshop.
• When installed on a hard drive whose name contains extended characters, Photoshop no longer reports that certain required files were not found in the Adobe Photoshop required folder.
• Metadata is better preserved in certain JPEG files.
• Photoshop now defaults to the last saved directory when saving new files. It no longer defaults to the TWAIN directory if one is present.
• Changing monitor configurations no longer causes problems while Photoshop or Adobe ImageReady® is running.
• Photoshop no longer produces a program error when resampling certain large 16-bit documents.
• An issue that prevented Photoshop 6.0 from opening certain files containing layer effects and edited in Photoshop 7.0 has been fixed.
• The Maximize Backwards Compatibility for Photoshop Files preference now correctly sets the state of the Maximize Compatibility checkbox in the Photoshop Format Options dialog box when you save a file as Photoshop (PSD) format.