+ see between -R and -r in OpenBSD rm(1), before "update" in mount(8),
+ or in DIAGNOSTICS in init(8), or before "is always true" in ksh(1).
+ The same happens with .Pp just before .El, see bgpd.conf(5).
+ Also have `It' complain if `Pp' is invoked at certain times (not
+ -compact?).
+
+- If the *first* line after .It is .Pp, break the line right after
+ the tag, do not pad with space characters before breaking.
+ See the description of the a, c, and i commands in sed(1).
+
+- If the first line after .It is .D1, do not assert a blank line
+ in between, see for example tmux(1).
+ reported by nicm@ 13 Jan 2011 00:18:57 +0000
+
+- .Nx 1.0a
+ should be "NetBSD 1.0A", not "NetBSD 1.0a",
+ see OpenBSD ccdconfig(8).
+
+- In .Bl -tag, if a tag exceeds the right margin and must be continued
+ on the next line, it must be indented by -width, not width+1;
+ see "rule block|pass" in OpenBSD ifconfig(8).
+
+- When the -width string contains macros, the macros must be rendered
+ before measuring the width, for example
+ .Bl -tag -width ".Dv message"
+ in magic(5), located in src/usr.bin/file, is the same
+ as -width 7n, not -width 11n.
+
+- The \& zero-width character counts as output.
+ That is, when it is alone on a line between two .Pp,
+ we want three blank lines, not two as in mandoc.
+
+- When .Fn arguments exceed one output line, all but the first
+ should be indented, see e.g. rpc(3);
+ reported by jmc@ on discuss@ Fri, 29 Oct 2010 13:48:33 +0100
+
+- .Ns should work when called at the end of an input line, see
+ the following code in vi(1):
+ .It Xo
+ .Op Ar line
+ .Cm a Ns Op Cm ppend Ns
+ .Op Cm !\&
+ .Xc
+ The input text is appended after the specified line.
+
+- Header lines of excessive length:
+ Port OpenBSD man_term.c rev. 1.25 to mdoc_term.c
+ and document it in mdoc(7) and man(7) COMPATIBILITY
+ found while talking to Chris Bennett
+
+- In man(7), the sequence
+ .HP
+ one line of regular text
+ .SH
+ should not produce two blank lines before the .SH,
+ see for example named-checkconf(8).
+
+- In man(7), the sequence
+ regular text
+ .RS
+ .IP
+ should have a blank line between the text and the beginning of the
+ indented paragraph, see for example sudo(1).
+
+- In man(7), the sequence
+ .SH HEADER
+ <blank line>
+ .PP
+ regular text
+ should not produce any blank lines between the header and the text,
+ see for example rsync(1).
+ Reported by naddy@ Mon, 28 Mar 2011 20:45:42 +0200
+
+- In man(7), the sequence
+ regular text
+ .PP
+ .RS
+ indented text
+ should produce one blank line between the regular and indented texts,
+ see for example rsync(1), and
+ .RE
+ <blank line>
+ .PP
+ .RS
+ should produce two,not one blank lines.
+ Reported by naddy@ Mon, 28 Mar 2011 20:45:42 +0200
+
+- In man(7), the sequence
+ regular text
+ .IP
+ .IP "tag"
+ indented text
+ should produce one, not four blank lines between the regular text
+ and the tag, see for example rsync(1).
+ Likewise,
+ regular text
+ .IP
+ indented text
+ should produce one, not two blank lines in between, and
+ regular text
+ .IP
+ .RS
+ .IP tag
+ indented text
+ should produce one, not three blank lines.
+ Reported by naddy@ Mon, 28 Mar 2011 20:45:42 +0200
+
+- At least sometimes, .sp is ignored right after .SH; see named.conf(5).
+
+- trailing whitespace must be ignored even when followed by a font escape,
+ see for example
+ makes
+ \fBdig \fR
+ operate in batch mode
+ in dig(1).
+
+************************************************************************
+* error reporting issues
+************************************************************************
git.ckatri.com / mandoc.git / blobdiff