Date: Fri, 16 Aug 2019 16:00:48 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-hackers@lists.postgresql.org,
	=?iso-8859-1?Q?J=FCrgen?= Purtz <juergen@purtz.de>
Subject: Re: pgsql: doc: Add some images
Message-ID: <20190816200048.GA5514@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E1h9Gp8-00089E-4B@gemulon.postgresql.org>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On 2019-Mar-27, Peter Eisentraut wrote:

> doc: Add some images
> 
> Add infrastructure for having images in the documentation, in SVG
> format.  Add two images to start with.  See the included README file
> for instructions.

> Author: Jürgen Purtz <juergen@purtz.de>
> Author: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

Now when I test Jürgen's new proposed image genetic-algorithm I find
that this stuff doesn't work in VPATH builds, at least for PDF -- I
don't get a build failure, but instead I get just a section title that
doesn't precede any actual image.  (There's a very small warning hidden
in the tons of other fop output).  If I edit the .fo file by hand to
make the path to .svg absolute, the image appears correctly.

I don't see any way in the fop docs to specify the base path for images.

I'm not sure what's a good way to fix this problem in a general way.
Would some new rule in the xslt would work?

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