GROFF_FONTSection: File Formats (5)
Updated: 27 June 2001
Return to Main Contents
NAMEgroff_font - format of groff device and font description files
DESCRIPTIONThe groff font format is roughly a superset of the ditroff font format. Unlike the ditroff font format, there is no associated binary format. The font files for device name are stored in a directory devname. There are two types of file: a device description file called DESC and for each font F a font file called F. These are text files; there is no associated binary format.
DESC file formatThe DESC file can contain the following types of line:
The res, unitwidth, fonts and sizes lines are compulsory. Other commands are ignored by troff but may be used by postprocessors to store arbitrary information about the device in the DESC file.
Font file formatA font file has two sections. The first section is a sequence of lines each containing a sequence of blank delimited words; the first word in the line is a key, and subsequent words give a value for that key.
Other commands are ignored by troff but may be used by postprocessors to store arbitrary information about the font in the font file.
The first section can contain comments which start with the # character and extend to the end of a line.
The second section contains one or two subsections. It must contain a charset subsection and it may also contain a kernpairs subsection. These subsections can appear in any order. Each subsection starts with a word on a line by itself.
The word charset starts the charset subsection. The charset line is followed by a sequence of lines. Each line gives information for one character. A line comprises a number of fields separated by blanks or tabs. The format is
name identifies the character: if name is a single character c then it corresponds to the groff input character c; if it is of the form \c where c is a single character, then it corresponds to the groff input character \c; otherwise it corresponds to the groff input character \[name] (if it is exactly two characters xx it can be entered as \(xx). Groff supports eight bit characters; however some utilities has difficulties with eight bit characters. For this reason, there is a convention that the name charn is equivalent to the single character whose code is n . For example, char163 would be equivalent to the character with code 163 which is the pounds sterling sign in ISO Latin-1. The name --- is special and indicates that the character is unnamed; such characters can only be used by means of the \N escape sequence in troff.
The type field gives the character type:
The code field gives the code which the postprocessor uses to print the character. The character can also be input to groff using this code by means of the \N escape sequence. The code can be any integer. If it starts with a 0 it will be interpreted as octal; if it starts with 0x or 0X it will be intepreted as hexadecimal.
The entity_name field gives an ascii string identifying the glyph which the postprocessor uses to print the character. This field is optional and has been introduced so that the html device driver can encode its character set. For example, the character `\[Po]' is represented as `£' in html 4.0.
Anything on the line after the encoding field resp. after `--' will be ignored.
The metrics field has the form:
There must not be any spaces between these subfields. Missing subfields are assumed to be 0. The subfields are all decimal integers. Since there is no associated binary format, these values are not required to fit into a variable of type char as they are in ditroff. The width subfields gives the width of the character. The height subfield gives the height of the character (upwards is positive); if a character does not extend above the baseline, it should be given a zero height, rather than a negative height. The depth subfield gives the depth of the character, that is, the distance below the lowest point below the baseline to which the character extends (downwards is positive); if a character does not extend below above the baseline, it should be given a zero depth, rather than a negative depth. The italic_correction subfield gives the amount of space that should be added after the character when it is immediately to be followed by a character from a roman font. The left_italic_correction subfield gives the amount of space that should be added before the character when it is immediately to be preceded by a character from a roman font. The subscript_correction gives the amount of space that should be added after a character before adding a subscript. This should be less than the italic correction.
A line in the charset section can also have the format
This indicates that name is just another name for the character mentioned in the preceding line.
The word kernpairs starts the kernpairs section. This contains a sequence of lines of the form:
SEE ALSOgroff_out(5), troff(1).
This document was created by man2html, using the manual pages.
Time: 01:15:15 GMT, March 05, 2024