Feedback-ID: ia2694551:Fastmail
Date: Wed, 11 Oct 2023 19:19:44 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: splarv@ya.ru, pgsql-docs@lists.postgresql.org
Subject: Re: 31.7.1. Initial Snapshot
Message-ID: <202310111719.h5b6ihmnpyku@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAKFQuwYfgDbWZkX3dUhY37fXFfxsM8rf+OoB2P6imn4Mdcq7QA@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202310111719.h5b6ihmnpyku%40alvherre.pgsql>
Precedence: bulk

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)