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 the client uses the roman8 character set and the 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 and ActiveX standards, Java components, Java clients, ActiveX components, and ActiveX clients all use 16-bit Unicode. Unicode contains mappings for all characters in all other known coded character sets.
For C and C++ components, you can specify code sets using EAServer Manager. The server Codeset property specifies the default for all C and C++ components. You can override the default for an individual component by setting the Codeset component property.
For C++ clients, you can specify a character set when initializing the EAServer client ORB by setting the ORBCodeSet property. See Chapter 15, “Creating CORBA C++ Clients,” in the EAServer Programmer’s Guide.
For MASP clients, the code set is specified as an Open Client or ODBC property before the client connection is opened. See Appendix A, “Executing Methods As Stored Procedures,” in the EAServer Programmer’s Guide.
Localizing Web applications EAServer supports the HTTP 1.1 internationalization features defined in the Java Servlet 2.3 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 21, “Creating Web Applications,” in the EAServer Programmer’s Guide.
Using non-ASCII text and the message service You can store, retrieve, and display non-ASCII text correctly when using the message service database by:
Specifying the Server Name for the message service connection cache using a jConnect™ for JDBC™ URL.
Changing the character set of the message service database to be consistent with the language you are using.
See Chapter 8, “Setting up the Message Service,” in the EAServer System Administration 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
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
