version 1.3, 2003/07/30 16:14:26
|
version 1.4, 2003/09/08 21:32:02
|
|
|
<html> | <html> |
<head> | <head> |
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> | <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
<meta name="GENERATOR" content="Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i686) [Netscape]"> |
<meta name="GENERATOR" content="Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i686) [Netscape]"> |
</head> | </head> |
<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#55188A" alink="#FF0000"> | <body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#55188A" alink="#FF0000"> |
| |
|
|
The CIM-XML documents contained in the HTTP messages</li> | The CIM-XML documents contained in the HTTP messages</li> |
| |
<li> | <li> |
Repository files and MOF files (<b>TODO</b> - remove MOF files if |
The files in the repository</li> |
we can't get this into 2.3)</li> |
|
</ul> |
<li> |
|
Note: Pegasus 2.3 does NOT support UTF-8 in the MOF files</li> |
|
|
|
<br> </ul> |
| |
<li> | <li> |
Support UTF-16 for internal data.</li> | Support UTF-16 for internal data.</li> |
|
|
External data to Pegasus is encoded in UTF-8. Internal data is encoded | External data to Pegasus is encoded in UTF-8. Internal data is encoded |
in UTF-16. | in UTF-16. |
<br> | <br> |
<p>External data includes the CIM-XML messages passed over the network, |
<p>UTF-8 support for external data includes the CIM-XML messages passed |
the repository files, and the MOF files. For the CIM-XML messages, |
over the network, and the repository files. Note: UTF-8 support |
Pegasus follows section 4.8 of the <a href="http://www.dmtf.org/standards/documents/WBEM/DSP200.html">CIM-HTTP |
was NOT added to the MOF Compiler for MOF files in release 2.3. |
|
For the CIM-XML messages, Pegasus follows section 4.8 of the <a href="http://www.dmtf.org/standards/documents/WBEM/DSP200.html">CIM-HTTP |
specification</a> Specifically, Pegasus supports the | specification</a> Specifically, Pegasus supports the |
"utf-8" setting for the charset parameter of the Content-Type header and | "utf-8" setting for the charset parameter of the Content-Type header and |
the XML encoding attribute. If no charset is specified, the 7-bit | the XML encoding attribute. If no charset is specified, the 7-bit |
ASCII is assumed. The Pegasus MOF compiler supports UTF-8 encoding |
ASCII is assumed. |
in the MOF files. (<b>TODO</b> - remove this statement if this is |
|
not in 2.3) |
|
<br> | <br> |
<p>The internal support of UTF-16 is encapsulated in the Pegasus String | <p>The internal support of UTF-16 is encapsulated in the Pegasus String |
class. This class has been updated to contain UTF-16 characters. | class. This class has been updated to contain UTF-16 characters. |
|
|
similiar to the one shown in the Resource Management section, including | similiar to the one shown in the Resource Management section, including |
the empty bundles in the tree. It is recommended that you ship a | the empty bundles in the tree. It is recommended that you ship a |
root resource bundle to be used as the fallback in case the client requests | root resource bundle to be used as the fallback in case the client requests |
a language that you are not supporting. |
a language that you are not supporting. The Pegasus make files are |
|
set up to automatically create and compile a root resource bundle for you. |
|
For Pegasus 2.3, the make will use your "en" bundle, upper case all the |
|
messages, and then put the uppercased messages into the root bundle. |
|
The uppercasing of the messages is necessary to create a "fallback" root |
|
bundle that contains invariant characters across all EBCIC and ASCII codepages. |
|
<br> |
|
<p>NOTE: When creating your resource bundles, the name of the table |
|
resource should contain the package name. For example, |
|
if you have a bundle with a package name of "xyz", then the "en" bundle |
|
should start like this: |
|
<p>xyz_en:table { |
|
<br>..... messages here |
|
<br> |
|
} |
|
<br> |
|
<p><i>not</i> like this: |
|
<p>en:table { |
|
<br>..... messages here |
|
<br> |
|
} |
|
<p>This is different than some of the examples in the <a href="http://oss.software.ibm.com/icu/userguide/ResourceManagement.html">Resource |
|
Management</a> section, but is needed because the -p option is not used |
|
on genrb by the make files. |
<br> | <br> |
<p>NOTE: Pegasus 2.3 only supports simple string resources in the | <p>NOTE: Pegasus 2.3 only supports simple string resources in the |
ICU resource bundles. String resources may only be loaded by key. | ICU resource bundles. String resources may only be loaded by key. |
|
|
| |
<li> | <li> |
pegasus/src/Pegasus/msg/CLI/pegasusCLI_*.txt for all CLI messages (except | pegasus/src/Pegasus/msg/CLI/pegasusCLI_*.txt for all CLI messages (except |
the MOF compiler)</li> |
the MOF compiler)</li> |
</ul> | </ul> |
| |
<p><br>The make messages target will compile these resource bundles. | <p><br>The make messages target will compile these resource bundles. |