Develop > Tailoring > Localization > Localize untranslated text strings in Service Manager resource files

Localize untranslated text strings in Service Manager resource files

If you want to localize untranslated text strings in Service Manager, follow the instructions in this section.

Note For the Windows Client, it is hard to distribute text translations by customers; additionally, since Micro Focus has been focusing on defect fixings instead of new feature development since Windows Client 9.3x, a very limited number of new text strings have been introduced. For these reasons, the Windows Client does not really needs self localization and is hence not discussed in this section.

Applications

The localization of the applications may include the following types of records: Format, Message, Help, HTML Template, and Unit of Measure.

Format

To localize a Format record into a target language (for example, Korean), follow these steps:

  1. Log on to the Service Manager Windows client as a system administrator with the target language.
  2. From the System Navigator, click Tailoring > Forms Designer.
  3. In the Form field, enter the name of the format.
  4. Click Search to display the record.
  5. Click Design.
  6. Localize the format record to the target language.
  7. Click OK.
  8. Click OK.

For more information, see Forms Designer.

Message

To localize a Message record into a target language, follow these steps:

  1. Log on to Service Manager as a system administrator.
  2. From the System Navigator, click Tailoring > Notifications > Messages.
  3. Enter other information as appropriate, and then click Search to display the record.
  4. Update the Text field to a localized version for the target language.
  5. Click Save.

For more information, see Add a message record.

Help

To localize a Help record into a target language, follow these steps:

  1. Log on to the Service Manager Windows client as a system administrator with the target language.
  2. From the System Navigator, click Tailoring > Database Manager.
  3. Type help in the Form field, and then click Search.
  4. Double-click the help (help.g) form.
  5. Click Search to display the record.
  6. Update the help record.
  7. Click Save.
  8. Click Accept.

For more information, see Field help editor.

HTML Template

To localize an HTML template into a target language, follow these steps:

  1. Log on to the Service Manager Windows client as a system administrator with the target language.
  2. From the System Navigator, click Tailoring > Notifications > HTML Templates.
  3. Enter information as appropriate, and then click Search to display the record.
  4. Update the template record to a localized version for the target language.
  5. Click Save.

For more information, see Localize a template.

Unit of Measure

To localize a unit of measure into a target language, follow these steps:

  1. Log on to the Service Manager Windows client as a system administrator with the target language.
  2. From the System Navigator, click Tailoring > Database Manager.
  3. Type unitofmeasure in the Table field, and then click Search.
  4. Enter information as appropriate, and then click Search to display the record.
  5. Update the Unit of Measure record to a localized version for the target language.
  6. Click Save.

Web Tier

The Service Manager Web Tier is a standard web application developed with Java, which uses the standard internalization technique introduced in Java Standard Edition. By using the native2scii tool, you can easily customize the label and message text strings in the Service Manager Web Tier.

The text strings that need to be localized are located in the following files:

<webtier-9.xx.war>/WEB-INF/classes/alert_en.properties
<webtier-9.xx.war>/WEB-INF/classes/calendarBundle_en.properties
<webtier-9.xx.war>/WEB-INF/classes/chMBundle_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/cwc/web/app_labels_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/branding/brandingBundle_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/cac/cac_logon_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/cpe_web_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/diagram/diagram_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/L10N/recordList/recordList_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/report/pivot/pivot_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/smc/smc_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/view/cpew_view_en.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/xslstrings_en.properties
<webtier-9.xx.war>/WEB-INF/classes/conditionEditorBundle_en.properties
<webtier-9.xx.war>/WEB-INF/classes/dashboardBundle_en.properties
<webtier-9.xx.war>/WEB-INF/classes/globalSearchBundle_en.properties
<webtier-9.xx.war>/WEB-INF/classes/workflowBundle_en.properties

The originally localized cwc_labels file in languages other than English are as follows:

<webtier-9.xx.war>/WEB-INF/classes/alert_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/calendarBundle_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/chMBundle_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/cwc/web/app_labels_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/branding/brandingBundle_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/cac/cac_logon_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/cpe_web_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/diagram/diagram_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/L10N/recordList/recordList_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/report/pivot/pivot_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/smc/smc_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/telephony/telephonyBundle_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/view/cpew_view_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/xslstrings_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/conditionEditorBundle_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/dashboardBundle_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/globalSearchBundle_xx.properties
<webtier-9.xx.war>/WEB-INF/classes/workflowBundle_xx.properties

