Addition and setup of a non-standard language 

The SAFE X3 technology software is used to manage a group of standard languages, which are systematically supplied on the CD-ROM. However, it is possible to add extra connection languages via a manual procedure.

This procedure does not guarantee the evolution of the messages of the language when a standard patch, likely to add messages, is delivered. In this case, it is necessary to add them in the non-standard language which has been created.

It is strongly recommended to export the texts of the new language from the APLSTD and ATEXTE tables to a backup file once the process has been carried out, in order to be able to import them again if need be. Sage does not guarantee that specific maintenance functions in folder management will not lead to the loss of potential messages of a non-standard language.


Prior to any translation of a non-standard language, it is necessary to obtain a new language code from Sage X3. Any request to add a language code is taken into account for the next release issues after the request date. This new release will include:

  • the new language in the dialogue box that is used to connect to X3,
  • the new language in the languages table, that is then used to create the folder with the language code to be managed.

Starting the translation

There are two translation methods:

  • Translation outside Sage X3: this translation is carried out externally but is strongly recommended in the case of starting a new translation, this method being the most rapid.
    To export the texts (ATEXTE table) and the messages/local menus (APLSTD table), it is necessary to use respectively the TRXXLS and TRDXLSPimport/export templates.
    If the language uses UNICODE characters, it is necessary to check import templates and modify them if need be.
  • Translation in Sage X3: this is carried out by using the standard translation tools that can be activated thanks to the DISactivity code. The use of these tools is recommended notably in the case of modifications or additions to the translation.

Installation of the environment

SEEINFO This stage only starts with the release which integrates the non-standard code.

The environment that will receive the translation must be installed as follows:

  • primary level: X3 parent folder,
  • secondary level: translation folder and production or prototype folder,
  • last level: no folder or production folder.

Each secondary or last level folder must contain:

  • the code for at least one standard language,
  • the non standard language code,
  • the DIS activity code must be set to 'Yes'.

The translation folder is the reference that is used to identify the translation differences. It is also used to change the translation following patches or updates: it is possible to determine the messages and texts remaining to be translated at any time in the Untranslated Texts-APLSTD documentation.

The production or prototype folder (whether this is the secondary or last level) is the destination folder for the translation.

The validation of each folder is used to manage the standard language dictionary and to create the architecture necessary for the importation of the non-standard language.

Setups in Sage X3

1 - When all the previous setup, outside Sage X3, has been carried out and the files have been renamed in .txt extension, import these to your folder, via the AIMPATD function for messages and the AIMPATR function for texts.
Check if the language uses UNICODE characters and if necessary, modify the import templates.

2 - In your folder, open the Language function (GESTLA).

  • If the code does not exist in the list, it is possible to add it as well as its description (in the connection language) or just modify it if it does exist.
    If the language is managed by the unicode standard, select 'Yes' in the [Unicode language] field.
    The language that has been set up is your connection language, select 'Yes' in the [Connection language] field.
    Enter the ISO code if necessary.
  • Right click on the description to enter the description translation function. Add the new code and its translation.

3 - Upon update of the language table, translate into the new language the descriptions of the other languages using the description translation function. Conversely, translate the description of the added language into the other languages (at least those which are likely to be used as connection language).

4 - Add the new language to the record of the folder ("Init" tab) and tick the [Translation ref.] field in the line of the added language.

5 - Open the Dictionary validation function (VALDICO) and tick the [Addition of a language] box.
Validate with the help of the [OK] button.

6 - Open the Create descriptions function (ALANG), select the line corresponding to the language that is being set up and tick (by double clicking) the [To generate] field. Validate by clicking on [OK].

7 - Log off.

8 - Copy the file that contains the messages of the added language engine from [X3_Install_dir]\folders\X3_PUB\X3_ROOT\GEN\ALL\LIB\"language code"  to the [X3_Install_dir]\runtime\lan directory of the main processing server and if necessary, of the other servers.

9 - Log on again in the initial setup language.

10 - Close the application so that the program can save the various operations.

11 - It is now possible to log on to the application in the new language and use the product in this language.