...

You may find some strings in the default properties file that are not applicable to your form. Here are a few examples strings that are only applicable if you're using the save/load feature, workflows feature or digital signaturesDigital Electronic Signatures.

Save\ failed.\ Status=
Save\ successful=
Save\ this\ form=
Saving=
Section\ A=
Sign\ this\ section=
load=
save=

Translation Considerations

• Some browser have problems with apostrophe characters. Internet Explorer 8 is one such browser. To ensure that your

...

• translations are ok on all

...

• browsesr you should use the html escape character in place of the apostrophe.

...

• Refer to this additional information describing HTML Reserved Characters.

# Do NOT DO THIS on IE8
Initializing\ form=l'initialisation de la forme
# Instead use the html apostrophe escape sequence like this
Initializing\ form=l'initialisation de la forme 

• Messages formatted in HTML that contain new line characters in the text may not translate properly. For Example, the Text "Trip Itinerary <br/> Please Complete" in a message control to label the Trip Intinerary section of the Travel Request form will appear on the screen to have a new line in it. New Lines are ignored by HTML. Do not use new lines in forms that require localization.

• Use English alphabet characters only when naming controls. For example, controls named with ó as in Póliza may cause issues when the control is used in a business rule and with submission data.

• The  Preview function displays in the default locale. This is as designed. Go to the existing internationalize page to test the use mode form in the target locale/language. 
• Be careful when internationalizing markup. Do not assume that the string property name is valid markup. For Example: Let's say you had a field called FirstName in your form with this stying applied to the label: <span style="color:red;font-weight:bold;">FirstName</span>. The default strings properties file shows the property name as: <span\ style"color:red;font-weight:bold;">FirstName</span>. It is missing the '=' after style.  This is intentionally stripped out because otherwise if it was left in, the = would be interpreted as the end of the property name. Adding <span style="color:red;font-weight:bold;">Primero Nombre</span> to the right side of the "=" sign, in this case, will translate this label successfully. If you see the error message " Failed to generate PDF snapshot: Could not generate PDF" check the markup in your translation files.

Upload and Test

Upload your translation file.

...

1. 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).
2. Browse to your translation file - TravelRequestForm_spanish.properties on disk
3. Click the upload button. You will see the new locale appear in the list above. In this case named Spanish::locale=spa
4. 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:

1. Stop you Stop the  server
2. Uncompress/expand the frevvo.war file. This is typically located here: <frevvo-home>/tomcat/webapps/frevvo.war 
3. Find the file named you need to modify located in Modify the files in /WEB-INF/data /localesas described in the topics Adding Locales, Runtime Strings and Design-Time Strings below. These file contains all of the strings that have been externalized as well as the list of supported locales and directions.
4. Make the changes as described in the topics Adding Locales, Runtime Strings, Design-Time Strings below.
5. Re-WAR to create a new updated frevvo.war file.
6. Re-deploy the WAR Replace the original frevvo.war file with the new updated frevvo.war file, typically located here: <frevvo-home>/tomcat/webapps/frevvo.war
7. 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).
8. 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.
9. Ensure the test translations show up as expected.

Adding Locales

To add new locale codes to the Choose Locale dropdown and add/change which locales are right to left languages, update these two properties files located in the frevvo.war file.

...

1. Refer to the steps above under Server Customization, then...
2. Find the file named "default" located in /WEB-INF/data/locales. This file contains all of the strings that have been externalized
3. 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".
4. Selectively edit the target language file and put in test add your translations.
5. Copy the target Copy your new target language file to /WEB-INF/data/locales Ex: /WEB-INF/data/locales/spa
6. Refer back to final steps under Server Customization.

...

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.

...

1. Refer to the steps above under Server Customization, then...
2. Find the file named "default" located in /WEB-INF/data/locales. This file contains all of the strings that have been externalized
3. 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".
4. Selectively edit the target language file and put in add your translations.
5. Copy the target language file to your new target language file to /WEB-INF/data/locales Ex: /WEB-INF/data/locales/spa
6. Refer back to final steps under Server Customization.

Test that your translation shows up as expected by:

...

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. 

International Characters for Print View and Submission PDFs

You can add support for International characters for a form's Print view and submission PDFs using a custom theme. Refer to this documentation for the details.