BI 4.0 Client Tools Translation Management Tool

1. BI 4.0 Client ToolsTranslation Management Tool Henry Banks Confidential

2. Agenda: Translation Management Tool • Overview • New Translation Framework

3. Extended functionality and New Object Support • BI 4.0, thetranslation management tool has been extended to support more resources: • Universes of New Semantic Layer, through the *.dfx and the *.blx • Crystal Reports documents • Dashboards • Most InfoObjects in the repository

4. Deliverables & Enhancements in BI 4.0 • Deliverables in BI 4.0 • New component : TranslationServer • New CMC right: Translate Objects • Enhancements • Support of concurrent translation • New workflows (for the translation management tool) • New file format (TMGR file) • Complete review of XLIFF generation

5. Local Translation • In BI 4.0, supported local resources are: • Classicuniverses (UNV) • New universes, through Business Layer (BLX) and Data Foundation (DFX) files • Web Intelligence documents (WID) • Workflow • Select a local resource and retrievemetadata to translate • Add new locales • Translate metadata in the new locales • Export back translations into the local resource • Constraints • It is no more possible to translate secured local resources (UNV or WID). • Translation management tooldoes not open the resourceanymore. It justretrieves the strings to translate. They are re-exported once translated.

6. Translation of Content from the Repository • Workflow • Select resourcefrom the repository • Retrieve strings to translate from the resources • Add new locales • Translate metadata in the new locales • Export back translations into the resources in the repository • Resolveconflicts • Advantages • No need to import the whole document from the repository. Only strings to translate are retrieved. • Multiple translators (for different locales) can translate itsimultaneously

7. Conflicts Resolution • Whenexporting back translated strings into the resource in the repository, someconflictsmayoccur • A string has been added in the original resource • A string has been removedfrom the original resource • A string has been modified in the original resource • Whensuchconflictshappen, translation management tool displays theseconflicts. • The user canchoose • To import updated content from the original resource (recommended) • To cancel translation export • To force translation export into the original resource

8. Concurrent Translation • In XI 3.X, translation of a resourcefrom the repositoryneeds to upload the wholeresource and to re-export it once translated. • This export mayoverwiteany changes performedmeanwhile. For example, a French translator canremove all Italian translations whenheispushinghis translations • In BI 4.0, better concurrent authoringcapabilities • Only strings to translate are retrieved and pushed. Other content in the resourceis not modified. • Added or modified locales are highlighted in the Graphical User Interface (with the *character) • Onlyadded or modified locales are pushedinto the source object. • The user canchoose the final result in case of conflictsbetweenits translations and the original resource

9. Overview • The user may • Add new locales to a resource • Translate the resource content in these locales. • Save back the translations in the resources • Define fallback locale • Define the locale as visible or not • Support external translations through XLIFF • Definestatus for eachindividual translation (using XLIFF format file)

10. Translation Management Tool – Summary List

11. Translation Management Tool – Summary List

12. Questions

13. Thank you!