Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 0ED882E2F9B for ; Fri, 28 Dec 2007 07:26:03 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 61040-08 for ; Fri, 28 Dec 2007 07:26:02 -0400 (AST) Received: from gauss.credativ.com (gauss.credativ.com [212.112.227.254]) by postgresql.org (Postfix) with ESMTP id 92B2A2E2F96 for ; Fri, 28 Dec 2007 07:26:02 -0400 (AST) Received: from hawking.credativ.lan (exit.credativ.com [87.139.82.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id 48C0477593; Fri, 28 Dec 2007 12:26:01 +0100 (CET) From: Peter Eisentraut To: pgsql-docs@postgresql.org Subject: Re: SGML docs can't be built as .PDF ... Date: Fri, 28 Dec 2007 12:25:58 +0100 User-Agent: KMail/1.9.7 Cc: Tom Lane References: <17720.1198777668@sss.pgh.pa.us> In-Reply-To: <17720.1198777668@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712281225.59596.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/59 X-Sequence-Number: 4727 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/