end of the line for Jade and DSSSL
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t75902psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 07:24 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t75902_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t75902_1 && git checkout t75902_1Patchset v1 (message #1) is on t75902_1
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
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
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.
The discussion that led up to that seems to be this thread:
/messages/by-id/29FD1BB6-9AD8-485C-B5D2-23D66C15DC97@numericable.fr
As best I can tell, the main point was not so much single-page HTML
as such, as that it allowed getting to a flat text representation.
Do we still have an answer for that?
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On 4/5/17 00:16, Tom Lane wrote:
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
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.The discussion that led up to that seems to be this thread:
/messages/by-id/29FD1BB6-9AD8-485C-B5D2-23D66C15DC97@numericable.frAs best I can tell, the main point was not so much single-page HTML
as such, as that it allowed getting to a flat text representation.
Do we still have an answer for that?
Alright, added that back in and committed the whole thing.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs