Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 642929FA2E0 for ; Fri, 15 Dec 2006 02:15:25 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 80839-10 for ; Fri, 15 Dec 2006 02:15:17 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from fetter.org (start.fetter.org [66.92.188.65]) by postgresql.org (Postfix) with ESMTP id BCD719FA2A7 for ; Fri, 15 Dec 2006 02:15:17 -0400 (AST) Received: by fetter.org (Postfix, from userid 500) id 272EAF3D16A; Thu, 14 Dec 2006 22:15:16 -0800 (PST) Date: Thu, 14 Dec 2006 22:15:16 -0800 From: David Fetter To: Tom Lane Cc: Scott Marlowe , josh@agliodbs.com, pgsql-docs@postgresql.org, Bruce Momjian , Peter Eisentraut , "Joshua D. Drake" , Guillaume Lelarge Subject: Re: Authoring Tools WAS: Switching to XML Message-ID: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25332.1166132046@sss.pgh.pa.us> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/160 X-Sequence-Number: 4083 On Thu, Dec 14, 2006 at 04:34:06PM -0500, Tom Lane wrote: > Scott Marlowe 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 http://fetter.org/ phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter Remember to vote!