Subject: Re: Switching to XML
From: "Joshua D. Drake" <jd@commandprompt.com>
To: Magnus Hagander <mha@sollentuna.net>
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
In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCEA0FDF2@algol.sollentuna.se>
References: <6BCB9D8A16AC4241919521715F4D8BCEA0FDF2@algol.sollentuna.se>
Content-Type: text/plain
Organization: Command Prompt, Inc.
Date: Mon, 11 Dec 2006 13:07:03 -0800
Message-Id: <1165871223.19970.105.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Mon, 2006-12-11 at 21:56 +0100, Magnus Hagander wrote:
> > 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.
> 
> Visual Studio has a *very* nice XML editor these days, and they don't do
> SGML...
> 
> (ok, ok, that's a joke. It's true, sure, but it's not very relevant...)

Actually it might be for Windows developers wishing to develop Windows
specific sections. How does it work with Docbook?

Sincerely,

Joshua D. Drake


> 
> //Magnus
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 
-- 

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate