===================================================================
RCS file: /cvs/mandoc/TODO,v
retrieving revision 1.45
retrieving revision 1.48
diff -u -p -r1.45 -r1.48
--- mandoc/TODO	2010/09/08 11:57:29	1.45
+++ mandoc/TODO	2010/09/23 19:52:36	1.48
@@ -1,6 +1,6 @@
 ************************************************************************
 * Official mandoc TODO.
-* $Id: TODO,v 1.45 2010/09/08 11:57:29 kristaps Exp $
+* $Id: TODO,v 1.48 2010/09/23 19:52:36 schwarze 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
 ************************************************************************
@@ -172,17 +175,7 @@ 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.