version 1.51, 2010/09/25 16:41:33 |
version 1.58, 2010/10/01 21:51:13 |
|
|
- 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 |
|
|
|
- Have `Sh', `It', `Ss' and others complain if `Pp' is invoked prior to |
|
close (in the post validation) or prior to open (pre). This noted by |
|
jmc@ a thousand years ago. |
|
|
************************************************************************ |
************************************************************************ |
* formatting issues: ugly output |
* formatting issues: ugly output |
************************************************************************ |
************************************************************************ |
|
|
to better distinguish the contents of .%T and .%J, |
to better distinguish the contents of .%T and .%J, |
see for example OpenBSD cat(1) |
see for example OpenBSD cat(1) |
|
|
- .It ${name Ns [ selector ] Ns } |
|
should be "${name[selector]}" not "${name [selector]}" |
|
This is parsed as |
|
text("${name") text("[") Ns() text(selector)... |
|
Opening punctuation should not fall out of .Ns. |
|
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) |
|
|
- .No text No ) is "text )", not "text)" |
|
see the terrible example |
|
case word in [[(] pattern [| pattern] ... ) list ;; ] ... esac |
|
in OpenBSD ksh(1) |
|
|
|
- .Sm should *not* produce as a blank line in .Bd -literal |
- .Sm should *not* produce as a blank line in .Bd -literal |
see for example "Brace expansion" in OpenBSD ksh(1) |
see for example "Brace expansion" in OpenBSD ksh(1) |
|
|
|
|
In -unfilled, tabs are 5 spaces, just like in -filled and -ragged. |
In -unfilled, tabs are 5 spaces, just like in -filled and -ragged. |
See the CCDF_* display in OpenBSD ccdconfig(8). |
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 |
- .Nx 1.0a |
should be "NetBSD 1.0A", not "NetBSD 1.0a", |
should be "NetBSD 1.0A", not "NetBSD 1.0a", |
see OpenBSD ccdconfig(8). |
see OpenBSD ccdconfig(8). |
|
|
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, |
- The \& zero-width character counts as output. |
there is no point in rendering two commata, |
That is, when it is alone on a line between two .Pp, |
see the first paragraph of the DESCRIPTION in OpenBSD mount_nfs(8). |
we want three blank lines, not two as in mandoc. |
|
|
- 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 168 Several areas can be cleaned up to make mandoc even fa |
|
Line 153 Several areas can be cleaned up to make mandoc even fa |
|
************************************************************************ |
************************************************************************ |
* structural issues |
* structural issues |
************************************************************************ |
************************************************************************ |
|
|