Parameters Multi Language Support (ttadv4106m000)

Use this session to

  • adjust the database factor (Multibyte Factor) for multibyte string fields. See Multibyte for details.
  • display the Unicode indicator. Refer to Unicode for details.
  • display an additional factor for zero width characters.
  • enable support for Multilanguage Fields.


If LN is installed in Native (multibyte/singlebyte) mode, you can specify the Multibyte Factor.


Ensure that you meet these requirements:

  • You are the only user on the system.
  • No running database drivers are present on the system when you start the bshell.
  • Do not run any LN application before starting this session.

After running this session, run these tasks:

  • Log off.
  • Stop the printer daemon.
  • Database drivers must be stopped
  • Run: bw.exe ttadv4206m000.
  • Start the printer daemon again.
  • Suppose the multibyte factor is one. You defined a field of the multibyte string type, with a length of 30. That means that if you specify 30 characters, every character must be only one byte. If you specify only characters of two bytes you can specify only 15 characters.

In the Table Definitions (ttadv4120s000) session you can define table definitions. A table can contain fields of the multibyte string type. Each table field has a certain length. For multibyte string fields, the length specifies the number of positions on which the characters can be placed.


You can enlarge the size of the multibyte strings with the multibyte factor. To specify 30 characters of two bytes in the field of the previous situation, you must enlarge the multibyte factor to two. If you enter a character of one byte in that situation, this character uses two bytes. In this situation you can specify 30 characters of one byte or 30 characters of two bytes.

If you enter a character of four bytes in the previous situation, it takes the place of two characters. So you shorten the length of the field. If in that situation you enter only characters of four bytes, you can enter a maximum of 15 characters.

See these examples:

Multibyte Factor: 1
field length: 20
You can enter: 20 single byte characters
  10 characters of 2 bytes
  6 characters of 3 bytes
  5 characters of 4 bytes
you can also enter: 10 single byte characters + 5 characters of 2 bytes, total 15 characters
Multibyte Factor: 2
field length: 30
You can enter: 30 single byte characters
  30 characters of 2 bytes
  20 characters of 3 bytes
  15 characters of 4 bytes
you can also enter: 15 characters of 2 bytes + 10 characters of 3 bytes, total 25 characters

Looking at the above mentioned examples you can say:

  • The space that is reserved for characters on a multibyte field is: Multibyte Factor * length
  • You cannot specify more characters than specified in the length of the field. If the Multibyte Factor is 2 and the length of the field is 30, you cannot enter 60 single byte characters.

Bear in mind that when you enlarge the database factor the table takes more space. When using only single byte characters, and a database factor of four and the field length is, for example, 30. The space that is used is 120 bytes for 30 characters. In that situation you can better use a database factor of one. Then the same string takes only 30 bytes.


To support all languages that are available for LN in one environment, you must install LN in Unicode mode. Unicode is the standard for multi-language support. It provides a unique code for each character regardless the language.

If LN is installed in Unicode mode, the Multibyte Factor field is read-only and has a fixed value of 4.

  • You cannot use this session to switch from Native (multibyte/singlebyte) mode to Unicode mode. For details on the conversion to Unicode, see the Infor Enterprise Server 8.4 - Conversion Guide Database to Unicode (U8887 US).
  • Before storing the settings in the Multibyte Parameters (ttadv406) table, the session corrects the Multibyte Factor with the Factor zero width characters. See the field help for details.

Field Information

Multi Byte

If this check box is selected, the database factor for multibyte string fields is active.


Indicates whether LN is installed in Unicode mode.

Multibyte Factor

The Multibyte Factor is used, during the conversion to runtime of the domains, to determine the internal length (CLEN) of a domain in case of multibyte strings.

For Unicode enabled installations the Multibyte Factor has a fixed value of 4. Before storing the settings in the Multibyte Parameters (ttadv406) table, the Multibyte Factor is multiplied by the Factor zero width characters incremented by one:

               Multibyte Factor * (Factor zero width characters + 1)

Example: with a Multibyte Factor of 4 for Unicode enabled installations and a Factor zero width characters of 0, the factor with which a multi byte string will be multiplied is: 4 * (0 + 1) = 4.

Factor zero width characters

This factor is used to determine the width on screen and on paper for zero width characters, such as Thai accents and other accents. It is used in Native (multibyte/singlebyte) mode and in Unicode mode as well.

This field is always read-only and has a fixed value of 0.

Multi Data Language Support

If this check box is selected, LN can store shared application data in multiple languages. Depending on the user’s software language, the application data can be displayed in the same language too. For details on the procedure to configure Multilanguage Fields Support, refer to Multilanguage application data (OP).

Note: To support multilanguage fields, LN must be installed in Unicode mode.

All Data Languages Always Available

If this check box is selected, then for multibyte fields that are “Multi Data Language Enabled” all language variants are read. For example, if an item description exists and this item is multi language enabled, then the description can exist in German, Dutch, English or French. When reading this record, all four languages are read.

If this check box is cleared, then only the language variants of the user's language are read. When a report is printed, the application can select the language that is read from the database or force to read all languages.

Note: If all data languages are always available, this can result in reduced performance in sessions with multilanguage fields.