ChordPro Implementation: Fonts

There are two ways to specify fonts: with a font filename, and a built-in font name.

A font filename must be either and absolute filename, or a relative filename which is interpreted relative to the font path, which consists of configuration setting fontdir, the fonts resource dir, and the contents of environment variable FONTDIR. In any case, the filename should point to a valid TrueType (.ttf) or OpenType (.otf) font.

The ChordPro Reference Implementation supports the following built-in font names:

Courier, Courier-Bold, Courier-BoldOblique, Courier-Oblique
Georgia, Georgia-Bold, Georgia-BoldItalic, Georgia-Italic
Helvetica, Helvetica-Bold, Helvetica-BoldOblique, Helvetica-Oblique
Verdana, Verdana-Bold, Verdana-BoldItalic, Verdana-Italic
Times-Roman, Times-Bold, Times-BoldItalic, Times-Italic
Symbol, Webdings, Wingdings, ZapfDingbats

Note that using built-in font names has some disadvantages. The fonts have only a limited number of characters (glyphs) and may not be suitable for anything but English and Western European languages. The quality of the output is less, since the built-in fonts do not support kerning. Since real versions of these fonts are easily available, if not already installed, it is strongly advised to not use built-in fonts unless you can deal with the limitations.

If you have quality PostScript Type1 fonts (pfa, pfb, with afm and/or pfm files) they are easily converted to TrueType or OpenType using a tool like FontForge.