Locating fonts when generating BIRT documents
To render or generate BIRT design output, iHub looks for font configuration information in the AC_SERVER_HOME/Jar/BIRT/platform/plugins/org.eclipse.birt.report.engine.fonts directory.
BIRT designs use five different types of font configuration files. The font configuration file naming convention includes information about the rendering format, the system platform, and the system locale, as shown in the following template:
fontsConfig_<Format>_<Platform>_<Locale>.xml
BIRT supports the following levels of font configuration files:
For all rendering formats:
These files have no format specifier in their names. The configuration files are divided into three sub‑levels:
The default configuration file:
fontsConfig.xml
Configuration files for a specific platform, for example:
fontsConfig_Windows_XP.xml
Configuration files for a specific platform and locale, for example:
fontsConfig_Windows_XP_zh.xml
fontsConfig_Windows_XP_zh_CN.xml
For certain formats only
These files include the format specifier in their names. These configuration files are divided into three sub‑levels:
The default configuration file for a format, for example:
fontsConfig_pdf.xml
Configuration files for a format for a specific platform:
fontsConfig_pdf_Windows_XP.xml
Configuration files for a format for a specific platform and locale:
fontsConfig_pdf_Windows_XP_en_AU.xml
iHub first looks for the font location in the font configuration files. If the font is not found, iHub searches for the font in the system‑defined font folder. An exception to this search order occurs if iHub encounters a <fonts‑path> section in one of the font configuration files. iHub searches each path coded in the <fonts‑path> section instead of searching the system-defined font folder.