Suppose that uifont.ali contains this entry in the section:
While formatting, Oracle Reports checks uifont.ali for any mappings of either specified font. If the user is running this report on a PostScript-1 printer and generating HTML output, the fonts are chosen as follows: Suppose that a report has layout objects associated with one of two fonts, Helvetica font of size 8, style Plain, and weight Medium, and Courier font. It should be noted that irrespective of any font in the output file, the final printed output will depend solely on the fonts installed in the printer. If a font matches the font size but nothing else and another font matches the style, weight, and width but not the font size, then Oracle Reports will pick the font with the same font size. If Oracle Reports can't match the font face, it will try to match the font size if it can't match the size, it will try to match the font style and so on. When attempting to match a font, Oracle Reports will try to find the closest match according to the following criteria for fonts with the same character set:įontface > fontsize > fontstyle > fontweight > fontwidth If more than one font has the same parameters, Oracle Reports picks the first one and uses it instead of the original font. After a set of fonts with a similar character set is found, Oracle Reports picks the closest match to the requested font based on the font weight, style, etc. If it cannot find any matching font for this character set, Oracle Reports searches for a font that has a character set for the environment in which the application is running. If this font name is not in that list, Oracle Reports tries to look for the closest matching font from the list of fonts given in the printer definition file.įor the SimSun font, the character set is 850. Oracle Reports will look for the font SimSun in the list of available fonts generated by the Font lookup algorithm. For example, suppose a report is originally designed with a Korean font SimSun and in the uifont.ali file no mapping for this font is found. If a particular font is needed but not found in the PPD file or if an AFM file is not found, Oracle Reports will look for the nearest matching font according to its matching rules. Once the list of available fonts is generated, the mapped font is searched for in this list of fonts and, again, the AFM files are read for the purpose of calculating the text size and weight. Otherwise, Oracle Reports matches this font to the closest available one. While looking for a font, Oracle Reports searches for an entry in the HPD file with the font name and accordingly takes the font if the TFM file for this font is also found. Note:Similarly for PCL printers, the HP printer definition file (glue file) is loaded and all the fonts defined in the file are also loaded.
For more information on Tk2Motif.MapsCS, refer to Font Configuration Files. Reports Builder includes only those fonts with an encoding of iso8859-1, unless specified differently in the toolkit resource file, Tk2Motif.MapsCS. The character set is driven by the NLS_LANG environment variable. From this font list, Reports Builder generates a list of usable fonts with the valid style, weight, width, size, and encoding characteristics to match the character set. The command is similar to the UNIX xlsfonts command, which lists all of the available fonts for the X-server display. On UNIX, the font list is derived by querying the X-server display on which the application is running for the available fonts.
True Type fonts are associated with a TTF icon. A small printer icon before the font name identifies printer fonts. On Windows, the font list is derived from the fonts that are installed on the system along with the fonts available on the current default printer. Description of the illustration font_pick.gif