Albert Cervera i Areny <[EMAIL PROTECTED]> writes:
> Given some of the problems I exposed earlier and the fact that the
> documentation of contrib modules isn't organized as a reference. I will be
> adding a new chapter to the "II. The SQL Language" part probably after "Full
> Text Search". This
Given some of the problems I exposed earlier and the fact that the
documentation of contrib modules isn't organized as a reference. I will be
adding a new chapter to the "II. The SQL Language" part probably after "Full
Text Search". This will also allow to have each module in one page as
desire
A Diumenge 14 Octubre 2007, Peter Eisentraut va escriure:
> Albert Cervera i Areny wrote:
> > The problem is that if we want these docs in the Reference section of
> > the documentation right after "PostgreSQL Server Applications" they
> > can't be chapters nor sections, they need to be 's.
>
> Tha
Albert Cervera i Areny wrote:
> The problem is that if we want these docs in the Reference section of
> the documentation right after "PostgreSQL Server Applications" they
> can't be chapters nor sections, they need to be 's.
That is not true, AFAICT. What do you base this assertion on?
--
Pete
Albert Cervera i Areny <[EMAIL PROTECTED]> writes:
> The problem is that if we want these docs in the Reference section of the
> documentation right after "PostgreSQL Server Applications" they can't be
> chapters nor sections, they need to be 's. That's the problem...
In any case one would think
The problem is that if we want these docs in the Reference section of the
documentation right after "PostgreSQL Server Applications" they can't be
chapters nor sections, they need to be 's. That's the problem...
A Diumenge 14 Octubre 2007, Peter Eisentraut va escriure:
> Albert Cervera i Areny w
Albert Cervera i Areny wrote:
> 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 pag
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
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 t
The problem with this approach is dblink[1], for example, in which I can't use
reference (as I've already used for dblink itself). I will probably have to
use in theses cases then...
[1] http://www.nan-tic.com/ftp/pgdoc/dblink.html
A Dijous 11 Octubre 2007, Tom Lane va escriure:
> Guillaume Le
Guillaume Lelarge <[EMAIL PROTECTED]> writes:
> The only (or simplest) way to have one page per module is to use the
> reference part.
If the plan is one module per page, why not handle 'em just like the
current command and client reference pages? Add another list to
reference.sgml, and away you
Hi,
Albert Cervera i Areny a écrit :
> I wanted to spend a week or so putting the contrib doc into shape so I
> want
> to start by moving the contrib part from a new appendix to the Reference
> part.
> The problems I find are:
> - I can't make this "contrib" doc a part because
Hi,
I wanted to spend a week or so putting the contrib doc into shape so I
want
to start by moving the contrib part from a new appendix to the Reference
part.
The problems I find are:
- I can't make this "contrib" doc a part because Reference already is a
part
and can't
13 matches
Mail list logo
