Adobe 65030365 - FrameMaker - PC Developer's Manual page 85

7
A p p l i c a t i o n d e f i n i t i o n f i l e
On a non-Western system, the text for an SGML file can contain double-byte text. This text
can be in any one of a number of different text encodings. For example, Japanese text on
a Unix system is typically in EUC, while on the Macintosh it is typically in Shift-JIS.
FrameMaker can interpret SGML files that contain double-byte text in #PCDATA, RCDATA,
and CDATA. The software expects all other text to be within the 7-bit ASCII range (which
is supported by all Asian fonts). This means that document content can be in double-byte
encodings, but the markup must be in the ASCII range. Typically, for example, the only text
in a DTD that will contain double-byte characters would be text used to specify attribute
values.
Important: For SGML documents, you should not use accented characters in
element tag names nor attribute names. If you use such characters, FrameMaker
may not be able to correctly import or export the document.
To import and export SGML that contains double-byte text, you should specify the character
encoding to use, either as a default for all applications, or for a specific SGML application.
For a given SGML application there can only be one encoding. If you don't specify an
encoding for your application, FrameMaker determines the encoding to use by considering
the current default user interface language and the current operating system; for the current
language, it uses the operating system's default encoding. The default encodings for the
supported operating systems are:
Roman languages
Japanese
Simplified Chinese
Traditional Chinese
Korean
It is possible to have an Asian language for the user interface, but the content of the
document files in Roman fonts. In this case, any exported Roman text that falls outside of
the ASCII range will be garbled. For this reason, we recommend that you specify an
encoding for any application that might be used on a non-Western system.
The template for your application must use fonts that support the language implied by the
encoding you specify. Otherwise, the text will appear garbled when imported into the
template. You can fix this problem after the fact by specifying different fonts to use in the
resulting files.
Structure Application Developer's Guide
Windows 95/NT
ANSI
Shift-JIS
GB8 EUC
Big5
KSC8 EUC
Macintosh
Macintosh ASCII
Shift-JIS
GB8 EUC
Big5
KSC8 EUC
Unix
ISOLatin-1
JIS8 EUC
GB8 EUC
CNS EUC
KSC8 EUC
67