Click Languages. Specifying the Default Language for the Sign-In Page

Localizing Oracle Business Intelligence 15-9 special characters as appropriate. You and the localization team are responsible for resolving any errors in the translated text strings. Consider that the contents of the catalog are updated whenever objects are added, deleted, or modified. You can make a copy of every output file for each language to be translated. Figure 15–2 shows an extract from an exported caption XML file before translation. The file is named myfoldercaptions.xml. Figure 15–3 shows an extract from the file after translation. The file is named myfoldercaptions_fr.xml. Figure 15–2 Caption XML File Before Translation Figure 15–3 Caption XML File After Translation

15.2.2.4 Step 4: Handling Duplicate Exported Text Strings

You might encounter an issue of having duplicate exported text strings from the catalog. This situation arises when the Export Captions utility is run simultaneously by multiple users or if the same user runs the utility twice in less than one minute. The following procedure describes how to address duplicate captions. To handle duplicate exported text strings: 1. Run the Export Captions utility, as described in Section 15.2.2.2, Step 2: Exporting Text Strings in the Catalog. 15-10 System Administrators Guide for Oracle Business Intelligence Enterprise Edition 2. In Catalog Manager, with the catalog still open in offline mode, select the folder that contains the strings to export.

3. From the Tools menu, select Export Captions.

4. Click Browse to select the location in which to write the output file, then click OK.

5. In the What to do with duplicate captions section, select one of the following options: ■ Leave alone — Specifies to leave the duplicate captions as they are. ■ Remove IDs — Specifies to generate new and unique IDs for any objects that contain duplicate or invalid IDs. ■ Remove texts — Specifies to generate new and unique IDs for any objects that contain invalid IDs and to delete the text string for an objects that contain valid but duplicate IDs. This option results in two objects with the same name being included in directory listings of the catalog. This option is most useful for a set of analyses that have unique names and message IDs, but that share the same text strings for components such as graph axes and legends. This option results in needing to translate components only once. For example, you might translate X Axis only once rather than once for each graph.

6. Click OK.

Consider the following webmessages.xml file, which contains duplicate captions: WebMessageTable system=catalog type=folder path=sharedexampleA WebMessage name=kcap12790830_5 use=Caption status=new TEXTA Really Good ReportTEXT WebMessage WebMessageTable WebMessageTable system=catalog type=folder path=sharedexampleB WebMessage name=kcap12790830_5 use=Caption status=new TEXTI like this reportTEXT WebMessage WebMessageTable WebMessageTable system=catalog type=folder path=sharedexampleCopy of A WebMessage name=kcap12790830_5 use=Caption status=new TEXTA Really Good ReportTEXT WebMessage WebMessageTable In this example file, Object B has an invalid duplicate message ID. Object Copy of A has a valid but duplicate message ID. You can make the following selections in the Export Captions dialog: ■ Selecting Leave alone makes no changes to the contents of the file. ■ Selecting Remove IDs generates new and unique IDs for both Object B and Object Copy of A. ■ Selecting Remove texts generates a new and unique ID for Object B and deletes the WebMessage element for Object Copy of A. While this option generally ensures fewer messages to translate, keep in mind that you now see two objects with the same name in a directory listing of the catalog in Presentation Services and in Catalog Manager.