Explain Output Formats, Fonts, Barcodes & Localization in Oracle BI

36 / 55

Publisherintermediate

Output Formats, Fonts, Barcodes & Localization

Explain how BI Publisher handles multiple output formats, embedded barcodes/special fonts, and multi-language/locale-aware document generation.

The same BI Publisher report frequently needs to serve very different downstream needs — a PDF for archival and legal compliance, an Excel file for a finance team to manipulate, and an EDI/text feed for a trading partner's system — all from the identical data model, and interviewers ask about this to gauge whether a candidate understands BIP's practical breadth beyond a single PDF invoice example.

It's like a single master recipe (data model + template) that a good chef can plate as a formal dinner (PDF), pack as takeout containers (Excel export), or convert into freeze-dried rations for a totally different delivery system (EDI feed) — same ingredients, same recipe, radically different final packaging depending on who's receiving it.

Key Concepts

BI Publisher's rendering engine supports numerous output formats from one template and data model pairing: PDF (most common, for print/archival), RTF/Word (editable output), Excel (native XLSX with formulas/formatting preserved where possible), PowerPoint, HTML (for portal embedding), and plain-text/EDI formats for machine-to-machine feeds — the format is typically chosen at either schedule-time or on-demand run-time, without needing a separate template per format in the common case.

output formats

Barcodes (Code 39, Code 128, QR codes, and others) and special fonts (MICR fonts for check printing, or region-specific fonts) are embedded directly via BI Publisher's barcode/font mapping configuration — a template references a barcode by simply wrapping the data value with the appropriate font/encoding syntax, and the engine converts the underlying text into the correct barcode symbology at render time using registered font mappings, which is why font/barcode setup at the server level is a prerequisite before any template can use them correctly.

Barcodesspecial fonts

Localization support goes beyond simple language translation: BI Publisher supports locale-specific templates (different RTF files per language/region, selected automatically based on a parameter or user locale) as well as XLIFF-based translation of a single template's text strings into multiple languages without duplicating the entire layout — appropriate when the layout structure is identical across locales and only the text needs translating, versus full separate templates when layout itself must differ (e.g., right-to-left languages, or fundamentally different legal document structures per country).

Localizationlocale-specific templatesXLIFF-based translation