John, I also started by looking at the XML output from MS Word. I had grandiose ideas of writing a converter from that XML form to something closer to the XML2RFC form, but gave up because it was more daunting than expected. After that I wound up using lots of emacs macros operating on the raw text, and then used hand tuning to add in the comment information. Tony Hansen tony@xxxxxxx John C Klensin wrote: > ... > Getting a simulation of XML out can be done simply by doing a > "save as" from the version of Word included in Office > Professional 2003. The difficulty is that it is > XML-used-as-format-markup, not XML-as-generic markup, and > "MS-XML" at that (i.e., if there is a defined DTD or Schema, it > appears to be only available to and manipulable by their > proprietary tools (and license-prohibited against reverse > engineering). > > I tried to do that conversion with a version of RFC2821bis that > was composed using the RFC3285 template plus a few corrections/ > twitches suggested by colleagues at Microsoft for better Office > 2003 compatibility. I can show pictures of the dents made in > the nearest brick wall by my head, a problem that was aggravated > by the fact that introducing either the 3285 template or yours > into my environment screws up the normal Word working > environment, which I need to keep pretty standard. > > RFC2821bis was finally converted to rfc2xml format on a > one-time, no going back, basis by Tony Hanson. I'm not sure of > exactly what he did, and suspect it involved some hand tuning, > but I at least ended up with something I can work with, get into > I-D form, and revise as I go along. The difficulty, of course, > is that I lost all of the finely-tuned Word change tracking and > comment stuff which was why I used Word in the first place: Tony > converted the comments to XML comments, but that just isn't the > same thing. _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf