Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Global Deployment Guide > Localizing Global Deployments > About the Localization ProcessLocalizing a Siebel application includes translating the user interface and modifying other attributes to meet locale-specific requirements. NOTE: It is recommended that you complete as much configuration as possible before you begin localizing the application. One reason for doing so is that configuration potentially alters what needs to be translated, so it is better to have a stable application. Also, the check-in and check-out mechanism in Siebel Tools or Siebel Web Tools is meant to be performed in only one language; if you perform localization tasks on the client during configuration, then there is a potential for data loss. For detailed information about working with user interface strings (including symbolic strings) and other locale-specific data, see Using Siebel Tools. You can use the Locale Management Utility (LMU) in Siebel Tools to manage strings and other data. More information about the LMU is provided later in this topic. For information about localizing strings for Lists of Values (LOVs) and multilingual lists of values (MLOVs), see Localizing Lists of Values and Multilingual Lists of Values. NOTE: See also Localizing an Unshipped Language. In general, you perform the tasks in that topic, where applicable, before you perform the other localization tasks described in this chapter. Localization ProcessThe localization process typically includes the following steps:
|
![]() ![]() |
Siebel Global Deployment Guide | Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |