public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Fetter <[email protected]>
To: Tom Lane <[email protected]>
Cc: Scott Marlowe <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: Bruce Momjian <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: Guillaume Lelarge <[email protected]>
Subject: Re: Authoring Tools WAS: Switching to XML
Date: Thu, 14 Dec 2006 22:15:16 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Thu, Dec 14, 2006 at 04:34:06PM -0500, Tom Lane wrote:
> Scott Marlowe <[email protected]> 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.

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

Cheers,
D
-- 
David Fetter <[email protected]> http://fetter.org/
phone: +1 415 235 3778        AIM: dfetter666
                              Skype: davidfetter

Remember to vote!

view thread (122+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Authoring Tools WAS: Switching to XML
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox