D Localizing Your Portal

This chapter describes how you can internationalize and localize your portal.

It includes the following sections:

Localizing Object Names and Descriptions
Localization Manager XML
About the Locale Map
About Search Service Internationalization Support

Localizing Object Names and Descriptions

You can localize object names and descriptions, so that users see the names and descriptions in their chosen language. For example, if you have an object called “Engineering,” you could add “Ingénierie” as the localized entry for French. A user viewing the French user interface would see the Ingénierie as the object name, as well as any other names and descriptions localized into French.

There are two ways to localize object names and descriptions: in the object's editor or using the Localization Manager.

To localize the name and description for a single object, use the object's editor.

See Localizing the Name and Description for an Object.
To localize all object names and descriptions, use the Localization Manager.

See Localizing All Object Names and Descriptions.

Localizing the Name and Description for an Object

Note:

You can localize names and descriptions into only the languages supported by the portal.
You cannot localize names and descriptions for users.
You can localize the names and descriptions for all objects at the same time using the Localization Manager.

Open the object's editor by creating a new object or editing an existing object.
Select Supports Localized Names.

The Localized Names and Descriptions section appears.
Add or edit the localized names and descriptions:
- To add an entry for a language, click New Localized Name, then, in the Name and Description dialog box, enter the localized name and/or description, select the appropriate language, and click Finish.
- To edit an existing entry, click the entry you want to change, then, in the Name and Description dialog box, edit the entry as necessary, and click Finish.
- To remove existing entries, select the entries you want to remove and click the Remove icon.
  
  To select or clear all entries, select or clear the check box to the left of Name.

Localizing All Object Names and Descriptions

To access the Localization Manager you must be a member of the Administrators Group.

Although you can supply localized names and descriptions 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 enables you to download an .xml file that includes the names and descriptions for all objects that support localized names. You can then edit the .xml file and upload it back into the portal.

Note:

You must configure each object to allow localization before downloading the .xml file.
You can localize names and descriptions into only the languages supported by the portal.
You cannot localize names and descriptions for users.
You can localize each object individually using the object's editor.

Click Administration.
In the Select Utility list, click Localization Manager.
Export the names and descriptions for all portal objects that support localization by clicking Download, and saving the XML file to your computer.
Open the file with a text editor, add or edit localized values for the objects, and save your changes.

For example, to edit the French term for Everyone, you might
```
make the following change:
<target language="fr">Tous</target>
```
Return to the Localization Manager, and click Browse.
Navigate to the exported file and click Open.
Upload and apply your changes to the portal by clicking Upload.

Localization Manager XML

Each localized object is represented by an entry in the Localization Manager XML file.

<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 classid represents the object type (in this example, a group).
The itemid represents the object ID in the portal database.
The stringid is “0” for the object name and “1” for the object description.

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.

Value	Language
de	German
en	English
es	Spanish
fr	French
it	Italian
ja	Japanese
ko	Korean
nl	Dutch
pt	Portuguese
zh	Simplified Chinese
zh-tw	Traditional Chinese

About the Locale Map

A Locale Map allows you to create custom mappings for locales supported by Oracle WebCenter Interaction. For example, since Traditional Chinese is used in Hong Kong, you might want to map the Hong Kong locale to the Traditional Chinese locale so that if users select Hong Kong as their locale in the portal or their browser, the portal displays Traditional Chinese.

The Locale Map is stored in the i18n folder of the installation directory (for example, install_dir\10.3.3\i18n\LocaleMap.xml).

To create the mapping from the Hong Kong locale to the Traditional Chinese locale, you add the following mapping to the LocaleMap.xml file:

<Mapping>
  <from>zh-hk</from>
  <to>zh-tw</to>
</Mapping>

About Search Service Internationalization Support

The portal provides support for 61 languages. The portal uses Unicode characters 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 user interface handles text using the UTF-8 encoding, so search results are always displayed correctly, if the appropriate fonts are available to the Web browser.

Some languages supported by the portal include support for word stemming and compound decomposition. This additional information is used to enhance results of the full-text index. For a list of supported languages, including which have enhanced support, see Chapter D, "Localizing Your Portal."

Crawling International Document Repositories

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.

Submitting International Documents to the Knowledge Directory

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.