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:04:57 +0100
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCEA0FDF4@algol.sollentuna.se>
In-Reply-To: <16510.1165874532@sss.pgh.pa.us>
Thread-Topic: [DOCS] Switching to XML 
Thread-Index: AccdcAySx4B8aRjeRbmuFSBjdq1C+AAAC7qQ
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Joshua D. Drake" <jd@commandprompt.com>,
	"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>

> >>> Visual Studio has a *very* nice XML editor these days, and they=20
> >>> don't do SGML...
> >>>=20
> >>> (ok, ok, that's a joke. It's true, sure, but it's not very
> >>> relevant...)
> >>=20
> >> Actually it might be for Windows developers wishing to develop=20
> >> Windows specific sections. How does it work with Docbook?
>=20
> > It works just fine with any XML inlcluding docbook. It does=20
> your basic=20
> > syntax highlighting, autoindenting and things like that.=20
> You can teach=20
> > it about things like docbook to get autocomplete on tags and=20
> > attributes, but I don't know if anybody has done that (I=20
> certainly haven't).
>=20
> How is it on the point of not introducing random reformatting=20
> into the XML source text?

it doesn't do it, period. Just to be clear, it's a XML *source* editor.
Just like emacs, excpet prettier ;-)

(and just for the record, these days even the GUI editors in Visual
Studio generally do a very good job of not breaking your manually tuned
markup, but there is no GUI editor for docbook)

//Magnus