Skip site navigation (1) Skip section navigation (2)

Re: Why the separate jade calls for pdf and ps output?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-docs(at)postgreSQL(dot)org
Subject: Re: Why the separate jade calls for pdf and ps output?
Date: 2010-04-29 16:27:46
Message-ID: 13908.1272558466@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-docs
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On tor, 2010-04-29 at 10:53 -0400, Tom Lane wrote:
>> However, diff'ing the results shows that the .tex-pdf and .tex-ps output
>> files are actually identical.  Would it be reasonable to simplify the
>> Makefile by eliminating the separate build rules?  I guess we'd have to
>> make an arbitrary choice between texdvi-output and texpdf-output flags.

> It has to do with graphics support, because tex and pdftex support
> different graphics formats.  Since we don't currently have any graphics,
> it's dead code.  I think you can actually do away with it anyway because
> TeX should support graphics file references without extensions, ISTR.
> So the actual reason for this might have been RTF support.

> If it's in the way, remove it.

It's not in the way, particularly; I was just curious whether we could
do without it.  The only obvious benefit would be to save some work
when building PS and PDF output at the same time, but I doubt very many
people do that.

Since there was just recently some discussion about adding graphics to
the docs, I don't feel a need to put possible roadblocks in the way of
that.  Maybe the best thing would be to wait for some work of that sort
to land, and then experiment to see if we can simplify without breaking
anything.

			regards, tom lane

In response to

pgsql-docs by date

Next:From: Bruce MomjianDate: 2010-04-29 20:54:29
Subject: pgsql: Move alpha release notes into a separate file; re-align sgml
Previous:From: Peter EisentrautDate: 2010-04-29 16:21:56
Subject: Re: Why the separate jade calls for pdf and ps output?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group