\n| <\/td>\n | \n hor<\/b> n<\/i><\/p>\n<\/td>\n | <\/td>\n | \n The horizontal resolution is n\u00a0<\/i>machine units.<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n<\/table>\n image_generator<\/b> string<\/i><\/p>\n Needed for grohtml<\/b> only. It specifies the program to generate PNG images from PostScript input. Under GNU\/Linux this is usually gs<\/i> but under other systems (notably cygwin) it might be set to another name.<\/p>\n paperlength<\/b> n<\/i><\/p>\n The physical vertical dimension of the output medium in machine units. This isn\u2019t used by troff<\/b> itself but by output devices. Deprecated. Use papersize<\/b> instead.<\/p>\n papersize<\/b> string<\/i><\/p>\n Select a paper size. Valid values for string<\/i> are the ISO paper types A0\u2013A7, B0\u2013B7, C0\u2013C7, D0\u2013D7, DL, and the US paper types letter, legal, tabloid, ledger, statement, executive, com10, and monarch. Case is not significant for string<\/i> if it holds predefined paper types. Alternatively, string<\/i> can be a file name (e.g. \/etc\/papersize<\/i>); if the file can be opened, groff<\/b> reads the first line and tests for the above paper sizes. Finally, string<\/i> can be a custom paper size in the format length<\/i>,<\/b>width<\/i> (no spaces before and after the comma). Both length<\/i> and width<\/i> must have a unit appended; valid values are \u2018i\u2019 for inches, \u2018c\u2019 for centimeters, \u2018p\u2019 for points, and \u2018P\u2019 for picas. Example: 12c,235p<\/b>. An argument which starts with a digit is always treated as a custom paper format. papersize<\/b> sets both the vertical and horizontal dimension of the output medium.<\/p>\n More than one argument can be specified; groff<\/b> scans from left to right and uses the first valid paper specification.<\/p>\n paperwidth<\/b> n<\/i><\/p>\n The physical horizontal dimension of the output medium in machine units. Deprecated. Use papersize<\/b> instead. This isn\u2019t used by troff<\/b> itself but by output devices.<\/p>\n pass_filenames<\/b><\/p>\n Make troff tell the driver the source file name being processed. This is achieved by another tcommand: F\u00a0<\/b>filename<\/i>.<\/p>\n postpro<\/b> program<\/i><\/p>\n Use program<\/i> as the postprocessor.<\/p>\n prepro<\/b> program<\/i><\/p>\n Call program<\/i> as a preprocessor.<\/p>\n print<\/b> program<\/i><\/p>\n Use program<\/i> as the spooler program for printing. If omitted, the \u2212l<\/b> and \u2212L<\/b> options of groff<\/b> are ignored.<\/p>\n\n\n| <\/td>\n | \n res<\/b> n<\/i><\/p>\n<\/td>\n | <\/td>\n | \n There are n<\/i> machine units per inch.<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n<\/table>\n sizes<\/b> s1 s2 … sn<\/i> 0<\/b><\/p>\n This means that the device has fonts at s1<\/i>, s2<\/i>, …, sn<\/i> scaled points. The list of sizes must be terminated by a 0<\/b>. Each si<\/i> can also be a range of sizes m<\/i>\u2013n<\/i>. The list can extend over more than one line.<\/p>\n sizescale<\/b> n<\/i><\/p>\n The scale factor for point sizes. By default this has a value of 1. One scaled point<\/i> is equal to one point\/n<\/i>. The arguments to the unitwidth<\/b> and sizes<\/b> commands are given in scaled points.<\/p>\n styles<\/b> S1 S2 … Sm<\/i><\/p>\n The first m<\/i> font positions are associated with styles S1<\/i>, …, Sm<\/i>.<\/p>\n tcommand<\/b><\/p>\n This means that the postprocessor can handle the t<\/b> and\u00a0u<\/b> output commands.<\/p>\n unicode<\/b><\/p>\n Indicate that the output device supports the complete Unicode repertoire. Useful only for devices which produce character entities<\/i> instead of glyphs.<\/p>\n If unicode<\/b> is present, no charset<\/b> section is required in the font description files since the Unicode handling built into groff<\/b> is used. However, if there are entries in a charset<\/b> section, they either override the default mappings for those particular characters or add new mappings (normally for composite characters).<\/p>\n This is used for \u2212Tutf8<\/b>, \u2212Thtml<\/b>, and \u2212Txhtml<\/b>.<\/p>\n unitwidth<\/b> n<\/i><\/p>\n Quantities in the font files are given in machine units for fonts whose point size is n\u00a0<\/i>scaled points.<\/p>\n unscaled_charwidths<\/b><\/p>\n Make the font handling module always return unscaled glyph widths. Needed for the grohtml<\/b> device.<\/p>\n use_charnames_in_special<\/b><\/p>\n This command indicates that troff should encode named glyphs inside special commands.<\/p>\n \n\n| <\/td>\n | \n vert<\/b> n<\/i><\/p>\n<\/td>\n | <\/td>\n | \n The vertical resolution is n\u00a0<\/i>machine units.<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n<\/table>\n The res<\/b>, unitwidth<\/b>, fonts<\/b>, and sizes<\/b> lines are compulsory. Not all commands in the DESC<\/i> file are used by troff<\/b> itself; some of the keywords (or even additional ones) are used by postprocessors to store arbitrary information about the device.<\/p>\n Here a list of obsolete keywords which are recognized by groff<\/b> but completely ignored: spare1<\/b>, spare2<\/b>, biggestfont<\/b>.<\/p>\n Font file format<\/b>
A font file has two sections; empty lines are ignored in both of them.<\/p>\n 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.
ligatures<\/b> lig1 lig2 … lign<\/i> [0<\/b>]<\/p>\n Glyphs lig1<\/i>, lig2<\/i>, …, lign<\/i> are ligatures; possible ligatures are ff<\/b>, fi<\/b>, fl<\/b>, ffi<\/b>, and ffl<\/b>. For backwards compatibility, the list of ligatures may be terminated with a\u00a00<\/b>. The list of ligatures may not extend over more than one line.<\/p>\n\n\n| <\/td>\n | \n name<\/b> F<\/i><\/p>\n<\/td>\n | <\/td>\n | \n The name of the font is\u00a0F<\/i>.<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n<\/table>\n slant<\/b> n<\/i><\/p>\n The glyphs of the font have a slant of n\u00a0<\/i>degrees. (Positive means forward.)<\/p>\n spacewidth<\/b> n<\/i><\/p>\n The normal width of a space is\u00a0n<\/i>.<\/p>\n special<\/b><\/p>\n The font is special<\/i>; this means that when a glyph is requested that is not present in the current font, it is searched for in any special fonts that are mounted.<\/p>\n Other commands are ignored by troff<\/b> but may be used by postprocessors to store arbitrary information about the font in the font file.<\/p>\n The first section can contain comments which start with the #<\/b> character and extend to the end of a line.<\/p>\n The second section contains one or two subsections. It must contain a charset<\/i> subsection and it may also contain a kernpairs<\/i> subsection. These subsections can appear in any order. Each subsection starts with a word on a line by itself.<\/p>\n The word charset<\/b> starts the charset subsection. The charset<\/b> line is followed by a sequence of lines. Each line gives information for one glyph. A line comprises a number of fields separated by blanks or tabs. The format is<\/p>\n name metrics type code<\/i> [entity_name<\/i>] [\u2212\u2212<\/b> comment<\/i>]<\/p>\n name<\/i> identifies the glyph: if name<\/i> is a single glyph c<\/i> then it corresponds to the groff input character c<\/i>; if it is of the form <\/b>c<\/i> where c is a single character, then it corresponds to the special character [<\/b>c<\/i>]<\/b>; otherwise it corresponds to the groff input character [<\/b>name<\/i>]<\/b>. If it is exactly two characters xx<\/i> it can be entered as (<\/b>xx<\/i>. Note that single-letter special characters can\u2019t be accessed as <\/b>c<\/i>; the only exception is \u2018\u2212\u2019 which is identical to \u2018[\u2212]\u2019. The name \u2212\u2212\u2212<\/b> is special and indicates that the glyph is unnamed; such glyphs can only be used by means of the N<\/b> escape sequence in troff<\/b>.<\/p>\n The type<\/i> field gives the glyph type:<\/p>\n\n\n| <\/td>\n | \n 1<\/p>\n<\/td>\n | <\/td>\n | \n means the glyph has a descender, for example, \u2018p\u2019;<\/p>\n<\/td>\n<\/tr>\n | \n| <\/td>\n | \n 2<\/p>\n<\/td>\n | <\/td>\n | \n means the glyph has an ascender, for example, \u2018b\u2019;<\/p>\n<\/td>\n<\/tr>\n | \n| <\/td>\n | \n 3<\/p>\n<\/td>\n | <\/td>\n | \n means the glyph has both an ascender and a descender, for example, \u2018(\u2019.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n The code<\/i> field gives the code which the postprocessor uses to print the glyph. The glyph can also be input to groff using this code by means of the N<\/b> escape sequence. The code can be any integer. If it starts with a\u00a00<\/b> it is interpreted as octal; if it starts with 0x<\/b> or 0X<\/b> it is interpreted as hexadecimal. Note, however, that the N<\/b> escape sequence only accepts a decimal integer.<\/p>\n The entity_name<\/i> field gives an ASCII string identifying the glyph which the postprocessor uses to print that glyph. This field is optional and is currently used by grops<\/b> to build sub-encoding arrays for PS fonts containing more than 256 glyphs. (It has also been used for grohtml<\/b>\u2019s entity names but for efficiency reasons this data is now compiled directly into grohtml<\/b>.)<\/p>\n Anything on the line after the encoding field or \u2018\u2212\u2212\u2019 are ignored.<\/p>\n The metrics<\/i> field has the form (in one line; it is broken here for the sake of readability):<\/p>\n width<\/i>[,<\/b>height<\/i>[,<\/b>depth<\/i>[,<\/b>italic-correction<\/i>
[,<\/b>left-italic-correction<\/i>[,<\/b>subscript-correction<\/i>]]]]]<\/p>\n There must not be any spaces between these subfields. Missing subfields are assumed to be\u00a00. 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<\/b> as they are in ditroff. The width<\/i> subfields gives the width of the glyph. The height<\/i> subfield gives the height of the glyph (upwards is positive); if a glyph does not extend above the baseline, it should be given a zero height, rather than a negative height. The depth<\/i> subfield gives the depth of the glyph, that is, the distance below the baseline to which the glyph extends (downwards is positive); if a glyph does not extend below the baseline, it should be given a zero depth, rather than a negative depth. The italic-correction<\/i> subfield gives the amount of space that should be added after the glyph when it is immediately to be followed by a glyph from a roman font. The left-italic-correction<\/i> subfield gives the amount of space that should be added before the glyph when it is immediately to be preceded by a glyph from a roman font. The subscript-correction<\/i> gives the amount of space that should be added after a glyph before adding a subscript. This should be less than the italic correction.<\/p>\n A line in the charset section can also have the format<\/p>\n name<\/i> “<\/b><\/p>\n This indicates that name<\/i> is just another name for the glyph mentioned in the preceding line.<\/p>\n The word kernpairs<\/b> starts the kernpairs section. This contains a sequence of lines of the form:<\/p>\n c1 c2 n<\/i><\/p>\n This means that when glyph c1<\/i> appears next to glyph c2<\/i> the space between them should be increased by\u00a0n<\/i>. Most entries in kernpairs section have a negative value for\u00a0n<\/i>.<\/p>\n | | | | |