didou Wed Dec 31 04:33:11 2003 EDT
Modified files:
/phpdoc/en/reference/network/functions fsockopen.xml
Log:
proto
Index: phpdoc/en/reference/network/functions/fsockopen.xml
diff -u phpdoc/en/reference/network/functions/fsockopen.xml:1.12
phpdoc/en/refer
> > - we should not drop the unix tools, let windows
> > guys
> > sweat the first time they join the team
Phing would be a wonderful idea - if everyone on windows had build tools,
and if (as Jesus mentioned) everyone was running PHP5. They don't, and
aren't. In the absence of build tools d
nlopess Wed Dec 31 05:39:43 2003 EDT
Modified files:
/phpdoc/en/reference/exec/functions exec.xml passthru.xml
system.xml
/phpdoc/en/reference/filesystem/functions chgrp.xml chmod.xml
Finally, if you change the build system for the PHP core documentation
project so radically without so much as a nod toward all the subsidiary PHP
documentation efforts we'll all end up even more out of sync than we
currently are. I have made a fair amount of effort to make php-gtk-doc at
least va
didou Wed Dec 31 06:02:17 2003 EDT
Modified files:
/phpdoc/en/reference/network/functions pfsockopen.xml
Log:
oups, proto too
Index: phpdoc/en/reference/network/functions/pfsockopen.xml
diff -u phpdoc/en/reference/network/functions/pfsockopen.xml:1.2
php
> I am looking at the build system from the ease-of-use perspective. If
> you only need to checkout the CVS module and can directly run the PHP
> script, it is much easier then installing cygwin, getting familiar with
> the command line, and put all the tools on the appropriate paths...
> Since liv
> If you don't have cygwin, how will you checkout the CVS module??
There are lot of CVS tools for Windows which don't need cygwin.
Jakub Vrana
I am looking at the build system from the ease-of-use perspective. If
you only need to checkout the CVS module and can directly run the PHP
script, it is much easier then installing cygwin, getting familiar with
the command line, and put all the tools on the appropriate paths...
Since livedocs will
Would it be possible to create a special version of Cygwin, with only
those apps we need for building? The only extra thing you need now is
(Open)Jade, all the other tools come with the standard Cygwin. If we
could add (Open)Jade to Cygwin, remove the other applications, and call
the result 'Th
> Hi People!
as long the new system doesn't need additional stuff, which means it will run
with a --disable-all configured php5 I'm + 1.
But I don't really see a necessity - when I joined the documentation team a
few years ago, I used Windows too, without problems - setting up the tools
was d
Would it be possible to create a special version of Cygwin, with only
those apps we need for building? The only extra thing you need now is
(Open)Jade, all the other tools come with the standard Cygwin. If we
could add (Open)Jade to Cygwin, remove the other applications, and call
the result 'Th
> There was quite some discussion on creating a central build system for
> the documentation projects, and livedocs will be a move towards this
> direction, since it should be developed with portability in mind
I inherited a lot of non-standard xml, as you know. We also have the
problem that php-
> If you don't have cygwin, how will you checkout the CVS module??
> Maybe we could use the script I made that implements the CVS protocol in
> PHP. :)
>
erm, against everything I said so far - tortoise works and is far less
unwieldy than cygwin .. it just has one or two areas where it's nice to h
Fine, except we don't use jade on php-gtk-doc either. We use xsltproc
because it's w-a-a-a-y faster.
> -Original Message-
> From: Jan Fabry [mailto:[EMAIL PROTECTED]
> Sent: 31 December 2003 11:34
> To: [EMAIL PROTECTED]
> Subject: [PHP-DOC] Re: dropping the unix tools
>
>
> Would it be p
So we are on making the phpdoc workers life
easier... One of the biggest
problems is for starters, that many tools are
needed. There has been
some discussion on dropping the required unix tools,
and base the whole
build system on PHP. That would mean that Windows
people would not need
to have c
> -Original Message-
> From: Gabor Hojtsy [mailto:[EMAIL PROTECTED]
> Sent: 31 December 2003 13:11
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [PHP-DOC] dropping the unix tools
>
>
> >>So we are on making the phpdoc workers life
> >>easier... One of the biggest
> >>prob
There was quite some discussion on creating a central build system for
the documentation projects, and livedocs will be a move towards this
direction, since it should be developed with portability in mind
I inherited a lot of non-standard xml, as you know. We also have the
problem that php-gtk-doc
If you don't have cygwin, how will you checkout the CVS module??
Maybe we could use the script I made that implements the CVS protocol in
PHP. :)
erm, against everything I said so far - tortoise works and is far less
unwieldy than cygwin .. it just has one or two areas where it's nice to have
cygwi
> To clear things up once and for all :) Wez started livedocs on his own
> machine without any revision control, and then some curious people
> peaked in (Derick Ilia and myself).
And me, actually..
I was able to convince Wez lately that livedocs
> should be moved to cvs.php.net, now we are wait
If you don't have cygwin, how will you checkout the CVS module??
Maybe we could use the script I made that implements the CVS protocol in
PHP. :)
erm, against everything I said so far - tortoise works and is far less
unwieldy than cygwin .. it just has one or two areas where it's nice
to have
cygw
To clear things up once and for all :) Wez started livedocs on his own
machine without any revision control, and then some curious people
peaked in (Derick Ilia and myself).
And me, actually..
Well, only those listed by me have CVS write Karma :) But others also
tested it, including Alan Knowles.
From: [EMAIL PROTECTED]
Operating system: Linux
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: testing the new customized quickfix
Description:
Please ignore.
Expected result:
You ignore this post :)
Actual result:
ID: 26754
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: Linux
PHP Version: Irrelevant
New Comment:
This bug has been fixed in CVS.
Snapsh
> >>To clear things up once and for all :) Wez started livedocs on his own
> >>machine without any revision control, and then some curious people
> >>peaked in (Derick Ilia and myself).
> >
> > And me, actually..
>
> Well, only those listed by me have CVS write Karma :) But others also
> tested it,
Hi !
What about adding a regexp that will link all the PHP functions in the
examples to their man page ?
This could be done with [26-Dec-2003 12:43]'s note in
http://php.net/highlight_string
Opinions ?
didou
> What about adding a regexp that will link all the PHP functions in the
> examples to their man page ?
That function should be slightly modified as PHP functions are
highlighted the same as user-defined functions.
I vote for it - by modification of highlight_php() website function.
Jakub Vrana
> I have already installed livedocs on my computer (windows with cygwin) and
> it works!
> It was a bit painfull, but now I have it working!
>
with phpdoc, yes :)
vrana Wed Dec 31 10:03:12 2003 EDT
Modified files:
/phpdoc/en/appendices aliases.xml
/phpdoc/en/reference/ircg configure.xml
/phpdoc/en/faq general.xml languages.xml
/phpdoc/en/chapters install.configure.graphics.xml
/phpdoc/en/referen
I like to give my contribute to
translation.
Best regards
Alexandre Altair de Melo.
31/12/2003
vrana Wed Dec 31 10:25:25 2003 EDT
Modified files:
/phpdoc/en/reference/curl configure.xml
/phpdoc/en/reference/domxml configure.xml
/phpdoc/en/reference/fdfconfigure.xml
/phpdoc/en/reference/gettextconfigure.xml
/phpdoc/en/reference/
Hi Alexandre!
Please read http://php.net/dochowto and contact [EMAIL PROTECTED]
Goba
Alexandre Altair de Melo wrote:
I like to give my contribute to translation.
Best regards
Alexandre Altair de Melo.
31/12/2003
What about adding a regexp that will link all the PHP functions in the
examples to their man page ?
That function should be slightly modified as PHP functions are
highlighted the same as user-defined functions.
I vote for it - by modification of highlight_php() website function.
Some code for this
gobaWed Dec 31 11:07:12 2003 EDT
Modified files:
/phpdoc/scripts/quickreforiginalafter.js processafter.php
Log:
use setAttribute() instead of setting the JS attribute, since it is DOM1, and
reported to work with IE
Index: phpdoc/scripts/quickref/origina
ID: 26754
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Closed
+Status: Open
Bug Type: Documentation problem
Operating System: Linux
PHP Version: Irrelevant
New Comment:
Repoening just for another quickfix try
vrana Wed Dec 31 11:08:07 2003 EDT
Modified files:
/phpdoc/en/reference/outcontrol reference.xml
Log:
double be
Index: phpdoc/en/reference/outcontrol/reference.xml
diff -u phpdoc/en/reference/outcontrol/reference.xml:1.11
phpdoc/en/reference/outcontrol/re
ID: 26754
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: Linux
PHP Version: Irrelevant
New Comment:
This bug has been fixed in the document
Hi!
As you can see below, now the documentation bugs (and website bugs) have
their own quickfix text, so the response to bugs is much more
customized... In case other custom messages would be needed for more fix
types, just write up the suggested text, and propose...
Goba
[EMAIL PROTECTED] wr
> Some code for this is available in the extended CHM generator. The
> problem is that you need a complete list of built in functions for that
> to work in memory (or you need to check if a file exists which documents
> that function) runtime. The second option should not be selected, since
> we ma
> As you can see below, now the documentation bugs (and website bugs) have
> their own quickfix text, so the response to bugs is much more
> customized... In case other custom messages would be needed for more fix
> types, just write up the suggested text, and propose...
I think that Submitted tw
Some code for this is available in the extended CHM generator. The
problem is that you need a complete list of built in functions for that
to work in memory (or you need to check if a file exists which documents
that function) runtime. The second option should not be selected, since
we made our bes
As you can see below, now the documentation bugs (and website bugs) have
their own quickfix text, so the response to bugs is much more
customized... In case other custom messages would be needed for more fix
types, just write up the suggested text, and propose...
I think that Submitted twice quick
> Duplicated is not used anymore... Ask Derick, why :))
Rather not :-).
Jakub Vrana
On Wed, 31 Dec 2003, Jakub Vrana wrote:
> > As you can see below, now the documentation bugs (and website bugs) have
> > their own quickfix text, so the response to bugs is much more
> > customized... In case other custom messages would be needed for more fix
> > types, just write up the suggested
> Well, that list of the list of functions implemented in PHP, and not the
> list of functions documented in the manual. Therefore it is not correct
> for linking stuff, since you might link to something which is not (yet)
> documented.
It will not be hard to write a script for it. But before I wa
Well, that list of the list of functions implemented in PHP, and not the
list of functions documented in the manual. Therefore it is not correct
for linking stuff, since you might link to something which is not (yet)
documented.
It will not be hard to write a script for it. But before I want to ask
On Wednesday 31 December 2003 14:52, Gabor Hojtsy wrote:
> And this brings us to the point of replacing the unix tools. You are on
> windows. You can have several GUI CVS clients (tortoisecvs being one of
> the easiest possibilities), you can install xsltproc with copying some
> files to the right
> Installed properly in the phpdoc-tools folder xmllint and xsltproc work very
> well, so AFAICS for proper validity checking cygwin is no requirement.
Also just for the records...
xmllint works well but xsltproc didn't complain about something (e.g.
inside ). Just be warned.
Jakub Vrana
P.S.
And this brings us to the point of replacing the unix tools. You are on
windows. You can have several GUI CVS clients (tortoisecvs being one of
the easiest possibilities), you can install xsltproc with copying some
files to the right place, and you already have PHP.
Now if you are working with the
gobaWed Dec 31 19:04:24 2003 EDT
Modified files:
/phpdoc/en bookinfo.xml
Log:
Happy new year PHPDoc
Index: phpdoc/en/bookinfo.xml
diff -u phpdoc/en/bookinfo.xml:1.35 phpdoc/en/bookinfo.xml:1.36
--- phpdoc/en/bookinfo.xml:1.35 Sat Dec 20 02:40:51 2003
+++ ph
Gabor Hojtsy wrote:
> The visual editor idea is aimed at solving the complexity of DocBook
> for authors and translators. But currently it is a more critical
> problem, that new updates take months to get on to the website (which
> does decrease the motivation of translators).
+1
The manuals are b
Gabor Hojtsy wrote:
> goba Wed Dec 31 19:04:24 2003 EDT
>
> Modified files:
> /phpdoc/en bookinfo.xml
> Log:
> Happy new year PHPDoc
I can't make this... for now, I'm still in 2003... ;)
[]s
André Æ
gobaWed Dec 31 19:35:42 2003 EDT
Modified files:
/phpdoc/scripts aspell.php bughunter.php diff_en_rev.php
entity-usage.php fixphpweb.php genPHP_INI_ENTRY.php
html_syntax.php xml_proto.php
/phpdoc/scripts/qui
gobaWed Dec 31 19:47:42 2003 EDT
Modified files:
/phpdoc/scripts checkdoc.php genfuncindex.php genfuncsummary.php
make_man.php process.php revcheck.php
sort_aliases.php
Log:
fix even more of the license stuf
The idea is to make the build system useable (and hopefully unified)
for all projects. Our needs are converging, since the PHP
documentation just needs to accomodate OO docs, long time after the
PHP-GTK and PEAR docs needed that.
Which the great problem with OO after all? Render, search, filenames?
gobaWed Dec 31 20:08:47 2003 EDT
Modified files:
/phpdoc/scripts checkent.php dbtags.php entities.php
file-entities.php.in missing-entities.php.in
phpweb-entities.php.in reference-split.php
gobaWed Dec 31 20:17:54 2003 EDT
Modified files:
/phpdoc LICENSE Makefile.in
Log:
the remaining 2003 -> 2004 fixes
Index: phpdoc/LICENSE
diff -u phpdoc/LICENSE:1.3 phpdoc/LICENSE:1.4
--- phpdoc/LICENSE:1.3 Tue Jun 10 03:46:48 2003
+++ phpdoc/LICENSE
From: [EMAIL PROTECTED]
Operating system:
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: php documentation examples contain slow code
Description:
The php.net manual contains lots of examples that use
less than desirable coding sty
kennyt Thu Jan 1 01:44:47 2004 EDT
Modified files:
/phpdoc/en/reference/array/functionsarray-search.xml
Log:
Switched argument order. It's needle, haystack, as stated just a few lines above. ;-)
Index: phpdoc/en/reference/array/functions/array-searc
ID: 26759
Comment by: ben at slax0rnet dot com
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type:Documentation problem
PHP Version: Irrelevant
Assigned To: kennyt
New Comment:
I truly can't believe the pickiness present here. In a lot of these
cases the "optimization
ID: 26759
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type:Documentation problem
PHP Version: Irrelevant
Assigned To: kennyt
New Comment:
Those 'insignificant gains' do add up. Does anyone want
to teach new PHP developers to [ab]use the
60 matches
Mail list logo
