After Cloud Manager scans its theming configuration file to identify the themes it is to apply, it begins at the top of the theme hierarchy and searches for the presence of a localization layer or “locale” that matches system settings. Cloud Manager uses the following order as it searches for a locale and theme to apply to its components:
The locale of the User object (defined in LDAP).
The theme (defined in cloudmanager-themes.cfg, which points to /themes/<theme>) and the locale for the Organization object where the User object resides (see Section 23.3, The Theming Configuration File).
The theme and locale defined for the system being used for viewing.
The default theme (CloudManager) and the default locale (en).
If Cloud Manager does not find a locale or theme in its first search that it can apply to its components, it proceeds to the next search level, and so on. With this theming hierarchy in mind, you can localize the interface, the system email messages, the reports for users in one of your organizations, or the look and feel of the Cloud Manager Application Server Console.
The Cloud Manager theming algorithm searches for the most specific variant of a language it can find. For example, if you define an /en_gb, locale folder, Cloud Manager looks in that folder for any files it might need before defaulting to the sibling, “less-specific” locale, /en. This makes it possible to customize your message text or colors to avoid any graphics, colors, or phrases that might be offensive in one locale but acceptable in another.
Because of the fallback nature of the search order, you might only customize a few files in a specific variant of a language. Cloud Manager only uses what it can find, so if a specific file is not present, it defaults to the sibling, “less specific” locale. If the parent locale is not found, Cloud Manager falls back to the installed locale, /themes/CloudManager/en.