Re: Switching to XML

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Switching to XML
Дата
Msg-id 200612150245.kBF2jqV23539@momjian.us
обсуждение исходный текст
Ответ на Re: Switching to XML  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Switching to XML  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-docs
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 <peter_e@gmx.net> 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   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +
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">

В списке pgsql-docs по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [pgsql-www] 8.2.0 pdf
Следующее
От: David Fetter
Дата:
Сообщение: Re: Authoring Tools WAS: Switching to XML