cvs: peardoc /en/guide/developers documentation.xml

danielc Wed Feb 11 21:46:44 2004 EDT Modified files: /peardoc/en/guide/developers documentation.xml Log: Revert unintended commit. http://cvs.php.net/diff.php/peardoc/en/guide/developers/documentation.xml?r1=1.3&r2=1.4&ty=u Index: peardoc/en/guide/developers/documentation.xml diff -u peardoc/en/guide/developers/documentation.xml:1.3 peardoc/en/guide/developers/documentation.xml:1.4 --- peardoc/en/guide/developers/documentation.xml:1.3 Wed Feb 11 21:43:20 2004 +++ peardoc/en/guide/developers/documentation.xml Wed Feb 11 21:46:44 2004 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.3 $ --> +<!-- $Revision: 1.4 $ --> <!-- WORK IN PROGRESS, THERE IS PROBABLY LITTLE POINT IN TRANSLATING THIS DOCUMENT YET. @@ -11,10 +11,6 @@ <firstname>Martin</firstname> <surname>Jansen</surname> </author> - <author> - <firstname>Daniel</firstname> - <surname>Convissor</surname> - </author> </docinfo> <title>Writing documentation</title> @@ -46,68 +42,16 @@ Even if Docbook XML can (like any other XML file) be written using a normal text editor, one needs to install some software on their machine in order to test the validity of the documenting - efforts. - </para> - - <para> - A list of the required software and a installation + efforts. A list of the required software and a installation instruction can be found in the <ulink url="&url.php.manual.howto;">PHP Documentation - HOWTO</ulink>. - </para> - <para> - Apart from providing information about the software, + HOWTO</ulink>. Apart from providing information about the software, this HOWTO does also provide a ton of other useful information that goes beyond this chapter. One is encouraged to completely read it. (Chapter II can be skipped, because it only contains information that is very PHP specific.) </para> <para> - If you are using a Windows machine, here are some tweaks to the - HOWTO's &quot;Installing the Tools&quot; section that will make - your documentation validation experience easier. - - <itemizedlist> - <listitem> - That page isn't clear on which Cygwin packages you need, but two - things you definitely need to install are autoconf and make, which - when running the setup program are under the Devel section. Once all - the Cygwin packages you need are installed, reboot your computer. - </listitem> - <listitem> - You don't need to check out the phpdoc sources. - </listitem> - <listitem> - You don't need to add a php.bat file to the phpdoc-tools directory. - </listitem> - <listitem> - Once you get the tools and peardoc sources (see below) installed, - the tree structure should look like this: - <informalexample> - <programlisting> -+--peardoc -| | -| +--CVS -| | -| +--en -| | -| \--... -| -\--phpdoc-tools - | - +--jade - | - \--jade.exe (etc) - </programlisting> - </informalexample> - </listitem> - </itemizedlist> - </para> - </sect2> - - <sect2> - <title>Getting the XML sources</title> - <para> Once the necessary software is in place, one has to get the latest version of the XML sources from PEAR's CVS repository: </para> @@ -141,36 +85,6 @@ mailinglist</ulink>. </para> </sect2> - - <sect2> - <title>Testing your docs</title> - <para> - Before committing your changes to CVS, make sure to test them out. - The second and third steps below only need to be done the first time. - </para> - <screen> - <userinput> -&dollar; cd peardoc - </userinput> - </screen> - <screen> - <userinput> -&dollar; autoconf - </userinput> - </screen> - <screen> - <userinput> -&dollar; ./configure - </userinput> - </screen> - <screen> - <userinput> -&dollar; make - </userinput> - </screen> - </sect2> - <xxxxxxxxxx> - </sect1> </chapter>