This background information about localization might be useful as you are implementing or troubleshooting an Oracle Content Management integration.

Some of the concepts described in this section go beyond the REST API.

Localization is performed according to the following steps:

1. Choose a language locale.

   1. If an HTTP request exists and has an X-Waggle-ForceLanguage header, then use the X-Waggle-ForceLanguage header value as the language locale and go to step 2.

   2. If a particular user is signed in or otherwise identified, check to see if the user has set a preferred language locale in their user profile. If set, use it and go to step 2.

      A language locale from LDAP will be copied to the user profile in Oracle Content Management. If the LDAP realm has sync-on-authentication enabled, then for each sign in, the LDAP values will overwrite the user profile settings. However, if the user changes the value in their Oracle Content Management profile, it is not written back to LDAP; Oracle Content Management does not write any attributes to LDAP.

      If the LDAP Preferred Language is not supported in Oracle Content Management (for example, ar), English is displayed regardless of the application default language setting.

   3. If an HTTP request exists and has an Accept-Language header, use the Accept-Language header to select the language locale.

      Using the Accept-Language header, perform a lookup as described in RFC-4647 section 3.4. This will result in a language locale being chosen based on an exact or partial match of the header, the available translation bundles, and the bundle of last resort.

   4. If the server has a language locale set, use it.

   5. Select the host machine default language locale.

2. Choose a translation bundle with the exact or longest possible partial match of the chosen language locale. If no exact or partial match exists, then choose the bundle for English.