This patch fixes the following SGML import and export problems discovered in Adobe FrameMaker+SGML 5.1.1P6c after its release. After you update FrameMaker+SGML 5.1.1P6c using this patch, the version remains the same (5.1.1P6c).

- Problem Parsing SGML Files
FrameMaker+SGML incorrectly reports parsing errors when carriage return (CR) characters are found in SGML files.

- Name-Case Recognition Problems with COLSPEC Elements in CALS Table
When name-case is declared significant by the statement NAMECASE GENERAL NO in the SGML Declaration, FrameMaker+SGML fails to recognize CALS table elements unless they are defined in all uppercase characters.

- COLS Attribute on TGROUP Not Recognized When TGROUP Is Unwrapped
When importing SGML, FrameMaker+SGML fails to import the information specified by the COLS attribute if the TGROUP element is unwrapped, resulting in a table having only one cell instead of a number of cells specified by the COLS attribute.

- Document Flagged as Modified When Saved as SGML
FrameMaker+SGML marks unmodified documents as modified if they were saved in SGML format. (If the document uses No Application, or has no specified application, the unpatched or patched FrameMaker+SGML prompts you to select an application. FrameMaker+SGML stores the application name in the document, which results in a modified document.)

- Entity Names Not Recognized When Name-Case Is Insignificant
When name-case is insignificant (ENTITY NAMECASE YES), FrameMaker+SGML does not recognize certain entity references and does not map them properly.

- Cross-Reference ID/IDREF Attributes Not Resolved Properly on Export to SGML
When FrameMaker+SGML exports to SGML a cross-reference element with both ID and IDREF attributes, it may also assign the IDREF value to the ID attribute, causing validation problems that result in parsing errors. (If FrameMaker returns the error, "No cross-reference ID specified for the SGML element (XREF)." when you re-importing the SGML instance, see the Additional Notes section below.)

To compile API clients, you need Microsoft Visual C++ 2.2 for compatibility with all Windows platforms or Microsoft Visual C++ 4.x if Windows 3.1 compatibility is not needed.

This patch fixes the following SGML import and export problems discovered in Adobe FrameMaker+SGML 5.1.1P6c after its release. After you update FrameMaker+SGML 5.1.1P6c using this patch, the version remains the same (5.1.1P6c).
- Problem Parsing SGML Files
FrameMaker+SGML incorrectly reports parsing errors when carriage return (CR) characters are found in SGML files.
- Name-Case Recognition Problems with COLSPEC Elements in CALS Table
When name-case is declared significant by the statement NAMECASE GENERAL NO in the SGML Declaration, FrameMaker+SGML fails to recognize CALS table elements unless they are defined in all uppercase characters.
- COLS Attribute on TGROUP Not Recognized When TGROUP Is Unwrapped
When importing SGML, FrameMaker+SGML fails to import the information specified by the COLS attribute if the TGROUP element is unwrapped, resulting in a table having only one cell instead of a number of cells specified by the COLS attribute.
- Document Flagged as Modified When Saved as SGML
FrameMaker+SGML marks unmodified documents as modified if they were saved in SGML format. (If the document uses No Application, or has no specified application, the unpatched or patched FrameMaker+SGML prompts you to select an application. FrameMaker+SGML stores the application name in the document, which results in a modified document.)
- Entity Names Not Recognized When Name-Case Is Insignificant
When name-case is insignificant (ENTITY NAMECASE YES), FrameMaker+SGML does not recognize certain entity references and does not map them properly.
- Cross-Reference ID/IDREF Attributes Not Resolved Properly on Export to SGML
When FrameMaker+SGML exports to SGML a cross-reference element with both ID and IDREF attributes, it may also assign the IDREF value to the ID attribute, causing validation problems that result in parsing errors. (If FrameMaker returns the error, "No cross-reference ID specified for the SGML element (XREF)." when you re-importing the SGML instance, see the Additional Notes section below.)
To compile API clients, you need Microsoft Visual C++ 2.2 for compatibility with all Windows platforms or Microsoft Visual C++ 4.x if Windows 3.1 compatibility is not needed.

This patch fixes the following SGML import and export problems discovered in Adobe FrameMaker+SGML 5.1.1P6c after its release. After you update FrameMaker+SGML 5.1.1P6c using this patch, the version in the .VERSION file in the $FMHOME directory remains the same (5.1.1P6c).

