This section provides information about how the Administrable Language Displays feature behaves in certain circumstances.
Note:
The considerations stated here apply only to the ISO 8859-1 encoding capability.
The ASCII (0x00 – 0x7F) does not require any conversion.
The range 0x80 – 0x9F is not supported when Display Character Set on the System Parameters Country-Options screen has the value Roman.
If CID is sent through a tandem server, the CID could display incorrectly on the server where the call terminates if that server does not support 8859-1/Eurofont conversion, or if the QSIG trunk does not have the conversion feature enabled.
If Communication Manager receives a name in the simple name form from another vendor and if that name contains accented characters, the name will not display correctly. This is because Communication Manager expects a simple name to use the Eurofont character set.
It is a known issue that this design does not properly handle names received in the extended name form in character sets other than 8859-1. For such cases, the characters outside the ASCII range will be improperly mapped to Eurofont resulting in an incorrect name display.
The following list describes the situations when the Display Messages screen is disabled:
After loading an avaya_user-defined.txt file, Communication Manager disables the following qualifiers for both the change and display display-message commands:
ad-programming, malicious-call-trace, softkey-labels, auto-wakeup-dn-dst, miscellaneous-features, time-of-day-routing, button-labels, transfer-conference, call-identifiers, property-management, view-buttons, date-time, self-administration, vustats, and leave-word-calling.
After loading an avaya_user-defined.txt file, Communication Manager disables the page 1 of the Posted Messages screen for both the change and display display-message commands. However, you can enter translations for the fixed languages in the Posted Messages screen.
After loading a custom_user-defined.txt file, Communication Manager disables the last page of the Posted Messages screen and relates to the user-defined translation for both the change and display display-message commands. You can, however, enter translations for the fixed languages in the Posted Messages screen.
After loading an avaya_user-defined.txt file, Communication Manager disables the user-defined keyword for the Label Language field on the Abbreviated Dialing screen. You can, however, enter translations for the fixed languages in the Abbreviated Dialing screen.
