From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201106141259.p5ECxfj28659@momjian.us>
Subject: Re: Documentation and explanatory diagrams
In-Reply-To: <BANLkTikBHP73RT+Ead2GQmd+YzP02x3hQg@mail.gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Date: Tue, 14 Jun 2011 08:59:41 -0400 (EDT)
CC: Tom Lane <tgl@sss.pgh.pa.us>, "Ross J. Reedstrom" <reedstrm@rice.edu>,
	Thom Brown <thom@linux.com>, Greg Smith <greg@2ndquadrant.com>,
	pgsql-docs@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Robert Haas wrote:
> On Mon, Jun 13, 2011 at 8:46 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Bruce Momjian <bruce@momjian.us> writes:
> >> Tom Lane wrote:
> >>> Bruce Momjian <bruce@momjian.us> writes:
> >>>> Perhaps we should allow any SVG file to be imported, but only allow
> >>>> modifications by a single SVG editor.
> >
> >>> How is that sensible? ?The first change to the file will result in
> >>> exactly the mass of cosmetic diffs that we wish to avoid.
> >
> >> I suggested this so we could get images into the docs and then only have
> >> a single diff change once the file is modified. ?If we don't do that
> >> then all image additions have to be done by someone with the proper
> >> editor.
> >
> > Or at least, somebody passes it through the "proper editor" before
> > committing. ?As long as said editor can read SVG output from a
> > reasonable range of other tools, this doesn't seem that onerous.
> 
> Bad news, Bruce: you're going to have to learn a new tool.  :-)

Yes, I am sensing that.  ;-)

Do we have any agreement on which tool will be the definitive one?

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +