From: | "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences |
Date: | 2023-01-20 19:33:46 |
Message-ID: | 20230120133346.3aa0b813@slate.karlpinc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg젠 토토SQL : Postg사설 토토 사이트SQL : Postg사설 토토 사이트SQL 메일 링리스트 : 2023-01-20 이후 PGSQL WWW 19:33 |
On Fri, 20 Jan 2023 20:12:03 +0100
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> On 2023-Jan-20, Karl O. Pinc wrote:
>
> > On Fri, 20 Jan 2023 12:42:31 +0100
> > Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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(at)karlpinc(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
From | Date | Subject | |
---|---|---|---|
Next Message | Matthias van de Meent | 2023-01-20 19:37:58 | Re: Improving btree performance through specializing by key shape, take 2 |
Previous Message | Jacob Champion | 2023-01-20 19:24:49 | Re: Authentication fails for md5 connections if ~/.postgresql/postgresql.{crt and key} exist |
From | Date | Subject | |
---|---|---|---|
Next Message | Karl O. Pinc | 2023-01-20 20:22:25 | Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences |
Previous Message | Alvaro Herrera | 2023-01-20 19:12:38 | Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences |