[PHP-DOC] #28637 [Opn->Csd]: French translation error : pack()
ID: 28637 Updated by: [EMAIL PROTECTED] Reported By: bmorel at ssi dot fr -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: none 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-06-05 04:04:37] bmorel at ssi dot fr Description: In page: http://fr2.php.net/manual/fr/function.pack.php Expected result: N entier long non signé (toujours 32 bits, ordre des bits big endian) V entier long non signé (toujours 32 bits, ordre des bits little endian) Actual result: -- N entier long non signé (toujours 16 bits, ordre des bits big endian) V entier long non signé (toujours 16 bits, ordre des bits little endian) -- Edit this bug report at http://bugs.php.net/?id=28637&edit=1
[PHP-DOC] #28637 [NEW]: French translation error : pack()
From: bmorel at ssi dot fr Operating system: none PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: French translation error : pack() Description: In page: http://fr2.php.net/manual/fr/function.pack.php Expected result: N entier long non signé (toujours 32 bits, ordre des bits big endian) V entier long non signé (toujours 32 bits, ordre des bits little endian) Actual result: -- N entier long non signé (toujours 16 bits, ordre des bits big endian) V entier long non signé (toujours 16 bits, ordre des bits little endian) -- Edit bug report at http://bugs.php.net/?id=28637&edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=28637&r=trysnapshot4 Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=28637&r=trysnapshot5 Fixed in CVS: http://bugs.php.net/fix.php?id=28637&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=28637&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=28637&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=28637&r=needscript Try newer version: http://bugs.php.net/fix.php?id=28637&r=oldversion Not developer issue:http://bugs.php.net/fix.php?id=28637&r=support Expected behavior: http://bugs.php.net/fix.php?id=28637&r=notwrong Not enough info:http://bugs.php.net/fix.php?id=28637&r=notenoughinfo Submitted twice:http://bugs.php.net/fix.php?id=28637&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=28637&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=28637&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=28637&r=dst IIS Stability: http://bugs.php.net/fix.php?id=28637&r=isapi Install GNU Sed:http://bugs.php.net/fix.php?id=28637&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=28637&r=float
[PHP-DOC] install part: iplanet server blues
Hi, So far the "split by os then by server" method is quite fine, Apache 2 has some notes which need to be on all ocassions of Apache 2, but they are not really huge, so it is not a real problem. However the iPlanet server docs has three sections which are meant to be cross-platform, so it is a good question on where should we put them. - Either we pick one platform and put these docs there, and link it in from the other one. This might not be good, since some docs have small differences based on OS. - Or we create snippet xml files out of the sections and insert them to both of the docs (Windows and Solaris). This might not be good, since some docs have small differences based on OS. - Or we put the somewhat different text at both places in the XML, only having OS relevant notes at both places. This makes the best output for our readers, but it is a bit harder to maintain and translate. See: http://php.net/install.netscape-enterprise Your choice? Number four? Goba
[PHP-DOC] updating the PHP manual (Xitami server)
Dear Imatix Support, We are in the process of seriously revising and updating the installation instructions presented in the PHP Manual. We have a short section on installing PHP with Xitami [1], and so a lot of users felt that they know that better, and added their instructions. We would like to present accurate and up to date instructions out of the box, so I would like to ask you to help us provide updated instructions for Xitami server, so our readers can get the information, and use PHP with your product with satisfaction. Note that this email is publicly archived, and we would like to ask you to reply with the 'reply all' function, so others in the team will be able to read the information. Note that your answer will also be publicly archived. [1] http://php.net/install.xitami Thanks, Tom Sommer - PHP Documentation
[PHP-DOC] cvs: phpdoc /en/install/windows index.xml sambar.xml xitami.xml
gobaFri Jun 4 17:51:43 2004 EDT Added files: /phpdoc/en/install/windows sambar.xml xitami.xml Modified files: /phpdoc/en/install/windows index.xml Log: Add Sambar and Xitami here http://cvs.php.net/diff.php/phpdoc/en/install/windows/index.xml?r1=1.4&r2=1.5&ty=u Index: phpdoc/en/install/windows/index.xml diff -u phpdoc/en/install/windows/index.xml:1.4 phpdoc/en/install/windows/index.xml:1.5 --- phpdoc/en/install/windows/index.xml:1.4 Fri Jun 4 17:26:23 2004 +++ phpdoc/en/install/windows/index.xml Fri Jun 4 17:51:43 2004 @@ -1,5 +1,5 @@ - + Installation on Windows systems @@ -32,6 +32,8 @@ &install.windows.apache2; &install.windows.iplanet; &install.windows.omnihttpd; + &install.windows.sambar; + &install.windows.xitami; &install.windows.building; &install.windows.extensions; http://cvs.php.net/co.php/phpdoc/en/install/windows/sambar.xml?r=1.1&p=1 Index: phpdoc/en/install/windows/sambar.xml +++ phpdoc/en/install/windows/sambar.xml Sambar Server on Microsoft Windows This section contains notes and hints specific to the Sambar Server for Windows. This list describes how to set up the ISAPI module to work with the Sambar server on Windows. Find the file called mappings.ini (in the config directory) in the Sambar install directory. Open mappings.ini and add the following line under [ISAPI]: ISAPI configuration of Sambar (This line assumes that PHP was installed in c:\php.) Now restart the Sambar server for the changes to take effect. http://cvs.php.net/co.php/phpdoc/en/install/windows/xitami.xml?r=1.1&p=1 Index: phpdoc/en/install/windows/xitami.xml +++ phpdoc/en/install/windows/xitami.xml Xitami on Microsoft Windows This section contains notes and hints specific to Xitami on Windows. This list describes how to set up the PHP CGI binary to work with Xitami on Windows. Important for CGI users Read the faq on cgi.force_redirect for important details. This directive needs to be set to 0. Make sure the webserver is running, and point your browser to xitamis admin console (usually http://127.0.0.1/admin), and click on Configuration. Navigate to the Filters, and put the extension which PHP should parse (i.e. .php) into the field File extensions (.xxx). In Filter command or script put the path and name of your PHP executable i.e. c:\php\php.exe. Press the 'Save' icon. Restart the server to reflect changes.
Re: [PHP-DOC] updating the PHP manual (Xitami server)
Could someone with fixed IP please resend this? I get a rejection email, since I have dynamic IP, and the imatix SMTP server does not seem to like this. Goba Gabor Hojtsy írta: Dear Imatix Support, We are in the process of seriously revising and updating the installation instructions presented in the PHP Manual. We have a short section on installing PHP with Xitami [1], and so a lot of users felt that they know that better, and added their instructions. We would like to present accurate and up to date instructions out of the box, so I would like to ask you to help us provide updated instructions for Xitami server, so our readers can get the information, and use PHP with your product with satisfaction. Note that this email is publicly archived, and we would like to ask you to reply with the 'reply all' function, so others in the team will be able to read the information. Note that your answer will also be publicly archived. [1] http://php.net/install.xitami Thanks, Gabor Hojtsy - PHP Documentation Editor
[PHP-DOC] updating the PHP manual (Xitami server)
Dear Imatix Support, We are in the process of seriously revising and updating the installation instructions presented in the PHP Manual. We have a short section on installing PHP with Xitami [1], and so a lot of users felt that they know that better, and added their instructions. We would like to present accurate and up to date instructions out of the box, so I would like to ask you to help us provide updated instructions for Xitami server, so our readers can get the information, and use PHP with your product with satisfaction. Note that this email is publicly archived, and we would like to ask you to reply with the 'reply all' function, so others in the team will be able to read the information. Note that your answer will also be publicly archived. [1] http://php.net/install.xitami Thanks, Gabor Hojtsy - PHP Documentation Editor
[PHP-DOC] cvs: phpdoc / installpart.xml.in /en/chapters install.oreilly.xml /en/install/windows index.xml omnihttpd.xml
gobaFri Jun 4 17:26:23 2004 EDT Added files: /phpdoc/en/install/windows omnihttpd.xml Removed files: /phpdoc/en/chapters install.oreilly.xml Modified files: /phpdoc installpart.xml.in /phpdoc/en/install/windows index.xml Log: Remove oreilly stuff from the old install part, since it was discontinued in 2001, and it's successor is not alive either. Add OmniHTTPd to the new install part since it seems to be living well http://cvs.php.net/diff.php/phpdoc/installpart.xml.in?r1=1.4&r2=1.5&ty=u Index: phpdoc/installpart.xml.in diff -u phpdoc/installpart.xml.in:1.4 phpdoc/installpart.xml.in:1.5 --- phpdoc/installpart.xml.in:1.4 Tue Jun 1 16:55:11 2004 +++ phpdoc/installpart.xml.in Fri Jun 4 17:26:23 2004 @@ -18,7 +18,6 @@ &chapters.install.iis; &chapters.install.iplanet; &chapters.install.omnihttpd; - &chapters.install.oreilly; &chapters.install.sambar; &chapters.install.xitami; &chapters.install.otherhttpd; http://cvs.php.net/diff.php/phpdoc/en/install/windows/index.xml?r1=1.3&r2=1.4&ty=u Index: phpdoc/en/install/windows/index.xml diff -u phpdoc/en/install/windows/index.xml:1.3 phpdoc/en/install/windows/index.xml:1.4 --- phpdoc/en/install/windows/index.xml:1.3 Fri Jun 4 06:30:07 2004 +++ phpdoc/en/install/windows/index.xml Fri Jun 4 17:26:23 2004 @@ -1,5 +1,5 @@ - + Installation on Windows systems @@ -31,6 +31,7 @@ &install.windows.apache1; &install.windows.apache2; &install.windows.iplanet; + &install.windows.omnihttpd; &install.windows.building; &install.windows.extensions; http://cvs.php.net/co.php/phpdoc/en/install/windows/omnihttpd.xml?r=1.1&p=1 Index: phpdoc/en/install/windows/omnihttpd.xml +++ phpdoc/en/install/windows/omnihttpd.xml OmniHTTPd Server This section contains notes and hints specific to OmniHTTPd on Windows. You need to complete the following steps to make PHP work with OmniHTTPd. This is a CGI executable setup. SAPI is supported by OmniHTTPd, but some tests have shown that it is not so stable to use PHP as an ISAPI module. Important for CGI users Read the faq on cgi.force_redirect for important details. This directive needs to be set to 0. Install OmniHTTPd server. Right click on the blue OmniHTTPd icon in the system tray and select Properties Click on Web Server Global Settings On the 'External' tab, enter: virtual = .php | actual = c:\path-to-php-dir\php.exe, and use the Add button. On the Mime tab, enter: virtual = wwwserver/stdcgi | actual = .php, and use the Add button. Click OK Repeat steps 2 - 6 for each extension you want to associate with PHP. Some OmniHTTPd packages come with built in PHP support. You can choose at setup time to do a custom setup, and uncheck the PHP component. We recommend you to use the latest PHP binaries. Some OmniHTTPd servers come with PHP 4 beta distributions, so you should choose not to set up the built in support, but install your own. If the server is already on your machine, use the Replace button in Step 4 and 5 to set the new, correct information.
[PHP-DOC] Re: updating the PHP manual (Oreilly Website Pro Server) [347015:117445]
Hi Jennifer, VisNetic WebSite (formerly WebSite Pro) was discontinued (retired) in January, 2004. Complete details are available in a press release at: http://www.deerfield.com/news/pressbox/VisNetic-WebSite/index.htm/180/ Effective March 1, 2004. The Deerfield.com-hosted VisNetic WebSite User Forum became 'Read-Only'. Read-Only allows users to search for answers to previously addressed questions but disables the posting of new questions. VisNetic WebSite and WebSite Pro users can now learn and share their knowledge in the Yahoo! Group - Websiteusers. You can access the Group home page by visiting: http://groups.yahoo.com/group/websiteusers Note: The websiteusers Yahoo! Group is in no way affiliated with Deerfield.com and will not necessarily be monitored by, or participated in, by Deerfield.com and/or the Developers of WebSite. Thanks for the quick answer. I will remove the Oreilly Website Pro docs then. Regards, Gabor Hojtsy - PHP Documentation Editor
[PHP-DOC] Re: doc-license mailing list
This was supposed to be a serious request! Goba Gabor Hojtsy írta: Quoting the 10th point of the 2003 docmeeting findings (which Rasmus attended): ---8<--- Rasmus will add a new mailing list ([EMAIL PROTECTED]) where license questions will be discussed. Anyone, who subscribes to this mailing list can become part of the process, thus eliminating problems with any elections needed to select a few responsible people. Generally the use of documentation is only problematic, if it is done on a large scale. If only some small part is redistributed, than it will probably be no pain for us. If someone would like to publish a significant amount of our work, then we will probably require him to give something back (ie. fix errors in the docs / translation or add examples). In case of translations, the group should ask those working on the translation too. ---8<--- Would it be possible to finally create that mailing list, so we can delegate the licensing questions and decisions to the group subscribed to that mailing list, and can go on with the crediting process. Unless this list is created, we have nowhere to point for licensing questions, and the license stays in the hands of "the authors listed on the frontpage". This legal questions is the one which prevented us from expanding on and making that list actual (while keeping historical credit). Please create that doc-license mailing list! Goba
[PHP-DOC] updating the PHP manual (Oreilly Website Pro Server)
Dear Deerfield.com staff, We are in the process of seriously revising and updating the installation instructions presented in the PHP Manual. While reseraching for information on the Oreilly Website Pro server, we have found out that it was discontinued [1] as of August 2001. That discontinuation statement also includes a reference to Deerfield.com, which is said to continue development on the product. Since the Oreilly server is not supported for nearly three years now, it seems to be logical to me to remove the instructions presented for that server, since there is no point anymore to keep them for historical reasons anyway. However if this server would still be available in your product line, it would be reasonable to update the instructions to match the current state. I was unable to find any information on this product being available on your site. Can you please provide some insight on what happened to this product? Note that this email is publicly archived, and we would like to ask you to reply with the 'reply all' function, so others in the team will be able to read the information. Note that your answer will also be publicly archived. Thanks, Gabor Hojtsy - PHP Documentation Editor
[PHP-DOC] updating the PHP manual
Dear Omnicron Technologies, We are in the process of seriously revising and updating the installation instructions presented in the PHP Manual. We would like to ask you if you are still interested in being part of the install section with the OmniHTTPd server, and if this is the case, could you provide accurate and official installation instructions, so we can update the suggestions in the manual? If you check our manual page on OmniHTTPd [1], you will find that we still refer to some OmniHTTPd servers having PHP 4 beta versions included. That is a clear sign that our documentation is out of date. It would be nice if we could update the instructions with your help. Also we would be happy to include notes on the suggested PHP settings you documented in the news section of your site. Note that this email is publicly archived, and we would like to ask you to reply with the reply all function, so others in the team will be able to read your opinions. Note that your answer will also be publicly archived. [1] http://php.net/install.omnihttpd Thanks, Gabor Hojtsy - PHP Documentation Editor
[PHP-DOC] cvs: phpdoc /en language-defs.ent language-snippets.ent /en/install snippet.apache2.compat.xml /en/install/windows apache1.xml apache2.xml
gobaFri Jun 4 16:29:35 2004 EDT Added files: /phpdoc/en/install snippet.apache2.compat.xml Modified files: /phpdoc/en language-defs.ent language-snippets.ent /phpdoc/en/install/windows apache1.xml apache2.xml Log: Several improvements around the new install part - clearly separate the Apache 2 CGI and SAPI install instructions - add small and big compatibility snippets appropriately, so we can reference them in both the Windows and Unix install instructions - move title snippets to language-defs, as it is supposed to be there - also wrap tidy snippet to make it conform http://cvs.php.net/diff.php/phpdoc/en/language-defs.ent?r1=1.15&r2=1.16&ty=u Index: phpdoc/en/language-defs.ent diff -u phpdoc/en/language-defs.ent:1.15 phpdoc/en/language-defs.ent:1.16 --- phpdoc/en/language-defs.ent:1.15Fri Jun 20 15:22:57 2003 +++ phpdoc/en/language-defs.ent Fri Jun 4 16:29:34 2004 @@ -1,5 +1,6 @@ - + + @@ -18,3 +19,19 @@ + + +Introduction'> +Requirements'> +Installation'> +Runtime Configuration'> +Resource Types'> +Predefined Constants'> +Predefined Classes'> +Constructor'> +Methods'> +Properties'> +Return values'> +Examples'> +See Also'> http://cvs.php.net/diff.php/phpdoc/en/language-snippets.ent?r1=1.92&r2=1.93&ty=u Index: phpdoc/en/language-snippets.ent diff -u phpdoc/en/language-snippets.ent:1.92 phpdoc/en/language-snippets.ent:1.93 --- phpdoc/en/language-snippets.ent:1.92Mon May 24 21:27:50 2004 +++ phpdoc/en/language-snippets.ent Fri Jun 4 16:29:34 2004 @@ -1,4 +1,4 @@ - + This extension is EXPERIMENTAL. The behaviour of this extension -- @@ -262,22 +262,6 @@ been compiled into PHP or dynamically loaded at runtime. '> - -Introduction'> -Requirements'> -Installation'> -Runtime Configuration'> -Resource Types'> -Predefined Constants'> -Predefined Classes'> -Constructor'> -Methods'> -Properties'> -Return values'> -Examples'> -See Also'> - This extension requires PHP 5.'> @@ -339,9 +323,17 @@ config and encoding were added in Tidy 2.0.'> -The config parameter can be passed either as an array -or as a string. If you pass it as a string, it means the name of the configuration file, otherwise -it is interpreted as the options themselves. Check &url.tidy.conf; -for an explanation about each option.The encoding parameter sets the -encoding for input/output documents. The possible values for encoding are: -ascii, latin1, raw, utf8, iso2022, mac, win1252, utf16le, utf16be, utf16, big5 and shiftjis.'> +The config parameter +can be passed either as an array or as a string. If you pass it as a string, +it means the name of the configuration file, otherwise it is interpreted as +the options themselves. Check &url.tidy.conf; +for an explanation about each option.The +encoding parameter sets the encoding for input/output +documents. The possible values for encoding are: +ascii, latin1, raw, utf8, iso2022, mac, win1252, utf16le, utf16be, +utf16, big5 and shiftjis.'> + + +Do not use Apache 2.0.x +and PHP in a production environment neither +on Unix nor on Windows.'> http://cvs.php.net/diff.php/phpdoc/en/install/windows/apache1.xml?r1=1.2&r2=1.3&ty=u Index: phpdoc/en/install/windows/apache1.xml diff -u phpdoc/en/install/windows/apache1.xml:1.2 phpdoc/en/install/windows/apache1.xml:1.3 --- phpdoc/en/install/windows/apache1.xml:1.2 Fri Jun 4 06:30:07 2004 +++ phpdoc/en/install/windows/apache1.xml Fri Jun 4 16:29:35 2004 @@ -1,5 +1,5 @@ - + Apache 1.3.x on Microsft Windows @@ -88,7 +88,7 @@ - + Installing as an Apache module http://cvs.php.net/diff.php/phpdoc/en/install/windows/apache2.xml?r1=1.2&r2=1.3&ty=u Index: phpdoc/en/install/windows/apache2.xml diff -u phpdoc/en/install/windows/apache2.xml:1.2 phpdoc/en/install/windows/apache2.xml:1.3 --- phpdoc/en/install/windows/apache2.xml:1.2 Fri Jun 4 06:30:07 2004 +++ phpdoc/en/install/windows/apache2.xml Fri Jun 4 16:29:35 2004 @@ -1,5 +1,5 @@ - + Apache 2.0.x on Microsoft Windows @@ -8,154 +8,108 @@ have instructions and notes for Apache 1.3.x users on a separate page. - - - Do not use Apache 2.0.x and PHP in a production - environment neither on Unix nor on Windows. - - + +&warn.apache2.compat; + You are highly encouraged to take a look at the Apache Documentation to get - a basic understanding of the Apache 2.0.x Server. + a basic understanding of the Apache 2.0.x Server. Also consider to + read the Windows specific + notes for Apache 2.0.x before reading on here. + +&install.snippet.apache2.compat; - - PHP and Apache 2.0.x compatibility notes - - The following versions of PHP are known to work with the most recent - version of Apache 2.0.x: - - - - PHP 4.3.0 or later available at -
[PHP-DOC] cvs: phpdoc /en/install/windows iis.xml
gobaFri Jun 4 15:52:04 2004 EDT Modified files: /phpdoc/en/install/windows iis.xml Log: fix links to internal IDs, add tags where missing, and a little bit of grammar http://cvs.php.net/diff.php/phpdoc/en/install/windows/iis.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/install/windows/iis.xml diff -u phpdoc/en/install/windows/iis.xml:1.1 phpdoc/en/install/windows/iis.xml:1.2 --- phpdoc/en/install/windows/iis.xml:1.1 Thu Jun 3 18:45:11 2004 +++ phpdoc/en/install/windows/iis.xml Fri Jun 4 15:52:04 2004 @@ -1,13 +1,13 @@ - + Microsoft IIS / PWS This section contains notes and hints specific to IIS (Microsoft -Internet Information Server). Installing PHP for -PWS/IIS 3, -PWS 4 or newer and -IIS 4 or newer versions. +Internet Information Server). We have included installation +instructions for PWS/IIS 3, +PWS 4 or newer and +IIS 4 or newer versions. @@ -25,7 +25,8 @@ The recommended method for configuring these servers is to use the REG file included with the distribution - (pws-php4cgi.reg). You may want to edit this file and make sure + (pws-php4cgi.reg in the SAPI folder). + You may want to edit this file and make sure the extensions and PHP install directories match your configuration. Or you can follow the steps below to do it manually. @@ -196,7 +197,7 @@ Edit the enclosed pws-php4cgi.reg -file (look into the SAPI dir) to reflect the location of +file (look into the SAPI folder) to reflect the location of your php.exe. Backslashes should be escaped, for example: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters\Script Map] ".php"="c:\\php\\php.exe" @@ -220,7 +221,7 @@ Edit the enclosed pws-php4isapi.reg -file (look into the SAPI dir) to reflect the location of +file (look into the SAPI folder) to reflect the location of your php4isapi.dll. Backslashes should be escaped, for example: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters\Script Map] ".php"="c:\\php\\sapi\\php4isapi.dll" @@ -272,19 +273,19 @@ Click Add, and in the Executable box, type: c:\php\php.exe (assuming -that you have unziped PHP in c:\php\). +that you have unziped PHP in c:\php\). In the Extension box, type the file name extension you want associated with PHP scripts. Leave 'Method exclusions' -blank, and check the Script engine checkbox. You may also +blank, and check the 'Script engine' checkbox. You may also like to check the 'check that file exists' box - for a small performance penalty, IIS (or PWS) will check that the script -file exists and sort out authentication before firing up php. +file exists and sort out authentication before firing up PHP. This means that you will get sensible 404 style error messages -instead of cgi errors complaining that PHP did not output any data. +instead of CGI errors complaining that PHP did not output any data. You must start over from the previous step for each @@ -313,16 +314,16 @@ If you don't want to perform HTTP Authentication using PHP, you can (and should) skip this step. Under ISAPI Filters, add a new ISAPI filter. Use PHP as the filter name, and -supply a path to the php4isapi.dll. +supply a path to the php4isapi.dll. Under 'Home Directory', click on the 'Configuration' button. Add a new entry to the Application Mappings. Use the path -to the php4isapi.dll as the Executable, supply -.php as the extension, leave Method -exclusions blank, and check the Script engine checkbox. +to the php4isapi.dll as the Executable, supply +.php as the extension, leave 'Method +exclusions' blank, and check the 'Script engine' checkbox.
[PHP-DOC] #28634 [Opn->Csd]: Error in the french documentation
ID: 28634 Updated by: [EMAIL PROTECTED] Reported By: bugPhp at warix dot net -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Documentation PHP Version: 4.3.7 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-06-04 19:42:59] bugPhp at warix dot net Description: Hi ! In the online french documentation, there is a mistake at the page : http://www.php.net/manual/fr/function.unlink.php It is written : «Note : Depuis PHP 5.0.0, unlink() peut aussi être utilisée avec quelques prôtocoles d'url. Voyez Annexe J pour une liste des prôtocoles supportant unlink().» The mistake was in the spelling of the word «prôtocoles». In the «petit Larousse» dictionary, the word is writen «protocoles». In reallity the correct way is : «Note : Depuis PHP 5.0.0, unlink() peut aussi être utilisée avec quelques protocoles d'url. Voyez Annexe J pour une liste des protocoles supportant unlink().» Thank you for this great documentation ! -- Edit this bug report at http://bugs.php.net/?id=28634&edit=1
[PHP-DOC] #28634 [NEW]: Error in the french documentation
From: bugPhp at warix dot net Operating system: Documentation PHP version: 4.3.7 PHP Bug Type: Documentation problem Bug description: Error in the french documentation Description: Hi ! In the online french documentation, there is a mistake at the page : http://www.php.net/manual/fr/function.unlink.php It is written : «Note : Depuis PHP 5.0.0, unlink() peut aussi être utilisée avec quelques prôtocoles d'url. Voyez Annexe J pour une liste des prôtocoles supportant unlink().» The mistake was in the spelling of the word «prôtocoles». In the «petit Larousse» dictionary, the word is writen «protocoles». In reallity the correct way is : «Note : Depuis PHP 5.0.0, unlink() peut aussi être utilisée avec quelques protocoles d'url. Voyez Annexe J pour une liste des protocoles supportant unlink().» Thank you for this great documentation ! -- Edit bug report at http://bugs.php.net/?id=28634&edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=28634&r=trysnapshot4 Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=28634&r=trysnapshot5 Fixed in CVS: http://bugs.php.net/fix.php?id=28634&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=28634&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=28634&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=28634&r=needscript Try newer version: http://bugs.php.net/fix.php?id=28634&r=oldversion Not developer issue:http://bugs.php.net/fix.php?id=28634&r=support Expected behavior: http://bugs.php.net/fix.php?id=28634&r=notwrong Not enough info:http://bugs.php.net/fix.php?id=28634&r=notenoughinfo Submitted twice:http://bugs.php.net/fix.php?id=28634&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=28634&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=28634&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=28634&r=dst IIS Stability: http://bugs.php.net/fix.php?id=28634&r=isapi Install GNU Sed:http://bugs.php.net/fix.php?id=28634&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=28634&r=float
Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/install README intro.xml problems.xml /en/install/macos client.xml index.xml packages.xml server.xml /en/install/windows apache1.xml apache2.xml building.xml extensions.xml iis.xml index.xml installer.xml m
On Friday 04 June 2004 17:21, Steph wrote: > - or take it straight from cvs.php.net - The preferred way AFAIK, as those in cvs is more complete, no? regards Friedhelm
RE: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/install README intro.xml problems.xml /en/install/macos client.xml index.xml packages.xml server.xml /en/install/windows apache1.xml apache2.xml building.xml extensions.xml iis.xml index.xml installer.xml m
- or take it straight from cvs.php.net - > -Original Message- > From: Friedhelm Betz [mailto:[EMAIL PROTECTED] > Sent: 04 June 2004 15:58 > To: [EMAIL PROTECTED] > Cc: Nuno Lopes; Gabor Hojtsy > Subject: Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/install README > intro.xml problems.xml /en/install/macos client.xml index.xml > packages.xml server.xml /en/install/windows apache1.xml apache2.xml > building.xml extensions.xml iis.xml index.xml installer.xml m > > > [...] > > * Do you still need the bindlib_w32.zip to build PHP in VC++? > AFAIK, yes > Friedhelm > -- > http://www.hostsharing.net/
Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/install README intro.xml problems.xml /en/install/macos client.xml index.xml packages.xml server.xml /en/install/windows apache1.xml apache2.xml building.xml extensions.xml iis.xml index.xml installer.xml ma
[...] > * Do you still need the bindlib_w32.zip to build PHP in VC++? AFAIK, yes Friedhelm -- http://www.hostsharing.net/
Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/install README intro.xml problems.xml /en/install/macos client.xml index.xml packages.xml server.xml /en/install/windows apache1.xml apache2.xml building.xml extensions.xml iis.xml index.xml installer.xml ma
I have just a few question to this: * Should we write the infos for PHP 4, PHP 5, or both? For both IMHO. The Apache stuff is written for both. It is not that different that it is worth the duplication. * If we write the informations for PHP 5 only, should we remove win 95 notes, as its support was removed? There is very little mention of Win95 if I remember correctly. * I think the installer for windows isn't avaliable anymore. Am I right? May we remove the info about it? The installer is *not yet* available for PHP 4.3.7, the code is just commented out with HTML comments, and the link is already updated. The file is just not there yet. IMHO it would also be nice to add more info on the prepackaged Apache-PHP-etc. setups. * PHP can run in windows 64-bits? If yes, the introduction text is wrong, since it refers to Win32. * Do you still need the bindlib_w32.zip to build PHP in VC++? I don't know anything about any of these two. Wez volunteered to fix the windows docs if we will be ready with the split/move. Goba
Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/install README intro.xml problems.xml /en/install/macos client.xml index.xml packages.xml server.xml /en/install/windows apache1.xml apache2.xml building.xml extensions.xml iis.xml index.xml installer.xml ma
I have just a few question to this: * Should we write the infos for PHP 4, PHP 5, or both? * If we write the informations for PHP 5 only, should we remove win 95 notes, as its support was removed? * I think the installer for windows isn't avaliable anymore. Am I right? May we remove the info about it? * PHP can run in windows 64-bits? If yes, the introduction text is wrong, since it refers to Win32. * Do you still need the bindlib_w32.zip to build PHP in VC++? Nuno
Re: [PHP-DOC] PHP Manual - PDF Format?
The PHP manual is not currently avaliable in PDF format. It will be avaliable in the near future. If you really want a PDF version of the manual, you may compile it yourself throught the CVS XML sources. When we have oficial PDF files, they will be avaliable in the php.net website. Nuno Lopes - Original Message - > Is there a PDF format somewhere of the manual so I can print it out all at > once? > > Wayne Stevens > BMC Software, Inc > [EMAIL PROTECTED] > (800) 537-1813 > <<...OLE_Obj...>>
[PHP-DOC] PHP Manual - PDF Format?
Is there a PDF format somewhere of the manual so I can print it out all at once? Wayne Stevens BMC Software, Inc [EMAIL PROTECTED] (800) 537-1813 <<...OLE_Obj...>> === BMC Software Proactive Notification will inform you via email of issues related to BMC Software products, such as the provision of flashes, technical bulletins, product upgrades and release notes. Access Hint: Go to http://www.bmc.com/support.html. Select "Proactive Notification" and enter your support login and password. If you do not have one, you may obtain one by clicking on "First time users" and completing the form presented. Once you've received confirmation of your login and password for the Technical Support Web page, select "Proactive Notification." Fill out the subscription form for Proactive Notification and select all products of interest. We will then notify you via email as new information is released. ===
Re: [PHP-DOC] Feedback for translation-practical.html
On Fri, 4 Jun 2004, Gabor Hojtsy wrote: > Thanks for the deep explanation, but this was fixed in the XML sources > of that document in August 2003 (along with a lot more grammar > problems), so there is nothing to fix there. That HTML version would > probably need an update. Derick, can you do that? Will do that, when I get access again. (Might be after the weekend). regards, Derick
[PHP-DOC] cvs: phpdoc /en/install problems.xml /en/install/macos client.xml index.xml packages.xml server.xml /en/install/windows apache1.xml apache2.xml extensions.xml index.xml installer.xml
gobaFri Jun 4 06:30:07 2004 EDT Modified files: /phpdoc/en/install problems.xml /phpdoc/en/install/macosclient.xml index.xml packages.xml server.xml /phpdoc/en/install/windows apache1.xml apache2.xml extensions.xml index.xml installer.xml Log: reviewing IDs, fixing intro text for MacOS installations, splitting syntax highlight info to the CGI and SAPI part of the Apache 1 docs, adding sections for the CGI and SAPI part so users will be able to identify what they are interested in really http://cvs.php.net/diff.php/phpdoc/en/install/problems.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/install/problems.xml diff -u phpdoc/en/install/problems.xml:1.1 phpdoc/en/install/problems.xml:1.2 --- phpdoc/en/install/problems.xml:1.1 Thu Jun 3 18:45:11 2004 +++ phpdoc/en/install/problems.xml Fri Jun 4 06:30:06 2004 @@ -1,10 +1,10 @@ - + Problems? - + Read the FAQ Some problems are more common than others. The most @@ -13,7 +13,7 @@ - + Other problems @@ -37,7 +37,7 @@ - + Bug reports If you think you have found a bug in PHP, please report it. The http://cvs.php.net/diff.php/phpdoc/en/install/macos/client.xml?r1=1.3&r2=1.4&ty=u Index: phpdoc/en/install/macos/client.xml diff -u phpdoc/en/install/macos/client.xml:1.3 phpdoc/en/install/macos/client.xml:1.4 --- phpdoc/en/install/macos/client.xml:1.3 Thu Jun 3 19:44:55 2004 +++ phpdoc/en/install/macos/client.xml Fri Jun 4 06:30:07 2004 @@ -1,17 +1,22 @@ - + - Compiling for MacOS X client + Compiling for MacOS X Client + + + - Those tips are graciously provided by Marc Liyanage. - - - The PHP module for the Apache web server included in Mac OS X. - This version includes support for the MySQL and PostgreSQL databases. - - - NOTE: Be careful when you do this, you could screw up your Apache web server! + The following instructions will help you install a PHP module for the Apache + web server included in MacOS X. This version includes support for the MySQL + and PostgreSQL databases. These instructions are graciously provided by + Marc Liyanage. + + +Be careful when you do this, you could screw up your Apache web server! + + Do this to install: http://cvs.php.net/diff.php/phpdoc/en/install/macos/index.xml?r1=1.3&r2=1.4&ty=u Index: phpdoc/en/install/macos/index.xml diff -u phpdoc/en/install/macos/index.xml:1.3 phpdoc/en/install/macos/index.xml:1.4 --- phpdoc/en/install/macos/index.xml:1.3 Thu Jun 3 19:45:15 2004 +++ phpdoc/en/install/macos/index.xml Fri Jun 4 06:30:07 2004 @@ -1,10 +1,13 @@ - + Installation on Mac OS X This section contains notes and hints specific to installing - PHP on Mac OS X. + PHP on Mac OS X. There are two slightly different versions of + Mac OS X, Client and Server, our manual deals with installing + PHP on both systems. Note that PHP is not available for MacOS + 9 and earlier versions. &install.macosx.packages; &install.macosx.server; http://cvs.php.net/diff.php/phpdoc/en/install/macos/packages.xml?r1=1.3&r2=1.4&ty=u Index: phpdoc/en/install/macos/packages.xml diff -u phpdoc/en/install/macos/packages.xml:1.3 phpdoc/en/install/macos/packages.xml:1.4 --- phpdoc/en/install/macos/packages.xml:1.3Thu Jun 3 19:45:15 2004 +++ phpdoc/en/install/macos/packages.xmlFri Jun 4 06:30:07 2004 @@ -1,5 +1,5 @@ - + Using Packages @@ -12,6 +12,9 @@ checking whether somebody has already built a packaged version of PHP with the features you need. + + + + Compiling for OS X Server - - There are two slightly different versions of Mac OS X, client and - server. The following is for OS X Server. - - - Mac OS X server install + + + Mac OS X Server install @@ -34,7 +31,7 @@ - If you want the compiler to do some optimization., you may also want to + If you want the compiler to do some optimization, you may also want to add this line: - You may get a message telling you that libmodphp4.a is out of date. If - so, go to the src/modules/php4 - directory inside your apache source directory and run this command: + You may get a message telling you that libmodphp4.a is + out of date. If so, go to the src/modules/php4 + directory inside your Apache source directory and run this command: ranlib libmodphp4.a. Then go back to the root of the - apache source directory and run the above configure + Apache source directory and run the above configure command again. That'll bring the link table up to date. Run make and make install again. http://cvs.php.net/diff.php/phpdoc/en/install/windows/apache1.xml?r1=1.1&r2=1.2&ty=u
[PHP-DOC] cvs: phpdoc /en/chapters DO_NOT_TRANSLATE
gobaFri Jun 4 05:44:16 2004 EDT Removed files: /phpdoc/en/chapters DO_NOT_TRANSLATE Log: I said: remove this
[PHP-DOC] cvs: phpdoc /en/chapters README /en/install/windows index.xml
gobaFri Jun 4 05:43:10 2004 EDT Added files: /phpdoc/en/chapters README Modified files: /phpdoc/en/install/windows index.xml Log: adding readme in place of DO_NOT_TRANSLATE, since now even file modification is discouraged (I will try to finish the install part to be production ready as soon as possible) http://cvs.php.net/diff.php/phpdoc/en/install/windows/index.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/install/windows/index.xml diff -u phpdoc/en/install/windows/index.xml:1.1 phpdoc/en/install/windows/index.xml:1.2 --- phpdoc/en/install/windows/index.xml:1.1 Thu Jun 3 18:45:11 2004 +++ phpdoc/en/install/windows/index.xml Fri Jun 4 05:43:10 2004 @@ -1,5 +1,5 @@ - + Installation on Windows systems @@ -30,6 +30,7 @@ &install.windows.iis; &install.windows.apache1; &install.windows.apache2; + &install.windows.iplanet; &install.windows.building; &install.windows.extensions;
Re: [PHP-DOC] Feedback for translation-practical.html
Hi Gary, In the following document: http://www.php.net/manual/howto/translation-practical.html the "word" paralelly is used. Please replace "paralelly" with the following: in parallel The "paralelly" doesn't exist as a word in English, and if it were, is misspelled. Therefore the clause of the third list item should read: Currently we have two systems used in parallel, not Currently we have two systems used paralelly, Thanks for the deep explanation, but this was fixed in the XML sources of that document in August 2003 (along with a lot more grammar problems), so there is nothing to fix there. That HTML version would probably need an update. Derick, can you do that? Goba
Re: [PHP-DOC] cvs: phpdoc /en/install/macos client.xml
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 04 June 2004 11:04, Gabor Hojtsy wrote: > > gui Thu Jun 3 19:44:55 2004 EDT > > > > Modified files: > > /phpdoc/en/install/macosclient.xml > > Log: > > reverting the yannick's mistake > > Please read the README file. I have added it for a reason! Indeed... I am really confused. Sorry... > Goba - -- Yannick -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAwD1gFJ1ADO+UjCcRAlYvAKCY3LdcOLlkVPM/ChYyQxkCY/czjQCcD7lP azpK+mbFWmkJ0ekdg1ZRWHY= =llNd -END PGP SIGNATURE-
Re: [PHP-DOC] cvs: phpdoc /en/install/macos client.xml
gui Thu Jun 3 19:44:55 2004 EDT Modified files: /phpdoc/en/install/macos client.xml Log: reverting the yannick's mistake Please read the README file. I have added it for a reason! Goba
