1 .\" $Id: roff.7,v 1.8 2010/06/01 11:54:23 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: June 1 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.
95 This macro is intended to have two arguments,
96 the name of the string to define and its content.
97 Currently, it is ignored including its arguments,
98 and the number of arguments is not checked.
100 The syntax of this macro is the same as that of
102 except that a leading argument must be specified.
103 It is ignored, as are its children.
107 half of an if/else conditional.
108 Pops a result off the stack of conditional evaluations pushed by
110 and uses it as its conditional.
111 If no stack entries are present (e.g., due to no prior
114 then false is assumed.
115 The syntax of this macro is similar to
117 except that the conditional is missing.
121 half of an if/else conditional.
122 The result of the conditional is pushed into a stack used by subsequent
125 which may be separated by any intervening input (or not exist at all).
126 Its syntax is equivalent to
129 Begins a conditional.
130 Right now, the conditional evaluates to true
131 if and only if it starts with the letter
133 indicating processing in
138 If a conditional is false, its children are not processed, but are
139 syntactically interpreted to preserve the integrity of the input
147 which may lead to interesting results, but
149 .D1 \&.if t \e .if t \e{\e
151 will continue to syntactically interpret to the block close of the final
153 Sub-conditionals, in this case, obviously inherit the truth value of
155 This macro has the following syntax:
157 .Bd -literal -offset indent -compact
162 .Bd -literal -offset indent -compact
166 .Bd -literal -offset indent -compact
171 .Bd -literal -offset indent -compact
176 COND is a conditional (for the time being, this always evaluates to
179 If the BODY section is begun by an escaped brace
181 scope continues until a closing-brace macro
183 If the BODY is not enclosed in braces, scope continues until the next
185 If the COND is followed by a BODY on the same line, whether after a
186 brace or not, then macros
188 begin with a control character.
189 It is generally more intuitive, in this case, to write
190 .Bd -literal -offset indent
197 than having the macro follow as
199 .D1 \&.if COND \e{ .foo
201 The scope of a conditional is always parsed, but only executed if the
202 conditional evaluates to true.
204 Note that text subsequent a
207 Furthermore, if an explicit closing sequence
209 is specified in a free-form line, the entire line is accepted within the
210 scope of the prior macro, not only the text preceding the close, with the
212 collapsing into a zero-width space.
215 Accepts the following syntax:
217 .Bd -literal -offset indent -compact
222 .Bd -literal -offset indent -compact
228 In the first case, input is ignored until a
230 macro is encountered on its own line.
231 In the second case, input is ignored until a
240 Do not use the escape
242 anywhere in the definition of END.
243 It causes very strange behaviour.
244 Furthermore, if you redefine a
250 the subsequent invocation of
252 will first signify the end of comment, then be invoked as a macro.
253 This behaviour really shouldn't be counted upon.
255 Remove a request, macro or string.
256 This macro is intended to have one argument,
257 the name of the request, macro or string to be undefined.
258 Currently, it is ignored including its arguments,
259 and the number of arguments is not checked.
261 Output character translation.
262 This macro is intended to have one argument,
263 consisting of an even number of characters.
264 Currently, it is ignored including its arguments,
265 and the number of arguments is not checked.
267 This section documents compatibility between mandoc and other other
268 troff implementations, at this time limited to GNU troff
272 refers to groff versions before the
275 .Pq somewhere between 1.15 and 1.19 .
279 Historic groff did not accept white-space buffering the custom END tag
286 and family would print funny white-spaces with historic groff when
287 depending on next-line syntax.
292 reference was written by
293 .An Kristaps Dzonsons Aq kristaps@bsd.lv .