===================================================================
RCS file: /cvs/mandoc/TODO,v
retrieving revision 1.44
retrieving revision 1.53
diff -u -p -r1.44 -r1.53
--- mandoc/TODO	2010/09/04 19:01:52	1.44
+++ mandoc/TODO	2010/09/27 09:26:27	1.53
@@ -1,6 +1,6 @@
 ************************************************************************
 * Official mandoc TODO.
-* $Id: TODO,v 1.44 2010/09/04 19:01:52 kristaps Exp $
+* $Id: TODO,v 1.53 2010/09/27 09:26:27 kristaps Exp $
 ************************************************************************
 
 ************************************************************************
@@ -90,6 +90,9 @@
   try e.g. .Bl -column It Ta Ta
   reported by millert Fri, 02 Apr 2010 16:13:46 -0400
 
+- 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
 ************************************************************************
@@ -142,18 +145,6 @@
   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).
-
 ************************************************************************
 * performance issues
 ************************************************************************
@@ -170,17 +161,4 @@ 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.
+- remove superfluous NOSPACE invocations (e.g., with term_word(p, "("))