RE: [PHP-DOC] Appendix: PHP Debugger
I would vote to rename the appendix to PHP 3 Debugger. James > -Original Message- > From: Hojtsy Gabor [mailto:[EMAIL PROTECTED]] > Sent: 20 January 2001 12:12 > To: PHP Documentation ML; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] Appendix: PHP Debugger > > > > > > Anyways, the current appendix is ut of date as it relates > to PHP 3's > > > > debugger which is no longer available in PHP 4. > > > but hp3 is still available, so it should stay inside... > > > > Hm, so we should throw away all chapters regarding extensions that are > in > > PHP 4 but not in PHP 3? Don't think so. > > > > For the time beeing this is okay, but how long will PHP 3 > stay supported > > anyway? > > The question here is, what manual the PHP 3 programmers use. They > should not use the actual manual I think, as there are so much > PHP 4 specific content... If I were a programmer using PHP 3, > I would use some older docs, but how are the others with this? > > Goba > __ > Hungarian PHP Manual :: Hungarian PHP Mirror :: http://hu.php.net/ > The starintg-point for Hungarian webmasters :: http://weblabor.hu/ >
Re: [PHP-DOC] cvs: phpdoc /en/chapters install.xml
Yeah Ill run through it and correct the few errors I can see, James - Original Message - From: "Hojtsy Gabor" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 26, 2001 2:43 PM Subject: [PHP-DOC] cvs: phpdoc /en/chapters install.xml > goba Fri Jan 26 06:43:18 2001 EDT > > Modified files: > /phpdoc/en/chapters install.xml > Log: > Inserting many-many new sections to the Windows install part. > >- Separate CGI and xSAPI installs >- Added SAPI notes (from Windows dist. README.txt) > >- Added the following server installs (from install.txt): > PWS 4 and up > Xitami > Oreilly > >- Added some text to Omni install about the built > in PHP > >- Added ISAPI to Apache, IIS, PWS sections > >- Added Windows 2000 and Me to the lists of Windows systems > >- Now it is time for someone to review my bad english grammar :) > > >
[PHP-DOC] cvs: phpdoc / global.ent /en/chapters install.xml
jmoore Fri Jan 26 08:48:53 2001 EDT Modified files: /phpdoc global.ent /phpdoc/en/chapters install.xml Log: Correcting Goba's english and some (infact lots) of whitespace changes Index: phpdoc/global.ent diff -u phpdoc/global.ent:1.69 phpdoc/global.ent:1.70 --- phpdoc/global.ent:1.69 Tue Jan 16 17:55:30 2001 +++ phpdoc/global.ent Fri Jan 26 08:48:52 2001 @@ -1,6 +1,6 @@
RE: [PHP-DOC] cvs: phpdoc /en/functions xslt.xml
> Yes it is not documented. I prefer the } else { style.
Personally I like
if ($foo)
{
} else
{
...
}
or
if ($foo)
{
}
else
{
...
}
then all braces are in same col.
James
RE: [PHP-DOC] cvs: phpdoc /en/functions xslt.xml
> But this doesn't fit into the scheme of the examples we have already in
> the manual. When I parse the source code I don't see such a malformed
> syntax. Ok, someone have used it...
this is true and PEAR also uses } else { so perhaps this is better in the
manual too
James
RE: [PHP-DOC] free translation of php specs
I believe there are already some people working on this see: http://cvs.php.net/viewcvs.cgi/phpdoc/it/ if your company feels inclined to help then please check out a copy from CVS and start on it, youll need to get some CVS accounts so you can commit back to the CVS repository. see http://www.php.net/anoncvs.php for more info and get cracking.. Its also normaly good form to contact other people mentioned in the translators files to see what they are up to. James
[PHP-DOC] cvs: phpdoc / Makefile.in
jmoore Wed Mar 7 03:54:08 2001 EDT Modified files: /phpdoc Makefile.in Log: Updating Copyright msg from php3 to php4 with new licience details. Index: phpdoc/Makefile.in diff -u phpdoc/Makefile.in:1.58 phpdoc/Makefile.in:1.59 --- phpdoc/Makefile.in:1.58 Fri Feb 9 20:46:14 2001 +++ phpdoc/Makefile.in Wed Mar 7 03:54:08 2001 @@ -1,32 +1,23 @@ +# # +--+ -# | PHP HTML Embedded Scripting Language Version 3.0 | +# | PHP Version 4.0 | # +--+ -# | Copyright (c) 1997,1998 PHP Development Team (See Credits file) | +# | Copyright (c) 1997-2001 The PHP Group| # +--+ -# | This program is free software; you can redistribute it and/or modify | -# | it under the terms of one of the following licenses: | -# | | -# | A) the GNU General Public License as published by the Free Software | -# | Foundation; either version 2 of the License, or (at your option) | -# | any later version. | -# | | -# | B) the PHP License as published by the PHP Development Team and | -# | included in the distribution in the file: LICENSE| -# | | -# | This program is distributed in the hope that it will be useful, | -# | but WITHOUT ANY WARRANTY; without even the implied warranty of | -# | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the| -# | GNU General Public License for more details. | -# | | -# | You should have received a copy of both licenses referred to here. | -# | If you did not, or have any questions about PHP licensing, please| -# | contact [EMAIL PROTECTED]| +# | This source file is subject to version 2.02 of the PHP licience, | +# | that is bundled with this package in the file LICENCE and is | +# | avalible through the world wide web at | +# | http://www.php.net/license/2_02.txt. | +# | If uou did not receive a copy of the PHP license and are unable to | +# | obtain it through the world wide web, please send a note to | +# | [EMAIL PROTECTED] so we can mail you a copy immediately| # +--+ # | Authors: Stig Bakken <[EMAIL PROTECTED]> | # +--+ +# # -# $Id: Makefile.in,v 1.58 2001/02/10 04:46:14 jmcastagnetto Exp $ +# $Id: Makefile.in,v 1.59 2001/03/07 11:54:08 jmoore Exp $ # VPATH=@srcdir@
RE: [PHP-DOC] Hi!
> > Hi! > This is not spam! > If to you this message has come, means you at one time were > registered for us on a rating or on > boards! > We invite you to work with our new project: http://www.bestloliz.com > It is new TOP in the given moment we have 20k of unique visitings > per day (thus TOP 4 days > (work only!)) If you worked with ours old top (RAPE and EXTREME, > FREE XXX TOP etc.), you will > understand that it not words told in empty, on old ratings was > 50-60k of the unique visitors per > day! Register now and you can raise popularity to the site since > get on the first places in TOP > still it is possible! > Beforehand are grateful! > Yours faithfully administration! I think we should take up their offer for the PHP Manual.. I think it would fit in well ;) James
RE: [PHP-DOC] cvs: phpdoc /en/functions classobj.xml
should be 4.0.6 James > -Original Message- > From: Daniel Beckham [mailto:[EMAIL PROTECTED]] > Sent: 27 March 2001 19:10 > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] cvs: phpdoc /en/functions classobj.xml > > > danbeck Tue Mar 27 10:09:43 2001 EDT > > Modified files: > /phpdoc/en/functions classobj.xml > Log: > one last change > > Index: phpdoc/en/functions/classobj.xml > diff -u phpdoc/en/functions/classobj.xml:1.17 > phpdoc/en/functions/classobj.xml:1.18 > --- phpdoc/en/functions/classobj.xml:1.17 Tue Mar 27 10:07:37 2001 > +++ phpdoc/en/functions/classobj.xml Tue Mar 27 10:09:42 2001 > @@ -347,7 +347,7 @@ > > > > - As of PHP 4.0.5, you can specify the class itself instead of > + As of PHP 4.0.5, you can specify the object itself instead of >class_name. For example: > > >
[PHP-DOC] .chm files
Could whoever build and added them to cvs please rebuild and readd them as binaries, at the moment all of them are corrupt in the phpweb, I got rasmus to add *.chm to cvswrappers so just cvs rm them and cvs add them again and it should work. I cant seem to get them to build here. Thanks James -- James Moore [EMAIL PROTECTED] PHP Web Scripting: http://www.php.net/ PHP QA Team: http://qa.php.net/ PHP-GTK: http://gtk.php.net/ VL-SRM: http://www.vl-srm.net/
RE: [PHP-DOC] .chm files
> > Could whoever build and added them to cvs please rebuild and > readd them as > > binaries, at the moment all of them are corrupt in the phpweb, > I got rasmus > > to add *.chm to cvswrappers so just cvs rm them and cvs add > them again and > > it should work. I cant seem to get them to build here. > > Will do, tomorrow I think. They need to be updated anyway. Im trying to build them now.. we will see if it works in a min ;) If it does Ill commit them this evening. James
RE: [PHP-DOC] php manual in man format
> Derik! > > > I just added this script as make_man.php to the phpdoc cvs tree, so that > > others can easily modify it. > > Have you tested it, or just uploaded into phpdoc? > > Goba Derick tested this before he commited it. - James
RE: [PHP-DOC] ["TelMedia.pl" ] PHP manual
The docs are right, he is wrong. - James > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of Stig Sæther Bakken > Sent: 19 April 2001 13:16 > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] ["TelMedia.pl" <[EMAIL PROTECTED]>] PHP manual > > > Hi all, > > Could someone with Windows experience verify this and commit a fix if > one is needed? > > - Stig > >
RE: [PHP-DOC] PHP easter Egg
Just wait for april 1st there is also a note in the manual about it.. http://www.php.net/manual/en/function.phpinfo.php I just censored it slightly - James > -Original Message- > From: Andrei Zmievski [mailto:[EMAIL PROTECTED]] > Sent: 23 April 2001 20:33 > To: Damien Seguy > Cc: [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] PHP easter Egg > > > On Mon, 23 Apr 2001, Damien Seguy wrote: > > Hi, > > > > Here are some PHP easter Egg. > > Should we document those? > > add this to any PHP 4 script : > > > > ?=PHPE9568F34-D428-11d2-A769-00AA001ACF42 > > ?=PHPE9568F36-D428-11d2-A769-00AA001ACF42 > > ?=PHPE9568F34-D428-11d2-A769-00AA001ACF42 > > > > This will bring some easter egg picture right from PHP > > > > Any suggestion? > > What's the point of Easter Egg if it's documented. I do wish these were > a bit easier to access. :) > > -Andrei > * It said 'Winmodem' on the box, but I still feel like I lost. *
RE: [PHP-DOC] Fw: PHP Manual note (Why [email protected] as default e-mail adderss?)
because they dont read the instructions. - James > -Original Message- > From: Hojtsy Gabor [mailto:[EMAIL PROTECTED]] > Sent: 25 April 2001 19:56 > To: PHP-DOC lista > Subject: [PHP-DOC] Fw: PHP Manual note (Why > [EMAIL PROTECTED] as default e-mail adderss?) > > > This is for annotation hunting people... (see the last lines of text) > > - Original Message - > From: "Yasuo Ohgaki" <[EMAIL PROTECTED]> > To: "Hojtsy Gabor" <[EMAIL PROTECTED]> > Sent: Wednesday, April 25, 2001 8:43 PM > Subject: Re: PHP Manual note (Why [EMAIL PROTECTED] as default > e-mail adderss?) > > > > - Original Message - > > From: "Hojtsy Gabor" <[EMAIL PROTECTED]> > > To: "Yasuo Ohgaki" <[EMAIL PROTECTED]>; "PHP Mirror List" > > <[EMAIL PROTECTED]> > > Sent: Thursday, April 26, 2001 2:48 AM > > Subject: Re: PHP Manual note (Why [EMAIL PROTECTED] as default > e-mail > > adderss?) > > > > > > > > I think one of the reason why there are questions for PHP Manual's > note is > > > > default e-mail address in note form. I guess some people are > misunderstood > > > it > > > > will be sent to php-general list. > > > > (Although, it clearly mentioned it's not the place to ask questions. > And I > > > have > > > > no idea how could possibly people misunderstood it will be sent to > > > php-general, > > > > though.) > > > > > > > > How about change it to something else? ( or make it empty and reject > > > null?) > > > > It may not reduce number of questions, but I think it's > worth to try. > > > > > > What questions, I can't understand... > > > > > > > I'm mentioning about annotated PHP Manual. It seems there are many > questions in > > note and note maintainers are busy to delete them. I was wondering why > many > > people post question to note system > > > > Yasuo Ohgaki > > > > > > > >
RE: [PHP-DOC] Installation notes for Windows
> I'd be grateful if someone on the doc team could check out my possibly > incompetent xml markup (I'm not at all familiar with the php doc > stuff), and > commit the file back into the doc tree if nobody reports any errors or > omissions in the near future. Phil, Ill try to find time to do this over the weekend and sort it then, atm Im very busy with ALevels though so Ill see what I can do. - James
RE: [PHP-DOC] [Making manual] help needed
Search the archives people have covered this multiple times with the fixes. - James > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 13 May 2001 23:06 > To: Jeroen > Cc: [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] [Making manual] help needed > > > Hello Jeroen, > > nice to have you aboard on the .nl translation. > You don;t have a linux install I guess? That makes stuff lots easier :) > Anyway, your CATALOG file could either not be found, or misses some > declarations, I dunno which exactly. I hope this info helps a little > > regards, > Derick > > On Sun, 13 May 2001, Jeroen wrote: > > > Hi, > > > > I must be really stupid with these docbooks, because I can't > succeed to make > > the manual myself :( > > > > I'm using win2k, with cygwin. > > > > This is the 'make html' output: (trimmed): > > > > > > /php/jade/jade -d html.dsl -V use-output-dir -t sgml ./phpdocxml.dcl > > manual.xml > > U:\php\jade\jade.exe:html.dsl:1:73:W: cannot generate system > identifier for > > public text "-//James Clark//DTD DSSSL Style Sheet//EN" > > U:\php\jade\jade.exe:html.dsl:7:0:E: reference to entity > "STYLE-SHEET" for > > which no system identifier could be generated > > U:\php\jade\jade.exe:html.dsl:1:0: entity was defined here > > U:\php\jade\jade.exe:html.dsl:7:0:E: DTD did not contain > element declaration > > for document type name > > U:\php\jade\jade.exe:html.dsl:2:0:E: notation "DSSSL" for entity > > "docbook.dsl" undefined > > U:\php\jade\jade.exe:html.dsl:17:12:E: element "STYLE-SHEET" undefined > > U:\php\jade\jade.exe:html.dsl:18:24:E: there is no attribute "ID" > > U:\php\jade\jade.exe:html.dsl:18:47:E: there is no attribute "USE" > > U:\php\jade\jade.exe:html.dsl:18:56:E: element "STYLE-SPECIFICATION" > > undefined > > U:\php\jade\jade.exe:html.dsl:19:25:E: element > "STYLE-SPECIFICATION-BODY" > > undefined > > U:\php\jade\jade.exe:html.dsl:32:27:E: there is no attribute "ID" > > U:\php\jade\jade.exe:html.dsl:32:46:E: there is no attribute "DOCUMENT" > > U:\php\jade\jade.exe:html.dsl:32:59:E: element "EXTERNAL-SPECIFICATION" > > undefined > > U:\php\jade\jade.exe:html.dsl:34:13:E: end tag for > "EXTERNAL-SPECIFICATION" > > omitted, but its declaration does not permit this > > U:\php\jade\jade.exe:html.dsl:32:0: start tag was here > > U:\php\jade\jade.exe:E: specification document does not have the DSSSL > > architecture as a base architecture > > PHP ManualStigSæther BakkenAlexanderAulbachEgonSchmidJimWinsteadLars > > TorbenWilsonRasmusLerdorfZeevSuraskiAndreiZmievskiJouniAhtoSat May 12 > > 00:39:47 2001StigSæther BakkenEgonSchmid19971998199920002001the PHP > > Documentation GroupCopyright > > This manual is © Copyright 1997, 1998, 1999, 2000, 2001 by > > the PHP Documentation Group. The members of this group are listed > > (and now follows the whole manual in plain-text) > > > > > > I don't know what the first error really means, memory and diskspace are > > okay, U: drive is world-r/w, and I really believed I've done > anything that > > was necessary... > > > > > > I did this: > > - extracted the newest dsssl from http://nwalsh.com/docbook/dsssl/ into > > [U:]/php/docbook > > - extracted the newest xsl from http://nwalsh.com/docbook/xsl/ into > > [U:]/php/xsl/docbook > > (U: is my cygwin-root) > > > > I ran autoconf, then: > > $ ./configure --with-dsssl=/php/docbook > --with-xsl=file:///php/xsl/docbook > > loading cache ./config.cache > > checking for perl... (cached) /usr/bin/perl > > checking for docbook.dsl... in /php/docbook > > checking for docbook.xsl... in file:///php/xsl/docbook > > checking for PHP source path... ../php4 > -- > > this dir doesn't exist! does that matter? > > checking for language... en (default) > > checking for treesaving... saving trees: #f > > checking for openjade... (cached) no > > checking for jade... (cached) /php/jade/jade > > creating ./config.status > > creating Makefile > > (more, no errors) > > > > I'm not certain about the --with-xsl parameter. I tried with > and without the > > file:// prefix. This way, html.xsl looks the best to me (with > on line 11: > > ), > of course I > > checked the existence of that file) > > > > I copied all files in the root of my phpdoc directory to > > http://www.a-es2.uu.nl/~jeroen/phpdoc/ > > > > Note: > > - I got EXACTLY the same errors when I didn't use the > --with-xsl options, > > and the html.xsl line 11 looked like: href="no-auto-detect"... > > > > - In my makefile, $CATALOG is set to the empty string. > > > > - I don't have the php4 sources downloaded in ../php4, as is > stated at the > > configure. > > > > I'm sorry to bother you with this, as soon as I've got it up > and running, > > I'll update the README.win32 file... > > > > Greetings, > > Jeroen van Wolffelaar > > > > > > Derick Rethans > > - > PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED] >
RE: [PHP-DOC] cvs: phpdoc / README.win32
> Modified files: > /phpdoc README.win32 > Log: > Fool proof version. > If you're capable of writing documentation, you > should now be able to get it running with M$ without > ever having to wonder what SGML etc is. > XSL things have been removed Is that wise.. some people might want to build with XSL and the stylesheets are fairly well maintained. I would restore it (more information the merrier) but make it clear it isnt the supported way of building phpdoc. - James
RE: [PHP-DOC] Function References not showing up in docs for mixed case function names
> > bad: Foo() does bar; > > good: The function foo() does bar. > > > > Daniel > > I agree with your second assertion. I could see a lot of > users getting confused if the first were followed blindly, > though (say, if one was documenting C). Which is one reason > (besides style) why I agree with the second assertion...:) Im sorry but I feel we should keep all function names lowercase. Take a look at http://php.net/manual/en/ref.pdf.php now, that really looks ugly too me, there is no reason to have function names at beginning of sentences and lets keep the manual consistent, if its all lowercase we will encourage people to name their functions properly etc, we are not going to start putting PdF_OpeN in the manual just because its supported lets keep the manual consistent and keep it lowercase, this has worked for the past x years and there is no real reason to change it. - James
Re: [PHP-DOC] cvs: phpdoc /howto generating.xml
> On Sun, 18 Nov 2001, Gabor Hojtsy wrote: > > > Nice to hear that it is every day now :)) I'll make the moficiations > > in the text to express this. Where have you found cron for win? > > Windows has something called 'system-agent' works like cron for me. It also has AT and the Scheduled tasks services depending on what version of windows your running - James
Re: [PHP-DOC] MySQL examples need review
> > What do others think about that? > I give a +1 for adapting the PEAR coding standard for Manual examples. -1 for anything complicated in the manual. Keep everything clear and concise why do we need to clutter examples with PEAR error everywhere (Nothing against pear I think its great but I dont think its all that clear for examples in a manual.) Most code out there isnt written with PEAR at all and thus when comparing code and the manual it might be unclear to the reader. - James
Re: [PHP-DOC] Coding Std. [was: Re: [PHP-DOC] MySQL examples need review]
> > $variables shoud be concatenated with '. instead of using "$var strng". > -1. I prefer "$var string". $var." string" is less ambigious. Actually it should be $var.' string' as "$var string" and '$var string' behave differently $var.' string' and $var." string" work the same. - James
RE: [PHP-DOC] cvs: phpdoc /it/functions w32api.xml
I am right in the middle of rewriting this now.. (Currently doing the asm to pass stuff by ref rather than by val so its probably an idea if this isnt documented yet as its going to change!!) James -Original Message- From: Simone Cortesi [mailto:[EMAIL PROTECTED]] Sent: 25 March 2002 19:12 To: [EMAIL PROTECTED] Subject: [PHP-DOC] cvs: phpdoc /it/functions w32api.xml cortesi Mon Mar 25 14:12:20 2002 EDT Added files: /phpdoc/it/functionsw32api.xml Log: adding translation by Rocco Curcio up to EN 1.4 Index: phpdoc/it/functions/w32api.xml +++ phpdoc/it/functions/w32api.xml Funzioni W32api Funzioni W32api w32api_set_call_method Imposta il metodo di chiamata usato Descrizione voidw32api_set_call_method intmethod &warn.experimental.func; &warn.undocumented.func; w32api_register_function Registra la funzione function_name dalla libreria con PHP Descrizione boolw32api_register_function stringlibary stringfunction_name &warn.experimental.func; &warn.undocumented.func; w32api_invoke_function ) Invoca la funzione funcname con gli argomenti passati dopo il nome della funzione Descrizione mixedw32api_invoke_function stringfuncname &warn.experimental.func; &warn.undocumented.func; w32api_deftype ...) Definisce un tipo per l'uso con altre w32api_functions Descrizione intw32api_deftype stringtypename stringmember1_type stringmember1_name &warn.experimental.func; &warn.undocumented.func; w32api_init_dtype Crea un'istanza ai tipi di dati typename e li riempie con i valori val1, val2, la funzione quindi restituisce un DYNAPARM che può essere passato all'invocazione di una funzione come parametro Descrizione resourcew32api_init_dtype stringtypename mixedval1 mixedval2 &warn.experimental.func; &warn.undocumented.func;
RE: [PHP-DOC] "optimizing" doc builds?
I did this with the PHP-GTK doc's for a while until I optimised the stylesheets enough that build times were quicker (Although it could probably do with it again now). I had one stylesheet which would take an argument of the id to build and it would load the entire xml file then just output that file (Good for checking documentation youve just done), the other option I had was to pass it ID's and it would only process those ID's (This was actually a stypesheet that I had a template for then used sed and awk to fill in the blanks). There were some problems with the output at times but nothing a bit more work couldnt fix. James -Original Message- From: Gabor Hojtsy [mailto:[EMAIL PROTECTED]] Sent: 30 March 2002 16:50 To: cece@balaton; PHPDOC Subject: Re: [PHP-DOC] "optimizing" doc builds? > An idea: > What about splitting out the doc builder? > > - Run one-html, multi-html and online docs builder frequently > (day-by-day all language). > - Pdf and other builders may run weekly > > Or can we do a format priority list based on popularity? Nice idea. ;) I have also thought about a system, where we can only rebuild the files changed. Though I cannot think of any good method where we can preserve the autonumbering, links to other files, etc. Goba
