Selecting and changing the language
You can control the multiple language-specific settings within the portal.
Changing the default portal language
Portlets
A portlet can support one or more locales. All portlets must have their own default language specified in the deployment descriptor. Otherwise the portlet cannot be installed.
Changing titles for pages
You can edit titles for pages in the portlet for Managing Pages using the configure option for the locale specific settings. Select Administration, Portal User Interface, Manage pages. Click the Edit Page Properties icon, expand the Advanced options, and select the option for setting page titles and descriptions. You can enter a different title for each available language.
Language selection by the user
Language determined by the portal
The portal determines the language for rendering the portal content by a search process along the following sequence at login time:
- The language that is encoded in the URL by the value for the locale parameter takes highest priority. The portal does not encode a locale into the URL by default. However, you can add code to the JSPs to support dynamic language selection. For details about this refer to Dynamically changing the language during the user session.
- The language that is encoded in the navigational state by the locale tag: <locale> . . . </locale>.
- The language that is stored in the com.ibm.wps.state.preprocessors.locale.CookieSupportedLanguagePreProcessor in the portal State Manager Service. For more information, read State Manager Service.
- If the user has logged in, the portal displays in the preferred language selected and stored in the user repository by the user.
- If no preferred user language can be found, the portal looks for the language defined in the user's browser. If the portal supports that language, it displays the content in that language. If the browser has more than one language defined, the portal uses the first language in the list to display the content.
- If no browser language can be found, for example if the browser used does not send a language or if the portal does not support the language set in the browser, the portal resorts to its own default language.
- If the user has a portlet that does not support the language that was determined by the previous steps, that portlet is shown in its own default language.
This sequence describes the language selection process that is applied for each user at logon time. For pages viewed by anonymous users only the last three steps for determining the language apply. This applies, for example, before login and after log off.
The language determined by this selection process is applied to the complete portal. If the portal or one component does not find the appropriate resources for the language as selected by this sequence, it tries to find the resources in a similar language. For example, if the determined language was US English (en_US), the next closest option is English (en).
This search sequence applies to all portal components individually down to portlets. For example, if a portlet does not support the language selected by the portal, it is shown in default language of the portlet. This way, the portal can show individual portlets in different languages.
If a page does not support any of the languages determined by the steps given in the preceding list, then the navigation displays the object ID of the page rather than the page title. Such an object ID can be, for example, 7_0_5T .