public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Robert Haas <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Ross J. Reedstrom <[email protected]>
Cc: Thom Brown <[email protected]>
Cc: Greg Smith <[email protected]>
Cc: [email protected]
Subject: Re: Documentation and explanatory diagrams
Date: Tue, 14 Jun 2011 08:59:41 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Robert Haas wrote:
> On Mon, Jun 13, 2011 at 8:46 PM, Tom Lane <[email protected]> wrote:
> > Bruce Momjian <[email protected]> writes:
> >> Tom Lane wrote:
> >>> Bruce Momjian <[email protected]> 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  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

view thread (114+ 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]
  Subject: Re: Documentation and explanatory diagrams
  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