pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-docs@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: SGML docs can't be built as .PDF ...
Date: Fri, 28 Dec 2007 12:25:58 +0100
Message-ID: <200712281225.59596.peter_e@gmx.net> (raw)
In-Reply-To: <17720.1198777668@sss.pgh.pa.us>
References: <17720.1198777668@sss.pgh.pa.us>

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/



view thread (3+ messages)

Message-ID: <200712281225.59596.peter_e@gmx.net>
Permalink:  ../200712281225.59596.peter_e@gmx.net/
Also on:    postgresql.org/message-id/200712281225.59596.peter_e@gmx.net

 · 

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: pgsql-docs@postgresql.org
  Cc: peter_e@gmx.net, tgl@sss.pgh.pa.us
  Subject: Re: SGML docs can't be built as .PDF ...
  In-Reply-To: <200712281225.59596.peter_e@gmx.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox