===================================================================
RCS file: /cvs/mandoc/TODO,v
retrieving revision 1.96
retrieving revision 1.99
diff -u -p -r1.96 -r1.99
--- mandoc/TODO	2011/03/23 22:16:03	1.96
+++ mandoc/TODO	2011/04/12 23:54:12	1.99
@@ -1,6 +1,6 @@
 ************************************************************************
 * Official mandoc TODO.
-* $Id: TODO,v 1.96 2011/03/23 22:16:03 schwarze Exp $
+* $Id: TODO,v 1.99 2011/04/12 23:54:12 schwarze Exp $
 ************************************************************************
 
 ************************************************************************
@@ -16,11 +16,6 @@
   .br \}
   reported by ulrich spoerlein  Tue, 19 Oct 2010 20:39:50 +0200
 
-- \. at the start of the line does *not* prevent interpretation
-  of the following word as a macro.
-  Werner LEMBERG on bug-groff@  Tue, 22 Mar 2011 14:21:28 +0100
-  http://lists.gnu.org/archive/html/bug-groff/2011-03/msg00011.html
-
 ************************************************************************
 * formatter bugs
 ************************************************************************
@@ -56,6 +51,11 @@
 
 - \c (interrupted text) occurs in chat(8)
 
+- \f(CW (constant width font) occurs in rsyncd.conf(5).
+  I think we should treat unknown/unavailable fonts as \fR
+  such that switching back with \fP works correctly -
+  and doesn't revert the _previous_ \fP.
+
 --- missing mdoc features ----------------------------------------------
 
 - fix bad block nesting involving multiple identical explicit blocks
@@ -264,6 +264,49 @@
   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,
@@ -276,6 +319,13 @@
 ************************************************************************
 * error reporting issues
 ************************************************************************
+
+- In man(7), an empty subsection (.SS) should not be an error, probably
+  not even a warning.  For example, in ExtUtils::CChecker(3p), this is
+  used in a way similar to empty .It -tag in mdoc(7), that is, explaining
+  two commands (both presented with .SS markup) in one paragraph of text.
+  Reported by Gleydson Soares <gsoares at trusted dot com dot br>
+  on ports@  Tue, 12 Apr 2011 15:39:26 -0300
 
 ************************************************************************
 * performance issues