Content-Type: text/plain; charset=UTF-8
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>,
	Josh Kupershmidt <schmiddy@gmail.com>,
	pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting
	level than \pd
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Bruce Momjian <bruce@momjian.us>
In-reply-to: <201104261515.p3QFFp808246@momjian.us>
References: <201104261515.p3QFFp808246@momjian.us>
Date: Tue, 26 Apr 2011 12:43:06 -0300
Message-Id: <1303831979-sup-5180@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Excerpts from Bruce Momjian's message of mar abr 26 12:15:50 -0300 2011:
> Tom Lane wrote:
> > Peter Eisentraut <peter_e@gmx.net> writes:
> > > On lr, 2011-03-12 at 09:13 -0500, Bruce Momjian wrote:
> > >> OK, it is not something worthwhile, or just something you don't have
> > >> time for.  If the later, can you give us a hint on how to fix it?
> > 
> > > I'm not even sure what the actual action item is supposed to be.
> > 
> > The last suggestion in the thread was to move the contrib docs up one
> > level in the hierarchy, ie each contrib module would get a chapter not a
> > sect1.
> 
> I think we would have to move "Additional Supplied Modules" up into its
> own book, and then list each module.  The problem is that there are 42
> modules so that list is going to be pretty long in the table of
> contents.

Also, most of the sections are pretty short.  Making each of them a
chapter seems a waste.  I think some of them deserve a full chapter
(dblink, citext?, hstore, intarray, ltree, pgbench, pgcrypto, pgtrgm?,
pg_upgrade, tablefunc), but most don't.  (Some of the others could,
perhaps, get moved under "Reference").

Would it work to move only some?

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support