Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Switching to XML
Date: Mon, 11 Dec 2006 23:00:35 +0100
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCEA0FDF3@algol.sollentuna.se>
In-Reply-To: <1165871223.19970.105.camel@localhost.localdomain>
Thread-Topic: [DOCS] Switching to XML
Thread-Index: AccdaBVabV1tcTk9T+STK2Jzt9Av4gAB49xg
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: "Tom Lane" <tgl@sss.pgh.pa.us>, "Peter Eisentraut" <peter_e@gmx.net>,
	"David Fetter" <david@fetter.org>,
	"Guillaume Lelarge" <guillaume@lelarge.info>,
	"Josh Berkus" <josh@agliodbs.com>, <pgsql-docs@postgresql.org>

> > > The real problem here is that you've still failed to=20
> establish any=20
> > > sizable benefit from converting.  As best I can tell at=20
> the moment,=20
> > > the acceptable options for editing XML will be about the same as=20
> > > they are for SGML: emacs, and not a lot else.  I don't really see=20
> > > why I should have to start spelling out every closing tag for a=20
> > > no-op like that.
> >=20
> > Visual Studio has a *very* nice XML editor these days, and=20
> they don't=20
> > do SGML...
> >=20
> > (ok, ok, that's a joke. It's true, sure, but it's not very=20
> > relevant...)
>=20
> Actually it might be for Windows developers wishing to=20
> develop Windows specific sections. How does it work with Docbook?

It works just fine with any XML inlcluding docbook. It does your basic
syntax highlighting, autoindenting and things like that. You can teach
it about things like docbook to get autocomplete on tags and attributes,
but I don't know if anybody has done that (I certainly haven't).

//Magnus