Internationalization

Purpose

The Internationalization page in the Admin Console allows you to configure the locales available to users, as well as the primary locale, time zone, and calendar that will be the default for all users in the environment.

Access

To access the Internationalization page, go to the Admin Console. Then, in the left navigation menu, under System, click Internationalization.

Map translation strings

The Map Translation Strings banner and button only appear in the Internationalization page if your environment includes record field values that are translation strings. When translation strings are generated from record field values, the translation strings are added to the translation set and Appian generates a system record type to hold the newly generated translation strings.

The system record type for the generated translation strings is automatically synced whenever the relevant translation set is updated, deleted, or edited by importing Excel files. If an error or issue occurs with automatic syncs, use the MAP button in the Map Translation Strings banner to manually map the translation strings to their corresponding values in the system record type.

Locale settings

The locale settings affect the language of Appian-generated text and the format of dates, times, and numbers. By default, it does not affect text that is configured by developers in design objects. To translate the text that is configured by developers in design objects, use a translation set.

The table below lists the locales that Appian supports.

Appian Supported Locales

Locale	Locale Code	Locale Support
		Appian Mobile/ Non-SAIL interfaces	Appian
Arabic	[ar]	No	Yes
Catalan	[ca]	Yes	Yes
Chinese (Simplified)	[zh_CN]	Yes	Yes
Chinese (Traditional)	[zh_HK]	Yes	Yes
Czech	[cs]	Yes	Yes
Danish	[da]	Yes	Yes
Dutch (Belgium)	[nl_BE]	Yes	Yes
Dutch (Netherlands)	[nl]	Yes	Yes
English (Australia)	[en_AU]	Yes	Yes
English (Canada)	[en_CA]	Yes	Yes
English (New Zealand)	[en_NZ]	Yes	Yes
English (South Africa)	[en_ZA]	Yes	Yes
English (United Kingdom)	[en_GB]	Yes	Yes
English (United States)	[en_US]	Yes	Yes
French (Belgium)	[fr_BE]	Yes	Yes
French (Canada)	[fr_CA]	Yes	Yes
French (France)	[fr_FR]	Yes	Yes
French (Switzerland)	[fr_CH]	Yes	Yes
German (Austria)	[de_AT]	Yes	Yes
German (Germany)	[de]	Yes	Yes
German (Switzerland)	[de_CH]	Yes	Yes
Greek (Greece)	[el]	Yes	Yes
Hebrew	[iw]	No	Yes
Hindi	[hi]	Yes	Yes
Hungarian	[hu]	Yes	Yes
Indonesian	[id]	Yes	Yes
Italian (Italy)	[it]	Yes	Yes
Japanese (Japan)	[ja]	Yes	Yes
Korean (South Korea)	[ko]	Yes	Yes
Polish (Poland)	[pl]	Yes	Yes
Portuguese (Brazil)	[pt]	Yes	Yes
Portuguese (Portugal)	[pt_PT]	Yes	Yes
Romanian	[ro]	Yes	Yes
Russian (Russia)	[ru]	Yes	Yes
Slovak	[sk]	Yes	Yes
Slovenian	[sl]	Yes	Yes
Spanish (Mexico)	[es_MX]	Yes	Yes
Spanish (Spain)	[Es_es]	Yes	Yes
Swedish (Sweden)	[sv]	Yes	Yes
Thai	[th]	Yes	Yes
Turkish	[tr]	Yes	Yes
Ukrainian	[uk]	Yes	Yes
Vietnamese	[vi]	Yes	Yes
Welsh	[cy]	Yes	Yes

Enabled locales

The enabled locales are the locales available for users to select as their user locale.

The user locale affects:

• The language of Appian-generated text, like the text in Appian Designer and the Admin Console.
• The format of dates, times, and numbers.

If you use a translation set to translate your applications, the user locale can also affect the interface text that displays to end users. For example, you can use translation sets to translate instructions, labels, and tooltips in your interface. If you've provided translations in the user locale of your end users, they will see the translated interface text in their user locale.

To enable a locale, select it from the Enabled Locales dropdown, then click SAVE CHANGES.

When enabling locale settings, consider:

• Appian must have at least one locale enabled. If no locales are selected, you must enable at least one locale before you can save your changes.
• For Appian Mobile applications, start and task forms appear in the locale preference set in Appian, News feed entries appear in the locale they were entered, and the remaining aspects of the mobile application, such as button names and titles, are determined by the device's language setting. The device's language setting does not need to be enabled as a locale in Appian to translate the button names correctly.
• The Process Modeler is translated to the developer's preferred locale, except for the following areas: the node and smart service palette, the font palette, and some validation messages.
• When locale is set to Arabic, the interface displays from right-to-left rather than left-to-right and default alignment for interface components and grid columns is right rather than left.
• Non-SAIL interfaces used in (Application Portal [Deprecated]) support all languages except Arabic and Hebrew.

Disabling locales

To disable a locale, remove the check from the corresponding entry in the Enabled Locales dropdown list.

If a user's preferred locale is set to a locale you have disabled, the primary system locale for the environment displays to the user instead. Users then can select a new preferred locale from one of the remaining locales that are enabled for your environment at any time.

Selecting a primary locale

To specify a default locale for your environment to use for all users that have not selected their own preferred locale, select a locale from the Primary Locale dropdown list. Only enabled locales are listed here.

Forcing system-wide locale settings

To force all users in the environment to use the primary locale regardless of user preferences, select the Always override users' selected locale checkbox.

