Package: manpages,groff Version: 1.18.1.1-12 I would like to resolve at least one inconsistency regarding preferred manpage formatting practices. Quoting .SH arguments; see Debian #368996. manpages man.7 and groff_man.7 have different advice about whether .SH arguments with spaces should be quoted. Colin indicates that man(7) should probably change.
Also, where are \f[BRP] documented, anyway? I hope there is something more than the groff.7 paragraph "Fonts are identified...".... On Thu, Jul 27, 2006 at 04:09:02PM +0100, Colin Watson wrote: > On Thu, Jul 27, 2006 at 10:15:37AM -0400, Justin Pryzby wrote: > > On Thu, Jul 27, 2006 at 08:39:42AM +0100, Colin Watson wrote: > > > On Thu, Jul 27, 2006 at 08:20:39AM +0200, Martin Schulze wrote: > > > > I'm writing you because of Bug#368996 in which the reporter > > > > claims that when you use the .SH macro and the parameter > > > > contains a space character it should be quoted. Is this true? > > > > > > To the best of my knowledge, this is not the case. See groff_man(7), > > > which says: > > > > > > .SH [text for a heading] > > > Sets up an unnumbered section heading sticking out to > > > the left. Prints out all the text following SH up to > > > the end of the line (resp. the text in the next input > > > line if there is no argument to SH) in bold face, one > > > size larger than the base document size. Additionally, > > > the left margin for the following text is reset to its > > > default value. > > > > I'm reading man.7: > > > > If the name contains spaces and appears on the same line as .SH, > > then place the heading in double quotes. > > In my experience, man(7) frequently gives somewhat dubious advice, and > is less authoritative than groff_man(7). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
