Jump to: navigation, search
(Created target blank page For Version: PSAAS:Julie)
 
(Automated save: adding PEC_Migrated template.)
 
Line 1: Line 1:
<!-- Creation of the target page -->
+
= Localization =
 +
 
 +
{{Template:PEC_Migrated}}
 +
 
 +
 
 +
 
 +
{{NoteFormat|For information on how to setup localization, please refer to the  [[GWCInternat|Localization Guide]]|1}}
 +
 
 +
==Usage==
 +
'calendar' namespace should be used when defining localization strings for Calendar plugin in your i18n JSON file.
 +
 
 +
In the example below, we demonstrate defining new strings for the 'en' (English) language. You may use any language codes you wish; there is no standard format. When selecting the active language in your configuration, you must match one of the language codes defined in your i18n JSON file. Please note that you must only define a language code once in your i18n JSON file. Inside each language object you should define new strings for each widget.
 +
 
 +
==Example i18n JSON==
 +
<source lang='javascript'>{
 +
"en": {
 +
"calendar": {
 +
"CalendarDayLabels": [
 +
"Sunday",
 +
"Monday",
 +
"Tuesday",
 +
"Wednesday",
 +
"Thursday",
 +
"Friday",
 +
"Saturday"
 +
],
 +
"CalendarMonthLabels": [
 +
"Jan",
 +
"Feb",
 +
"Mar",
 +
"Apr",
 +
"May",
 +
"Jun",
 +
"Jul",
 +
"Aug",
 +
"Sept",
 +
"Oct",
 +
"Nov",
 +
"Dec"
 +
],
 +
"CalendarLabelToday": "Today",
 +
"CalendarLabelTomorrow": "Tomorrow",
 +
"CalendarTitle": "Schedule a Call",
 +
"CalendarOkButtonText": "Okay",
 +
"CalendarError": "Unable to fetch availability details.",
 +
"CalendarClose": "Cancel"
 +
}
 +
}
 +
}</source>
 +
 
 +
[[Category:V:PSAAS:Julie]]

Latest revision as of 22:32, June 21, 2020

Localization

Important
This content may not be the latest Genesys Engage cloud content. To find the latest content, go to Genesys Engage cloud for Administrators.



Important
For information on how to setup localization, please refer to the Localization Guide

Usage

'calendar' namespace should be used when defining localization strings for Calendar plugin in your i18n JSON file.

In the example below, we demonstrate defining new strings for the 'en' (English) language. You may use any language codes you wish; there is no standard format. When selecting the active language in your configuration, you must match one of the language codes defined in your i18n JSON file. Please note that you must only define a language code once in your i18n JSON file. Inside each language object you should define new strings for each widget.

Example i18n JSON

{
	"en": {
		"calendar": {
			"CalendarDayLabels": [
				"Sunday",
				"Monday",
				"Tuesday",
				"Wednesday",
				"Thursday",
				"Friday",
				"Saturday"
			],
			"CalendarMonthLabels": [
				"Jan",
				"Feb",
				"Mar",
				"Apr",
				"May",
				"Jun",
				"Jul",
				"Aug",
				"Sept",
				"Oct",
				"Nov",
				"Dec"
			],
			"CalendarLabelToday": "Today",
			"CalendarLabelTomorrow": "Tomorrow",
			"CalendarTitle": "Schedule a Call",
			"CalendarOkButtonText": "Okay",
			"CalendarError": "Unable to fetch availability details.",
			"CalendarClose": "Cancel"
		}
	}
}
This page was last edited on June 21, 2020, at 22:32.
Comments or questions about this documentation? Contact us for support!