On 5/4/16 11:08 AM, Alexander Law wrote:
As was stated in the aforementioned thread, solution 2 can be much (8x)
faster with some xslt optimizations, but I think now we should outline
some roadmap before we start to prepare patches and so.
Maybe we should convert to XML with DocBook4 at first step?
Then, once we get everything stabilized, we can upgrade to DocBook5.
Shouldn't we decompose the conversion procedure, so we could perform
fully automatic conversion without any manual changes, and then fix
non-valid situations, you described before?
I think the process should be something like this:
- Apply your XSLT performance patch. The patch should be submitted to
the next commit fest.
- Wait a while to make sure everyone is happy with the performance.
Keep tweaking if necessary.
- Port all DSSSL customizations to XSLT. Manually evaluate output for
quality.
- Switch to XSLT build for official HTML documentation. [milestone 1]
- Convert sources to XML. (There could be substeps here.) [milestone 2]
- Then consider upgrading to DocBook 5. [milestone 3]
--
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
