pegasus/doc/Globalization_HOWTO.htm - diff

Return to Globalization_HOWTO.htm CVS log

Up to [Pegasus] / pegasus / doc

Diff for /pegasus/doc/Globalization_HOWTO.htm between version 1.3 and 1.4

version 1.3, 2003/07/30 16:14:26

version 1.4, 2003/09/08 21:32:02

Line 2

<html>

<head>

</head>

Line 69

The CIM-XML documents contained in the HTTP messages</li>

<li>

Repository files and MOF files  (TODO - 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>

</ul>

<li>

Support UTF-16 for internal data.</li>

Line 126

Line 129

External data to Pegasus is encoded in UTF-8.  Internal data is encoded

in UTF-16.

External data includes the CIM-XML messages passed over the network,

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

"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

ASCII is assumed.  The Pegasus MOF compiler supports UTF-8 encoding

ASCII is assumed.

in the MOF files.  (TODO - remove this statement if this is

not in 2.3)

The internal support of UTF-16 is encapsulated in the Pegasus String

class.  This class has been updated to contain UTF-16 characters. 

Line 309

Line 311

similiar to the one shown in the Resource Management section, including

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

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.

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:

xyz_en:table {

..... messages here

}

not like this:

en:table {

..... messages here

}

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.

NOTE:  Pegasus 2.3 only supports simple string resources in the

ICU resource bundles.  String resources may only be loaded by key. 

Line 988

Line 1013

<li>

pegasus/src/Pegasus/msg/CLI/pegasusCLI_*.txt for all CLI messages (except

the MOF compiler)</li>

the MOF compiler)</li>

</ul>

The make messages target will compile these resource bundles.

Legend:

Removed from v.1.3
changed lines
	Added in v.1.4

No CVS admin address has been configured