> > A partial proposal: CHANGELOG refsect1
> >
> > What it will contain:
> > 1) Parameter changes (new, modified, ...)
> > 2) Function changes (new features, new behaviors, ...)
> > 3) PHP Version info for each change
> >
> > From TODO:
> >   new roles: seealso, newparameter, and changedparameter.
> 
> Of course this is a good idea, but I don't know how hard is the
> implemetation.
> With this we could have costumized manuals for each php version (with
> livedocs).

We'll have to be careful here because we don't want person A
reading person B's version of the manual and getting confused.
I was thinking of only differentiated CSS stylesheets but
maybe you mean something like that.  Just as long as different
manual builds aren't floating around.

> My only concern is how to implement all this...  My docbook knowledge isn't
> good, as well as XSLT, dsssl, etc... Do anyone have enough time to implement
> this at 100%?
> I don't have many ideas for you (yet). I'm gonna think on the subject later.

The lack of a DSSSL and XSLT guru has plagued our work for years 
so perhaps the use of livedocs will change all of that.  If not
implemented in DSSSL we'd have to wait until livedocs becomes 
official.  Of course both would be ideal :)

> > This would be great and it's a perfect time to implement because
> > when people update old docs to the new refsect1 style we would
> > also implement these changelog entries!  Woohoo!!!
> 
> What is the new refsext1 style? The credits tag?...

Each manual page is split up in sections, see language-defs.ent
for a list of entities and the exif/mysqli docs for examples.
Some of the mysqli docs list examples after the see also so 
we'd want to change that unless everyone feels that a change in
order is needed.  I don't!  I committed a new doc skeleton to the
HOWTO as well.  I was fairly certain this was agreed upon but
don't remember any official call for votes.

Now as to the CHANGELOG, I am guessing nobody will implement it
in DSSSL (I know I won't) so focusing on livedocs may end up
happening.  Livedocs or bust, 2004!

Regards,
Philip

Reply via email to