![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to TODO CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [cvsweb.bsd.lv] / mandoc|
Return to TODO CVS log | Up to [cvsweb.bsd.lv] / mandoc |
| version 1.44, 2010/09/04 19:01:52 | version 1.52, 2010/09/25 16:52:15 | ||
|---|---|---|---|
|
|
||
| try e.g. .Bl -column It Ta Ta | try e.g. .Bl -column It Ta Ta | ||
| reported by millert Fri, 02 Apr 2010 16:13:46 -0400 | 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 | * formatting issues: gratuitious differences | ||
| ************************************************************************ | ************************************************************************ | ||
|
|
||
| on the next line, it must be indented by -width, not width+1; | on the next line, it must be indented by -width, not width+1; | ||
| see "rule block|pass" in OpenBSD ifconfig(8). | 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, | - Bogus .Pp before .Bl should not cause a double blank line, | ||
| see "The route utility provides the following simple commands:" | see "The route utility provides the following simple commands:" | ||
| in OpenBSD route(8). | in OpenBSD route(8). | ||
|
|
||
| * structural issues | * structural issues | ||
| ************************************************************************ | ************************************************************************ | ||
| - rendering frontend code can calculate widths only for plain strings, | - remove superfluous NOSPACE invocations (e.g., with term_word(p, "(")) | ||
| 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. |