...

The form Url parameter locale= controls which language the form renders. If the parameter is not present or the value is empty (&locale=) or is set to a locale code for which no translation file exists, then the form will render in the default language. To render the form in a different language such as in Spanish rather than the default add &locale=spa to the form Url. The test button and the share button on the Locale Home Page do that for you automatically. The test & share buttons on the Forms Home Page are by default for default locale.

Server Configuration

Live Forms In-house supports the ability to customize use mode and design time features on the server.You can add runtime and design time strings and add additional locales and RTL languages. To make any of these changes to your In-house  server you must follow these steps:

• Stop you  server
• Uncompress/expand the frevvo.war file. This is typically located here: <frevvo-home>/tomcat/webapps/frevvo.war 
• 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.

Adding Locales

To add new locale codes and add/change which locales are right to left languages. This is configured via , update these two properties files located in the frevvo.war file in <frevvo-home>/tomcat/webapps/frevvo.war. You nned to unpack the frevvo.war file. Make your changes to these two files in WEB-INF/data/users folder.:

•  locale.directions - add/remove locale codes to this file that need to be displayed in rtl format
•  locales.properties - add/remove locale codes here from the Choose Locale dropdown

Use Mode Strings

...

Runtime Strings

• Unpack the frevvo.war file

...

• Make a copy of  WEB-INF/data/locales/default to a locale name of your choice. Ex: WEB-INF/data/locales/default/spa
• Make your changes to WEB-INF/data/locales/

...

• spa
• Then repack the war file and place the new war file in the <frevvo-home>/tomcat/webapps directory. 

...

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.The form designer strings cannot currently be localized. This may be possible in a future version of Live Forms In-house.

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.