From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: splarv@ya.ru
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: 31.7.1. Initial Snapshot
Date: Wed, 11 Oct 2023 19:19:44 +0200
Message-ID: <202310111719.h5b6ihmnpyku@alvherre.pgsql> (raw)
In-Reply-To: <CAKFQuwYfgDbWZkX3dUhY37fXFfxsM8rf+OoB2P6imn4Mdcq7QA@mail.gmail.com>
On 2023-Oct-11, David G. Johnston wrote:
> Or move 4 paragraphs of introductory material into its own section so that
> there are two sections and a brief sentence for an intro.
We have lots of other places where this (single-entry TOCs) happens. I
don't think we want to add spurious <section> tags in all those places
is going to be a good idea.
> I don't see a special case for a single section to be a productive use of
> time.
Well, it's the only case where it's not obvious what is going on, but I
agree it's not a great fix -- maybe we have some place where the
introductory material is very long and the first section is several
pagefuls below, and not having a TOC in that case wouldn't be great.
> Improved formatting overall for the chapter ToC has merit.
Great ...
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Crear es tan difícil como ser libre" (Elsa Triolet)
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: alvherre@alvh.no-ip.org, david.g.johnston@gmail.com, splarv@ya.ru, pgsql-docs@lists.postgresql.org
Subject: Re: 31.7.1. Initial Snapshot
In-Reply-To: <202310111719.h5b6ihmnpyku@alvherre.pgsql>
* 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