===================================================================
RCS file: /cvs/mandoc/TODO,v
retrieving revision 1.80
retrieving revision 1.104
diff -u -p -r1.80 -r1.104
--- mandoc/TODO 2011/01/22 20:36:02 1.80
+++ mandoc/TODO 2011/04/30 10:18:24 1.104
@@ -1,12 +1,15 @@
************************************************************************
* Official mandoc TODO.
-* $Id: TODO,v 1.80 2011/01/22 20:36:02 schwarze Exp $
+* $Id: TODO,v 1.104 2011/04/30 10:18:24 kristaps Exp $
************************************************************************
************************************************************************
* parser bugs
************************************************************************
+- .TP before .SH is still FATAL in man(7)
+ reported by brad@ Sat, 15 Jan 2011 15:54:54 -0500
+
- the roff parser doesn't tolerate additional characters between
a macro and the \} terminating a conditional block, e.g.
.if n \{
@@ -17,19 +20,47 @@
* formatter bugs
************************************************************************
+- tbl(7): Horizontal and vertical lines are formatted badly:
+ With the box option, there is too much white space at the end of cells.
+ Horizontal lines from "=" lines are a bit too long.
+ yuri dot pankov at gmail dot com Thu, 14 Apr 2011 05:45:26 +0400
+
************************************************************************
* missing features
************************************************************************
--- missing roff features ----------------------------------------------
+- .ad (adjust margins)
+ .ad l -- adjust left margin only (flush left)
+ .ad r -- adjust right margin only (flush right)
+ .ad c -- center text on line
+ .ad b -- adjust both margins (alias: .ad n)
+ .na -- temporarily disable adjustment without changing the mode
+ .ad -- re-enable adjustment without changing the mode
+ Adjustment mode is ignored while in no-fill mode (.nf).
+
+- .it (line traps) occur in mysql(1), yasm_arch(7)
+ generated by DocBook XSL Stylesheets v1.71.1
+ reported by brad@ Sat, 15 Jan 2011 15:48:18 -0500
+
- .ns (no-space mode) occurs in xine-config(1)
reported by brad@ Sat, 15 Jan 2011 15:45:23 -0500
- xloadimage(1) wants .ti (temporary indent), rep by naddy@
+- .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)
+
+- \f(CW (constant width font) occurs in rsyncd.conf(5).
+ I think we should treat unknown/unavailable fonts as \fR
+ such that switching back with \fP works correctly -
+ and doesn't revert the _previous_ \fP.
+
--- missing mdoc features ----------------------------------------------
- fix bad block nesting involving multiple identical explicit blocks
@@ -53,6 +84,10 @@
because libmdoc does not yet use mandoc_getarg().
Also check what happens in plain text, it must be identical to \e.
+- .Bd -filled should not be the same as .Bd -ragged, but align both
+ the left and right margin. In groff, it is implemented in terms
+ of .ad b, which we don't have either. Found in cksum(1).
+
- implement blank `Bl -column', such as
.Bl -column
.It foo Ta bar
@@ -61,6 +96,16 @@
- explicitly disallow nested `Bl -column', which would clobber internal
flags defined for struct mdoc_macro
+- In .Bl -column .It, the end of the line probably has to be regarded
+ as an implicit .Ta, if there could be one, see the following mildly
+ ugly code from login.conf(5):
+ .Bl -column minpasswordlen program xetcxmotd
+ .It path Ta path Ta value of Dv _PATH_DEFPATH
+ .br
+ Default search path.
+ reported by Michal Mazurek
+ via jmc@ Thu, 7 Apr 2011 16:00:53 +0059
+
- inside `.Bl -column' phrases, punctuation is handled like normal
text, e.g. `.Bl -column .It Fl x . Ta ...' should give "-x -."
@@ -78,11 +123,8 @@
--- missing man features -----------------------------------------------
-- bashbug(1) complains "line scope broken" after
- .SM
- .B something
- should either just work or be a warning
- reported by naddy@
+- .RS/.RE can be nested, see e.g. the x11/fluxbox manuals
+ noticed by dcoppa@ Wed, Apr 13, 2011 at 04:58:14PM +0200:
- groff an-ext.tmac macros (.UR, .UE) occur in xine(5)
reported by brad@ Sat, 15 Jan 2011 15:45:23 -0500
@@ -102,6 +144,14 @@
see textproc/mgdiff(1) for nice examples
(3) undefined, just output the character -> perhaps WARNING
+- The \t escape sequence is the same as a literal tab, see for example
+ the ASCII table in hexdump(1) where
+ .Bl -column \&000_nu \&001_so \&002_st \&003_et \&004_eo
+ .It \&000\ nul\t001\ soh\t002\ stx\t003\ etx\t004\ eot\t005\ enq
+ produces
+ 000 nul 001 soh 002 stx 003 etx 004 eot 005 enq
+ and the example in oldrdist(1)
+
- look at pages generated from reStructeredText, e.g. devel/mercurial hg(1)
These are a weird mixture of man(7) and custom autogenerated low-level
roff stuff. Figure out to what extent we can cope.
@@ -118,6 +168,9 @@
* formatting issues: ugly output
************************************************************************
+- a column list with blank `Ta' cells triggers a spurrious
+ start-with-whitespace printing of a newline
+
- double quotes inside double quotes are escaped by doubling them
implement this in mdoc(7), too
so far, we only have it in roff(7) and man(7)
@@ -135,11 +188,20 @@
try e.g. .Bl -column It Ta Ta
reported by millert Fri, 02 Apr 2010 16:13:46 -0400
+- .%T can have trailing punctuation. Currently, it puts the trailing
+ punctuation into a trailing MDOC_TEXT element inside its own scope.
+ That element should rather be outside its scope, such that the
+ punctuation does not get underlines. This is not trivial to
+ implement because .%T then needs some features of in_line_eoln() -
+ slurp all arguments into one single text element - and one feature
+ of in_line() - put trailing punctuation out of scope.
+ Found in mount_nfs(8) and exports(5), search for "Appendix".
+
- 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: gratuitous differences
************************************************************************
- .Rv (and probably .Ex) print different text if an `Nm' has been named
@@ -157,10 +219,23 @@
- A bogus .Pp between two .It must not produce a double blank line,
see between -R and -r in OpenBSD rm(1), before "update" in mount(8),
- or in DIAGNOSTICS in init(8).
+ or in DIAGNOSTICS in init(8), or before "is always true" in ksh(1).
+ The same happens with .Pp just before .El, see bgpd.conf(5).
Also have `It' complain if `Pp' is invoked at certain times (not
-compact?).
+- .Pp between two .It in .Bl -column should produce one,
+ not two blank lines, see e.g. login.conf(5).
+ reported by jmc@ Sun, 17 Apr 2011 14:04:58 +0059
+
+- If the *first* line after .It is .Pp, break the line right after
+ the tag, do not pad with space characters before breaking.
+ See the description of the a, c, and i commands in sed(1).
+
+- If the first line after .It is .D1, do not assert a blank line
+ in between, see for example tmux(1).
+ reported by nicm@ 13 Jan 2011 00:18:57 +0000
+
- .Nx 1.0a
should be "NetBSD 1.0A", not "NetBSD 1.0a",
see OpenBSD ccdconfig(8).
@@ -169,6 +244,12 @@
on the next line, it must be indented by -width, not width+1;
see "rule block|pass" in OpenBSD ifconfig(8).
+- When the -width string contains macros, the macros must be rendered
+ before measuring the width, for example
+ .Bl -tag -width ".Dv message"
+ in magic(5), located in src/usr.bin/file, is the same
+ as -width 7n, not -width 11n.
+
- The \& zero-width character counts as output.
That is, when it is alone on a line between two .Pp,
we want three blank lines, not two as in mandoc.
@@ -177,11 +258,86 @@
should be indented, see e.g. rpc(3);
reported by jmc@ on discuss@ Fri, 29 Oct 2010 13:48:33 +0100
+- .Ns should work when called at the end of an input line, see
+ the following code in vi(1):
+ .It Xo
+ .Op Ar line
+ .Cm a Ns Op Cm ppend Ns
+ .Op Cm !\&
+ .Xc
+ The input text is appended after the specified line.
+
- Header lines of excessive length:
Port OpenBSD man_term.c rev. 1.25 to mdoc_term.c
and document it in mdoc(7) and man(7) COMPATIBILITY
found while talking to Chris Bennett
+- In man(7), the sequence
+ .HP
+ one line of regular text
+ .SH
+ should not produce two blank lines before the .SH,
+ 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
+ regular text
+ should not produce any blank lines between the header and the text,
+ see for example rsync(1).
+ Reported by naddy@ Mon, 28 Mar 2011 20:45:42 +0200
+
+- 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
+ should produce one, not four blank lines between the regular text
+ and the tag, see for example rsync(1).
+ Likewise,
+ regular text
+ .IP
+ indented text
+ should produce one, not two blank lines in between, and
+ regular text
+ .IP
+ .RS
+ .IP tag
+ indented text
+ 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
+ \fBdig \fR
+ operate in batch mode
+ in dig(1).
+
************************************************************************
* error reporting issues
************************************************************************
@@ -204,4 +360,8 @@ Several areas can be cleaned up to make mandoc even fa
- Find better ways to prevent endless loops
in roff(7) macro and string expansion.
-
+
+- Finish cleanup of date handling.
+ Decide which formats should be recognized where.
+ Update both mdoc(7) and man(7) documentation.
+ Triggered by Tim van der Molen Tue, 22 Feb 2011 20:30:45 +0100