[PHP-DOC] cvs: livedocs / livedoc.php
wez Wed May 5 04:49:43 2004 EDT
Modified files:
/livedocs livedoc.php
Log:
it's funny the things you remember once you've actually gone to bed.
http://cvs.php.net/diff.php/livedocs/livedoc.php?r1=1.101r2=1.102ty=u
Index: livedocs/livedoc.php
diff -u livedocs/livedoc.php:1.101 livedocs/livedoc.php:1.102
--- livedocs/livedoc.php:1.101 Tue May 4 21:37:05 2004
+++ livedocs/livedoc.phpWed May 5 04:49:43 2004
@@ -18,7 +18,7 @@
// | Generate an HTML version of a phpdoc/docbook page on the fly |
// +--+
//
-// $Id: livedoc.php,v 1.101 2004/05/05 01:37:05 wez Exp $
+// $Id: livedoc.php,v 1.102 2004/05/05 08:49:43 wez Exp $
define('LIVEDOC_SOURCE', dirname(__FILE__));
include LIVEDOC_SOURCE . '/common.php';
@@ -117,7 +117,9 @@
echo call_user_func($aliases[$current_page]);
} else {
echo $page-transform($map, $current_page);
- echo format_user_notes($current_page);
+ if ($NOTESDB) {
+ echo format_user_notes($current_page);
+ }
}
if (empty($file_revision)) {
[PHP-DOC] cvs: phpdoc /en/reference/com reference.xml
wez Wed May 5 05:18:22 2004 EDT Modified files: /phpdoc/en/reference/comreference.xml Log: forgot to commit this http://cvs.php.net/diff.php/phpdoc/en/reference/com/reference.xml?r1=1.6r2=1.7ty=u Index: phpdoc/en/reference/com/reference.xml diff -u phpdoc/en/reference/com/reference.xml:1.6 phpdoc/en/reference/com/reference.xml:1.7 --- phpdoc/en/reference/com/reference.xml:1.6 Mon May 3 10:55:01 2004 +++ phpdoc/en/reference/com/reference.xml Wed May 5 05:18:22 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- reference id=ref.com titleCOM and .Net (Windows)/title titleabbrevCOM/titleabbrev @@ -195,7 +195,11 @@ specification/ulink or perhaps take a look at Don Box's ulink url=url.yacl;Yet Another COM Library (YACL)/ulink. You might find some additional useful information in our FAQ for xref - linkend=faq.com/ + linkend=faq.com/. + If you're thinking of using MS Office applications on the server side, + you should read the information here: ulink + url=url.msoffice.serverside;Considerations for Server-Side Automation + of Office/ulink. /para /section /partintro
[PHP-DOC] cvs: phpdoc /en/reference/filesystem/functions link.xml linkinfo.xml readlink.xml symlink.xml /en/reference/misc/functions usleep.xml /entities global.ent
wez Wed May 5 05:30:55 2004 EDT Modified files: /phpdoc/en/reference/filesystem/functions link.xml linkinfo.xml readlink.xml symlink.xml /phpdoc/en/reference/misc/functions usleep.xml /phpdoc/entitiesglobal.ent Log: Some windows notes. http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/link.xml?r1=1.6r2=1.7ty=u Index: phpdoc/en/reference/filesystem/functions/link.xml diff -u phpdoc/en/reference/filesystem/functions/link.xml:1.6 phpdoc/en/reference/filesystem/functions/link.xml:1.7 --- phpdoc/en/reference/filesystem/functions/link.xml:1.6 Sat Aug 16 17:42:13 2003 +++ phpdoc/en/reference/filesystem/functions/link.xml Wed May 5 05:30:55 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- !-- splitted from ./en/functions/filesystem.xml, last change in rev 1.2 -- refentry id=function.link refnamediv @@ -18,6 +18,7 @@ /para note.no-remote; +note.no-windows; para See also the functionsymlink/function to create soft links, http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/linkinfo.xml?r1=1.5r2=1.6ty=u Index: phpdoc/en/reference/filesystem/functions/linkinfo.xml diff -u phpdoc/en/reference/filesystem/functions/linkinfo.xml:1.5 phpdoc/en/reference/filesystem/functions/linkinfo.xml:1.6 --- phpdoc/en/reference/filesystem/functions/linkinfo.xml:1.5 Sat Dec 20 23:21:46 2003 +++ phpdoc/en/reference/filesystem/functions/linkinfo.xml Wed May 5 05:30:55 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.5 $ -- +!-- $Revision: 1.6 $ -- !-- splitted from ./en/functions/filesystem.xml, last change in rev 1.2 -- refentry id=function.linkinfo refnamediv @@ -34,6 +34,7 @@ /programlisting /example /para +note.no-windows; para See also functionsymlink/function, functionlink/function, and functionreadlink/function. http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/readlink.xml?r1=1.5r2=1.6ty=u Index: phpdoc/en/reference/filesystem/functions/readlink.xml diff -u phpdoc/en/reference/filesystem/functions/readlink.xml:1.5 phpdoc/en/reference/filesystem/functions/readlink.xml:1.6 --- phpdoc/en/reference/filesystem/functions/readlink.xml:1.5 Tue Feb 10 05:02:58 2004 +++ phpdoc/en/reference/filesystem/functions/readlink.xml Wed May 5 05:30:55 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.5 $ -- +!-- $Revision: 1.6 $ -- !-- splitted from ./en/functions/filesystem.xml, last change in rev 1.2 -- refentry id=function.readlink refnamediv @@ -32,6 +32,7 @@ /programlisting /example /para +note.no-windows; para See also functionis_link/function, functionsymlink/function, and http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/symlink.xml?r1=1.4r2=1.5ty=u Index: phpdoc/en/reference/filesystem/functions/symlink.xml diff -u phpdoc/en/reference/filesystem/functions/symlink.xml:1.4 phpdoc/en/reference/filesystem/functions/symlink.xml:1.5 --- phpdoc/en/reference/filesystem/functions/symlink.xml:1.4Thu Jun 12 21:40:03 2003 +++ phpdoc/en/reference/filesystem/functions/symlink.xmlWed May 5 05:30:55 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.4 $ -- +!-- $Revision: 1.5 $ -- !-- splitted from ./en/functions/filesystem.xml, last change in rev 1.2 -- refentry id=function.symlink refnamediv @@ -21,6 +21,7 @@ para return.success; /para +note.no-windows; para See also functionlink/function to create hard links, and functionreadlink/function along with http://cvs.php.net/diff.php/phpdoc/en/reference/misc/functions/usleep.xml?r1=1.4r2=1.5ty=u Index: phpdoc/en/reference/misc/functions/usleep.xml diff -u phpdoc/en/reference/misc/functions/usleep.xml:1.4 phpdoc/en/reference/misc/functions/usleep.xml:1.5 --- phpdoc/en/reference/misc/functions/usleep.xml:1.4 Sat Jun 21 06:28:05 2003 +++ phpdoc/en/reference/misc/functions/usleep.xml Wed May 5 05:30:55 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.4 $ -- +!-- $Revision: 1.5 $ -- !-- splitted from ./en/functions/misc.xml, last change in rev 1.14 -- refentry id=function.usleep refnamediv @@ -19,7 +19,7 @@ /simpara note simpara - This function does not work on Windows systems. + This function did not work on Windows systems until PHP 5.0.0 /simpara /note simpara http://cvs.php.net/diff.php/phpdoc/entities/global.ent?r1=1.179r2=1.180ty=u Index: phpdoc/entities/global.ent diff -u phpdoc/entities/global.ent:1.179 phpdoc/entities/global.ent:1.180 --- phpdoc/entities/global.ent:1.179Mon May 3 10:55:01 2004 +++ phpdoc/entities/global.ent Wed May 5 05:30:55 2004 @@ -1,6 +1,6 @@
[PHP-DOC] #28255 [Asn]: DLL directory missing
ID: 28255 User updated by: pburden98 at yahoo dot com Reported By: pburden98 at yahoo dot com Status: Assigned Bug Type: Documentation problem Operating System: windows 98 2nd Edition PHP Version: 5.0.0RC2 Assigned To: nlopess New Comment: I found another on line 181 of INSTALL. Since PHP 4.0.5 MySQL, ODBC, FTP...and XML support is built-in. This is not true. I was told by a friend, MySQL is not loaded because of licensing problems Will you be patching the whole chapter Installation of Windows extensions on the INSTALL? Previous Comments: [2004-05-03 15:32:19] [EMAIL PROTECTED] I don't have karma to update the INSTALL file, but I'll make a patch for it and I'll update this in the migration appendix. [2004-05-03 13:51:21] [EMAIL PROTECTED] That's correct; we moved them to avoid the need to put anything outside of you PHP install dir, as that causes people many problems when they upgrade (they always forget to check their system dir). Making this a documentation problem. [2004-05-03 13:14:27] bart at mediawave dot nl I'm not an official bugs administrator but I might know the answer. I think they moved the files in the dlls directory into the main directory. (Where php.exe is) As far as I know, with PHP5, you don't need to copy/move any files to your windows and system32 directories anymore. Just extract the zipfile into a directory. Edit php.ini. Create the mappings in IIS. (.php C:\your-installation-dir\php.exe). Restart IIS. And it should work. Also, make sure that you remove any php files from your windows and system32 directory from previous PHP installations. [2004-05-02 20:20:47] pburden98 at yahoo dot com That is line 158 of INSTALL doc in the php-5.0.0RC2-Win32.zip [2004-05-02 20:18:49] pburden98 at yahoo dot com Description: Line 158 down explains : Please copy the bundled dlls from the 'dlls/' directory... Ok. Where is this directory? Reproduce code: --- Unpack php-5.0.0RC2-Win32.zip and will find no dll directory. Expected result: The dll directory in the archive. Actual result: -- No dll directory -- Edit this bug report at http://bugs.php.net/?id=28255edit=1
[PHP-DOC] livedocs with user notes
I updated my livedocs test-bed to use the PHP cvs and grab the user notes. From my crontab: 26 4 * * 2 /home/wez/bin/update-phpdoc 35 * * * * /home/wez/bin/update-livedocs-cvs 5 1 * * * /home/wez/src/livedocs/build.sh You can see the output at: http://livedocs.thebrainroom.net For an example of user notes: http://livedocs.thebrainroom.net/en/class.com.html
[PHP-DOC] #28283 [NEW]: path separator should be directory separator
From: todd at magnifisites dot com Operating system: All PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: path separator should be directory separator Description: On the dirname function page of the documentation, there is a sentence referring to the path separator character. Actually, this should refer to the directory separator character to more closely match the PHP constant definitions of PATH_SEPARATOR and DIRECTORY_SEPARATOR. Reproduce code: --- The current documentation: On Windows, both slash (/) and backslash (\) are used as path separator character. In other environments, it is the forward slash (/). Expected result: On Windows, both slash (/) and backslash (\) are used as directory separator character. In other environments, it is the forward slash (/). -- Edit bug report at http://bugs.php.net/?id=28283edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=28283r=trysnapshot4 Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=28283r=trysnapshot5 Fixed in CVS: http://bugs.php.net/fix.php?id=28283r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=28283r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=28283r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=28283r=needscript Try newer version: http://bugs.php.net/fix.php?id=28283r=oldversion Not developer issue:http://bugs.php.net/fix.php?id=28283r=support Expected behavior: http://bugs.php.net/fix.php?id=28283r=notwrong Not enough info:http://bugs.php.net/fix.php?id=28283r=notenoughinfo Submitted twice:http://bugs.php.net/fix.php?id=28283r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=28283r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=28283r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=28283r=dst IIS Stability: http://bugs.php.net/fix.php?id=28283r=isapi Install GNU Sed:http://bugs.php.net/fix.php?id=28283r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=28283r=float
[PHP-DOC] #28288 [NEW]: Apache 2 manual page update
From: okapi at yahoo dot com Operating system: PHP version: 4.3.6 PHP Bug Type: Documentation problem Bug description: Apache 2 manual page update Description: I would like to have adjusted the information on the PHP apache 2 manual page (http://www.php.net/manual/en/install.apache2.php) from: *Warning* Do not use Apache 2.0 and PHP in a production environment neither on Unix nor on Windows. To something more clear. This line has been the death to many to try Apache 2. The statement should be more along the lines of Some PHP modules are not fully tested for running in the default multithreaded environment of Apache 2. Core functions should be safe for this environment. To be extra careful, it is recommended to run Apache 2 in prefork mode which should avoid problems as it runs similar to Apache 1.3.x in this mode. Something along the lines of this and then for there to be a list of modules tested / check and not tested which could have problems. This single ambigous line of Do not use... is not productive. -- Edit bug report at http://bugs.php.net/?id=28288edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=28288r=trysnapshot4 Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=28288r=trysnapshot5 Fixed in CVS: http://bugs.php.net/fix.php?id=28288r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=28288r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=28288r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=28288r=needscript Try newer version: http://bugs.php.net/fix.php?id=28288r=oldversion Not developer issue:http://bugs.php.net/fix.php?id=28288r=support Expected behavior: http://bugs.php.net/fix.php?id=28288r=notwrong Not enough info:http://bugs.php.net/fix.php?id=28288r=notenoughinfo Submitted twice:http://bugs.php.net/fix.php?id=28288r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=28288r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=28288r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=28288r=dst IIS Stability: http://bugs.php.net/fix.php?id=28288r=isapi Install GNU Sed:http://bugs.php.net/fix.php?id=28288r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=28288r=float
[PHP-DOC] #28288 [Opn-Bgs]: Apache 2 manual page update
ID: 28288 Updated by: [EMAIL PROTECTED] Reported By: okapi at yahoo dot com -Status: Open +Status: Bogus Bug Type:Documentation problem PHP Version: 4.3.6 New Comment: Duplicate of #27583. Previous Comments: [2004-05-05 18:00:56] okapi at yahoo dot com Description: I would like to have adjusted the information on the PHP apache 2 manual page (http://www.php.net/manual/en/install.apache2.php) from: *Warning* Do not use Apache 2.0 and PHP in a production environment neither on Unix nor on Windows. To something more clear. This line has been the death to many to try Apache 2. The statement should be more along the lines of Some PHP modules are not fully tested for running in the default multithreaded environment of Apache 2. Core functions should be safe for this environment. To be extra careful, it is recommended to run Apache 2 in prefork mode which should avoid problems as it runs similar to Apache 1.3.x in this mode. Something along the lines of this and then for there to be a list of modules tested / check and not tested which could have problems. This single ambigous line of Do not use... is not productive. -- Edit this bug report at http://bugs.php.net/?id=28288edit=1
[PHP-DOC] #27583 [Com]: Not enough info on Apache 2 issues
ID: 27583 Comment by: okapi at yahoo dot com Reported By: stewart dot james at vu dot edu dot au Status: Open Bug Type: Documentation problem Operating System: Any PHP Version: Irrelevant New Comment: Can we have adjusted the information on the PHP apache 2 manual page http://www.php.net/manual/en/install.apache2.php) from: *Warning* Do not use Apache 2.0 and PHP in a production environment neither on Unix nor on Windows. To something more clear. This line has been the death to many to try Apache 2. The statement should be more along the lines of Some PHP modules are not fully tested for running in the default multithreaded environment of Apache 2. Core functions should be safe for this environment. To be extra careful, it is recommended to run Apache 2 in prefork mode which should avoid problems as it runs similar to Apache 1.3.x in this mode. Something along the lines of this and then for there to be a list of modules tested / check and not tested which could have problems. A comment was made: The PHP core is perfectly stable on Apache 2 -- It's just a few extensions that cause trouble... We should probably be saying that instead of just rejecting Apache 2 entirely. This single ambigous line of Do not use... is not productive. Previous Comments: [2004-04-27 15:09:46] jlx at surfeu dot de unable to get apache2.0.49 work with php4.3.6 and use php as a static library, only the dso version works :-( [2004-03-19 07:11:05] anon at example dot com It's true that we have a fully evolved 'Chicken' under Unix. However, under Windows, it's still in its pre-chicken state. A2 deals with that. It's what the APR is all about, dealing with poor POSIX conformance under windows. In my experience it does work better than A1 with PHP4, but persuading people of that is hard because of the notice the PHP developers have put up. rant Remember some people *have* to run MS Windows-- the decision out of their hands. And that is quite apart from the fact that there are (shriek! heresey!) situations where it is more appropriate than Unix./rant [2004-03-19 01:37:32] rick at alpinenetworking dot com I for one would much prefer to use php on apache 2. One of the main reasons for this is that just about every linux distro known to man won't install apache 1.3 for me anymore. I have to manually install it and manually do all of the updates or look to a 3rd party to get package files for whatever distro I happen to be installing on. It would be much nicer if I could just use the version of apache that came with the distro and use the standard update tools to do security/version updates. It seems like there is no really good reason not to except well it's no better and nobody really wants it. I'll bet that a lot more people would start running php on apache2 once it became stable. Is there anyway to make it so that php will only run on the prefork MPM so that you can at least say that php is stable under those conditions? It seems like that would satisfy the people who want to use php on apache 2 but not force you to deal with the thread safety issues for now. [2004-03-14 18:27:52] stewart dot james at vu dot edu dot au Reading the first comment your probably right the chicken itself is fine just some of the feathers need fixing (e.g. some extentions abnd their libs being the issue not core PHP) - at least thats just info from reading the first reponse to this bug report. Thanks for the tip on subversion. Will look into that this week. [2004-03-14 12:33:07] [EMAIL PROTECTED] I suppose it is a bit of a chicken and egg situation with the one exception that we have a nicely working chicken already. Also note that you do not need Apache2 for SubVersion. You can use the standalone svnserve instead. See http://lxnt.info:/book/book.html#svn-ch-5-sect-4.2 The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/27583 -- Edit this bug report at http://bugs.php.net/?id=27583edit=1
Re: [PHP-DOC] user contributed notes in livedocs
I've just comitted some code that will optionally generate a notes database at the time when you build your livedocs index. (you need to know the token to access the notes from master, so not many of you will be able to play with this feature yet). I've checked the code of user-notes.php at it seems that I need to crack the md5 hash to try this feature :) All files are using the same token, so I think you could change that token so that all livedocs devellopers could use it, without having access to the others features. At the moment the notes are presented in a read-only format, without any admin or submit note links; this is something for the phpweb template to add (you may well need to move my code around for that). The php.net them had already the notes implemented, so maybe they are displaying the notes twice. (I've not tested this, since I don't belong to the VIP group that has access to the token.) The implementation is simple and just calls the function that is used in the current on-line manual. It includes the links to delete/reject/modify the notes. BTW: did anyone cook up a pre-generate-all script yet? I don't really know what you mean where (because of my poor english :)), but I've already tested livedocs with several languages at once. I and Moshe were working in RTL support and others charset, but since we can't commit any further code, I've stopped the developpement of livedocs. The livedocs was being developed slowly and now that the CVS is restricted. I'm not really excited in developping livedocs and having to send patches all the times to the VIP members so that they can apply them. BTW2: Anyone feel like tweaking the code highlighting so that function names are turned into links to the manual pages? There is a user note in highlight_string() that has the code. It is simple to implement (but I can't do that, I have no karma...) Nuno
[PHP-DOC] cvs: phpdoc /en/reference/filesystem/functions basename.xml dirname.xml
nlopess Wed May 5 12:29:13 2004 EDT Modified files: /phpdoc/en/reference/filesystem/functions basename.xml dirname.xml Log: fix #28283: path separator-directory separator http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/basename.xml?r1=1.4r2=1.5ty=u Index: phpdoc/en/reference/filesystem/functions/basename.xml diff -u phpdoc/en/reference/filesystem/functions/basename.xml:1.4 phpdoc/en/reference/filesystem/functions/basename.xml:1.5 --- phpdoc/en/reference/filesystem/functions/basename.xml:1.4 Mon Dec 15 11:49:45 2003 +++ phpdoc/en/reference/filesystem/functions/basename.xml Wed May 5 12:29:13 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.4 $ -- +!-- $Revision: 1.5 $ -- !-- splitted from ./en/functions/filesystem.xml, last change in rev 1.2 -- refentry id=function.basename refnamediv @@ -21,7 +21,7 @@ /para para On Windows, both slash (literal//literal) and backslash - (literal\/literal) are used as path separator character. In + (literal\/literal) are used as directory separator character. In other environments, it is the forward slash (literal//literal). /para http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/dirname.xml?r1=1.7r2=1.8ty=u Index: phpdoc/en/reference/filesystem/functions/dirname.xml diff -u phpdoc/en/reference/filesystem/functions/dirname.xml:1.7 phpdoc/en/reference/filesystem/functions/dirname.xml:1.8 --- phpdoc/en/reference/filesystem/functions/dirname.xml:1.7Sat Apr 3 11:00:56 2004 +++ phpdoc/en/reference/filesystem/functions/dirname.xmlWed May 5 12:29:13 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.7 $ -- +!-- $Revision: 1.8 $ -- !-- splitted from ./en/functions/filesystem.xml, last change in rev 1.2 -- refentry id=function.dirname refnamediv @@ -18,9 +18,10 @@ /para para On Windows, both slash (literal//literal) and backslash - (literal\/literal) are used as path separator character. In + (literal\/literal) are used as directory separator character. In other environments, it is the forward slash - (literal//literal)./para + (literal//literal). +/para para example titlefunctiondirname/function example/title
[PHP-DOC] #28283 [Opn-Csd]: path separator should be directory separator
ID: 28283 Updated by: [EMAIL PROTECTED] Reported By: todd at magnifisites dot com -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: All PHP Version: Irrelevant New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: [2004-05-05 15:51:22] todd at magnifisites dot com Description: On the dirname function page of the documentation, there is a sentence referring to the path separator character. Actually, this should refer to the directory separator character to more closely match the PHP constant definitions of PATH_SEPARATOR and DIRECTORY_SEPARATOR. Reproduce code: --- The current documentation: On Windows, both slash (/) and backslash (\) are used as path separator character. In other environments, it is the forward slash (/). Expected result: On Windows, both slash (/) and backslash (\) are used as directory separator character. In other environments, it is the forward slash (/). -- Edit this bug report at http://bugs.php.net/?id=28283edit=1
[PHP-DOC] Re: livedocs access
[group@: this is the end of thread] [phpdoc@: please read and digest] This is turning into a pissing contest; I certainly don't have time for that. Derick restricted the karma because more than one person had made changes without discussing them, which then had to be reverted. This is not a dig at you personally, Moshe. Don't think I enjoy this; Ego and the trouble it causes is massive pain in the ass--it's already wasted too much of our time today; you could have been writing code instead of complaining, and I could have been doing likewise instead of trying to put you at ease. The Karma will stick until we see a couple of patches coming in and being discussed. I'm now officially around on phpdoc@ and will look at the patches. Now, quit complaining and get coding ;-) --Wez. moshe wrote: Wez wrote: On Wed, 5 May 2004, moshe doron wrote: i need access for livedocs for rtl support. right now i did the initial work and publish it on the doc group, but rtl still require tunings. limiting my access (i'm not taking this personaly even if i need ;)) will kill any future progress in this area just because i'm the only one that work on rtl and i'm too busy (just like you all) begging after livedoc team to commit my patchs. I think you're over-exaggerating; there are enough people with karma to commit any good patches that are presented. my experience show that you have to ask and ask again for someone that will do the job for you. Anyway I don't said it became impossible, just said it make the work much less attractive. And much more time consuming. Limiting access was needed because people were committing to it without discussing at all. Unless that's done adequately we're not adding any more people to livedoc's accesslist. I've seen a few none-core livedocs people making commits and then being asked to revert them recently; it does get annoying because it is totally unnecessary--it can be avoided by talking about it first. CVS is a useful tool, but only if you don't clog it up with noise from reverts and whitespace commits. Here are a couple of good reasons why you should discuss before you commit, that apply in general to OpenSource: 1: Things work in a particular way for a reason that might not be clear to you, and you might accidentally break something. 2: Things might be planned to go in a particular direction and you might not be aware of it. 3: Discussing gives others a chance to review your code and help spot any silly mistakes; QA is good. OpenSource only works if people are working (more or less) towards the same purpose. If people are not operating (roughly) within these guidelines, we will end up with a mess. So, although I feel that karma restriction might be a little over the top, I don't really mind it right now--it will force you to become good OpenSource citizens. Once we see a steady stream of good patches coming in, we will grant karma, but until then we will baby-sit the code. 0. I don't agrue about all above. and already apologize on the group. I respect all the efforts you all making for the php project and understanding livedocs restriction. My below words are intending to convince you giving me access, not to flaming you. 1. I'm holding an access to the phpdoc repository for a while and afair never run into those conflicts. 2. while I have a lot of plans and improvment ideas I keep not to start massing when I suspect if my time 'll not allow me completing the task. 3. I have a reason to believe that some of you may enjoy smoothly using livedoc on cygwin (my patch): I did this patch without knowing that I have write access to livedocs, I posted it to the group but no one response. I waited some days and email some of you but still no response .After some days I see by accident that I have livedocs access and committed the patch. I asking again from you to think again about your decision and give me livedoc access, anyway I will respect your decision.
Re: [PHP-DOC] user contributed notes in livedocs
I've checked the code of user-notes.php at it seems that I need to crack the md5 hash to try this feature :) All files are using the same token, so I think you could change that token so that all livedocs devellopers could use it, without having access to the others features. The most important one is using a different token. However, it is better to distribute the data using other means; we can set up rsync for it once we are sure that it's worth it. In the meantime, if you're working on livedocs and want the notes database, I can supply you with a copy; please send me an email if you need it. At the moment the notes are presented in a read-only format, without any admin or submit note links; this is something for the phpweb template to add (you may well need to move my code around for that). The php.net them had already the notes implemented, so maybe they are displaying the notes twice. (I've not tested this, since I don't belong to the VIP group that has access to the token.) The implementation is simple and just calls the function that is used in the current on-line manual. It includes the links to delete/reject/modify the notes. Yep, no doubt there will be a bit of tweaking needed to make it work nicely for the phpweb templates. BTW: did anyone cook up a pre-generate-all script yet? I don't really know what you mean where (because of my poor english :)), but I've already tested livedocs with several languages at once. I meant has anyone made a patch to pre-generate the whole manual as html using livedocs yet. BTW2: Anyone feel like tweaking the code highlighting so that function names are turned into links to the manual pages? There is a user note in highlight_string() that has the code. It is simple to implement (but I can't do that, I have no karma...) You can submit a patch. --Wez.
[PHP-DOC] [PATCH] rtl...
Wez Furlong [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Now, quit complaining and get coding ;-) --Wez. http://moshe.i-com-it.com/patchs/livedocs-rtl3.patch.txt this patch contains: 1. initial rtl support. 2. add some missing htmlspecialchars(). i change the htmlentities(); on pre into htmlspecialchars() coz htmlentities(); doesn't fit well for not english charsets, do i miss something? --/moshe
Re: [PHP-DOC] [PATCH] rtl...
Moshe, as I've already told you, your patch had a little bug with GLOBALS.
Attached is a correction for your patch.
Nuno
- Original Message -
Wez Furlong [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Now, quit complaining and get coding ;-)
--Wez.
http://moshe.i-com-it.com/patchs/livedocs-rtl3.patch.txt
this patch contains:
1. initial rtl support.
2. add some missing htmlspecialchars().
i change the htmlentities(); on pre into htmlspecialchars() coz
htmlentities(); doesn't fit well for not english charsets, do i miss
something?
--/mosheIndex: common.php
===
RCS file: /repository/livedocs/common.php,v
retrieving revision 1.12
diff -u -r1.12 common.php
--- common.php 5 May 2004 01:37:03 - 1.12
+++ common.php 5 May 2004 17:33:36 -
@@ -83,5 +83,15 @@
$NOTESDB = false;
}
+$rtl_langs = array('he','ar');
+define('RTL', isset($rtl_langs[$lang])?1:0);
+
+
+/* TODO: add all languages here */
+$chars = array('ar' = 'ISO-8859-6',
+ 'he' = 'windows-1255',
+ 'ja' = 'UTF-8');
+
+define('CHARSET', isset($chars[$lang]) ? $chars[$lang] : 'iso-8859-1');
?
Index: style_mapping.php
===
RCS file: /repository/livedocs/style_mapping.php,v
retrieving revision 1.11
diff -u -r1.11 style_mapping.php
--- style_mapping.php 1 May 2004 11:34:50 - 1.11
+++ style_mapping.php 5 May 2004 17:33:36 -
@@ -150,7 +150,11 @@
}
}
- return sprintf('div class=copyrightCopyright copy; %s by %s/div',
implode(, , $y), $holder);
+ if(RTL) {
+ return sprintf('div dir=ltr class=copyrightCopyright copy; %s
by span dir=rtl%s/spannbsp;/div', implode(, , $y), $holder);
+ } else {
+ return sprintf('div class=copyrightCopyright copy; %s by
%s/div', implode(, , $y), $holder);
+ }
}
function format_refpurpose($node)
@@ -199,25 +203,28 @@
function format_parameter($node)
{
- return sprintf('span class=%s$%s/span', $node-tagname, $node-content);
+ return sprintf('span class=%s$%s/span', $node-tagname,
htmlspecialchars($node-content, ENT_NOQUOTES));
}
function format_pubdate($node)
{
- return sprintf('div class=%sPublished on: %s/div', $node-tagname,
$node-content);
+ return sprintf('div class=%sPublished on: %s/div', $node-tagname,
htmlspecialchars($node-content, ENT_NOQUOTES));
}
function format_ulink($node)
{
- return sprintf('a target=_blank class=ulink href=%s%s/a',
- $node-attributes['url'],
- $node-content
- );
+ $dir = (RTL !ereg(([à-ú]+),$node-content)) ? ' dir=ltr' : ;
+ return sprintf('a target=_blank class=ulink href=%s%s%s/a',
+ $node-attributes['url'],
+ $dir,
+ htmlspecialchars($node-content, ENT_NOQUOTES)
+ );
+
}
function format_warning_title($node)
{
- return sprintf('span class=warning_title%s/span', $node-content);
+ return sprintf('span class=warning_title%s/span',
htmlspecialchars($node-content, ENT_NOQUOTES));
}
function format_link($node)
@@ -232,11 +239,14 @@
$caption = $node-attributes['linkend'];
}
$url = generate_url_for_id($lang, $node-attributes['linkend']);
- return sprintf('a class=%s href=%s%s/a',
- $node-tagname,
- $url,
- $caption
- );
+ $dir = isset($node-attributes['dir']) ? ' dir='.$node-attributes['dir'].''
: '';
+
+ return sprintf('a class=%s href=%s%s%s/a',
+ $node-tagname,
+ $url,
+ $dir,
+ $caption
+ );
}
function format_function($node)
@@ -262,12 +272,18 @@
return sprintf('span class=%s%s()/span', $class, $node-content);
}
- $url = generate_url_for_id($lang, $dest);
- return sprintf('a class=%s href=%s%s()/a',
- $class,
- $url,
- $node-content
- );
+ $dir = RTL ? ' dir=ltr' : '';
+ if ($current_page == $dest) {
+ return sprintf('span class=%s%s%s()/span', $class, $dir,
$node-content);
+ }
+
+ $url = generate_url_for_id($lang, $dest);
+ return sprintf('a class=%s href=%s%s%s()/a',
+ $class,
+ $url,
+ $dir,
+ htmlspecialchars($node-content, ENT_NOQUOTES)
+ );
}
function format_listing($node)
@@ -315,13 +331,14 @@
case 'html':
case 'xml':
case 'c':
- $content = 'pre' . htmlentities($content) . '/pre';
+ $content = 'pre' . htmlspecialchars($content) . '/pre';
break;
default:
[PHP-DOC] [Spam 05.70] RE: [PHP-DOC] [PATCH] rtl...
This mail is probably spam. The original message has been attached
along with this report, so you can recognize or block similar unwanted
mail in future. See http://spamassassin.org/tag/ for more details.
Content preview: [this message may have been sent out twice; the
previous message has a bogus email address; my apologies] Thanks; looks
good, although I'd prefer it if we didn't have too many special cases
going on. [...]
Content analysis details: (5.70 points, 5 required)
NO_REAL_NAME (0.8 points) From: does not include a real name
IN_REP_TO (-0.5 points) Has a In-Reply-To header
HTML_00_10 (1.2 points) BODY: Message is 0% to 10% HTML
HTML_MESSAGE (0.1 points) BODY: HTML included in message
FORGED_MUA_OUTLOOK (3.5 points) Forged mail pretending to be from MS Outlook
MISSING_OUTLOOK_NAME (0.6 points) Message looks like Outlook, but isn't
---BeginMessage---
[this message may have been sent out twice; the previous message has a bogus
email address; my apologies]
Thanks; looks good, although I'd prefer it if we didn't have too many
special cases going on.
You have an RTL constant to indicate that the content is RTL, but then there
are a number of places where you use that to generate a dir=rtl attribute.
It would be better to define a DIRECTION constant that held dir=rtl or
dir=ltr as appropriate for the language, and use that unconditionally.
Likewise for the copyright text in style_mapping.php; just fold it into a
single line that includes the directionality in any case:
return sprintf('pDEFANGED_div dir=ltr class=copyrightCopyright copy; %s by
DEFANGED_span %s%s/DEFANGED_span/pDEFANGED_div', implode(, , $y), DIRECTION,
$holder);
The other thing I noticed was that you have:
$map['emphasis'] = 'format_emphasis';
but then:
function format_em($node) { ... }
--Wez.
-Original Message-
From: moshe doron [mailto:[EMAIL PROTECTED]
Sent: 05 May 2004 19:14
To: [EMAIL PROTECTED]
Subject: [PHP-DOC] [PATCH] rtl...
Wez Furlong [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Now, quit complaining and get coding ;-)
--Wez.
http://moshe.i-com-it.com/patchs/livedocs-rtl3.patch.txt
this patch contains:
1. initial rtl support.
2. add some missing htmlspecialchars().
i change the htmlentities(); on pre into htmlspecialchars() coz
htmlentities(); doesn't fit well for not english charsets, do i miss
something?
--/moshe
---End Message---
Re: [PHP-DOC] [PATCH] rtl...
you correction is mistake. RTL and CHARSET are defines not vars at all. --/moshe Nuno Lopes [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Moshe, as I've already told you, your patch had a little bug with GLOBALS. Attached is a correction for your patch. Nuno - Original Message - Wez Furlong [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Now, quit complaining and get coding ;-) --Wez. http://moshe.i-com-it.com/patchs/livedocs-rtl3.patch.txt this patch contains: 1. initial rtl support. 2. add some missing htmlspecialchars(). i change the htmlentities(); on pre into htmlspecialchars() coz htmlentities(); doesn't fit well for not english charsets, do i miss something? --/moshe
Re: [PHP-DOC] [PATCH] rtl...
OMG. using global $DEFINE is right! If you don't declare it as global, it won't work if register_globals is off (as you should have it! :) Nuno - Original Message - you correction is mistake. RTL and CHARSET are defines not vars at all. --/moshe
[PHP-DOC] Re: [Spam 05.70] RE: [PHP-DOC] [PATCH] rtl...
Thanks; looks good, although I'd prefer it if we didn't have too many
special cases going on.
You have an RTL constant to indicate that the content is RTL, but then
there
are a number of places where you use that to generate a dir=rtl
attribute.
It would be better to define a DIRECTION constant that held dir=rtl or
dir=ltr as appropriate for the language, and use that unconditionally.
i'll adopt the idea.
Likewise for the copyright text in style_mapping.php; just fold it into a
single line that includes the directionality in any case:
return sprintf('pDEFANGED_div dir=ltr class=copyrightCopyright
copy; %s by
DEFANGED_span %s%s/ DEFANGED_span/pDEFANGED_div', implode(, ,
$y), DIRECTION, $holder);
this line is anyway candidate to change due to the by that have to be
translated by into entity that reflect the translation (my preference btw,
is is one dictionary file per language to keep the livedocs core
independent).
this change 'll change this lumpy line logic - lets just i keep it simple
for now.
i touched this line just because i wanted that the manual cover looks
professional.
The other thing I noticed was that you have:
$map['emphasis'] = 'format_emphasis';
but then:
function format_em($node) { ... }
i'll fix it. it was lost on last model changing.
--Wez.
Re: [PHP-DOC] user contributed notes in livedocs
BTW2: Anyone feel like tweaking the code highlighting so that
function names are turned into links to the manual pages?
There is a user note in highlight_string() that has the code. It is
simple
to implement (but I can't do that, I have no karma...)
You can submit a patch.
--Wez.
Here is my patch to style_mapping.php.
It has a bug: doesn't work with OO yet. For example:
$object-xxx() or $static::static()
Apart of that bug, which I'll solve latter (maybe tomorrow), this works
great!
Nuno
Index: style_mapping.php
===
RCS file: /repository/livedocs/style_mapping.php,v
retrieving revision 1.11
diff -u -r1.11 style_mapping.php
--- style_mapping.php 1 May 2004 11:34:50 - 1.11
+++ style_mapping.php 5 May 2004 18:27:28 -
@@ -270,6 +270,17 @@
);
}
+
+/* Callback to link highlighted function to the manual */
+function function_callback($matches) {
+ global $lang, $FORCE_DYNAMIC, $WEBBASE;
+
+ $link = strtr($matches[1], array('_' = '-'));
+ $link = WEBBASE . (FORCE_DYNAMIC ? ?l=$langq=function.$link :
$lang/function.$link.html);
+
+ return 'a class=phpfunc target=_blank title='.$matches[1].'
href='.$link.''.$matches[1].'/a(';
+}
+
function format_listing($node)
{
$content = trim($node-content);
@@ -310,6 +321,8 @@
),
highlight_string($content, 1));
}
+ $content =
preg_replace_callback('{([\w_]+)(\s*/span)(\s*span\s+class=keyword\s*\()}m',
'function_callback', $content);
+
break;
case 'shell':
case 'html':
[PHP-DOC] cvs: livedocs / style_mapping.php /themes/default livedoc.css
wez Wed May 5 14:52:03 2004 EDT
Modified files:
/livedocs style_mapping.php
/livedocs/themes/defaultlivedoc.css
Log:
Hyperlink enable function names in highlighted code.
Patch by Nuno, slightly modified.
http://cvs.php.net/diff.php/livedocs/style_mapping.php?r1=1.11r2=1.12ty=u
Index: livedocs/style_mapping.php
diff -u livedocs/style_mapping.php:1.11 livedocs/style_mapping.php:1.12
--- livedocs/style_mapping.php:1.11 Sat May 1 07:34:50 2004
+++ livedocs/style_mapping.php Wed May 5 14:52:03 2004
@@ -18,7 +18,7 @@
// | Helper functions for formatting elements |
// +--+
//
-// $Id: style_mapping.php,v 1.11 2004/05/01 11:34:50 derick Exp $
+// $Id: style_mapping.php,v 1.12 2004/05/05 18:52:03 wez Exp $
// almost XPATH.. ;-)
$map = array(
@@ -270,6 +270,15 @@
);
}
+function format_listing_hyperlink_function($matches)
+{
+ global $lang;
+
+ $link = strtr($matches[1], array('_' = '-'));
+ $link = WEBBASE . (FORCE_DYNAMIC ? ?l=$langq=function.$link :
$lang/function.$link.html);
+ return 'a class=phpfunc href=' . $link . '' . $matches[1] . '/a(';
+}
+
function format_listing($node)
{
$content = trim($node-content);
@@ -310,6 +319,7 @@
),
highlight_string($content, 1));
}
+ $content =
preg_replace_callback('{([\w_]+)(\s*/span)(\s*span\s+class=keyword\s*\()}m',
'format_listing_hyperlink_function', $content);
break;
case 'shell':
case 'html':
http://cvs.php.net/diff.php/livedocs/themes/default/livedoc.css?r1=1.4r2=1.5ty=u
Index: livedocs/themes/default/livedoc.css
diff -u livedocs/themes/default/livedoc.css:1.4 livedocs/themes/default/livedoc.css:1.5
--- livedocs/themes/default/livedoc.css:1.4 Tue May 4 21:37:13 2004
+++ livedocs/themes/default/livedoc.css Wed May 5 14:52:03 2004
@@ -1,4 +1,4 @@
-/* $Id: livedoc.css,v 1.4 2004/05/05 01:37:13 wez Exp $ */
+/* $Id: livedoc.css,v 1.5 2004/05/05 18:52:03 wez Exp $ */
body {
font-family: verdana;
font-size: 11pt;
@@ -157,6 +157,14 @@
font-size: 10pt;
}
+div.phpcode a.phpfunc {
+ text-decoration: none;
+}
+
+div.phpcode a.phpfunc:hover {
+ text-decoration: underline;
+}
+
div.shellcode, div.xmlcode, div.inicode,
div.htmlcode, div.screen, div.apache-confcode,
div.code, div.synopsis {
[PHP-DOC] Re: [Spam 05.70] RE: [PHP-DOC] [PATCH] rtl...
Moshe Doron [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Thanks; looks good, although I'd prefer it if we didn't have too many special cases going on. You have an RTL constant to indicate that the content is RTL, but then there are a number of places where you use that to generate a dir=rtl attribute. It would be better to define a DIRECTION constant that held dir=rtl or dir=ltr as appropriate for the language, and use that unconditionally. i'll adopt the idea. i didn't read you carfuly enough. on rtl mode we need times to dump dir=rtl and times dir=ltr on non-rtl languages we have no worries about this issue. my guideline is to leave the ltr document as it was before my plays. you never know how any browser behave after dir=ltr even if the it sensible that this instruction should have no effect. anyway i follow your line of thought and make the RTL hold the text. here the new patch: http://moshe.i-com-it.com/patchs/livedocs-rtl4.patch.txt --/moshe.
RE: [PHP-DOC] user contributed notes in livedocs
Thanks :) I made a slight adjustment; when working with constants, you don't need to declare them global. I mention this because in your modified version of Moshe's patch you were doing something similar. --Wez. -Original Message- From: Nuno Lopes [mailto:[EMAIL PROTECTED] Sent: 05 May 2004 19:33 To: Wez Furlong; [EMAIL PROTECTED] Subject: Re: [PHP-DOC] user contributed notes in livedocs BTW2: Anyone feel like tweaking the code highlighting so that function names are turned into links to the manual pages? There is a user note in highlight_string() that has the code. It is simple to implement (but I can't do that, I have no karma...) You can submit a patch. --Wez. Here is my patch to style_mapping.php. It has a bug: doesn't work with OO yet. For example: $object-xxx() or $static::static() Apart of that bug, which I'll solve latter (maybe tomorrow), this works great! Nuno
[PHP-DOC] cvs: phpdoc /en/language basic-syntax.xml
didou Wed May 5 14:58:33 2004 EDT Modified files: /phpdoc/en/language basic-syntax.xml Log: Document the third way (script language=php/script) http://cvs.php.net/diff.php/phpdoc/en/language/basic-syntax.xml?r1=1.36r2=1.37ty=u Index: phpdoc/en/language/basic-syntax.xml diff -u phpdoc/en/language/basic-syntax.xml:1.36 phpdoc/en/language/basic-syntax.xml:1.37 --- phpdoc/en/language/basic-syntax.xml:1.36Wed Dec 10 08:31:35 2003 +++ phpdoc/en/language/basic-syntax.xml Wed May 5 14:58:33 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.36 $ -- +!-- $Revision: 1.37 $ -- chapter id=language.basic-syntax titleBasic syntax/title @@ -113,7 +113,12 @@ commandconfigure/command. Even if it is enabled by default in php.ini-dist, use of short tags are discouraged. /para - + + para +The third way is always available and safe like the first one. However, +the first is the preferred and most used one. + /para + para The fourth way is only available if ASP-style tags have been enabled using the link linkend=ini.asp-tagsasp_tags/link
[PHP-DOC] cvs: phpdoc /en/language basic-syntax.xml control-structures.xml expressions.xml functions.xml oop.xml operators.xml types.xml
damsWed May 5 16:19:51 2004 EDT Modified files: /phpdoc/en/language basic-syntax.xml control-structures.xml expressions.xml functions.xml oop.xml operators.xml types.xml Log: moved repleable to varname, added some extra tags http://cvs.php.net/diff.php/phpdoc/en/language/basic-syntax.xml?r1=1.37r2=1.38ty=u Index: phpdoc/en/language/basic-syntax.xml diff -u phpdoc/en/language/basic-syntax.xml:1.37 phpdoc/en/language/basic-syntax.xml:1.38 --- phpdoc/en/language/basic-syntax.xml:1.37Wed May 5 14:58:33 2004 +++ phpdoc/en/language/basic-syntax.xml Wed May 5 16:19:50 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.37 $ -- +!-- $Revision: 1.38 $ -- chapter id=language.basic-syntax titleBasic syntax/title @@ -109,9 +109,9 @@ functionshort_tags/function function (PHP 3 only), by enabling the link linkend=ini.short-open-tagshort_open_tag/link configuration setting in the PHP config file, or by compiling PHP -with the --enable-short-tags option to +with the option--enable-short-tags/option option to commandconfigure/command. Even if it is enabled by default in -php.ini-dist, use of short tags are discouraged. +filenamephp.ini-dist/filename, use of short tags are discouraged. /para para @@ -120,12 +120,11 @@ /para para -The fourth way is only available if ASP-style tags have been -enabled using the link linkend=ini.asp-tagsasp_tags/link +The fourth way is only available if productnameASP/productname +tags have been enabled using the link linkend=ini.asp-tagsasp_tags/link configuration setting. - note - paraSupport for ASP-style tags was added in 3.0.4./para + paraSupport for productnameASP/productname tags was added in 3.0.4./para /note /para http://cvs.php.net/diff.php/phpdoc/en/language/control-structures.xml?r1=1.89r2=1.90ty=u Index: phpdoc/en/language/control-structures.xml diff -u phpdoc/en/language/control-structures.xml:1.89 phpdoc/en/language/control-structures.xml:1.90 --- phpdoc/en/language/control-structures.xml:1.89 Sun Mar 21 05:27:53 2004 +++ phpdoc/en/language/control-structures.xml Wed May 5 16:19:50 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.89 $ -- +!-- $Revision: 1.90 $ -- chapter id=language.control-structures titleControl Structures/title @@ -24,8 +24,10 @@ informalexample programlisting ![CDATA[ -if (expr) -statement +?php + if (expression) +commandes +? ]] /programlisting /informalexample @@ -42,8 +44,8 @@ /simpara para The following example would display computeroutputa is bigger -than b/computeroutput if replaceable$a/replaceable is bigger -than replaceable$b/replaceable: +than b/computeroutput if varname$a/varname is bigger +than varname$b/varname: informalexample programlisting role=php ![CDATA[ @@ -61,9 +63,9 @@ with an literalif/literal clause. Instead, you can group several statements into a statement group. For example, this code would display computeroutputa is bigger than b/computeroutput -if replaceable$a/replaceable is bigger than -replaceable$b/replaceable, and would then assign the value of -replaceable$a/replaceable into replaceable$b/replaceable: +if varname$a/varname is bigger than +varname$b/varname, and would then assign the value of +varname$a/varname into varname$b/varname: informalexample programlisting role=php ![CDATA[ @@ -95,8 +97,8 @@ in case the expression in the literalif/literal statement evaluates to false;. For example, the following code would display computeroutputa is bigger than -b/computeroutput if replaceable$a/replaceable is bigger than -replaceable$b/replaceable, and computeroutputa is NOT bigger +b/computeroutput if varname$a/varname is bigger than +varname$b/varname, and computeroutputa is NOT bigger than b/computeroutput otherwise: informalexample programlisting role=php @@ -199,7 +201,7 @@ simpara In the above example, the HTML block A is equal to 5 is nested within an literalif/literal statement written in the alternative syntax. The -HTML block would be displayed only if $a is equal to 5. +HTML block would be displayed only if varname$a/varname is equal to 5. /simpara para The alternative syntax applies to literalelse/literal and @@ -390,24 +392,24 @@ /informalexample /para simpara -The first expression (replaceableexpr1/replaceable) is +The first expression (varnameexpr1/varname) is evaluated (executed) once unconditionally at the beginning of the loop. /simpara simpara In the beginning of each iteration, -replaceableexpr2/replaceable is evaluated. If it evaluates to +varnameexpr2/varname is evaluated.
[PHP-DOC] cvs: phpdoc /en/language control-structures.xml
didou Wed May 5 16:33:32 2004 EDT Modified files: /phpdoc/en/language control-structures.xml Log: no french here http://cvs.php.net/diff.php/phpdoc/en/language/control-structures.xml?r1=1.90r2=1.91ty=u Index: phpdoc/en/language/control-structures.xml diff -u phpdoc/en/language/control-structures.xml:1.90 phpdoc/en/language/control-structures.xml:1.91 --- phpdoc/en/language/control-structures.xml:1.90 Wed May 5 16:19:50 2004 +++ phpdoc/en/language/control-structures.xml Wed May 5 16:33:32 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.90 $ -- +!-- $Revision: 1.91 $ -- chapter id=language.control-structures titleControl Structures/title @@ -26,7 +26,7 @@ ![CDATA[ ?php if (expression) -commandes +statement ? ]] /programlisting
Re: [PHP-DOC] [PATCH] rtl...
On Wed, 5 May 2004, Nuno Lopes wrote: OMG. using global $DEFINE is right! If you don't declare it as global, it won't work if register_globals is off (as you should have it! :) $GLOBALS['key'] please, no global $key; Derick
Re: [PHP-DOC] CHM Manual of Japanese version
The latest version(29 Apr. 5,083,031bytes) looks like well, but its keyword list still turns into garbage. I guess this is because the system settings checked to support Japanese only, not to set *default*. You can take a look at http://www.nihongo-ok.com/method/010326/6_general_l.jpg . If it is certain to set default language to Japanese, it is impossible to generate a correct file on a non-Japanese platform. Then what can I do for the next? regards -- Akira Shirogane [EMAIL PROTECTED]
