Siebel Global Deployment Guide > Localizing Global Deployments > Localizing an Unshipped Language >

Creating Language and Locale Records

This topic is part of Localizing an Unshipped Language.

Localizing an unshipped language requires that appropriate Siebel language and locale records exist in the Siebel Database. If these records do not already exist, you must create them in the Siebel application. You do this in the Administration - Data screen, in the Languages and Locale views.

Language codes used by Siebel applications use a three-letter code, such as ENU for U.S. English, FRA for French, THA for Thai, and so on. Using language codes with only two characters does not work and is not supported. See also About Parameters for Language and Locale.

These codes follow conventions used by Microsoft, where the first two letters represent a two-letter language code from ISO Standard 639, and the third letter differentiates the main country where this language is used. Multiple entries can represent different countries that use variants of the same language (for example, PTG for Portuguese - Portugal, and PTB for Portuguese - Brazil).

When you create language records for an unshipped language, use the language code names published by Microsoft. For example, the language code defined for Polish, a language that is not shipped for Siebel Business Applications, is PLK.

When creating language records, observe the following guidelines:

  • Language codes must be defined using all capital letters (such as PLK rather than plk, for Polish).
  • Your language code must use the same first two letters as the Microsoft code for the language, in order to ensure that the correct internal libraries will be used. For example, if you want to create a language code for Austrian German, name it DEA, so it will use the same code page as German (DEU). Similarly, use ENG for British English.

Siebel language records are stored in the S_LANG table.

For more information about Microsoft codes, see Microsoft documentation.

Two parameters, Language Code and (optionally) OM - Resource Language Code, are used to specify how an application uses languages. For more information, see About Parameters for Language and Locale.

To create a Siebel language record for an unshipped language

  1. In the Siebel application, navigate to Administration - Data > Languages.
  2. If necessary, create a new record for the unshipped language.

    For example, for Polish, specify Polish as the Name value and specify PLK as the Code value.

  3. Start Siebel Tools against the server database, and verify that the language record displays correctly. Also verify in the List of Values Administration screen that you can enter LOV records for the new language.

NOTE:  If necessary, after you create the language record, also create a record for any new locale you require. More information about locales is provided below.

About Creating a Locale

If an existing Siebel locale does not cover the users of the unshipped language you are implementing, you must also create a locale record for the location for these users.

Locales correspond to user or machine-specific settings such as Regional Settings defined in your Microsoft Windows control panel.

For example, if you create a Polish (PLK) language record, then Polish-speaking users may use an existing locale, such as Germany, or may require a locale for Poland, in order to specify settings such as time zone, dialing code, date formatting, and so on.

When creating a locale, copying an existing locale for which some of the same settings apply will make data entry easier. After you create a new locale, create translation records to provide the name for the locale for all the languages you are using.

Siebel locale records are stored in the S_LOCALE table.

See also Additional Information About Setting Up and Administering Locales.

For detailed information about creating locales, see Siebel Applications Administration Guide.

Siebel Global Deployment Guide Copyright © 2007, Oracle. All rights reserved.