Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1pIx9E-0002YF-QM
	for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jan 2023 19:34:00 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1pIx9D-0001Sp-AT
	for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jan 2023 19:33:59 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <kop@karlpinc.com>)
	id 1pIx9D-0001SO-1Q
	for pgsql-hackers@lists.postgresql.org; Fri, 20 Jan 2023 19:33:59 +0000
Received: from janus.karlpinc.com ([173.161.46.12] helo=smtp.karlpinc.com)
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <kop@karlpinc.com>)
	id 1pIx97-0002XE-H6
	for pgsql-hackers@lists.postgresql.org; Fri, 20 Jan 2023 19:33:57 +0000
Received: from slate.karlpinc.com (unknown [192.168.1.14])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest
 SHA256)
	(No client certificate requested)
	by smtp.karlpinc.com (Postfix) with ESMTPS id 68806A19B;
	Fri, 20 Jan 2023 13:33:48 -0600 (CST)
Received: from slate.karlpinc.com (localhost [IPv6:::1])
	by slate.karlpinc.com (Postfix) with ESMTPS id 292243FC11;
	Fri, 20 Jan 2023 13:33:48 -0600 (CST)
Date: Fri, 20 Jan 2023 13:33:46 -0600
From: "Karl O. Pinc" <kop@karlpinc.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Doc: Rework contrib appendix -- informative titles, tweaked
 sentences
Message-ID: <20230120133346.3aa0b813@slate.karlpinc.com>
In-Reply-To: <20230120191203.7nyqjbw3qe7xx4ru@alvherre.pgsql>
References: <20230120062600.690e80ea@slate.karlpinc.com>
	<20230120191203.7nyqjbw3qe7xx4ru@alvherre.pgsql>
X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/20230120133346.3aa0b813%40slate.karlpinc.com>
Precedence: bulk

On Fri, 20 Jan 2023 20:12:03 +0100
Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:

> On 2023-Jan-20, Karl O. Pinc wrote:
> 
> > On Fri, 20 Jan 2023 12:42:31 +0100
> > Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:  
> 
> > > Hmm, I didn't know that.  I guess I can put it back.  My own
> > > instinct is to put the most important stuff first, not last, but
> > > if research says to do otherwise, fine, let's do that.  
> > 
> > A quick google on the subject tells me that I can't figure out a
> > good quick google.  I believe it's from the book at bottom.
> > Memorability goes "end", "beginning", "middle".  IIRC.  
> 
> Ah well.  I just put it back the way you had it.
> 
> > > I hope somebody with more docbook-fu can comment: maybe
> > > there's a way to fix it more generally somehow?  
> > 
> > What would the general solution be?  
> 
> I don't know, I was thinking that perhaps at the start of the appendix
> we could have some kind of marker that says "in this chapter, the
> <sect1>s all get a page break", then a marker to stop that at the end
> of the appendix.  Or a tweak to the stylesheet, "when inside an
> appendix, all <sect1>s get a pagebreak", in a way that doesn't affect
> the other chapters.
> 
> The <?hard-pagebreak?> solution looks really ugly to me (in the source
> code I mean), but I suppose if we discover no other way to do it, we
> could do it like that.

I can do a forced page break for sect1-s in the pdf stylesheet just 
for the contrib appendix (appendix F) by looking for a parent 
with an id of "contrib".  That would work, but seems like a kludge.
(Otherwise, you look for a parent of "appendix" and force the page
break in all appendixes.)

I'll send a patch.

Regards,

Karl <kop@karlpinc.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein