public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: Switching to XML
Date: Thu, 14 Dec 2006 21:45:52 -0500 (EST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
I have applied the attached documentation patch to HEAD and 8.2.X to
document the use of Tom's patch to openjade to get ouput in a reasonable
amount of time.
---------------------------------------------------------------------------
Tom Lane wrote:
> Peter Eisentraut <[email protected]> writes:
> > Tom Lane wrote:
> >> Since jade does not go into this kind of spiral when producing html
> >> output from the same sources, I suggest that it's not jade's fault,
> >> but rather crummy coding in the sgml-to-tex conversion scripts it's
> >> using.
>
> > Right. I fixed that, so now it takes about 15 minutes to build the
> > whole thing.
>
> Actually, I just finished fixing what seems to be the underlying problem
> in jade: it's got a spectacularly bad implementation of linked lists.
> In PG-code terms, if the list is built by successive lappends(), then
> both lfirst() and lnext() take O(N) time for an N-element list, thus
> iterating through the list in the usual way is O(N^2) ... and not even
> with a reasonably small multiplier, because it stresses the hell out of
> memory allocation and garbage collection while it's at it. (Which may
> well mean that it's really more like O(N^3), since the garbage collector
> will iterate over every allocated object every so often.)
>
> With the patch it takes me about 5 minutes to do the jade step of the
> PDF build, using this morning's SGML sources. (I don't know how to set
> the TeX configuration to get the pdfjadetex steps to go through, so I
> dunno about total time.)
>
> However, I have no idea what it'll take to get this patch propagated
> into the copies people actually use, so your fix sounds good for the
> short term.
>
> regards, tom lane
>
> diff -cr openjade-1.3.2.orig/style/ELObj.cxx openjade-1.3.2/style/ELObj.cxx
> *** openjade-1.3.2.orig/style/ELObj.cxx Fri Jan 11 10:48:38 2002
> --- openjade-1.3.2/style/ELObj.cxx Sat Dec 9 21:58:36 2006
> ***************
> *** 1044,1049 ****
> --- 1044,1054 ----
--
Bruce Momjian [email protected]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Attachments:
[text/x-diff] /bjm/diff (1.4K, 2-%2Fbjm%2Fdiff)
download | inline diff:
Index: doc/src/sgml/docguide.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v
retrieving revision 1.61
diff -c -c -r1.61 docguide.sgml
*** doc/src/sgml/docguide.sgml 10 Dec 2006 20:46:03 -0000 1.61
--- doc/src/sgml/docguide.sgml 15 Dec 2006 02:39:37 -0000
***************
*** 115,120 ****
--- 115,123 ----
<acronym>DSSSL</acronym> stylesheets), as well as a number of
related tools. <productname>Jade</productname> is now being
maintained by the OpenJade group, no longer by James Clark.
+ (If generating Postscript or PDF output, you will need to
+ compile from source and use a special patch to get output
+ in a reasonable amount of time.)
</para>
</listitem>
</varlistentry>
***************
*** 295,300 ****
--- 298,311 ----
installed and you want to install the rest of the tool chain
locally.)
</para>
+
+ <para>
+ OpenJade release 1.3.2 and perhaps earlier and later releases
+ have a known bug that causes Postscript and PDF output
+ generation to take days. This <ulink
+ url="http://archives.postgresql.org/pgsql-docs/2006-12/msg00064.php">patch</ulink>
+ fixes the problem and generates output in a few minutes.
+ </para>
</step>
<step id="doc-openjade-install">
view thread (122+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Switching to XML
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox