************************************************************************
* Official mandoc TODO.
-* $Id: TODO,v 1.43 2010/09/04 18:52:21 kristaps Exp $
+* $Id: TODO,v 1.49 2010/09/25 15:29:12 kristaps Exp $
************************************************************************
************************************************************************
try e.g. .Bl -column It Ta Ta
reported by millert Fri, 02 Apr 2010 16:13:46 -0400
-- %A doesn't put an "and" before the final author name.
+- 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
Opening punctuation should not fall out of .Ns.
see for example OpenBSD csh(1)
-- .%A should append the last author with " and " (if there are two)
- or ", and " (if there are more), not ", "
- see for example OpenBSD csh(1)
-
- In .Bl -bullet, the groff bullet is "+\b+\bo\bo", the mandoc bullet
is just "o\bo".
see for example OpenBSD ksh(1)
see "The route utility provides the following simple commands:"
in OpenBSD route(8).
+- In -T[x]html, Rs/Re need a div.
+
************************************************************************
* performance issues
************************************************************************
* 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.