Ccing bug #411303 not #349388
On Tue, Apr 24, 2007 at 06:00:39PM +0200, Michael Kerrisk wrote:
> Hi Hustin,
>
> >> If you would like to get this pushed upstream, the following would help:
> >>
> >> 1. Follow man-pages formatting conventions would help. In particular, the
> >> use of lines containing just a "." (to force a blank line) should be
> >> avoided. Just remove all of those lines. (Most man-pages do not have the
> >> more than one blank line to separate sections.)
> > I'd actually like to see some resolution to #411303 before changing
> > everything back; nobody has commented on it yet. After spending some
> > effort reading documentation, it's not inspiring to be told that the
> > documentation is wrong.
>
> Umm -that bug report is about quoting after .SH -- an unrelated issue. Or
The no-empty-lines things is from roff.7 which documents historical
roff. So I think you're right that this is a nonissue.
man.7
status values or a program
s/or/f&/
groff_man requires that arguments for some formatting macros (like
.BR) be on the same line, yet man.7 seems to say that they can be on
different lines.
Colin: groff.7: "afterwards the string to be defined"
I think just: after ........................
"registers starting with a dot a read-only"
^^^
are
.di macro Divert to macro .
^^^^^^^
There should be no space here, and the underlining is messed up;
.I macro .
.IR macro .
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
