version 1.45, 2010/09/08 11:57:29 |
version 1.48, 2010/09/23 19:52:36 |
|
|
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 |
************************************************************************ |
************************************************************************ |
Line 172 Several areas can be cleaned up to make mandoc even fa |
|
Line 175 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: |
- another example of the same problem: |
.Bl -tag -width "\eD{format}XX" -compact |
.Bl -tag -width "\eD{format}XX" -compact |
in OpenBSD ksh(1) gives the wrong width |
in OpenBSD ksh(1) gives the wrong width |
because "\e" is one character in groff, two in mandoc |
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. |
|