EAServer supports localization in the following ways:
Coded character set conversions EAServer supports multiple coded character sets for clients and components. When a client and component use different coded character sets, EAServer automatically converts character data from one character set to another. For example, if a client uses the roman8 character set and a component uses iso_1, EAServer converts string parameters and return values automatically from roman8 to iso_1 when the client calls the component methods.
In accordance with the Java standards, Java components and Java clients use 16-bit Unicode. Unicode contains mappings for all characters in all other known coded character sets.
For C++ components, you can specify code sets using the Management Console. The server Codeset property specifies the default for all C++ components. You can override the default for an individual component by setting the Codeset property at the component level.
For C++ clients, you can specify a character set when initializing the EAServer client ORB by setting the ORBCodeSet property. See Chapter 9, “Developing CORBA/C++ Clients,” in the EAServer CORBA Components Guide.
Localizing Web applications EAServer supports the HTTP 1.1 internationalization features defined in the Java Servlet 2.4 specification. Using these features, you can develop servlets that respond in the language specified by the request header, or configure localized versions of Web site’s static pages.
See Chapter 1, “Defining Web Applications,” in the EAServer Web Application Programmer’s Guide.
Coded character set interoperability with PowerBuilder The Sybase document Guidelines for Code Set Interoperability with PowerBuilder and EAServer includes information about the following topics:
Transmission code set
Client code set
Component code set
PowerBuilder code set
The euro character
