To: pgsql-docs <pgsql-docs@postgresql.org>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Subject: end of the line for Jade and DSSSL
Organization: 2ndQuadrant
Message-ID: <4c682fda-87e0-b95d-6df0-a937c8fc6a4f@2ndquadrant.com>
Date: Tue, 4 Apr 2017 22:28:46 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0)
 Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="------------EBA01BFB631EB92340371B2B"
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

This is a multi-part message in MIME format.
--------------EBA01BFB631EB92340371B2B
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

To wrap up the ongoing documentation tool chain conversion for this
release, I propose the attached patch, which

- removes all uses of Jade and DSSSL, in particular the "oldhtml" target

- removes JadeTex and moves FOP in its place for PDF builds

- updates the documentation about the required tools

One thing I didn't carry over is the single-page HTML output (make
postges.html).  This could be added, but I'm not sure if anyone was
using that.

This would conclude the conversion from DSSSL to XSLT.  The plan for
PG11 would include converting the source files from SGML to XML, but
that's going to be another thread sometime.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--------------EBA01BFB631EB92340371B2B
Content-Type: invalid/octet-stream;
 name="0001-Remove-use-of-Jade-and-DSSSL.patch"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="0001-Remove-use-of-Jade-and-DSSSL.patch"