On Windows, a font face name, such as "Courier.Physical font, in a format typically used on the platform: StyleName - one of the four standard font styles:īolditalic.LogicalFontName - one of the five logical font names:ĭialoginput.Throughout the font configuration files, a number of different Files without this suffix are assumed to be in binary format. properties suffix are assumed to be properties files as specified by the Properties class and are loaded through that class. bfc JavaHome /lib/fontconfig.properties JavaHome /lib/fontconfig.bfcįiles with a. The runtime uses the first of the following files it finds: JavaHome /lib/fontconfig. Version - a string identifying the operating system version.OS - a string identifying an operating system variant:.JavaHome - the JDK directory, as given by the system property.The font configuration file for a host operating system is located as follows: In other words, a user-supplied file is preferred if it is a match. On platforms that support font configuration files, the runtime will look first in $JDKHOME/conf/fonts. Instead, put any updates or custom versions of the configuration files in $JDKHOME/conf/fonts. The JDK places any files that it provides in $JDKHOME/lib. The binary format is undocumented and used only for the JDK's predefined configurations the corresponding files in properties format are available for reference as files with the. The properties format is described in detail in this document and can be used for user-defined configurations.
You can edit or create your own font configuration files to adjust the mappings to your particular system setup, however these must be placed in conf/fonts, and are subject to implementation notes discussed below.įont configuration files come in two formats: a properties format and a binary format. The files are distributed with the JDK installation. There may be several files to support different mappings depending on the host operating system version. One way the Oracle JDK maps logical font names to physical fonts is by using font configuration files. These logical font names are mapped to physical fonts in implementation dependent ways.
For the German lower-case diacritical marks, all Headline Types complements contain alternative integrated accents which allow the compact setting of lower-case headlines.The Java Platform defines five logical font names that every implementation must support: Serif, SansSerif, Monospaced, Dialog, and DialogInput. For a number of Bodytypes, hairlines and serifs were thickened or the whole typeface was adjusted to meet the optical requirements for setting type in small sizes. For the Bodytypes, fine spaces were created which prevented the smear effect on acute angles in small typesizes. In addition to the adjustment of spacing, there are also adjustments in the design. The kerning tables, as well, have been individualized for each of these type varieties. That of the Headline Types is decidedly more narrow in order to do justice to the requirements of headline typesetting. That of the Bodytypes is adjusted for readability. The most obvious differentiation can be found in the spacing. One is designed specifically for headline typesetting (SH: Scangraphic Headline Types) and one specifically for text typesetting (SB Scangraphic Bodytypes). Since the release of these fonts most typefaces in the Scangraphic Type Collection appear in two versions.