| Configuration Multilanguage Fields Support (OP)To support multilanguage fields, LN must be installed
in Unicode mode. You can choose the Unicode character set in the LN Installation
Wizard. For more information on the prerequisites for a Unicode
installation, see the Technical Notes. Before you start the configuration of Multilanguage Fields
Support, it is recommended you create a backup of the application data. For
example, you can extract your application data through the Création de vidage séquentiel de table (ttaad4226m000) session, or you can create a backup
through the backup tools in your RDBMS. Etape 1. Enable support for Multilanguage FieldsTo enable support for Multilanguage fields: - Start the Parameters Multi Language Support (ttadv4106m000) session.
- Configure Multibyte and Unicode, and perform the required
steps for this configuration. See the instructions displayed in the session's
window.
- Select the Support de langue multi données check box.
-
Use the Toutes les langues de données toujours disponibles check box to specify whether all
language variants should be read: Si cette case est cochée, then for multibyte
fields that are “Multi Data Language Enabled” all language variants are read. This might result in reduced performance in sessions
with multilanguage fields. - Si cette case n'est pas cochée, 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.
- Save the changes and close the session.
Etape 2. Define data languagesTo define data languages: - Start the Langues de données (ttaad1111m000) session.
- Define the desired data languages. A data language consists
of an ISO 639-1 language code and, optionally, an ISO 3166-1 country code. You
can zoom to the Langues ISO 639 (ttaad1512m000) session and the Pays ISO 3166-1 (ttaad1513m000) session.
- Define the base language: Select a data language and, on
the Vues, Références, Actions menu, click Valider comme langue de base.
Note: The base language is used as a fall back
language. Application data is displayed in the base language if both of the
following scenarios occur: - No data language is defined in the user data of an LN user.
- No data language is linked to the user's software
language.
- Convert the data languages to the runtime data dictionary.
On the Vues, Références, Actions menu, click Convertir les langues de données à Runtime. The conversion
process generates the $BSE/lib/data_langs file.
Important: - Only perform this step if you are sure you no longer
want to change the base language. See the restrictions listed in the online
help of the Langues de données (ttaad1111m000) session.
- During the conversion to runtime, all users must be
logged off.
- When the conversion to runtime has finished, you must
restart the LN environment.
- Close the session.
Data Languages have a status that is used to control their
life cycle. For details, refer to "Life cycle of a data language" in the online
help of the Langues de données (ttaad1111m000) session. Etape 3. Link data languages to software languagesYou must link data languages to the corresponding software
languages. To link a data language to a software
language: - Start the Langues (ttaad1510m000) session.
- To start the Langues (ttaad1110s000) session, double-click a software language. In the Langue de données field, enter the desired data language.
Note: - You can zoom to the Langues de données (ttaad1111m000) session.
- You can only select data languages with status "Base
Language" and "Available".
- If you leave the Langue de données field blank, LN displays the
application data in the data language defined in the user data of an LN user, or in the
base language.
- Save the changes and close the sessions.
To ensure that application software and application data are
displayed in the same language, link the data languages to the software
languages. Etape 4. Register Multilanguage Tables and Table FieldsRegister the tables and table fields that must be
multilanguage enabled. For all package combinations you want to be
multilanguage-enabled: - Start the Tables enregistrées avec champs multilingues (ttadv4137m000) session.
- Select a package combination.
- Add the tables you want to be Multilanguage
Enabled.
Per table, specify whether all languages should be
read for records from the table: - If all languages should be read, select the Toutes les langues de données toujours disponibles check box.
- Otherwise, clear this check box.
Note: - If all data languages are always available, this might
result in reduced performance in sessions with multilanguage fields.
- You can only clear this check box if the application
feature pack is high enough.
- The Toutes les langues de données toujours disponibles setting is saved in the data
dictionary of the table. Therefore, after a change in this setting, a
conversion to runtime for tables is required.
- Double-click a table. The Champs multilingues enregistrés (ttadv4138m000) session starts.
- For each field you want to be multilanguage enabled, select
the Activé check box.
- Save the changes and close the sessions.
Etape 5. Convert to runtimeTo convert the multilanguage settings to the runtime data
dictionary: - Start the Convert to Runtime Data Dictionary (ttadv5215m000) session.
- Select the Tables check box and the Reconfigure Tables check box.
- For package combinations, packages, and tables, specify
the appropriate selection ranges.
Click Convertir en runtime Optionally, start the Données utilisateur (ttaad2500m000) session, and define a data language per user. The data
language specified in the user data takes precedence over the data language
linked to a software language. For more information, see "Language types" in Multilanguage application data (OP).
Remarque If you use the DEM Content Pack with Infor LN, consider
using the MAA0050 (Multi Data Languages for Descriptions) wizard to set up
multilanguage support. You can execute this predefined wizard from the Assistants par modèle de projet (tgwzr4502m000) session after you specified the business
function model for your company. | |