...
- Stop you server
- Uncompress/expand the frevvo.war file. This is typically located here: <frevvo-home>/tomcat/webapps/frevvo.war
- Find the file named you need to modify located in /WEB-INF/data/locales. These file contains all of the strings that have been externalized as well as the list of supported locales and directions.
- Make the changes as described in the topics Adding Locales, Runtime Strings, Design-Time Strings below.
- Re-WAR to create a new updated frevvo.war file.
- Re-deploy the WAR file, typically located here: <frevvo-home>/tomcat/webapps/frevvo.war
- Re-start your server.
- 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.
...
- 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-startEx: /WEB-INF/data/locales/spa
- Refer back to final steps under Server Customization.
| Warning | ||
|---|---|---|
| ||
The default runtime 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 runtime Urls. |
...
Test that your translation shows up as expected, for example on your Task list by:
- Get the share Url to your task list
- 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.
Test that your translation shows up as expected.
| Code Block |
|---|
http://localhost:8082/frevvo/web/tn/nancy.com/subject/designer/tasks?submissionState=PENDING?embed=&locale=testspa |
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 spa 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.
...
- 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.locales Ex: /WEB-INF/data/locales/spa
- Refer back to final steps under Server Customization.
Test that your translation shows up as expected by:
- Login and navigate to a target test forms in the forms home page. On Click the form, copy the URL for the form in the editor (use "copy link location" in firefox for example).'s share button and copy the Raw Form Link choice
- 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 design-time 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> the form edit Url. |
The install contains a locale file named test that you can try out. If you are not logged in, Live Forms will require you to authenticate by displaying the login page. The locale choice will automatically flow to the login page and those stings will be translated as well.
| Code Block |
|---|
http://localhost:8082/frevvo/web/tn/nancy.com/subjectuser/designer/tasks?submissionState=PENDING?embed=&locale=test |
...
/app/_bgWqAH0xEeGX-qtBMhaCVw/formtype/_b9WKQIPPEeGZwdXdRCHn6A?_method=post&embed=true&locale=spa |
In-house server localization is only for OEM embedding. ie. you use this on a task list the form designer embedded in your own web site. This is not for use in Live Formsthe '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. UI.
Custom Styles
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 for full details.