Each resource file follows a naming rule, which is <basename>_<language>.properties or <basename>_<language>_<country>.properties. Take the cpe_web_en.properties file for example, ‘cpe_web’ is the basename, and ‘en’ is the language code. For cpe_web_zh_CN.properties, ‘CN’ is the country code. The file names are case-sensitive.

The following table lists the language codes of the supported languages in Service Manager. This table uses cpe_web as an example resource file base name (other resource files follow the same rule).

Note For the languages highlighted in the following table, new content in the SM 9.60 release is not localized.

Resource base name

Language Code

Country Code

Description

cpe_web

 

 

Default

cpe_web

en

 

English

cpe_web

ar

 

Arabic

cpe_web

cs

 

Czech

cpe_web

de

 

German (Standard)

cpe_web

es

 

Spanish(Spain)

cpe_web

fr

 

French(Standard)

cpe_web

hu

 

Hungarian

cpe_web

it

 

Italian (Standard)

cpe_web

ja

 

Japanese

cpe_web

ko

 

Korean

cpe_web

zh

CN

Chinese (PRC)

cpe_web

nl

 

Dutch (Standard)

cpe_web

pt_BR

 

Portuguese (Brazil)

cpe_web

ru

 

Russia

cpe_web

iw

 

Hebrew

cpe_web

pl

 

Polish

cpe_web

tr

 

Turkish

Service Manger uses UTF-8 as the default encoding when interpreting the resources. When localizing the untranslated text strings, you need to convert all resources files in native language in UTF-8 file encoding into files containing Latin-1 and/or Unicode-encoded characters with the native2scii tool. The localization process consists of the following steps.

Step 1. Set up Java development Environment on Windows

Perform the following steps on a Windows machine.

  1. Download and install Java Standard Edition 8.
  2. Set the JAVA_HOME variable and add <JAVA_HOME>/bin to the system's path variable.

  3. Open the operating system's Command Prompt, and run the following command to verify that JRE 8 is correctly configured: 

    java  -version

Step 2. Convert texts in a specific language to Unicode

  1. Check the Service Manager release notes for newly introduced strings and their corresponding resource base names.

  2. Translate the newly introduced strings to a target language and name it to <basename>_<lang>.txt.

    Make sure the text file uses the UTF-8 encoding.

  3. Run the native2ascii command to convert the text strings.

    native2ascii -encoding utf-8 <basename>_<lang>.txt <basename>_<lang>.properties

    Tip For more information about how to use this tool, see here.

  4. Copy the output file of the native2ascii command (that is, <basename>_<lang>.properties) to the same folder in which <basename>_<lang>_en.properties is located. If a file with the same name already exists, merge the content to the existing file.

Suppose the newly introduced string is “WebController.Main_Menu_1=Main Menu” and the base name is “cpe_web”. Take Turkish for example, follow these steps to do the localization:

  1. Translate the new string to Turkish and save it to cpe_web_tr.txt.

    This file should contain the following content: 

    WebController.Main_Menu_1=Ana Menü

  2. Run the native2ascii command:

    native2ascii -encoding utf-8 cpe_web_tr.txt cpe_web_tr.properties

    After conversion, the content of cpe_web_tr.properties should look like the following:

    WebController.Main_Menu_1=Ana Men\u00fc

  3. Copy the converted content and add it to the cpe_web_tr.properties file located in the following directory (using Tomcat as an example):

    <Tomcat>/webapps/<webtier-9.xx.war>/WEB-INF/classes/com/hp/ov/sm/client/webtier/

    Now the text conversion for Turkish is complete.

Service Request Catalog (SRC)

Text strings in SRC that should be localized are located in the following folder: <src-xxxx.war>\resources\client\<lang> . Here, <lang> is a language code.

You can use the native2scii tool to localize the new text strings. The steps are similar to those for the web tier. For details, see Web Tier.

Mobility Client

Text strings in Mobility Client that should be localized are located in the following folder: <webapp-9.xx.xxxx.war>\WEB-INF\classes. There are three base names: appLoginBundle, appMainBundle, and getIT.

You can use the native2scii tool to localize the new text strings. The steps are similar to those for the web tier. For details, see Web Tier.

Chat

To localize the Chat UI into a target language, follow these steps:

  1. Go to the <chat-ui-xxxx.war>\assets\locales the folder.
  2. Open the folder for the target language. For example, open the tr folder for Turkish.
  3. Open the i18n.json file in a text editor.
  4. Update the untranslated text strings in this file to the target language.

  5. Save the file with the UTF-8 encoding.

    Caution Do not save it with the ANSI encoding.

Related topics

Localization

Localize Service Manager with the Open Localization Toolkit