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

Re: Authoring Tools WAS: Switching to XML

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, 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>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Subject: Re: Authoring Tools WAS: Switching to XML
Date: 2006-12-15 06:39:24
Message-ID: 1166164764.18226.53.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-docs
> > 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




In response to

pgsql-docs by date

Next:From: Peter EisentrautDate: 2006-12-15 09:07:52
Subject: Re: Switching to XML
Previous:From: David FetterDate: 2006-12-15 06:15:16
Subject: Re: Authoring Tools WAS: Switching to XML

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