Here is an example locale properties translation file. This forms contains several controls labeled in English. Also you will always see the labels for the submit button and the save, load, and print icons. These can be localized too. In this example only the field labels were translated.
# Default strings for formtype: Travel Request Form # Note that spaces in keys must be properly escaped with a '\' # Generated on: Wed Jul 15 21:49:45 EDT 2009 Buiness\ Purpose=Negocio Propósito Car\ class=Coche Clase Departure\ Date=Salida Fecha Departure\ Time=Salida Tiempo EMail\ Address=Correo Electrónico Submit= load= print= save=
You will see a line for every control label in your form, message control text, hint, help, etc... in the format:
Add translations for each each text string:
<Text String>=<Text String in Spanish>
First\ Name=Primero Nombre
Notice that the strings on the left hand side of the '=' have spaces escaped with the '\' character. This is needed so do not remove that. The escape character is not needed on the right hand side of the '='. The example above correctly has "First\ Name" on the left and "JPrimero Nombre" on the right.
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 Electronic Signatures.
Save\ failed.\ Status= Save\ successful= Save\ this\ form= Saving= Section\ A= Sign\ this\ section= load= save=
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
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.
Upload your translation file.
The string locale=spa in the name is the Url parameter that you need to append to the form's Share Url to make the form appear in Spanish rather than the default. The test button and the share button here 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. If a locale Url parameter is not specified it defaults to the default locale.
Translations use UTF-8 encoding by default but you may also upload ISO-8859-1 (Unicode) strings. If you are using Unicode, check the ISO checkbox above the upload button.
To update an existing locale translation, edit the downloaded .properties file and re-upload it choosing the same locale name from the Choose Locale dropdown. This will replace the existing translation with the new translation.
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.
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:
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.
Refer to the steps above under Server Customization.
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.
The default runtime strings will not be updated simply by editing the file named "default". You must make a copy as described above, customize the 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:
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 ' UI. ie. if you append &locale=spa to the task list as an experiment shown above you will notice that ' 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.
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.
The default runtime strings will not be updated simply by editing the file named "default". You must make a copy as described above, customize the strings in the copy and then append &locale=<name of copy> to your edit mode Url.
Test that your translation shows up as expected by:
In-house server localization is only for OEM embedding. ie. you use this on the form designer embedded in your own web site. This is not for use in the ' UI.
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.
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.