[PHP-DOC] #25121 [Opn->Csd]: French XSLT documentation is outdated

2003-08-17 Thread didou
 ID:   25121
 Updated by:   [EMAIL PROTECTED]
 Reported By:  obones at meloo dot com
-Status:   Open
+Status:   Closed
 Bug Type: Documentation problem
 Operating System: Linux
 PHP Version:  4.3.2
 New Comment:

This have been commited to cvs in june, we've got to wait for the
manual update :)

didou


Previous Comments:


[2003-08-17 18:59:06] obones at meloo dot com

Description:

The French documentation for the XLST functions is outdated and as such
innaccurate.
It still refers to the old syntax which leads to a segmentation fault
in apache when used with the latest version of PHP and Sablotron.

Reproduce code:
---
No code needed






-- 
Edit this bug report at http://bugs.php.net/?id=25121&edit=1


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP-DOC] #25121 [NEW]: French XSLT documentation is outdated

2003-08-17 Thread obones at meloo dot com
From: obones at meloo dot com
Operating system: Linux
PHP version:  4.3.2
PHP Bug Type: Documentation problem
Bug description:  French XSLT documentation is outdated

Description:

The French documentation for the XLST functions is outdated and as such
innaccurate.
It still refers to the old syntax which leads to a segmentation fault in
apache when used with the latest version of PHP and Sablotron.

Reproduce code:
---
No code needed


-- 
Edit bug report at http://bugs.php.net/?id=25121&edit=1
-- 
Try a CVS snapshot (php4):  http://bugs.php.net/fix.php?id=25121&r=trysnapshot4
Try a CVS snapshot (php5):  http://bugs.php.net/fix.php?id=25121&r=trysnapshot5
Fixed in CVS:   http://bugs.php.net/fix.php?id=25121&r=fixedcvs
Fixed in release:   http://bugs.php.net/fix.php?id=25121&r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=25121&r=needtrace
Try newer version:  http://bugs.php.net/fix.php?id=25121&r=oldversion
Not developer issue:http://bugs.php.net/fix.php?id=25121&r=support
Expected behavior:  http://bugs.php.net/fix.php?id=25121&r=notwrong
Not enough info:http://bugs.php.net/fix.php?id=25121&r=notenoughinfo
Submitted twice:http://bugs.php.net/fix.php?id=25121&r=submittedtwice
register_globals:   http://bugs.php.net/fix.php?id=25121&r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=25121&r=php3
Daylight Savings:   http://bugs.php.net/fix.php?id=25121&r=dst
IIS Stability:  http://bugs.php.net/fix.php?id=25121&r=isapi
Install GNU Sed:http://bugs.php.net/fix.php?id=25121&r=gnused


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP-DOC] cvs: phpdoc /en/chapters install.iplanet.xml

2003-08-17 Thread Uwe Schindler
thetaphiSun Aug 17 18:15:08 2003 EDT

  Modified files:  
/phpdoc/en/chapters install.iplanet.xml 
  Log:
  some more infos to ini settings
  
Index: phpdoc/en/chapters/install.iplanet.xml
diff -u phpdoc/en/chapters/install.iplanet.xml:1.6 
phpdoc/en/chapters/install.iplanet.xml:1.7
--- phpdoc/en/chapters/install.iplanet.xml:1.6  Tue Aug  5 18:06:05 2003
+++ phpdoc/en/chapters/install.iplanet.xml  Sun Aug 17 18:15:07 2003
@@ -1,5 +1,5 @@
 
-
+
   
Servers-Netscape, iPlanet and SunONE

@@ -160,8 +160,10 @@
 ]]>
  
  (PHP >= 4.3.3) As additional parameters you can add some special 
&php.ini;-values, for example you
- can set a docroot specific to the context 
php4_execute
- is called.
+ can set a docroot="/path/to/docroot" specific 
to the context php4_execute
+ is called. For boolean ini-keys please use 0/1 as value, not 
"On","Off",...
+ (this will not work correctly), e.g. 
zlib.output_compression=1 instead of
+ zlib.output_compression="On"
 


@@ -325,8 +327,10 @@
 ]]>

(PHP >= 4.3.3) As additional parameters you can add some special 
&php.ini;-values, for example you
-   can set a docroot specific to the context 
php4_execute
-   is called.
+   can set a docroot="/path/to/docroot" specific to 
the context php4_execute
+   is called. For boolean ini-keys please use 0/1 as value, not 
"On","Off",...
+   (this will not work correctly), e.g. 
zlib.output_compression=1 instead of
+   zlib.output_compression="On"
   
  
  



-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP-DOC] #25120 [NEW]: contridictory statements in install.txt

2003-08-17 Thread kingjojo75 at hotmail dot com
From: kingjojo75 at hotmail dot com
Operating system: win2k
PHP version:  4.3.2
PHP Bug Type: Documentation problem
Bug description:  contridictory statements in install.txt

Description:

the install.txt doc in the windows binaries distros seem to cover several
versions of php and seem to be contridictory.

first the file warns that you should not use the sapi modules, then later
you are told that the sapi modules are stable and that you should not use
the cgi file ("to do so is suicide") perhaps the wording needs to be
retooled, but is is confusing as it is.

