Following are the top 20 pages of the manual, sorted by the number
of user notes contributed. These sections could use a polish, those
notes represent 8.5% of the 9545 total user notes.
Notes | Page
---+-
44 | http://php.net/manual/
Well, I suppose we've been waiting for suggestions enough. Time to work.
I will start, if you don't mind.
Great.
Goba
Nuno Lopes wrote:
I doubt we are able to mix them in one section. They all stand for
different functionality and should be described in proper sections, i.e.
call, set and get -- oop5.overloading.
But I like your idea: oop5.magic should include tostring, autoload and
*, imho.
- oop5.intro : I
ID: 28716
Updated by: [EMAIL PROTECTED]
Reported By: devnull at latinmail dot com
-Status: Open
+Status: Bogus
Bug Type: Documentation problem
Operating System: windows
PHP Version: 4.3.7
New Comment:
I've already solved this problem
From: devnull at latinmail dot com
Operating system: windows
PHP version: 4.3.7
PHP Bug Type: Documentation problem
Bug description: [chm] bug on function.php-uname.html
Description:
I have found a bug on page function.php-uname.html
[chm date: 2003-09-06]...
It
Gabor Hojtsy wrote:
I thought it is easier to to grant every doc involved people with karma
first, so we can jumpstart the site. But I can act as karma provider for
this module if that is fine. Is it?
Yup, that was my idea.
OK, so then I am the one who ask docweb karma for.
Good :) I'm not sure i
I thought it is easier to to grant every doc involved people with karma
first, so we can jumpstart the site. But I can act as karma provider for
this module if that is fine. Is it?
Yup, that was my idea.
OK, so then I am the one who ask docweb karma for.
Goba
On Wed, 9 Jun 2004, Gabor Hojtsy wrote:
> I thought it is easier to to grant every doc involved people with karma
> first, so we can jumpstart the site. But I can act as karma provider for
> this module if that is fine. Is it?
Yup, that was my idea.
Derick
Now I would like to ask you to just think about this a bit, and if you
are interested in the development, please provide your opinion on how
would it be best to discuss the further directions (crosspost replies, a
designated mailing list, personal emails, IRC, or something else?)
Mailinglist would
On Wed, 9 Jun 2004, Gabor Hojtsy wrote:
> Now I would like to ask you to just think about this a bit, and if you
> are interested in the development, please provide your opinion on how
> would it be best to discuss the further directions (crosspost replies, a
> designated mailing l
[Note: intentionally crossposted to a lot of addresses.]
Now I would like to ask you to just think about this a bit, and if you
are interested in the development, please provide your opinion on how
would it be best to discuss the further directions (crosspost replies, a
designated mailing list,
Now I would like to ask you to just think about this a bit, and if you
are interested in the development, please provide your opinion on how
would it be best to discuss the further directions (crosspost replies, a
designated mailing list, personal emails, IRC, or something else?)
Mailinglist would
On Wed, 9 Jun 2004, Gabor Hojtsy wrote:
> >>Now I would like to ask you to just think about this a bit, and if you
> >>are interested in the development, please provide your opinion on how
> >>would it be best to discuss the further directions (crosspost replies, a
> >>designated mailing list, per
Hi Goba,
first a big thank you for your work!
>
> I am reporting that the restructuring part of the install section is at
> least prepared. It needs review from more people (ie. build the HTML
> version and/or review with livedocs). There might be incosistent IDs,
> titles, etc. If the structure
Start from http://www.docbook.org/tdg/en/html/authorgroup.html to get
more information on the tag and possible parents.
For translated versions, the nicknames can be fetched from the Revision
comments, where those are appropriately specified. For the original
English text, everything not added by H
> Wez came up with the idea of putting author information into the
> refentries and sections, which should make it quite easy to give credit.
> This can be done with a in a , and a
> for a . Both of these take on an element which
> may contain all necessary information. This method lets people d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 09 June 2004 16:15, Gabor Hojtsy wrote:
> > Yeah, i'm working on it with Medhi since one week and the result is cool
> > :) Actualy, just livedocs not work on it, Medhi must do it soon.
> >
> > I think that tomorow, we could give some CVS
Yeah, i'm working on it with Medhi since one week and the result is cool :)
Actualy, just livedocs not work on it, Medhi must do it soon.
I think that tomorow, we could give some CVS access for people who want's to
help us.
cvs.php.net will include a module soon (today hopefully) to put this
stuf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 09 June 2004 15:46, Vincent Gevers wrote:
> On Wednesday 09 June 2004 15:04, Gabor Hojtsy wrote:
> > It is a long time TODO item on the phpdoc TODO list, that we should set
> > up a website specifically for the documentation team. Now as w
Types of other contributors:
- user note maintainers:
andrew, meebay, didou, ... The list can be generated from
the php-notes mailing list archive. Wez is going to do make
a script pull it out from archives, and after that we're going
to put up guidelines for who is a maintainer an
This sounds very cool, nice one Goba!
Not my idea :)
For php-gtk-doc, I'm still awaiting some form of agreed object documentation model across php.net that I can adopt before going into the whole livedocs thing again. From that perspective, working more closely in this way will hopefully get us th
On Wednesday 09 June 2004 12:31, Gabor Hojtsy wrote:
>
> Types of other contributors:
> - user note maintainers:
> andrew, meebay, didou, ... The list can be generated from
> the php-notes mailing list archive. Wez is going to do make
> a script pull it out from archives, and afte
Now I would like to ask you to just think about this a bit, and if you
are interested in the development, please provide your opinion on how
would it be best to discuss the further directions (crosspost replies, a
designated mailing list, personal emails, IRC, or something else?)
Mailinglist would
On Wednesday 09 June 2004 15:04, Gabor Hojtsy wrote:
> It is a long time TODO item on the phpdoc TODO list, that we should set
> up a website specifically for the documentation team. Now as we are
> preparing for an initial version of the site, and livedocs is in the
> works, a need for a join
I have not changed manual.xml.in yet, since I beleive it is only viable
if we review the structure and selected IDs at least (so notes can be
moved and links can be corrected within the manual).
The on-line manual takes so long to update that you can change the
manual.xml.in and then we have two mo
> > I doubt we are able to mix them in one section. They all stand for
> > different functionality and should be described in proper sections, i.e.
> > call, set and get -- oop5.overloading.
> >
> > But I like your idea: oop5.magic should include tostring, autoload and
> > *, imho.
> >
> > - oop5.i
This sounds very cool, nice one Goba!
For php-gtk-doc, I'm still awaiting some form of agreed object documentation model
across php.net that I can adopt before going into the whole livedocs thing again.
From that perspective, working more closely in this way will hopefully get us there
more qu
I personally like the idea of having a joint documentation. There have been
several people playing (working?) with live-docs in the last few month - but
afaik from the pear-doc-team there is not yet something definitive when we
would have the chance to switch to livedocs (correct me if needed).
On Wed, 9 Jun 2004, Gabor Hojtsy wrote:
> Now I would like to ask you to just think about this a bit, and if you
> are interested in the development, please provide your opinion on how
> would it be best to discuss the further directions (crosspost replies, a
> designated mailing list, personal em
> It would be nice to look at this work from a technical perspective first
> (file names, organization, IDs, section titles), so we can fix that up,
> and then go on to fix the contents. I have done make test-ing and make
> test_xml also found no errors. Here is how to test:
>
> - edit your local
Gabor Hojtsy wrote:
Now I would like to ask you to just think about this a bit, and if you
are interested in the development, please provide your opinion on how
would it be best to discuss the further directions (crosspost replies, a
designated mailing list, personal emails, IRC, or something e
On Wed, 9 Jun 2004 at 15:05:06, Gabor Hojtsy wrote:
> [Note: intentionally crossposted to a lot of addresses.]
Did so as well :-))
> It is a long time TODO item on the phpdoc TODO list, that we should set
> up a website specifically for the documentation team. Now as we are
> preparing for an
Hi,
[Note: intentionally crossposted to a lot of addresses.]
It is a long time TODO item on the phpdoc TODO list, that we should set
up a website specifically for the documentation team. Now as we are
preparing for an initial version of the site, and livedocs is in the
works, a need for a joint
vincent Wed Jun 9 08:10:06 2004 EDT
Modified files:
/phpdoc/en/reference/ftp/functions ftp-chmod.xml
Log:
fixed typo
http://cvs.php.net/diff.php/phpdoc/en/reference/ftp/functions/ftp-chmod.xml?r1=1.3&r2=1.4&ty=u
Index: phpdoc/en/reference/ftp/functions/ftp-chm
Cheers,
And now, here we start again! :) Following on the creation of the
doc-license mailing list, we are ready to start moving on with
crediting. For those not aware of why this was a needed step, here is
the explanation:
Since the copyright statement said that the PHP Documentation Group
m
I doubt we are able to mix them in one section. They all stand for
different functionality and should be described in proper sections, i.e.
call, set and get -- oop5.overloading.
But I like your idea: oop5.magic should include tostring, autoload and
*, imho.
- oop5.intro : Introduction
-
gobaWed Jun 9 05:54:47 2004 EDT
Modified files:
/phpdoc/en bookinfo.xml
/phpdoc/entitiesglobal.ent
/phpdoc/howto working.xml
Log:
The doc-license mailing list is ready. This means:
- The license holders are supposed to be subscribed
37 matches
Mail list logo
