Re: [PHP-DEV] Language Auto Detection / www.php.net
is there any chance that we can revert this annoying feature? The translated documentation is always behind and partly lacks important information from the english version. I want to read the documentation in english (and I am not the only one). This is only possible if I change the url after all searches to /en/ The site should at least be so intelligent to search in the /en/ part of the manual if I search from an /en/ page. This is fixed now, and works again the way it was before the weekend (if you explicitly specify a language with being on a manual page in a language, or using the search page with a language parameter, that language is carried on). We do have language specification abilities in URL shortcuts, which is the short term solution, while I (or someone else) add the language cookie support. See http://php.net/urlhowto Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Language Auto Detection / www.php.net
is there any chance that we can revert this annoying feature? The translated documentation is always behind and partly lacks important information from the english version. I want to read the documentation in english (and I am not the only one). This is only possible if I change the url after all searches to /en/ The site should at least be so intelligent to search in the /en/ part of the manual if I search from an /en/ page. This is fixed now, and works again the way it was before the weekend (if you explicitly specify a language with being on a manual page in a language, or using the search page with a language parameter, that language is carried on). We do have language specification abilities in URL shortcuts, which is the short term solution, while I (or someone else) add the language cookie support. See http://php.net/urlhowto I remember adding a cookie before for something trivial (user-configurable css) and jimw pointing out that it tends to do silly things with caching... (ie, renders it useless) Adding a cookie for langauge preference is the same as using the user's accept-language header from the technology and caching perspective. I have thought out the whole caching problem, and written down in my my.php.net proposal. You can find it in the archives (news.php.net). Basically if the setting does not modify the pages HTML code, there is no problem with it. This is the case with a language setting cookie, and the accept-language. If we would like to provide CSS selection, the way to go is to have a link rel=stylesheet href=/style.php / at the top, and print out stylesheets without caching (or cookie dependant caching) from that page. This would make pages have the same HTML code, but with different user based CSS files. Anyway, we do not have any CSS preference plans, do we? Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Language Auto Detection / www.php.net
I agree, this auto language detection is quite annoying... I concur, why not add a cookie which remembers the last chosen language? OK, I am not a php-dev member, so I have not read your mails. Can someone please summarize the problems or provide me with links to archived mails explaining what is annoying with the language detection? We have not received any bad comments at [EMAIL PROTECTED] so far, only some bug reports, which are fixed now... Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Language Auto Detection / www.php.net
is there any chance that we can revert this annoying feature? The translated documentation is always behind and partly lacks important information from the english version. I want to read the documentation in english (and I am not the only one). This is only possible if I change the url after all searches to /en/ The site should at least be so intelligent to search in the /en/ part of the manual if I search from an /en/ page. Well, this is absolutely a bug, and it was of course thought about. When I introduced this feature, it worked exactly the way Stephan would like to see it. If you explicitly specified the language (by viewing a manual page in a language or passing a lang=code parameter in the URL, it was carried on in the search form). I have enhanced the detection code however at the weekend to cope with Safari (Apple's new browser), and forgot to check that this feature still works. So I introduced a bug. I cannot correct this bug now (I don't have a CVS excutable our a valid checkout here), but you can do so, by replacing: if (!isset($explicitly_specified)) with if (empty($explicitly_specified)) [This is because I have changed the defaults] Please do so, and the bug will be fixed, and the explicitly specified langauges will absolutely override the accept language setting again. Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Language Auto Detection / www.php.net
It detects upon the user-prefered language in the browser, hence I don't have this problem as I prefer english in browser. But yes - if you prefer your native language in general, this can be annoying especially since you don't have any control over it (like with a cookie saving general prefs for .php.net). What browser denies you from setting this accept-language thing? You do have control over it, and it is far more general then having a cookie in the browser. Which is also not that flexible, as we would probably only store one language code. Someone popped up that we should keep it very simple. Well, adopting a web standard isn't simpler then inventing our own way? Please direct any mail traffic reagarding this problem to [EMAIL PROTECTED] which is intended to be the list for such discussions, and so the people responsible for the site can read the comments on it... I guess php-dev does not need more offopic mails ;) Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Language Auto Detection / www.php.net
What browser denies you from setting this accept-language thing? You do have control over it, and it is far more general then having a cookie in the browser. Which is also not that flexible, as we would probably only store one language code. Gabor, the problem is that you can't override it. If you are unlucky enough to be speaking a language for which the PHP documentation is crappy, but you still want to set your accept-language to that language for use on other sites, then you are out of luck on php.net. All right then, I'll add a cookie based setting, which can override the accept-language setting... I have no problem with a cookie, but thought that it is a good automation for language selection. :( Once I have proposed a cookie based language setting (as part of my my.php.net proposal), it was said that I should keep it simple, and use the accept-language... Now it seems this assumption was quite bad... Why the translations suck is another question. I think there is too much to learn to get in (XML, the whole translation system, make test, etc). :(( So the situation won't get better soon... Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: function.main
It was fixed in that it will link to documention for include() or require() (depending on the error) instead of main(). So, it links to different yet more appropriate pages now. Not sure if/what other errors cause a link to here but I agree we may as well create a dummy page for main() with some hopefully helpful information. I just comitted main.xml in /info/ so have a look, comments welcome. Cool. Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: function.main
That is if I understand correctly a link in an error message. So either PHP needs to hide that link in error messages, or the function.main shortcut shuold point to somewhere on the homepage, explaining what is function.main speaking of the link feature: can't we deactivate that for error_log output? error messages in the logfiles are almost unreadable right now (at least it takes a long time to identify the actual message, esp. on 'file not found' types of messages)? If you turn of html_errors, that should turn off that link too IMHO, not tested though... Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Apache 2.x / PHP 4.2.3 compatibility issue
On your apache2 compatibility page you state Apache 2.0 SAPI-support started with PHP 4.2.0. PHP 4.2.3 its known to work in conjunction with Apache 2.0.39. Don't try to use this version of PHP with any other version of Apache. We do not recommend to use PHP 4.2.3 along with Apache 2.0.39. This is totally confusing. PHP 4.2.3 its known to work with Apache 2.0.39 (besides being grammatically incorrect) does not agree with We do not recommend using PHP4.2.3 along with Apache 2.0.39. Do they work allright togethe,rbut you just personally do not recommend the combination? They won't work togerther in some cases. That information was provided by the server API developers, who probably know what are the problems, but this is a user documentation, so we have not detailed, what is the problem exactly... BTW that grammar problem should be fixed, yes... Goba [one [EMAIL PROTECTED]] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: function.main
what is function.main? it keeps popping up on my requires and links to = yoru site but nuthin' happens That is if I understand correctly a link in an error message. So either PHP needs to hide that link in error messages, or the function.main shortcut shuold point to somewhere on the homepage, explaining what is function.main This was fixed in CVS awhile ago (4.3.1) and now points to the proper docs. See: http://bugs.php.net/bug.php?id=21499 How was that fixed? Will there be any links with those errors for function.main but for a different page, or no links? I think it would be nice to make http://php.net/function.main show something (preferably the same thing that this fixed error message points to), if applicable... Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: function.main
what is function.main? it keeps popping up on my requires and links to = yoru site but nuthin' happens That is if I understand correctly a link in an error message. So either PHP needs to hide that link in error messages, or the function.main shortcut shuold point to somewhere on the homepage, explaining what is function.main Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: cvs checkout skip dir
I am actually pondering about removing distrobutions from phpweb, and moving it to it's own cvs module, with slightly more heavier control over it. This is to be a bit more secure over releases, and also it is usually not needed during a checkout of phpweb. (if you're going to checkout phpweb, you're usually just working on the site, not actually keeping a local copy, rsync is fine for that). if no-one objects i'm going to go ahead and do this next week. Please do! And please turn on cvs mails again (without diifs) for changes in distributions. It would be quite nice to see when it changes. We don't receive any notice about it right now... Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: cvs checkout skip dir
hmm. that is an interesting idea... hacking the dolog.pl script to publish the diffs for large attachements instead of including them inline might not be a bad thing (tm). Now, **no** cvs mails are sent regarding the distributions dir. It is skipped because the files are big. But diffs cannot be made for images and I guess, the mailer won't try to create diffs for bz2s exes and the like, so it may be easy to turn those mails on again... But please don't test it by adding a large bz2 file ;)) Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: cvs checkout skip dir
we could also just do a system(file $_); or whatever to work out what kind of file we're adding... and if it's a binary type file, then just don't diff. Images and compressed files are not diffed. So if I update Mirrors-htdig.tgz then nobody can see what I have changed in the instructions inside ;) Well, it is a problem for this case, this is why I would like to move the instructions to mirroring-htdig.php and mirroring-stats.php respectiely for the two services. But thats another question :) So cvswrappers defines what files are binary files (not to be diffed). I have added *.bz2, *.zip and *.tar now, so it probably won't be a problem to remove the lines from commitinfo and mail distributions commits again. | # The next two lines prevent massive cvs commit messages from being | # mailed out. It would be nice if we could instead just send the | # commit log for these ones. | .*distributions.* /bin/true Though I am not sure what effects will this have, so I don't do that :) But I would like to see commit messages for distributions on php-mirrors (without diffs ;). for large diffs, like date changes or doc changes, then publishing the diffs at a site like cvs.php.net/diffs/ or similar would also be trivial, i think. Maybe... This is offtrack now... Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: http://www.php.net/extra/
Hi! Do the files hosted at $subj have any use now, or is there any point in hosting files from as far as 1997 or 1998? bindlib_w32.zip and win32build.zip are definitely still needed. Hm, it's quite interesting to see that packages from two or four years ago still work on Windows ;) And what about the others? Anybody? Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] please add some more links to snaps.php.net
Hi! It would be nice to add links to the latest aliases to the snaps.php.net main page. It seems that the aliases containing latest instead of the package / compile time are still in effect, so please add the links to them on the snaps page. Thanks, Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
1. It's not production ready Ah yes - but that will contradict greatly, to the best version yet marketing trick the Apache Group is advertising on their front page. We can mention it to users, in the bug db etc. But officially documenting, that Apache 2 is really a beta product, doesn't really express consistency, between the family. I'm aware that this is not a technical reason not to do this, I'm just pointing out how this can be perceived. As far as I can see, we should not not put into the PHP documentation that Apache 2 is not production ready, but PHP is not production ready for Apache 2. This is of course shows us in a negative manner, but we need to make our users be aware of the fact that PHP should not be used for production in Apache 2 (as long as this is the case). Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] RE: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC]Apache 2 installation instructions
As far as I can see, we should not not put into the PHP documentation that Apache 2 is not production ready, but PHP is not production ready for Apache 2. But it's incorrect :). By saying Do not use Apache 2 and PHP in a production environment you don't blame any of the two projects. I agree with Derick's approach. There's no need to cast dispersions on either Apache2 or PHP. Simply stating _clearly_ that the combination of PHP4 and Apache2 should not be used in a production environment is sufficient. No need to play the blame-game. :) Ack. So then, please add us some info on PHP - Apache2 versions compatibility so we can add the info to the docs. Or is it only Sascha who knows this (apache2 sapi author)? Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
The aspect people complaining about is more a version thingie, e.g. they try to set up php 4.2.3 with apache 2.0.43 and this could not succeed. Is it really necessary to document that apache 2.03x works only with php 4.2.x1, php4.2.x2 and apache 2.04x only with php4.2y1 or php4.2.y2? It should be clearly mentioned, that the support for apache2 isn't production stable ;-) I think, it would be nice to add information to one place, the documentation about Apache 2 support. 1. It's not production ready 2. If someone want to set it up, how to do it (Linux, Windows) 3. What PHP versions work with what Apache 2 versions 4. It should be noted, that Apache 1 support is continued ;) Also a point to consider is the name of the correct cgi executable for win: in 4.2.3 it's php.exe the cli-build names php-cli.exe. In the 4.3.0-dev the cli names php.exe and the cgi-version php-cgi.exe. I don't know why the names changed, maybe to confuse the people once more and to give some work for the doc-folks ;-) Doh, it would be nice to stick to some final names ;) NOTE: cca. 80% of the user notes on the Apache setup page deals with Apache 2 installation. We should add verified info to the docs, and delete those notes. There are many sites offering a php4apache2.dll to download. These can harm our users, as they can contain any vulnerable code, which our users download, just because there is no official support/documentation for Apache... http://www.php.net/manual/en/install.apache.php Please keep this in mind, Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Apache 2 installation instructions
Hi! We receive many complaints at [EMAIL PROTECTED] about failures in setting up PHP with Apache 2. Can somebody please update the documentation with details on Apache 2 on Linux and Windows, or provide information for the documentation team to add to the documentation. It would definitely help users. Thanks, Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] iconv-extension
What php-dev guys think about this? Goba - Original Message - From: Friedhelm Betz [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 08, 2002 12:06 PM Subject: [PHP-DOC] iconv-extension Sources state iconv extensions as experimental. Is this (still) correct? If so, I'll add the appropriate notes in the docs. Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Error List...
IMHO if anyone gets on this job, general errors should be put somewhere to an appendix, and function specific errors should go to every function ;) Like what errors mail() can emit. This is a *huge* work as I can see. This sounds good, can this process be at least partialy automated? That'd be nice :) That's up to some php-dev people ;) I cannot donate time myself for this project right now. BTW as the php source is getting modified to print out errors with php_error_docref (or something named like this), and the errors will point to pages explaining the error, it would be nice to have pages explaining the error ;)) +1 for listing the errors in the appendix and specific function pages. Also, a side project might be a knowledge base of errors and their possible solutions. On a related note, how about more mysql_error() type functions ... like file_error()? That's absolutely up to the devteam (ccing). Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV]php_error_docref
Then there is only the last argument not spoken about yet: Externally developed extensions. and PECL extensions respectively. For external developed extensions I suggest putting them into PECL (at least the documentation, if there are license issues about the extension's code itself) and for PECL docs I suggest some kind of shortcut like: php.net/pecl.function and php.net/pear.function while we are at it. | Erm - good point we cannot find pecl.function.name automatically by | docref=NULL. Either pecl must be available by function.name or by | just using name on php.net. This is also a problem for external copies | of the manual. PECL, PEAR and other functions won't be available as function.name or even name from php.net because namespace issues. We have enough URL shortcuts now ( see http://php.net/urlhowto ). Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV]php_error_docref
| Erm - good point we cannot find pecl.function.name automatically by | docref=NULL. Either pecl must be available by function.name or by | just using name on php.net. This is also a problem for external copies | of the manual. PECL, PEAR and other functions won't be available as function.name or even name from php.net because namespace issues. We have enough URL shortcuts now ( see http://php.net/urlhowto ). I was just about explaining in detail but now i am more likely to look for a better solution - posting here if i can find any. Until i find one pecl and pear extensions will not be able to set docref=NULL. If you know that an error is issued from a PECL or a PEAR extension, than it's equally easy to have a URL for php.net/pear.func or pear.php.net/func Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] php_error_docref
php_error_docref(function.fopen TSRMLS_CC, E_WARNING, Spongebob Square Pants lives in a pineapple under the sea); To me that should be the recommended method, as it will allow the php.ini values for language to override everything nicely, and everyone can see the PHP manual in their desired language. The error of course is still in English but thats another matter. | NULL or #target is best here since it allows the phpdoc group to | change their mind for naming the pages. It's not likely that this naming scheme will change. Internal linking, php.net/funcname lookups, IDE integrations all depend on this naming scheme... Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Fwd: Re: [PHP-DEV] filesystem security questions
Can someone please help out Wez? ;) I don't really know what streams are about [it's not documented ;)], so if it's a new extension, Wez can start with copy-pasting one extensions documentation (see phpdoc/en/reference/ANY_EXTENSION_NAME). The XML files are quite self descriptive, so the tags to be used speak for themselfs. But we would also be happy with a nicely formatted text file (like the one in the overload/README), and so we can build up an XML file based on it. Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: 4.2.1 download missing Apache2 experimental folder
Forwarding this to php-dev. Those guys can answer your question... Goba [one [EMAIL PROTECTED]] - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 24, 2002 5:28 PM Subject: 4.2.1 download missing Apache2 experimental folder Referring to... PHP 4.2.1 zip package [5,217Kb] - 14 May 2002 (CGI binary plus server API versions for Apache, Apache2 (experimental), ISAPI, NSAPI, Servlet and Pi3Web. MySQL support built-in, many extensions included, packaged as zip) The Apache2 (experimental) piece apparently didn't make it into this zip file. Is that intentional? If so, I presume the current 4.2.0 release is still the most current. Is there a timeframe for a production grade API version of PHP? Thanks in advance. Hood __ This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by aw. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. _ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-EVANGELISM] RE: [PHP-DEV] The PHP Platform
It has been mentioned before -- what is there left to do to PHP? -- and I believe that we could just fix up all the bugs left, and then work on writing add-ons in pecl or pear. Really, lets stop turning this language into bloat-ware with all the latest plugins and gadgets (that make other languages hell to learn), and stick with our original principles : and easy language to learn and extend. Just a note, that we also have a web server written in PHP ;) http://nanoweb.si.kz/ Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Apache 2 news
Hi! Please post a notice to [EMAIL PROTECTED] if you are ready with the full Apache 2 compatibilty, and it will be available in some release of PHP. A new news item in this case would be nice, to announce a milestone in the php-apache front, especially regarding *security*. Thanks, Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Apache 2 news
Please post a notice to [EMAIL PROTECTED] if you are ready with the full Apache 2 compatibilty, and it will be available in some release of PHP. A new news item in this case would be nice, to announce a milestone in the php-apache front, especially regarding *security*. What kind of security issues are you refering to? We're not quite ready for full Apache 2 support, but I hope to have all known issues fixed today (in the next couple hours). You can run PHP in module, while you can specify the user name used by PHP for executing the scripts. That's new, and so you need not use CGI. This is the major advantage of using PHP CGI with Apache, instead of the module, in the current Apache versions, with setuid. Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] list of php.net sites
Hi! It would be nice to have a list of php.net sites available online at http://php.net/sites.php linked from the uppper menu on all pages. I only know a few, and never used bonsai.php.net or lxr.php.net, as I am not part of the development team. So it would be nice from some guys, who can put up a list of relevant php.net sites and two sentences about each site, to collect this info, and so I can put up that page with all the info. It would be nice to group them by. eg sites for en users (like pear.php.net) and sites for PHP developers (like lxr and bonsai). Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Fw: PHP 4.1.2 zip package [5,824Kb] - 12 March 2002
Khm... - Original Message - From: Preiß, Sebastian [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, March 15, 2002 8:58 AM Subject: PHP 4.1.2 zip package [5,824Kb] - 12 March 2002 Note: This File (PHP 4.1.2 zip package [5,824Kb] - 12 March 2002) seems to include PHP/4.1.3-dev, not PHP 4.1.2! This is shown when Apache starts (when using PHP as module)... -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 4.1.2 for windows
Hi! From hour to hour we receive questions at [EMAIL PROTECTED] about the availability of PHP 4.1.2 for Windows. First I tried to give an estimate, but now I don't know what to say. Will there ever be a PHP 4.1.2 for windows, or a 4.1.3??? Guys are waiting for the security fix... Why to kick out windows users from installing a more secure version of PHP? Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.1.2 for windows
AFAIK the problem is not afecting windows users. Because of that there is no windows binary. AFAIK it affect Windows. Forwarded letter from Zeev: - Original Message - From: Zeev Suraski [EMAIL PROTECTED] To: Rasmus Lerdorf [EMAIL PROTECTED] Cc: Jonathan Abbett [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, March 02, 2002 2:25 AM Subject: Re: 4.1.2 win binaries? ?! Why not? They will be offered soon. Zeev At 23:07 01/03/2002, Rasmus Lerdorf wrote: They aren't really required since the changes from 4.1.1 should have no effect on Windows. On Fri, 1 Mar 2002, Jonathan Abbett wrote: Will PHP.net be offering ver. 4.1.2 Windows binaries any time soon? Thanks! Jonathan Abbett [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.1.2 for windows
AFAIK Why not? === Why they are not required? But regardless of this, we should either declare on the website, that they are not required, or release that version. As Zeev pointed out again, it will be available sometime in the future. Goba As far as I see Rasmus says :They aren't really required since the changes from 4.1.1 should have no effect on Windows. And Zeev says : Why not? They will be offered soon. - why not to have 4.1.2 for windows. ?! Why not? They will be offered soon. Zeev They aren't really required since the changes from 4.1.1 should have no effect on Windows. Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: PHP 4.1.2 installer?
Could you direct me to where I can find the PHP 4.1.2 installer for windows or is it not available yet? If it would be available we would have put up a download link. Please wait for the guys to compile and pack it up. Goba [one [EMAIL PROTECTED]] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: ZE repositories
At 10:32 AM 2/5/2002, Derick Rethans wrote: Under which ugly licence is it now? =) I'm all for make sure these are compatible, so that the two repositories caan be merged. GPL, I believe? It's GPL. We also have a LICENSE file in the root of the phpdoc repository to make this clear for everybody. There were discussions about switching to another - documentation oriented - license, but we never came to a decision. So it is just a TODO item now... :(( We also had the same problems with intergrating some parts of Zak's book to the manual... So we dropped the idea of integrating the nice ready parts... Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Tabs Vs Spaces (and other coding styles)
have we ever decided on this? in our code do we go for tabs or spaces? Is there a style guide anywhere on this? Tabs, they've been used historically. 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. Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] new php.net shortcuts
Hi! As all you know, we have php.net shortcuts for manual pages, so php.net/exit go to the exit() function page, etc. As one of the php.net webmasters I realized, that we also give php.net webpage addresses so often to people like php.net/downloads.php, php.net/links.php or php.net/support.php. This is why I made this a part of the shortcut system, so access to pages withouht the PHP extensions is available now. Try: http://php.net/support or http://php.net/links for examples. This access is higher priority than functions, but AFAIK we have no pages named the same any function, so this would not be a problem. This improvement would also help php-general support people to be able to type less while giving answers to questions. One more thing came into our mind is to introduce a shortcut table for often tried shortcuts, like php.net/ini php.net/windows php.net/install While the last one seems obvious to work, actually only php.net/installation works. This would be only simple translation table for keyword to keywords, so it should work for any language manual: $CUSTOM_SHORTCUTS = array ( 'ini' = 'configuration', 'windows' = 'install.windows', 'install' = 'installation' ... ); By using this shortcut list (short shortcut to long shortcut), language preferences wont lose their effects, so hu.php.net/ini will bring up the Hungarian ini page. I am waiting for suggestions about what shortcuts would be useful, and I'll add all these to the shortcut handling code. All these changes are to make support people's life (typing requirements) easier, and to let people find pages with some common shortcuts not used in the manual, nor as manual page ids. Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] diff style bug update headers
Hi! I would like to propose a diff like bug update header style, so to use ID: 15357 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Win XP PHP Version: 4.1.0 Instead of: ID: 15357 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Old Status: Open Status: Closed Bug Type: Documentation problem Operating System: Win XP PHP Version: 4.1.0 IMHO all we can read the diff style easier, and the reporters would also understand what was changed for a first look. The web interface to bugs are getting easier to use, why not improve the mails sent out too ;) I'll make the changes if we will come to a decision. Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] new php.net shortcuts
$CUSTOM_SHORTCUTS = array ( 'ini' = 'configuration', 'windows' = 'install.windows', 'install' = 'installation' How about starting an archive of terms posted into the php.net search box. This will make for some good data which will eventually provide info to expand this feature. I think I'll also post this question to the php-general list, where most of the support people providing answers can come up with a common list of keywords. Then we can see if those keywords are already working (php.net pages | manual pages), or they should be added to this list. I would like to start with a basic list though to put up as an announcement, and prove that this simple thing works too... On a related note, www.php.net needs a nasty popup that says Choose a mirror!!! ;) This is for a long time on our TODO list. Actually a nice automatic mirror chooser, and advice box would be good, and not an annoying popup box IMHO. Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] new php.net shortcuts
On a related note, www.php.net needs a nasty popup that says Choose a mirror!!! ;) This is for a long time on our TODO list. Actually a nice automatic mirror chooser, and advice box would be good, and not an annoying popup box IMHO. This will be a nice system. Btw, was kidding about the popup, sometimes I wonder if anyone gets me :) Point is, the fear this will bog down www. even more. ALL the shortcut things work on anymirror.php.net. If all these shortcut types go working, I think we'll need a php.net/shortcuts page for description of what type shortcuts exists, and how to use them. Many people even don't know, that http://php.net/hu/echo will give the Hungarian echo page, as http://hu.php.net/echo but http://hu.php.net/en/echo gives the English one ;) This works for a very long time now, but seems to be an undocumented feature... So I think we'll need an explanatory page for this up on the site... Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] config options / php.ini settings
Hi! We just noticed a major problem in the docs, and so we would like to invent a new name for php.ini settings. Now look at http://www.php.net/manual/en/install.configure.php and http://www.php.net/manual/en/configuration.php pages I am sure that it is confusing for people, to have two completely different sections, with names consequently starting with config [configuration and configure options]. We should invent another name for php.ini directives, eg. settings or some other word, that is easily distinquisable from configure. I was also confused for some days when I first saw these two chapters (years ago ;). Yes, you can say, that we have a note on the configure options page, that these are compile time options. But there are many places, where we refer to configure options, and configuration directives (yes, we use these two phrases for the two distinct things). Consider the massive base of Windows users, who even don't know what is configure, and what to do with configure options, while they are interested in php.ini settings. IMHO it is not corrent to name php.ini settings as configuration directives, as we refer to them now... Is setting / ini setting / ini directive / directive the right name to use for php.ini directives, and configure option to use for configure options? Goba -- PHP Development 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]
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] superglobals and bc
I mean, you could check php_version() and stick in some extract() calls for older versions wherever you use the superglobals, but that seems rather ugly. Some really want it, let's define the most efficient/least ugly types of hacks :) For example with get, checking phpversion, I think it is better to check for the existense of these vars, not the version! then appropriatly defining $_GET = $HTTP_GET_VARS. And in a function, do: global $_GET. Right :) Now mimicking $_SESSION functionality is another story, eww, maybe that's going too far. This can be done by a register_shutdown_function() who registers all the vars in $_SESSION, using session_register. That's all :)) If I can understand this new feature correctly (I never used it). Regarding the extract() idea, please clarify a little more. I think Rasmus referred to the register_globals deprecation question, which is another thing IMHO, that need to be documented. There are many user notes coming up about using: extract($_REQUEST); and the like to simluate register_globals. This can be a really bad thing sometimes... Goba -- PHP Development 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]
[PHP-DEV] Re: [PHP-DOC] RE: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] superglobals and bc
?php
session_start();
if(ini_get('register_globals') AND !isset($session_global_var)){
$session_global_var = array();
}
session_register('session_global_var');
if(ini_get('register_globals')){
$SESSION = $session_global_var;
}else{
$SESSION = $HTTP_SESSION_VARS['session_global_var'];
}
?
Use the above code and you will be able to add/remove anything from the
$SESSION array and it will be reflected in the next request.
OK, but this is a way of intorducing another thing: $SESSION, instead
of making $_SESSION work like in 4.1.0 in older versions... Using
register_shutdown_function, you can make this feature transparently
working. Though you can't make the superglobal thing work, as you cannot
declare superglobals...
Goba
--
PHP Development 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]
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] superglobals and bc
I mean, you could check php_version() and stick in some extract() calls for older versions wherever you use the superglobals, but that seems rather ugly. Some really want it, let's define the most efficient/least ugly types of hacks :) For example with get, checking phpversion, I think it is better to check for the existense of these vars, not the version! But you have to be careful here. If variables get automatically populated in the global namespace you can too easily fake them (I'm not saying you do it that way, I just want to mention it so the one who writes something about this keeps that in mind). At least, I think so. The question is to check for $_GET [isset($_GET)] or phpversion() 4.1.0 [version_compare() is the function for that thing :)]. Well, you are right, that if we are 4.1.0, you can do: fake.php?_GET[a]=b_GET[c]=d so my idea may not be that good :) Goba -- PHP Development 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]
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] superglobals and bc
The question is to check for $_GET [isset($_GET)] or phpversion() 4.1.0 [version_compare() is the function for that thing :)]. Well, you are right, that if we are 4.1.0, you can do: fake.php?_GET[a]=b_GET[c]=d so my idea may not be that good :) Yep ... I'ld like to see a the-all-in-one solution does work 4.1.0 and with = 4.1.0 without too many restriction. Correction, no 'I' like to see it, but it could be of very valueable benefit for many developers out there. To correct my statements above, for version compares, version_compare() is only available in PHP 4 = 4.1.0, so for these compatibility snippets, one need to use his own version compare function. Goba -- PHP Development 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]
[PHP-DEV] PHP 4.1.1 for win
Hi! As the new year is over now, can someone be so kind to compile and release a PHP 4.1.1 for windows? Please also make the windows file names reflect the standards. Thanks, Goba -- PHP Development 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]
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] [IMPORTANT] wishes for php ...
Ah, and btw, that's what we've the documentation team for, no? Well, no php-dev people is engaged to know DocBook XML, the doc building process, or translation related things. No phpdoc people engaged to know C, some know very few C, or have no experience with C at all. I have seen a note in the php-weekly sometime ago from Rasmus, bringing the fact to attention, that all people who have write Karma to the php4 module, have write Karma to the phpdoc module. This needs to be for something :) Maybe just to give a possibility for a dream to come true :) IMHO only a few poeple have write Karma to php4 from phpdoc. I do not say, that to document any extension or function, we need write Karma. This only shows, that the majority of documentation people are not involved in development. I took part in Sterlings whole day workshop and Zak's intro to the PHP source session at the php conference. I cannot say I understand what's in the C code know, but I have a better understanding. Using that knowledge, I was able to write documentation for things like ini_file(), and some functions like this. As you know, to understand the PHP C source, knowing C is not enough. One even need to know the Zend API. For the Zend API, we have a somewhat oudated documentation, from the early days, when the PHP 4 version was not even released. So one with some C knowledge can hardly underastand the code, and try to guess what's in it, if there are no comments to guide him. I think the thing Wolfgang is dreaming of is what Andrei written for example for his Override extension. See the README in ext/override. He asked the phpdoc team for documentation and I was able to make a DocBook XML version, with some added example [asking for some guidance from Andrei] in an hour, and here it is, documented... If php-dev people would come to the phpdoc module (they can!), and write their extensions documentation in DocBook XML as ready to serve doc pieces, then there would be no need to have the phpdoc group, right. But this is not what we expect from php-dev people to do even in our very best dreams. The majority of extensions are not that easy to document as the overload one, with only one function with a clear usage. But despite this fact, small comments in code, and clear protos can help any docu pepole to write a some documentation. It would also be nice for extension authors, to at least check the docu pages for their extensions from time to time, point out weaknesses, and provide more accurate explanations, or examples where needed. I would not like to engage you to do anything. This mail was a place for my dreams. If one finds my dreams doable, things may be better in my eyes. Goba [from phpdoc and phpweb] -- PHP Development 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]
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Fw: Typos?
Anyway, this is a doc problem. Forwarded to PHP-DOC. Are you sure? Are the official ZendAPI docs suddenly in the /phpdoc cvs tree? Couldn't find them there ... IMHO they're still at zend.com and beside me no one hasn't updated them for a while. At phpdoc, we have an automation, putting () after every function tag we use, so eg functionecho/function will print out echo() and not echo. This is one handy customization of the style sheets we use. We'll on the machine, where that zend stuff was developed, this customization was not there. This is why there are literal () used after function names. As the zend XML stuff is not in phpdoc, we are not able to correct that file. IMHO modifying the style sheets is not a good point as we take advantage of this feature manual-wise. It would generally be good to have that zend thing here in phpdoc, as this way it can be corrected, updated, translated, and so on... Goba -- PHP Development 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]
[PHP-DEV] Fw: php downloads
Hi! Forwarding this request to php-dev, where people make the packages :) Goba [one [EMAIL PROTECTED]] - Original Message - From: Alexei Saveliev [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 27, 2001 10:13 PM Subject: php downloads Hello Webmaster, I appreciate all work you and PHP team are doing. Your site always was source of info and wisdom for me. I have one suggestion about downloads area - guys you are releasing source of new version of PHP as a whole bunch that is bandwidth consuming and sometimes unnecessary. I think that making version diffs could be a good idea - I use PHP since 3.0.x version and anytime then new version released I had to download whole source tree for it. For God sake please make version patches available too. -- Best regards, Alexei mailto:[EMAIL PROTECTED] -- PHP Development 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]
[PHP-DEV] Re: [PHP-DOC] Please read. session.xml
Does anyone mind if I update session.xml? I would like to prevent flood of bug reports. Thank you. Update as you see fit. Goba -- PHP Development 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]
[PHP-DEV] Re: phpweb / downloads.php
+ li?php download_link(php-4.1.0-Win32.zip, PHP 4.1.0 zip package); ? - 12 + li?php download_link(php410-installer.exe, PHP 4.1.0 installer); ? - 12 Are there any plans to make the windows binary file names standard... So eg. php-4.1.0-installer.exe sor something alike. It would be really nice :) Thanks, Goba -- PHP Development 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]
[PHP-DEV] right path on WinXP to document
Hi! As written in the PHP weekly summary on zend.com: | Sebastian Bergmann has confirmed that he can successfully | compile and install PHP on his Windows XP setup. As of | this week, XP will be added to the list of platforms that | PHP works on. As noone added it to the manual till now, I am just trying to figure it out. But as I have no XP here to see, please give me the necessary details about where is the system32 directory, where should php.ini go (c:\windows, c:\winnt, c:\winxp ???), and other operating system related info. Plese see http://www.php.net/install.windows about needed path information... Thanks, Goba -- PHP Development 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-DEV] Re: right path on WinXP to document
Nope... at least, that's not what I've heard. Windows 2000 uses c:\winnt (for php.ini) and c:\winnt\system32 (for php4ts.dll) Windows XP uses c:\windows and c:\windows\system32 Hm, this may well be, since I 'just' updated the system from Windows 2000 to WindowsXP and did no fresh install. you can use the %WINDIR% or %SystemRoot% env-variables to detect such things. OK, so as I have updated the installation instructions to refer to NT/2000/XP as the same regarding path names. So can anybody confirm, that a fresh install of Win XP uses the same dirs as Win2000 or Win98, or what? Goba -- PHP Development 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-DEV] Re: right path on WinXP to document
Nope... at least, that's not what I've heard. Windows 2000 uses c:\winnt (for php.ini) and c:\winnt\system32 (for php4ts.dll) Windows XP uses c:\windows and c:\windows\system32 Hm, this may well be, since I 'just' updated the system from Windows 2000 to WindowsXP and did no fresh install. you can use the %WINDIR% or %SystemRoot% env-variables to detect such things. OK, so as I have updated the installation instructions to refer to NT/2000/XP as the same regarding path names. So can anybody confirm, that a fresh install of Win XP uses the same dirs as Win2000 or Win98, or what? obviously it depends :) (fresh) win9x - windows winnt4/5 - winnt winxp - windows (overwritten) win9x - winxp - windows win9x - winnt5 - windows winnt5 - winxp - winnt some users may also use different directories... but IMO they should be smart enough to know where they have installed windows. just do something like Win9x: copy to %WINDIR%\system Winnt4/2000/XP: copy to %SystemRoot%\system32 OK, so I'll update the manual this week, adding a central note somewhere about system and windows dirs, and pointing there from all the other places. Goba -- PHP Development 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]
