cvs: peardoc /en/chapters faq.xml

arnaud Fri Aug 15 17:18:01 2003 EDT Modified files: /peardoc/en/chapters faq.xml Log: * php4/pear became php-src/pear * typos * fix wrongly named id attribute Index: peardoc/en/chapters/faq.xml diff -u peardoc/en/chapters/faq.xml:1.7 peardoc/en/chapters/faq.xml:1.8 --- peardoc/en/chapters/faq.xml:1.7 Fri Aug 15 17:15:54 2003 +++ peardoc/en/chapters/faq.xml Fri Aug 15 17:18:01 2003 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.7 $ --> +<!-- $Revision: 1.8 $ --> <!-- [mj] The FAQ needs some heavy revision - don't translate it right now --> <chapter id="faq"> @@ -44,7 +44,7 @@ If you just want to make a simple extension that does not follow the <link linkend="standards">PEAR coding standards</link>, put it in pear/PECL/ extname (that is where extensions from - php4/ext/extname will be moved). If you want to write an extension + php-src/ext/extname will be moved). If you want to write an extension following PEAR's function/class naming, put it in pear/Foo_Bar or whatever the right name is. </para> @@ -106,7 +106,7 @@ <simpara> You can compile this extension directly into your PHP binary, too. For this you have to extract the package into - <filename>php4/ext</filename> (in your source directory). After + <filename>php-src/ext</filename> (in your source directory). After that do also phpize in this new module-directory. But before you can configure your main php-exectuable, you have to do a <filename>./buildconf</filename> @@ -118,14 +118,14 @@ --> <sect1 id="faq.separated"> <title> - Why is PEAR seperated into pear/ and php4/pear/? + Why is PEAR seperated into pear/ and php-src/pear/? </title> <titleabbrev> - Why pear/ and php4/pear? + Why pear/ and php-src/pear? </titleabbrev> <simpara> - The first elements of PEAR were stored in the directory php4/pear + The first elements of PEAR were stored in the directory php-src/pear and so they were bundled with each new PHP release. </simpara> <simpara> @@ -133,7 +133,7 @@ become too big to be bundled with every release of PHP. So there was a decision to commit all new elements to an own top level directory pear. The other elements which are currently remaining - in php4/pear will be moved to the new top level directory soon. + in php-src/pear will be moved to the new top level directory soon. Only the <link linkend="about-pfc">PFC code</link> and the PEAR package manager code will be bundled with every new release automatically. @@ -142,10 +142,10 @@ <sect1 id="faq.directory-structure"> <title> - Why does the directory structure of pear/ and php4/pear/ differ? + Why does the directory structure of pear/ and php-src/pear/ differ? </title> <titleabbrev> - Why do pear/ and php4/pear differ? + Why do pear/ and php-src/pear differ? </titleabbrev> <simpara> @@ -153,7 +153,7 @@ </simpara> <para> - The directory structure of <filename>php4/pear/</filename> + The directory structure of <filename>php-src/pear/</filename> matches that of the install tree (by default <filename>/usr/local/lib/php</filename>), and are organized as a simple hierarchy. However, the directory structure of @@ -274,14 +274,14 @@ package directory. </para> <para> - Test scripts are recommened when your class has to be compiled, + Test scripts are recommended when your class has to be compiled, requires special extentions/programs or needs correctly installed additional files (i.e. templates, graphics). Store them in sub directory called 'tests'. </para> </sect1> - <sect1 id="faq.competetive-packages"> + <sect1 id="faq.competitive-packages"> <title> Are different packages or classes with similar features allowed? </title> @@ -444,7 +444,7 @@ </para> <para> - The recomended licenses are + The recommended licenses are <ulink url="&url.license.php;">PHP</ulink>, <ulink url="&url.license.lgpl;">LGPL</ulink> and <ulink url="&url.license.bsd;">BSD</ulink>