Subject: Re: Authoring Tools WAS: Switching to XML
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: josh@agliodbs.com, pgsql-docs@postgresql.org,
	Bruce Momjian <bruce@momjian.us>, Peter Eisentraut <peter_e@gmx.net>,
	"Joshua D. Drake" <jd@commandprompt.com>, David Fetter <david@fetter.org>,
	Guillaume Lelarge <guillaume@lelarge.info>
In-Reply-To: <25332.1166132046@sss.pgh.pa.us>
References: <200612131714.kBDHEI800289@momjian.us>
	<200612141258.44479.josh@agliodbs.com>
	<1166131397.3243.181.camel@state.g2switchworks.com>
	<25332.1166132046@sss.pgh.pa.us>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1166132220.3243.184.camel@state.g2switchworks.com>
Mime-Version: 1.0
Date: Thu, 14 Dec 2006 15:37:01 -0600

On Thu, 2006-12-14 at 15:34, Tom Lane wrote:
> Scott Marlowe <smarlowe@g2switchworks.com> writes:
> > On Thu, 2006-12-14 at 14:58, Josh Berkus wrote:
> >> It would be more accurate to say that we have not identified a WYSWYG tool 
> >> which does not mess up the source.  There may be one, it would just take a 
> >> fair amount of testing to find it.
> 
> > Is this strictly a question of indentation, or one of actually mangling
> > tags and such?
> 
> What we need is something that does not change regions of the file that
> the user did not intend to modify.  I think horizonal-white-space-only
> changes could be worked around if the user is careful to use diff
> --ignore-space-change when submitting the patch, but I suspect that an
> editor that thinks it can mangle whitespace will also figure that it can
> change line boundaries, and then diff will never be able to extract any
> signal from that noise.

Ahhhh.  I see.

Well, I don't mind teaching myself some docbook, but the first time I
looked at adding to the docs I was overwhelmed with what I didn't know,
and didn't even see a starting point.  I'll look in the appendices and
see what I can see.