Using Siebel Tools > Working With Strings and Other Locale-Specific Data >

Finding Existing Translations

You can search through objects in the repository to find existing translations for untranslated strings. This allows you to reuse existing translations for user interface objects that you have created or modified.

The LMU compares untranslated strings with string attributes of other objects in the repository. If it finds an object with the same string, it searches for a translation in the language that you have selected as the target language of the current LMU session. If a translation exists, the LMU displays the best candidate for translation and allows you to export it to a file.

For example, suppose you have selected English-American as your source language and Spanish as the target language. You have an applet with a title of Customer that has not been translated. After clicking the Find Translation button, the LMU searches through the repository for other objects with attributes of Customer. If it finds one, it looks for a Spanish translation of the string. If a translation already exists, the translation is displayed and you can export it to a file.

If the LMU finds more than one translation for a source string, the following rules apply:

• If the source string is an attribute of an object that is related to a business component, such as Control Caption or List Column Display Name, then translations from the same business component are examined first. If multiple translations exist in the same business component, the string that occurs the most is selected. If none of the translations exist in the same business component, then the translation that occurs the most often from among all business components is selected.

  For example, suppose Applet A is based on the Account business component. Applet A contains a control caption with the value of Account and this value has been translated to Account_FRA for French. Now suppose you create a new applet, Applet B, that is also based on the Account business component and that also contains a control caption with the value of Account. When you run Find Translations, the LMU would find Account_FRA as an existing translation and select it as the best candidate for this string.

• If the source string is not an attribute related to a business component, such as Menu Item Caption, the translation that occurs the most is selected as the best candidate.

To find translated strings

1. Choose Tools > Utilities > Locale Management.

   The Locale Management dialog box.

2. In the Options tab, under Languages, select the source language and the target language.
3. Under Objects, select the applications or projects that you want to localize.
4. Click the Untranslated Strings tab.
5. Click the Find Translations button.

   The LMU compares untranslated strings with strings of other objects in the repository. If other objects use the same source string, the LMU looks for existing translations of the string and displays the best candidates for translation in the Results window.