public inbox for [email protected]  

help / color / mirror / Atom feed

From: Rafael Martinez <[email protected]>
To: Robert Haas <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Thom Brown <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: pgsql-docs <[email protected]>
Cc: Marc Fournier <[email protected]>
Subject: Re: Documentation and explanatory diagrams
Date: Sun, 4 Jul 2010 20:49:33 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>


Robert Haas wrote:
> On Sat, Jul 3, 2010 at 7:14 PM, Tom Lane <[email protected]> wrote:
>> Robert Haas <[email protected]> writes:
>>> Seems like a good one.  But I'd still like to know the answer to the
>>> question I asked upthread - how is anyone supposed to generate images
>>> this way?
>>
>> Hmm, judging from
>> http://live.gnome.org/Dia
>>
>> the answer is that .dia files aren't meant to be human readable but only
>> to be a storage format for WYSIWYG editing.  I find this less than
>> thrilling: it essentially means you *can't* edit the images any other
>> way than using dia.  (I'd bet a nickel that any small change results in
>> massive changes in the file contents, too, which will be un-fun for
>> keeping them in a VCS.)
>
> Anyone know of any other alternatives we could investigate?
>

All this was tested and sent to the list in april 2010. Check this post for more
information:

http://archives.postgresql.org/pgsql-docs/2010-04/msg00038.php

As you can see, any small change does not result in massive changes in the file
contents.

-- 
Rafael Martinez, <[email protected]>
Center for Information Technology Services
University of Oslo, Norway

PGP Public Key: http://folk.uio.no/rafael/

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], [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