To: Bruce Momjian <bruce@momjian.us>
cc: "Ross J. Reedstrom" <reedstrm@rice.edu>, Thom Brown <thom@linux.com>,
	Greg Smith <greg@2ndquadrant.com>, pgsql-docs@postgresql.org
Subject: Re: Documentation and explanatory diagrams 
In-reply-to: <201106132334.p5DNYaW01934@momjian.us> 
References: <201106132334.p5DNYaW01934@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Mon, 13 Jun 2011 19:34:36 -0400"
Date: Mon, 13 Jun 2011 20:14:55 -0400
Message-ID: <11932.1308010495@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Bruce Momjian <bruce@momjian.us> writes:
> I think the big question is whether we can afford to allow multiple SVG
> editor file formats to be checked in, and hence support git diff churn
> as we switch SVG editors for commits.  This doesn't seem likely to
> improve anytime soon so we should just decide and move forward.

> 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 think we probably have to specify the One True Graphics Editor, and
maybe even specific version(s) of it, if we want to avoid unreadable
diffs.  The reason we have not managed to come to a consensus yet is
that people would prefer not to do that, but it's becoming obvious that
there just isn't any way around it.

			regards, tom lane