Reproduce code:
---
please note that the SAPI modules are *NOT* yet considered to be
production quality.
The reason for this is that the PHP SAPI modules are using the thread-safe
version of the PHP code, which is new to PHP 4, and has not yet been
tested and pounded enough to be considered completely stable,.

Now that version 4.1 introduces a safer sapi module, we recommend that you
configure PHP as a module in Apache

If you wish to install PHP as a CGI binary, read this first:
http://www.cert.org/advisories/CA-1996-11.html
and then if you are really sure, insert these lines to your conf file: 
ScriptAlias /php/ "c:/php/"
AddType application/x-httpd-php .php
Action application/x-httpd-php "/php/php.exe"
Note, we consider installing PHP like this suicidal.

Expected result:

I would hope for a straight forward install doc specific for the version
its packaged with, not an entire history.


-- 
Edit bug report at http://bugs.php.net/?id=25120&edit=1
-- 
Try a CVS snapshot (php4):  http://bugs.php.net/fix.php?id=25120&r=trysnapshot4
Try a CVS snapshot (php5):  http://bugs.php.net/fix.php?id=25120&r=trysnapshot5
Fixed in CVS:   http://bugs.php.net/fix.php?id=25120&r=fixedcvs
Fixed in release:   http://bugs.php.net/fix.php?id=25120&r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=25120&r=needtrace
Try newer version:  http://bugs.php.net/fix.php?id=25120&r=oldversion
Not developer issue:http://bugs.php.net/fix.php?id=25120&r=support
Expected behavior:  http://bugs.php.net/fix.php?id=25120&r=notwrong
Not enough info:http://bugs.php.net/fix.php?id=25120&r=notenoughinfo
Submitted twice:http://bugs.php.net/fix.php?id=25120&r=submittedtwice
register_globals:   http://bugs.php.net/fix.php?id=25120&r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=25120&r=php3
Daylight Savings:   http://bugs.php.net/fix.php?id=25120&r=dst
IIS Stability:  http://bugs.php.net/fix.php?id=25120&r=isapi
Install GNU Sed:http://bugs.php.net/fix.php?id=25120&r=gnused


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP-DOC] return issues, array issues

2003-08-17 Thread Heilig (Cece) Szabolcs
Hello!

>> >> return 0;
>> >> // 0 aren't variable, it's an expression.
>> >> // should it be return (0); ?
>> >
>> > no, why?
>>
>> If we got the rules strictly, 0 is an expression, not a
>> variable. But that's a really basic expression :)
>>
>> What about arrays?
>
> I agree with Derick. What is the problem with this? It doesn't matter
> at all what kind of expression appears after the 'return', but some
> expression must (unless you want to return null).

That was a stupid question from me to clear all issues :)
There is no problem with return. The problem is how to handle
"array".
I am ready to revert all modifications with array, but need
to know is's okay to all to revert back all array() to array ().

Cece




-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DOC] return issues

2003-08-17 Thread Lars Torben Wilson
On Sun, 2003-08-17 at 07:39, Heilig (Cece) Szabolcs wrote:
> Hello!
> 
> >> return 0;
> >> // 0 aren't variable, it's an expression.
> >> // should it be return (0); ?
> >
> > no, why?
> 
> If we got the rules strictly, 0 is an expression, not a
> variable. But that's a really basic expression :)
> 
> What about arrays?

I agree with Derick. What is the problem with this? It doesn't matter
at all what kind of expression appears after the 'return', but some
expression must (unless you want to return null).


-- 
 Torben Wilson <[EMAIL PROTECTED]>+1.604.709.0506
 http://www.thebuttlesschaps.com  http://www.inflatableeye.com
 http://www.hybrid17.com  http://www.themainonmain.com
 - Boycott Starbucks!  http://www.haidabuckscafe.com -




-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP-DOC] cvs: phpdoc /en/faq html.xml

2003-08-17 Thread Derick Rethans
derick  Sun Aug 17 15:09:25 2003 EDT

  Modified files:  
/phpdoc/en/faq  html.xml 
  Log:
  - Pretty up examples
  
  
Index: phpdoc/en/faq/html.xml
diff -u phpdoc/en/faq/html.xml:1.21 phpdoc/en/faq/html.xml:1.22
--- phpdoc/en/faq/html.xml:1.21 Tue Apr  8 23:22:19 2003
+++ phpdoc/en/faq/html.xml  Sun Aug 17 15:09:25 2003
@@ -1,5 +1,5 @@
 
-
+
  
   PHP and HTML
   PHP and HTML
@@ -49,7 +49,7 @@
 
 
 
@@ -69,7 +69,7 @@
 
 
 
@@ -233,7 +233,7 @@
   are all passed with the same widget name. ie.
   
 
   
   Each selected option will arrive at the action handler as:
@@ -248,7 +248,7 @@
   should be used:
   
 
   
   This tells PHP to treat $var as an array and
@@ -307,7 +307,7 @@
   // (preserve the original query string
   //   -- post variables will need to handled differently)
 
-  echo "\n";
+  echo "