public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Robert Haas <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Rafael Martinez <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Documentation and explanatory diagrams
Date: Fri, 02 Jul 2010 22:13:21 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Robert Haas <[email protected]> writes:
> On Fri, Jul 2, 2010 at 5:43 PM, Bruce Momjian <[email protected]> wrote:
>> People often built them to verify the SGML markup and to view the
>> content/markup before submitting a doc patch.

> Actually, they often DON'T, which is a problem, and adding more
> requirements is only going to make it worse.

> There is not much reason for an end-user to build the docs - most
> end-users will install from RPMs or one-click installers or whatever.
> But everyone who is a developer needs to be able to build them,

I think that adding dia to the set of requirements isn't that big a
deal, assuming that it's a widely available package.  It's just one
program and should be a lot easier to install and configure than our
other doc toolchain requirements.

What I'm more worried about at the moment is whether it's a reasonable
choice of tool.  If the "source" for a diagram is larger than the PNG
image representation, there is something seriously wrong with the
language design.

			regards, tom lane

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