===================================================================
RCS file: /cvs/mandoc/TODO,v
retrieving revision 1.48
retrieving revision 1.52
diff -u -p -r1.48 -r1.52
--- mandoc/TODO	2010/09/23 19:52:36	1.48
+++ mandoc/TODO	2010/09/25 16:52:15	1.52
@@ -1,6 +1,6 @@
 ************************************************************************
 * Official mandoc TODO.
-* $Id: TODO,v 1.48 2010/09/23 19:52:36 schwarze Exp $
+* $Id: TODO,v 1.52 2010/09/25 16:52:15 kristaps Exp $
 ************************************************************************
 
 ************************************************************************
@@ -145,20 +145,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).
-
-- 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
 ************************************************************************
@@ -175,7 +165,4 @@ Several areas can be cleaned up to make mandoc even fa
 * structural issues
 ************************************************************************
 
-- 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
+- remove superfluous NOSPACE invocations (e.g., with term_word(p, "("))