Reference - International Culture Support

TSL Ping Tree > Reference

Reference - International Culture Support

TSL Ping Tree can be used to accurately process leads in all cultures that use the Gregorian calendar, e.g.
  • en-US    English (United States)
  • en-CA    English (Canada)
  • en-GB    English (United Kingdom)
  • fr-CA      French (Canada)
  • fr-FR      French (France)
  • de-DE    German (Germany)
  • es-MX    Spanish (Mexico)
  • es-ES    Spanish (Spain)
  • es-US    Spanish (United States)
The list of presently supported cultures can be found on the Form configuration page; if you need to support a culture for one of your offers and it is not available on the Form page then please let us know.

The culture that you specify for a given Form allows the system to properly translate all raw posted posted String values into correct strongly typed DateTime, Decimal, and Integer values.  For example. when the culture specified is "en-GB" then "4/8/1960" maps to the date August 4, 1960 and not April 8, 1960.

Error messages can also be customized via Field Validations and Filters that use LeftHand/RightHand rules.  This covers all except for high level system errors (such as not supplying a ping tree and promotion ID on a post) as well as data type casting errors (for example trying to cast the string "30-30-2012" into a DateTime); the errors produced for these situations are all in English (US).

The user interface of the product, the Portal, is written in English (US) and our email and phone support is only provided in English.  Your visitors/leads never see our system so this only affects you and your other authorized users.  We have plans to present configuration pages in other cultures but today everything is English (US).  So, if you are one of our UK or Australian customers, for example, you will see that calendar controls are presently in the English (US) culture. Likewise, when a textbox is available to enter a number or a date we use the English (US/GB) encoding.  For numbers the Thousands separator is a comma and the radix or decimal point is a period, e.g. "12.75" for Twelve and 75/100ths.  For dates month comes before year, e.g. "4/8/1960" maps to the date April 8, 1960.

All reports including posting specifications are also generated in the English (US) culture and language.  Since you may distribute posting specifications to your affiliates please take care to review and edit before distributing.

Another area of the system where language and culture apply is with our Modifiers.  All Modifier numeric and date/time literal arguments are expressed in the "en-US" or English (US) culture.  So please take care when expressing Numeric and DateTime constants.  For example, "12.75" equals Twelve and 75/100ths and "7/4/2012" equals July 4, 2012.  We recommend that you use the ISO 8601 date format, yyyy-MM-ddTHH:mm:ssZ, or the abbreviated "yyyy-MM-dd" format (e.g. 2012-07-04") when expressing dates to avoid any ambiguity since this date format is honored the same way for all of the cultures that we presently support.  Token Substitutions also use "en-US" or English (US) as the default culture when turning a DateTime or Numeric value into a String, however, the Format modifier allows you to override the culture to get the desired result.

Finally, anywhere in the system that our Expression Builder control appears you may specify a string with optionally embedded ${} styled tokens which are evaluated at run-time.  For example, the Expression Builder is used with Interface parameter mapping and with the LeftHand/RightHand rules that are available in Field Validations and Filters.  Again, the default culture used whenever there is a need to implicitly cast a resulting String value into a DateTime, Decimal, or Integer is "en-US".  For example, LeftHand/RightHand rule "${'Monthly Net Income'} Greater Than "3.500,50" will not work if you are used to working in Spanish.  You will have to express the rules as "${'Monthly Net Income'} Greater Than "3,500.50" or as "${'Monthly Net Income'} Greater Than "3500.50" (no thousands separator) in order for it to work.