From: bogus@does.not.exist.com () Date: Sun, 23 Aug 2009 12:19:48 -0000 Subject: No subject Message-ID: location that is kept up-to-date with regard to the boilerplate names, which one(s) are valid, etc. My biggest *practical* problem getting and I-D done with xml2rfc is getting stuck trying to guess the boilerplate name that idnits will pass. In that context, decoupling the boilerplate from the xml2rfc distribution itself is not a good idea -- it requires the baseline user to discover and use the incantation to access the boilerplate. Dale Dale Worley worley at alum.mit.edu -- 668: The Neighbor of the Beast From: bogus@does.not.exist.com () Date: Sun, 23 Aug 2009 12:19:48 -0000 Subject: No subject Message-ID: the time. Known behavior? A note in the readme file would be handy. Thanks, -bill --0-957639532-1273603536=:25340 Content-Type: text/html; charset=us-ascii
It seems I have to source xml2rfc.tcl with the CWD containing all the files form the tarball (less the examples and such).  If I source it form outside that directory I get an odd result (all normal paragraph text centered in the doc).  I unpacked the tarball into a separate directory and did not want to clutter my working directory with it.  From: bogus@does.not.exist.com () Date: Sun, 23 Aug 2009 12:19:48 -0000 Subject: No subject Message-ID: the time. 
 
Known behavior? 
 
A note in the readme file would be handy.
 
Thanks,
 
-bill
--0-957639532-1273603536=:25340--