Hi -
From: "Julian Reschke" <julian(_dot_)reschke(_at_)gmx(_dot_)de>
To: "Randy Presuhn" <randy_presuhn(_at_)mindspring(_dot_)com>
Cc: "IETF Discussion Mailing List" <ietf(_at_)ietf(_dot_)org>
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 mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf