=================================================================== RCS file: /cvs/mandoc/TODO,v retrieving revision 1.138 retrieving revision 1.143 diff -u -p -r1.138 -r1.143 --- mandoc/TODO 2012/07/18 10:39:19 1.138 +++ mandoc/TODO 2012/10/12 16:45:34 1.143 @@ -1,6 +1,6 @@ ************************************************************************ * Official mandoc TODO. -* $Id: TODO,v 1.138 2012/07/18 10:39:19 schwarze Exp $ +* $Id: TODO,v 1.143 2012/10/12 16:45:34 schwarze Exp $ ************************************************************************ ************************************************************************ @@ -191,6 +191,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 ************************************************************************ @@ -203,13 +211,6 @@ is just "o\bo". see for example 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 @@ -250,48 +251,10 @@ 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 - .SH HEADER - - .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