1 .\" $Id: roff.7,v 1.52 2014/04/05 20:34:57 schwarze Exp $
3 .\" Copyright (c) 2010, 2011, 2012 Kristaps Dzonsons <kristaps@bsd.lv>
4 .\" Copyright (c) 2010, 2011, 2013, 2014 Ingo Schwarze <schwarze@openbsd.org>
6 .\" Permission to use, copy, modify, and distribute this software for any
7 .\" purpose with or without fee is hereby granted, provided that the above
8 .\" copyright notice and this permission notice appear in all copies.
10 .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
11 .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
12 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
13 .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
14 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
15 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
16 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
18 .Dd $Mdocdate: April 5 2014 $
23 .Nd roff language reference for mandoc
27 language is a general purpose text formatting language.
28 Since traditional implementations of the
32 manual formatting languages are based on it,
33 many real-world manuals use small numbers of
35 requests and escape sequences intermixed with their
40 To properly format such manuals, the
42 utility supports a tiny subset of
45 Only these requests and escapes supported by
47 are documented in the present manual,
48 together with the basic language syntax shared by
59 Input lines beginning with the control character
61 are parsed for requests and macros.
67 Requests change the processing state and manipulate the formatting;
68 some macros also define the document structure and produce formatted
72 is accepted as an alternative control character,
78 Lines not beginning with control characters are called
80 They provide free-form text to be printed; the formatting of the text
81 depends on the respective processing context.
84 documents may contain only graphable 7-bit ASCII characters, the space
85 character, and, in certain circumstances, the tab character.
86 The backslash character
88 indicates the start of an escape sequence, used for example for
90 .Sx Special Characters ,
91 .Sx Predefined Strings ,
93 user-defined strings defined using the
96 For a listing of escape sequences, consult the
97 .Sx ESCAPE SEQUENCE REFERENCE
100 Text following an escaped double-quote
102 whether in a request, macro, or text line, is ignored to the end of the line.
103 A request line beginning with a control character and comment escape
106 Furthermore, request lines with only a control character and optional
107 trailing whitespace are stripped from input.
110 .Bd -literal -offset indent -compact
111 \&.\e\(dq This is a comment line.
112 \&.\e\(dq The next line is ignored:
114 \&.Sh EXAMPLES \e\(dq This is a comment, too.
115 \&example text \e\(dq And so is this.
117 .Ss Special Characters
118 Special characters are used to encode special glyphs and are rendered
119 differently across output media.
120 They may occur in request, macro, and text lines.
121 Sequences begin with the escape character
123 followed by either an open-parenthesis
125 for two-character sequences; an open-bracket
127 for n-character sequences (terminated at a close-bracket
129 or a single one character sequence.
132 .Bl -tag -width Ds -offset indent -compact
134 Two-letter em dash escape.
136 One-letter backslash escape.
143 Terms may be text-decorated using the
145 escape followed by an indicator: B (bold), I (italic), R (regular), or P
146 (revert to previous mode).
147 A numerical representation 3, 2, or 1 (bold, italic, and regular,
148 respectively) may be used instead.
149 The indicator or numerical representative may be preceded by C
150 (constant-width), which is ignored.
152 The two-character indicator
154 requests a font that is both bold and italic.
155 It may not be portable to old roff implementations.
158 .Bl -tag -width Ds -offset indent -compact
160 Write in \fBbold\fP, then switch to regular font mode.
161 .It Li \efIitalic\efP
162 Write in \fIitalic\fP, then return to previous font mode.
163 .It Li \ef(BIbold italic\efP
164 Write in \f(BIbold italic\fP, then return to previous font mode.
171 which encourages semantic annotation.
172 .Ss Predefined Strings
173 Predefined strings, like
174 .Sx Special Characters ,
175 mark special output glyphs.
176 Predefined strings are escaped with the slash-asterisk,
186 .Bl -tag -width Ds -offset indent -compact
188 Two-letter ampersand predefined string.
190 One-letter double-quote predefined string.
193 Predefined strings are not recommended for use,
194 as they differ across implementations.
199 Manuals using these predefined strings are almost certainly not portable.
201 Whitespace consists of the space character.
202 In text lines, whitespace is preserved within a line.
203 In request and macro lines, whitespace delimits arguments and is discarded.
205 Unescaped trailing spaces are stripped from text line input unless in a
207 In general, trailing whitespace on any input line is discouraged for
208 reasons of portability.
209 In the rare case that a blank character is needed at the end of an
210 input line, it may be forced by
213 Literal space characters can be produced in the output
214 using escape sequences.
215 In macro lines, they can also be included in arguments using quotation; see
219 Blank text lines, which may include whitespace, are only permitted
220 within literal contexts.
221 If the first character of a text line is a space, that line is printed
222 with a leading newline.
224 Many requests and macros support scaled widths for their arguments.
225 The syntax for a scaled width is
226 .Sq Li [+-]?[0-9]*.[0-9]*[:unit:] ,
227 where a decimal must be preceded or followed by at least one digit.
228 Negative numbers, while accepted, are truncated to zero.
230 The following scaling units are accepted:
232 .Bl -tag -width Ds -offset indent -compact
245 default vertical span
257 default horizontal span
262 Using anything other than
268 is necessarily non-portable across output media.
272 If a scaling unit is not provided, the numerical value is interpreted
273 under the default rules of
275 for vertical spaces and
280 .Bl -tag -width ".Bl -tag -width 2i" -offset indent -compact
281 .It Li \&.Bl -tag -width 2i
282 two-inch tagged list indentation in
285 two-inch tagged list indentation in
291 Each sentence should terminate at the end of an input line.
292 By doing this, a formatter will be able to apply the proper amount of
293 spacing after the end of sentence (unescaped) period, exclamation mark,
294 or question mark followed by zero or more non-sentence closing
303 The proper spacing is also intelligently preserved if a sentence ends at
304 the boundary of a macro line.
307 .Bd -literal -offset indent -compact
308 Do not end sentences mid-line like this. Instead,
309 end a sentence like this.
310 A macro would end like this:
314 A request or macro line consists of:
318 the control character
322 at the beginning of the line,
324 optionally an arbitrary amount of whitespace,
326 the name of the request or the macro, which is one word of arbitrary
327 length, terminated by whitespace,
329 and zero or more arguments delimited by whitespace.
332 Thus, the following request lines are all equivalent:
333 .Bd -literal -offset indent
339 Macros are provided by the
343 languages and can be defined by the
346 When called, they follow the same syntax as requests, except that
347 macro arguments may optionally be quoted by enclosing them
348 in double quote characters
350 Quoted text, even if it contains whitespace or would cause
351 a macro invocation when unquoted, is always considered literal text.
352 Inside quoted text, pairs of double quote characters
354 resolve to single double quote characters.
356 To be recognised as the beginning of a quoted argument, the opening
357 quote character must be preceded by a space character.
358 A quoted argument extends to the next double quote character that is not
359 part of a pair, or to the end of the input line, whichever comes earlier.
360 Leaving out the terminating double quote character at the end of the line
362 For clarity, if more arguments follow on the same input line,
363 it is recommended to follow the terminating double quote character
364 by a space character; in case the next character after the terminating
365 double quote character is anything else, it is regarded as the beginning
366 of the next, unquoted argument.
368 Both in quoted and unquoted arguments, pairs of backslashes
370 resolve to single backslashes.
371 In unquoted arguments, space characters can alternatively be included
372 by preceding them with a backslash
374 but quoting is usually better for clarity.
377 .Bl -tag -width Ds -offset indent -compact
378 .It Li .Fn strlen \(dqconst char *s\(dq
381 into one function argument.
387 would be considered separate arguments.
388 .It Li .Op \(dqFl a\(dq
391 as literal text instead of a flag macro.
393 .Sh REQUEST REFERENCE
397 parser recognises the following requests.
400 language defines many more requests not implemented in
403 Set line adjustment mode.
404 This line-scoped request is intended to have one argument to select
405 normal, left, right, or centre adjustment for subsequent text.
406 Currently, it is ignored including its arguments,
407 and the number of arguments is not checked.
409 Append to a macro definition.
410 The syntax of this request is the same as that of
412 It is currently ignored by
416 Append to a macro definition, specifying the macro name indirectly.
417 The syntax of this request is the same as that of
419 It is currently ignored by
423 Append to a macro definition, switching roff compatibility mode off
424 during macro execution.
425 The syntax of this request is the same as that of
427 It is currently ignored by
431 Append to a user-defined string.
432 The syntax of this request is the same as that of
434 If a user-defined string with the specified name does not yet exist,
435 it is set to the empty string before appending.
437 Changes the control character.
438 Its syntax is as follows:
439 .Bd -literal -offset indent
440 .Pf . Cm \&cc Op Ar c
445 is not specified, the control character is reset to
447 Trailing characters are ignored.
450 This line-scoped request is intended to take one integer argument,
451 specifying how many lines to center.
452 Currently, it is ignored including its arguments, and the number
453 of arguments is not checked.
458 Its syntax can be either
459 .Bd -literal -offset indent
460 .Pf . Cm \&de Ar name
466 .Bd -literal -offset indent
467 .Pf . Cm \&de Ar name Ar end
472 Both forms define or redefine the macro
475 .Ar macro definition ,
476 which may consist of one or more input lines, including the newline
477 characters terminating each line, optionally containing calls to
481 macros or high-level macros like
485 macros, whichever applies to the document in question.
489 macro works in the same way as for
494 .Ar macro definition ,
495 and after that, it is also evaluated as a
499 macro, but not as a high-level macro.
501 The macro can be invoked later using the syntax
503 .D1 Pf . Ar name Op Ar argument Op Ar argument ...
505 Regarding argument parsing, see
509 The line invoking the macro will be replaced
510 in the input stream by the
511 .Ar macro definition ,
512 replacing all occurrences of
517 .Ar N Ns th Ar argument .
519 .Bd -literal -offset indent
521 \efI\e^\e\e$1\e^\efP\e\e$2
528 .D1 \efI\e^XtFree\e^\efP.
530 in the input stream, and thus in the output: \fI\^XtFree\^\fP.
532 Since macros and user-defined strings share a common string table,
535 clobbers the user-defined string
539 can also be printed using the
541 string interpolation syntax described below
543 but this is rarely useful because every macro definition contains at least
544 one explicit newline character.
546 In order to prevent endless recursion, both groff and
548 limit the stack depth for expanding macros and strings
549 to a large, but finite number.
550 Do not rely on the exact value of this limit.
554 macro, specifying the macro name indirectly.
555 The syntax of this request is the same as that of
557 It is currently ignored by
563 macro that will be executed with
565 compatibility mode switched off during macro execution.
566 This is a GNU extension not available in traditional
568 implementations and not even in older versions of groff.
573 compatibility mode at all, it handles this request as an alias for
576 Define a user-defined string.
577 Its syntax is as follows:
579 .D1 Pf . Cm \&ds Ar name Oo \(dq Oc Ns Ar string
585 arguments are space-separated.
588 begins with a double-quote character, that character will not be part
590 All remaining characters on the input line form the
592 including whitespace and double-quote characters, even trailing ones.
596 can be interpolated into subsequent text by using
597 .No \e* Ns Bq Ar name
600 of arbitrary length, or \e*(NN or \e*N if the length of
602 is two or one characters, respectively.
603 Interpolation can be prevented by escaping the leading backslash;
604 that is, an asterisk preceded by an even number of backslashes
605 does not trigger string interpolation.
607 Since user-defined strings and macros share a common string table,
614 used for defining a string can also be invoked as a macro,
615 in which case the following input line will be appended to the
617 forming a new input line passed to the
621 .Bd -literal -offset indent
632 Such abuse is of course strongly discouraged.
636 half of an if/else conditional.
637 Pops a result off the stack of conditional evaluations pushed by
639 and uses it as its conditional.
640 If no stack entries are present (e.g., due to no prior
643 then false is assumed.
644 The syntax of this request is similar to
646 except that the conditional is missing.
648 End an equation block.
652 Begin an equation block.
655 for a description of the equation language.
657 Change the font family.
658 This line-scoped request is intended to have one argument specifying
659 the font family to be selected.
660 It is a groff extension, and currently, it is ignored including its
661 arguments, and the number of arguments is not checked.
664 Its syntax is as follows:
666 .D1 Pf . Cm \&ft Op Ar font
670 arguments are supported:
671 .Bl -tag -width 4n -offset indent
672 .It Cm B , BI , 3 , 4
681 switches to normal font
682 .It Cm P No "or no argument"
683 switches back to the previous font
686 This request takes effect only locally, may be overridden by macros
687 and escape sequences, and is only supported in
691 Specify hyphenation points in words.
692 This line-scoped request is currently ignored.
694 Set automatic hyphenation mode.
695 This line-scoped request is currently ignored.
699 half of an if/else conditional.
700 The result of the conditional is pushed into a stack used by subsequent
703 which may be separated by any intervening input (or not exist at all).
704 Its syntax is equivalent to
707 Begins a conditional.
708 This request has the following syntax:
709 .Bd -literal -offset indent
712 .Bd -literal -offset indent
716 .Bd -literal -offset indent
722 COND is a conditional statement.
725 supports the following subset of roff conditionals:
730 is prefixed to COND, the condition is logically inverted.
732 If the first character of COND is
738 COND evaluates to true.
740 If the first character of COND is
742 .Pq character available ,
748 .Pq register accessed ,
752 COND evaluates to false.
754 If COND starts with a digit, optionally prefixed by a minus sign,
755 it is evaluated as a numerical expression of the form
756 .Ar number operator number ,
767 Otherwise, the first character of COND is regarded as a delimiter
768 and COND evaluates to true if the string extending from its first
769 to its second occurrence is equal to the string extending from its
770 second to its third occurrence.
772 If COND cannot be parsed, it evaluates to false.
775 If a conditional is false, its children are not processed, but are
776 syntactically interpreted to preserve the integrity of the input
784 which may lead to interesting results, but
786 .D1 \&.if t .if t \e{\e
788 will continue to syntactically interpret to the block close of the final
790 Sub-conditionals, in this case, obviously inherit the truth value of
793 If the BODY section is begun by an escaped brace
795 scope continues until the end of the input line containing the
796 matching closing-brace escape sequence
798 If the BODY is not enclosed in braces, scope continues until
800 If the COND is followed by a BODY on the same line, whether after a
801 brace or not, then requests and macros
803 begin with a control character.
804 It is generally more intuitive, in this case, to write
805 .Bd -literal -offset indent
812 than having the request or macro follow as
814 .D1 \&.if COND \e{ .foo
816 The scope of a conditional is always parsed, but only executed if the
817 conditional evaluates to true.
821 is converted into a zero-width escape sequence if not passed as a
830 being considered an argument of the
835 Its syntax can be either
836 .Bd -literal -offset indent
843 .Bd -literal -offset indent
849 In the first case, input is ignored until a
851 request is encountered on its own line.
852 In the second case, input is ignored until the specified
854 macro is encountered.
855 Do not use the escape character
857 anywhere in the definition of
859 it would cause very strange behaviour.
863 macro is a roff request or a roff macro, like in
867 the subsequent invocation of
869 will first terminate the
871 then be invoked as usual.
872 Otherwise, it only terminates the
874 and arguments following it or the
876 request are discarded.
878 Change the output line length.
879 Its syntax is as follows:
881 .D1 Pf . Cm \&ll Op Oo +|- Oc Ns Ar width
885 argument is omitted, the line length is reset to its previous value.
886 The default setting for terminal output is 78n.
887 If a sign is given, the line length is added to or subtracted from;
888 otherwise, it is set to the provided value.
889 Using this request in new manuals is discouraged for several reasons,
890 among others because it overrides the
895 Declare the need for the specified minimum vertical space
896 before the next trap or the bottom of the page.
897 This line-scoped request is currently ignored.
899 Turn off automatic hyphenation mode.
900 This line-scoped request is currently ignored.
902 Define or change a register.
903 A register is an arbitrary string value that defines some sort of state,
904 which influences parsing and/or formatting.
905 Its syntax is as follows:
907 .D1 Pf \. Cm \&nr Ar name Oo +|- Oc Ns Ar value
911 may, at the moment, only be an integer.
912 If it is prefixed by a sign, the register will be
913 incremented or decremented instead of assigned to.
915 The following register
917 is handled specially:
920 If set to a positive integer value, certain
922 macros will behave in the same way as in the
925 If set to 0, these macros will behave in the same way as outside the
927 section, even when called within the
930 Note that starting a new
934 macro will reset this register.
937 Turn on no-space mode.
938 This line-scoped request is intended to take no arguments.
939 Currently, it is ignored including its arguments,
940 and the number of arguments is not checked.
943 This line-scoped request is intended to take one numerical argument.
944 Currently, it is ignored including its arguments,
945 and the number of arguments is not checked.
947 Remove a request, macro or string.
948 Its syntax is as follows:
950 .D1 Pf \. Cm \&rm Ar name
953 Its syntax is as follows:
955 .D1 Pf \. Cm \&rr Ar name
957 Include a source file.
958 Its syntax is as follows:
960 .D1 Pf \. Cm \&so Ar file
964 will be read and its contents processed as input in place of the
967 To avoid inadvertent inclusion of unrelated files,
969 only accepts relative paths not containing the strings
974 This request requires
976 to change to the right directory before calling
978 per convention to the root of the manual tree.
979 Typical usage looks like:
981 .Dl \&.so man3/Xcursor.3
983 As the whole concept is rather fragile, the use of
991 This line-scoped request can take an arbitrary number of arguments.
992 Currently, it is ignored including its arguments.
994 Output character translation.
995 Its syntax is as follows:
997 .D1 Pf \. Cm \&tr Ar [ab]+
1001 characters are replaced
1005 Replacement (or origin) characters may also be character escapes; thus,
1009 replaces all invocations of \e(xx with \e(yy.
1011 Re-start a table layout, retaining the options of the prior table
1016 End a table context.
1020 Begin a table, which formats input in aligned rows and columns.
1023 for a description of the tbl language.
1024 .Sh ESCAPE SEQUENCE REFERENCE
1028 parser recognises the following escape sequences.
1031 language defines more escape sequences not implemented in
1037 documents, using escape sequences is discouraged except for those
1042 A backslash followed by any character not listed here
1043 simply prints that character itself.
1045 A backslash at the end of an input line can be used to continue the
1046 logical input line on the next physical input line, joining the text
1047 on both lines together as if it were on a single input line.
1049 The escape sequence backslash-space
1051 is an unpaddable space-sized non-breaking space character; see
1054 The rest of the input line is treated as
1057 Hyphenation allowed at this point of the word; ignored by
1060 Non-printing zero-width character; see
1063 Acute accent special character; use
1067 .Sx Special Characters
1068 with two-letter names, see
1070 .Ss \e*[ Ns Ar name ]
1071 Interpolate the string with the
1074 .Sx Predefined Strings
1077 For short names, there are variants
1083 .Dq mathematical minus sign .
1084 .Ss \e[ Ns Ar name ]
1085 .Sx Special Characters
1086 with names of arbitrary length, see
1089 One-twelfth em half-narrow space character, effectively zero-width in
1092 Grave accent special character; use
1096 Begin conditional input; see
1099 One-sixth em narrow space character, effectively zero-width in
1102 End conditional input; see
1105 Paddable non-breaking space character.
1107 Digit width space character.
1108 .Ss \eA\(aq Ns Ar string Ns \(aq
1109 Anchor definition; ignored by
1111 .Ss \eB\(aq Ns Ar string Ns \(aq
1114 is a numerical expession; ignored by
1116 .Ss \eb\(aq Ns Ar string Ns \(aq
1117 Bracket building function; ignored by
1119 .Ss \eC\(aq Ns Ar name Ns \(aq
1120 .Sx Special Characters
1121 with names of arbitrary length.
1123 Interrupt text processing to insert requests or macros; ignored by
1125 .Ss \eD\(aq Ns Ar string Ns \(aq
1126 Draw graphics function; ignored by
1129 Move down by half a line; ignored by
1132 Backslash special character.
1133 .Ss \eF[ Ns Ar name ]
1134 Switch font family (groff extension); ignored by
1136 For short names, there are variants
1140 .Ss \ef[ Ns Ar name ]
1144 .Sx Text Decoration .
1145 For short names, there are variants
1149 .Ss \eg[ Ns Ar name ]
1150 Interpolate the format of a number register; ignored by
1152 For short names, there are variants
1156 .Ss \eH\(aq Ns Oo +|- Oc Ns Ar number Ns \(aq
1157 Set the height of the current font; ignored by
1159 .Ss \eh\(aq Ns Ar number Ns \(aq
1160 Horizontal motion; ignored by
1162 .Ss \ek[ Ns Ar name ]
1163 Mark horizontal input place in register; ignored by
1165 For short names, there are variants
1169 .Ss \eL\(aq Ns Ar number Ns Oo Ar c Oc Ns \(aq
1170 Vertical line drawing function; ignored by
1172 .Ss \el\(aq Ns Ar number Ns Oo Ar c Oc Ns \(aq
1173 Horizontal line drawing function; ignored by
1175 .Ss \eM[ Ns Ar name ]
1176 Set fill (background) color (groff extension); ignored by
1178 For short names, there are variants
1182 .Ss \em[ Ns Ar name ]
1183 Set glyph drawing color (groff extension); ignored by
1185 For short names, there are variants
1189 .Ss \eN\(aq Ns Ar number Ns \(aq
1192 on the current font.
1193 .Ss \en[ Ns Ar name ]
1194 Interpolate the number register
1196 For short names, there are variants
1200 .Ss \eo\(aq Ns Ar string Ns \(aq
1205 .Ss \eR\(aq Ns Ar name Oo +|- Oc Ns Ar number Ns \(aq
1206 Set number register; ignored by
1208 .Ss \eS\(aq Ns Ar number Ns \(aq
1209 Slant output; ignored by
1211 .Ss \es\(aq Ns Oo +|- Oc Ns Ar number Ns \(aq
1212 Change point size; ignored by
1215 .No \es Ns Oo +|- Oc Ns Ar n ,
1216 .No \es Ns Oo +|- Oc Ns \(aq Ns Ar number Ns \(aq ,
1217 .No \es Ns [ Oo +|- Oc Ns Ar number ] ,
1219 .No \es Ns Oo +|- Oc Ns [ Ar number Ns ]
1220 are also parsed and ignored.
1222 Horizontal tab; ignored by
1225 Move up by half a line; ignored by
1227 .Ss \eV[ Ns Ar name ]
1228 Interpolate an environment variable; ignored by
1230 For short names, there are variants
1234 .Ss \ev\(aq Ns Ar number Ns \(aq
1235 Vertical motion; ignored by
1237 .Ss \ew\(aq Ns Ar string Ns \(aq
1238 Interpolate the width of the
1242 .Ss \eX\(aq Ns Ar string Ns \(aq
1245 as device control function; ignored in nroff mode and by
1247 .Ss \ex\(aq Ns Ar number Ns \(aq
1248 Extra line space function; ignored by
1250 .Ss \eY[ Ns Ar name ]
1251 Output a string as a device control function; ignored in nroff mode and by
1253 For short names, there are variants
1257 .Ss \eZ\(aq Ns Ar string Ns \(aq
1260 with zero width and height; ignored by
1263 Output the next character without advancing the cursor position;
1266 by simply skipping the next character.
1268 This section documents compatibility between mandoc and other
1270 implementations, at this time limited to GNU troff
1274 refers to groff version 1.15.
1284 macros are considered regular macros.
1287 implementations, these are special macros that must be specified without
1288 spacing between the control character (which must be a period) and the
1293 register is only compatible with OpenBSD's groff-1.15.
1295 Historic groff did not accept white-space before a custom
1303 and family would print funny white-spaces with historic groff when
1304 using the next-line syntax.
1314 .%A Joseph F. Ossanna
1315 .%A Brian W. Kernighan
1316 .%I AT&T Bell Laboratories
1317 .%T Troff User's Manual
1318 .%R Computing Science Technical Report
1320 .%C Murray Hill, New Jersey
1322 .%U http://www.kohala.com/start/troff/cstr54.ps
1325 .%A Joseph F. Ossanna
1326 .%A Brian W. Kernighan
1328 .%T Heirloom Documentation Tools Nroff/Troff User's Manual
1329 .%D September 17, 2007
1330 .%U http://heirloom.sourceforge.net/doctools/troff.pdf
1333 The RUNOFF typesetting system, whose input forms the basis for
1335 was written in MAD and FAP for the CTSS operating system by Jerome E.
1337 Doug McIlroy rewrote it in BCPL in 1969, renaming it
1339 Dennis M. Ritchie rewrote McIlroy's
1341 in PDP-11 assembly for
1343 Joseph F. Ossanna improved roff and renamed it nroff
1346 then ported nroff to C as troff, which Brian W. Kernighan released with
1348 In 1989, James Clarke re-implemented troff in C++, naming it groff.
1353 reference was written by
1354 .An Kristaps Dzonsons Aq Mt kristaps@bsd.lv
1356 .An Ingo Schwarze Aq Mt schwarze@openbsd.org .