xref: /openbsd-src/share/man/man7/man.7 (revision b058e777acbf34e2fc7e3eb7c4d67c742d4c66ae)
1.\"	$OpenBSD: man.7,v 1.17 2011/03/07 01:35:33 schwarze Exp $
2.\"
3.\" Copyright (c) 2009, 2010 Kristaps Dzonsons <kristaps@bsd.lv>
4.\"
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.
8.\"
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.
16.\"
17.Dd $Mdocdate: March 7 2011 $
18.Dt MAN 7
19.Os
20.Sh NAME
21.Nm man
22.Nd man language reference
23.Sh DESCRIPTION
24The
25.Nm man
26language was historically used to format
27.Ux
28manuals.
29This reference document describes its syntax, structure, and usage.
30.Pp
31.Bf -emphasis
32Do not use
33.Nm
34to write your manuals.
35.Ef
36Use the
37.Xr mdoc 7
38language, instead.
39.Pp
40A
41.Nm
42document follows simple rules:  lines beginning with the control
43character
44.Sq \&.
45are parsed for macros.
46Other lines are interpreted within the scope of
47prior macros:
48.Bd -literal -offset indent
49\&.SH Macro lines change control state.
50Other lines are interpreted within the current state.
51.Ed
52.Sh INPUT ENCODING
53.Nm
54documents may contain only graphable 7-bit ASCII characters, the
55space character, and the tab character.
56.Pp
57Blank lines are acceptable; where found, the output will assert a
58vertical space.
59.Pp
60If the first character of a line is a space, that line is printed
61with a leading newline.
62.Ss Comments
63Text following a
64.Sq \e\*q ,
65whether in a macro or free-form text line, is ignored to the end of
66line.
67A macro line with only a control character and comment escape,
68.Sq \&.\e\*q ,
69is also ignored.
70Macro lines with only a control character and optionally whitespace are
71stripped from input.
72.Ss Special Characters
73Special characters may occur in both macro and free-form lines.
74Sequences begin with the escape character
75.Sq \e
76followed by either an open-parenthesis
77.Sq \&(
78for two-character sequences; an open-bracket
79.Sq \&[
80for n-character sequences (terminated at a close-bracket
81.Sq \&] ) ;
82or a single one-character sequence.
83See
84.Xr mandoc_char 7
85for a complete list.
86Examples include
87.Sq \e(em
88.Pq em-dash
89and
90.Sq \ee
91.Pq back-slash .
92.Ss Text Decoration
93Terms may be text-decorated using the
94.Sq \ef
95escape followed by an indicator: B (bold), I (italic), R (Roman), or P
96(revert to previous mode):
97.Pp
98.D1 \efBbold\efR \efIitalic\efP
99.Pp
100A numerical representation 3, 2, or 1 (bold, italic, and Roman,
101respectively) may be used instead.
102A text decoration is only valid, if specified in free-form text, until
103the next macro invocation; if specified within a macro, it's only valid
104until the macro closes scope.
105Note that macros like
106.Sx \&BR
107open and close a font scope with each argument.
108.Pp
109The
110.Sq \ef
111attribute is forgotten when entering or exiting a macro block.
112.Ss Whitespace
113Whitespace consists of the space character.
114In free-form lines, whitespace is preserved within a line; unescaped
115trailing spaces are stripped from input (unless in a literal context).
116Blank free-form lines, which may include spaces, are permitted and
117rendered as an empty line.
118.Pp
119In macro lines, whitespace delimits arguments and is discarded.
120If arguments are quoted, whitespace within the quotes is retained.
121.Ss Scaling Widths
122Many macros support scaled widths for their arguments, such as
123stipulating a two-inch paragraph indentation with the following:
124.Bd -literal -offset indent
125\&.HP 2i
126.Ed
127.Pp
128The syntax for scaled widths is
129.Sq Li [+-]?[0-9]*.[0-9]*[:unit:]? ,
130where a decimal must be preceded or proceeded by at least one digit.
131Negative numbers, while accepted, are truncated to zero.
132The following scaling units are accepted:
133.Pp
134.Bl -tag -width Ds -offset indent -compact
135.It c
136centimetre
137.It i
138inch
139.It P
140pica (~1/6 inch)
141.It p
142point (~1/72 inch)
143.It f
144synonym for
145.Sq u
146.It v
147default vertical span
148.It m
149width of rendered
150.Sq m
151.Pq em
152character
153.It n
154width of rendered
155.Sq n
156.Pq en
157character
158.It u
159default horizontal span
160.It M
161mini-em (~1/100 em)
162.El
163.Pp
164Using anything other than
165.Sq m ,
166.Sq n ,
167.Sq u ,
168or
169.Sq v
170is necessarily non-portable across output media.
171.Pp
172If a scaling unit is not provided, the numerical value is interpreted
173under the default rules of
174.Sq v
175for vertical spaces and
176.Sq u
177for horizontal ones.
178.Em Note :
179this differs from
180.Xr mdoc 7 ,
181which, if a unit is not provided, will instead interpret the string as
182literal text.
183.Ss Sentence Spacing
184When composing a manual, make sure that sentences end at the end of
185a line.
186By doing so, front-ends will be able to apply the proper amount of
187spacing after the end of sentence (unescaped) period, exclamation mark,
188or question mark followed by zero or more non-sentence closing
189delimiters
190.Po
191.Sq \&) ,
192.Sq \&] ,
193.Sq \&' ,
194.Sq \&"
195.Pc .
196.Sh MANUAL STRUCTURE
197Each
198.Nm
199document must contain the
200.Sx \&TH
201macro describing the document's section and title.
202It may occur anywhere in the document, although conventionally it
203appears as the first macro.
204.Pp
205Beyond
206.Sx \&TH ,
207at least one macro or text node must appear in the document.
208Documents are generally structured as follows:
209.Bd -literal -offset indent
210\&.TH FOO 1 2009-10-10
211\&.SH NAME
212\efBfoo\efR \e(en a description goes here
213\&.\e\*q .SH LIBRARY
214\&.\e\*q For sections 2 & 3 only.
215\&.\e\*q Not used in OpenBSD.
216\&.SH SYNOPSIS
217\efBfoo\efR [\efB\e-options\efR] arguments...
218\&.SH DESCRIPTION
219The \efBfoo\efR utility processes files...
220\&.\e\*q .SH IMPLEMENTATION NOTES
221\&.\e\*q Not used in OpenBSD.
222\&.\e\*q .SH RETURN VALUES
223\&.\e\*q For sections 2, 3, & 9 only.
224\&.\e\*q .SH ENVIRONMENT
225\&.\e\*q For sections 1, 6, 7, & 8 only.
226\&.\e\*q .SH FILES
227\&.\e\*q .SH EXIT STATUS
228\&.\e\*q For sections 1, 6, & 8 only.
229\&.\e\*q .SH EXAMPLES
230\&.\e\*q .SH DIAGNOSTICS
231\&.\e\*q For sections 1, 4, 6, 7, & 8 only.
232\&.\e\*q .SH ERRORS
233\&.\e\*q For sections 2, 3, & 9 only.
234\&.\e\*q .SH SEE ALSO
235\&.\e\*q .BR foo ( 1 )
236\&.\e\*q .SH STANDARDS
237\&.\e\*q .SH HISTORY
238\&.\e\*q .SH AUTHORS
239\&.\e\*q .SH CAVEATS
240\&.\e\*q .SH BUGS
241\&.\e\*q .SH SECURITY CONSIDERATIONS
242\&.\e\*q Not used in OpenBSD.
243.Ed
244.Pp
245The sections in a
246.Nm
247document are conventionally ordered as they appear above.
248Sections should be composed as follows:
249.Bl -ohang -offset indent
250.It Em NAME
251The name(s) and a short description of the documented material.
252The syntax for this is generally as follows:
253.Pp
254.D1 \efBname\efR \e(en description
255.It Em LIBRARY
256The name of the library containing the documented material, which is
257assumed to be a function in a section 2 or 3 manual.
258For functions in the C library, this may be as follows:
259.Pp
260.D1 Standard C Library (libc, -lc)
261.It Em SYNOPSIS
262Documents the utility invocation syntax, function call syntax, or device
263configuration.
264.Pp
265For the first, utilities (sections 1, 6, and 8), this is
266generally structured as follows:
267.Pp
268.D1 \efBname\efR [-\efBab\efR] [-\efBc\efR\efIarg\efR] \efBpath\efR...
269.Pp
270For the second, function calls (sections 2, 3, 9):
271.Pp
272.D1 \&.B char *name(char *\efIarg\efR);
273.Pp
274And for the third, configurations (section 4):
275.Pp
276.D1 \&.B name* at cardbus ? function ?
277.Pp
278Manuals not in these sections generally don't need a
279.Em SYNOPSIS .
280.It Em DESCRIPTION
281This expands upon the brief, one-line description in
282.Em NAME .
283It usually contains a break-down of the options (if documenting a
284command).
285.It Em IMPLEMENTATION NOTES
286Implementation-specific notes should be kept here.
287This is useful when implementing standard functions that may have side
288effects or notable algorithmic implications.
289.It Em RETURN VALUES
290This section documents the return values of functions in sections 2, 3, and 9.
291.It Em ENVIRONMENT
292Documents any usages of environment variables, e.g.,
293.Xr environ 7 .
294.It Em FILES
295Documents files used.
296It's helpful to document both the file name and a short description of how
297the file is used (created, modified, etc.).
298.It Em EXIT STATUS
299This section documents the command exit status for
300section 1, 6, and 8 utilities.
301Historically, this information was described in
302.Em DIAGNOSTICS ,
303a practise that is now discouraged.
304.It Em EXAMPLES
305Example usages.
306This often contains snippets of well-formed,
307well-tested invocations.
308Make sure that examples work properly!
309.It Em DIAGNOSTICS
310Documents error conditions.
311This is most useful in section 4 manuals.
312Historically, this section was used in place of
313.Em EXIT STATUS
314for manuals in sections 1, 6, and 8; however, this practise is
315discouraged.
316.It Em ERRORS
317Documents error handling in sections 2, 3, and 9.
318.It Em SEE ALSO
319References other manuals with related topics.
320This section should exist for most manuals.
321.Pp
322.D1 \&.BR bar \&( 1 \&),
323.Pp
324Cross-references should conventionally be ordered
325first by section, then alphabetically.
326.It Em STANDARDS
327References any standards implemented or used, such as
328.Pp
329.D1 IEEE Std 1003.2 (\e(lqPOSIX.2\e(rq)
330.Pp
331If not adhering to any standards, the
332.Em HISTORY
333section should be used.
334.It Em HISTORY
335A brief history of the subject, including where support first appeared.
336.It Em AUTHORS
337Credits to the person or persons who wrote the code and/or documentation.
338Authors should generally be noted by both name and email address.
339.It Em CAVEATS
340Common misuses and misunderstandings should be explained
341in this section.
342.It Em BUGS
343Known bugs, limitations, and work-arounds should be described
344in this section.
345.It Em SECURITY CONSIDERATIONS
346Documents any security precautions that operators should consider.
347.El
348.Sh MACRO SYNTAX
349Macros are one to three characters in length and begin with a
350control character,
351.Sq \&. ,
352at the beginning of the line.
353The
354.Sq \(aq
355macro control character is also accepted.
356An arbitrary amount of whitespace (spaces or tabs) may sit between the
357control character and the macro name.
358Thus, the following are equivalent:
359.Bd -literal -offset indent
360\&.PP
361\&.\ \ \ PP
362.Ed
363.Pp
364To include space characters in macro arguments, arguments may be quoted;
365see the
366.Sq MACRO SYNTAX
367section in the
368.Xr roff 7
369manual for details.
370.Pp
371The
372.Nm
373macros are classified by scope: line scope or block scope.
374Line macros are only scoped to the current line (and, in some
375situations, the subsequent line).
376Block macros are scoped to the current line and subsequent lines until
377closed by another block macro.
378.Ss Line Macros
379Line macros are generally scoped to the current line, with the body
380consisting of zero or more arguments.
381If a macro is scoped to the next line and the line arguments are empty,
382the next line, which must be text, is used instead.
383Thus:
384.Bd -literal -offset indent
385\&.I
386foo
387.Ed
388.Pp
389is equivalent to
390.Sq \&.I foo .
391If next-line macros are invoked consecutively, only the last is used.
392If a next-line macro is followed by a non-next-line macro, an error is
393raised, except for
394.Sx \&br ,
395.Sx \&sp ,
396and
397.Sx \&na .
398.Pp
399The syntax is as follows:
400.Bd -literal -offset indent
401\&.YO \(lBbody...\(rB
402\(lBbody...\(rB
403.Ed
404.Pp
405.Bl -column -compact -offset indent "MacroX" "ArgumentsX" "ScopeXXXXX" "CompatX"
406.It Em Macro Ta Em Arguments Ta Em Scope     Ta Em Notes
407.It Sx \&AT  Ta    <=1       Ta    current   Ta    \&
408.It Sx \&B   Ta    n         Ta    next-line Ta    \&
409.It Sx \&BI  Ta    n         Ta    current   Ta    \&
410.It Sx \&BR  Ta    n         Ta    current   Ta    \&
411.It Sx \&DT  Ta    0         Ta    current   Ta    \&
412.It Sx \&I   Ta    n         Ta    next-line Ta    \&
413.It Sx \&IB  Ta    n         Ta    current   Ta    \&
414.It Sx \&IR  Ta    n         Ta    current   Ta    \&
415.It Sx \&R   Ta    n         Ta    next-line Ta    \&
416.It Sx \&RB  Ta    n         Ta    current   Ta    \&
417.It Sx \&RI  Ta    n         Ta    current   Ta    \&
418.It Sx \&SB  Ta    n         Ta    next-line Ta    \&
419.It Sx \&SM  Ta    n         Ta    next-line Ta    \&
420.It Sx \&TH  Ta    >1, <6    Ta    current   Ta    \&
421.It Sx \&UC  Ta    <=1       Ta    current   Ta    \&
422.It Sx \&br  Ta    0         Ta    current   Ta    compat
423.It Sx \&fi  Ta    0         Ta    current   Ta    compat
424.It Sx \&in  Ta    1         Ta    current   Ta    compat
425.It Sx \&na  Ta    0         Ta    current   Ta    compat
426.It Sx \&nf  Ta    0         Ta    current   Ta    compat
427.It Sx \&sp  Ta    1         Ta    current   Ta    compat
428.El
429.Pp
430Macros marked as
431.Qq compat
432are included for compatibility with the significant corpus of existing
433manuals that mix dialects of roff.
434These macros should not be used for portable
435.Nm
436manuals.
437.Ss Block Macros
438Block macros comprise a head and body.
439As with in-line macros, the head is scoped to the current line and, in
440one circumstance, the next line (the next-line stipulations as in
441.Sx Line Macros
442apply here as well).
443.Pp
444The syntax is as follows:
445.Bd -literal -offset indent
446\&.YO \(lBhead...\(rB
447\(lBhead...\(rB
448\(lBbody...\(rB
449.Ed
450.Pp
451The closure of body scope may be to the section, where a macro is closed
452by
453.Sx \&SH ;
454sub-section, closed by a section or
455.Sx \&SS ;
456part, closed by a section, sub-section, or
457.Sx \&RE ;
458or paragraph, closed by a section, sub-section, part,
459.Sx \&HP ,
460.Sx \&IP ,
461.Sx \&LP ,
462.Sx \&P ,
463.Sx \&PP ,
464or
465.Sx \&TP .
466No closure refers to an explicit block closing macro.
467.Pp
468As a rule, block macros may not be nested; thus, calling a block macro
469while another block macro scope is open, and the open scope is not
470implicitly closed, is syntactically incorrect.
471.Pp
472.Bl -column -compact -offset indent "MacroX" "ArgumentsX" "Head ScopeX" "sub-sectionX" "compatX"
473.It Em Macro Ta Em Arguments Ta Em Head Scope Ta Em Body Scope  Ta Em Notes
474.It Sx \&HP  Ta    <2        Ta    current    Ta    paragraph   Ta    \&
475.It Sx \&IP  Ta    <3        Ta    current    Ta    paragraph   Ta    \&
476.It Sx \&LP  Ta    0         Ta    current    Ta    paragraph   Ta    \&
477.It Sx \&P   Ta    0         Ta    current    Ta    paragraph   Ta    \&
478.It Sx \&PP  Ta    0         Ta    current    Ta    paragraph   Ta    \&
479.It Sx \&RE  Ta    0         Ta    current    Ta    none        Ta    compat
480.It Sx \&RS  Ta    1         Ta    current    Ta    part        Ta    compat
481.It Sx \&SH  Ta    >0        Ta    next-line  Ta    section     Ta    \&
482.It Sx \&SS  Ta    >0        Ta    next-line  Ta    sub-section Ta    \&
483.It Sx \&TP  Ta    n         Ta    next-line  Ta    paragraph   Ta    \&
484.El
485.Pp
486Macros marked
487.Qq compat
488are as mentioned in
489.Sx Line Macros .
490.Pp
491If a block macro is next-line scoped, it may only be followed by in-line
492macros for decorating text.
493.Sh REFERENCE
494This section is a canonical reference to all macros, arranged
495alphabetically.
496For the scoping of individual macros, see
497.Sx MACRO SYNTAX .
498.Ss \&AT
499Sets the volume for the footer for compatibility with man pages from
500.Tn AT&T UNIX
501releases.
502The optional arguments specify which release it is from.
503.Ss \&B
504Text is rendered in bold face.
505.Pp
506See also
507.Sx \&I
508and
509.Sx \&R .
510.Ss \&BI
511Text is rendered alternately in bold face and italic.
512Thus,
513.Sq .BI this word and that
514causes
515.Sq this
516and
517.Sq and
518to render in bold face, while
519.Sq word
520and
521.Sq that
522render in italics.
523Whitespace between arguments is omitted in output.
524.Pp
525Examples:
526.Pp
527.Dl \&.BI bold italic bold italic
528.Pp
529The output of this example will be emboldened
530.Dq bold
531and italicised
532.Dq italic ,
533with spaces stripped between arguments.
534.Pp
535See also
536.Sx \&IB ,
537.Sx \&BR ,
538.Sx \&RB ,
539.Sx \&RI ,
540and
541.Sx \&IR .
542.Ss \&BR
543Text is rendered alternately in bold face and roman (the default font).
544Whitespace between arguments is omitted in output.
545.Pp
546See
547.Sx \&BI
548for an equivalent example.
549.Pp
550See also
551.Sx \&BI ,
552.Sx \&IB ,
553.Sx \&RB ,
554.Sx \&RI ,
555and
556.Sx \&IR .
557.Ss \&DT
558Has no effect.
559Included for compatibility.
560.Ss \&HP
561Begin a paragraph whose initial output line is left-justified, but
562subsequent output lines are indented, with the following syntax:
563.Bd -filled -offset indent
564.Pf \. Sx \&HP
565.Op Cm width
566.Ed
567.Pp
568The
569.Cm width
570argument must conform to
571.Sx Scaling Widths .
572If specified, it's saved for later paragraph left-margins; if unspecified, the
573saved or default width is used.
574.Pp
575See also
576.Sx \&IP ,
577.Sx \&LP ,
578.Sx \&P ,
579.Sx \&PP ,
580and
581.Sx \&TP .
582.Ss \&I
583Text is rendered in italics.
584.Pp
585See also
586.Sx \&B
587and
588.Sx \&R .
589.Ss \&IB
590Text is rendered alternately in italics and bold face.
591Whitespace between arguments is omitted in output.
592.Pp
593See
594.Sx \&BI
595for an equivalent example.
596.Pp
597See also
598.Sx \&BI ,
599.Sx \&BR ,
600.Sx \&RB ,
601.Sx \&RI ,
602and
603.Sx \&IR .
604.Ss \&IP
605Begin an indented paragraph with the following syntax:
606.Bd -filled -offset indent
607.Pf \. Sx \&IP
608.Op Cm head Op Cm width
609.Ed
610.Pp
611The
612.Cm width
613argument defines the width of the left margin and is defined by
614.Sx Scaling Widths .
615It's saved for later paragraph left-margins; if unspecified, the saved or
616default width is used.
617.Pp
618The
619.Cm head
620argument is used as a leading term, flushed to the left margin.
621This is useful for bulleted paragraphs and so on.
622.Pp
623See also
624.Sx \&HP ,
625.Sx \&LP ,
626.Sx \&P ,
627.Sx \&PP ,
628and
629.Sx \&TP .
630.Ss \&IR
631Text is rendered alternately in italics and roman (the default font).
632Whitespace between arguments is omitted in output.
633.Pp
634See
635.Sx \&BI
636for an equivalent example.
637.Pp
638See also
639.Sx \&BI ,
640.Sx \&IB ,
641.Sx \&BR ,
642.Sx \&RB ,
643and
644.Sx \&RI .
645.Ss \&LP
646Begin an undecorated paragraph.
647The scope of a paragraph is closed by a subsequent paragraph,
648sub-section, section, or end of file.
649The saved paragraph left-margin width is reset to the default.
650.Pp
651See also
652.Sx \&HP ,
653.Sx \&IP ,
654.Sx \&P ,
655.Sx \&PP ,
656and
657.Sx \&TP .
658.Ss \&P
659Synonym for
660.Sx \&LP .
661.Pp
662See also
663.Sx \&HP ,
664.Sx \&IP ,
665.Sx \&LP ,
666.Sx \&PP ,
667and
668.Sx \&TP .
669.Ss \&PP
670Synonym for
671.Sx \&LP .
672.Pp
673See also
674.Sx \&HP ,
675.Sx \&IP ,
676.Sx \&LP ,
677.Sx \&P ,
678and
679.Sx \&TP .
680.Ss \&R
681Text is rendered in roman (the default font).
682.Pp
683See also
684.Sx \&I
685and
686.Sx \&B .
687.Ss \&RB
688Text is rendered alternately in roman (the default font) and bold face.
689Whitespace between arguments is omitted in output.
690.Pp
691See
692.Sx \&BI
693for an equivalent example.
694.Pp
695See also
696.Sx \&BI ,
697.Sx \&IB ,
698.Sx \&BR ,
699.Sx \&RI ,
700and
701.Sx \&IR .
702.Ss \&RE
703Explicitly close out the scope of a prior
704.Sx \&RS .
705.Ss \&RI
706Text is rendered alternately in roman (the default font) and italics.
707Whitespace between arguments is omitted in output.
708.Pp
709See
710.Sx \&BI
711for an equivalent example.
712.Pp
713See also
714.Sx \&BI ,
715.Sx \&IB ,
716.Sx \&BR ,
717.Sx \&RB ,
718and
719.Sx \&IR .
720.Ss \&RS
721Begin a part setting the left margin.
722The left margin controls the offset, following an initial indentation,
723to un-indented text such as that of
724.Sx \&PP .
725This has the following syntax:
726.Bd -filled -offset indent
727.Pf \. Sx \&Rs
728.Op Cm width
729.Ed
730.Pp
731The
732.Cm width
733argument must conform to
734.Sx Scaling Widths .
735If not specified, the saved or default width is used.
736.Ss \&SB
737Text is rendered in small size (one point smaller than the default font)
738bold face.
739.Ss \&SH
740Begin a section.
741The scope of a section is only closed by another section or the end of
742file.
743The paragraph left-margin width is reset to the default.
744.Ss \&SM
745Text is rendered in small size (one point smaller than the default
746font).
747.Ss \&SS
748Begin a sub-section.
749The scope of a sub-section is closed by a subsequent sub-section,
750section, or end of file.
751The paragraph left-margin width is reset to the default.
752.Ss \&TH
753Sets the title of the manual page with the following syntax:
754.Bd -filled -offset indent
755.Pf \. Sx \&TH
756.Ar title section date
757.Op Ar source Op Ar volume
758.Ed
759.Pp
760Conventionally, the document
761.Ar title
762is given in all caps.
763The recommended
764.Ar date
765format is
766.Sy YYYY-MM-DD
767as specified in the ISO-8601 standard;
768if the argument does not conform, it is printed verbatim.
769If the
770.Ar date
771is empty or not specified, the current date is used.
772The optional
773.Ar source
774string specifies the organisation providing the utility.
775The
776.Ar volume
777string replaces the default rendered volume, which is dictated by the
778manual section.
779.Pp
780Examples:
781.Pp
782.Dl \&.TH CVS 5 "1992-02-12" GNU
783.Ss \&TP
784Begin a paragraph where the head, if exceeding the indentation width, is
785followed by a newline; if not, the body follows on the same line after a
786buffer to the indentation width.
787Subsequent output lines are indented.
788The syntax is as follows:
789.Bd -filled -offset indent
790.Pf \. Sx \&TP
791.Op Cm width
792.Ed
793.Pp
794The
795.Cm width
796argument must conform to
797.Sx Scaling Widths .
798If specified, it's saved for later paragraph left-margins; if
799unspecified, the saved or default width is used.
800.Pp
801See also
802.Sx \&HP ,
803.Sx \&IP ,
804.Sx \&LP ,
805.Sx \&P ,
806and
807.Sx \&PP .
808.Ss \&UC
809Sets the volume for the footer for compatibility with man pages from
810BSD releases.
811The optional first argument specifies which release it is from.
812.Ss \&br
813Breaks the current line.
814Consecutive invocations have no further effect.
815.Pp
816See also
817.Sx \&sp .
818.Ss \&fi
819End literal mode begun by
820.Sx \&nf .
821.Ss \&in
822Indent relative to the current indentation:
823.Pp
824.D1 Pf \. Sx \&in Op Cm width
825.Pp
826If
827.Cm width
828is signed, the new offset is relative.
829Otherwise, it is absolute.
830This value is reset upon the next paragraph, section, or sub-section.
831.Ss \&na
832Don't align to the right margin.
833.Ss \&nf
834Begin literal mode: all subsequent free-form lines have their end of
835line boundaries preserved.
836May be ended by
837.Sx \&fi .
838.Ss \&sp
839Insert vertical spaces into output with the following syntax:
840.Bd -filled -offset indent
841.Pf \. Sx \&sp
842.Op Cm height
843.Ed
844.Pp
845Insert
846.Cm height
847spaces, which must conform to
848.Sx Scaling Widths .
849If 0, this is equivalent to the
850.Sx \&br
851macro.
852Defaults to 1, if unspecified.
853.Pp
854See also
855.Sx \&br .
856.Sh COMPATIBILITY
857This section documents areas of questionable portability between
858implementations of the
859.Nm
860language.
861.Pp
862.Bl -dash -compact
863.It
864In quoted literals, GNU troff allowed pair-wise double-quotes to produce
865a standalone double-quote in formatted output.
866It is not known whether this behaviour is exhibited by other formatters.
867.It
868troff suppresses a newline before
869.Sq \(aq
870macro output; in mandoc, it is an alias for the standard
871.Sq \&.
872control character.
873.It
874The
875.Sq \eh
876.Pq horizontal position ,
877.Sq \ev
878.Pq vertical position ,
879.Sq \em
880.Pq text colour ,
881.Sq \eM
882.Pq text filling colour ,
883.Sq \ez
884.Pq zero-length character ,
885.Sq \ew
886.Pq string length ,
887.Sq \ek
888.Pq horizontal position marker ,
889.Sq \eo
890.Pq text overstrike ,
891and
892.Sq \es
893.Pq text size
894escape sequences are all discarded in mandoc.
895.It
896The
897.Sq \ef
898scaling unit is accepted by mandoc, but rendered as the default unit.
899.It
900The
901.Sx \&sp
902macro does not accept negative values in mandoc.
903In GNU troff, this would result in strange behaviour.
904.El
905.Sh SEE ALSO
906.Xr man 1 ,
907.Xr mandoc 1 ,
908.Xr mandoc_char 7 ,
909.Xr mdoc 7 ,
910.Xr roff 7 ,
911.Xr tbl 7
912.Sh HISTORY
913The
914.Nm
915language first appeared as a macro package for the roff typesetting
916system in
917.At v7 .
918It was later rewritten by James Clark as a macro package for groff.
919The stand-alone implementation that is part of the
920.Xr mandoc 1
921utility written by Kristaps Dzonsons appeared in
922.Ox 4.6 .
923.Sh AUTHORS
924This
925.Nm
926reference was written by
927.An Kristaps Dzonsons Aq kristaps@bsd.lv .
928.Sh CAVEATS
929Do not use this language.
930Use
931.Xr mdoc 7 ,
932instead.
933