[Contents][Index]


Footnotes

(1)

What You See Is What You Get

(2)

Jerome H. Saltzer, a grad student then, later a Professor of Electrical Engineering, now retired. Saltzer’s PhD thesis was the first application for RUNOFF and is available from the MIT Libraries.

(3)

The same is true for the other main macro packages that come with groff: man, mdoc, ms, mm, and mandoc. This won’t work in general; for example, to load trace.tmac, either ‘-mtrace’ or ‘-m trace must be used.

(4)

This section is derived from Writing Papers with nroff using -me by Eric P. Allman.

(5)

If you need finer granularity of the vertical space, use the pvs request (see Changing Type Sizes).

(6)

Note that the use of a ‘.ll length’ request to initialize the line length, prior to use of the ‘TH’ macro, is supported for backward compatibility with some versions of the man program. Always use the -rLL=length option, or an equivalent ‘.nr LL length’ request, in preference to such a ‘.ll length’ request. In particular, note that in nroff mode, the request ‘.ll 65n’, (with any length expression that evaluates equal to 65n, i.e., the formatter’s default line length in nroff mode), does not set the line length to 65n (it is adjusted to the man macro package’s default setting of 78n), whereas the use of the -rLL=65n option, or the ‘.nr LL 65n’ request does establish a line length of 65n.

(7)

Actually, only the title is required.

(8)

For an explanation what special characters are see Special Characters.

(9)

those that specify vertical or horizontal motion or a type size

(10)

Note that, for example, ‘!(-1)’ evaluates to ‘true’ because gtroff treats both negative numbers and zero as ‘false’.

(11)

Plan 9’s troff implementation also allows tabs for argument separation – gtroff intentionally doesn’t support this.

(12)

The last solution, i.e., using escaped spaces, is “classical” in the sense that it can be found in most troff documents. Nevertheless, it is not optimal in all situations, since ‘ inserts a fixed-width, non-breaking space character that can’t stretch. gtroff provides a different command \~ to insert a stretchable, non-breaking space.

(13)

Unfortunately, this is a lie. But hopefully future gtroff hackers will believe it :-)

(14)

Soft hyphen character is a misnomer since it is an output glyph.

(15)

Tab repetition character is a misnomer since it is an output glyph.

(16)

Leader repetition character is a misnomer since it is an output glyph.

(17)

Note that a one-character symbol is not the same as an input character, i.e., the character a is not the same as \[a]. By default, groff defines only a single one-character symbol, \[-]; it is usually accessed as \-. On the other hand, gtroff has the special feature that \[charXXX] is the same as the input character with character code XXX. For example, \[char97] is identical to the letter a if ASCII encoding is active.

(18)

\C is actually a misnomer since it accesses an output glyph.

(19)

Note that the output glyphs themselves don’t have such properties. For gtroff, a glyph is a numbered box with a given width, depth, and height, nothing else. All manipulations with the cflags request work on the input level.

(20)

char is a misnomer since an output glyph is defined.

(21)

This is usually the parenthesis. Note that in most cases the real dimensions of the glyphs in a font are not related to its type size! For example, the standard POSTSCRIPT font families ‘Times Roman’, ‘Helvetica’, and ‘Courier’ can’t be used together at 10pt; to get acceptable output, the size of ‘Helvetica’ has to be reduced by one point, and the size of ‘Courier’ must be increased by one point.

(22)

The created output nodes must be identical. See Gtroff Internals.

(23)

The name of this conditional operator is a misnomer since it tests names of output glyphs.

(24)

While it is possible to define and call a macro ‘.’ with

.de .
.  tm foo
..
.
..    \" This calls macro `.'!

you can’t use this as the end-of-macro macro: during a macro definition, ‘..’ is never handled as a call to ‘.’, even if you say ‘.de foo .’ explicitly.

(25)

Margin character is a misnomer since it is an output glyph.

(26)

Except the escapes \f, \F, \H, \m, \M, \R, \s, and \S, which are processed immediately if not in copy-in mode.

(27)

char is a misnomer since it reports missing glyphs – there aren’t missing input characters, only invalid ones.

(28)

To be completely independent of the current escape character, use \(rs, which represents a reverse solidus (backslash) glyph.

(29)

The parser and postprocessor for intermediate output can be found in the file
groff-source-dir/src/libs/libdriver/input.cpp.

(30)

c’ is actually a misnomer since it outputs a glyph.

(31)

Plan 9 troff has also abandoned the binary format.

(32)

This keyword is misnamed since it starts a list of ordered glyphs, not characters.

(33)

The distinction between input, characters, and output, glyphs, is not clearly separated in the terminology of groff; for example, the char request should be called glyph since it defines an output entity.


  [Contents][Index]