From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Release.sgml markup |
Date: | 2003-07-22 15:32:58 |
Message-ID: | 1058887977.46558.15.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Tue, 2003-07-22 at 15:35, Peter Eisentraut wrote:
> Rod Taylor writes:
>
> > As for the brackets. Currently they are a part of the content in order
> > to achieve a specific style in the output of the resulting page. The
> > data could be tabular (items on left, names to right), different type of
> > bracket, removed entirely for different outputs, or perhaps different
> > names would be processed in different ways (Bruce could be hyperlinked
> > to his homepage via the stylesheet for HTML output only) -- thus it is
> > the job of the stylesheets to manage.
>
> But you are trying to attach additional semantics to predefined elements.
> The predefined semantics is "<simplelist> is a list". Your proposed new
> semantic is "<simplelist> withing <itemizedlist> within the PostgreSQL
> release notes identifies the contributor of the feature identified in the
> parent <listitem>". If you want to go in that direction, you need to
> define new elements.
I see what you mean now. You are right that the simplelist should use
the "role" attribute for this purpose, which I will do when the time is
appropriate (after the 4.2 doc upgrade + XSL implementation).
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-07-22 15:35:24 | Re: Release.sgml markup |
Previous Message | Tom Lane | 2003-07-22 14:39:38 | Re: PATCH: Memory leaks on start-up |