From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Alexander Law <exclusion(at)gmail(dot)com>, obartunov(at)gmail(dot)com, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Alexander Lakhin <a(dot)lakhin(at)postgrespro(dot)ru> |
Cc: | Jürgen Purtz <juergen(at)purtz(dot)de>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Docbook 5.x |
Date: | 2016-11-08 13:25:04 |
Message-ID: | e4e972b8-425b-164b-031e-f6db2daef9d2@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 9/14/16 7:18 AM, Alexander Law wrote:
> Please look at the
> http://oc.postgrespro.ru/index.php/s/ttJyMDLr8Xr1HTu/download
> where I have gathered together all the significant differences, that we
> have between DSSSL and XSLT outputs.
> I have marked red the differences that I would consider as negative.
> Let's decide which ones are acceptable and which we need to eliminate.
Thank you for making that list. I have a similar list that is not quite
the same, so together we'll probably find all the problems. I have
checked both lists and most of the issues are not terribly critical.
I have now committed fixes for what I think were the major missing
usability issues: header customization and index letter links. I would
be comfortable with switching the default build to XSLT now and work out
the remaining issues on the fly. What do you think?
(I also have a similar list for switching the PDF build from jadetex to
fop. We are also in pretty good shape there, but I have not finished
the evaluation fully.)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | vodevsh | 2016-11-08 14:27:39 | misleading ALTER TABLE SET STORAGE |
Previous Message | sallyx | 2016-11-04 18:58:41 | SET AUTOCOMMIT TO OFF is no longer supported |