Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


 will detect the language setting of the browser and search for a corresponding ISO named translation file in the WEB-INF/data/locale directory. If a translation file exists, the designer and server-wide runtime strings display with the translations specified in this file. If the translation file does not exist, the designer and server-wide runtime strings display in English - the language of the default translation file. If a locale-specific file does not contain a particular property or string, then the English translation in the default file is used.

When you first examine the locale directory, you will notice a sample translation file named ger (German). Let's say you copy/modify the default translation file to make a second file for German named with the ISO 639-1 two-character code - de. Then you create/modify another German translation file and name it de_AT for German/Austria. 

Select German/Austria (de-at) as the language in the Firefox browser and log into in to 

 as  as a designer user. The designer displays the translations from the de_AT file. If thee the de_AT translation file was not present in the WEB-INF/data/locale directory, the designer and server-wide runtime strings display the translations specified in the ger (German) file. If the ger file was not present in the locale directory, the translations in the default file (English) would be used.

To display the designer and server-wide runtime strings using the translations from the de (German) file, you would have to change the language in the browser to German (de).

ISO 8559-1 Unicode Characters

There are two options for the runtime and design-time translation strings.

  1. UTF-8 encoded language files named with ISO language codes without any extension. Examples would be spa, ger, de, es, de_AT, etc.
  2. Unicode versions using use the same name but with an extension of .unicode. For example, the French unicode language file would be named fre.unicode. This file must contain the unicode equivalent for any international characters that cannot be properly represented in the UTF-8 language file. Some examples are shown in the image:Here are some examples.
    Image Modified

For example, let's say you are translating the designer to Spanish French (esfr) and the Spanish French word for the video Upload control is vídeotélécharger.

  1. Follow the steps above to copy the default properties language file to make the spafre.unicode file.
  2. Provide the translations.
  3. To properly represent the Ãé, you must provide it's its unicode equivalent. You can use a tool such as native2ascii, which is included in the JDK, to convert the international characters to their unicode equivalents. Be sure to save the file with UTF-8 encoding before running the conversion.
  4. Or you can manually encode international characters by replacing it with \uxxxx where the xxxx is the 4 digit hex value for the unicode character.
  5. Refer back to steps 4 - 6 under Server Customization for the instructions to complete.

Here is what the Video Upload control looks like in the designer if the entry in the spafre.unicode file for the Spanish French word for video contains the unicode equivalent for the à the é (\u00eu00e9). The language of the browser is set to Spanish (es - if using Firefox):Image RemovedFrench.

Unicode File with Unicode EquivalentUpload Control in Palette

Image Added

The UTF-8 and unicode files for a language must reside in the <frevvo-home>/tomcat/webapps/locale directory. You can mix the two different file types with regards to different languages. For a particular language/locale, the system will try to load the UTF-8 version first.

Testing Runtime and Design-Time Translations

Runtime Translations:

Test To test that your Runtime string translations show up as expected, for example on your Task list by:, follow these steps.

  1. Get the share Url URL to your task list.
  2. In another browser window/tab, paste the url URL and append "&locale=yyy" where yyy is the target language code and the name of the target language file that was added to the war WEB-INF file.
Code Block

If you append &locale=spa to the task list as a test as discussed above you will notice that 

' surrounding page content is visible (as expected) and is not localized. This is correct and expected behavior. You are expected to embed the task list in your own localized web sitewebsite.  

Design Time Translations: 

Test that your designer translations show up as expected by:

  1. Set your browser to the target language.
  2. Login to the
     as a designer user. 
  3. Edit a form to verify the designer strings are translated to the language specified by the language file that was added to the war file. An example is shown in the Chinese translation example above.

Date and Time Controls


You can add support for International characters for a form's Print view and submission PDFs by adding unicode Unicode fonts with broad language support to the 

 war file. Refer to this documentation for the details.