...
To localize runtime strings such as those found when a user logs in to access their task list, the login page, access denied messages, etc. update the "defaults" property file located in the frevvo.war file.
- Refer to the steps above under Server Customization, then.
...
- ..
- Find the file named "default" located in /WEB-INF/data/locales. This file contains all of the strings that have been externalized
...
- Copy the file "default" to another file that is named as one of the language codes listed in ISO 639-2. For example, German is "ger", English is "eng", Portuguese is "por" and Chinese is "chi".
- Selectively edit the target language file and put in test translations.
- Copy the target language file to /WEB-INF/data/locales and re-WAR the war file.
- Re-deploy the WAR file. Re-start.
- Login and navigate to a target test forms. On the form, copy the URL for the form in the editor (use "copy link location" in firefox for example).
- In another browser window/tab, paste the 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 file.
Ensure the test translations show up as expected.
| Warning | ||
|---|---|---|
| ||
The default use mode strings will not be updated simply by editing the default file. You must make a copy as described above, customize the message strings in the copy and then append &locale=<name of copy> to all your use mode forms. |
...
In-house server localization is only for embedding. ie. you use this on a task list embedded in your own web site. This is not for use in Live Forms's UI. ie. if you append &locale=test to the task list as an experiment shown above you will notice that Live Forms's surrounding page content is visible (as expected) and is not localized. This is correct and expected behavior. You are expected to embedded the task list in your own localized web site.
Design Time Strings
Custom Style
Your form's style (colors, font, etc...) can be locale specific. This enables the form designer to select culturally appropriate colors based on the current locale and to match forms to websites that have also been localized using cultural fonts and colors. See locale specific themes for full details To localize design-time strings such as those found in the palette controls, wizard, etc. update the "defaults" property file located in the frevvo.war file.
- Refer to the steps above under Server Customization, then...
- Find the file named "default" located in /WEB-INF/data/locales. This file contains all of the strings that have been externalized
- Copy the file "default" to another file that is named as one of the language codes listed in ISO 639-2. For example, German is "ger", English is "eng", Portuguese is "por" and Chinese is "chi".
- Selectively edit the target language file and put in test translations.
- Copy the target language file to /WEB-INF/data/locales and re-WAR the war file.
- Re-deploy the WAR file. Re-start.
- Login and navigate to a target test forms. On the form, copy the URL for the form in the editor (use "copy link location" in firefox for example).
- In another browser window/tab, paste the 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 file.