public inbox for [email protected]  

help / color / mirror / Atom feed

From: Oleg Bartunov <[email protected]>
To: Tom Lane <[email protected]>
Cc: Craig Ringer <[email protected]>
Cc: Steve Atkins <[email protected]>
Cc: [email protected]
Subject: Re: Images in the official documentation
Date: Tue, 27 Feb 2018 11:52:45 +0300
Message-ID: <CAF4Au4ySVu8y0MP-D1Jfrpi1B_cmdqNjBazq-76tVRAh47GJ-Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<CAMsr+YEfh3qgxDeyAThi-nv0k3ptxhOZKW44kKzcaspGnWzC2A@mail.gmail.com>
	<[email protected]>
	<CAMsr+YGE8PU4THTTEXk4YkbfkZQrU32JJYojJzhQaKkZUKfXAQ@mail.gmail.com>
	<[email protected]>

On Mon, Feb 26, 2018 at 10:23 PM, Tom Lane <[email protected]> wrote:
> Craig Ringer <[email protected]> writes:
>> On 26 February 2018 at 12:16, Tom Lane <[email protected]> wrote:
>>> How can we resolve these issues?
>
>> Question the assumptions and requirements. Why do we actually _need_
>> diffable, mergeable images? Sure, it'd be *nice*, but what's the real world
>> impact if we don't have it?
>
> Well, I'll tell you exactly why I'm being sticky about this: we've been
> down this road before.  We used to have some figures in .gif format,
> and one of the problems with them was they were too hard to update.
> I don't buy the "they won't need updates" argument for a second, either.
> For instance, I recall that one of the images we had was a diagram of
> the system catalog cross-references, and it was constantly out of date
> because of the difficulty of updating it.
>
> Admittedly, this was 15+ years ago.  Maybe the state of the art in
> figure editors has advanced to the point where it won't be so hard.
> But color me suspicious.


In case you missed, a couple of years ago we discussed this on pgcon:

Heikki's version:
https://wiki.postgresql.org/wiki/Figures_%26_Pics_in_Docs

Emre suggested to use Markdeep (BSD license),
http://casual-effects.com/markdeep/
http://www.sai.msu.su/~megera/postgres/gin-ascii-v2.md.html

It looks good for small diagrams, but will not work for complex stuff,
such as pg_catalog structure.


>
>                         regards, tom lane
>

view thread (23+ 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]
  Subject: Re: Images in the official documentation
  In-Reply-To: <CAF4Au4ySVu8y0MP-D1Jfrpi1B_cmdqNjBazq-76tVRAh47GJ-Q@mail.gmail.com>

* 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