Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id B91749F9F75 for ; Sun, 10 Dec 2006 02:02:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 37302-08 for ; Sun, 10 Dec 2006 02:02:59 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 328CA9F9F46 for ; Sun, 10 Dec 2006 02:02:59 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kBA62kAi028994; Sun, 10 Dec 2006 01:02:46 -0500 (EST) To: David Fetter cc: Guillaume Lelarge , "Joshua D. Drake" , Peter Eisentraut , Josh Berkus , pgsql-docs@postgresql.org, David Blewett Subject: Re: Switching to XML In-reply-to: <20061210053926.GB19472@fetter.org> References: <4579720E.4000707@dawninglight.net> <200612082115.53566.peter_e@gmx.net> <1165609294.24745.19.camel@localhost.localdomain> <200612082158.06649.peter_e@gmx.net> <1165613160.24745.36.camel@localhost.localdomain> <457A71F8.6070001@lelarge.info> <20061210053926.GB19472@fetter.org> Comments: In-reply-to David Fetter message dated "Sat, 09 Dec 2006 21:39:26 -0800" Date: Sun, 10 Dec 2006 01:02:46 -0500 Message-ID: <28993.1165730566@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200612/73 X-Sequence-Number: 3996 David Fetter writes: > In addition to the long-standing problem that there is no way to edit > the SGML docs with any known GUI tool, The point not in evidence is that there exists a GUI tool we'd accept for editing XML-format docs. Can you point to some that don't mess up XML source code to the point of being unreadable? > ... That Tom found > a need to fork a document tool, i.e. take ownership of a whole large > piece of software, that being what forking means, is a neon sign that > means, "we're stuck with broken tools." Um, I spend all day every day on making sometimes-comparable improvements in Postgres. Will you abandon Postgres as soon as someone points out a(nother) serious performance bug in it? As for "fork", I have no intention of forking anything --- that patch is already submitted upstream. regards, tom lane