Page Comparison

...

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

...

• Some browsers have problems with apostrophe characters. Internet Explorer 8 is one such browser. To ensure that your translations are ok on all browsers 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 IE8If this does not work in your browser:
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 Check the 'Save Value' property for Message controls that you will want to translate.
• 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 Itinerary 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.

• Translate the string "You can't leave this empty" to Buttons in the  UI, such as "Set" in the Visual Rule Builder or "Log In" in the Form/Flow Properties Document Action tab, may not resize to fit translated text that has more characters than original text. In this scenario, consider using a different label or abbreviating to ensure text fits neatly.
  
  

• Translate the string "You can't leave this empty" to show an error message if data is not entered into a required field. See the Error Message property for more information.

...

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. 

Error message strings that the designer adds to a form using the error message property are translated using these uploaded translation files. The translation of  built-in error messages is done in the translation file located in the <frevvo-home>/tomcat/webapps/frevvo directory. war.  

...

will recognize the browser locale and alter displays and input formats as well as language according to the user's browser setting. Refer to browser Locale Handling for the details. You can override the browser's locale setting via the form's locale URL parameter which is typically only done for testing your translations. For example to render the form in Spanish rather than the default browser locale, 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 do not set the locale parameter and thus use the browser's default locale setting.

...

 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 the  server
2. Uncompress/expand the frevvo.war file. This is typically located here: Open the directory <frevvo-home>/tomcat/webapps/frevvo.war .
3. Copy the /WEB-INF/data directory to a temporary location.
4. Modify the files in /WEB-INF/data as described in the topics Adding Locales, Runtime Strings and Design-Time Strings below. These files contain all of the strings that have been externalized as well as the list of supported locales and directions.
5. Re-WAR to create a new updated frevvo.war file.
6. Replace the original frevvo.war file with the updated one, typically located here: <frevvo-home>/tomcat/webapps/frevvo.warReplace the /WEB-INF/data directory with your modified version.
7. Re-start your  server.

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 /Web-INF/data/users directory in the frevvo.war file. /data/users directory in the <frevvo-home>/tomcat/webapps/frevvo directory

•  /WEB-INF/data/users/locale.directions - add/remove locale codes to this file that need to be displayed in rtl format
•  /WEB-INF/data/users/locales.properties - add/remove locale codes here from the Choose Locale dropdown - when adding locales ensure that strings are unique and conform to ISO 639-2 (three character code) standards

Refer to the steps above under Server Customization for the instructions to unzipreplace the /rezip the <frevvoWEB-home>/tomcat/webapps/frevvo.war .INF/data directory.

Creating Runtime and Design-Time Translations

Runtime strings such as those found when a user logs in to access their task list, the login page, access denied messages, etc and Design-time strings such as those found in the palette controls, wizards, built-in error messages etc. are localized in the default file in the WEB-INF/data/locale directory.

Follow these steps:

1. Refer to steps 1 and 2 above under Server Customization to unzip frevvo.war, then...
2. Find the file named "default" located in /WEB-INF/data/locales. This file contains all of the runtime and designer strings that have been externalized. Notice there are partially completed Chinese and German sample translation files provided in this directory as well.

3. Copy the file "default" to a new file named using the ISO 639-2 three character or the the ISO 639-1 two character language codes .For example, the German translation file can be called ger or de, for English you can use eng or en. The Portuguese translation file can be named por or pt and the Chinese translation file an be chi or zh.  
   

   Tip

   Translation files can also be named to specify a country code. In this case you must name the file using this format: <language code>_<country code>. For Example, let's say the Firefox browser is set for de-at (German/Austria). The translation file in the Web_INF/data/locales directory MUST be named de_AT. The de represents the german language, followed by the underscore followed by a capitol AT which is the country code for Austria. These file names are case sensitive.

4. There are several files for specific areas of the application. The names of these files indicate the area for which the file contains externalized text strings:

   • form-designer-properties

   • flow-designer-properties

   • flow-designer-step-properties

   • rule-builder

   • frevvo-ui (currently covers the template install dialog)

