Table of Contents
Advertisement
1
W h a t ' s n e w i n F r a m e M a k e r 7 . 0
Application development
Because of the differences between SGML and XML, you must specify which structure
applications are for SGML and which are for XML. For XML structure applications you can
specify how an application manages:
•
CSS files
•
Namespaces
•
Character encoding and Unicode support in XML
For more information, see Chapter 7, "Working with Special Files."
Read/write rules
Because XML is case-sensitive, any references to XML keywords in your read/write rules
must match the case of these keywords. Generally, these keywords are in uppercase
letters.
The names of the following read/write rules have changed:
From:
fmsgml version
write sgml document
write sgml document instance only
Namespaces
FrameMaker 7.0 supports XML namespace declarations. For more information, see
"Namespace declaration" on page 25
CSS support
FrameMaker does not use CSS data when importing XML, but it does retain the CSS
specification in an XML document on export. You can also generate a CSS from the
formatting information that is stored in an EDD. See Chapter 15, "Saving EDD Formatting
Information as a CSS Stylesheet."
Exporting variables to markup
FrameMaker exports non-element variables as entities. Depending on the variable, some of
these entities can be SDATA or CDATA. XML doesn't support SDATA or CDATA entities—
you have two options for handling such non-element variables:
•
By default, FrameMaker writes the variables out as text
•
You can use read/write rules to map the variables to empty elements
For variables that are elements, FrameMaker exports them as empty elements in markup.
Structure Application Developer's Guide
To:
fm version
write structured document
write structured document instance only
5
Advertisement
Table of Contents
