The font can be either .ttf (TrueType) or .otf (OpenType).
Note that .otf (OpenType) is not supported on Windows XP.
Using InlineSetting with the
Face setting name is the preferred method of specify a desired font. Fonts are used by specifying the family name of the font in the
InlineSetting=Face option in the string meter. (e.g.
InlineSetting=Face | Trebuchet MS). The family name can be found by double clicking the font .ttf/.otf file and at the very top left in the Windows font viewer see the Font Name:.
Additional attributes for the font can then be specified with the other
InlineSetting setting names, such as
GradientColor and more. See the InlineSetting reference for details.
Note: There is a great deal more functionality and flexibility possible when using the
InlineSetting options rather than the older
FontFace option described below. In particular, the
Weight setting, with up to ten possible values from "Hairline" to "Ultra Black", is much more flexible than the older
StringStyle with just "Normal" or "Bold". In addition, several font styling options are only available with
InlineSetting. and not with
While not as powerful or flexible as
InlineSetting, fonts can also be used by specifying the family name of the font in the FontFace option in the string meter. (e.g.
FontFace=Trebuchet MS). This name can be found by double clicking the font .ttf/.otf file and at the very top in the Windows font viewer see the Font Name: at the top left.
Most, but not all fonts used with
FontFace can be modified with additional String meter options. (e.g.
StringEffect) Alternatively, some fonts, particularly some of the ones with subfamily endings such as "Bold" or "Italic", will REQUIRE that the matching StringStyle option be added to the string meter. If there are problems using a font, try adding or removing these option on the string meter.
Installed Vs. Uninstalled Fonts
Fonts installed in Windows (they will be in the Windows\Fonts folder) may be used by simply specifying the family name in the
FontFace option of a string meter as described above.
3rd-party font files not installed in Windows can be used by creating a folder @Resources\Fonts in the root level folder of the skin, and putting the font .ttf/.otf files there. Rainmeter will automatically load any fonts found in that folder, and they will be available to use with the family name of the font as if they were installed in Windows.
Note: While it is possible to set a .rmskin to automatically install included fonts in a user's Windows system, this is strongly discouraged. There is literally never a good reason to do this, and it makes it more difficult for users who are running Rainmeter as a "portable" application to use the skin. The fonts should be put in the @Resources\Fonts folder and they will be available and used when the .rmskin is distributed.
There are two ways Rainmeter will react if there is a problem with a font or the way it has been used in a string meter.
- It may produce no error, but display the default Arial font instead of the one specified in
FontFace. This will happen if the wrong family name is specified.
- A log error "Can't create font" may be produced, and the entire string meter will fail to display. This generally means that a string modifier option like
StringStyle=Boldhas been used with a font that does not support it, or the font itself is just not compatible with Rainmeter.