You can translate reports and catalogs in Publisher.
Publisher supports translation in two ways, as described in the following sections:
What Is Catalog Translation?
Catalog translation is a feature of Publisher that enables you to extract the translatable strings from all objects contained in a selected catalog folder into a separate file.
If Publisher is integrated with Oracle Business Intelligence Enterprise Edition, Publisher catalog translation (folder and report, data model, style template and sub template names) is ignored. The Oracle BI Enterprise Edition catalog translation mechanism is applied instead.
The separate string file can be translated and uploaded back to Publisher and assigned the appropriate language code.
Catalog translation extracts not only translatable strings from the report layouts, but also the user interface strings that are displayed to users, such as catalog object descriptions, report parameter names, and data display names.
Users viewing the catalog see the item translations that are appropriate for the user interface language that they selected in their My Account preferences. Users see report translations that are appropriate for the Report Locale that they selected in their My Account preferences.
What Is Template Translation?
Template translation enables you to extract the translatable strings from a single RTF-based template (including sub templates and style templates) or a single Publisher layout template (.xpt file).
Use this option when you need only the final report documents translated. For example, you must generate translated invoices to send to German and Japanese customers.
About Supported Languages
Publisher supports any language that is supported by Unicode and doesn't require a special algorithm to render.
Examples of languages that require a special algorithm to render are Hindi and Farsi. It's the user's responsibility to prepare an appropriate font if the language isn't supported by Albany fonts.
Publisher does support Arabic and Hebrew.