From: | Albert Cervera i Areny <albert(at)nan-tic(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Tips needed for contrib doc |
Date: | 2007-10-12 18:04:44 |
Message-ID: | 200710122004.44884.albert@nan-tic.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Not that I want to make each module a reference. With previous discussions we
seemed to agree that:
- It should go into the References part of the documentation (right
after "III. PostgreSQL Server Applications).
- Each module docs should be in a single page, mainly because some contrib
modules have/require very little documentation.
So it seems that the only way of achieving both things is to make each contrib
module a <refentry> inside a new <reference id="contrib">. I don't like this
idea, among other things because dblink won't be abe to be treated as a
<reference> which I think is appropiate in this case.
If you've got another solution for this, it'll be very welcome!
A Divendres 12 Octubre 2007, Peter Eisentraut va escriure:
> Am Mittwoch, 10. Oktober 2007 schrieb Albert Cervera i Areny:
> > - I can't make this "contrib" doc a part because Reference
> > already is a part and can't be nested.
>
> The Reference things in DocBook are mostly to support legacy man pages, and
> man pages are not necessary the greatest format to document everything.
> What is your reason that you want this as a reference rather than a part
> with chapters?
--
Albert Cervera i Areny
http://www.NaN-tic.com
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Barwick | 2007-10-12 18:04:56 | FAQ corrections |
Previous Message | Peter Eisentraut | 2007-10-12 17:47:14 | Re: Tips needed for contrib doc |