"Joshua D. Drake" <jd@commandprompt.com> writes:
> Secondly the make postgres.xml would be a one time thing.
Agreed, the cost of conversion is one-time ... but it's not small.
Aside from getting the files themselves converted, there's the effort
for people to find, install, and learn suitable tools, not to mention
come up to speed on the differences between xml and sgml. (I assume
there are some significant ones, else why are we having this discussion?)
The real problem here is that you've still failed to establish any
sizable benefit from converting. As best I can tell at the moment,
the acceptable options for editing XML will be about the same as they
are for SGML: emacs, and not a lot else. I don't really see why I
should have to start spelling out every closing tag for a no-op like
that.
regards, tom lane
