version 1.42, 2010/08/20 22:51:29 |
version 1.54, 2010/09/27 10:47:48 |
|
|
- allow `Qq', `Dq', `Sq', `Aq', `Bq' to have 0 arguments |
- allow `Qq', `Dq', `Sq', `Aq', `Bq' to have 0 arguments |
noted by Alex Kozlov 08/06/10 23:05 |
noted by Alex Kozlov 08/06/10 23:05 |
|
|
- 'br\} doesn't correctly close scope. |
|
Noted by joerg@, 28/7/2010. |
|
|
|
************************************************************************ |
************************************************************************ |
* formatting issues: ugly output |
* formatting issues: ugly output |
************************************************************************ |
************************************************************************ |
|
|
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 |
|
|
- %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 |
* formatting issues: gratuitious differences |
|
|
Opening punctuation should not fall out of .Ns. |
Opening punctuation should not fall out of .Ns. |
see for example OpenBSD csh(1) |
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 |
- In .Bl -bullet, the groff bullet is "+\b+\bo\bo", the mandoc bullet |
is just "o\bo". |
is just "o\bo". |
see for example OpenBSD ksh(1) |
see for example OpenBSD ksh(1) |
|
|
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, |
|
see "The route utility provides the following simple commands:" |
|
in OpenBSD route(8). |
|
|
|
************************************************************************ |
************************************************************************ |
* performance issues |
* performance issues |
************************************************************************ |
************************************************************************ |
Line 178 Several areas can be cleaned up to make mandoc even fa |
|
Line 160 Several areas can be cleaned up to make mandoc even fa |
|
************************************************************************ |
************************************************************************ |
* structural 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. |
|