=================================================================== RCS file: /cvs/mandoc/TODO,v retrieving revision 1.46 retrieving revision 1.55 diff -u -p -r1.46 -r1.55 --- mandoc/TODO 2010/09/15 13:10:30 1.46 +++ mandoc/TODO 2010/09/27 11:21:39 1.55 @@ -1,6 +1,6 @@ ************************************************************************ * Official mandoc TODO. -* $Id: TODO,v 1.46 2010/09/15 13:10:30 kristaps Exp $ +* $Id: TODO,v 1.55 2010/09/27 11:21:39 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 ************************************************************************ @@ -131,9 +134,6 @@ In -unfilled, tabs are 5 spaces, just like in -filled and -ragged. See the CCDF_* display in OpenBSD ccdconfig(8). -- In .Bd -unfilled, .Pp should produce one blank line, not two; - see the ccd.conf display in OpenBSD ccdconfig(8). - - .Nx 1.0a should be "NetBSD 1.0A", not "NetBSD 1.0a", see OpenBSD ccdconfig(8). @@ -142,20 +142,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). - -- In -T[x]html, Rs/Re need a div. - ************************************************************************ * performance issues ************************************************************************ @@ -171,13 +157,3 @@ 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