Skip site navigation (1) Skip section navigation (2)

Re: Switching to XML

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Peter Eisentraut" <peter_e(at)gmx(dot)net>,"David Fetter" <david(at)fetter(dot)org>,"Guillaume Lelarge" <guillaume(at)lelarge(dot)info>,"Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Switching to XML
Date: 2006-12-11 22:00:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
> > > 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?

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).


In response to


pgsql-docs by date

Next:From: Tom LaneDate: 2006-12-11 22:02:12
Subject: Re: Switching to XML
Previous:From: Tom LaneDate: 2006-12-11 21:23:15
Subject: Re: Switching to XML

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group