Translation files

ELO provides a number of options for translating texts with the help of translation files. This section explains how you can do this.

Translation, filesVariables

You can use variables from translation files in:

  • Names of fields in metadata
  • Names of forms in metadata
  • Keyword lists
  • Node names in workflows
  • Name when forwarding workflows
  • In scripts and forms

The translation files are stored as the file type PROPERTIES. The following conditions apply:

Properties
  • Character encoding: UTF-8
  • Path in ELO: Administration//Localization//custom
  • One for each language: A properties file with the corresponding country code (de, en, fr, ...)
Character encodingUTF-8

The following example describes how to work with translation files using translated fields in the metadata. In principle, this method works for the other points listed above. For detailed information about using translations in workflows and forms, refer to the ELO Java Client Workflow manual.

Example

In the following example, we use a metadata form named Photo.

Step by step

1. Create a text file. You can enter any name for this file. However, you must add an underscore between the end of the name and the language abbreviation and use the file extension .properties. In our example, this is:

masksAndFields_en.properties

2. For each field, enter a variable and the name of the field in the respective language. You must use the following format:

<prefix>.<variable>=<text>

  • Prefix: You can choose any prefix you like. However, you should use the same prefix for a specific purpose.
  • Variable: You can choose any variable you like. In this example, we use the group name of the corresponding field to make it easier to map.
  • Text: The text is displayed as the name of the field. The language should correspond to the respective language abbreviation.

3. For each language, create a copy of the first properties file with the corresponding language abbreviation. Otherwise, the name of the file must match that of the first file. For example:

masksAndFields_de.properties

4. Replace the texts in the corresponding language.

5. Save the files in ELO. Use the path:

Administration//Localization//custom

Optional: To provide a default language if a language file is not found, save a corresponding file without the language abbreviation.

6. Open the ELO Administration Console.

7. Go to the Field templates area.

8. Select a field of the selected form.

9. Enter the variable for the corresponding field in the Translation variable field. The variable must match the variable in the properties files.

10. Save the changes.

11. Repeat steps 8-11 for all fields of the form.

12. Reload the ELO Indexserver.

The field names are now displayed in the respective language.

Was this information helpful?

  • Yes
  • No


The captcha is not correct. Please check the code.

*Mandatory fields

  We do not reply to support requests sent through this form.
If you require assistance, contact your ELO partner or ELO Support.