Date: Tue, 27 Feb 2018 12:19:14 -0300
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Craig Ringer <craig@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	Steve Atkins <steve@blighty.com>, pgsql-docs@lists.postgresql.org
Subject: Re: Images in the official documentation
Message-ID: <20180227151914.2xtoygrwlm357fqo@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3f20469f-57b0-33cc-6bcc-e92316d52cbd@2ndquadrant.com>
User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0)
Precedence: bulk

Peter Eisentraut wrote:
> On 2/26/18 20:02, Craig Ringer wrote:
> > If I were maintaining the docs in a vacuum, I'd use graphviz for
> > something like that, because it's a figure that does need regular
> > updates and changes. And because
> >  the list of fun things to do in my life definitely does not include
> > hand-writing SVG. Not that tweaking GraphViz .dot is fun, but it's the
> > default tool for a reason.
> > 
> > I'd be awfully tempted to generate the node-map part of the catalog
> > relationship .dot file from a query, too.
> 
> I think graphviz would be a great fit for what we are discussing here.
> Certainly more so then some-person-on-github's latest idea for how to
> convert ASCII art into diagrams.

... particularly so if said idea involves PHP, Haskell, Go, Python, or
any other language that we don't currently have as requirement in our
build chain.

GraphViz gets my vote, too.  It may not produce the most elegant
diagrams in the universe, but the source format is as good as we can
get.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services