1 .\" $Id: roff.7,v 1.4 2010/05/17 02:01:05 kristaps Exp $
3 .\" Copyright (c) 2010 Kristaps Dzonsons <kristaps@bsd.lv>
5 .\" Permission to use, copy, modify, and distribute this software for any
6 .\" purpose with or without fee is hereby granted, provided that the above
7 .\" copyright notice and this permission notice appear in all copies.
9 .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
10 .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
11 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
12 .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
13 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
14 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
15 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
17 .Dd $Mdocdate: May 17 2010 $
22 .Nd roff language reference
26 language is a general-purpose text-formatting language. The purpose of
27 this document is to consistently describe those language constructs
30 utility. It is a work in progress.
34 document follows simple rules: lines beginning with the control
39 are parsed for macros. Other lines are interpreted within the scope of
41 .Bd -literal -offset indent
42 \&.xx Macro lines change control state.
43 Other lines are interpreted within the current state.
47 documents may contain only graphable 7-bit ASCII characters, the space
48 character, and, in certain circumstances, the tab character. All
53 Macros are arbitrary in length and begin with a control character ,
57 at the beginning of the line.
58 An arbitrary amount of whitespace may sit between the control character
60 Thus, the following are equivalent:
61 .Bd -literal -offset indent
66 This section is a canonical reference of all macros, arranged
69 The syntax of this macro is the same as that of
71 except that a leading argument must be specified.
72 It is ignored, as are its children.
74 The syntax of this macro is the same as that of
76 except that a leading argument must be specified.
77 It is ignored, as are its children.
79 The syntax of this macro is the same as that of
81 except that a leading argument must be specified.
82 It is ignored, as are its children.
84 The syntax of this macro is the same as that of
86 except that a leading argument must be specified.
87 It is ignored, as are its children.
89 The syntax of this macro is the same as that of
91 except that a leading argument must be specified.
92 It is ignored, as are its children.
94 The syntax of this macro is the same as that of
96 except that a leading argument must be specified.
97 It is ignored, as are its children.
99 Begins a conditional that always evaluates to false.
100 If a conditional is false, its children are not processed, but are
101 syntactically interpreted to preserve the integrity of the input
109 which may lead to interesting results, but
111 .D1 \&.if t \e .if t \e{\e
113 will continue to syntactically interpret to the block close of the final
115 Sub-conditionals, in this case, obviously inherit the truth value of
117 This macro has the following syntax:
119 .Bd -literal -offset indent -compact
124 .Bd -literal -offset indent -compact
128 .Bd -literal -offset indent -compact
133 .Bd -literal -offset indent -compact
138 COND is a conditional (for the time being, this always evaluates to
141 If the BODY section is begun by an escaped brace
143 scope continues until a closing-brace macro
145 If the BODY is not enclosed in braces, scope continues until the next
147 If the COND is followed by a BODY on the same line, whether after a
148 brace or not, then macros
150 begin with a control character.
151 It is generally more intuitive, in this case, to write
152 .Bd -literal -offset indent
159 than having the macro follow as
161 .D1 \&.if COND \e{ .foo
163 The scope of a conditional is always parsed, but only executed if the
164 conditional evaluates to true.
166 Note that text subsequent a
169 Furthermore, if an explicit closing sequence
171 is specified in a free-form line, the entire line is accepted within the
172 scope of the prior macro, not only the text preceding the close.
175 Accepts the following syntax:
177 .Bd -literal -offset indent -compact
182 .Bd -literal -offset indent -compact
188 In the first case, input is ignored until a
190 macro is encountered on its own line.
191 In the second case, input is ignored until a
200 Do not use the escape
202 anywhere in the definition of END.
203 It causes very strange behaviour.
204 Furthermore, if you redefine a
210 the subsequent invocation of
212 will first signify the end of comment, then be invoked as a macro.
213 This behaviour really shouldn't be counted upon.
215 This section documents compatibility between mandoc and other other
216 troff implementations, at this time limited to GNU troff
220 refers to groff versions before the
223 .Pq somewhere between 1.15 and 1.19 .
227 Historic groff did not accept white-space buffering the custom END tag
234 and family would print funny white-spaces with historic groff when
235 depending on next-line syntax.
240 reference was written by
241 .An Kristaps Dzonsons Aq kristaps@bsd.lv .