public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: Steve Atkins <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Documentation and explanatory diagrams
Date: Sun, 18 Jul 2010 00:46:30 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Tom Lane wrote:
> Steve Atkins <[email protected]> writes:
> > On Jul 16, 2010, at 7:20 PM, Robert Haas wrote:
> >> Unless I'm misunderstanding what you're talking about here, this is a
> >> really, really bad idea.
>
> > You're misunderstanding.
>
> Yeah, I think that in the main you guys are in violent agreement.
>
> > My feeling is that SVG is a decent lowest common denominator.
>
> I think this might be true in principle but not necessarily in
> practice. For example, if two tools write out SVG with different
> whitespace layout, that's going to kill diff-ing and VCS friendliness.
> This could probably be worked around, eg by settling on some particular
> tool as the one to run it through before committing (sort of a pgindent
> for graphics). But we need to do some experimentation with specific
> tools and see what the output really looks like and how it changes
> given small changes in the diagram, before we choose anything.
Well, if we want _any_ images for the 9.0 docs, we had better decide
soon.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
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]
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