[PHP-DOC] #34195 [Opn]: Running PHP 4 and PHP 5 concurrently
ID: 34195 User updated by: phpnet at gwaihir dot net Reported By: phpnet at gwaihir dot net Status: Open Bug Type: Documentation problem Operating System: all PHP Version: Irrelevant New Comment: Derick, of course, if modules are possible that would be best. But while that setup of yours is an excellent one for testing with multiple versions, I don't quite see that work out on a standard production server just yet, where for various reasons (mainly firewalls and suspicions) all users will need to be served from port 80. Or is there is some way to internally redirect from one Apache to another? I.e. receive all requests with the Apache on port 80, but redirect some to another internally, with for example an .htaccess on a particular folder. Previous Comments: [2005-08-20 22:07:47] [EMAIL PROTECTED] I think that running as CGI is quite suboptimal. I prefer to run two different apache setups. Some info on that is here: http://ez.no/community/articles/multiple_apache_installations_howto [2005-08-20 14:55:42] phpnet at gwaihir dot net Description: This much needed bit of documentation is missing. It may not work the 3 - 4 way, but A way is badly needed to get major hosts to start the transition period. After all, expecting folk to just flip the switch on a production machine just isn't realistic (nor would it get PHP a good rep). So, I hear it can be done by adding php5 as CGI (initially). Can you write down how? It would be even better of course, if some folk subsequently went out and familiarized some of the major hosting panel makers (such as CPanel) on how to make it part of their software.. -- Edit this bug report at http://bugs.php.net/?id=34195edit=1
[PHP-DOC] #34195 [Opn]: Running PHP 4 and PHP 5 concurrently
ID: 34195 Updated by: [EMAIL PROTECTED] Reported By: phpnet at gwaihir dot net Status: Open Bug Type: Documentation problem Operating System: all PHP Version: Irrelevant New Comment: That's exactly what the document describes - using mod_proxy to proxy through something that only is bind to localhost:8080. Ofcourse, if you have two external IPs you can simply bind each of the apaches to a different IP. Previous Comments: [2005-08-22 14:23:40] phpnet at gwaihir dot net Derick, of course, if modules are possible that would be best. But while that setup of yours is an excellent one for testing with multiple versions, I don't quite see that work out on a standard production server just yet, where for various reasons (mainly firewalls and suspicions) all users will need to be served from port 80. Or is there is some way to internally redirect from one Apache to another? I.e. receive all requests with the Apache on port 80, but redirect some to another internally, with for example an .htaccess on a particular folder. [2005-08-20 22:07:47] [EMAIL PROTECTED] I think that running as CGI is quite suboptimal. I prefer to run two different apache setups. Some info on that is here: http://ez.no/community/articles/multiple_apache_installations_howto [2005-08-20 14:55:42] phpnet at gwaihir dot net Description: This much needed bit of documentation is missing. It may not work the 3 - 4 way, but A way is badly needed to get major hosts to start the transition period. After all, expecting folk to just flip the switch on a production machine just isn't realistic (nor would it get PHP a good rep). So, I hear it can be done by adding php5 as CGI (initially). Can you write down how? It would be even better of course, if some folk subsequently went out and familiarized some of the major hosting panel makers (such as CPanel) on how to make it part of their software.. -- Edit this bug report at http://bugs.php.net/?id=34195edit=1
[PHP-DOC] #34195 [Opn]: Running PHP 4 and PHP 5 concurrently
ID: 34195 User updated by: phpnet at gwaihir dot net Reported By: phpnet at gwaihir dot net Status: Open Bug Type: Documentation problem Operating System: all PHP Version: Irrelevant New Comment: Oops.. sorry. Apparently missed that bit. Only saw the direct multi-port approach. So, a link to your document from the php.net docs would pretty much be all it takes to fill this hiatus. :) Although.. this approach moves sites (virtual hosts) over as a whole. Would there be a more finegrained way too, allowing an individual user to run some scripts on php4 still while running others on php5 already? I'm thinking towards using .php5 as extention, or a .htaccess directive in a specific folder.. Previous Comments: [2005-08-22 14:43:34] [EMAIL PROTECTED] That's exactly what the document describes - using mod_proxy to proxy through something that only is bind to localhost:8080. Ofcourse, if you have two external IPs you can simply bind each of the apaches to a different IP. [2005-08-22 14:23:40] phpnet at gwaihir dot net Derick, of course, if modules are possible that would be best. But while that setup of yours is an excellent one for testing with multiple versions, I don't quite see that work out on a standard production server just yet, where for various reasons (mainly firewalls and suspicions) all users will need to be served from port 80. Or is there is some way to internally redirect from one Apache to another? I.e. receive all requests with the Apache on port 80, but redirect some to another internally, with for example an .htaccess on a particular folder. [2005-08-20 22:07:47] [EMAIL PROTECTED] I think that running as CGI is quite suboptimal. I prefer to run two different apache setups. Some info on that is here: http://ez.no/community/articles/multiple_apache_installations_howto [2005-08-20 14:55:42] phpnet at gwaihir dot net Description: This much needed bit of documentation is missing. It may not work the 3 - 4 way, but A way is badly needed to get major hosts to start the transition period. After all, expecting folk to just flip the switch on a production machine just isn't realistic (nor would it get PHP a good rep). So, I hear it can be done by adding php5 as CGI (initially). Can you write down how? It would be even better of course, if some folk subsequently went out and familiarized some of the major hosting panel makers (such as CPanel) on how to make it part of their software.. -- Edit this bug report at http://bugs.php.net/?id=34195edit=1
[PHP-DOC] #33598 [Ver-Opn]: Throwing exception from __destruct causes fatal error
ID: 33598
Updated by: [EMAIL PROTECTED]
Reported By: carlo dot razzeto at mtginfo dot com
-Status: Verified
+Status: Open
-Bug Type: Class/Object related
+Bug Type: Documentation problem
Operating System: *
PHP Version: 5CVS-2005-08-03
New Comment:
Throwing exceptions in __desctruct() is not allowed.
Should be documented..
Previous Comments:
[2005-07-07 01:46:59] carlo dot razzeto at mtginfo dot com
Description:
When performing an operation which throws an exception in the
__destruct method of a class, the following Error is generated
Fatal error: Exception thrown without a stack frame in Unknown on line
0
I have only observed this happening when an object goes out of scope
because the script has ended. Rather than generating a scripting engine
error, PHP should allow for the script to deal with the error, for
instance when an exception handler has been specified by the script.
Reproduce code:
---
class test {
function __construct() {
echo Construct\n;
}
function greet() {
echo Hello World\n;
}
function __destruct() {
echo Destruct\n;
throw new Exception( 'test' );
}
}
$test = new test();
$test-greet();
Expected result:
Construct
Hello World
Destruct
Fatal error: Uncaught exception 'Exception' with message 'test' in
/home/crazzeto/test.php:13
Stack trace:
#0 /home/crazzeto/test.php(13): test::__destruct()
#1 /home/crazzeto/test.php(20): test::__destruct()
#2 /home/crazzeto/test.php(20): unknown()
#3 {main}
thrown in /home/crazzeto/test.php on line 13
Actual result:
--
[EMAIL PROTECTED] crazzeto]$ php test.php
Construct
Hello World
Destruct
Fatal error: Exception thrown without a stack frame in Unknown on line
0
--
Edit this bug report at http://bugs.php.net/?id=33598edit=1
[PHP-DOC] #34212 [NEW]: Brazilian portuguese translation for ngettext function
From: tfpsky at yahoo dot com dot br Operating system: Irrelevant PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: Brazilian portuguese translation for ngettext function Description: In brazilian documentation version, ngettext explanation is not saying what the function actually does. Reproduce code: --- No code. Expected result: Suggestion for new translation: ngettext (PHP 4 = 4.2.0, PHP 5) ngettext -- Versão plural para gettext Descrição string ngettext ( string msgid1, string msgid2, int n ) ngettext() retorna a tradução de msgid1 caso o terceiro parâmetro seja igual a 1. Caso contrário, retorna a tradução de msgid2. Actual result: -- The current translation: ngettext (PHP 4 = 4.2.0, PHP 5) ngettext -- O mesmo que gettext, mas você pode especificar mais de uma mensagem Description string ngettext ( string msgid1, string msgid2, int n ) -- Edit bug report at http://bugs.php.net/?id=34212edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=34212r=trysnapshot4 Try a CVS snapshot (php5.0): http://bugs.php.net/fix.php?id=34212r=trysnapshot50 Try a CVS snapshot (php5.1): http://bugs.php.net/fix.php?id=34212r=trysnapshot51 Fixed in CVS:http://bugs.php.net/fix.php?id=34212r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=34212r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=34212r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=34212r=needscript Try newer version: http://bugs.php.net/fix.php?id=34212r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=34212r=support Expected behavior: http://bugs.php.net/fix.php?id=34212r=notwrong Not enough info: http://bugs.php.net/fix.php?id=34212r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=34212r=submittedtwice register_globals:http://bugs.php.net/fix.php?id=34212r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=34212r=php3 Daylight Savings:http://bugs.php.net/fix.php?id=34212r=dst IIS Stability: http://bugs.php.net/fix.php?id=34212r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=34212r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=34212r=float No Zend Extensions: http://bugs.php.net/fix.php?id=34212r=nozend MySQL Configuration Error: http://bugs.php.net/fix.php?id=34212r=mysqlcfg
[PHP-DOC] build failure en (2005-08-23)
/usr/bin/openjade:manual.xml:125:20:E: character data is not allowed here /usr/bin/openjade:manual.xml:126:7:E: end tag for part which is not finished /usr/bin/openjade:manual.xml:154:23:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:11:15:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:13:33:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:14:18:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:16:26:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:17:25:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:19:35:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:20:34:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:21:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:30:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:32:32:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:33:31:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:34:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:39:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:41:31:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:42:30:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:43:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:54:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:56:35:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:57:34:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:58:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:63:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:65:33:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:66:32:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:67:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:76:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:78:11:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:80:29:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:81:28:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:83:39:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:84:38:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:85:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:93:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:95:38:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:96:37:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:97:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:121:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:123:11:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:125:24:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:126:23:E: character data is not allowed here
[PHP-DOC] #34215 [NEW]: language.expressions.php - Translation error
From: xenon54 at generationphp dot net Operating system: Irrelevant PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: language.expressions.php - Translation error Description: Just an error of translation for this page: http://www.php.net/manual/fr/language.expressions.php 2 paragraphs after the Example 14-1, you can read: PHP supporte 3 types de variables scalaires : les valeurs entières (entier), les nombres à virgule flottante (float), les chaînes de caractères (chaîne de caractères) et les booléens (boolean). After some counting and checking with the English version, we should read: PHP supporte 4 types de variables scalaires : les valeurs entières (entier), les nombres à virgule flottante (float), les chaînes de caractères (chaîne de caractères) et les booléens (boolean). -- Edit bug report at http://bugs.php.net/?id=34215edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=34215r=trysnapshot4 Try a CVS snapshot (php5.0): http://bugs.php.net/fix.php?id=34215r=trysnapshot50 Try a CVS snapshot (php5.1): http://bugs.php.net/fix.php?id=34215r=trysnapshot51 Fixed in CVS:http://bugs.php.net/fix.php?id=34215r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=34215r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=34215r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=34215r=needscript Try newer version: http://bugs.php.net/fix.php?id=34215r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=34215r=support Expected behavior: http://bugs.php.net/fix.php?id=34215r=notwrong Not enough info: http://bugs.php.net/fix.php?id=34215r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=34215r=submittedtwice register_globals:http://bugs.php.net/fix.php?id=34215r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=34215r=php3 Daylight Savings:http://bugs.php.net/fix.php?id=34215r=dst IIS Stability: http://bugs.php.net/fix.php?id=34215r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=34215r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=34215r=float No Zend Extensions: http://bugs.php.net/fix.php?id=34215r=nozend MySQL Configuration Error: http://bugs.php.net/fix.php?id=34215r=mysqlcfg
[PHP-DOC] #33772 [Ctl-Opn]: __destruct is run too early (session_save_handler)
ID: 33772
Updated by: [EMAIL PROTECTED]
Reported By: msipria at suomi24 dot fi
-Status: Critical
+Status: Open
-Bug Type: Class/Object related
+Bug Type: Documentation problem
Operating System: *
PHP Version: 5CVS-2005-07-19
New Comment:
Reclassified as documentation issue.
Previous Comments:
[2005-08-09 14:55:03] [EMAIL PROTECTED]
This patch fixes this problem by doing php_session_flush() before any
__destruct()'s are called:
http://www.php.net/~jani/patches/bug33772.patch
Note: It won't work if you have compiled ext/session as shared. We need
a better solution, I'm submitting this just as as temporary one.
[2005-08-09 14:01:49] [EMAIL PROTECTED]
This is chicken/egg problem and it cannot be solved. One expect that
destructors are called before session close the other uses object for
save handlers.
[2005-07-21 16:38:11] msipria at suomi24 dot fi
my class isn't extension of mysqli class, it just use it as object, and
with real class i have tryed session_write_close() function but mysql
connection is deat, i don't wanna restor it, i just wanna that it will
be alive at the end like now.
[2005-07-21 00:10:05] toma at smartsemantics dot com
Adding session_write_close() to the __destruct() function will restore
the write, close, and destroy functions to their proper order.
I use a custom session handler that extends my custom mysqli class. It
automatically checks for lost database connections and attempts
reconnects, etc.
This is still a bug, but the following makes your custom session
handler viable.
public function __destruct(){
@session_write_close();
}
Without session_write_close:
starting session
connecting to database
destroying session
writing session
can't write, database connection does not exist
connecting to database
writing session
closing session
With session_write_close:
starting session
connecting to database
writing session
closing session
destroying session
[2005-07-19 21:20:45] [EMAIL PROTECTED]
I need this fixed too, it's not possible to use e.g. mysqli as save
handler otherwise..
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/33772
--
Edit this bug report at http://bugs.php.net/?id=33772edit=1
[PHP-DOC] Re: build failure en (2005-08-23)
I think it's because the manual build machine didn't run 'cvs up' before make. And also it should run 'autoconf', since 'configure.in' was also changed. Actually I just build the Chinese manual this afternoon, not a single problem. [EMAIL PROTECTED] 写入消息新闻:[EMAIL PROTECTED] /usr/bin/openjade:manual.xml:125:20:E: character data is not allowed here /usr/bin/openjade:manual.xml:126:7:E: end tag for part which is not finished /usr/bin/openjade:manual.xml:154:23:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:11:15:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:13:33:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:14:18:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:16:26:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:17:25:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:19:35:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:20:34:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:21:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:30:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:32:32:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:33:31:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:34:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:39:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:41:31:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:42:30:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:43:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:54:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:56:35:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:57:34:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:58:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:63:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:65:33:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:66:32:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:67:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:76:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:78:11:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:80:29:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:81:28:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:83:39:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:84:38:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:85:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:93:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:95:38:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:96:37:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:97:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:121:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:123:11:E: end tag for section which is not
[PHP-DOC] #34215 [Opn-Csd]: language.expressions.php - Translation error
ID: 34215 Updated by: [EMAIL PROTECTED] Reported By: xenon54 at generationphp dot net -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Irrelevant 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: [2005-08-23 02:58:51] xenon54 at generationphp dot net Description: Just an error of translation for this page: http://www.php.net/manual/fr/language.expressions.php 2 paragraphs after the Example 14-1, you can read: PHP supporte 3 types de variables scalaires : les valeurs entières (entier), les nombres à virgule flottante (float), les chaînes de caractères (chaîne de caractères) et les booléens (boolean). After some counting and checking with the English version, we should read: PHP supporte 4 types de variables scalaires : les valeurs entières (entier), les nombres à virgule flottante (float), les chaînes de caractères (chaîne de caractères) et les booléens (boolean). -- Edit this bug report at http://bugs.php.net/?id=34215edit=1
