===================================================================
RCS file: /cvs/mandoc/TODO,v
retrieving revision 1.49
retrieving revision 1.59
diff -u -p -r1.49 -r1.59
--- mandoc/TODO	2010/09/25 15:29:12	1.49
+++ mandoc/TODO	2010/10/10 09:59:48	1.59
@@ -1,6 +1,6 @@
 ************************************************************************
 * Official mandoc TODO.
-* $Id: TODO,v 1.49 2010/09/25 15:29:12 kristaps Exp $
+* $Id: TODO,v 1.59 2010/10/10 09:59:48 kristaps Exp $
 ************************************************************************
 
 ************************************************************************
@@ -74,6 +74,10 @@
 - allow `Qq', `Dq', `Sq', `Aq', `Bq' to have 0 arguments
   noted by Alex Kozlov 08/06/10 23:05
 
+- Have `Sh', `It', `Ss' and others complain if `Pp' is invoked prior to
+  close (in the post validation) or prior to open (pre).  This noted by
+  jmc@ a thousand years ago.
+
 ************************************************************************
 * formatting issues: ugly output
 ************************************************************************
@@ -101,25 +105,10 @@
   to better distinguish the contents of .%T and .%J,
   see for example OpenBSD cat(1)
 
-- .It ${name Ns [ selector ] Ns }
-  should be "${name[selector]}" not "${name [selector]}"
-  This is parsed as
-  text("${name") text("[") Ns() text(selector)...
-  Opening punctuation should not fall out of .Ns.
-  see for example OpenBSD csh(1)
-
 - In .Bl -bullet, the groff bullet is "+\b+\bo\bo", the mandoc bullet
   is just "o\bo".
   see for example OpenBSD ksh(1)
 
-- .No text No ) is "text )", not "text)"
-  see the terrible example
-    case word in [[(]  pattern [| pattern] ... ) list ;; ] ... esac
-  in OpenBSD ksh(1)
-
-- .Sm should *not* produce as a blank line in .Bd -literal
-  see for example "Brace expansion" in OpenBSD ksh(1)
-
 - The characters "|" and "\*(Ba" should never be bold,
   not even in the middle of a word, e.g. ".Cm b\*(Bac" in
   "mknod [-m mode] name b|c major minor"
@@ -134,9 +123,6 @@
   In -unfilled, tabs are 5 spaces, just like in -filled and -ragged.
   See the CCDF_* display in OpenBSD ccdconfig(8).
 
-- In .Bd -unfilled, .Pp should produce one blank line, not two;
-  see the ccd.conf display in OpenBSD ccdconfig(8).
-
 - .Nx 1.0a
   should be "NetBSD 1.0A", not "NetBSD 1.0a",
   see OpenBSD ccdconfig(8).
@@ -145,20 +131,10 @@
   on the next line, it must be indented by -width, not width+1;
   see "rule block|pass" in OpenBSD ifconfig(8).
 
-- When .%T is used outside an .Rs context and with a trailing comma,
-  there is no point in rendering two commata,
-  see the first paragraph of the DESCRIPTION in OpenBSD mount_nfs(8).
+- 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 .%T is used outside an .Rs context and without a trailing comma,
-  no comma should be rendered at all,
-  see the first paragraph of the DESCRIPTION in OpenBSD exports(5).
-
-- Bogus .Pp before .Bl should not cause a double blank line,
-  see "The route utility provides the following simple commands:"
-  in OpenBSD route(8).
-
-- In -T[x]html, Rs/Re need a div.
-
 ************************************************************************
 * performance issues
 ************************************************************************
@@ -174,4 +150,3 @@ Several areas can be cleaned up to make mandoc even fa
 ************************************************************************
 * structural issues
 ************************************************************************
-