You can control the multiple language-specific settings within the portal.
Changing the default portal language
After the installation you can change the default language of the portal. To do this, use the Global Settings
portlet. Select Administration, Portal settings, Global Settings. From the pull down list, select the desired default language for the portal. This can be, for example, en
for English. Refer to Language support
for a list of the languages supported by the portal.
The Global Settings portlet does not work in portal cluster configurations. For portal clusters set the portal default language in the portal Localizer service by using the administrative console. For details about how to set the language refer to the topic about Setting service configuration properties.
For details about the language settings refer to the Localizer Service
For details on how to add a new language or to remove support for a language refer to Supporting a new language
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 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 encoded in the URL 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 session.
- If no language is encoded in the URL, 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, 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.
The sequence listed above 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). The language is determined as follows:
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 above, then the object ID of the page is displayed in the navigation rather than its title. Such an object ID can be, for example, 7_0_5T
Installing IBM WebSphere® Portal or Web Content Management fixes may reset the language fallback filter setting. This changes the way by which the server determines the language for rendering portlets. After installing a WebSphere Portal or Web Content Management fix, you must reset the language fallback filter in the web.xml
file to use the SortingLocaleFilter
In order for Lotus Quickr to work properly, make sure you reset the language fallback filter in both of these locations:
To reset the language fallback servlet filter to the default Lotus Quickr setting, replace the extended
locale filter with the sorting
locale filter as follows:
Restart your portal for the change to take effect. For more information about the language fallback filter, see Setting the language fallback filter
Parent topic: Language support: qp85
Dynamically changing the language during the session: qp85
Installing fix packs: qp85
Supporting a new language: qp85
Changing the character set for a language: qp85