-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
My apologies for the subject line. I'm very disappointed that the silent
majority of draft authors isn't speaking up. I can't imagine that the
vast majority of draft authors has absolutely no problems with XML2RFC.
So I'm assuming they've been ignoring the thread, hopefully the new
subject line will get some of them to chime in. If that doesn't happen
I'll shut up and try to figure out why I have so much trouble with
something that nobody else finds difficult.
I don't mind the XML part of writing the drafts, it's just annoying that
so few DTDs are available to edit the things. There are a ton of
commercial XML editors out there--Word, Dreamweaver, and many others.
But, not being an XML expert, I don't know how to get a DTD to work in
any of these software packages, so editing the XML side is a matter of
hand coding it. <blech>
I think a lot of the problem is the issues with editing these things. If
we had a DTD that worked in other pieces of software, it could be
converted using commonly available software into text formats. The
problem, from my perspective, isn't the format, it's the lack of tools
to work in that format, at this point.
:-)
Russ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkpTWmkACgkQER27sUhU9ORlnwCdF1PckJKO7f0vRO6JdJ2UPdJ+
s/QAmQHnUXbr/DoOPj0YF9YRwkAIPlIU
=72jr
-----END PGP SIGNATURE-----
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf