Multi Language Setup
Multi Language Setup
The language application also allows the default number formats to be specified for a language, for
example French users would normally expect to see the number 12345.67 displayed as 12.345,67, whereas
an English user would display the number as 12,345.67. The default for the language is defined in the field
AMOUNT.FORMAT as first the thousand delimiter and then the decimal point delimiter. This setting can be
overridden in the USER profile, field AMOUNT.FORMAT.
A further feature that is available is the ability to be able to specify the minimum length of description
language fields by language. Often the minimum length is defined as 3 characters for description fields in
English as anything shorter would ultimately have no meaning. However in some languages one character
is sufficient to convey sufficient meaning. By defining this field to the minimum number of characters
users will be allowed to enter the specified minimum characters.
The Attributes field allows the User to justify all text and fields from right to the left.
T24 performs initial edit checks according to the type of field. This checking will ensure that only valid
characters may be entered. A set of valid characters is defined using the T24 application ASCII.VAL.TABLE.
The ASCII value of the allowed range of characters is defined. Multiple ranges and individual characters
may be specified.
The Standard record character sets for each T24 character type are released with the key of
STANDARD.XXX where XXX is the character type. These records cannot be modified, but can be copied and
modified as required. The example in Figure 3 shows a record called TEST.A, which allows additional ASCII,
characters 200 - 220.
The application ASCII.VAL.TABLE is used to link a type of character validation to the character set defined in
ASCII.VALUES. This may be defined for individual applications, for specific language fields either for an
application, or any language field, or as a default for all fields of the specified type.
In order to identify the validation type for a specific field, the STANDARD.SELECTION record for the
application should be viewed. The validation type can be found in the associated SYS.VAL.PROG. The
example in Figure below shows the field type for the CUSTOMER fields SHORT.NAME and NAME.1. The field
SHORT.NAME can seen as type IN2SS whilst NAME.1 is type IN2S.
The screenshot below shows an example of an amended alphanumeric (IN2A) ASCII.VALUES record to allow
the character set TEST.A for German (DE):
STATIC.TEXT
This application is used to translate the T24 Screen prompts and to provide translatable text for written
reports. Details of reports, which use STATIC.TEXT records, are listed in the relevant chapters of the user
guide.
Screen messages and prompts used in T24 are contained in the record, GLOBAL.TEXT. The English
equivalents are shown below:
STATIC.TEXT 5
Setup
STATIC.TEXT 6
Setup
Note that item (45) “PLEASE ENTER YOUR SIGN ON NAME” and (57) “PLEASE ENTER YOUR PASSWORD” will
only use the English Text, since at this point the user has not yet signed in and their language has not been
determined. If all or most users are not English, the English version of these values could be changed to the
local language.
DYNAMIC.TEXT
This application is used to translate messages generated from T24 applications, such as error messages and
overrides. It is also used to translate application field names into the user language.
Dynamic text records are automatically created in the unauthorised file when a foreign language user
receives a message or prompt for which a translation cannot be found. In this way the translations can be
added as required, most common used text will be translated first.
Application Text
Application field names are also translated using the DYNAMIC.TEXT application. Each field name is
individually translated. Field names to be translated must be specified in the format
APPLICATIONFIELD.NAME. Multi-value elements should not be specified, e.g. the field XX.OTHER.OFFICER
in the application ACCOUNT should be defined as ACCOUNT*OTHER.OFFICER.
Note the standard 9 system fields (RECORD.STATUS to AUDIT.DATE.TIME) do not require the application id
to be specified.
DE.FORMAT.PRINT
This application is used to specify the format of printed delivery output. The format of the record key is
message, Advice format, User format, Language code. For example the output for a Money Market confirmation
would be 320.1.1.GB. All text specified should be in the language identified in the key.
DYNAMIC.TEXT 7
Setup
The language to be used for the advice is based on the CUSTOMER to whom the message is addressed. It is
defined in the application DE.PRODUCT and CUSTOMER as the default.
Enquiry
Translation of header items is achieved by entering the foreign language text in the corresponding multi-
value of the HEADER field.
Items displayed in the ENQUIRY may be translated in two different ways, the first uses the DYNAMIC.TEXT
mechanism, specified by a TYPE of TRANSLATE; the second used for language data fields uses a TYPE of
LANGUAGE.
The example in the figure below of an enquiry, based on the CUSTOMER application, uses both TRANSLATE
and LANGUAGE types.
Enquiry 8
Setup
Note that the language order could specify a VERSION with English and German only by entering 1 & 3 the
LANGUAGE.CODE fields.
REPGEN.CREATE
In the same manner as VERSION, you can specify language options in REPGEN.CREATE for all or a specific
language.
• jBASE 4.1.1
• Desktop 1.2.994
• jBASE Connection Manager
Multi-byte characters are not supported by T24 i9 in native Windows or via the Classic interface or a
Telnet connection.
Consult the jBASE manuals on setting up the Connection Manager and Internationalisation.
General Information
Multi-byte characters will be stored in UTF8 form in the T24 files. Desktop will use Unicode to handle the
characters and will translate the characters as it receives them from or sends them to the T24 server.
The following steps will show you have to setup an additional language on the Microsoft windows 2000
operating system; this may differ on any other operating systems. Please refer to the documentation
supplied with your operating system.
Select any of the languages you want to configure like the following.
For Example:
Check any of the languages you want to in the Regional Options Dialog Box (Language settings for the
system). See below.
Select any language from the Select System Locale dialog box.
A Windows based message will appear on the screen like below and it will ask u for the Windows 2000
language pack which comes along with Windows 2000.
You will have to restart your PC for the change of System Locale to take effect
Now select the tab Input Locale in the Regional Options dialog box and make sure the languages selected
earlier in the Select System Locale dialog box appear in the Installed input locales frame as shown
below.
In the TCServer the environment.vars file in the conf directory should have a field called