Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Global Deployment Guide > Localizing Global Deployments > Localizing an Unshipped Language > Creating Language and Locale RecordsThis 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, then you must create them in the Siebel application. You do this in the Administration - Data screen, in the Languages and Locale views. Each language code used by Siebel applications uses 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. For more information about the language codes used by Siebel Business Applications, see Language. 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 can be used to differentiate the countries 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 Norwegian, a language that is not shipped for Siebel Business Applications, is NOR. When creating language records, observe the following guidelines:
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
NOTE: If necessary, then, after you create the language record, also create a record for any new locale that you require. More information about locales is provided, as follows. About Creating a LocaleIf an existing Siebel locale does not cover the users of the unshipped language that you are implementing, then you must also create a locale record for the location for these users. Locales correspond to user-specific or computer-specific settings such as Regional and Language Options in the Control Panel on Microsoft Windows. For example, if you create a Norwegian (NOR) language record, then Norwegian-speaking users might use an existing locale, such as for Sweden, or might require using a locale for Norway in order to specify settings such as dialing code, date formatting, and so on. In some cases, time zones will differ between locales. 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 of the languages that 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 © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |