[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
nohnWed Feb 14 18:02:14 2007 UTC Modified files: /phpdoc/en/faq obtaining.xml Log: * fix #40399 http://cvs.php.net/viewvc.cgi/phpdoc/en/faq/obtaining.xml?r1=1.21&r2=1.22&diff_format=u Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.21 phpdoc/en/faq/obtaining.xml:1.22 --- phpdoc/en/faq/obtaining.xml:1.21Sun Jul 31 19:05:13 2005 +++ phpdoc/en/faq/obtaining.xml Wed Feb 14 18:02:14 2007 @@ -1,5 +1,5 @@ - + Obtaining PHP Obtaining PHP @@ -38,7 +38,7 @@ many Linux distributions come with PHP built in these days. Windows binaries can be downloaded from our Downloads page, for Linux - binaries, please visit your distributions website. + binaries, please visit your distribution's website.
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
sfoxSun Jul 31 15:05:13 2005 EDT Modified files: /phpdoc/en/faq obtaining.xml Log: updating the ldap stuff http://cvs.php.net/diff.php/phpdoc/en/faq/obtaining.xml?r1=1.20&r2=1.21&ty=u Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.20 phpdoc/en/faq/obtaining.xml:1.21 --- phpdoc/en/faq/obtaining.xml:1.20Sun Aug 15 08:42:40 2004 +++ phpdoc/en/faq/obtaining.xml Sun Jul 31 15:05:13 2005 @@ -1,5 +1,5 @@ - + Obtaining PHP Obtaining PHP @@ -70,18 +70,13 @@ - LDAP* (Unix). - - - - LDAP (Unix/Win) : - Netscape Directory (LDAP) SDK 1.1. + Mozilla Directory (LDAP) SDK - free LDAP server. + free LDAP server.
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml /en/install/windows building.xml index.xml /en/language/oop5 basic.xml
nlopess Sun Aug 15 08:42:40 2004 EDT Modified files: /phpdoc/en/faq obtaining.xml /phpdoc/en/install/windows building.xml index.xml /phpdoc/en/language/oop5basic.xml Log: fix build http://cvs.php.net/diff.php/phpdoc/en/faq/obtaining.xml?r1=1.19&r2=1.20&ty=u Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.19 phpdoc/en/faq/obtaining.xml:1.20 --- phpdoc/en/faq/obtaining.xml:1.19Mon May 10 14:23:46 2004 +++ phpdoc/en/faq/obtaining.xml Sun Aug 15 08:42:40 2004 @@ -1,5 +1,5 @@ - + Obtaining PHP Obtaining PHP @@ -203,7 +203,7 @@ First, you will need Microsoft Visual C++ v6 (v5 may do it also, but we do it with v6), and you will need some support files. See the manual section about - building PHP from + building PHP from source on Windows. http://cvs.php.net/diff.php/phpdoc/en/install/windows/building.xml?r1=1.3&r2=1.4&ty=u Index: phpdoc/en/install/windows/building.xml diff -u phpdoc/en/install/windows/building.xml:1.3 phpdoc/en/install/windows/building.xml:1.4 --- phpdoc/en/install/windows/building.xml:1.3 Tue Aug 10 12:30:15 2004 +++ phpdoc/en/install/windows/building.xml Sun Aug 15 08:42:40 2004 @@ -1,6 +1,6 @@ - - + + Building from source Before getting started, it is worthwhile answering the question: @@ -27,7 +27,7 @@ - + &reftitle.required; To compile and build PHP you need a Microsoft @@ -72,7 +72,7 @@ - + Putting it all together After downloading the required packages you have to extract them in a @@ -155,7 +155,7 @@ - + Configure MVC ++ The next step is to configure MVC ++ to prepare for compiling. @@ -185,7 +185,7 @@ - + Build resolv.lib You must build the resolv.lib library. @@ -231,7 +231,7 @@ - + Compiling The best way to get started is to build the CGI version. http://cvs.php.net/diff.php/phpdoc/en/install/windows/index.xml?r1=1.12&r2=1.13&ty=u Index: phpdoc/en/install/windows/index.xml diff -u phpdoc/en/install/windows/index.xml:1.12 phpdoc/en/install/windows/index.xml:1.13 --- phpdoc/en/install/windows/index.xml:1.12Fri Aug 6 11:09:50 2004 +++ phpdoc/en/install/windows/index.xml Sun Aug 15 08:42:40 2004 @@ -1,5 +1,5 @@ - + Installation on Windows systems @@ -15,7 +15,7 @@ If you have Microsoft Visual Studio, you can also -build +build PHP from the original source code. http://cvs.php.net/diff.php/phpdoc/en/language/oop5/basic.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/language/oop5/basic.xml diff -u phpdoc/en/language/oop5/basic.xml:1.1 phpdoc/en/language/oop5/basic.xml:1.2 --- phpdoc/en/language/oop5/basic.xml:1.1 Sat Aug 14 20:17:12 2004 +++ phpdoc/en/language/oop5/basic.xml Sun Aug 15 08:42:40 2004 @@ -1,10 +1,10 @@ - + The Basics - + class Every class definition begins with the keyword class, followed by a class @@ -33,9 +33,9 @@ ]]> - + - + new To create an instance of an object, a new object must be created and @@ -93,9 +93,9 @@ ]]> - + - + extend A class can inherit methods and members of another class by using the @@ -108,7 +108,7 @@ linkend="language.oop5.final">final, by redeclaring them within the same name defined in the parent class. It is possible to access the overloaded method or members by referencing them with parent:: +linkend="language.oop5.paamayim-nekudotayim">parent:: Simple Class Inherintance @@ -137,7 +137,7 @@ ]]> - +
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
nlopess Mon May 10 14:23:47 2004 EDT Modified files: /phpdoc/en/faq obtaining.xml Log: the browscap problem is fixed now http://cvs.php.net/diff.php/phpdoc/en/faq/obtaining.xml?r1=1.18&r2=1.19&ty=u Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.18 phpdoc/en/faq/obtaining.xml:1.19 --- phpdoc/en/faq/obtaining.xml:1.18Mon Mar 1 08:39:21 2004 +++ phpdoc/en/faq/obtaining.xml Mon May 10 14:23:46 2004 @@ -1,5 +1,5 @@ - + Obtaining PHP Obtaining PHP @@ -215,7 +215,7 @@ You can find a browscap.ini file at - &url.browscap.download;. + &url.browscap.download;.
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
On Mon, 1 Mar 2004, Jakub Vrana wrote: > Derick Rethans wrote: > >> Removed anchor as it redirects user back > > > Please revert this until we have a final solution. > > I suspected this... I removed only the anchor, URL remained there. perfect :) Derick
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
On Mon, 1 Mar 2004, Mehdi Achour wrote: > Derick Rethans wrote: > > On Mon, 1 Mar 2004, Jakub Vrana wrote: > > > > > >>vrana Mon Mar 1 08:39:21 2004 EDT > >> > >> Modified files: > >>/phpdoc/en/faq obtaining.xml > >> Log: > >> Removed anchor as it redirects user back > >> # to do: try to fix get_browser and return the link > > > > > > Please revert this until we have a final solution. > > The link is actually redirecting back to php.net. > I'm sure Jakub removed the anchor so that user copy/paste the URL and > don't get redirected. What's the problem with this ? Ah, none then. Derick
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
Derick Rethans wrote: >> Removed anchor as it redirects user back > Please revert this until we have a final solution. I suspected this... I removed only the anchor, URL remained there. Mehdi Achour wrote: > The link is actually redirecting back to php.net. > I'm sure Jakub removed the anchor so that user copy/paste the URL and > don't get redirected. What's the problem with this ? Exactly. Jakub Vrana
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
On Mon, 1 Mar 2004, Jakub Vrana wrote: > vrana Mon Mar 1 08:39:21 2004 EDT > > Modified files: > /phpdoc/en/faqobtaining.xml > Log: > Removed anchor as it redirects user back > # to do: try to fix get_browser and return the link Please revert this until we have a final solution. Derick
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
Derick Rethans wrote: On Mon, 1 Mar 2004, Jakub Vrana wrote: vrana Mon Mar 1 08:39:21 2004 EDT Modified files: /phpdoc/en/faq obtaining.xml Log: Removed anchor as it redirects user back # to do: try to fix get_browser and return the link Please revert this until we have a final solution. The link is actually redirecting back to php.net. I'm sure Jakub removed the anchor so that user copy/paste the URL and don't get redirected. What's the problem with this ? didou
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
vrana Mon Mar 1 08:39:21 2004 EDT Modified files: /phpdoc/en/faq obtaining.xml Log: Removed anchor as it redirects user back # to do: try to fix get_browser and return the link http://cvs.php.net/diff.php/phpdoc/en/faq/obtaining.xml?r1=1.17&r2=1.18&ty=u Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.17 phpdoc/en/faq/obtaining.xml:1.18 --- phpdoc/en/faq/obtaining.xml:1.17Thu Feb 12 12:04:51 2004 +++ phpdoc/en/faq/obtaining.xml Mon Mar 1 08:39:21 2004 @@ -1,5 +1,5 @@ - + Obtaining PHP Obtaining PHP @@ -215,7 +215,7 @@ You can find a browscap.ini file at - &url.browscap.download;. + &url.browscap.download;.
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml /en/reference/snmp reference.xml /entities global.ent
nlopess Thu Feb 12 12:04:53 2004 EDT Modified files: /phpdoc/en/faq obtaining.xml /phpdoc/en/reference/snmp reference.xml /phpdoc/entitiesglobal.ent Log: ucd-snmp is obsolete UCD-SNMP and NET-SMP are the same http://cvs.php.net/diff.php/phpdoc/en/faq/obtaining.xml?r1=1.16&r2=1.17&ty=u Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.16 phpdoc/en/faq/obtaining.xml:1.17 --- phpdoc/en/faq/obtaining.xml:1.16Tue Feb 4 04:38:22 2003 +++ phpdoc/en/faq/obtaining.xml Thu Feb 12 12:04:51 2004 @@ -1,5 +1,5 @@ - + Obtaining PHP Obtaining PHP @@ -92,7 +92,7 @@ - SNMP* (Unix): . + SNMP* (Unix): . http://cvs.php.net/diff.php/phpdoc/en/reference/snmp/reference.xml?r1=1.7&r2=1.8&ty=u Index: phpdoc/en/reference/snmp/reference.xml diff -u phpdoc/en/reference/snmp/reference.xml:1.7 phpdoc/en/reference/snmp/reference.xml:1.8 --- phpdoc/en/reference/snmp/reference.xml:1.7 Sun Jul 13 05:45:47 2003 +++ phpdoc/en/reference/snmp/reference.xml Thu Feb 12 12:04:52 2004 @@ -1,5 +1,5 @@ - + SNMP functions SNMP @@ -15,7 +15,6 @@ &reftitle.required; In order to use the SNMP functions on Unix you need to install the - UCD SNMP or NET-SNMP package. On Windows these functions are only available on NT and not on Win95/98. http://cvs.php.net/diff.php/phpdoc/entities/global.ent?r1=1.163&r2=1.164&ty=u Index: phpdoc/entities/global.ent diff -u phpdoc/entities/global.ent:1.163 phpdoc/entities/global.ent:1.164 --- phpdoc/entities/global.ent:1.163Thu Feb 12 02:04:55 2004 +++ phpdoc/entities/global.ent Thu Feb 12 12:04:53 2004 @@ -1,6 +1,6 @@
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
Ok, its done and ready for commit. faqurl.ent is properly merged with global.ent, no leading faqurl anymore. The en/faq is updated properly and also ready to commit, the build system gets rid off faqurl.ent (manual.xml.in installpart.xml modofied) BUT, following (partly) translations exists: phpdoc-cs phpdoc-de phpdoc-he phpdoc-it phpdoc-ja phpdoc-pl phpdoc-zh Three ways to go on: (A) Commiting and let the other lang modules take care for the changes. (B) Inform the other translation teams, explain them what happend and how they can easily fix their faq translation. Maybe (A) and (B) together, or Lets do (B) first, then if for some time they do not reply, (A). Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
> > Commemts? > > I don't see a reason to have any faq only urls. Why > do we need this at all? I vote merge them all! :) > Ok, its done and ready for commit. faqurl.ent is properly merged with global.ent, no leading faqurl anymore. The en/faq is updated properly and also ready to commit, the build system gets rid off faqurl.ent (manual.xml.in installpart.xml modofied) BUT, following (partly) translations exists: phpdoc-cs phpdoc-de phpdoc-he phpdoc-it phpdoc-ja phpdoc-pl phpdoc-zh Three ways to go on: (A) Commiting and let the other lang modules take care for the changes. (B) Inform the other translation teams, explain them what happend and how they can easily fix their faq translation. Maybe (A) and (B) together, or (c) I check out the modules in question and make the changes. Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
On Sun, 26 Jan 2003, Friedhelm Betz wrote: > > > I totally agree with your point of view ;-) > > > It might be desirable to merge faqurl amd global entities file? > > > > I like this idea, why do we have faq specific urls at all? > > It seems like a bad idea and only means duplicate urls. > > Serious votes against merging faqurl.ent and global.ent? > > My ideas: > > Merge them, seperate special faqonly urls by comment > > and keep the leading faqurl for those special urls > > Commemts? I don't see a reason to have any faq only urls. Why do we need this at all? I vote merge them all! :) Regards, Philip -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
I totally agree with your point of view ;-) It might be desirable to merge faqurl amd global entities file? I like this idea, why do we have faq specific urls at all? It seems like a bad idea and only means duplicate urls. Serious votes against merging faqurl.ent and global.ent? My ideas: Merge them, seperate special faqonly urls by comment and keep the leading faqurl for those special urls Commemts? OK. Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
> > I totally agree with your point of view ;-) > > It might be desirable to merge faqurl amd global entities file? > > I like this idea, why do we have faq specific urls at all? > It seems like a bad idea and only means duplicate urls. Serious votes against merging faqurl.ent and global.ent? My ideas: Merge them, seperate special faqonly urls by comment and keep the leading faqurl for those special urls Commemts? I would like to see this merge very soon to avoid conflicts with already translated faq sections. I know the fallback solution for entities but if they are renamed (like the infozip one would become, because its simply doubled) this mechanism will fail. Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] reference: where to obtain files. was Re: [PHP-DOC]cvs: phpdoc /en/faq obtaining.xml
I see three options: a) Update the faq by hand with links used in reference.xml b) Create an autogenerated list here c) Remove most of the faq and simply state that the info has been moved as each extension now lists how to obtain.. I like the idea of (c). I also like the idea of (b) in the future but this doesn't really belong in the faq but rather when we finally autogenerate a list of all configure options, it'd go near there. c) + autogenerate the list in the future to an appendix. This information should really be in the reference sections, and not in a faq. This information is core. On a related note. Windows dll information should be listed within every reference.xml too as currently only some list this information. Like: a) If the dll is bundled b) If it's compiled in the binary (no dll needed) c) If the dll can be found offsite (mcrypt is an example) Windows dll information should also be moved out of the install (or configure?) section where it is currently (a list of Windows dlls), and moved to the reference sections with all information available ;) Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] Re: reference: where to obtain files. was Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
> On Fri, 24 Jan 2003, Gabor Hojtsy wrote: >> > This page is outdated and does not coincide with what we >> > have in the reference.xml files. Sometimes the faq urls >> > are different than the 'normal' ones. >> > >> > To remain BC, we can keep this faq but how about we not >> > use the faq urls for it but rather we use the same links >> > found within each reference.xml instead. >> >> This should be moved to the reference part IMHO, as it is partly >> there already ;) > AFAICT it's fully in both places currently. I believe every > reference.xml now has this information, at least it should. > I see three options: > a) Update the faq by hand with links used in reference.xml ugly ;-) > b) Create an autogenerated list here > c) Remove most of the faq and simply state that the info > has been moved as each extension now lists how to obtain.. +1 > I like the idea of (c). I also like the idea of (b) in the > future but this doesn't really belong in the faq but rather > when we finally autogenerate a list of all configure options, > it'd go near there. autogenerated list yes, but not in the faq. > On a related note. Windows dll information should be listed > within every reference.xml too as currently only some list > this information. Like: > a) If the dll is bundled I remember Sara Golemon did some work on this, but I don't know how far it is complete. > b) If it's compiled in the binary (no dll needed) As I can say, builtin information is up to date (4.3.0) (Working on the configure options I added this info where appropriate) > c) If the dll can be found offsite (mcrypt is an example) Can't remember any other like mcrypt. And IMHO the "offical policy" suggests to use only the dlls provided by php.net, where mcrypt seems to be a special topic. If anyone likes to work on the windows dll topic, it would be helpfull to use /en/refernce/rsusi.txt or open an similar file, where the ongoing work could be noted. Regards Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
>> I totally agree with your point of view ;-) >> It might be desirable to merge faqurl amd global entities file? > I like this idea, why do we have faq specific urls at all? Historic reasons? The integration of the FAQ happend not too long ago, therfore I guess. > It seems like a bad idea and only means duplicate urls. +1 for merging. >> btw: to add one more topic to statistics and summaries, what about a >> generated list (from references) of all external libs? I do not apply >> for. > Sounds like a good idea to me although not sure how this > would be done. Some of the requirements sections are > wordy. Can you explain your idea a little further and > what the end result would look like? In short: Each reference.xml holds an section like . Scanning for patterns should be possible, extracting and collecting them in a general list, which goes into an appendix (ore somewhere else?). Looks like: External libs Library Download required by extension Bzip2:url link to bzip2 Curl: url link to Curl Attention should be payed to some common ones like zlib. This is IMHO not a must have feature, but nice to have a central overview. Regards Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] reference: where to obtain files. was Re: [PHP-DOC] cvs: phpdoc/en/faq obtaining.xml
On Fri, 24 Jan 2003, Gabor Hojtsy wrote: > > This page is outdated and does not coincide with what we > > have in the reference.xml files. Sometimes the faq urls > > are different than the 'normal' ones. > > > > To remain BC, we can keep this faq but how about we not > > use the faq urls for it but rather we use the same links > > found within each reference.xml instead. > > This should be moved to the reference part IMHO, as it is partly > there already ;) AFAICT it's fully in both places currently. I believe every reference.xml now has this information, at least it should. I see three options: a) Update the faq by hand with links used in reference.xml b) Create an autogenerated list here c) Remove most of the faq and simply state that the info has been moved as each extension now lists how to obtain.. I like the idea of (c). I also like the idea of (b) in the future but this doesn't really belong in the faq but rather when we finally autogenerate a list of all configure options, it'd go near there. On a related note. Windows dll information should be listed within every reference.xml too as currently only some list this information. Like: a) If the dll is bundled b) If it's compiled in the binary (no dll needed) c) If the dll can be found offsite (mcrypt is an example) Regards, Philip -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
> > On a related note: > > > This page is outdated and does not coincide with what we > > have in the reference.xml files. Sometimes the faq urls > > are different than the 'normal' ones. > > > To remain BC, we can keep this faq but how about we not > > use the faq urls for it but rather we use the same links > > found within each reference.xml instead. > > I totally agree with your point of view ;-) > It might be desirable to merge faqurl amd global entities file? I like this idea, why do we have faq specific urls at all? It seems like a bad idea and only means duplicate urls. > btw: to add one more topic to statistics and summaries, what about a > generated list (from references) of all external libs? I do not apply > for. Sounds like a good idea to me although not sure how this would be done. Some of the requirements sections are wordy. Can you explain your idea a little further and what the end result would look like? Regards, Philip -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
This page is outdated and does not coincide with what we have in the reference.xml files. Sometimes the faq urls are different than the 'normal' ones. To remain BC, we can keep this faq but how about we not use the faq urls for it but rather we use the same links found within each reference.xml instead. This should be moved to the reference part IMHO, as it is partly there already ;) Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
> On a related note: > This page is outdated and does not coincide with what we > have in the reference.xml files. Sometimes the faq urls > are different than the 'normal' ones. > To remain BC, we can keep this faq but how about we not > use the faq urls for it but rather we use the same links > found within each reference.xml instead. I totally agree with your point of view ;-) It might be desirable to merge faqurl amd global entities file? btw: to add one more topic to statistics and summaries, what about a generated list (from references) of all external libs? I do not apply for. In the case of infozip the faqurl entity was really out of range :-) Regards Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
On a related note: This page is outdated and does not coincide with what we have in the reference.xml files. Sometimes the faq urls are different than the 'normal' ones. To remain BC, we can keep this faq but how about we not use the faq urls for it but rather we use the same links found within each reference.xml instead. Regards, Philip -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
betzFri Jan 24 15:05:23 2003 EDT Modified files: /phpdoc/en/faq obtaining.xml Log: tabs 2 spaces Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.14 phpdoc/en/faq/obtaining.xml:1.15 --- phpdoc/en/faq/obtaining.xml:1.14Wed Apr 3 12:46:45 2002 +++ phpdoc/en/faq/obtaining.xml Fri Jan 24 15:05:23 2003 @@ -1,5 +1,5 @@ - + Obtaining PHP Obtaining PHP @@ -64,119 +64,119 @@ - -LDAP (Unix). - - - - -LDAP* (Unix). - - - - -LDAP (Unix/Win) : -Netscape Directory (LDAP) SDK 1.1. - - - - -free LDAP server. - - - - -Berkeley DB2 (Unix/Win) : -&faqurl.sleepycat;. - - - - -SNMP* (Unix): . - - - - -GD* (Unix/Win). - - - - -mSQL* (Win). - - - - -mSQL* (Unix). - - - - -PostgreSQL (Unix). - - - - -IMAP* (Win/Unix). - - - - -Sybase-CT* (Linux, libc5) : -Available locally. - - - - -FreeType (libttf):. - - - - -ZLib (Unix/Win32). - - - - -expat XML parser (Unix/Win32). - - - - -PDFLib. - - - - -mcrypt. - - - - -mhash. - - - - -t1lib. - - - - -dmalloc. - - - - -aspell. - - - - -readline. - - - + + LDAP (Unix). + + + + + LDAP* (Unix). + + + + + LDAP (Unix/Win) : + Netscape Directory (LDAP) SDK 1.1. + + + + + free LDAP server. + + + + + Berkeley DB2 (Unix/Win) : + &faqurl.sleepycat;. + + + + + SNMP* (Unix): . + + + + + GD* (Unix/Win). + + + + + mSQL* (Win). + + + + + mSQL* (Unix). + + + + + PostgreSQL (Unix). + + + + + IMAP* (Win/Unix). + + + + + Sybase-CT* (Linux, libc5) : + Available locally. + + + + + FreeType (libttf):. + + + + + ZLib (Unix/Win32). + + + + + expat XML parser (Unix/Win32). + + + + + PDFLib. + + + + + mcrypt. + + + + + mhash. + + + + + t1lib. + + + + + dmalloc. + + + + + aspell. + + + + + readline. + + + -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
cortesi Wed Apr 3 12:46:54 2002 EDT Modified files: /phpdoc/en/faq obtaining.xml Log: one commit to Uppercase the all Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.13 phpdoc/en/faq/obtaining.xml:1.14 --- phpdoc/en/faq/obtaining.xml:1.13Sat Jan 12 05:38:23 2002 +++ phpdoc/en/faq/obtaining.xml Wed Apr 3 12:46:45 2002 @@ -1,5 +1,5 @@ - + Obtaining PHP Obtaining PHP @@ -65,17 +65,17 @@ -LDAP (unix). +LDAP (Unix). -LDAP* (unix). +LDAP* (Unix). -LDAP (unix/win) : +LDAP (Unix/Win) : Netscape Directory (LDAP) SDK 1.1.
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
zak Sat Jan 12 05:38:23 2002 EDT Modified files: /phpdoc/en/faq obtaining.xml Log: Removed MySQL from the list of non-thread-safe extensions -- they have a thread safe lib Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.12 phpdoc/en/faq/obtaining.xml:1.13 --- phpdoc/en/faq/obtaining.xml:1.12Thu Dec 13 04:47:08 2001 +++ phpdoc/en/faq/obtaining.xml Sat Jan 12 05:38:23 2002 @@ -1,5 +1,5 @@ - + Obtaining PHP Obtaining PHP @@ -108,11 +108,6 @@ mSQL* (Unix). - - - - -MySQL* (Unix).
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
jeroen Sun Aug 5 11:14:45 2001 EDT Modified files: /phpdoc/en/faq obtaining.xml Log: Remove a ':w' save Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.5 phpdoc/en/faq/obtaining.xml:1.6 --- phpdoc/en/faq/obtaining.xml:1.5 Sun Aug 5 06:51:44 2001 +++ phpdoc/en/faq/obtaining.xml Sun Aug 5 11:14:45 2001 @@ -1,4 +1,4 @@ - + Obtaining PHP Obtaining PHP @@ -194,8 +194,7 @@ - :w - + I got the latest version of the PHP source code from the CVS repository on my Windows 95/NT machine, what do I need to compile it? @@ -240,4 +239,5 @@ sgml-local-catalogs:nil sgml-local-ecat-files:nil End: + vim: ts=1 sw=1 et syntax=sgml -->
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
gobaSun Jul 22 09:39:57 2001 EDT Modified files: /phpdoc/en/faq obtaining.xml Log: Copy pasting is dangerous :)) Index: phpdoc/en/faq/obtaining.xml diff -u phpdoc/en/faq/obtaining.xml:1.2 phpdoc/en/faq/obtaining.xml:1.3 --- phpdoc/en/faq/obtaining.xml:1.2 Sat Jul 21 07:42:27 2001 +++ phpdoc/en/faq/obtaining.xml Sun Jul 22 09:39:57 2001 @@ -10,7 +10,7 @@ - What is PHP? + Where can I obtain PHP?
[PHP-DOC] cvs: phpdoc /en/faq obtaining.xml
damsWed Jul 18 10:34:08 2001 EDT Added files: /phpdoc/en/faq obtaining.xml Log: Adding new entry to faq.Still 8 to come :-) Index: phpdoc/en/faq/obtaining.xml +++ phpdoc/en/faq/obtaining.xml Obtaining PHP Where to download PHP? This section has details about PHP download locations, and OS issues. What is PHP? You can download PHP from any of the members of the PHP network of sites. These can be found at &faqurl.php;. You can also use anonymous CVS to get the absolute latest version of the source. For more information, go to &faqurl.php.cvs;. Are pre-compiled binary versions available? Yes, although they are not always up to date. The Windows binary is generally current, but the Unix binaries lag behind and are only available for certain platforms. All download are available in the Downloads section. Where can I get libraries needed to compile some of the optional PHP extensions? Those marked with * are not thread-safe libraries, and should not be used with PHP as a server module in the multi-threaded Windows web servers (IIS, Netscape). This does not matter in Unix environments, yet. LDAP (unix). LDAP* (unix). LDAP (unix/win) : Netscape Directory (LDAP) SDK 1.1. free LDAP server. Berkeley DB2 (Unix/Win) : &faqurl.sleepycat;. SNMP* (Unix): . GD* (Unix/Win). mSQL* (Win). mSQL* (Unix). MySQL* (Unix). IMAP* (Win/Unix). Sybase-CT* (Linux, libc5) : Available locally. FreeType (libttf):. ZLib (Unix/Win32). expat XML parser (Unix/Win32). PDFLib. mcrypt. mhash. t1lib. dmalloc. aspell. readline. How do I get these libraries to work? You will need to follow instructions provided with the library. Some of these libraries are detected automatically when you run the 'configure' script of PHP (such as the GD library), and others you will have to enable using '--with-EXTENSION' options to 'configure'. Run 'configure --help' for a listing of these. I got the latest version of the PHP source code from the CVS repository on my Windows 95/NT machine, what do I need to compile it? First, you will need Microsoft Visual C++ v6 (v5 may do it also, but we do it with v6), and you will need to download the support files. You will need to unzip this file (which has subdirectories, so make sure your unzip program keeps them) into the win32 subdirectory of the source distribution. Where do I find the Browser Capabilities File? You can find a browscap.ini file at &faqurl.browscap;.
