Using Globalization in Applications
Requirements for Multi Language Support
Example: Set Culture in the Player
The Player provides, if Globalization is enabled in Candera, a checkbox to select all cultures, which are available as language packs in the loaded asset.

Candera Globalization API
The following table explains the usage of Globalization interfaces and how they are used in application code.
Access to cultures and changing of current culture
Singleton: Candera::Globalization::CultureManager::GetInstance()
Retrieve available cultures:
return CultureManager::GetInstance().GetCultureCount();
Get current culture:
Culture::SharedPointer culture = CultureManager::GetInstance().GetCurrentCulture();
Get culture name:
Culture::SharedPointer culture = CultureManager::GetInstance().GetCulture(index);
return culture->GetDisplayName();
Set new culture:
Culture::SharedPointer culture = CultureManager::GetInstance().GetCulture(index);
FEATSTD_LOG_INFO(" -> Select culture '%s'", culture->GetDisplayName());
rc = CultureManager::GetInstance().SetCurrentCulture(culture->GetLocale());
Base class for listeners to culture change events
Notification of CultureChangeEvents
Point of access to a text in currently active language
Non-translatable String
Translatable String
FeatStd::String text(FeatStd::TextId("textField_1_3"));Direct Text-Id: "#\<HEX_HASH_VALUE\>"
FeatStd::String text(0x13); // for accessing text referenced by a hex-value-id of 13