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

Re: Authoring Tools WAS: Switching to XML

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: josh(at)agliodbs(dot)com, pgsql-docs(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, David Fetter <david(at)fetter(dot)org>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Subject: Re: Authoring Tools WAS: Switching to XML
Date: 2006-12-14 21:37:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
On Thu, 2006-12-14 at 15:34, Tom Lane wrote:
> Scott Marlowe <smarlowe(at)g2switchworks(dot)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.

In response to

pgsql-docs by date

Next:From: Bruce MomjianDate: 2006-12-15 01:22:03
Subject: Re: [DOCS] 8.2.0 pdf
Previous:From: Tom LaneDate: 2006-12-14 21:34:06
Subject: Re: Authoring Tools WAS: Switching to XML

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