Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 37AA42E01D8 for ; Thu, 27 Dec 2007 14:08:24 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 16706-09 for ; Thu, 27 Dec 2007 14:08:17 -0400 (AST) Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id D7C1D2E012E for ; Thu, 27 Dec 2007 14:08:18 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id lBRI8Ij14652; Thu, 27 Dec 2007 13:08:18 -0500 (EST) From: Bruce Momjian Message-Id: <200712271808.lBRI8Ij14652@momjian.us> Subject: Re: SGML docs can't be built as .PDF ... In-Reply-To: <17720.1198777668@sss.pgh.pa.us> To: Tom Lane Date: Thu, 27 Dec 2007 13:08:18 -0500 (EST) CC: pgsql-docs@postgresql.org X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/58 X-Sequence-Number: 4726 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: >=20 > LaTeX Warning: Reference `PGCRYPTO-WITH-WITHOUT-OPENSSL' on page xlvii un= define > d on input line 55630. >=20 >=20 > LaTeX Warning: Reference `101017' on page xlvii undefined on input line 5= 5655. >=20 > ! TeX capacity exceeded, sorry [grouping levels=3D255]. > \rlap #1->\hb@xt@ \z@=20 > {#1\hss } > l.55663 {start}} > \Link% > ! =3D=3D> Fatal error occurred, the output PDF file is not finished! >=20 > 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 >=20 > {\def\Label% > {PL-LANGUAGE-TABLE}}\endNode{}\endSeq{}\endLink{}\endPar{}\endSeq{}\endSe= q{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}= \endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\en= dSeq{}\endSeq{}\endSeq{}\endS= eq{}\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{}\endS= eq{}\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{}\en= dSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSe= q{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}= \end! > Seq{}\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{}\en= dSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSe= q{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}= \endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\en= dSeq{}\endSeq{}\endSeq{}\endS= eq{}\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{}\endS= eq{}\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= {}\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{}\end= Seq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq= {}\endSeq{}\endSeq{}\endSeq{}= \endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\endSeq{}\en= dSeq{}\endSpS{}\Node% > {\def\Element% >=20 > 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? >=20 > (A workaround might be to suppress the list-of-tables in PDF output, > but I dunno how to do that either.) >=20 > regards, tom lane >=20 > ---------------------------(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 --=20 Bruce Momjian http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +