| Understanding font configuration file priorities |
BIRT reports 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 general format:
fontsConfig_<Format>_<Platform>_<Locale>.xml
The platform name is defined by the Java System property, os.name. The current Java Network Launch Protocol (JNLP) specification does not list the values for the os attributes. Instead it states that all values are valid as long as they match the values returned by the system property os.name. Values that only match the beginning of os.name are also valid. If you specify Windows and the os.name is Windows 98, for example, the operating system name is accepted as valid.
The following sample Java class code shows how to check the os.name property for the value on your machine:
class WhatOS
{
public static void main( String args[] )
{
System.out.println( System.getProperty("os.name") );
}
}
BIRT supports the following types of font configuration files, with increasing priority:
For all rendering formats
These files have no format specifier in their names. These configuration files are divided into three sub‑types.
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 two sub‑types:
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