- Name-Case Recognition Problems with COLSPEC Elements in CALS Table
When name-case is declared significant by the statement NAMECASE GENERAL NO in the SGML Declaration, FrameMaker+SGML fails to recognize CALS table elements unless they are defined in all uppercase characters.

- COLS Attribute on TGROUP Not Recognized When TGROUP Is Unwrapped
When importing SGML, FrameMaker+SGML fails to import the information specified by the COLS attribute if the TGROUP element is unwrapped, resulting in a table having only one cell instead of a number of cells specified by the COLS attribute.

- Document Flagged as Modified When Saved as SGML
FrameMaker+SGML marks unmodified documents as modified if they were saved in SGML format. (If the document uses No Application, or has no specified application, the unpatched or patched FrameMaker+SGML prompts you to select an application. FrameMaker+SGML stores the application name in the document, which results in a modified document.)

- Entity Names Not Recognized When Name-Case Is Insignificant
When name-case is insignificant (ENTITY NAMECASE YES), FrameMaker+SGML does not recognize certain entity references and does not map them properly.

- Cross-Reference ID/IDREF Attributes Not Resolved Properly on Export to SGML
When FrameMaker+SGML exports to SGML a cross-reference element with both ID and IDREF attributes, it may also assign the IDREF value to the ID attribute, causing validation problems that result in parsing errors. (If FrameMaker returns the error, "No cross-reference ID specified for the SGML element (XREF)." when you re-importing the SGML instance, see the Additional Notes section below.)

This patch fixes the following SGML import and export problems discovered in Adobe FrameMaker+SGML 5.1.1P6c after its release. After you update FrameMaker+SGML 5.1.1P6c using this patch, the version in the .VERSION file in the $FMHOME directory remains the same (5.1.1P6c).
- Name-Case Recognition Problems with COLSPEC Elements in CALS Table
When name-case is declared significant by the statement NAMECASE GENERAL NO in the SGML Declaration, FrameMaker+SGML fails to recognize CALS table elements unless they are defined in all uppercase characters.
- COLS Attribute on TGROUP Not Recognized When TGROUP Is Unwrapped
When importing SGML, FrameMaker+SGML fails to import the information specified by the COLS attribute if the TGROUP element is unwrapped, resulting in a table having only one cell instead of a number of cells specified by the COLS attribute.
- Document Flagged as Modified When Saved as SGML
FrameMaker+SGML marks unmodified documents as modified if they were saved in SGML format. (If the document uses No Application, or has no specified application, the unpatched or patched FrameMaker+SGML prompts you to select an application. FrameMaker+SGML stores the application name in the document, which results in a modified document.)
- Entity Names Not Recognized When Name-Case Is Insignificant
When name-case is insignificant (ENTITY NAMECASE YES), FrameMaker+SGML does not recognize certain entity references and does not map them properly.
- Cross-Reference ID/IDREF Attributes Not Resolved Properly on Export to SGML
When FrameMaker+SGML exports to SGML a cross-reference element with both ID and IDREF attributes, it may also assign the IDREF value to the ID attribute, causing validation problems that result in parsing errors. (If FrameMaker returns the error, "No cross-reference ID specified for the SGML element (XREF)." when you re-importing the SGML instance, see the Additional Notes section below.)

This patch fixes the following SGML import and export problems discovered in Adobe FrameMaker+SGML 5.1.1P6c after its release. After you update FrameMaker+SGML 5.1.1P6c using this patch, the version remains the same (5.1.1P6c).

- Problem Parsing SGML Files
FrameMaker+SGML incorrectly reports parsing errors when carriage return (CR) characters are found in SGML files.

- Name-Case Recognition Problems with COLSPEC Elements in CALS Table
When name-case is declared significant by the statement NAMECASE GENERAL NO in the SGML Declaration, FrameMaker+SGML fails to recognize CALS table elements unless they are defined in all uppercase characters.

- COLS Attribute on TGROUP Not Recognized When TGROUP Is Unwrapped
When importing SGML, FrameMaker+SGML fails to import the information specified by the COLS attribute if the TGROUP element is unwrapped, resulting in a table having only one cell instead of a number of cells specified by the COLS attribute.

