When you choose the option to review or change a partition's multilingual attributes on the housekeeping menu, a screen similar to the following will result:
From the Multilingual Partition Languages screen it is possible to:
Select the language(s) that you wish to review or change or use the Add function key to add a new language that is to be supported in this partition.
On the following screens, you may use the CHANGE key to place the screen in change mode and make the desired changes.
The following input options apply to changing a partition's multilingual attributes:
A 1 to 4 character code that uniquely identifies the language within the partition. It should be the same code used for the same language in other partitions, allowing language matching on import and export runs. If it is a base language then it should be the same code as detailed in the LANSA Multilingual Application Design Guide. Recommended codes are also in the LANSA Multilingual Application Design Guide.
A 1 to 20 character full description of the language. This is used on some reports as an unambiguous description of the language being used.
DBCS Support Required
Whether or not the language requires DBCS (double byte character set or ideographic) support to successfully implement applications using this language.
IGCCNV Support Required
Used to indicate whether IGC conversion (via the DDS keyword IGCCNV) is required for applications generated under this language in this partition. YES indicates IGC conversion is required. Any other value will indicate that IGC conversion is not required for this language.
Function Key / Description
If IGC conversion is required, specify the function key that is to be assigned to the IGC conversion task and a short form description of the function key. Choose a function key number in the range of 01 to 24 so that it does not conflict with any other CUA assigned function key in this partition. You must also provide a short form description of the function key.
Important Note: If you are using a DBCS language you may find that you cannot specify the function key description in the DBCS language initially. To solve this problem:
If IGC conversion is required, specify the line on the screen panel that the conversion area is to be placed.
It is recommended that the conversion area be placed on the same line as the message area. If your system is configured to show messages on line 22, it is advisable to also place the IGC conversion area on line 22.
RLTB Support Required
Whether or not the language requires right to left support (or bi-directional) to successfully implement applications using this language.
Specifies if this language is the default language for this partition.
One of the languages defined using these options must be nominated as the default language. The default language is an important language and has the following implications:
Specifies if this language is a development language for this partition. That is, applications can be developed in LANSA with all development panels being displayed in the nominated language.
Warning: The ENG (English) language is a development language by default and must not be specified as a development language.
You should contact your product vendor before indicating if any language is to be used as a development language to confirm its availability for use in development.
PC Locale uppercasing required
In a client/server configuration, this option is set on each PC during system initialisation on the PC.
This option is only used with fields created without the attribute LC (Lowercase entry allowed) specified. When LC (Lowercase entry allowed) is not specified, that field's input values in the range a to z will be converted to upper case (that is A to Z).
Set this option to:
YES if you wish to have characters outside the a to z range also converted to upper case, for example, from à to À
NO, if you want the special characters to remain as lower case while those in the a to z range are converted to upper case. This could be the result: RESUMé.
Default is NO.
ISO language code
The ISO 639-1 two-letter language code. It can be optionally qualified by an ISO 3166-1 two-letter country code. The language code or qualified language-country code must be a valid registered code, for example: en (English), en-US (English–United States) and en-GB (English–United Kingdom). This field is case sensitive. Values must be entered in the correct case (for example: en-US).
The ISO language code is commonly used in Web applications and when interfacing with external libraries that support localization.
For more information, refer to Input Attributes in the Technical Reference Guide.
Refer to Creating or Changing System Partition Definitions for details.
Refer to Creating or Changing System Partition Definitions for details of the following items:
Process Menu Prompt Line
Help Option On Menus
Return Prefix On Menus
Exit Option On Menus
Library For Help Panel Groups
This item is shown only if Panel Groups are used in this LANSA system for the presentation of HELP text (see section on 'using Panel Groups for HELP text'). The specification of a library name is optional. If no library is specified, any Panel Groups created will be placed into a library with the generated name 'PN@pppllll' where ppp is the partition identifier, and llll is the language. If a library is specified here, any Panel Groups created for this language will be placed into this library. The library does not need to exist when the name is specified here. It will be created, if required, when the first Panel Group is compiled for this language. The name will then be put on file automatically.
This library will be added into the library list at the start of a LANSA session. It should be specified, if required, before panel groups are created for this partition, and should not be changed later. If the library specified here is changed after panel groups have been created, these Panel Groups should be moved to the new library, or deleted and re-created, so that the HELP text for this language is found at execution time. This is the user's responsibility.
User Message Files
Up to 10 user defined message files may be nominated for the language. They are used to execute OVRMSGF commands when entering applications defined within this partition.
Refer to the LANSA Multilingual Application Design Guide for detailed information on specifying message files.
IBM i EBCDIC CCSID
When text is moved from the client to the server and vice versa it must be translated from one system's code page to the other. Specify the CCSID to be used to translate text to the correct IBM i format for the selected language. If the code page is not entered then the default CCSID for the language will be used by the LANSA system.
Windows ANSI code page
When text is moved from the client to the server and vice versa it must be translated from one system's code page to the other. Specify the code page to be used to translate text to the correct Windows format for the selected language. If the code page is not entered then the default code page for the language will be used by the LANSA system.
Linux code page
When text is moved from the client to the server and vice versa it must be translated from one system's code page to the other. Specify the code page to be used to translate text to the correct Linux format for the selected language. If the code page is not entered then the default code page for the language will be used by the LANSA system
Function Key Short Form Descriptions
Allows you to specify the short form description for all SAA/CUA function keys in the appropriate language. For details, refer to If you Comply with SAA/CUA Standards and Guidelines.
Delete Partition Language
The delete key will only delete the record in the LANSA internal file associating the language with the current partition. The language is then not available for use in the current partition. There may be many other records in the internal LANSA multilingual extension files, i.e.process and function descriptions in the now deleted language. Refer to the parameter Delete Deleted Partition Language Extensions in Submit Job to Reorganize the Database for further details.