Re: Automatically updated Table of Contents with Nroff

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi -

> From: "Julian Reschke" <julian.reschke@xxxxxx>
> To: "Randy Presuhn" <randy_presuhn@xxxxxxxxxxxxxx>
> Cc: "IETF Discussion Mailing List" <ietf@xxxxxxxx>
> Sent: Wednesday, July 15, 2009 10:13 AM
> Subject: Re: Automatically updated Table of Contents with Nroff
...
> Point is: nroff and xml2rfc share the advantage that they are simple 
> text based formats, which can be put under version control, and 
> collaborative editing/change control just works. Missing features can 
> simply implemented using automated pre- or post-processing stages.
...

With respect to boilerplate, xml2rfc lacks this advantage.
*It* generates the boilerplate; the user has no way of knowing whether
the option present in the source file will result in the same output
text today as it did yesterday.  From a configuration management /
revision control perspective, this is highly undesirable.  It would be
much better to be able to "#include" a versioned source file for
those bits.

Randy

_______________________________________________

Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]