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


> > 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.
> 
> Could post-processing with tidy clean this up?  I'm pretty sure that
> tidy's output is deterministic, at least if the editor hasn't mangled
> tags...
> 

Yes tidy makes things pretty darn clean. However, there is one thing
that it won't do and that is remove extra tags. Thus something like
OpenOffice is still a no-op.

Joshua D. Drake

> Cheers,
> D
-- 

      === 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