loading table of contents...

Blueprint Developer Manual / Version 2310

Table Of Contents Locales Administration

Each site is bound to a specific locale (see Locale). In order to ensure a consistent usage of locale strings across multiple sites that might be managed in a single content repository, the entire list of available locales is maintained in a central content item of type CMSettings.

The content item /Settings/Options/Settings/LocaleSettings contains in the property Settings a String List property availableLocales which contains locale strings. Example 5.9, “XML of locale Struct” shows the XML structure of the Struct:

  <Struct xmlns=""
    <StringListProperty Name="availableLocales">

Example 5.9. XML of locale Struct

Please make sure, that the path to the LocaleSettings is configured in the Studio properties, as described in Section 9.22, “Available Locales” in Studio Developer Manual.

For providing a new locale, you can simply open the content item LocaleSettings and add a new entry to the list of locales. See Section 4.6.4, “Editing Struct Properties” in Studio User Manual for details on how to edit a struct property and add items to string lists. Figure 5.28, “Locales Administration in CoreMedia Studio” shows a Studio tab in which the LocalesSettings content item is being edited.

Sometimes you might want to define locales for a supranational region such as Africa or Latin America. In this case you can add the language code followed by the UN M.49 area code as described in For Spanish in Latin America and the Caribbean add, for example, "es-419".

Locales Administration in CoreMedia Studio

Figure 5.28. Locales Administration in CoreMedia Studio

Search Results

Table Of Contents

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.