All of this is interesting reading indeed and reveals stuff that I did not know about. However, I have never regarded boilerplate issues as something that has bothered me a lot when writing a draft. These boilerplates are pretty stable and once you got them in place in the first draft (often by copying them from another document) you can mostly forget about them. Id-nits will always scream if you need to update. What I personally has felt as the major void is an easy way to see your finished product, not after, but during edit. I don't want to save my current edit to a file and enter it into some kind of tool to see what I write. I want to see it while I'm editing. E.g. what happens if I include a page break here? Does it look better if I add an extra line or should I keep this section on same page?, etc. I've learned that there are trivial ways to solve many hard issues like TOC generation in nroff. Seeing how its done it appears trivial only if you know how to do it and if you are prepared to expand your knowledge about nroff quite a bit. And you still won't see the result while you edit. /Stefan On 09-07-16 7:15 AM, "Julian Reschke" <julian.reschke@xxxxxx> wrote: > Randy Presuhn wrote: >> 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 >> ... >>> And of course you can do that with xml2rfc as well; just automate the >>> process of converting the source file to something that can be included >>> into the XML source using the standard XML include mechanisms. >> .... >> >> I couldn't find such mechanisms described anywhere the first time I used >> xml2rfc. >> I just looked at the W3C website XML pages, and still am unable to find them. >> How does one do a simple ".so" or a "#include" in XML? > > <http://xml.resource.org>, see under "Helpful Hints / Including Files". > That page also links to <http://tools.ietf.org/tools/templates/> with > templates. Look, for instance, at > <http://tools.ietf.org/tools/templates/template-edu-xml2rfc.xml>. > > In the XML spec, look for "external entities" > (<http://www.w3.org/TR/REC-xml/#sec-external-ent>). > > There are other inclusion mechanisms; xml2rfc supports a processing > instruction: > <http://xml.resource.org/authoring/README.html#include.file.facility> (I > don't like this one as it is specific to the xml2rfc processor). > > And then, because it's XML, preprocessing is easy; such as with XInclude > mentioned by Marc Petit-Huguenin. > > Hope this helps, Julian > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf _______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf