MIME-Version: 1.0
References: <CA+TgmobvXwu+iJmBg3hncdjY0-agg3giP-aLi_KhDyrL9+OLew@mail.gmail.com>
 <202403202105.bhhrojsf2diu@alvherre.pgsql>
In-Reply-To: <202403202105.bhhrojsf2diu@alvherre.pgsql>
From: Robert Haas <robertmhaas@gmail.com>
Date: Wed, 20 Mar 2024 17:21:53 -0400
Message-ID: <CA+TgmobJcFAKtS9frnEHTGyV3L54m8NynfHpwRO5fihSYGsHfg@mail.gmail.com>
Subject: Re: documentation structure
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Andrew Dunstan <andrew@dunslane.net>, 
	"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BTgmobJcFAKtS9frnEHTGyV3L54m8NynfHpwRO5fihSYGsHfg%40mail.gmail.com>
Precedence: bulk

On Wed, Mar 20, 2024 at 5:05=E2=80=AFPM Alvaro Herrera <alvherre@alvh.no-ip=
.org> wrote:
> I think you can achieve this with a much smaller patch that just changes
> the outer tag in each file so that each file is a <sect1>, then create a
> single file that includes all of these plus an additional outer tag for
> the <chapter> (or maybe just add the <chapter> in postgres.sgml).  This
> has the advantage that each AM continues to be a separate single file,
> and you still have your desired structure.

Right, that could also be done, and not just for 0003. I just wasn't
sure that was the right approach. It would mean that the division of
the SGML into files continues to reflect the original chapter
divisions rather than the current ones forever. In the short run
that's less churn, less back-patching pain, etc.; but in the long term
it means you've got relics of a structure that doesn't exist any more
sticking around forever.

--=20
Robert Haas
EDB: http://www.enterprisedb.com