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