===================================================================
RCS file: /cvs/mandoc/TODO,v
retrieving revision 1.133
retrieving revision 1.144
diff -u -p -r1.133 -r1.144
--- mandoc/TODO	2012/05/31 01:54:45	1.133
+++ mandoc/TODO	2012/10/31 09:20:23	1.144
@@ -1,6 +1,6 @@
 ************************************************************************
 * Official mandoc TODO.
-* $Id: TODO,v 1.133 2012/05/31 01:54:45 schwarze Exp $
+* $Id: TODO,v 1.144 2012/10/31 09:20:23 schwarze Exp $
 ************************************************************************
 
 ************************************************************************
@@ -115,6 +115,8 @@
 
 - groff an-ext.tmac macros (.UR, .UE) occur in xine(5)
   reported by brad@  Sat, 15 Jan 2011 15:45:23 -0500
+  also occur in freeciv-client(6) freeciv-server(6) freeciv-modpack(6)
+  reported by bentley@  Tue, 30 Oct 2012 01:05:57 -0600
 
 - -T[x]html doesn't stipulate non-collapsing spaces in literal mode
 
@@ -169,9 +171,6 @@
   so far, we only have it in roff(7) and man(7)
   reminded by millert@  Thu, 09 Dec 2010 17:29:52 -0500
 
-- perl(1) SYNOPSIS looks bad; reported by deraadt@
-  1) man(7) seems to need SYNOPSIS .Nm blocks, too
-
 - In .Bl -column,
   .It Em Authentication<tab>Key Length
   ought to render "Key Length" with emphasis, too,
@@ -194,6 +193,14 @@
 - in enclosures, mandoc sometimes fancies a bogus end of sentence
   reminded by jmc@  Thu, 23 Sep 2010 18:13:39 +0059
 
+- Trailing isolated dots lack EOS for some macros.
+  This cannot use mandoc_eos() because groff only does EOS
+  for isolated dots at least in some of these cases.
+  Affected macros included those using in_line_eoln().
+  Make sure to fix open(2)
+  without breaking fstat(1), ksh(1), tzset(3) and UKC(8).
+  reported by Nicolas Joly  Fri, 12 Oct 2012 17:00:36 +0200
+
 ************************************************************************
 * formatting issues: gratuitous differences
 ************************************************************************
@@ -206,18 +213,6 @@
   is just "o\bo".
   see for example 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"
-  in OpenBSD ksh(1)
-
-- A bogus .Pp between two .It must not produce a double blank line,
-  see between -R and -r in OpenBSD rm(1), before "update" in mount(8),
-  or in DIAGNOSTICS in init(8), or before "is always true" in ksh(1).
-  The same happens with .Pp just before .El, see bgpd.conf(5).
-  Also have `It' complain if `Pp' is invoked at certain times (not
-  -compact?).
-
 - .Pp between two .It in .Bl -column should produce one,
   not two blank lines, see e.g. login.conf(5).
   reported by jmc@  Sun, 17 Apr 2011 14:04:58 +0059
@@ -258,68 +253,17 @@
   Also, we don't want to break the line within the argument of:
   .Fa "chtype tl"
 
-- .Ns should work when called at the end of an input line, see
-  the following code in vi(1):
-    .It Xo
-    .Op Ar line
-    .Cm a Ns Op Cm ppend Ns
-    .Op Cm !\&
-    .Xc
-    The input text is appended after the specified line.
-
 - Header lines of excessive length:
   Port OpenBSD man_term.c rev. 1.25 to mdoc_term.c
   and document it in mdoc(7) and man(7) COMPATIBILITY
   found while talking to Chris Bennett
 
-- In man(7), the sequence
-    .HP
-    one line of regular text
-    .SH
-  should not produce two blank lines before the .SH,
-  see for example named-checkconf(8).
-
-- In man(7), the sequence
-    .SH HEADER
-    <blank line>
-    .PP
-    regular text
-  should not produce any blank lines between the header and the text,
-  see for example rsync(1).
-  Reported by naddy@  Mon, 28 Mar 2011 20:45:42 +0200
-
-- In man(7), the sequence
-    regular text
-    .IP
-    .IP "tag"
-    indented text
-  should produce one, not four blank lines between the regular text
-  and the tag, see for example rsync(1).
-  Likewise,
-    regular text
-    .IP
-    indented text
-  should produce one, not two blank lines in between, and
-    regular text
-    .IP
-    .RS
-    .IP tag
-    indented text
-  should produce one, not three blank lines.
-  Reported by naddy@  Mon, 28 Mar 2011 20:45:42 +0200
-
 - trailing whitespace must be ignored even when followed by a font escape,
   see for example 
     makes
     \fBdig \fR
     operate in batch mode
   in dig(1).
-
-************************************************************************
-* error reporting issues
-************************************************************************
-
-- .TP directly followed by .RS gives an assertion.
 
 ************************************************************************
 * performance issues