Changes in translations over time

The current Vertec translation system is described in the article Multilingualism with Vertec .

In this article, you can find information about the translations in older Vertec versions:

MLStrings

Native language from Vertec 6.4

From Vertec 6.4, in addition to the four languages DE, EN, FR and IT, there is a “native” language NV, in which a term to be translated can be entered. This is automatically translated by the translation system into the relevant language in the respective program jargon. In this case, the other languages do not have to be set.

On the first boot after the convert, Vertec checks the existing MLString attributes. If an attribute only defines an EN or DE text, this term is entered as a native language, i.e. as NV:

• If an EN text is defined, it is set as the NV text
• If no EN text is defined, but a DE text is defined, this is set as the NV text
• If neither an EN nor a DE text is defined, no NV text is set

Since the texts already set do not change and take precedence over the native terms, this does not change anything in existing installations. The adaptation would only be noticeable if you later changed to a different interface language, which had not previously set a value.

DD from Vertec 6.5.0.9

Starting with version 6.5.0.9, the language DD (German Germany) is also supported.

Vertec translation system

Up to version 6.4.0.8

The translation was done in runtime on the user interface. In some cases, this could lead to problems with the customer’s user data whenever it happened to be named the same. For example, PM in the tree in a German Vertec was always shown as PL (because PM was interpreted and translated by the translation mechanism as project manager).    

From version 6.4.0.9

As of Vertec 6.4.0.9, the date is no longer translated on the interface, but in the business logic. This means:

• Terms are only translated if the object has an entry ID: By default, all objects created by Vertec contain an entry ID (see Using entry ID).
• Therefore, only names of objects that have an entry ID are translated. Object created by customers, such as folders, are no longer translated.

  • If you still want to have the name of a self-created object translated by the translation system, you can assign an entry ID to the object (via Python via argobject.eintragid=”XX” on the corresponding object).

  • Exception: Display names overridden by class settings are translated without an entry ID condition.
• Pay attention to the renderer rndTranslate  in the list settings : This is no longer needed under the new system.
  • This fixes the problem of confused sorting in lists, as they sort in the source language, which corresponds to the displayed term without a translate renderer.
  • This has no effect on the translation of the list titles. This is done as before via the MLString function.
  • Translate renderers will not be removed from existing customer installations even with the update to 6.4.0.9. If they interfere anywhere, you can manually remove them from the list settings.

Customer dictionary UserDict for customer-specific translations (Vertec on-premises and versions prior to 6.5.0.9 only)

Starting with Vertec 6.5.0.9, customer-specific translations can be managed directly in Vertec. The exact procedure is described in the article Multilingualism in Vertec .

In Vertec versions prior to 6.5.0.9, customer-specific translations were stored in a translation file.

To create a customer-specific translation, a text file named UserDict.txt is created in the Vertec installation directory and saved with the ANSI encoding.

The following files are required for a text dictionary:

• UserLng.txt (provided by Vertec)
• UserDict.txt (created by customer)

The customer-specific dictionary is used if the two files UserDict.txt and UserLng.txt are present when you start Vertec.

The order of translation is:

1. Priority: UserDict.txt
2. Priority: Vertec.mld

The UserLng.txt file is supplied as a template file by Vertec and is located in your Vertec installation directory. It contains all available Vertec languages. If you open it with a text editor, it looks like this (turn off line breaks):

To create a translation, a file called UserDict.txt must be created. This is a normal text file. The columns are separated by tabs.

The easiest way to create such a file is to use Microsoft Excel. The first column contains the term in the native language, i.e. the original term from Vertec. For each language defined in UserLang.txt, another column is added, in the same order as in the language file.

Only the terms that differ from the native language need to be translated. The mandate language inherits from the project language, and German Germany inherits from German Switzerland.

For example, the Excel file looks like this:

When saving, specify UserDict.txt as the file name and select the file type text (tab-separated) (*.txt) as the file type. Save the file to the Vertec installation directory.