[BACK]Return to TODO CVS log [TXT][DIR] Up to [cvsweb.bsd.lv] / mandoc

Diff for /mandoc/TODO between version 1.96 and 1.104

version 1.96, 2011/03/23 22:16:03 version 1.104, 2011/04/30 10:18:24
Line 16 
Line 16 
   .br \}    .br \}
   reported by ulrich spoerlein  Tue, 19 Oct 2010 20:39:50 +0200    reported by ulrich spoerlein  Tue, 19 Oct 2010 20:39:50 +0200
   
 - \. at the start of the line does *not* prevent interpretation  
   of the following word as a macro.  
   Werner LEMBERG on bug-groff@  Tue, 22 Mar 2011 14:21:28 +0100  
   http://lists.gnu.org/archive/html/bug-groff/2011-03/msg00011.html  
   
 ************************************************************************  ************************************************************************
 * formatter bugs  * 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 features
 ************************************************************************  ************************************************************************
Line 56 
Line 56 
   
 - \c (interrupted text) occurs in chat(8)  - \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 ----------------------------------------------  --- missing mdoc features ----------------------------------------------
   
 - fix bad block nesting involving multiple identical explicit blocks  - fix bad block nesting involving multiple identical explicit blocks
Line 91 
Line 96 
 - explicitly disallow nested `Bl -column', which would clobber internal  - explicitly disallow nested `Bl -column', which would clobber internal
   flags defined for struct mdoc_macro    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 <akfaew at jasminek dot net>
     via jmc@ Thu, 7 Apr 2011 16:00:53 +0059
   
 - inside `.Bl -column' phrases, punctuation is handled like normal  - inside `.Bl -column' phrases, punctuation is handled like normal
   text, e.g. `.Bl -column .It Fl x . Ta ...' should give "-x -."    text, e.g. `.Bl -column .It Fl x . Ta ...' should give "-x -."
   
Line 108 
Line 123 
   
 --- missing man features -----------------------------------------------  --- 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:
   
 - groff an-ext.tmac macros (.UR, .UE) occur in xine(5)  - groff an-ext.tmac macros (.UR, .UE) occur in xine(5)
   reported by brad@  Sat, 15 Jan 2011 15:45:23 -0500    reported by brad@  Sat, 15 Jan 2011 15:45:23 -0500
   
Line 183 
Line 201 
   reminded by jmc@  Thu, 23 Sep 2010 18:13:39 +0059    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  - .Rv (and probably .Ex) print different text if an `Nm' has been named
Line 206 
Line 224 
   Also have `It' complain if `Pp' is invoked at certain times (not    Also have `It' complain if `Pp' is invoked at certain times (not
   -compact?).    -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  - If the *first* line after .It is .Pp, break the line right after
   the tag, do not pad with space characters before breaking.    the tag, do not pad with space characters before breaking.
   See the description of the a, c, and i commands in sed(1).    See the description of the a, c, and i commands in sed(1).
Line 263 
Line 285 
     .IP      .IP
   should have a blank line between the text and the beginning of the    should have a blank line between the text and the beginning of the
   indented paragraph, see for example sudo(1).    indented paragraph, see for example sudo(1).
   
   - In man(7), the sequence
       .SH HEADER
       <blank line>
       .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
       <blank line>
       .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).  - At least sometimes, .sp is ignored right after .SH; see named.conf(5).
   
Legend:
Removed from v.1.96  
changed lines
  Added in v.1.104
CVSweb