Jump to: navigation, search

Localization

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

Usage

'knowledgecenter' namespace should be re-used when defining localization strings for Search 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": {
		"knowledgecenter": {
			"SidebarButton": "Search",
			"SearchButton": "Search",
			"Title": "Ask a Question",
			"Ask": "Ask",
			"Close": "Close",
			"Categories": "Categories",
			"NoResults": "No Results",
			"NoResultsTextUnder": "We're sorry but we could not find a suitable answer for you.",
			"NoResultsTextRephrase": "Could you please try rephrasing the question?",
			"WasThisHelpful": "Was this helpful?",
			"Yes": "Yes",
			"No": "No",
			"ArticleHelpfulnessYes": "Article Helpfulness - 'Yes'",
			"ArticleHelpfulnessYesDesc": "Great! We're very pleased to hear that the article assisted you in your search. Have a great day!",
			"ArticleHelpfulnessNo": "Article Helpfulness - 'No'",
			"ArticleHelpfulnessNoDesc": "We're sorry that the article wasn't a good match for your search. We thank you for your feedback!",
			"TypeYourQuestion": "Type your question",
			"Back": "Back",
			"More": "More",
			"Error": "Error!",
			"GKCIsUnavailable": "Knowledge Center Server is currently not available"
		}
	}
}

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on March 7, 2018, at 11:39.