[PHP-DOC] testing!
-- James Cox - Engineer - [EMAIL PROTECTED] Global Reach Technology - Empowering Business Online
Re: [PHP-DOC] Re: server(s) for the phpdoc team
On 26 May 2004, at 10:01, Gabor Hojtsy wrote: I think you misunderstood the point. We would not like to split up the stuff and host on different servers. We would better live with a server which is capable of serving our needs (building docs in HTML, PDF, etc., regular building of revcheck info, providing services for translation teams, etc.). I need to set-up this for real, it 'kinda' works now, but misses some parts (ie. for PDF). I hope get it this done later this week (as soon as I settled in here). But, I don't see really why we need to have this same box as a testbed for livedocs; I don't really want people messing with the set-up of this machine. I myself would be fine with a different testbed. Our first goal is to make regular builds work again for the often requested formats (including PDF). Then if it is done, it would be nice to set up a server with public web accessibility to host stuff which helps documentation authors and translators cope with our system (revcheck outputs, readable build logs, maybe even websites hosted on that machine containing information for translation teams, or at least links to the team websites - now every team has its website elsewhere, etc). This should be the basis for the documentation team website, which would host the dochowto too. Given that maintaining yet another machine to publicly test livedocs might not be a good idea, this machine would be able to serve as a testbed for livedocs too. Now what do you think about this two server setup suggestion? I have a server that will be ready soon available for your use... you need to draw up some guidelines for using it however, as it wouldn't be under the immediate purview of the php systems team - so we'd need to know the sorts of things you plan to do - i think it'd be ok to add plain user accounts for php documentors - but we'd need to limit those who get sudo.
Re: [PHP-DOC] Re: distribution of INI information in the manual
We can get you a space for doc building and so forth, but right now we're working on some other important stuff that takes precedence.. - james On 24 May 2004, at 15:33, Gabor Hojtsy wrote: As Mehdi pointed out, he was able to get some hardware and hosting offer, and the future admin of the server also offered root access to systems people, so if that admin has no opportunity to set up the services on the server, than maybe systems@ has? BTW Derick told me that the current docs. machine should not be made public. Maybe because of the bandwidth issues, I am not aware of the real reason... Goba If you come up with a concrete list of what you need to do, we should be able to sort something out. IIRC, the docs.php.net box is marked for phpdoc (but has some bandwidth problems?). --Wez. -Original Message- From: Gabor Hojtsy [mailto:[EMAIL PROTECTED] Sent: 24 May 2004 15:19 To: Wez Furlong Cc: 'Nuno Lopes'; 'Mehdi Achour'; 'PHPdoc'; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [PHP-DOC] Re: distribution of INI information in the manual I know you guys are overly prejudiced against systems@, but why not run it on our own systems?? Our experience was that the guys at systems are already overloaded with work, and it would probably not be a good idea to put more load on them. There are some long awaiting stuff, which would need that new machine. The PDFs are not built for a long time now, and the so called 'new machine' - which is probably building the HTML versions right now - was said to have enough resources to build the PDFs. There is a good amount of demand for them, and we need a strong machine to build them. Goba -- James Cox - james (at) imajes (dot) info - http://imajes.info/
Re: [PHP-DOC] Re: Setting up a website for the phpdoc team
David: we'd be interested in what you have to offer - please contact me directly and we will figure something out. :) thanks, - james
Re: [PHP-DOC] Re: Setting up a website for the phpdoc team
On 1 Feb 2004, at 12:09, Mehdi Achour wrote: Derick Rethans wrote: On Sat, 31 Jan 2004, Mehdi Achour wrote: a big big big +1 here :) It will be great to allow some ssh access for some active persons of the doc team. Having the doc.php.net on another (isolated) machine will also make happy systems@ IMHO :) Why do you need ssh access? Because you always say that you're too busy ? :) It's also handy for webmastering to have the ability of quickly updating the site. For the last problem with bugs.php.net, all I was able to do was sitting there at three a.m. in the morning fighting my sleep to see if the errors were fixed. If only I was able to do something like : ssh bugs.php.net cd /var/www/ cvs up -PAd Which would break everything because all the systems are running a very precise set of scripts and structures that someone not familiar with would essentially break. I understand that systems staff can be a little unresponsive - we do, after all, have day jobs. If some other members of the project wished to become responsible for infrastructure, i'm sure we'd consider additions to the group.
Re: [PHP-DOC] Re: Setting up a website for the phpdoc team
On 31 Jan 2004, at 22:20, David Costa wrote: On Jan 31, 2004, at 11:15 PM, Mehdi Achour wrote: Gabor Hojtsy wrote: - revcheck output hosting - build logs, error reports Those will end up on the doc build machine, which is now sc1.php.net (and yes, they still need to be enabled) So then it will be ideal to set up this docteam website on the same machine, since a lot of the needed checkouts are already present there... I'm not too happy with that, as this box has no visible websites, it doesn't even run apache or mysql. It's solely meant for rsync, snapsbuilding and docbuilding. Ah, all right... Understandable. Then the question is still up to systems@ whether there is some willingness to set up a machine/vhost, or we will better do with opening a vhost on some new donated machine offered by a docteam member? I am available for a full machine donation e.g. a server at www.servercove.com ( nice guys as you can chose which distribution and pretty fast on tickets) or ev1servers.net is something I could sponsor (monthly fee). Any provider will do for me, as long as it is within the same budget ;) The docs leader could have the ssh access of everything they want as my role would be of mere sponsor (and no, I don't need any particular mention/link on the site..so it's a pure donation). Let me know if there is any interest. I am ready Regards David Costa The added benefit of the latter option would be that we will not be reliant on the systems@ group for configuration changes, but the site could still be registered as doc.php.net, and we can be more flexible with its development and setup... The more I think about it, the more I like this option :) -- James Cox (Editor) :: [EMAIL PROTECTED] :: http://www.apress.com/ Apress. The Experts Voice (tm)
[PHP-DOC] Combating the spam
All, in an effort to negate the effect of the Sobig virus sending mail to these lists, I have disabled the ability to post to the list without being subscribed. This will screw up a few auto-generated mails (eg, the phpdoc bugs and stats) but it's better than having 10 virus mails per hour appear on the lists. Any problems, just reply to this mail. Thanks, -- james -- James Cox :: james at imajes dot info :: http://imajes.info/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ The good people sleep much better at night than the bad people. Of course, the bad people enjoy the waking hours much more. - Woody Allen -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] Next build?
I will kick of a build in the next hour, and then on continuously. You guys bugged me enough to actually get everything moved over so I can have a box just for builds. :) -- james > -Original Message- > From: Dimitris Glezos [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 17, 2003 10:21 PM > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] Next build? > > > > Hello, > > There are some people, including a university professor and > other fellow translators who have done a great job, that keep > asking me when will the greek php manual appear on php.net, > and I keep telling them "it will when the next build will take place". > > Do we know approximately when will the build (at least for the EL > module) take place? > > Thanks in advance, > > Dimitris > > > - > Department of Computer Engineering and Informatics > University of Patras, Greece (ceid.upatras.gr) > ICQ: 9295964, PGP: 0xA5A04C3B > > "He who gives up functionality for ease of use > loses both and deserves neither." (Anonymous) > - > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] Web manual and manual.ced
> On Thu, 6 Mar 2003, Gabor Hojtsy wrote: > > > > I know that someone has already told you that it was ages since the > > > manual on www.php.net was last built. I can build it on my > box without a > > > problem, so there is no syntax error in the manual (afaik). > > > > There may be some problems with the programs and tools available there, > > I don't know... > > There are no problems, it's just not in cron yet Actually, there are problems. Building the manual seems to a: take forever, and b: causes rsync to fight with the cpu, which is not a good thing. Builds will start again in about a week once i move some stuff around. -- james -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] Re: Suggestion for a clean PHP 5 - Manual
The problem with PDF etc is that the entire library of pdf files adds _another_ 80MB to the rsync distribution. I couldn't add them before when we were using va to rsync -- jirka, i need to re-add your account on the new box and ask you to upload them again. I will get them rsynced automatically this time. :) -- james > -Original Message- > From: Jirka Kosek [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 23, 2003 3:07 PM > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] Re: Suggestion for a clean PHP 5 - Manual > > > Thomas schöfbeck wrote: > > > Since we aren't able to build a pdf-version due to a lack of resources: > > I built PDFs for several languages few months ago and they aren't still > published on web-site, even I urged it at least one or two times since > then :-( > > -- > - > Jirka Kosek > e-mail: [EMAIL PROTECTED] > http://www.kosek.cz > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Cybercash no more
On Tue, 2002-12-31 at 11:00, John Coggeshall wrote: > I was just looking through the CVS tree: > > http://cvs.php.net/cvs.php/php4/ext/cybercash > > And I noticed that the cybercash extension apparently simply doesn't > exist anymore. It looks like the service itself has disappeared > (actually been baught out) hence, no need for an extension. > > I don't have access to my tree, can someone confirm what I have found > and remove the documentation for the extension? I see absolutely no > reason why we should keep the documentation at all, as anybody who was > using the extension simply can't anymore if the service simply doesn't > exist. > I think we could remove the documentation from the main tree and place it into the pear documentation. We need to look at a general way for providing "bc" for cases like this so links don't end up broken. -- james -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] CVS module
On Tue, 2002-12-31 at 15:14, Gabor Hojtsy wrote: > > I'm tired for asking (writing to [EMAIL PROTECTED] ) to create module > phpdoc-lt > > for lithuanian language translation. Maybe someone there can help me? > > Avtually only [EMAIL PROTECTED] or [EMAIL PROTECTED] can help you. Others have > no access to the machines directly... > I am actually fixing this... -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Can't see build log
OK, because of the presence of phpdoc/zh (the bad checkin) it couldn't checkout phpdoc-zh to it... so it got all hot and flustered. Same for tw. I have tar'ed the old zh and tw trees, and deleted them from phpdoc. zh looks checked out now ok, so next build should see us a built (or not) zh tree. Thanks, James On Fri, 2002-12-20 at 03:38, Dallas Thunder wrote: > When I try to access http://www.php.net/zh/blog, I get this response: > > Search Results > Sorry, no documents matched your search for "manual/zh/build.log.gz". > > If you can see Chinese build logs, would you please send it to me? So I can > find out what was wrong. Thanks! > > > "James Cox" <[EMAIL PROTECTED]> > :[EMAIL PROTECTED] > > As i have said time and time again, there are build logs. > > > > the Chinese manual fails to build. Please consult the build log @ > > php.net or a possibly more up-to-date one @ > > > > http://rsync.php.net/~imajes/manual/ > > > > Thanks, > > > > James > > > > On Fri, 2002-12-20 at 02:47, Dallas Thunder wrote: > > > Dear PHP doc members, > > > > > > The PHP Chinese manual is not available since Nov 19th. When try to > access > > > http://www.php.net/manual/zh/, the browser address will become > > > http://www.php.net/search.php?show=manual&pattern=manual%2Fzh%2F and > > > displays > > > Search Results > > > Sorry, no documents matched your search for "manual/zh/". > > > > > > There's also no building log. > > > Our Chinese translation team have checked again and again, but have no > idea > > > about what's going on here. We can successfully build PHP manual in our > own > > > computer. > > > > > > Would someone please check the PHP manual tree and make Chinese manual > > > available, many thanks! > > > > > > > > > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Serious request about online Chinese manual
As i have said time and time again, there are build logs. the Chinese manual fails to build. Please consult the build log @ php.net or a possibly more up-to-date one @ http://rsync.php.net/~imajes/manual/ Thanks, James On Fri, 2002-12-20 at 02:47, Dallas Thunder wrote: > Dear PHP doc members, > > The PHP Chinese manual is not available since Nov 19th. When try to access > http://www.php.net/manual/zh/, the browser address will become > http://www.php.net/search.php?show=manual&pattern=manual%2Fzh%2F and > displays > Search Results > Sorry, no documents matched your search for "manual/zh/". > > There's also no building log. > Our Chinese translation team have checked again and again, but have no idea > about what's going on here. We can successfully build PHP manual in our own > computer. > > Would someone please check the PHP manual tree and make Chinese manual > available, many thanks! > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] manual builds (when)
actually, it was rebuilt weekly, and sorta built daily. this will happen again, i just need to tidy the scripts and then cronjob it, something i'll do tomorrow. -- james > -Original Message- > From: Philip Olson [mailto:[EMAIL PROTECTED]] > Sent: Saturday, November 30, 2002 4:36 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [PHP-DOC] manual builds (when) > > > Hi- > > The /en/ manual hasn't been built since November 20, > which was about 10 days ago. Can you please let us > know how often this will be built these days? It > used to be roughly every 48 hours. Why does the > entire build process (phpweb, phpdoc, etc.) seemingly > take so much longer since the big move? > > Regards, > Philip > > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] PHP Documentation HOWTO...
... is now mirrored: http://www.php.net/manual/howto/ this should sort out all the problems of downloading the file from cvs(.php.net). -- james -- James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] latest builds
Ok, so the round of builds i kicked off the other day are done. http://rsync.php.net/~imajes/manual/ seems the following langs didn't build correctly: ar, fi, fr, he, hk, kr, pl, ro, ru, sk, sl, sv, tr. So, i propose that we spend the next couple of weeks doing nothing but fixing (or depreciating) builds. Welcome to Operation "Manual" Fix! what we need to do is check the build logs at the above mentioned url, and correct the errors that it specifices when a make test (or a make test_man_gen) is run. for translations that seem to be more or less non existant, I propose that they just don't get built, and so we don't end up with 5% translated builds for the site, which just seems to be silly. Hmm, ok that seems to be it for now... but lets get builds fixed. If there isn't enough of a build in a translation, then let me know and i will remove it from the build tree. -- james -- James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] cvs: phpdoc /en/reference/ldap reference.xml
Sara. please commit at once, not singular files. This just generates extra noise. -- james > -Original Message- > From: Sara Golemon [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 25, 2002 2:15 AM > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] cvs: phpdoc /en/reference/ldap reference.xml > > > pollita Sun Nov 24 21:15:15 2002 EDT > > Modified files: > /phpdoc/en/reference/ldap reference.xml > Log: > Added note for Win32 users. "Must copy libsasl.dll" > > > Index: phpdoc/en/reference/ldap/reference.xml > diff -u phpdoc/en/reference/ldap/reference.xml:1.4 > phpdoc/en/reference/ldap/reference.xml:1.5 > --- phpdoc/en/reference/ldap/reference.xml:1.4Sat Sep 14 > 17:18:20 2002 > +++ phpdoc/en/reference/ldap/reference.xmlSun Nov 24 21:15:14 2002 > @@ -1,5 +1,5 @@ > > - > + > >LDAP functions >LDAP > @@ -108,6 +108,15 @@ > use the linkend="install.configure.with-ldap">--with-ldap > configuration option when compiling PHP to enable LDAP support. > > + > + Note to Win32 Users > + > + In order to enable this module on a Windows environment, > you must copy > + libsasl.dll from the DLL folder of > the PHP/Win32 binary > + package to the SYSTEM32 folder of your windows machine. > (Ex: C:\WINNT\SYSTEM32 > + or C:\WINDOWS\SYSTEM32) > + > + > > > &reference.ldap.ini; > > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] RE: [DOC-HU] build logs
to be honest, the only thing that needs to happen is a conversion to xslt and not jade. Any other things are incidental. -- james > > > Build logs for translations are available at: > > > > http://rsync.php.net/~imajes/manual/ > > > > the cronjob copies them every 5 minutes, but be warned, they may not > update > > for weeks on end ! > > I just wanted to say, that building PDFs is not needed right now, > as we do not have links to PDF files (because they are incomplete). > But as I have seen the needed programs are not installed anyway: > > # a hack around bugs in jade/jadetex... > mv php_manual_hu.tex php_manual_hu.tex.tmp > sed -e '/HeadingText/,/endHeadPar/ s/_/\\137/g' php_manual_hu.tex.tmp > > php_manual_hu.tex > rm php_manual_hu.tex.tmp > jadetex php_manual_hu.tex > make: jadetex: Command not found > make: [php_manual_hu.dvi] Error 127 (ignored) > jadetex php_manual_hu.tex > make: jadetex: Command not found > make: [php_manual_hu.dvi] Error 127 (ignored) > jadetex php_manual_hu.tex > make: jadetex: Command not found > make: [php_manual_hu.dvi] Error 127 (ignored) > dvipdfm -o php_manual_hu.pdf -p a4 php_manual_hu.dvi > make: dvipdfm: Command not found > make: *** [php_manual_hu.pdf] Error 127 > > BTW the PDF build parts may be removed from the mirror build > targets, until someone finds a real solution for the problem... > This would make the builds faster... > > Goba > > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] build logs
Build logs for translations are available at: http://rsync.php.net/~imajes/manual/ the cronjob copies them every 5 minutes, but be warned, they may not update for weeks on end ! -- james -- James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] he build failed
http://rsync.php.net/~imajes/manual/he-build.log.gz -- James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] hk build failed
http:/rsync.php.net/~imajes/manual/hk-build.log.gz -- james -- James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] fi translation...
good thinking batman! > -Original Message- > From: Derick Rethans [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 21, 2002 9:03 PM > To: James Cox > Cc: phpdoc > Subject: Re: [PHP-DOC] fi translation... > > > On Thu, 21 Nov 2002, James Cox wrote: > > > is broken: > > They're missing some entities, better send this to the > [EMAIL PROTECTED] list. > > Derick > > > > > >>> running make test_man_gen ... > > touch .manual.xml > > CONFIG_FILES=manual.xml CONFIG_HEADERS= ./config.status > > creating manual.xml > > /usr/bin/nsgmls -wno-idref -i lang-fi -D . -s > > /local/mirrors/phpdoc/dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml > > > /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/filesystem/func > tions/fget > > s.xml:72:23:E: character data is not allowed here > > > /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/filesystem/func > tions/fget > > ss.xml:32:23:E: character data is not allowed here > > > /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/filesystem/func > tions/file > > .xml:30:23:E: character data is not allowed here > > /usr/bin/nsgmls:entities/missing-ids.xml:3:37:E: general entity > > "MissingStuff" not defined and no default entity > > make: *** [test_man_gen] Error 1 > > > > -- > > James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ > > Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] fi translation...
is broken: >>> running make test_man_gen ... touch .manual.xml CONFIG_FILES=manual.xml CONFIG_HEADERS= ./config.status creating manual.xml /usr/bin/nsgmls -wno-idref -i lang-fi -D . -s /local/mirrors/phpdoc/dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/filesystem/functions/fget s.xml:72:23:E: character data is not allowed here /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/filesystem/functions/fget ss.xml:32:23:E: character data is not allowed here /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/filesystem/functions/file .xml:30:23:E: character data is not allowed here /usr/bin/nsgmls:entities/missing-ids.xml:3:37:E: general entity "MissingStuff" not defined and no default entity make: *** [test_man_gen] Error 1 -- James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] manual build issues (hu)
the server will go down for 5 minutes later us time so that we can install more memory at this point i'll start a new doc build, so i can get a: new docs, and b: build logs... -- james > -Original Message- > From: Gabor Hojtsy [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 19, 2002 7:20 PM > To: Philip Olson > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] manual build issues (hu) > > > > > > It appears that all build logs are missing. Also, > > > > the /en/ build is about seven days old. AFICT the > > > > only missing online manual is /hu/. Strangly, > > > > download-docs.php does list a working /hu/ version. > > > > > > It's list was restored some days ago with old manual > > > contents. The downloads always display old packages > > > as long as news ones are not available... > > > > In this case a check should exist that at least puts > > this old build into phpweb too as opposed to an empty > > directory. > > Manuals are not deleted from phpweb in normal times, so > old manuals are preserved in both the online reading area > and the download ares. Now after the server updates, we > have a strange state and until everything comes back it > will stay this way I think... > > Goba > > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] manual build issues (hu)
Yes, all the builds are going to be delayed a few days now till we get the memory upgrade in. -- james > -Original Message- > From: Philip Olson [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 19, 2002 5:57 PM > To: Gabor Hojtsy > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] manual build issues (hu) > > > > It appears that all build logs are missing. Also, > the /en/ build is about seven days old. AFICT the > only missing online manual is /hu/. Strangly, > download-docs.php does list a working /hu/ version. > > Philip > > > On Tue, 19 Nov 2002, Gabor Hojtsy wrote: > > > Hi! > > > > See http://php.net/manual/hu (it's quite empty). The only thing the > > revcheck file says: "The hu language code is not valid". There is even > > no build log. What does that mean, what is the problem. I don't think > > it is something I can solve... > > > > Goba > > > > > > > > > > > > -- > > PHP Documentation Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] phpdoc building woes
oh, hey, now i haven't replied yet! :) > > > not having seen any replies to this, i'm slightly annoyed, but > i'll assume > > people didn't see my point / questions in the email. > > > > so, i'll make it to the point: > > > > do we need to run test_man_gen through the process, and if so, why is it > > that half the translations aren't building? > > Yep, there is no point in trying to build without running "test_man_gen", > it is already a stripped down version of "test" to test for only those > things, which will stop generation anyway. So it would only take more time > to omit that test, as build will fail anyway. that's what i figured. > > The reason for the failure is that there were some major restructuring > in the manual and some teams are not up to date. > good -- i had pondered it was a build error down to a bad setup. > For things like you quoted from the ar of fr build problems, they seem > to be language specific (non SGML character usage). These can only be > corrected by the authors. The MissingStuff entity missing is probably > simply becuase the language's language-defs.ent file is not updated. > > So the errors I can see our language specific and not reported because > the build system is in bad shape... I'll try and check the hungarian > translation to fix build issues. > > BTW do you have any answer to our question regarding the build problems > on PHP.net? See http://php.net/blog/hu for example (it is some core > problem). yeah, that was the lack of a core file not being run, it's been fixed now.. -- james -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] phpdoc building woes
so, not having seen any replies to this, i'm slightly annoyed, but i'll assume people didn't see my point / questions in the email. so, i'll make it to the point: do we need to run test_man_gen through the process, and if so, why is it that half the translations aren't building? -- james > -Original Message- > From: James Cox [mailto:[EMAIL PROTECTED]] > Sent: Friday, November 15, 2002 1:23 AM > To: phpdoc > Cc: [EMAIL PROTECTED] > Subject: [PHP-DOC] phpdoc building woes > > > Guys, > > So the reason that rsync isn't back on yet is that phpweb is _STILL_ > building. That's like longer than 24 hours!! > > :/local/mirrors/phpweb/manual/ar:$ zcat build.log.gz |head -n 1 > >>> starting build at: Wed Nov 13 08:29:35 PST 2002 > :/local/mirrors/phpweb/manual/ar:$ date > Thu Nov 14 17:04:47 PST 2002 > > i'm struggling to work out why it's taking so long. actually, no, they > haven't upgraded memory in this box yet, i don't think: > > :/local/mirrors/phpweb/manual/ar:$ free > total used free sharedbuffers cached > Mem:255612 251332 4280 0 13052 141968 > > Anyhow, the point is with whatever memory, it's damn slow! > (general prod in > the direction of Gabor and Harmut... :)) > > to business. trying to build peardoc has some issues: > > >>> running make html ... > touch .manual.xml > CONFIG_FILES=manual.xml CONFIG_HEADERS= ./config.status > creating manual.xml > /usr/bin/openjade -wno-idref -d html.dsl -V use-output-dir -t sgml > ./phpdocxml.dcl manual.xml > /usr/bin/openjade:manual.xml:40:10:E: general entity "DevelopersGuide" not > defined and no default entity > make: *** [html/index.html] Error 1 > > this is only for a couple of the translations, so i'm not > entirely sure why > i am seeing this bug. However, bad entities has caused a few > translations to > fail, so some advice or fixage of source would be good! > > phpweb has failed some: > > for the ar translation: > > /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/curl/reference. > xml:26:23: > E: character data is not allowed here > /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/curl/reference. > xml:27:9:E > : document type does not allow element "para" here > /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/curl/reference. > xml:34:12: > E: end tag for "section" which is not finished > /usr/bin/nsgmls:I: maximum number of errors (200) reached; change with -E > option > make: *** [test_man_gen] Error 1 > > no sure why i am seeing this... again, advice appreciated. > > from fr trans: > > /usr/bin/nsgmls:/local/mirrors/phpdoc/fr/reference/pgsql/functions > /pg-field- > is-null.xml:22:39:E: non SGML character number 141 > /usr/bin/nsgmls:/local/mirrors/phpdoc/fr/reference/zlib/functions/ > readgzfile > .xml:35:9:E: non SGML character number 143 > /usr/bin/nsgmls:entities/missing-ids.xml:3:37:E: general entity > "MissingStuff" not defined and no default entity > make: *** [test_man_gen] Error 1 > > perhaps test_man_gen doesn't need to be run, and we should force > generation > on the build machine? > > so far, the following tranlations have been done: > > 12k ar > 24M cs > 24M de > 24M en > 23M es > 12k fi > 12k fr > 12k he > 12k hk > 12k hu > 24M it > 24M ja > 12k kr > > basically any dir that is 12k didn't build, for some reason. mostly for > MissingStuff being ... well, missing :) > > Thanks, > > James > > -- > James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ > Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] pt_BR build fail
yeah, it's old. -- james > -Original Message- > From: André LFS Bacci [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 14, 2002 2:52 PM > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] pt_BR build fail > > > http://www.php.net/manual/pt_BR/build.log.gz > > >>> starting build at: Qua Nov 13 05:26:57 PST 2002 > >>> making work directory ... > >>> running ./configure --with-lang=pt_BR ... > /local/bin/build-manual: /local/mirrors/phpdoc/configure: No such file or > directory > > Any ideia? > > []s > > André Æ > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] phpdoc building woes
Guys, So the reason that rsync isn't back on yet is that phpweb is _STILL_ building. That's like longer than 24 hours!! :/local/mirrors/phpweb/manual/ar:$ zcat build.log.gz |head -n 1 >>> starting build at: Wed Nov 13 08:29:35 PST 2002 :/local/mirrors/phpweb/manual/ar:$ date Thu Nov 14 17:04:47 PST 2002 i'm struggling to work out why it's taking so long. actually, no, they haven't upgraded memory in this box yet, i don't think: :/local/mirrors/phpweb/manual/ar:$ free total used free sharedbuffers cached Mem:255612 251332 4280 0 13052 141968 Anyhow, the point is with whatever memory, it's damn slow! (general prod in the direction of Gabor and Harmut... :)) to business. trying to build peardoc has some issues: >>> running make html ... touch .manual.xml CONFIG_FILES=manual.xml CONFIG_HEADERS= ./config.status creating manual.xml /usr/bin/openjade -wno-idref -d html.dsl -V use-output-dir -t sgml ./phpdocxml.dcl manual.xml /usr/bin/openjade:manual.xml:40:10:E: general entity "DevelopersGuide" not defined and no default entity make: *** [html/index.html] Error 1 this is only for a couple of the translations, so i'm not entirely sure why i am seeing this bug. However, bad entities has caused a few translations to fail, so some advice or fixage of source would be good! phpweb has failed some: for the ar translation: /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/curl/reference.xml:26:23: E: character data is not allowed here /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/curl/reference.xml:27:9:E : document type does not allow element "para" here /usr/bin/nsgmls:/local/mirrors/phpdoc/en/reference/curl/reference.xml:34:12: E: end tag for "section" which is not finished /usr/bin/nsgmls:I: maximum number of errors (200) reached; change with -E option make: *** [test_man_gen] Error 1 no sure why i am seeing this... again, advice appreciated. from fr trans: /usr/bin/nsgmls:/local/mirrors/phpdoc/fr/reference/pgsql/functions/pg-field- is-null.xml:22:39:E: non SGML character number 141 /usr/bin/nsgmls:/local/mirrors/phpdoc/fr/reference/zlib/functions/readgzfile .xml:35:9:E: non SGML character number 143 /usr/bin/nsgmls:entities/missing-ids.xml:3:37:E: general entity "MissingStuff" not defined and no default entity make: *** [test_man_gen] Error 1 perhaps test_man_gen doesn't need to be run, and we should force generation on the build machine? so far, the following tranlations have been done: 12k ar 24M cs 24M de 24M en 23M es 12k fi 12k fr 12k he 12k hk 12k hu 24M it 24M ja 12k kr basically any dir that is 12k didn't build, for some reason. mostly for MissingStuff being ... well, missing :) Thanks, James -- James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] PDF versions of manual only 267 pages
We actually have new pdf's, as generated kindly by Jirka. However, we have 80MB of them, so i am waiting till we come up with a more efficient way of distributing them -- because i'd hate to add 80MB to rsync right now. -- james > > Hi all- > > The PDF version of the english manual is only 14 > chapters in length. This is seriously broke. Many > languages are small like this too: > > http://www.php.net/download-docs.php?sizes=1 > > In comparison, the older french version is 44 chapters. > Both are incomplete but currently 44 chapters is > considered okay. 14 though isn't. > > I don't think a 267 page version of a manual should > ever be posted on php.net Maybe if the new size is > under ~4mb it shouldn't be updated. IDK, part of me > thinks that any incomplete PDF version shouldn't be > listed at all... > > Regards, > Philip > > > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] About manual generation..
no. the cron job will start in 7 hours and finish sometime in the afternoon. in theory. (the crontab shows that it executes daily..) -- james > > I changed an URL in phpdoc/entities/faqurls.ent > and I was wondering how long does it take for such > changes get into the generated online manual? > > http://www.php.net/manual/en/faq.obtaining.php > shows: Last updated: Sat, 19 Oct 2002 > > Do I need to touch that xml file too to get this > one url to be correct? > > --Jani > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] ZendAPI figures
I'm in two minds about adding the figures into phpweb cvs, so the images work. Whilst this would be a workaround fix to the general problem, it does beg the question: what are the license restrictions in doing this? I don't want to just add them there and find that actually i'm breaking some law in doing so... anyone know? -- james -- James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] Why http://www.php.net/docs.php page didn't update?
> > I saw 'Last updated' time of most pages under www.php.net are on > Sep 25, how > come http://www.php.net/docs.php page was still Sep 19? Is there anything > wrong in this page? > > I ask this because it displays 'English, Brazilian Portuguese, , > Czech,' but > there should be a 'Chinese' before 'Czech' and between two commas. > looks fine to me. - james -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] Re: Full PDF Manual for 4.2.2
> James Cox wrote: > > > for now, you can upload to your home directory. I will setup a public > > directory for them once we're settled in. > > I uploaded PDF files to pdf directory in my home. So anyone with proper > rights can move them to web space. > When I work out where it makes sense to locate it, i'll get it there. -- james -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] Re: Full PDF Manual for 4.2.2
how often would you be able to do this Jirka? and how often are the chm manuals you generate done, Derick? -- james > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Sunday, September 08, 2002 9:27 PM > To: Jirka Kosek > Cc: [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] Re: Full PDF Manual for 4.2.2 > > > On Sun, 8 Sep 2002, Jirka Kosek wrote: > > > Gabor Hojtsy wrote: > > > > > If you can put this up to a stable URL and regenerate > sometime, we would > > > be happy to include a link. If you cannot handle the load on > your server, > > > [EMAIL PROTECTED] can help you setting up an SSH based account on > our rsync > > > server. > > > > The second idea sounds reasonably. I can upload PDFs on some location > > provided by php.net. However I'm not sure whether it is possible to use > > rsync for this task from Windows based machine. Or should I upload files > > to rsync server using secure copy (scp) and rsync is used only to > > synchronize this with web servers all around the world? > > Yup, use scp to get it onto the server, rsync is only for distributing. > > > > > > We would be happy to find a solution for PDF generation with XSL. > > > Then we can migrate our system to be XSL based. The main consern > > > regarding the XSL transformations is that we cannot generate PDF > > > files correctly. Hartmut made some test and found no good solution > > > based on free software... > > > > I can generate PDFs with Word and Distiller locally until we find some > > free solution which is able to work on server. > > > > BTW: If I wanna to get all translations of phpdoc, which CVS module > > should I use? Is the phpdoc-all correct one? I know that I can get > > phpdoc-en, phpdoc-de, phpdoc-cs, ... but it will be waste of disk space > > as en tree is duplicated in each module. > > phpdoc-all would be the corect one. > > Derick > > -- > - > Did I help you? http://www.derickrethans.nl/link.php?url=giftlist > Frequent ranting: http://www.derickrethans.nl/ > -- > - > PHP: Scripting the Web - [EMAIL PROTECTED] > All your branches are belong to me! > SRM: Script Running Machine - www.vl-srm.net > -- > - > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] local lists
Calling all translators: I just got done fixing [EMAIL PROTECTED] Please email me (and/or) this list with a list that might be broken. Thanks, James ___ This mail sent using V-webmail - http://www.v-webmail.co.uk -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] cvs: phpdoc /en/reference/domxml/functions DomXsltStylesheet-process.xml domxml-xslt-stylesheet-doc.xml domxml-xslt-stylesheet-file.xml domxml-xslt-stylesheet.xml
> > > would it make sense to have all xml files with lower case names? > > I notice this particularly with domxml stuff. > > Well, DomXML is special in phpdoc (similarly to ming) where > we have classes and methods, but not functions... How they > are currently documented is not the best way to go (as discussed > earlier at the documentation meeting). So the documentation should > be reorganized to use DocBook 4 OO features and not simply document > class methods as PHP functions... > sure, but initially my point was about casing of FILES in docbook cvs :) -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] cvs: phpdoc /en/reference/domxml/functions DomXsltStylesheet-process.xml domxml-xslt-stylesheet-doc.xml domxml-xslt-stylesheet-file.xml domxml-xslt-stylesheet.xml
would it make sense to have all xml files with lower case names? I notice this particularly with domxml stuff. James > -Original Message- > From: Christian Stocker [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 30, 2002 10:00 AM > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] cvs: phpdoc /en/reference/domxml/functions > DomXsltStylesheet-process.xml domxml-xslt-stylesheet-doc.xml > domxml-xslt-stylesheet-file.xml domxml-xslt-stylesheet.xml > > > chreguTue Jul 30 05:00:18 2002 EDT > > Added files: > /phpdoc/en/reference/domxml/functions > DomXsltStylesheet-process.xml > > domxml-xslt-stylesheet-doc.xml > > domxml-xslt-stylesheet-file.xml > domxml-xslt-stylesheet.xml > Log: > Beginning of XSLT Documentation within domxml > > > > Index: phpdoc/en/reference/domxml/functions/DomXsltStylesheet-process.xml > +++ phpdoc/en/reference/domxml/functions/DomXsltStylesheet-process.xml > > > > > DomXsltStylesheet->process > > Applies the XSLT-Transformation on a DomDocument Object. > > > > Description > > > objectDomXsltStylesheet->process > > objectDomDocument > >choice="opt">arrayxslt_parameters er> >choice="opt">boolparam_is_xpath > > > > &warn.experimental.func; > &warn.undocumented.func; > > > > > See also domxml_xslt_stylesheet, > domxml_xslt_stylesheet_file, > domxml_xslt_stylesheet_doc > > > > > > > Index: phpdoc/en/reference/domxml/functions/domxml-xslt-stylesheet-doc.xml > +++ phpdoc/en/reference/domxml/functions/domxml-xslt-stylesheet-doc.xml > > > > > domxml_xslt_stylesheet_doc > > Creates a DomXsltStylesheet Object from a > DomDocument Object. > > > > Description > > > objectdomxml_xslt_stylesheet_doc > objectDocDocument > Object > > &warn.experimental.func; > &warn.undocumented.func; > > > > > See also DomXsltStylesheet->process, > domxml_xslt_stylesheet, > domxml_xslt_stylesheet_file > > > > > > > Index: > phpdoc/en/reference/domxml/functions/domxml-xslt-stylesheet-file.xml > +++ phpdoc/en/reference/domxml/functions/domxml-xslt-stylesheet-file.xml > > > > > domxml_xslt_stylesheet_file > > Creates a DomXsltStylesheet Object from a xsl > document in a file. > > > > Description > > > objectdomxml_xslt_stylesheet_file > stringxsl > file > > &warn.experimental.func; > &warn.undocumented.func; > > > > > See also DomXsltStylesheet->process, > domxml_xslt_stylesheet, > domxml_xslt_stylesheet_doc > > > > > > > Index: phpdoc/en/reference/domxml/functions/domxml-xslt-stylesheet.xml > +++ phpdoc/en/reference/domxml/functions/domxml-xslt-stylesheet.xml > > > > > domxml_xslt_stylesheet > > Creates a DomXsltStylesheet Object from a xml > document in a string. > > > > Description > > objectdomxml_xslt_stylesheet > stringxsl > document > > &warn.experimental.func; > &warn.undocumented.func; > > > > > See also DomXsltStylesheet->process, > domxml_xslt_stylesheet_file, > domxml_xslt_stylesheet_doc > > > > > > > > > -- > PHP Documentation Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] File /manual/en/tutorial.whatsnext.php (I assume other langs too?)
as far as geoip stuff, expect to see it being used on the site in a day or so, just tieing in a few tweaks. as far as the linkage goes, i would prefer it as www.php.net/links.php -- that'll use geoip to find a mirror (anyway), and then it allows us to make the phpweb version of the phpmanual rsyncable seperately to the site; meaning we can distribute load better. - - James -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DOC] cvs: phpdoc / configure.in
> Modified files: > /phpdoc configure.in > Log: > We do not check actually for the PHP version, so do not say it's OK, > just print it out > yeah we do... we make sure it's better than php3... -- james -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/language types.xml
imajes Thu Jul 11 19:37:01 2002 EDT
Modified files:
/phpdoc/en/language types.xml
Log:
heredoc is one word.
Index: phpdoc/en/language/types.xml
diff -u phpdoc/en/language/types.xml:1.84 phpdoc/en/language/types.xml:1.85
--- phpdoc/en/language/types.xml:1.84 Mon Jun 10 05:15:36 2002
+++ phpdoc/en/language/types.xmlThu Jul 11 19:37:00 2002
@@ -1,5 +1,5 @@
-
+
Types
@@ -681,7 +681,7 @@
Heredoc
- Another way to delimit strings is by using here doc syntax
+ Another way to delimit strings is by using heredoc syntax
("<<<"). One should provide an identifier after
<<<, then the string, and then the
same identifier to close the quotation.
@@ -723,14 +723,14 @@
- Here doc text behaves just like a double-quoted string, without
+ Heredoc text behaves just like a double-quoted string, without
the double-quotes. This means that you do not need to escape quotes
in your here docs, but you can still use the escape codes listed
above. Variables are expanded, but the same care must be taken
when expressing complex variables inside a here doc as with
strings.
- Here doc string quoting example
+ Heredoc string quoting example
RE: [PHP-DOC] I'm back :0
> > Yes, they have split. But why can't I subscribe to phpdoc-de? > > WTF, why [EMAIL PROTECTED] intead of phpdoc-de? > > Mark > well, it was realised that given we're all on lists.php.net, it probably means that we're doing php stuff, so having php in all the names is a little redundant. All new lists are being created without the php prefix. -- james -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs commits
Hey,
Would phpdoc committers please remember that they don't need to commit each
file in cvs seperately, and it's usually only wise to do so if you wish to
log very specific different notices, or they are in vastly different parts
of the cvs repository.
eg, you could do this:
cd /your/src/dir/phpdoc-pl/reference/datetime/functions
cvs commit *
and go from that, as opposed to committing them one by one.
This cuts down on "duplicate" style cvs mail.
thanks,
-- james
--
James Cox :: [EMAIL PROTECTED] :: Landonize It! http://landonize.it/
Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/
RE: [PHP-DOC] cvs: phpdoc /en/appendices phpdevel.xml
> > I prefer keeping the "Extending PHP 3" section in > the manual because: > > a) Historical reasons. Even the php/fi manual > still lives on php.net > b) PHP 3 is not dead. Some still use it, maybe > they prefer the license? > c) Too much information isn't bad. And the devel > information may be seperated from the users > information soon anyways. > > There is an entire section on extending PHP 4, and > only one appendix for extending PHP 3. > > * http://www.php.net/manual/en/phpdevel.php > * http://www.php.net/manual/en/zend.php > > What's so bad (stupid) about that? Maybe phpdevel > should "see also" the zend docs? Or similar. > fair enough, and all valid points. splitting up the docs is a good thing, i'm for it anyhow. i think we can rename this appendix extending php 3, not phpdevel because I don't think it's overly clear. -- james
RE: [PHP-DOC] cvs: phpdoc /en/appendices phpdevel.xml
> Please put back *all* the PHP 3.0 entries you have removed from > here. This document deals only with extending PHP 3.0.x and not > a general documentation for extending PHP. This is why we retained > (and even added) 3.0 version noticies everywhere into this doc. > Extending PHP 4.x is covered in the zendapi docs. > > As we talked about this before, it may be nice to have these two > in a separate "PHP Developers Manual", and providing the current > one as "PHP Users Manual", as the vast majority of guys programming > in PHP never even thought about extending it. > well then we remove this appendix from the manual, and point to the zend info. Having references to PHP3 is ridiculous and makes us look stupid.
[PHP-DOC] cvs: phpdoc /en/appendices phpdevel.xml
imajes Fri May 31 05:55:37 2002 EDT Modified files: /phpdoc/en/appendices phpdevel.xml Log: 3.0 was years ago Index: phpdoc/en/appendices/phpdevel.xml diff -u phpdoc/en/appendices/phpdevel.xml:1.19 phpdoc/en/appendices/phpdevel.xml:1.20 --- phpdoc/en/appendices/phpdevel.xml:1.19 Tue Apr 2 22:22:17 2002 +++ phpdoc/en/appendices/phpdevel.xml Fri May 31 05:55:37 2002 @@ -1,12 +1,12 @@ - + - Extending PHP 3 + Extending PHP - Adding functions to PHP 3 + Adding functions to PHP Function Prototype @@ -192,7 +192,7 @@ fault. So please take care and free all of your wasted memory. -If you compile with "-DDEBUG", PHP 3 will print out a list of all +If you compile with "-DDEBUG", PHP will print out a list of all memory that was allocated using emalloc() and estrdup() but never freed with efree() when it is done running the specified script. @@ -219,7 +219,7 @@ -Symbol tables in PHP 3.0 are implemented as hash tables. At any +Symbol tables in PHP are implemented as hash tables. At any given time, &symbol_table is a pointer to the 'main' symbol table, and active_symbol_table points to the currently active symbol table (these may be identical like in startup, or @@ -252,7 +252,7 @@ -Arrays in PHP 3.0 are implemented using the same hashtables as +Arrays in PHP are implemented using the same hashtables as symbol tables. This means the two above functions can also be used to check variables inside arrays. @@ -478,7 +478,7 @@ Using the resource list -PHP 3.0 has a standard way of dealing with various types of +PHP has a standard way of dealing with various types of resources. This replaces all of the local linked lists in PHP 2.0. @@ -558,7 +558,7 @@ Using the persistent resource table -PHP 3.0 has a standard way of storing persistent resources (i.e., +PHP has a standard way of storing persistent resources (i.e., resources that are kept in between hits). The first module to use this feature was the MySQL module, and mSQL followed it, so one can get the general impression of how a persistent resource should @@ -653,7 +653,7 @@ Adding runtime configuration directives -Many of the features of PHP 3 can be configured at runtime. These +Many of the features of PHP can be configured at runtime. These configuration directives can appear in either the designated php3.ini file, or in the case of the Apache module version in the Apache .conf files. The advantage of having them in the Apache
RE: [PHP-DOC] Docs howto
Agreed, and this has been discussed before -- Jim, could you add it to the rsync / manual magic, and have it as master.php.net/dochowto/ ? Thanks, james > -Original Message- > From: Edin Kadribasic [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 24, 2002 1:15 PM > To: Gabor Hojtsy > Cc: PHP Documentation List > Subject: Re: [PHP-DOC] Docs howto > > > What I meant was why not put the bowto itself on a webserver directly so > people can avoid the hassle og downloading, unpacking... > > Edin > - Original Message - > From: "Gabor Hojtsy" <[EMAIL PROTECTED]> > To: "Philip Olson" <[EMAIL PROTECTED]>; "Edin Kadribasic" > <[EMAIL PROTECTED]> > Cc: "PHP Documentation List" <[EMAIL PROTECTED]> > Sent: Friday, May 24, 2002 1:52 PM > Subject: Re: [PHP-DOC] Docs howto > > > > > The link is posted here: > > > > > > http://www.php.net/download-docs.php > > > > > > And Goba is/was working on making php.net/phpdochowto > > > link to it iirc. > > > > It is http://php.net/dochowto and it works for > > some days now ;)) BTW I'll alias it as phpdochowto > > for guys trying their ideas out ;)) > > > > like: php.net/whatisphp /what_is_php / whatis ;)) > > > > > Another link may want to live here: > > > > > > http://www.php.net/manual/about.howtohelp.php > > > > I'll add the link there... > > > > Goba > > > > > > > > > >
RE: [PHP-DOC] doc.php.net ?
how about master.php.net/doc-howto/ ? James > -Original Message- > From: Mark Kronsbein [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 10, 2002 7:09 PM > To: Jan Lehnardt > Cc: Anderson Fortaleza; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] doc.php.net ? > > > > yeah, what about putting the manual howto under doc.php.net ? > > Not bad. I wont care, but the idea is okay. > > Mark > > -- > German Gabber Network @ http://www.gabber.de > Infos und Tips zu PHP http://www.php-homepage.de > > >
RE: [PHP-DOC] Fw: Installation documentation.
Title: Installation documentation. no, this was a lewd comment which i deleted -- didn't get a chance to follow up on mail. -Original Message-From: Gabor Hojtsy [mailto:[EMAIL PROTECTED]]Sent: Thursday, May 09, 2002 6:42 PMTo: [EMAIL PROTECTED]Subject: [PHP-DOC] Fw: Installation documentation. A nice note on Sambar installation ;) I cannot check it if it works. If someone can find the time and a piece of Sambar, then add this to the docu ;) Goba - Original Message - From: Brown, Niall To: '[EMAIL PROTECTED]' Sent: Wednesday, May 08, 2002 8:12 PM Subject: Installation documentation. You should perhaps check this link. I just noticed it while looking up installl info, see the last comment on the page, it was posted today.not sure how relevant it is. Niall http://www.php.net/manual/en/installation.php
RE: [PHP-DOC] split complete, here's how to fix your checkout
> I usually make changes to /it and /en, but sometimes I commit to > all other > languages. Like I did after banana-split to correct some errors in the > various reference.xml files. And when I spot problems in the build > processes of other languages. > > However, IMHO, you can split the avail files, but ask everybody > if he want > commit rights just to thier own translation + /en or not. Maybe > this is not > feasible. > > Or work out something different like having some ppl with access to the > whole manual (including those interested in checking if all the > manuals are > building correctly) and ppl who are just translating to a specified > language and thus dont need access to other languages. > I agree. would it seem inappropriate to maintain full phpdoc access for people who are interested in managing all of it (as simone suggested), as well as language + en for people who just want to translate? James
RE: [PHP-DOC] split complete, here's how to fix your checkout
> > > > simone@TOLKIEN ~/phpdoc/it > > $ cvs commit -m 'removing maxim WIP' translation.xml > > Access denied: insufficient karma (cortesi|phpdoc-it) > > Contact [EMAIL PROTECTED] for access to phpdoc-it > > cvs server: Pre-commit check failed > > cvs [server aborted]: correct above errors first! > > > > > > Whats wrong? > > i'm dumb, and forgot to adjust the avail file. this should be fixed now. > Guys, would there be uproar if we split up the cvs avail for each language? ie, i'm not going to need to be touching hebrew, japanese style languages -- given i have no idea how to type them, etc :) Also, splitting up the avail file will mean it should become easier to see who's translating what; as well as removing the potential for mistakes. Thanks, James
RE: [PHP-DOC] cvs: phpdoc /de Translators
You probably collided in CVS, and the logging software sent out one mail. or maybe it's you in 2 different identies. scary. -Original Message- From: Simone Cortesi [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 2:00 AM To: Egon Schmid Cc: [EMAIL PROTECTED] Subject: Re: [PHP-DOC] cvs: phpdoc /de Translators At 02.47 16/04/02 +0200, Egon Schmid wrote: >Good idea! With Cornelia I have spoken this evening and told her >that Catharina is back again. I have told Conni, that she should do >the same, but it seems that you knows about our speaking at >Stuttgart (MySQL meeting in the pub "Step In"). I dunno why, but if you look at my commit it seems like I did change something in the /de/Translators file, but if you look at cvs.php.net on the web the change has been made by Cornelia. -- "People forget how fast you did a job, but they remember how well you did it." -- Howard Newton, American advertising executive
RE: [PHP-DOC] cvs: phpdoc /de/functions filesystem.xml
iirc, there is a rfc on it, for a url that can't be registered, or something. i'm not too sure. james -Original Message- From: Friedhelm Betz [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 12:13 PM To: James Cox Cc: Georg Richter; [EMAIL PROTECTED] Subject: Re: [PHP-DOC] cvs: phpdoc /de/functions filesystem.xml > this should probably be in the entities file as a default example url, imho. +1 default.url="www.example.com" and also for example mail adresses? Friedhelm
RE: [PHP-DOC] cvs: phpdoc /de/functions filesystem.xml
Georg, this should probably be in the entities file as a default example url, imho. -Original Message- From: Georg Richter [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 11:55 AM To: [EMAIL PROTECTED] Subject: [PHP-DOC] cvs: phpdoc /de/functions filesystem.xml georg Tue Apr 9 06:55:18 2002 EDT Modified files: /phpdoc/de/functionsfilesystem.xml Log: changed domainnames Index: phpdoc/de/functions/filesystem.xml diff -u phpdoc/de/functions/filesystem.xml:1.36 phpdoc/de/functions/filesystem.xml:1.37 --- phpdoc/de/functions/filesystem.xml:1.36 Tue Mar 26 18:10:42 2002 +++ phpdoc/de/functions/filesystem.xml Tue Apr 9 06:55:17 2002 @@ -768,13 +768,13 @@ @@ -1390,7 +1390,7 @@
RE: [PHP-DOC] Bug #16476 Updated: unpacking
if we want to make our lives easier wrt windows users, we should support .zip not tar.gz. +1 for .zip. -Original Message- From: Gabor Hojtsy [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 07, 2002 11:46 PM To: Sander Roobol; Simone Cortesi Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; PHP Documentation List Subject: Re: [PHP-DOC] Bug #16476 Updated: unpacking > >> > Anyway, the files unpack just fine on w2k with the right tools > >> [tm] (i > >> > used cygwin, bunzip2). If it doesn't work for you your tools are > >> broken > >> > or you don't know how to use them. > >> > >> Again, as nobody on windows is familiar with bzip2, which is > >> perfectly > >> normal as nobody else uses it, dont expect users to be familiar with > >> it. > >> > >> i strongly recommend to use .tar.gz again. > > > > +1 > > And a +1 from me... -1. We need to educate the guys. Bzip2 is not that hard... Goba
[PHP-DOC] RE: Security INFO
Hey, i'm rewriting all the win32 install stuff + cgi security. James -Original Message- From: Gabor Hojtsy [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 04, 2002 9:33 PM To: Kæstutis Snieðka; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Security INFO Please see http://www.php.net/release_4_1_2_win32.php (this should be integrated into the docs, I don't know if it is done yet, or not). Goba [one [EMAIL PROTECTED]] - Original Message - From: Kæstutis Snieðka To: [EMAIL PROTECTED] Sent: Thursday, April 04, 2002 9:03 PM Subject: Security INFO Have a look at http://www.securiteam.com/windowsntfocus/5ZP030U60U.html - Vulnerability using apache & PHP & Windows... Any Idea, how to solve ? - Documentation must be corrected ASAP, I suppose... Good Luck Kæstutis Snieðka, Labourant at Computer Network Departament in Kaunas University of Technology
RE: [PHP-DOC] Server
you're welcome... -Original Message- From: Thales [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 2:33 AM To: James Cox; [EMAIL PROTECTED] Subject: Re: [PHP-DOC] Server Hey guy... You have just saved my life! It worked! I just deleted the module lines and it worked... I just didn't understand because it worked once, before I formatted my HD, and it was correct! I used this module lines. Well... Thanks a lot! You don't know how I'm happy for that! If you need a help from me (who knows nothing about configuring a server), you can count on me. See ya! Thales Medeiros. - Original Message - From: James Cox <[EMAIL PROTECTED]> To: Thales <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, April 01, 2002 10:14 PM Subject: RE: [PHP-DOC] Server Thales. I just ran a test with Xitami, IIS (the big brother to PWS) and Apache. again. all work, so i know it's not PHP's fault. :) So, looking at your *apache* errors, I see a few obvious errors: since you seem to like using PHP as CGI, you don't need to add module lines -- delete those and change : ScriptAlias /php/ "c:/arquivos de programas/php/" AddType application/x-httpd-php .php Action application/x-httpd-php "/arquivos de programas/php/php.exe" - the action line here should be /php/php.exe - NOT /arqui this should work. let me know.
RE: [PHP-DOC] Server
Thales. I just ran a test with Xitami, IIS (the big brother to PWS) and Apache. again. all work, so i know it's not PHP's fault. :) So, looking at your *apache* errors, I see a few obvious errors: since you seem to like using PHP as CGI, you don't need to add module lines -- delete those and change : ScriptAlias /php/ "c:/arquivos de programas/php/" AddType application/x-httpd-php .php Action application/x-httpd-php "/arquivos de programas/php/php.exe" - the action line here should be /php/php.exe - NOT /arqui this should work. let me know.
RE: [PHP-DOC] Server
apologies for not getting back to you. this works fine with apache. set cgi.force-redirect to 1 in php.ini and restart your computer. it should work fine after that. -Original Message- From: Thales [mailto:[EMAIL PROTECTED]] Sent: Monday, April 01, 2002 11:51 PM To: [EMAIL PROTECTED] Subject: [PHP-DOC] Server Hi everybody! It's me again. Please, somebody, help me! I need this PHP working fastly! I have a page to finish and I cannot make it run even in Apache! I tried Apache, PWS and Xitami, and in all of them it had the same error when I tried to load a page in PHP: "Security Alert! PHP CGI cannot be accessed directly. This PHP CGI binary was compiled with force-cgi-redirect enabled. This means that a page will only be served up if the REDIRECT_STATUS CGI variable is set. This variable is set, for example, by Apache's Action directive redirect. You may disable this restriction by recompiling the PHP binary with the --disable-force-cgi-redirect switch. If you do this and you have your PHP CGI binary accessible somewhere in your web tree, people will be able to circumvent .htaccess security by loading files through the PHP parser. A good way around this is to define doc_root in your php.ini file to something other than your top-level DOCUMENT_ROOT. This way you can separate the part of your web space which uses PHP from the normal part using .htaccess security. If you do not have any .htaccess restrictions anywhere on your site you can leave doc_root undefined. If you are running IIS, you may safely set cgi.force_redirect=0 in php.ini." If somebody knows how to resolve it, please tell me! Thank you all! See ya! Thales Medeiros.
RE: [PHP-DOC] Inteligent question about installing PHP
Hi Thales, I specifically said that I would be investigating this today, and would get back to you. If you are having problems setting up apache, might i suggest http://httpd.apache.org/ and check out the installation guide. As far as PWS goes, I am investigating as to why it is not behaving as reported. James -Original Message- From: Thales [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 4:33 PM To: [EMAIL PROTECTED] Subject: [PHP-DOC] Inteligent question about installing PHP Ok! Somebody said and I have to agree with you. It's not a stupid question anymore, but I need an answer. I still couldn't make it work. Does anybody help me? The problem is that I can't install PHP under any kind of server. It was functioning perfectly up to the day I had to reinstall my Windows (I know it's also a stupid thing to do - work under Windows). I tried to install PHP with the PWS, and when the server is running and I try to open a file.php, I have this error message: "Security Alert! PHP CGI cannot be accessed directly. This PHP CGI binary was compiled with force-cgi-redirect enabled. This means that a page will only be served up if the REDIRECT_STATUS CGI variable is set. This variable is set, for example, by Apache's Action directive redirect. You may disable this restriction by recompiling the PHP binary with the --disable-force-cgi-redirect switch. If you do this and you have your PHP CGI binary accessible somewhere in your web tree, people will be able to circumvent .htaccess security by loading files through the PHP parser. A good way around this is to define doc_root in your php.ini file to something other than your top-level DOCUMENT_ROOT. This way you can separate the part of your web space which uses PHP from the normal part using .htaccess security. If you do not have any .htaccess restrictions anywhere on your site you can leave doc_root undefined. If you are running IIS, you may safely set cgi.force_redirect=0 in php.ini." Well... Then I tried setting the cgi.force_redirect to 0, and the same problem was related. So I almost punched the screen and I decided to install Apache Server. Before I format my HD, I had Apache Server working perfectly. But now it wanted to say something bad to me. When I install PHP with Apache Server and do all the configurations in the httpd.conf and in php.ini, I try to Start Apache and the answer is: "Syntax error on line 1022 of c:/arquivos de programas/apache/conf/httpd.conf: Cannot load c:/arquivos de programas/php/sapi/php4apache.dll into server: (1157) Nao e possivel encontrar um dos arquivos de biblioteca necessario para executar esse aplicativo: Note the errors or messages above, and press the key to exit. 29..." The error reported is in Portuguese. It says: "It's not possible to find one of the library files that is need to run the application.". But the file is in the location said and I already sent it to various directories and it does the same message. Does anybody help me? Save me, please! Thanks all... Thales Medeiros From Brazil.
RE: [PHP-DOC] Stupid question about installing PHP
This isn't a stupid question! It should work if you set cgi.force_redirect to 0 in php.ini. You may need to restart PWS for these settings to take effect. -Original Message- From: Thales [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 7:43 AM To: [EMAIL PROTECTED] Subject: [PHP-DOC] Stupid question about installing PHP Ok! I know it's a stupid question for everybody, but I'm here just for translate the manual. Nothing more. So... I don't know nothing about compiling in "C" or something like that. I just know about other languages. The problem is that I can't install PHP under any kind of server. It was functioning perfectly up to the day I had to reinstall my Windows (I know it's also a stupid thing to do - work under Windows). I tried to install PHP with the PWS, and when the server is running and I try to open a file.php, I have this error message: "Security Alert! PHP CGI cannot be accessed directly. This PHP CGI binary was compiled with force-cgi-redirect enabled. This means that a page will only be served up if the REDIRECT_STATUS CGI variable is set. This variable is set, for example, by Apache's Action directive redirect. You may disable this restriction by recompiling the PHP binary with the --disable-force-cgi-redirect switch. If you do this and you have your PHP CGI binary accessible somewhere in your web tree, people will be able to circumvent .htaccess security by loading files through the PHP parser. A good way around this is to define doc_root in your php.ini file to something other than your top-level DOCUMENT_ROOT. This way you can separate the part of your web space which uses PHP from the normal part using .htaccess security. If you do not have any .htaccess restrictions anywhere on your site you can leave doc_root undefined. If you are running IIS, you may safely set cgi.force_redirect=0 in php.ini." Well... Then I tried setting the cgi.force_redirect to 0, and the same problem was related. So I almost punched the screen and I decided to install Apache Server. Before I format my HD, I had Apache Server working perfectly. But now it wanted to say something bad to me. When I install PHP with Apache Server and do all the configurations in the httpd.conf and in php.ini, I try to Start Apache and the answer is: "Syntax error on line 1022 of c:/arquivos de programas/apache/conf/httpd.conf: Cannot load c:/arquivos de programas/php/sapi/php4apache.dll into server: (1157) Nao e possivel encontrar um dos arquivos de biblioteca necessario para executar esse aplicativo: Note the errors or messages above, and press the key to exit. 29..." The error reported is in Portuguese. It says: "It's not possible to find one of the library files that is need to run the application.". But the file is in the location said and I already sent it to various directories and it does the same message. Does anybody help me? Save me, please! Thanks all... Thales Medeiros From Brazil.
[PHP-DOC] cvs: phpdoc /en/appendices resources.xml /en/chapters install.configure.databases.xml
imajes Thu Mar 21 18:00:00 2002 EDT Modified files: /phpdoc/en/appendices resources.xml /phpdoc/en/chapters install.configure.databases.xml Log: velocis -> birdstep # do the blank entries in appendices/resources.xml actually do anything usefull? Index: phpdoc/en/appendices/resources.xml diff -u phpdoc/en/appendices/resources.xml:1.22 phpdoc/en/appendices/resources.xml:1.23 --- phpdoc/en/appendices/resources.xml:1.22 Mon Dec 17 14:33:05 2001 +++ phpdoc/en/appendices/resources.xml Thu Mar 21 18:00:00 2002 @@ -1,5 +1,5 @@ - + List of Resource Types @@ -1585,14 +1585,14 @@ ODBC result - velocis link + birdstep link - velocis result + birdstep result Index: phpdoc/en/chapters/install.configure.databases.xml diff -u phpdoc/en/chapters/install.configure.databases.xml:1.1 phpdoc/en/chapters/install.configure.databases.xml:1.2 --- phpdoc/en/chapters/install.configure.databases.xml:1.1 Fri Jan 11 18:17:15 2002 +++ phpdoc/en/chapters/install.configure.databases.xml Thu Mar 21 18:00:00 2002 @@ -1,5 +1,5 @@ - + Database options @@ -276,14 +276,14 @@ - + - --with-velocis[=DIR] + --with-birdstep[=DIR] - Include Velocis support. DIR is the Velocis base install directory, - defaults to /usr/local/velocis. + Include Birdstep support. DIR is the Birdstep base install directory, + defaults to /usr/local/birdstep.
RE: [PHP-DOC] alternative interfaces
actually a man interface would be pretty cool. i'm +1bn for that. James > -Original Message- > From: Egon Schmid [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 28, 2002 8:13 AM > To: Enrico Weigelt; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] alternative interfaces > > > We doesn´t need alternative interfaces. > > -Egon > > - Original Message - > From: "Enrico Weigelt" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, February 28, 2002 8:46 AM > Subject: [PHP-DOC] alternative interfaces > > > > > > hi folks, > > > > i'm new to the php documentation stuff and i wanna write some > > alternative interfaces for the php documentation, i.e. for > > good old *nix man. > > > > where should i start looking at ? > > > > ~-n > > > > -- > > Enrico Weigelt== meTUX IT services > > software development, IT service, internet security solutions > > www: http://www.metux.de/phone: +49 36207 519931 > > email: [EMAIL PROTECTED]cellphone: +49 174 7066481 > > > >
RE: [PHP-DOC] .tar.gz gone?
> > Unexperienced users had trouble with zip before they learned > how to handle it. Jut let people learn more things ;) Bz2 files > are way smaller than any other compression we used in the past. > Bandwith can be a big issue for many sites and mirrors. Let > people get what they want quickly by using small files, and > not bothering the server host the same thing three times > redundantly... > Still, it'd be nice to offer them in more common formats. I'm sure we can think of something...
RE: [PHP-DOC] .tar.gz gone?
> How many pepople do you think use Windows Commander? It is heavily > used here in Hungary, but I have no international statistics. > There is also a freely downloadable plugin (from the WinCMD site) > to unzip bz2 files, enter them as directories, etc. This is not built > in to WinCMD, as tar.gz and zip support is built in... > never heard of it..
RE: [PHP-DOC] .tar.gz gone?
> > > > Perhaps, I am the only one, who has this problem. But: If not, > > there will be _many_ mails about this problem. I don't think > > that anyone wants to answer 20 "Why can't I extract .bz2 on > > Windows"-mails > > You are the first to report bz2 problems. ;) > Actually, when Jim Winstead moved to bz2 only i expressed reservations, since i knew winzip can't handle it. I use stuffit/expander now exclusively, 'cause i love the double click lazy expansion, but if it comes to having more people complain we'll just build the zips again. James
[PHP-DOC] cvs: phpdoc /en/functions strings.xml
imajes Thu Feb 21 13:21:52 2002 EDT Modified files: /phpdoc/en/functionsstrings.xml Log: typo error for print function example. Index: phpdoc/en/functions/strings.xml diff -u phpdoc/en/functions/strings.xml:1.161 phpdoc/en/functions/strings.xml:1.162 --- phpdoc/en/functions/strings.xml:1.161 Tue Feb 12 04:13:12 2002 +++ phpdoc/en/functions/strings.xml Thu Feb 21 13:21:47 2002 @@ -1,5 +1,5 @@ - + String functions Strings @@ -1670,7 +1670,7 @@ print "This spans\nmultiple lines. The newlines will be\noutput as well."; -print "escaping characters is done \"Like this\"." +print "escaping characters is done \"Like this\"."; // You can use variables inside of an print statement $foo = "foobar";
[PHP-DOC] cvs: phpdoc /entities global.ent
imajes Thu Feb 21 13:17:08 2002 EDT Modified files: /phpdoc/entitiesglobal.ent Log: new velocis url. Index: phpdoc/entities/global.ent diff -u phpdoc/entities/global.ent:1.11 phpdoc/entities/global.ent:1.12 --- phpdoc/entities/global.ent:1.11 Thu Feb 21 10:12:20 2002 +++ phpdoc/entities/global.ent Thu Feb 21 13:17:07 2002 @@ -1,6 +1,6 @@
[PHP-DOC] cvs: phpdoc / configure.in
imajes Sat Feb 16 10:11:09 2002 EDT Modified files: /phpdoc configure.in Log: minor typo. Index: phpdoc/configure.in diff -u phpdoc/configure.in:1.139 phpdoc/configure.in:1.140 --- phpdoc/configure.in:1.139 Sat Feb 16 08:37:19 2002 +++ phpdoc/configure.in Sat Feb 16 10:11:09 2002 @@ -1,4 +1,4 @@ -dnl $Id: configure.in,v 1.139 2002/02/16 13:37:19 goba Exp $ +dnl $Id: configure.in,v 1.140 2002/02/16 15:11:09 imajes Exp $ dnl autoconf initialisation AC_INIT() @@ -762,7 +762,7 @@ if test -f "$srcdir/$LANGDIR/chapters/install.xml"; then echo " Using install.xml in language dir" else - echo "" >> entities/chapters.ent + echo "" >> entities/chapters.ent echo "" >> entities/chapters.ent echo >> entities/chapters.ent echo " Using the install part from installpart.xml"
RE: [PHP-DOC] the PHP Documentation License
As far as the license clauses that Rasmus mentioned, i think these are it: > > VI. ADDITIONAL LICENSE TERMS > > A. Distribution of "substantively modified" versions of this document is > prohibited without the explicit permission of the copyright holder. > "Substantive modification" is defined as a change to the content of the > document, and excludes mere changes in format or typographical > corrections. > > B. Commercial distribution of the work or derivative of the work in any > standard (paper) book form is prohibited unless prior permission is > obtained from the copyright holder. > and based on that assumption, i think that they are acceptable, but with modification to state "without the acknowledgement of the PHP documentation team, available at [EMAIL PROTECTED]". The point being there is that it wouldn't be so prohibitive, but would allow for us to know of works that will use it. but that's just my 2 cents. :) james
RE: [PHP-DOC] the PHP Documentation License
Egon, from ZendAPI LICENSE file: OPEN PUBLICATION LICENSE I. REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED VERSIONS The Open Publication works may be reproduced and distributed in whole or in part, in any medium physical or electronic, provided that the terms of this license are adhered to, and that this license or an incorporation of it by reference (with any options elected by the author(s) and/or publisher) is displayed in the reproduction. Proper form for an incorporation by reference is as follows: Copyright (c) 2000 by Zend Technologies, Ltd. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). The reference must be immediately followed with the following terms: A. Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. "Substantive modification" is defined as a change to the content of the document, and excludes mere changes in format or typographical corrections. B. Commercial distribution of the work or derivative of the work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder. Other than as otherwise set forth herein, commercial redistribution of Open Publication-licensed material is permitted. Any publication in standard (paper) book form shall require the citation of the original publisher and author. The publisher and author's names shall appear on all outer surfaces of the book. On all outer surfaces of the book the original publisher's name shall be as large as the title of the work and cited as possessive with respect to the title. II. COPYRIGHT The copyright to each Open Publication is owned by its author(s) or designee. III. SCOPE OF LICENSE The following license terms apply to all Open Publication works, unless otherwise explicitly stated in the document. Mere aggregation of Open Publication works or a portion of an Open Publication work with other works or programs on the same media shall not cause this license to apply to those other works. The aggregate work shall contain a notice specifying the inclusion of the Open Publication material and appropriate copyright notice. SEVERABILITY. If any part of this license is found to be unenforceable in any jurisdiction, the remaining portions of the license remain in force. NO WARRANTY. Open Publication works are licensed and provided "as is" without warranty of any kind, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose or a warranty of non-infringement. IV. REQUIREMENTS ON MODIFIED WORKS All modified versions of documents covered by this license, including translations, anthologies, compilations and partial documents, must meet the following requirements: 1) The modified version must be labeled as such. 2) The person making the modifications must be identified and the modifications dated. 3) Acknowledgement of the original author and publisher if applicable must be retained according to normal academic citation practices. 4) The location of the original unmodified document must be identified. 5) The original author's (or authors') name(s) may not be used to assert or imply endorsement of the resulting document without the original author's (or authors') permission. V. GOOD-PRACTICE RECOMMENDATIONS In addition to the requirements of this license, it is requested from and strongly recommended of redistributors that: 1) If you are distributing Open Publication works on hardcopy or CD-ROM, you provide email notification to the authors of your intent to redistribute at least thirty days before your manuscript or media freeze, to give the authors time to provide updated documents. This notification should describe modifications, if any, made to the document. 2) All substantive modifications (including deletions) be either clearly marked up in the document or else described in an attachment to the document. Finally, while it is not mandatory under this license, it is considered good form to offer a free copy of any hardcopy and CD-ROM expression of an Open Publication-licensed work to its author(s). VI. ADDITIONAL LICENSE TERMS A. Distribution of "substantively modified" versions of this document is prohibited without the explicit permission of the copyright holder. "Substantive modification" is defined as a change to the content of the document, and excludes mere changes in format or typographical corrections. B. Commercial distribution of the work or derivative of the work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder.
RE: [PHP-DOC] the PHP Documentation License
For those of you in the following list, and on this list, could you comment on changing the documentation license? Stig Sæther Bakken Alexander Aulbach Egon Schmid Jim Winstead Lars Torben Wilson Rasmus Lerdorf Andrei Zmievski Jouni Ahto Thank You, james > -Original Message- > From: James Cox [mailto:[EMAIL PROTECTED]] > Sent: Saturday, February 09, 2002 2:37 PM > To: phpdoc > Subject: RE: [PHP-DOC] the PHP Documentation License > > > Guys, > > has anything happened with this? Egon, have you started to > contact those who > currently hold the license? > > Thanks, > > james > >
RE: [PHP-DOC] the PHP Documentation License
Guys, has anything happened with this? Egon, have you started to contact those who currently hold the license? Thanks, james
RE: [PHP-DOC] the PHP Documentation License
> On Wed, 2002-02-06 at 02:26, James Cox wrote: > > > > - a small number of people have "acclaim" for the documentation. And > > whatever anyone might say, it's not edited by Stig and Egon, but by many > > more people. People like Harmut should be on the front page of > the manual, > > and he's not - and that's a bad thing. > > The "Editor" title in this context is meant as a team manager or > "overseer", not like an editor in a traditional book-writing context. Yea, i understand that - but it's not all that clear. Essentially, this is a book, so being called "editor" appropriates certain things. :) The point is, though, -- i don't obviously want to "demote" or "denegrate" anything that anyone has done for the documentation project so far -- but i think that a small "covert" number of people having all control is just not useful here. I also am not entirely sure either for the way to go forward. Obviously nothing can be done unless all the "documentation group" agree... Egon, would you be willing to give a call to arms to that collective so we may be able to discuss things here? Thanks for all your co-operations too. It's nice to see that there aren't lots of people heavily opposed to change. :) james
[PHP-DOC] the PHP Documentation License
Hey Guys. Ok, the first thing i want to mention before i get into the point of this email is that i'm not in anyway trying to be difficult. What i am trying to do is start discussion again about the documentation license. And yes, i've read the archives, and no Egon, i don't want to hear from your lawyers. This stuff has been spoken about before, but given that we now have ZendAPI in the repository, (which, btw, i'm working on converting to phpdoc proper...) this is perhaps time to standardize everything. With those caveats spoken about, let me go on to the main point of this message. As it stands right now, the PHP Documentation does not go along with that of the main PHP source license. This is bad for a number of reasons: - a small number of people have "acclaim" for the documentation. And whatever anyone might say, it's not edited by Stig and Egon, but by many more people. People like Harmut should be on the front page of the manual, and he's not - and that's a bad thing. - a small number of people religiously hold control over the Documentation. This is bad, and does not help or encourage new people to take part. - If i want/see a need to make a change to the front page, i shouldn't expect to be shouted at (unless i had broken it, etc). So the point here is that - in theory - only a small number of people "own" the license to the documentation. This doesn't really go along with the whole aim of the project, at large. As far as the actual license goes, GPL is probably not where we want to be - it's something i personally shy away from due to it's restrictiveness. There are many other open source documentation licenses, and we should probably be looking at them. Finally, yes i am aware that this is also due to be discussed at the meeting in march, however i feel it's of importance (given zendapi's introduction to PHP cvs) to start discussion now - and at least have some idea of current general thoughts. -- James Cox :: [EMAIL PROTECTED] :: Landonize It! http://landonize.it/ Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/
[PHP-DOC] cvs: phpdoc / TODO
imajes Tue Feb 5 18:21:57 2002 EDT Modified files: /phpdoc TODO Log: typo + ZendAPI todo. Index: phpdoc/TODO diff -u phpdoc/TODO:1.25 phpdoc/TODO:1.26 --- phpdoc/TODO:1.25Tue Feb 5 08:44:38 2002 +++ phpdoc/TODO Tue Feb 5 18:21:57 2002 @@ -5,7 +5,7 @@ working on it, to prevent double-work. DISCUSSIONS: - - coding standars for scripts in phpdoc (see the howto + - coding standards for scripts in phpdoc (see the howto and http://www.holliwell.de/draft/draft1 for now) - licensing issues, possible licenses - users manual / developers manual division? @@ -32,6 +32,7 @@ at a single location. BUILD SYSTEM: + - merge ZendAPI into phpdoc proper (imajes) - improve php detection in configure for win (hartmut) - finish makefile cleanup (hartmut) - support both dsssl and xsl processors with configure/make (hartmut)
RE: [PHP-DOC] Re: [PHP-DEV] Tabs Vs Spaces (and other coding styles)
> > As this was crossposted to phpdoc, I consider it a question for > phpdoc too. We use one space for XML indentation and 4 spaces > for PHP codes in examples, no tabs. This is for phpdoc. And it > is documented in the phpdoc howto. Yes, i wanted to explicitly check each.
[PHP-DOC] Tabs Vs Spaces (and other coding styles)
Guys, have we ever decided on this? in our code do we go for tabs or spaces? Is there a style guide anywhere on this? thanks, james -- James Cox :: [EMAIL PROTECTED] Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/
RE: [PHP-DOC] FW: [PHP-NOTES] note 18678 added to index
> > Right. I am waiting for Hartmut who have more experience with > DocBook 4 than I. The HowTo would IMHO be a good place to publish > all steps for the the change from DocBook 3 to 4. HOWTO would be a good place to describe 3 > 4 changes, but also could use an upgrade ;) james
RE: [PHP-DOC] FW: [PHP-NOTES] note 18678 added to index
docbook4, which we're converting to, right? james > -Original Message- > From: Egon Schmid [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 31, 2002 4:50 PM > To: James Cox; phpdoc > Subject: Re: [PHP-DOC] FW: [PHP-NOTES] note 18678 added to index > > > From: "James Cox" <[EMAIL PROTECTED]> > > > I have deleted this note, but it may be worth discussing... > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, January 31, 2002 10:10 AM > > To: [EMAIL PROTECTED] > > Subject: [PHP-NOTES] note 18678 added to index > > > > > > A suggestion for the manual pages: > > It's time to categorize them into higher-level sections, e.g. > built-in > > modules, communication modules, db modules, security modules, > graphics > > modules etc. Even as an experienced user, I find it difficult to > locate the > > right section now. New users must be totally confused. Thank you. > > -- > > http://www.php.net/manual/en/index.php > > http://master.php.net/manage/user-notes.php?action=edit+18678 > > http://master.php.net/manage/user-notes.php?action=delete+18678 > > http://master.php.net/manage/user-notes.php?action=reject+18678 > > This was discussed several times. It is easier to categorize the > modules with DocBook 4. > > -Egon > >
[PHP-DOC] FW: [PHP-NOTES] note 18678 added to index
I have deleted this note, but it may be worth discussing... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 31, 2002 10:10 AM To: [EMAIL PROTECTED] Subject: [PHP-NOTES] note 18678 added to index A suggestion for the manual pages: It's time to categorize them into higher-level sections, e.g. built-in modules, communication modules, db modules, security modules, graphics modules etc. Even as an experienced user, I find it difficult to locate the right section now. New users must be totally confused. Thank you. -- http://www.php.net/manual/en/index.php http://master.php.net/manage/user-notes.php?action=edit+18678 http://master.php.net/manage/user-notes.php?action=delete+18678 http://master.php.net/manage/user-notes.php?action=reject+18678 -- PHP Notes Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DOC] document generated HTML
i'm saying that some browsers (usually old, underdeveloped) choke on strange html. However, that's probably not even an important consideration :) James
RE: [PHP-DOC] document generated HTML
yeah, but for some clients, i guess adding new lines etc may confuse them. if it works, it works. James > -Original Message- > From: Egon Schmid [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 29, 2002 9:08 PM > To: James Cox; phpdoc > Subject: Re: [PHP-DOC] document generated HTML > > > From: "James Cox" <[EMAIL PROTECTED]> > > > oh well, lets hope that no-one inspects our html :) > > There are also some working DocBook stylesheets in the background. > The transformation from XML to HTML is valid. I know the HTML code > is looking strange and ugly, but the HTML code is correct (almost > all time, if someone doesn´t correct the errors in the XML source :) > > -Egon > > > > -Original Message- > > > From: Egon Schmid [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, January 29, 2002 8:38 PM > > > To: James Cox; phpdoc > > > Subject: Re: [PHP-DOC] document generated HTML > > > > > > > > > From: "James Cox" <[EMAIL PROTECTED]> > > > > > > > has anyone else noticed that the generated HTML sucks, and is > > > there a way to > > > > fix this? > > > > > > No, if we use Jade. > > > > > > -Egon > > > > > > > > > >
RE: [PHP-DOC] document generated HTML
oh well, lets hope that no-one inspects our html :) James > -Original Message- > From: Egon Schmid [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 29, 2002 8:38 PM > To: James Cox; phpdoc > Subject: Re: [PHP-DOC] document generated HTML > > > From: "James Cox" <[EMAIL PROTECTED]> > > > has anyone else noticed that the generated HTML sucks, and is > there a way to > > fix this? > > No, if we use Jade. > > -Egon > >
[PHP-DOC] document generated HTML
Hey, has anyone else noticed that the generated HTML sucks, and is there a way to fix this? example: Chapter 1. IntroductionTable of ContentsWhat is PHP?http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/
[PHP-DOC] cvs: phpdoc /en/chapters intro.xml
imajes Tue Jan 29 09:53:00 2002 EDT Modified files: /phpdoc/en/chapters intro.xml Log: verysign => VeriSign Index: phpdoc/en/chapters/intro.xml diff -u phpdoc/en/chapters/intro.xml:1.27 phpdoc/en/chapters/intro.xml:1.28 --- phpdoc/en/chapters/intro.xml:1.27 Mon Dec 17 14:11:48 2001 +++ phpdoc/en/chapters/intro.xmlTue Jan 29 09:53:00 2002 @@ -1,5 +1,5 @@ - + Introduction @@ -204,7 +204,7 @@ While using PHP in the ecommerce field, you'll find -the Cybercash payment, CyberMUT, Verysign Payflow +the Cybercash payment, CyberMUT, VeriSign Payflow Pro and CCVS functions useful for your online payment programs. @@ -246,3 +246,11 @@ vim: et tw=78 syn=sgml vi: ts=1 sw=1 --> + + + + + + + +
[PHP-DOC] cvs: phpdoc /en/chapters install.apache.xml
imajes Wed Jan 23 20:54:12 2002 EDT Modified files: /phpdoc/en/chapters install.apache.xml Log: Rasmus recommended fixes, plus a few other tweaks Index: phpdoc/en/chapters/install.apache.xml diff -u phpdoc/en/chapters/install.apache.xml:1.2 phpdoc/en/chapters/install.apache.xml:1.3 --- phpdoc/en/chapters/install.apache.xml:1.2 Wed Jan 23 15:56:47 2002 +++ phpdoc/en/chapters/install.apache.xml Wed Jan 23 20:54:11 2002 @@ -1,5 +1,5 @@ - + Servers-Apache @@ -31,7 +31,7 @@ 5. cd apache_xxx 6. ./configure --prefix=/www 7. cd ../php-xxx -8. ./configure --with-mysql --with-apxs=/www/bin/apxs --enable-track-vars +8. ./configure --with-mysql --with-apxs=/www/bin/apxs 9. make 10. make install @@ -122,7 +122,7 @@ - This will again create a libphp4.so shared + This will create a libphp4.so shared library for Apache, but it will also create a pgsql.so shared library that is loaded into PHP either by using the extension directive in
[PHP-DOC] cvs: phpdoc /en/chapters install.apache.xml
imajes Wed Jan 23 15:56:48 2002 EDT Modified files: /phpdoc/en/chapters install.apache.xml Log: changed the recommended apache install procedure, since it didn't make much sense. please look over it, and check etc. Index: phpdoc/en/chapters/install.apache.xml diff -u phpdoc/en/chapters/install.apache.xml:1.1 phpdoc/en/chapters/install.apache.xml:1.2 --- phpdoc/en/chapters/install.apache.xml:1.1 Wed Jan 9 18:52:08 2002 +++ phpdoc/en/chapters/install.apache.xml Wed Jan 23 15:56:47 2002 @@ -1,5 +1,5 @@ - + Servers-Apache @@ -13,52 +13,49 @@ You can select arguments to add to the configure on line 8 below from the Complete list of configure - options. + options. The version numbers have been ommitted here, to + ensure the instructions are not incorrect. You will need to replace + the 'xxx' here with the correct values from your files. - Installation Instructions (Apache Module Version) + Installation Instructions (Apache Module Version) for PHP 4
RE: [PHP-DOC] How to prevent undocumented function to be documented?
don't commit your documentation till it's all done? :) actually, if i remember correctly, a warning explaining that the status is experimental, or whatever, works. James > -Original Message- > From: Yasuo Ohgaki [mailto:[EMAIL PROTECTED]] > Sent: Sunday, January 20, 2002 8:12 AM > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] How to prevent undocumented function to be > documented? > > > Hi all, > > I'm a maintainer of PostgreSQL module and I was about to > document new functions. > > I saw some of new functions are documented with no > documentation warning. I guess these are generated > automatically. > > How do I prevent it? > > I don't want half done(alpha) functions to be > documented :) > > -- > Yasuo Ohgaki > >
[PHP-DOC] cvs: phpdoc /en/chapters install.windows.xml
imajes Sat Jan 19 01:40:36 2002 EDT Modified files: /phpdoc/en/chapters install.windows.xml Log: another attempt to hack a workaround Index: phpdoc/en/chapters/install.windows.xml diff -u phpdoc/en/chapters/install.windows.xml:1.3 phpdoc/en/chapters/install.windows.xml:1.4 --- phpdoc/en/chapters/install.windows.xml:1.3 Sat Jan 19 01:35:19 2002 +++ phpdoc/en/chapters/install.windows.xml Sat Jan 19 01:40:36 2002 @@ -1,5 +1,5 @@ - + Installation on Windows systems @@ -366,7 +366,8 @@ Follow the instructions for installing the unzip utility of your choosing. - + + Execute setup.exe and follow the installation @@ -377,6 +378,8 @@ your autoexec.bat. On Windows NT, go to My Computer => Control Panel => System and select the environment tab. + + Make a temporary directory for Cygwin to use, otherwise many @@ -385,7 +388,7 @@ mkdir %SystemDrive%\tmp. - + Make a directory and unzip win32build.zip into it.
[PHP-DOC] cvs: phpdoc /en/chapters install.windows.xml
imajes Sat Jan 19 01:35:19 2002 EDT Modified files: /phpdoc/en/chapters install.windows.xml Log: ok, so you can't cheat like that. reverting fix. Index: phpdoc/en/chapters/install.windows.xml diff -u phpdoc/en/chapters/install.windows.xml:1.2 phpdoc/en/chapters/install.windows.xml:1.3 --- phpdoc/en/chapters/install.windows.xml:1.2 Sat Jan 19 01:31:02 2002 +++ phpdoc/en/chapters/install.windows.xml Sat Jan 19 01:35:19 2002 @@ -1,5 +1,5 @@ - + Installation on Windows systems @@ -377,7 +377,6 @@ your autoexec.bat. On Windows NT, go to My Computer => Control Panel => System and select the environment tab. - Make a temporary directory for Cygwin to use, otherwise many @@ -386,7 +385,9 @@ mkdir %SystemDrive%\tmp. - + + + Make a directory and unzip win32build.zip into it.
[PHP-DOC] cvs: phpdoc /en/chapters DO_NOT_TRANSLATE install.windows.xml
imajes Sat Jan 19 01:31:03 2002 EDT Modified files: /phpdoc/en/chapters DO_NOT_TRANSLATE install.windows.xml Log: typo, and fix for width problem in a warning within a list. Index: phpdoc/en/chapters/DO_NOT_TRANSLATE diff -u phpdoc/en/chapters/DO_NOT_TRANSLATE:1.1 phpdoc/en/chapters/DO_NOT_TRANSLATE:1.2 --- phpdoc/en/chapters/DO_NOT_TRANSLATE:1.1 Mon Jan 14 04:34:50 2002 +++ phpdoc/en/chapters/DO_NOT_TRANSLATE Sat Jan 19 01:31:02 2002 @@ -1,3 +1,3 @@ PLEASE DO NOT START TO TRANSLATE THE install.whatever.xml FILES -IN THIS DIRECTORY. THESE FILES MAY CHANGE NAMES, PATH AND COTENT -IN THE SHORT TERM. \ No newline at end of file +IN THIS DIRECTORY. THESE FILES MAY CHANGE NAMES, PATH AND CONTENT +IN THE SHORT TERM. Index: phpdoc/en/chapters/install.windows.xml diff -u phpdoc/en/chapters/install.windows.xml:1.1 phpdoc/en/chapters/install.windows.xml:1.2 --- phpdoc/en/chapters/install.windows.xml:1.1 Wed Jan 9 18:52:08 2002 +++ phpdoc/en/chapters/install.windows.xml Sat Jan 19 01:31:02 2002 @@ -1,5 +1,5 @@ - + Installation on Windows systems @@ -377,6 +377,7 @@ your autoexec.bat. On Windows NT, go to My Computer => Control Panel => System and select the environment tab. + Make a temporary directory for Cygwin to use, otherwise many @@ -385,7 +386,6 @@ mkdir %SystemDrive%\tmp. - Make a directory and unzip win32build.zip into it. @@ -841,4 +841,4 @@ vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 ---> \ No newline at end of file +-->
[PHP-DOC] strange wrapping (or non-wrapping) problems
Does this make you scroll horizontally for you? http://www.php.net/manual/en/function.mktime.php I am not sure how that would be fixed.. James -- James Cox :: [EMAIL PROTECTED] Please CC me when replying to my messages on lists. Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/
RE: [PHP-DOC] cvs: phpdoc /en bookinfo.xml
Ok, well i know Stig (slightly, from irc ;)) so perhaps i could prod him about that? James > -Original Message- > From: Egon Schmid [mailto:[EMAIL PROTECTED]] > Sent: Saturday, January 12, 2002 12:11 AM > To: James Cox; Mark Kronsbein; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] cvs: phpdoc /en bookinfo.xml > > > From: "James Cox" <[EMAIL PROTECTED]> > > > and, er, who class as editors now? > > This is the job for Stig Bakken. > > -Egon > >
RE: [PHP-DOC] cvs: phpdoc /en bookinfo.xml
and, er, who class as editors now? > -Original Message- > From: Egon Schmid [mailto:[EMAIL PROTECTED]] > Sent: Saturday, January 12, 2002 12:00 AM > To: Mark Kronsbein; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] cvs: phpdoc /en bookinfo.xml > > > From: "Mark Kronsbein" <[EMAIL PROTECTED]> > > > mk Fri Jan 11 18:40:00 2002 EDT > > > > Modified files: > > /phpdoc/en bookinfo.xml > > Log: > > Hartmut should be there too (IMHO) > > > > Index: phpdoc/en/bookinfo.xml > > diff -u phpdoc/en/bookinfo.xml:1.23 phpdoc/en/bookinfo.xml:1.24 > > --- phpdoc/en/bookinfo.xml:1.23 Thu Jan 3 03:04:54 2002 > > +++ phpdoc/en/bookinfo.xml Fri Jan 11 18:40:00 2002 > > @@ -1,5 +1,5 @@ > > > > - > > + > > > > > > > > @@ -34,6 +34,10 @@ > > > > > > JouniAhto > > + > > + > > + > > +HartnutHolzgraefe > > > > > > > > Please revert your patch. Only an editor can make such additions. > > -Egon > >
[PHP-DOC] cvs: phpdoc /en/functions mail.xml /entities global.ent
imajes Fri Jan 11 13:05:35 2002 EDT Modified files: /phpdoc/en/functionsmail.xml /phpdoc/entitiesglobal.ent Log: Added new rfc/pear links, from Richard Heyes Index: phpdoc/en/functions/mail.xml diff -u phpdoc/en/functions/mail.xml:1.34 phpdoc/en/functions/mail.xml:1.35 --- phpdoc/en/functions/mail.xml:1.34 Wed Dec 12 15:47:00 2001 +++ phpdoc/en/functions/mail.xmlFri Jan 11 13:05:34 2002 @@ -1,5 +1,5 @@ - + Mail functions Mail @@ -89,10 +89,19 @@ be specified by putting a comma between each address in to. Email with attachments and special types of content can be sent using this function. This is - accomplished via MIME-encoding - for more information, see - http://www.zend.com/zend/spotlight/sendmimeemailpart1.php"; - >http://www.zend.com/zend/spotlight/sendmimeemailpart1.php or - RFC 1896). + accomplished via MIME-encoding - for more information, see this + http://www.zend.com/zend/spotlight/sendmimeemailpart1.php";> + Zend article or the http://pear.php.net/get/Mail_Mime";> + PEAR Mime Classes. + + + The following RFC's may also be useful: + RFC 1896, + RFC 2045, + RFC 2046, + RFC 2047, + RFC 2048 and + RFC 2049. mail returns &true; if the mail Index: phpdoc/entities/global.ent diff -u phpdoc/entities/global.ent:1.1 phpdoc/entities/global.ent:1.2 --- phpdoc/entities/global.ent:1.1 Sun Jan 6 10:42:28 2002 +++ phpdoc/entities/global.ent Fri Jan 11 13:05:35 2002 @@ -1,6 +1,6 @@
RE: [PHP-DOC] cvs: phpdoc /en/chapters install.apache.xml install.caudium.xml install.commandline.xml install.configure.xml install.fhttpd.xml install.hpux.xml install.iis.xml install.linux.xml install.macosx.xml install.netscape-enterprise.xml install.om
Nice work on this! James > -Original Message- > From: Mark Kronsbein [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 09, 2002 11:52 PM > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] cvs: phpdoc /en/chapters install.apache.xml > install.caudium.xml install.commandline.xml install.configure.xml > install.fhttpd.xml install.hpux.xml install.iis.xml install.linux.xml > install.macosx.xml install.netscape-enterprise.xml install.omniht > > > mkWed Jan 9 18:52:09 2002 EDT > > Added files: > /phpdoc/en/chapters install.apache.xml install.caudium.xml > install.commandline.xml > install.configure.xml > install.fhttpd.xml install.hpux.xml > install.iis.xml install.linux.xml > install.macosx.xml > install.netscape-enterprise.xml > install.omnihttpd.xml install.openbsd.xml > install.oreilly.xml install.otherhttpd.xml > install.problems.xml install.solaris.xml > install.unix.xml install.windows.xml > install.xitami.xml > > Modified files: > /phpdoc/en/chapters install.xml > Log: > Split of config.xml. "make test" works fine, so lets see, if > this will help people to get more information on the installation. >
[PHP-DOC] RE: Error delivering message to: imajes@php.net!
Hey Guys, you'll have seen this error for messages today to phpdoc. I have asked jimw (and he has obliged) to remove this person from the list, so they should go away. james > -Original Message- > From: Postmaster [mailto:Postmaster] > Sent: Wednesday, January 09, 2002 12:47 AM > To: [EMAIL PROTECTED] > Subject: Error delivering message to: [EMAIL PROTECTED]! > > > Your message was not delivered for the following reason: > > E-mail Account: webmaster is over the limit of 31457280 bytes. > > Automated Postmaster > > Original E-mail > >From [EMAIL PROTECTED] Tue Jan 8 18:32:51 2002 > Return-Path: <[EMAIL PROTECTED]> > Received: from mta07-svc.ntlworld.com ([62.253.162.47]) by ; > Tue, 08 Jan 2002 18:32:51 -0600 > Received: from gandalf ([213.107.40.116]) by mta07-svc.ntlworld.com > (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP > id <20020109003249.BXPF23801.mta07-svc.ntlworld.com@gandalf>; > Wed, 9 Jan 2002 00:32:49 + > From: "James Cox" <[EMAIL PROTECTED]> > To: "Jim Winstead" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Subject: RE: FW: Error delivering message to: [EMAIL PROTECTED]! > Date: Wed, 9 Jan 2002 00:33:05 - > Message-ID: <[EMAIL PROTECTED]> > MIME-Version: 1.0 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: base64 > X-Priority: 3 (Normal) > X-MSMail-Priority: Normal > X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600. > Importance: Normal > In-Reply-To: <[EMAIL PROTECTED]> > X-Rcpt-To: <[EMAIL PROTECTED]> > > aGVoLCB5b3Ugd291bGRuJ3QgYmVsaWV2ZSB0aGUgdGhpbmdzIGkgdGVuZCB0byBtaX > NzISA6KQ0K > DQpKYW1lcw0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IE > ppbSBXaW5z > dGVhZCBbbWFpbHRvOmppbXdAYXBhY2hlLm9yZ10NCj4gU2VudDogV2VkbmVzZGF5LC > BKYW51YXJ5 > IDA5LCAyMDAyIDEyOjM1IEFNDQo+IFRvOiBKYW1lcyBDb3gNCj4gQ2M6IHdlYm1hc3 > RlckB3ZWJ0 > b2J1c2luZXNzLm5ldA0KPiBTdWJqZWN0OiBSZTogRlc6IEVycm9yIGRlbGl2ZXJpbm > cgbWVzc2Fn > ZSB0bzogaW1hamVzQHBocC5uZXQhDQo+IA0KPiANCj4gYWgsIHJpZ2h0IHlvdSBhcm > UuIGRvbid0 > IGtub3cgaG93IGkgbWlzc2VkIHRoYXQuDQo+IA0KPiB3ZWJtYXN0ZXJAd2VidG9idX > NpbmVzcy5u > ZXQgaGFzIGJlZW4gdW5zdWJzY3JpYmVkIGZyb20gcGhwZG9jIG1hbnVhbGx5Lg0KPi > ANCj4gamlt > DQo+IA0KPiBPbiBXZWQsIEphbiAwOSwgMjAwMiBhdCAxMjoyNjozOUFNIC0wMDAwLC > BKYW1lcyBD > b3ggd3JvdGU6DQo+ID4gPiA+IFgtUmNwdC1UbzogPHdlYm1hc3RlckB3ZWJ0b2J1c2 > luZXNzLm5l > dD4NCj4gPiANCj4gPiBpc24ndCB0aGF0IHRoZSBvbmU/DQo+ID4gDQo+ID4gamFtZX > MNCj4gPiAN > Cj4gPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4gPiBGcm9tOiBKaW > 0gV2luc3Rl > YWQgW21haWx0bzpqaW13QGFwYWNoZS5vcmddDQo+ID4gPiBTZW50OiBXZWRuZXNkYX > ksIEphbnVh > cnkgMDksIDIwMDIgMTI6MjggQU0NCj4gPiA+IFRvOiBKYW1lcyBDb3gNCj4gPiA+IF > N1YmplY3Q6 > IFJlOiBGVzogRXJyb3IgZGVsaXZlcmluZyBtZXNzYWdlIHRvOiBpbWFqZXNAcGhwLm > 5ldCENCj4g > PiA+IA0KPiA+ID4gDQo+ID4gPiB3aG8/IHdoYXQgeW91IGZvcndhcmRlZCBkb2Vzbi > d0IGNvbnRh > aW4gYW55IGluZm9ybWF0aW9uIGFib3V0IHRoZQ0KPiA+ID4gaWRlbnRpdHkgb2YgdG > hlIGJvdW5j > aW5nIHBlcnNvbi4NCj4gPiA+IA0KPiA+ID4gamltDQo+ID4gPiANCj4gPiA+IE9uIF > R1ZSwgSmFu > IDA4LCAyMDAyIGF0IDExOjUwOjIzUE0gLTAwMDAsIEphbWVzIENveCB3cm90ZToNCj > 4gPiA+ID4g > SmltLA0KPiA+ID4gPiANCj4gPiA+ID4gY291bGQgeW91IGxvc2UgdGhpcyBndXkgZn > JvbSB0aGUg > bWFpbGluZyBsaXN0cz8gDQo+ID4gPiA+IA0KPiA+ID4gPiBUaGFua3MsDQo+ID4gPi > A+IA0KPiA+ > ID4gPiBKYW1lcw0KPiA+ID4gPiANCj4gPiA+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYW > dlLS0tLS0N > Cj4gPiA+ID4gRnJvbTogUG9zdG1hc3RlciBbbWFpbHRvOlBvc3RtYXN0ZXJdDQo+ID > 4gPiA+IFNl > bnQ6IFR1ZXNkYXksIEphbnVhcnkgMDgsIDIwMDIgMTE6NTcgUE0NCj4gPiA+ID4gVG > 86IGltYWpl > c0BwaHAubmV0DQo+ID4gPiA+IFN1YmplY3Q6IEVycm9yIGRlbGl2ZXJpbmcgbWVzc2 > FnZSB0bzog > aW1hamVzQHBocC5uZXQhDQo+ID4gPiA+IA0KPiA+ID4gPiANCj4gPiA+ID4gWW91ci > BtZXNzYWdl > IHdhcyBub3QgZGVsaXZlcmVkIGZvciB0aGUgZm9sbG93aW5nIHJlYXNvbjoNCj4gPi > A+ID4gDQo+ > ID4gPiA+IEUtbWFpbCBBY2NvdW50OiB3ZWJtYXN0ZXIgaXMgb3ZlciB0aGUgbGltaX > Qgb2YgMzE0 > NTcyODAgYnl0ZXMuDQo+ID4gPiA+IA0KPiA+ID4gPiBBdXRvbWF0ZWQgUG9zdG1hc3 > Rlcg0KPiA+ > ID4gPiANCj4gPiA+ID4gLS0tLS0tLS1PcmlnaW5hbCBFLW1haWwtLS0tLS0tLQ0KPi > A+ID4gPiA+ > RnJvbSBpbWFqZXNAcGhwLm5ldCAgVHVlIEphbiAgOCAxNzo0MzoyNSAyMDAyDQo+ID > 4gPiA+IFJl > dHVybi1QYXRoOiA8aW1hamVzQHBocC5uZXQ+DQo+ID4gPiA+IFJlY2VpdmVkOiBmcm > 9tIHBiMS5w > YWlyLmNvbSAoWzIxNi45Mi4xMzEuNF0pIGJ5ICA7IFR1ZSwgMDggSmFuIA0KPiA+ID > 4gMjAwMiAx > Nzo0MzoyNSAtMDYwMA0KPiA+ID4gPiBSZWNlaXZlZDogKHFtYWlsIDU1NDI4IGludm > 9rZWQgYnkg > dWl
[PHP-DOC] cvs: phpdoc /en/faq html.xml
imajes Tue Jan 8 19:29:37 2002 EDT Modified files: /phpdoc/en/faq html.xml Log: htmlescape() ==> htmlspecialchars() Index: phpdoc/en/faq/html.xml diff -u phpdoc/en/faq/html.xml:1.12 phpdoc/en/faq/html.xml:1.13 --- phpdoc/en/faq/html.xml:1.12 Wed Dec 12 15:46:33 2001 +++ phpdoc/en/faq/html.xml Tue Jan 8 19:29:37 2002 @@ -1,5 +1,5 @@ - + PHP and HTML PHP and HTML @@ -27,7 +27,7 @@ HTML interpretation. In order to specify a random string, you - must include it in double quotes, and htmlescape + must include it in double quotes, and htmlspecialchars the the whole value. @@ -46,7 +46,7 @@ @@ -67,7 +67,7 @@ @@ -90,7 +90,7 @@ @@ -104,9 +104,9 @@ -You need to htmlescape the whole URL, because the +You need to htmlspecialchars the whole URL, because the URL occurs as value of an HTML-attribute. In this case, the browser -will first un-htmlescape the value, and then pass +will first un-htmlspecialchars the value, and then pass the URL on. PHP will understand the URL correcly, because you urlencoded the data. @@ -115,7 +115,7 @@ by &. Although most browsers will recover if you forget this, this isn't always possible. So even if your URL is not dynamic, you need to -htmlescape the URL. +htmlspecialchars the URL.
