Re: documentation structure
От | Tom Lane |
---|---|
Тема | Re: documentation structure |
Дата | |
Msg-id | 106570.1710969945@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: documentation structure (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: documentation structure
|
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Wed, Mar 20, 2024 at 5:05 PM 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. I'd say that a separate file per AM is a good thing regardless. Elsewhere in this same thread are grumblings about how big func.sgml is; why would you think it good to start down that same path for the AM documentation? regards, tom lane
В списке pgsql-hackers по дате отправления: