At 08:56 AM 8/9/00 +0100, Hildo Biersma wrote:
> > =head1 DESCRIPTION
> >
> > Making what's changed in documentation stand out's quite useful,
> > something I'm coming to appreciate more and more as the RFCs are
> > flying back and forth. The standard way to do this is to mark the
> > changed sections with one or more vertical bars on the left margin.
> >
> > Since changes can themselves be changed, multiple levels of change bar
> > can occur. This mirrors the common practice in printed documentation.
>
>I have a strong feeling this is a bad idea, because:
>- Not everyone is interested in the changes
>- Human authors are fallible, and it's easy to forget changebars
>- We don't want the pods to grow indefinitely
Ah, you misunderstand. I'm not asking that these be required for anyone's
pods (though I would like 'em for the RFCs), merely that the pod syntax
supports it. It's fine with me if the bars are automagically generated, and
I don't much care if the first thing that someone does is run through and
strip out the bars that are 2 (or more) deep already.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