5.  PrePre-pended  the locale onto the file. For example for french, "form-designer-properties" becomes "fr-form-designer-properties". All 6 files are required for each locale in order for this to work properly. For example for french (fr), you must place the following files into WEB-INF/data/locales, even if not all of them are translated:

   • fr

   • fr-form-designer-properties

   • fr-flow-designer-properties

   • fr-flow-designer-step-properties

   • fr-rule-builder

   • fr-frevvo-ui

6. Edit the new language file and add your translations.
7. Refer back to steps 4 - 6 under Server Customization for the instructions to complete.

Here is a section of the chi (Chinese) translation file with translations for the palette controls in the designer. This file is included in the frevvo directory.war.  

# Default strings in the frevvo UI
# Form designer
Text=他饿小他
TextArea=他饿小他啊人饿啊
Date=的啊他饿
Time=他没饿
Date/Time=的啊他饿／他没饿
EMail=饿没啊一了
Money=没哦年饿有
Phone=批和哦年饿
Quantity=去哦哦年他哦他有
Number=年哦没不饿人
BooleanCheckbox=他／发
Image=哦没啊个饿
Video=我哦的饿哦
Submit=是哦不没哦他
Cancel=才啊年才饿了
Dropdown=的人哦批的哦我年
Radio=人啊的哦批
Checkbox=才和饿才可不哦小
Section=是饿才他哦哦年
Repeat=人饿批饿啊他
Tabs=他啊不是
Tab=他啊不
Panel=批啊年饿了
Table=他啊不了饿
Col=才哦了
Message=没饿是是啊个饿
Link=了哦年可
Trigger=他人哦个个饿人
Upload=哦批了哦啊的

Setting the Firefox browser language to Chinese displays the designer palette controls as shown:

  Image Added

...

http://localhost:8082/frevvo/web/tn/nancy.com/subject/designer/tasks?submissionState=PENDING?embed=&locale=spa

...

Date and time type controls are locale parsing and formatting aware. When Automatic format is selected, both date and time entry and display formatting  will be locale specific.The designer has the option to force a particular date or time format upon the users that is independent of the locale by using the date format and time format properties. but this is not recommended.

...

The automatic locale specific formatting and parsing for date, time and date/time controls can be configured by manually adding the following properties in the locale properties file:

For example, let's say you want to change the MM.DD.YYYY to display as "Day of the week, Month Day ,year" in the German locale. Simply add the following to the ger locale file located in the WEB-INF/data/locale directory after expanding the frevvo.war as explained above:

frevvo.date.format="EEE, MMM d, ''yy"

After rezipping and replacing the frevvo.war /WEB-INF/data directory file with the updated one, the date will display as shown in the Firefox browser set for the German locale:

...

Date Picker

The Date picker will be automatically translated according to the browser locale. You can override the browser setting by adding the properties shown below to the locale file. This localization only applies to the date picker on the desktop as the native date picker will be shown on mobile devices. You can translate  (locale-specific) month names and abbreviated day of week names (two character).  The days of the week will always be shown as Sunday through Saturday, left to right on the date picker.  Only the Gregorian calendar system is supported.

To localize the date picker on the desktop, manually add the following properties in the appropriate locale properties file in the WEB-INF/data/locale directory after expanding the frevvo.war as explained above.

For example, Let's say you add the properties below to a Chinese translation file named zh:

frevvo.date.month.1=JaC
frevvo.date.month.2=FeC
frevvo.date.month.3=MaC
frevvo.date.month.4=ApC
frevvo.date.weekday.1=Mc
frevvo.date.weekday.2=Tc
frevvo.date.weekday.3=Wc
frevvo.date.weekday.4=Tc  

After rezipping and replacing the modified frevvo.war modified /WEB-INF/data directory file, restarting  and setting the Firefox browser to Chinese - zh, the date picker will display as shown in the image:

...