Postgres Pro
Downloads
Home   >   mailing lists

Thread: SGML docs can't be built as .PDF ...

SGML docs can't be built as .PDF ...

From
Tom Lane
Date:
I've confirmed recent reports of trouble building PDF output from our
CVS HEAD SGML.  Using Fedora 8 openjade (plus slow-lists patch),
with the TeX parameter size increases recommended in our docs, it dies
here:

LaTeX Warning: Reference `PGCRYPTO-WITH-WITHOUT-OPENSSL' on page xlvii undefine
d on input line 55630.


LaTeX Warning: Reference `101017' on page xlvii undefined on input line 55655.

! TeX capacity exceeded, sorry [grouping levels=255].
\rlap #1->\hb@xt@ \z@
                      {#1\hss }
l.55663 {start}}
                \Link%
!  ==> Fatal error occurred, the output PDF file is not finished!

There does not seem to be any parameter controlling "grouping levels",
but in any case it seems that this is not so much TeX's problem as a bug
in the TeX code emitted by openjade.  The failure is occurring in the
list-of-tables (presumably at the 255'th table, though I didn't count),
and at the end of the list of tables I find

{\def\Label%

{PL-LANGUAGE-TABLE}}\endNode{}\endSeq{}\endLink{}\endPar{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\end!

Seq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\e!
 ndSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}

\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSpS{}\Node%
{\def\Element%

All those \endSeq{}'s correspond to unclosed \Seq macros in the code for
each list-of-tables entry.  So this looks to me like a stylesheet bug,
but I don't know the DSSSL stuff well enough to know where to look.
Anyone want to tackle it?

(A workaround might be to suppress the list-of-tables in PDF output,
but I dunno how to do that either.)

            regards, tom lane

Re: SGML docs can't be built as .PDF ...

From
Bruce Momjian
Date:
I can confirm your exact behavior on my machine and I am researching
group levels too.  I haven't come up with any fix yet either.

---------------------------------------------------------------------------

Tom Lane wrote:
> I've confirmed recent reports of trouble building PDF output from our
> CVS HEAD SGML.  Using Fedora 8 openjade (plus slow-lists patch),
> with the TeX parameter size increases recommended in our docs, it dies
> here:
>
> LaTeX Warning: Reference `PGCRYPTO-WITH-WITHOUT-OPENSSL' on page xlvii undefine
> d on input line 55630.
>
>
> LaTeX Warning: Reference `101017' on page xlvii undefined on input line 55655.
>
> ! TeX capacity exceeded, sorry [grouping levels=255].
> \rlap #1->\hb@xt@ \z@
>                       {#1\hss }
> l.55663 {start}}
>                 \Link%
> !  ==> Fatal error occurred, the output PDF file is not finished!
>
> There does not seem to be any parameter controlling "grouping levels",
> but in any case it seems that this is not so much TeX's problem as a bug
> in the TeX code emitted by openjade.  The failure is occurring in the
> list-of-tables (presumably at the 255'th table, though I didn't count),
> and at the end of the list of tables I find
>
> {\def\Label%
>
{PL-LANGUAGE-TABLE}}\endNode{}\endSeq{}\endLink{}\endPar{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\end!
>
Seq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\e!
>  ndSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}
>
\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSpS{}\Node%
> {\def\Element%
>
> All those \endSeq{}'s correspond to unclosed \Seq macros in the code for
> each list-of-tables entry.  So this looks to me like a stylesheet bug,
> but I don't know the DSSSL stuff well enough to know where to look.
> Anyone want to tackle it?
>
> (A workaround might be to suppress the list-of-tables in PDF output,
> but I dunno how to do that either.)
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

Re: SGML docs can't be built as .PDF ...

From
Peter Eisentraut
Date:
Am Donnerstag, 27. Dezember 2007 schrieb Tom Lane:
> All those \endSeq{}'s correspond to unclosed \Seq macros in the code for
> each list-of-tables entry.  So this looks to me like a stylesheet bug,
> but I don't know the DSSSL stuff well enough to know where to look.

It's in the file dbautoc.dsl function built-lot.  It's not really a stylesheet
bug, since in Scheme programming is necessarily done through recursive calls.
The problem is that the Scheme code generates code for a different system
(TeX) which does not expect such constructions.

I have disabled the LOT for the time being.  The PDF now builds for me.  I
have also sent a bug report inquiring about the grouping levels.

We could probably do something about the built-lot function, too, but it would
probably hit us again later.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/