- Document Flagged as Modified When Saved as SGML
FrameMaker+SGML marks unmodified documents as modified if they were saved in SGML format. (If the document uses No Application, or has no specified application, the unpatched or patched FrameMaker+SGML prompts you to select an application. FrameMaker+SGML stores the application name in the document, which results in a modified document.)

- Entity Names Not Recognized When Name-Case Is Insignificant
When name-case is insignificant (ENTITY NAMECASE YES), FrameMaker+SGML does not recognize certain entity references and does not map them properly.

- Cross-Reference ID/IDREF Attributes Not Resolved Properly on Export to SGML
When FrameMaker+SGML exports to SGML a cross-reference element with both ID and IDREF attributes, it may also assign the IDREF value to the ID attribute, causing validation problems that result in parsing errors. (If FrameMaker returns the error, "No cross-reference ID specified for the SGML element (XREF)." when you re-importing the SGML instance, see the Additional Notes section below.)

To compile API clients, you need Microsoft Visual C++ 2.2 for compatibility with all Windows platforms or Microsoft Visual C++ 4.x if Windows 3.1 compatibility is not needed.

This patch fixes the following SGML import and export problems discovered in Adobe FrameMaker+SGML 5.1.1 after its release.

- Name-Case Recognition Problems with COLSPEC Elements in CALS Table
When name-case is declared significant by the statement NAMECASE GENERAL NO in the SGML Declaration, FrameMaker+SGML fails to recognize CALS table elements unless they are defined in all uppercase characters.

- COLS Attribute on TGROUP Not Recognized When TGROUP Is Unwrapped
When importing SGML, FrameMaker+SGML fails to import the information specified by the COLS attribute if the TGROUP element is unwrapped, resulting in a table having only one cell instead of a number of cells specified by the COLS attribute.

- Document Flagged as Modified When Saved as SGML
FrameMaker+SGML marks unmodified documents as modified if they were saved in SGML format. (If the document uses No Application, or has no specified application, the unpatched or patched FrameMaker+SGML prompts you to select an application. FrameMaker+SGML stores the application name in the document, which results in a modified document.)

- Entity Names Not Recognized When Name-Case Is Insignificant
When name-case is insignificant (ENTITY NAMECASE YES), FrameMaker+SGML does not recognize certain entity references and does not map them properly.

- Cross-Reference ID/IDREF Attributes Not Resolved Properly on Export to SGML
When FrameMaker+SGML exports to SGML a cross-reference element with both ID and IDREF attributes, it may also assign the IDREF value to the ID attribute, causing validation problems that result in parsing errors. (If FrameMaker returns the error, "No cross-reference ID specified for the SGML element (XREF)." when you re-importing the SGML instance, see the Additional Notes section below.)

This patch fixes the following SGML import and export problems discovered in Adobe FrameMaker+SGML 5.1.1P6c after its release. After you update FrameMaker+SGML 5.1.1P6c using this patch, the version in the .VERSION file in the $FMHOME directory remains the same (5.1.1P6c).

- Name-Case Recognition Problems with COLSPEC Elements in CALS Table
When name-case is declared significant by the statement NAMECASE GENERAL NO in the SGML Declaration, FrameMaker+SGML fails to recognize CALS table elements unless they are defined in all uppercase characters.

- COLS Attribute on TGROUP Not Recognized When TGROUP Is Unwrapped
When importing SGML, FrameMaker+SGML fails to import the information specified by the COLS attribute if the TGROUP element is unwrapped, resulting in a table having only one cell instead of a number of cells specified by the COLS attribute.

- Document Flagged as Modified When Saved as SGML
FrameMaker+SGML marks unmodified documents as modified if they were saved in SGML format. (If the document uses No Application, or has no specified application, the unpatched or patched FrameMaker+SGML prompts you to select an application. FrameMaker+SGML stores the application name in the document, which results in a modified document.)

- Entity Names Not Recognized When Name-Case Is Insignificant
When name-case is insignificant (ENTITY NAMECASE YES), FrameMaker+SGML does not recognize certain entity references and does not map them properly.

- Cross-Reference ID/IDREF Attributes Not Resolved Properly on Export to SGML
When FrameMaker+SGML exports to SGML a cross-reference element with both ID and IDREF attributes, it may also assign the IDREF value to the ID attribute, causing validation problems that result in parsing errors. (If FrameMaker returns the error, "No cross-reference ID specified for the SGML element (XREF)." when you re-importing the SGML instance, see the Additional Notes section below.)