This chapter describes how you can internationalize and localize your portal, and includes the following sections:
Each object can have an alternate name and description for each language that is supported in the portal. When you create an object (for example, a portlet) in the portal, you supply a primary name and description for the object, which displays to users, regardless of their locale choice. However, to accommodate users whose portal interface displays in a different language, you can also supply localized names and descriptions.
For example, if you have an object called "Engineering," then you might have the French translation, "Ingénierie," as the alternate name for that object. So when users log in using the French user interface, they see the object names and descriptions associated with French.
Although you can supply the localized terms on an object-by-object basis through the object editor, you might find it more efficient to edit all objects at the same time through the Localization Manager.
The Localization Manager allows you to download an .xml file that includes the names and descriptions for all objects that support localized names. Configure each object to allow localization before downloading the .xml file. You can then edit the list and upload it back into the portal.
To enable the object to be localized:
To localize objects using the Localization Manager:
<target language="fr">Tous</target>
For instructions and a detailed description of any page in the portal, click Help.
Each localized object has an entry in the following format:
<segment classid="2" itemid="51" stringid="0">
<source language="en">Everyone</source>
<target language="de" />
<target language="en" />
<target language="es" />
<target language="fr" />
<target language="it" />
<target language="ja" />
<target language="ko" />
<target language="pt" />
<target language="zh" />
</segment>
The first line displays information about the object entry:
The second line displays the primary language term (in this example, the primary language is English and the term is Everyone).
The remaining lines display the available languages:
To specify a name and description, language, localized names and descriptions, and properties of this object in the Properties and Names page of the object editor (for instructions on navigating to this editor, see Enabling Object Localization), do the following:
The primary language sets the default language, so users whose locale settings are outside of the supported languages will see the name and description in the primary language you have selected.
Note: If this object has already been localized into all supported languages, you cannot add more localized names and descriptions. (The new Localized Name button is not displayed.)
Unicode characters are used to store and retrieve text, and the system has access to linguistic rules for multiple languages during full-text indexing. This makes it possible to have documents of different languages within the same search collection, with significantly improved results.
The portal provides support for 61 languages. Of these, the following languages include support for word stemming and compound decomposition. This additional information is used to enhance results of the full-text index.
The following languages are supported at a reduced level.
All content in the search collection is stored as Unicode characters. The user interface handles text using the UTF-8 encoding, so search results are always displayed correctly, assuming that the appropriate fonts are available to the Web browser.
For information on searching international documents, see Search Language.
Web and file content crawlers are associated with a specific language. All documents processed by a content crawler are indexed using the linguistic rules appropriate for the specified language. For optimal results, create a separate content crawler to handle documents of different languages. For most European languages, mixing languages within a single crawl will not render the content unsearchable; however, word stemming and decomposition information stored in the documents will be missing for languages other than the content crawler's designated language. Avoid indexing Asian language documents with a content crawler configured for a European language, as special tokenization rules are required for processing the Asian languages.
When you use the Submit Document utility to add documents to the Knowledge Directory, you specify the document language by choosing from a pop-up list of the supported languages. As with content crawlers, this language should be set to the actual language of the document for optimal results. Correct specification of language is particularly crucial for proper indexing of Asian language content.