When a localized client application connects to TRS, Adaptive Server, or Open Server, the server checks to see if it supports the client’s language and character set. If it does, then the server:
Automatically handles all character set translation
Issues server messages in the client’s language and character set
If TRS does not support the language or character set sort of the client, it issues a warning message to this effect, and Client-Library fails the connection. However, DB-Library accepts the connection.
Table C-1 describes these client and server behaviors:
Does server support client character set? |
Does server support client language? |
ASE server behavior |
Open Server behavior |
Client-Library behavior |
DB-Library behavior |
|---|---|---|---|---|---|
yes |
yes |
Performs all necessary message translation and character set conversion |
Performs all necessary message translation and character set conversion |
Operates normally |
Operates normally |
no |
yes |
N/A for Adaptive Server, because when Adaptive Server supports a language, it supports all character sets for that language |
Uses the language and character set of the Open Server application |
N/A for Adaptive Server; fails the connection for Open Server |
N/A for Adaptive Server; accepts the connection for Open Server |
yes |
no |
Uses the language us_english and the client’s character set |
Uses the language and character set of the Open Server application |
Fails the connection |
Accepts the connection |
no |
no |
Uses the language us_english and the character set ascii_7 |
Uses the language and character set of the Open Server application |
Fails the connection |
Accepts the connection |
