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).
There are two options for the runtime and design-time translation strings.
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.
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):French.
|Unicode File with Unicode Equivalent||Upload Control in Palette|
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.
Test To test that your Runtime string translations show up as expected, for example on your Task list by:, follow these steps.
If you append &locale=spa to the task list as a test as discussed above you will notice that
Test that your designer translations show up as expected by:
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.