Date and time settings

The preferred locale setting governs the format of dates and numbers that are displayed by the system. For example, if the preferred locale is set to English (US) [en_US], the date is displayed with the month preceding the day. The same date, when the preferred locale is set to Spanish [es], is displayed with the day preceding the month.

Display formats used by default locales

The following table lists the date and time formats used when a certain default locale is selected (or is the only enabled locale).

Preferred Locale	Date and Time Format	Example
US English (en_US)	Month Day, Year Hour:Minute AM/PM	Dec 15, 2010 3:32 PM
UK English (en_GB)	Day Month Year Hour:Minute	15 Dec 2010 15:32
French (ca_FR)	Year-Month-Day Hour:Minute	2010-12-15 15:32
Spanish (es_MX)	Day/Month/Year Hour:Minute	15/12/2010 15:32

Hours displayed in US English use a 12-hour clock with an AM or PM designation.

Number formats

The separators between digits in a number change based on the preferred locale. For example, if the preferred locale is English (US) [en_US], a comma (,) is used as a separator (1,000). If, however, the preferred locale is set to German [de]), a full stop (.) is used as the separator (1.000).

Calendar settings

According to the US Naval Observatory, the Gregorian calendar is the internationally accepted civil calendar. This is the default calendar used in Appian.

Selecting a primary calendar

To change the default Gregorian calendar to a different calendar, select a calendar from the Primary Calendar dropdown list. Options include the calendars listed below.

Islamic calendars

You can select from three Islamic calendars, which use slightly different leap year patterns and different means for calculation.

Type	Leap Years	Description
1	2 5 7 10 13 16 18 21 24 26 29	Kūshyār ibn Labbān (11th cent. CE) Ulugh Beg (15th cent. CE) Similar to the "Kuwaiti algorithm"
2	2 5 7 10 13 15 18 21 24 26 29	Most Commonly Used
Um Al Qura Calendar تقويم أم القرى	Not applicable	Based on observation or astronomical calculation.

The leap year patterns are based on the following logic:

• There are 11 leap years in a 30-year cycle. Noting that the average year has 354 11/30 days and a common year has 354 days, at the end of the first year, the remainder is 11/30ths of a day.

The difference between calendar type 1 and type 2 centers on when the leap day is added.

• With calendar type 1, whenever the remainder is at least half a day (15/30ths of a day) a leap day is added to that year, reducing the remainder by one day.
• With calendar type 2, when the remainder exceeds 15/30ths of a day, a leap day is added.

The difference between the Type 1 and Type 2 leap-year schemes are shown in the following table, which lists the remainder for each year in the 30-year cycle.

Year	Type 1 remainder	Type 2 remainder	Year	Type 1 remainder	Type 2 remainder	Year	Type 1 remainder	Type 2 remainder
1	11/30	11/30	11	1/30	1/30	21	7/10 *	7/10 *
2	22/30 *	22/30 *	12	2/5	2/5	22	1/15	1/15
3	1/10	1/10	13	23/30 *	23/30 *	23	13/30	13/30
4	7/15	7/15	14	2/15	2/15	24	4/5 *	4/5 *
5	5/6 *	5/6 *	15	1/2 *	1/2	25	1/6	1/6
6	1/5	1/5	16	-2/15	13/15 *	26	8/15 *	8/15 *
7	17/30 *	17/30 *	17	7/30	7/30	27	-1/10	-1/10
8	-1/15	-1/15	18	3/5 *	3/5 *	28	4/15	4/15
9	3/10	3/10	19	-1/30	-1/30	29	19/30 *	19/30 *
10	2/3 *	2/3 *	20	1/3	1/3	30	0	0

Islamic calendar epoch

The epoch defines the starting point of the Calendar (the first day of year one). The following epochs can be selected for Islamic Type 1 and 2 calendars.

Epoch	Day 1 / Year 1	Description
A	15/July/622 CE/Julian	Thursday or Astronomical Epoch
B	16/July/622 CE/Julian	Friday or Civil Epoch

Setting a system-wide calendar

To override all users' preferred calendar settings with the primary calendar, select the Always override users' selected calendar checkbox when selecting the primary calendar.

Selecting a primary time zone

Locale preferences and time zone preferences affect how dates and times may be displayed. For example, a process start time of Oct 12, 2011 at 5:00 pm Eastern is displayed differently for a user with Spanish locale and Central time zone preferences.

Process start time	User's Preferred Setting	User's Preferred Time Zone	Displayed start time
Oct 12, 2011 at 5:00 PM Eastern Daylight Time	Spanish - Mexico	Ciudad de México (México) (America/Mexico_City)	12/10/2011 at 4:00 PM GMT-05:00

As with locales, system administrators must also specify a primary time zone for the environment. At installation, the primary time zone is set to Greenwich Mean Time (GMT). To specify another primary time zone for the environment, select a time zone from the Primary Time Zone dropdown list. This recommended list is based on the selected locale. Self-managed customers can override the default list of recommended time zones or add a list for a new locale by modifying the Appian CR configuration file.

To override all users' preferred time zone settings with the primary time zone, select the Always override users' selected time zone checkbox.

When selecting a Continental US time zone, we recommend using the following settings.

• Eastern - America/New_York
• Central - America/Chicago
• Mountain - America/Denver
• Pacific - America/Los_Angeles

A process model can take a specific time zone, which is used by each process spawned from the model. Alternatively, models can be configured to use the time zone preference of the user who starts the process model. This is set in the process model's properties.

Feedback