Supporting a new language

To support a new language to HCL WebSphere Portal you add resource bundles and, where applicable, JSPs for the new language. Some JSPs use resource bundles; others, such as help JSPs, are translated directly. Then you update the list of available languages by adding the new language to the portal. We do this using the XML configuration interface. Use the example XML script CreateLanguage.xml to add the new language for the portal. We can also use it to remove an existing language from the portal. The new language is then listed in the language selection menu boxes available in administration portlets, or for example, in Edit My Profile, Preferred language.

Note: The new language will be available only to portlets that you add to the portal, if these portlets support the newly added language and if you make the required language files available. None of the HCL WebSphere Portal user interface or messages will be translated to the new language.

• • Add resource bundles for a new language To allow the portal users to work in an extra language, add resource bundles for that language. Resource bundles are used to store text that is displayed in JSPs or text used in Java code.
  • Add a new language to render localized content We can add new languages to the portlet to render localized content in different languages and reach a larger audience.
  • Add JSPs for a new language For the new language in the portal, you also need to add JSPs. Some JSPs that contain mostly text, such as help JSPs, are translated directly which means that the text is contained in the JSP and not in a resource bundle. For JSPs that do not use resource bundles, we need to copy and translate an existing JSP and store it in the appropriate location.
  • Globalization for People Finder fields All fields of the People Finder portlet must have associated language strings defined in each language property file, PeopleFinderUI_language_code.properties. The field names are the names of the corresponding attributes in Member Manager.
  • XML samples for creating or removing language definitions We can modify these XML samples and use them to create or remove language definitions from the portal.

• Add resource bundles for a new language To allow the portal users to work in an extra language, add resource bundles for that language. Resource bundles are used to store text that is displayed in JSPs or text used in Java code.
• Add a new language to render localized content We can add new languages to the portlet to render localized content in different languages and reach a larger audience.
• Add JSPs for a new language For the new language in the portal, you also need to add JSPs. Some JSPs that contain mostly text, such as help JSPs, are translated directly which means that the text is contained in the JSP and not in a resource bundle. For JSPs that do not use resource bundles, we need to copy and translate an existing JSP and store it in the appropriate location.
• Globalization for People Finder fields All fields of the People Finder portlet must have associated language strings defined in each language property file, PeopleFinderUI_language_code.properties. The field names are the names of the corresponding attributes in Member Manager.
• XML samples for creating or removing language definitions We can modify these XML samples and use them to create or remove language definitions from the portal.

• Add resource bundles for a new language To allow the portal users to work in an extra language, add resource bundles for that language. Resource bundles are used to store text that is displayed in JSPs or text used in Java code.
• Add a new language to render localized content We can add new languages to the portlet to render localized content in different languages and reach a larger audience.
• Add JSPs for a new language For the new language in the portal, you also need to add JSPs. Some JSPs that contain mostly text, such as help JSPs, are translated directly which means that the text is contained in the JSP and not in a resource bundle. For JSPs that do not use resource bundles, we need to copy and translate an existing JSP and store it in the appropriate location.
• Globalization for People Finder fields All fields of the People Finder portlet must have associated language strings defined in each language property file, PeopleFinderUI_language_code.properties. The field names are the names of the corresponding attributes in Member Manager.
• XML samples for creating or removing language definitions We can modify these XML samples and use them to create or remove language definitions from the portal.