The Sage software makes it possible to work in several languages (notably French, English, Spanish, Italian, Portuguese, Chinese). The user, on connecting to the software, chooses the language in which the dialogue screens must be displayed.

This functionality is based on the presence of two tables in the database, storing all the elements likely to be translated : The ATEXTE table, which contains the texts identified by a number, and the APLSTD table, which contains the messages organised in chapters. In these two tables, the language code is present, in order to stock the text in several languages.

The ATEXTE table corresponds to the field titles located on the screens. The standard texts are stored with a number less than 100.000. Specific/custom text is stored with a number greater than this. The access key to this table is composed of two elements : the language and the message number.

The APLSTD table contains the error messages or warnings sent by the software, as well as the local menus and the radio button headers. Each chapter, identified by number, regroups all the elements identified by a number in the chapter. The access key includes the language code, the chapter and the number.

These elements are delivered in a standard fashion with each new major version and can be re-updated at each intermediate version for all standard languages (with the exception of custom/specific texts, and certain local menus that can be set up). Their inclusion in the screens is made during the validation of the software's screens and windows (for performance reasons, the texts are directly inserted as a function of the language in the interface descriptions in XML format).

It can be useful to be able to personalize certain vocabulary elements. For example, it may be appropriate to replace the generic term Representatives by the term Commercial agents, or possibly to replace the term Routing by the term Recipe. To carryout such modifications directly in the APLSTD and ATEXTE tables does not make sense, because these are not permanent. It is for this reason that a specific table has been created, managed by this function.

This table, named AVOCAB in the database, stores a list of exceptions. It is in this way possible to say, for a given language, a chapter and/or a given text number, that a special text replaces the standard text.

A list with the texts to be personalized for a given language or version is entered.

A version being a vocabulary. This makes it possible to deliver several vocabularies in a reference folder as well as to determine which one must be used in the production folder.

Saving the vocabulary entry does not immediately change the vocabulary. To take the new vocabulary into account, the user has to press the Validation button.

A window opens. The user has to choose the version:

Current version 

Standard version

The version selected in the initial screen is the one taken into account. In this case, the ATEXTE and APLSTD tables of the current folder are updated with data from table AVOCAB.

The CUR and VER fields are equal to the version number.

In this case, the ATEXTE and APLSTD tables of the current folder are updated with the reference folder tables that have the same names.

The CUR field is set to 0. The VER field still contains the current version.

Then, the user checks "Screen Revalidation" or not.

The screen revalidation is used to regenerate the application screens and windows. Only elements for which vocabulary was entered. In fact, this means that the XML files representing the user interface contain the new vocabulary. It is based on the ATEXTE and APLSTD tables.

It should be noted that only standard messages (i.e. the ATEXTE messages whose number is inferior to 100.000) can be personalized if the current folder has not been revalidated.

If the current folder has been revalidated, the ATEXTE texts that are superior to 100.000 are added in the reference folder ATEXTE table. So, specific texts can be personalized.

As standard, the AVOCAB table is delivered empty, and it is never modified by an update.

Prerequisite

See also Refer to documentation Implementation

Screen management

Entry screen

The language and the version are selected. The different versions correspond to different vocabularies.

Block number 1

Language (field LAN)

This field defines the language in which the standard messages are to be modified.

Version (field VER)
Current version (field LIBCUR)
Primary language (field LANMAIN)

Grid

Text type (field TYP)

This type can correspond to :

  •  either to the messages table(APLSTD) that notably stores the local menus. In this table, the texts are structured in the form of a chapter number and a message number.
  • or to the texts table (ATEXTE) that notably stores messages coming from the screens. The access key is a message number less than 100,000 for the standard texts, which are only ones concerned with the vocabulary personalization function.
Chapter (field CHP)

When the text to be translated comes from the messages table APLSTD, the corresponding chapter number is specified here.

Number (field NUM)

This field is used to enter the number corresponding to the text to be translated. It should be noted that a text search can be carried out when a message or text containing a given chain of characters is searched. In this case, the right click Message search or Text search makes it possible to enter the chain to be searched for; but the selection window only allows the entry of a message or a text, which means it is necessary to use this facility carefully if it is used on a group of texts. Then moving to the line by right click, described in the function documentation.
Standard text (field STD)

This field is used to display the standard text as it exists in the dictionary shipped with the software.

Text (field TXT)

Entered here is the text destined to replace the standard text in the screens for the folder.

Additional text

This button makes it possible to load into the grid all the texts containing a given chain of characters. Once these texts are loaded, it is possible to enter the translation in the Text column.

Specific Buttons