This chapter provides an overview of localization options for an Oracle WebCenter deployment.
All Oracle WebCenter products are fully Unicode-compliant and use UTF-8 encoding.
For additional details on localization and Oracle WebCenter, see the Administrator Guide for Oracle WebCenter Interaction.
For developer documentation on localizing custom Web services and portlets, see the Oracle WebCenter Interaction Web Service Development Guide.
Out of the box, the Oracle WebCenter Interaction user interface is localized into eleven languages: Dutch, English, French, German, Italian, Portuguese, Spanish, Japanese, Korean, Simplified Chinese, and Traditional Chinese.
Each portal user can choose her preferred language by changing her locale under My Account | Edit Locale Settings. For example, if a portal user changes her locale setting to any of the German locales (Austria, Germany, Luxembourg, or Switzerland), the user interface language will change to German.
You can create additional languages for the Oracle WebCenter Interaction user interface. For details, see Adding Custom Languages.
Oracle WebCenter Collaboration and Oracle-BEA AquaLogic Interaction Publisher are localized to the same eleven languages as the Oracle WebCenter Interaction user interface. Oracle-BEA AquaLogic Interaction Studio and Oracle-BEA AquaLogic Interaction Workflow are localized to a subset of those languages.
It is possible to add custom languages to these applications; however, these customizations are not recommended unless done by Oracle professional services. To engage Oracle professional services, contact your Oracle representative.
The Search index is stored in UTF-8 Unicode and supports 62 languages.
The Search engine supports advanced stemming and tokenization for the following 23 languages:
In addition to those 23 languages, the Search engine provides basic tokenization support for an additional 39 languages.
The Search engine languages are hard-coded and cannot be customized.
You can localize the names and descriptions of portal objects. For example, if you create a portlet with the name “Travel Portlet,” it is possible to associate the name “Dienstreise Portlet” with the portlet for display to German locales.
Names and descriptions are added or modified using the administrative user interface for each object. When the object is opened in the administrative editor, the Properties and Names page allows you to specify a name and description for any available language.
For details on editing object properties, see the Oracle WebCenter Interaction online help.
You can export and import localized names and descriptions in bulk with the Localization Manager. Names and descriptions of objects are exported from the Oracle WebCenter Interaction database into an XML file. The XML file contains name and description strings and their translations. Translations are added or edited in the XML file, and then the names and descriptions imported into the Oracle WebCenter Interaction database using the Localization Manager.
This is a small sample of exported names and descriptions:
<localizationtable>
<languages count='9'>
<language>de</language>
<language>en</language>
<language>es</language>
<language>fr</language>
<language>it</language>
<language>ja</language>
<language>ko</language>
<language>pt</language>
<language>zh</language>
</languages>
<segments count='554'>
<segment stringid='0' itemid='1' classid='2'>
<source language='en'>Administrators Group</source>
<target language='de'>Administratorengruppe</target>
<target language='en'></target>
<target language='es'>Grupo Administradores</target>
<target language='fr'>Groupe d'administrateurs</target>
<target language='it'>Gruppo Amministratori</target>
<target language='ja'></target>
<target language='ko'></target>
<target language='pt'>Grupo de administradores</target>
<target language='zh'></target>
</segment>
<segment stringid='1' itemid='1' classid='2'>
<source language='en'>WCI Administrators Group</source>
<target language='de'>WCI-Administratorengruppe</target>
<target language='en'></target>
<target language='es'>Grupo Administradores de WCI</target>
<target language='fr'>Groupe d'administrateurs WCI</target>
<target language='it'>Gruppo Amministratori WCI</target>
<target language='ja'></target>
<target language='ko'>WCI </target>
<target language='pt'>Grupo de administradores WCI</target>
<target language='zh'>WCI </target>
</segment>
…
</segments>
</localizationtable>
contains all of the user interface languages supported in the portal.
contains one or more <segment>
nodes. The count
element shows the total number of name or description strings in the portal.<segment>
contains a single name or description string and its translations. The contained <source>
node is the original, to be translated text. The <target>
nodes are the translations of the <source>
node text.
The language
element of each node is the ISO 639-1 two letter identifier for the given language.
This section covers adding custom languages to the Oracle WebCenter Interaction portal user interface. Adding custom languages to other Oracle WebCenter products, such as Oracle WebCenter Collaboration or Oracle-BEA AquaLogic Interaction Publisher must be done by Oracle professional services.
Adding a custom language to the Oracle WebCenter Interaction portal user interface is a four step process:
Caution: | Customizing OpenFoundation language resources is currently not supported. |
The portal component loads supported languages based on the contents of the directory PT_HOME/ptportal/version/i18n. This directory contains one subdirectory for each supported language, each named with the ISO-639-1 language code.
The first step in adding a new language to the portal is to add a directory for that language to PT_HOME/ptportal/version/i18n. To do this:
The second step in adding a new language to the portal is to add style sheets for that language. This is done by editing template files that are built into CSS by the Oracle WebCenter Interaction cssmill component.
The following steps describe this process, using the Czech language as an example:
Note: | Extended characters must be translated into their Unicode escape (\uxxxx), and the leading backslash must be escaped with a second backslash (\\uxxxx). |
colorscheme.name.
language_code
line to each file and setting it equal to the name of the color scheme in the language. For example, in color.1.properties the English language color scheme is named with this line:colorscheme.name.en=Plum
To create a new name for the Czech locale, add a line:
colorscheme.name.cz=Lavendelblauw
<macrodef name="make_main_css">
, in the <sequential>
node.For Czech, the added line would be:
<make_main_language_css LANGUAGE=”cz” COLOR=”@{CIKIR}”/>
<macrodef name="make_508colors_css">
, in the <sequential>
node.For Czech, the added line would be:
<make_508_lang_color_css LANGUAGE="cz" COLOR="@{COLOR}" CSSPATH="@{CSSPATH}" />
<macrodef name="make_comm_color_css">
, in the <sequential>
node.For Czech, the added line would be:
<make_comm_lang_color_css LANGUAGE="cz" COLOR="@{COLOR}" CSSPATH="@{CSSPATH}" INDEX="@{CSSPATH}index.properties"/>
<macrodef name="append_index_for_color">
, in the <sequential>
node.For Czech, the added line would be:
<concat_color destfile="@{INDEX}" keyprop="mainstyle@{COLOR}-cz.css" valprop="pre@{COLOR}.colorscheme.name.cz"/>
<target name="make_main_css" depends="make_css_dir">
.For Czech, the added line would be:
<antcall target="make_main_language_css"><param name="LANGUAGE" value="cz"/></antcall>
<target name="make_508colors_css">
.For Czech, the added line would be:
<antcall target="make_508_lang_color_css"> <param name="LANGUAGE" value="cz"/><param name="COLOR" value="${COLOR}" /></antcall>
<target name="make_comm_color_css">
.For Czech, the added line would be:
<antcall target="make_comm_lang_color_css"><param name="LANGUAGE" value="cz"/></antcall>
<target name="append_index_for_color">
.For Czech, the added line would be:
<concat destfile="${INDEX}" append="true">mainstyle${COLOR}-cz.css=${colorscheme.name.cz}
</concat>
Online help is located on the Image Service under each product’s private/help directory. For example, the Oracle WebCenter Interaction online help files are located in imageserver/plumtree/portal/private/help. Under this directory are two directories, std for standard online help and 508 for Section 508-compliant help. Under those directories are directories for each supported language.
For example, the standard English online help for Oracle WebCenter Interaction is located in imageserver/plumtree/portal/private/help/std/en.
Online help is compiled using RoboHelp X5 for European languages and RoboHelp 2002 for Asian languages. RoboHelp projects are made available upon request. Contact Oracle Support at http://www.oracle.com/support/index.html for details.
You must localize string files for various Javascript user interface components when adding a language to the portal. The following Javascript components require you to add a string file with each added language:
These components are located on the Image Service, under imageserver/plumtree/common/private/js. The string files are located under each component’s directory, in LATEST/strings.
To add a string file for the new language:
LATEST/strings/PTControls-en.js
LATEST/strings/PTControls-cz.js.