From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from scc-mailout.scc.kit.edu (scc-mailout.scc.kit.edu [129.13.185.201]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id p718FRdF028591 for ; Mon, 1 Aug 2011 04:15:27 -0400 (EDT) Received: from hekate.usta.de (asta-nat.asta.uni-karlsruhe.de [172.22.63.82]) by scc-mailout-01 with esmtp (Exim 4.72 #1) id 1Qnneo-00033k-11; Mon, 01 Aug 2011 10:15:26 +0200 Received: from donnerwolke.usta.de ([172.24.96.3]) by hekate.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1Qnneo-0005LE-5c; Mon, 01 Aug 2011 10:15:26 +0200 Received: from iris.usta.de ([172.24.96.5] helo=usta.de) by donnerwolke.usta.de with esmtp (Exim 4.69) (envelope-from ) id 1Qnneo-0001vI-3i; Mon, 01 Aug 2011 10:15:26 +0200 Received: from schwarze by usta.de with local (Exim 4.72) (envelope-from ) id 1Qnneo-0000yN-2f; Mon, 01 Aug 2011 10:15:26 +0200 Date: Mon, 1 Aug 2011 10:15:26 +0200 From: Ingo Schwarze To: Jason McIntyre Cc: tech@mdocml.bsd.lv Subject: Re: document delimiter handling in mdoc(7) Message-ID: <20110801081526.GB30355@iris.usta.de> References: <20110731221208.GJ1831@iris.usta.de> <20110801072541.GB9580@harkle.home.gateway> X-Mailinglist: mdocml-tech Reply-To: tech@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110801072541.GB9580@harkle.home.gateway> User-Agent: Mutt/1.5.21 (2010-09-15) Hi Jason, Jason McIntyre wrote on Mon, Aug 01, 2011 at 08:25:17AM +0100: > - (just checking) you call \& a "non-breaking space", right? Good catch, that's plainly wrong. It must be "zero-width space". Non-breaking would be "\~". Fixed in two places. > - your list of delimeters should probably not use (). for example: > > . (period) > would read better as > . period Yes, i removed the .Pq. While here, i also removed a few hyphens and added "mark" to "question" and "exclamation". > - you have a typo: encouter Fixed, and updated patch appended. > - shouldn;t the middle delimeter list (|) be listed with the other > delimiters? In a way, that would be nice, but i can't think of a good way to do it without causing other issues: * The sentence about \. should come right after the closing delimiters, so there is at least one small paragraph in between, anyway. * Unlike opening and closing delimiters, middle delimiters do not fall out of the beginning and end of macros (except at the end after closing delimiters, which is not very useful and so weird that i'm not planning to document it). Putting them together with the others might cause confusion in this respect. * The only aspect special about middle delimiters is interrupting .Fl-style in-line macros, so i would like to put them close to the text explaining that. * Having the ugly \*(Ba special case at the very end is quite nice, i wouldn't want that ugliness somewhere in the middle. However, it should come right after introducing the bar. So, if you have a suggestion for a better ordering, i'm open to that, but i can't think of any right now... Yours, Ingo Index: mdoc.7 =================================================================== RCS file: /cvs/src/share/man/man7/mdoc.7,v retrieving revision 1.76 diff -u -r1.76 mdoc.7 --- mdoc.7 1 Aug 2011 07:45:08 -0000 1.76 +++ mdoc.7 1 Aug 2011 08:07:14 -0000 @@ -65,43 +65,6 @@ is also ignored. Macro lines with only a control character and optional whitespace are stripped from input. -.Ss Reserved Characters -Within a macro line, the following characters are reserved: -.Pp -.Bl -tag -width Ds -offset indent -compact -.It \&. -.Pq period -.It \e. -.Pq escaped period -.It \&, -.Pq comma -.It \&: -.Pq colon -.It \&; -.Pq semicolon -.It \&( -.Pq left-parenthesis -.It \&) -.Pq right-parenthesis -.It \&[ -.Pq left-bracket -.It \&] -.Pq right-bracket -.It \&? -.Pq question -.It \&! -.Pq exclamation -.It \&| -.Pq vertical bar -.It \e*(Ba -.Pq reserved-word vertical bar -.El -.Pp -For general use in macro lines, these characters can either be escaped -with a non-breaking space -.Pq Sq \e& -or, if applicable, an appropriate escape sequence can be used. -In text lines, these may be used as normal punctuation. .Ss Special Characters Special characters may occur in both macro and text lines. Sequences begin with the escape character @@ -629,7 +592,7 @@ produces .Sq Op Fl O Ar file . To prevent a macro call and render the macro name literally, -escape it by prepending a non-breaking space, +escape it by prepending a zero-width space, .Sq \e& . For example, .Sq \&Op \e&Fl O @@ -763,9 +726,8 @@ .It Sx \&Xo Ta Yes Ta Yes Ta closed by Sx \&Xc .El .Ss Block partial-implicit -Like block full-implicit, but with single-line scope closed by -.Sx Reserved Characters -or end of line. +Like block full-implicit, but with single-line scope closed by the +end of the line. .Bd -literal -offset indent \&.Yo \(lB\-arg \(lBval...\(rB\(rB \(lBbody...\(rB \(lBres...\(rB .Ed @@ -811,9 +773,8 @@ .It Sx \&Ta Ta Yes Ta Yes Ta closed by Sx \&Ta , Sx \&It .El .Ss In-line -Closed by -.Sx Reserved Characters , -end of line, fixed argument lengths, and/or subsequent macros. +Closed by the end of the line, fixed argument lengths, +and/or subsequent macros. In-line macros have only text children. If a number (or inequality) of arguments is .Pq n , @@ -903,6 +864,90 @@ .It Sx \&br Ta \&No Ta \&No Ta 0 .It Sx \&sp Ta \&No Ta \&No Ta 1 .El +.Ss Delimiters +When a macro argument consists of one single input character +considered as a delimiter, the argument gets special handling. +This does not apply when delimiters appear in arguments containing +more than one character. +Consequently, to prevent special handling and just handle it +like any other argument, a delimiter can be escaped by prepending +a zero-width space +.Pq Sq \e& . +In text lines, delimiters never need escaping, but may be used +as normal punctuation. +.Pp +For many macros, when the leading arguments are opening delimiters, +these delimiters are put before the macro scope, +and when the trailing arguments are closing delimiters, +these delimiters are put after the macro scope. +For example, +.Pp +.D1 Pf \. \&Aq "( [ word ] ) ." +.Pp +renders as: +.Pp +.D1 Aq ( [ word ] ) . +.Pp +Opening delimiters are: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It \&( +left parenthesis +.It \&[ +left bracket +.El +.Pp +Closing delimiters are: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It \&. +period +.It \&, +comma +.It \&: +colon +.It \&; +semicolon +.It \&) +right parenthesis +.It \&] +right bracket +.It \&? +question mark +.It \&! +exclamation mark +.El +.Pp +Note that even a period preceded by a backslash +.Pq Sq \e.\& +gets this special handling; use +.Sq \e&. +to prevent that. +.Pp +Many in-line macros interrupt their scope when they encounter +delimiters, and resume their scope when more arguments follow that +are not delimiters. +For example, +.Pp +.D1 Pf \. \&Fl "a ( b | c \e*(Ba d ) e" +.Pp +renders as: +.Pp +.D1 Fl a ( b | c \*(Ba d ) e +.Pp +This applies to both opening and closing delimiters, +and also to the middle delimiter: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It \&| +vertical bar +.El +.Pp +As a special case, the predefined string \e*(Ba is handled and rendered +in the same way as a plain +.Sq \&| +character. +Using this predefined string is not recommended in new manuals. .Sh REFERENCE This section is a canonical reference of all macros, arranged alphabetically. @@ -2917,7 +2962,7 @@ lists will restart the sequence only for the sub-list. .It .Sx \&Li -followed by a reserved character is incorrectly used in some manuals +followed by a delimiter is incorrectly used in some manuals instead of properly quoting that character, which sometimes works with historic groff. .It -- To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv