OpenPortal^? - Internationalization and Localization

Welcome to the Globalization Community wiki. This wiki talks about OpenPortal^? Internationalization and Localization. OpenPortal^? is Internationalized i.e. You can localized it. OpenPortal^? has been localized out of box in 7 languages - German(de), French(fr), Spanish(es), Japanese(ja), Traditional Chinese(zh_TW), Simplified Chinese(zh_CN) and Korean(ko).

Internationalization, Localization and Globalization

Internationalization - I18n - '18' refers to the 18 letters between I and n
Internationalization is the process of developing a software product whose core design does not make assumptions based on a locale. It potentially handles all targeted linguistic and cultural variations (such as text orientation, date/time format, currency, accented and double-byte characters, sorting, etc.) within a single code base. Isolating all message strings in text files is another necessary step to prepare a product for localization.

Localization - L10n - '10' refers to the 10 letters between L and n
Customizing software and documentation for a particular country. It includes the translation of menus and messages into the native spoken language as well as changes in the user interface to accommodate different alphabets and culture.

Globalization - G11n - G11n is combination of Internationalization and Localization In the translation/localization business marketplace, it refers to the whole problem of making any product or service global.

Location of OpenPortal^? L10n sources

L10n sources are part the OpenPortal^? repository

Download Open Portal Repository - Refer Instructions
All the l10n files are located along with their english counterparts. It makes them easier to locate.

ex. English File location :../openportal/portal/admincli/src/com/sun/portal/admin/cli/commands/LocalStrings.properties
Gernam File location : ../openportal/portal/admincli/src/com/sun/portal/admin/cli/commands/LocalStrings_de.properties

*L10n source file encording*
Under the repository L10n files have following encoding

• . ".properties" files - native2ascii encoding
• ".xml" and ".xsl" files - UTF-8 encoding

Build OpenPortal^? with L10n

To provide seamless experience to L10n users, there are no special steps for Building OpenPortal^? with L10n.
Refer Build Instructions

Installing OpenPortal^? with L10n

To provide seamless experience to L10n users, there are no special steps for Installing OpenPortal^? with L10n.
Installation will also install all the l10n files of seven localized languages mentioned above. Refer Install Instructions

L10n How to and Tips

How to invoke installer of OpenPortal^? in your language - GUI Mode

Portal Server 7.2 installer is localized in German (de), Spanish (es), French (fr), Japanese (ja), Korean (ko), Simplified Chinese (zh_CN), and Tranditional Chinese (zh_TW) languages. You can install Portal Server 7.2 in any of the languages by changing the system locale before doing installation . The following procedure explains how to change system locale in UNIX system.

1) Change the default locale by setting the LC_ALL and LC_LANG environment variables. For example, to set the Czech locale with UTF-8 encoding, run the following commands.

$ LC_ALL=es_ES.UTF-8
$ export LC_ALL
$ LANG=es_ES.UTF-8
$ export LANG

To verify locale is set correctly use following command.

$ locale

3) Run following command to invoke the Portal Server 7.2 GUI installation wizard to install the software.

 ./installer -j $[JAVA_HOME] 

The Portal Server 7.2 installation wizard is invoked and the Welcome screen appears in language selected in Step 1.

Then follow PortalInstallInstructions#Install_Portal_Server_7_2^?

After installation you can follow instruction of [[Configuring Sample Portals][PortalInstallInstructions#Install_sample_portals] section to configure samples. Samples are also localized in German (de), Spanish (es), French (fr), Japanese (ja), Korean (ko), Simplified Chinese (zh_CN), and Traditional Chinese (zh_TW) languages.

On Microsoft Windows, currently zip install is only supported. There is no GUI Installer.

How to access OpenPortal^? in your language

Please make sure you set correct prefer language in your browser before you access portal server: 'de' for German, 'es' for Spanish , 'fr' for french , 'ja' or 'ja-JP' for Japanese , 'ko' or 'ko-KR' for Korean , 'zh-cn' for Simplified Chinese and 'zh-tw' for Tranditional Chinese. You will get localized page after you set it correctly in browser.

For Internet Explorer browser, here are steps to set it: 1.Open Internet Explorer by clicking the Start button Picture of the Start button, and then clicking Internet Explorer. 2.Click the Tools button, and then click Internet Options. 3.Click the General tab, and then click Languages. 4.In the Language Preference dialog box, click Add. 5.In the Add Language dialog box, select a language from the list, and then click OK. 6.Up that language to first one. 7.Click OK twice.

For Firefox browser on windows, here are steps to set it: 1.Open Firefox browser 2.Click the Tools button, and then click Preferences. 3.Click 'Advanced' in top, and then click Languages in General tab. 4.In the Language dialog box, select your language and click Add. 5.Up that language to first one. 6.Click OK twice.

The steps is similar if your run Firefox on solaris. You can find Preferences under 'Edit' menu.

Please refer your browser's document about how to set prefer language in your browser if you are using other type browser accessing portal server.

How to execute Portal CLI in your environment

Portal CLI command (psadmin) can be executed in one of the localized seven language.

Step1 : On Unix , Change the default system locale by setting the LC_ALL and LC_LANG environment variables, e.g. to set the Czech locale with UTF-8 encoding, you would need to run:

$ LC_ALL=es_ES.UTF-8
$ export LC_ALL
$ LANG=es_ES.UTF-8
$ export LANG

To verify locale is set correctly use following command.

$ locale

On Unix, you can see which is the current locale by running the {{locale}} command.

Step2 : Execute psadmin command and output will be there in language set in Step1.

On Microsoft Windows, you need to change the system locale in the regional settings:

Open the Control Panel from the Start menu to modify the operating system locale settings. On Windows 2000, click Regional Options. On Windows XP and Windows 2003, click Regional and Language Options.

To set locale for the current operating system user on Windows 2000, select the desired locale from the pop-up list in "Settings for the current user" area on the General tab. On Windows XP and Windows 2003, select the desired locale from the pop-up list in "Standards and formats" area on the Regional Options tab.

Some of the locales may be unavailable until you install required operating system support files. On Windows 2000, make sure that the relevant language group is selected in "Language settings for the system" area on the General tab. On Windows XP and Windows 2003, make sure the relevant check boxes are checked in "Supplemental language support" area on Languages tab.

;Note:The operating system must be restarted after the system locale is changed. See also the operating system documentation for further information about Windows locale settings.

How to Change channel titles and other properties in Portal Server Admin Console

1. Log in to the Portal Server management console.
2. Select the Portals tab.
3. Select a portal from Portals.
4. FromSelectDNdrop^?-downmenu, select any DN.
5. UnderTask^?, click Manage Channels and Containers.
6. Select a channel or container in the tree on left frame to display Edit Properties page on the right frame.
7. Change the properties, and click Save. For example, to change channel's title for ja locale:
   
   1. Click Table Preferences icon on the properties table. This will show Table Preferences input area in the table.
      b. Type a locale, ja in Locale input area
      c. Click OK. This will show specified locale properties.
      d. Change title in properties
      e. Click Save
      

How to Participate

Get Involved

Email aliases : dev@portal.dev.java.net or users@portal.dev.java.net.

Identifying L10n issues

Following are some examples for L10n issues -

• Text is not localized
• Localized Translation is not correct
• Context of translation is not correct

Identifying I18n issues

Following are some examples of I18n issues -

• Text is garbled i.e coming as ????
• Date format is not correct as per locale
• Strings are hard coded in Source files
• Sorting order is not correct as per locale

L10n Blogs/Articles

Portal Post
Locale codes
Creating Multilingual Portals
I18n and L10n of Portlets