mandoc/TODO - diff

Return to TODO CVS log

Up to [cvsweb.bsd.lv] / mandoc

Diff for /mandoc/TODO between version 1.107 and 1.121

version 1.107, 2011/05/21 21:38:17

version 1.121, 2011/09/18 16:43:28

Line 7

* parser bugs

************************************************************************

- ".\}" on its own line gets translated to bare ".\&"

which forces pset() into man(7)

and then triggers an unknown macro error

reported by naddy@ Sun, 3 Jul 2011 21:52:24 +0200

- .TP before .SH is still FATAL in man(7)

reported by brad@ Sat, 15 Jan 2011 15:54:54 -0500

also occurs in emulators/pcsxr/patches/patch-doc_pcsx_1

jeremy@ commit Wed, 7 Sep 2011 10:00:19 -0600 (MDT)

- the roff parser doesn't tolerate additional characters between

a macro and the \} terminating a conditional block, e.g.

.if n \{

.br \}

reported by ulrich spoerlein Tue, 19 Oct 2010 20:39:50 +0200

************************************************************************

* formatter bugs

************************************************************************

Line 31

Line 32

--- missing roff features ----------------------------------------------

- .if n \{

.br\}

should cause an extra space to be raised.

- .ad (adjust margins)

.ad l -- adjust left margin only (flush left)

.ad r -- adjust right margin only (flush right)

Line 52

Line 57

- .ta (tab settings) occurs in ircbug(1) and probably gnats(1)

reported by brad@ Sat, 15 Jan 2011 15:50:51 -0500

- pod2man expects `tr' to be implemented for \*(-- to work

- \c (interrupted text) occurs in chat(8)

--- missing mdoc features ----------------------------------------------

Line 116

Line 119

(e.g., NetBSD mDNSShared/dns-sd.1)

(mdoc_html.c and mdoc_term.c `Nm' handlers can be slightly simplified)

- When there is free text in the SYNOPSIS and that free text contains

the .Nm macro, groff somehow understands to treat the .Nm as an in-line

macro, while mandoc treats it as a block macro and breaks the line.

No idea how the logic for distinguishing in-line and block instances

should be, needs investigation.

uqs@ Thu, 2 Jun 2011 11:03:51 +0200

uqs@ Thu, 2 Jun 2011 11:33:35 +0200

--- missing man features -----------------------------------------------

- .RS/.RE can be nested, see e.g. the x11/fluxbox manuals

noticed by dcoppa@ Wed, Apr 13, 2011 at 04:58:14PM +0200:

also affects p5-Net-SFTP-Foreign-1.65

as reported by gsoares@ Wed, 18 May 2011 09:59:06 -0300

- groff an-ext.tmac macros (.UR, .UE) occur in xine(5)

reported by brad@ Sat, 15 Jan 2011 15:45:23 -0500

- -T[x]html doesn't stipulate non-collapsing spaces in literal mode

--- missing tbl features -----------------------------------------------

- implement basic non-parametric .de to support e.g. sox(1)

Line 258

Line 266

- When .Fn arguments exceed one output line, all but the first

should be indented, see e.g. rpc(3);

reported by jmc@ on discuss@ Fri, 29 Oct 2010 13:48:33 +0100

reported again by Nicolas Joly via wiz@ Sun, 18 Sep 2011 18:24:40 +0200

Also, we don't want to break the line within the argument of:

.Fa "chtype tl"

- .Ns should work when called at the end of an input line, see

the following code in vi(1):

Line 281

Line 292

see for example named-checkconf(8).

- In man(7), the sequence

regular text

.RS

.IP

should have a blank line between the text and the beginning of the

indented paragraph, see for example sudo(1).

- In man(7), the sequence

.SH HEADER

.PP

Line 298

Line 302

- In man(7), the sequence

regular text

.PP

.RS

indented text

should produce one blank line between the regular and indented texts,

see for example rsync(1), and

.RE

.PP

.RS

should produce two,not one blank lines.

Reported by naddy@ Mon, 28 Mar 2011 20:45:42 +0200

- In man(7), the sequence

regular text

.IP

.IP "tag"

indented text

Line 330

Line 320

should produce one, not three blank lines.

Reported by naddy@ Mon, 28 Mar 2011 20:45:42 +0200

- At least sometimes, .sp is ignored right after .SH; see named.conf(5).

- trailing whitespace must be ignored even when followed by a font escape,

see for example

makes

Line 354 Several areas can be cleaned up to make mandoc even fa

Line 342 Several areas can be cleaned up to make mandoc even fa

- improve hashing mechanism for characters (not as important)

- the PDF file is HUGE: this can be reduced by using relative offsets

- instead of re-initialising the roff predefined-strings set before each

parse, create a read-only version the first time and copy it

************************************************************************

* structural issues

CVSweb