Date: Thu, 8 Apr 2010 13:48:09 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Devrim =?iso-8859-1?B?R9xORNxa?= <devrim@gunduz.org>,
	pgsql-docs <pgsql-docs@postgresql.org>, Peter Eisentraut <peter_e@gmx.net>
Subject: Re: PDF build issue with 9.0 Alpha5
Message-ID: <20100408174809.GG4126@alvh.no-ip.org>
References: <1270189232.5018.7.camel@hp-laptop2.gunduz.org>
	<23456.1270324388@sss.pgh.pa.us>
	<20100408172211.GE4126@alvh.no-ip.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100408172211.GE4126@alvh.no-ip.org>
User-Agent: Mutt/1.5.20 (2009-06-14)

Alvaro Herrera wrote:
> Tom Lane wrote:
> 
> > There turns out to be a very easy way to inject the code change, which
> > is to create a file "jadetex.cfg" in the doc/src/sgml directory,
> > containing the modified version of the relevant TeX macro.
> > (Note: in the vpath case we'd probably need to link it into the build
> > directory; I haven't experimented with that.)
> 
> FWIW I was able to build the PDF in a VPATH build by dropping this file
> in the source dir, without any other change.

Huh, sorry, I rechecked by moving the file elsewhere and it still builds
:-(  The TeX stats look like this:

Here is how much of TeX's memory you used:
 246183 strings out of 246240
 1743979 string characters out of 1818266
 650918 words of memory out of 1585000
 175202 multiletter control sequences out of 10000+262143
 102154 words of font info for 154 fonts, out of 1200000 for 2000
 54 hyphenation exceptions out of 8191
 28i,13n,45p,1206b,3965s stack positions out of 1500i,500n,1500p,200000b,50000s


-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.