![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
> A premise behind the formatting rules for IETF documents is that they are > easy to create and easy to read. As popular as XML is in the minds of the > technical community, there are few tools for creating it and little > widespread use of it. > > So far. dave - i think this is one of those ymmv things. i know a lot of people who do a lot of xml input using wysiwyg editors. rfc 2629 listed a couple of tools from a couple of years ago, there are a lot more out there now. in other words, i politely question the basis for your assertion above. for myself, i use emacs simply because i can use it to edit all kinds of files on all kinds of systems. this is a trade-off from having xml-specific support, but that's okay. finally, for those folks who are using the rfc2629-based tool called xml2rfc: there is a new release available that generates nroff, in addition to txt (rfc 2223) and html. the reason why it generates nroff is that you can give that to the rfc-editor along with your txt file and it gives them a leg up on their editing process - http://xml.resource.org/ /mtr
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.