Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 46C589FC0AA for ; Fri, 12 Oct 2007 14:14:12 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 79349-08 for ; Fri, 12 Oct 2007 14:13:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from k2smtpout02-01.prod.mesa1.secureserver.net (k2smtpout02-01.prod.mesa1.secureserver.net [64.202.189.90]) by postgresql.org (Postfix) with SMTP id 677C49FB9D8 for ; Fri, 12 Oct 2007 14:13:35 -0300 (ADT) Received: (qmail 23026 invoked from network); 12 Oct 2007 17:13:33 -0000 Received: from unknown (HELO mail.cowdot.com) (208.109.83.21) by k2smtpout02-01.prod.mesa1.secureserver.net (64.202.189.90) with ESMTP; 12 Oct 2007 17:13:33 -0000 Received: by mail.cowdot.com (Postfix, from userid 99) id EC0B12A99AC; Fri, 12 Oct 2007 10:13:16 -0700 (MST) Received: from albert.local (111.pool85-52-225.static.orange.es [85.52.225.111]) by mail.cowdot.com (Postfix) with ESMTP id 5C79D2A99A2; Fri, 12 Oct 2007 10:13:13 -0700 (MST) From: Albert Cervera i Areny Organization: NaN To: Tom Lane Subject: Re: Tips needed for contrib doc Date: Fri, 12 Oct 2007 19:13:37 +0200 User-Agent: KMail/1.9.7 Cc: pgsql-docs@postgresql.org References: <200710102315.50067.albert@nan-tic.com> <470DD549.40307@lelarge.info> <12721.1192111726@sss.pgh.pa.us> In-Reply-To: <12721.1192111726@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710121913.38339.albert@nan-tic.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/39 X-Sequence-Number: 4460 The problem with this approach is dblink[1], for example, in which I can't use reference (as I've already used for dblink itself). I will probably have to use in theses cases then... [1] http://www.nan-tic.com/ftp/pgdoc/dblink.html A Dijous 11 Octubre 2007, Tom Lane va escriure: > Guillaume Lelarge writes: > > The only (or simplest) way to have one page per module is to use the > > reference part. > > If the plan is one module per page, why not handle 'em just like the > current command and client reference pages? Add another list to > reference.sgml, and away you go. > > regards, tom lane -- Albert Cervera i Areny http://www.NaN-tic.com