===================================================================
RCS file: /cvs/mandoc/TODO,v
retrieving revision 1.42
retrieving revision 1.57
diff -u -p -r1.42 -r1.57
--- mandoc/TODO	2010/08/20 22:51:29	1.42
+++ mandoc/TODO	2010/09/27 22:42:48	1.57
@@ -1,6 +1,6 @@
 ************************************************************************
 * Official mandoc TODO.
-* $Id: TODO,v 1.42 2010/08/20 22:51:29 schwarze Exp $
+* $Id: TODO,v 1.57 2010/09/27 22:42:48 kristaps Exp $
 ************************************************************************
 
 ************************************************************************
@@ -74,9 +74,10 @@
 - allow `Qq', `Dq', `Sq', `Aq', `Bq' to have 0 arguments
   noted by Alex Kozlov 08/06/10 23:05
 
-- 'br\} doesn't correctly close scope.
-  Noted by joerg@, 28/7/2010.
-  
+- 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
 ************************************************************************
@@ -93,7 +94,8 @@
   try e.g. .Bl -column It Ta Ta
   reported by millert Fri, 02 Apr 2010 16:13:46 -0400
 
-- %A doesn't put an "and" before the final author name.
+- in enclosures, mandoc sometimes fancies a bogus end of sentence
+  reminded by jmc@  Thu, 23 Sep 2010 18:13:39 +0059
 
 ************************************************************************
 * formatting issues: gratuitious differences
@@ -110,10 +112,6 @@
   Opening punctuation should not fall out of .Ns.
   see for example OpenBSD csh(1)
 
-- .%A should append the last author with " and " (if there are two)
-  or ", and " (if there are more), not ", "
-  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)
@@ -140,9 +138,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).
@@ -151,18 +146,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).
-
 ************************************************************************
 * performance issues
 ************************************************************************
@@ -178,18 +165,3 @@ Several areas can be cleaned up to make mandoc even fa
 ************************************************************************
 * structural issues
 ************************************************************************
-
-- rendering frontend code can calculate widths only for plain strings,
-  not for strings containing escape sequences.  For example, this
-  hinders calculation of the indent required for .Nm \&[ in text(1).
-  comments from kristaps@  Wed, 21 Jul 2010 23:26:08 +0200
-
-- another example of the same problem:
-  .Bl -tag -width "\eD{format}XX" -compact
-  in OpenBSD ksh(1) gives the wrong width
-  because "\e" is one character in groff, two in mandoc
-
-- Now that `ds' is minimally supported, we can get rid of some
-  predefined strings.  \*(C+ has already been thrown out.  Track these
-  down and whack them.  Look in e.g. gcc.1 for the top-level `ds'
-  invocations.  These are reproduced across most crappy GNU manuals.