Burakkucat has pointed out to me that the config file is just XML.
The XML config is longwinded and scary-looking, so if I were feeling very energetic, I could
generate a config from a vastly simplified XML source doc by using an XSL transformation. I love XSLT. :-)
If I should ever get round to this, I will of course post the relevant .xsl file up, together with a tool I wrote to run XSL transformations under Windows (using the free MSXML6 library). The tool, if I can ever find where I put it, actually is capable of running a chained pipeline if XSLT transformations, like a UNIX pipe, output to XML or arbitrary text of some sort. I'm sure that other o/s have a fairly easy way of running some XSLT engine. The WinNT tool I wrote uses a batch file and some JS.