From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jürgen Purtz <juergen(at)purtz(dot)de>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Docbook 5.x |
Date: | 2016-05-03 20:55:10 |
Message-ID: | 26343.1462308910@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> On 05/03/2016 12:34 PM, Alvaro Herrera wrote:
>> Yes, agreed. The killer objection placed last time was that it took
>> something like 10x longer to generate the HTML using the XML-based
>> toolchain than the SGML-based ones. If this is not fixed, let's forget
>> about this whole thing until it is. So, would you time the process
>> using both toolchains and report back?
> IIRC:
> TGL submitted a patch for the openjade bug way back when that caused
> that issue.
I think you're thinking of this:
http://www.postgresql.org/message-id/24388.1166800682@sss.pgh.pa.us
I do not recall just when/how that got resolved upstream, or if they
ever even responded to me. But it must have been resolved, because the
performance before that was patched was untenable even then, and would be
far more so now considering how much our docs have grown since 2006.
I have not heard anyone complaining lately that PDF output takes three
days to build.
In short, I doubt that that's relevant anymore. If it was, it would
certainly not be favorable to the XML toolchain.
BTW, the thread that that message is embedded in is pretty relevant,
because it was all about yet another lets-switch-to-XML proposal...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-05-03 21:05:06 | Re: Docbook 5.x |
Previous Message | Oleg Bartunov | 2016-05-03 20:13:21 | Re: Docbook 5.x |