...
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- Choose the locale from the dropdown. In this example we choose Spanish. Note the list of available locales is configured by your Live Forms your system administrator (Live Forms In-house only).
- Browse to your translation file - TravelRequestForm_spanish.properties on disk
- Click the upload button. You will see the new locale appear in the list above. In this case named Spanish::locale=spa
- Click the application icon to test the form with your translation to this new locale
...
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 Customization
Live Forms In In-house supports the ability to customize 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:
...
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 Formsin ' s UI. ie. if you append &locale=spa to the task list as an experiment shown above you will notice that Live Forms 's surrounding 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.
...